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 d6a38798fc..e56a9183f1 100644 --- a/translations/de-DE/content/actions/creating-actions/about-actions.md +++ b/translations/de-DE/content/actions/creating-actions/about-actions.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'übersicht' topics: - - Action development - - Fundamentals + - 'Action development' + - 'Fundamentals' --- {% 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 06a4177f2d..f43c028893 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 @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'Referenz' --- {% data reusables.actions.enterprise-beta %} 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 196b198120..ce398fb1e9 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 @@ -1,7 +1,7 @@ --- title: Metadaten-Syntax für GitHub-Aktionen shortTitle: Metadaten-Syntax -intro: 'Du kannst Aktionen erstellen, um Aufgaben in Ihrem Repository zu erledigen. Für Aktionen ist eine Metadaten-Datei erforderlich, welche die YAML-Syntax verwendet.' +intro: Du kannst Aktionen erstellen, um Aufgaben in Ihrem Repository zu erledigen. Für Aktionen ist eine Metadaten-Datei erforderlich, welche die YAML-Syntax verwendet. product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/metadata-syntax-for-github-actions @@ -12,7 +12,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'Referenz' --- {% data reusables.actions.enterprise-beta %} @@ -58,7 +58,7 @@ inputs: Wenn Du eine Eingabe für eine Aktion in einer Workflow-Datei angibst oder einen Standardeingabewert verwendest, erstellt {% data variables.product.prodname_dotcom %} eine Umgebungsvariable für die Eingabe mit dem Namen `INPUT_`. Die erstellte Umgebungsvariable wandelt Eingabenamen in Großbuchstaben um und ersetzt Leerzeichen durch `_`-Zeichen. -Wenn beispielsweise ein Workflow die Eingaben „numOctocats“ und „octocatEyeColor“ definiert hat, kann der Aktionscode die Werte für die Eingaben mithilfe der Umgebungsvariablen `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` lesen. +For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables. #### `inputs.` @@ -76,6 +76,10 @@ Wenn beispielsweise ein Workflow die Eingaben „numOctocats“ und „octocatEy **Optional**: Ein `String`, der den Standardwert darstellt. Der Standardwert wird verwendet, wenn ein Eingabeparameter in einer Workflow-Datei nicht angegeben ist. +#### `inputs..deprecationMessage` + +**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives. + ### `outputs` **Optional**: Ausgabeparameter erlauben Dir, Daten zu deklarieren, die eine Aktion setzt. Aktionen, die in einem Workflow später ausgeführt werden, können die Ausgabedaten der zuvor ausgeführten Aktionen verwenden. Wenn beispielsweise eine Aktion vorliegt, die zwei Eingaben addiert hat (x + y = z), kann die Aktion die Summe (z) für andere Aktionen ausgeben, damit sie als Eingabe verwendet wird. 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 276fb3a4ea..903872ff3e 100644 --- a/translations/de-DE/content/actions/guides/about-continuous-integration.md +++ b/translations/de-DE/content/actions/guides/about-continuous-integration.md @@ -10,11 +10,16 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' type: 'overview' +topics: + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### Informationen zur fortlaufenden Integration @@ -26,7 +31,9 @@ Zum Erstellen und Testen des Codes ist ein Server erforderlich. Sie können Aktu ### Informationen zur kontinuierlichen Integration mit {% data variables.product.prodname_actions %} -CI mit {% data variables.product.prodname_actions %} bietet Workflows, die den Code in Ihrem Repository erstellen und Ihre Tests ausführen können. Workflows können auf {% data variables.product.prodname_dotcom %}gehosteten virtuellen Maschinen oder auf Computern ausgeführt werden, die Sie selbst hosten. 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)." +{% if currentVersion == "github-ae@latest" %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on virtual machines hosted by {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." +{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows können auf {% data variables.product.prodname_dotcom %}gehosteten virtuellen Maschinen oder auf Computern ausgeführt werden, die Sie selbst hosten. 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)." +{% endif %} Sie können Ihren CI-Workflow so konfigurieren, dass er ausgeführt wird, wenn ein {% data variables.product.product_name %} Ereignis auftritt (z. B. wenn neuer Code an Ihr Repository übertragen wird), nach einem festgelegten Zeitplan oder wenn ein externes Ereignis mithilfe des Repository-Dispatch-Webhooks auftritt. @@ -46,6 +53,26 @@ Eine Definition von gebräuchliche Begriffe finden Sie unter "[Kernkonzepte für Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +### Skipping workflow runs + +If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any any of the following strings to the commit message in a push, or the HEAD commit of a pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`. + +You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message. + +{% note %} + +**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running. + +{% endnote %} + ### Benachrichtigungen für Workflow-Läufe {% data reusables.repositories.workflow-notifications %} 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 c5a81826e9..20a69e6daa 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 @@ -9,9 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'übersicht' topics: - - Pakete erstellen + - 'Pakete erstellen' --- {% 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 acde483706..4a1daf9c37 100644 --- a/translations/de-DE/content/actions/guides/about-service-containers.md +++ b/translations/de-DE/content/actions/guides/about-service-containers.md @@ -9,10 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'übersicht' topics: - - Containers - - Docker + - 'Containers' + - 'Docker' --- {% 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 ae9fd07e4a..a76df7bca0 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Ant run: ant -noinput -buildfile build.xml ``` @@ -70,7 +71,7 @@ jobs: Dieser Workflow führt die folgenden Schritte aus: 1. Der Schritt `checkout` lädt eine Kopie Deines Repositorys auf den Runner herunter. -2. Der Schritt `setup-java` konfiguriert das Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. Der Schritt „Build with Ant“ (mittels Ant bauen) führt das standardmäßige „Target“ (Ziel) in Deiner `build.xml` im nicht-interaktiven Modus aus. Die Standard-Workflow-Vorlagen sind ausgezeichnete Ausgangspunkte beim Erstellen des Build- und Testworkflows, und Du kannst die Vorlage an die Anforderungen Deines Projekts anpassen. @@ -91,9 +92,10 @@ Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder ein anderes Ziel ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Ant jar target run: ant -noinput -buildfile build-ci.xml jar ``` @@ -109,7 +111,11 @@ Ant erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichni ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ant -noinput -buildfile build.xml - uses: actions/upload-artifact@v2 with: 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 4aadf45fca..64383d883b 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Gradle run: ./gradlew build ``` @@ -70,7 +71,7 @@ jobs: Dieser Workflow führt die folgenden Schritte aus: 1. Der Schritt `checkout` lädt eine Kopie Deines Repositorys auf den Runner herunter. -2. Der Schritt `setup-java` konfiguriert das Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. Der Schritt "Build with Gradle" führt das Wrapper-Skript `gradlew` aus, um sicherzustellen, dass dein Code gebaut, Tests bestanden und ein Paket erstellt werden kann. Die Standard-Workflow-Vorlagen sind ausgezeichnete Ausgangspunkte beim Erstellen des Build- und Testworkflows, und Du kannst die Vorlage an die Anforderungen Deines Projekts anpassen. @@ -91,9 +92,10 @@ Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder einen anderen Ta ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Gradle package task run: ./gradlew -b ci.gradle package ``` @@ -107,10 +109,11 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Gradle packages uses: actions/cache@v2 with: @@ -143,7 +146,11 @@ Gradle erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeic ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ./gradlew build - uses: actions/upload-artifact@v2 with: 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 4d6b19aee1..d607b24522 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Maven run: mvn --batch-mode --update-snapshots verify ``` @@ -70,7 +71,7 @@ jobs: Dieser Workflow führt die folgenden Schritte aus: 1. Der Schritt `checkout` lädt eine Kopie Deines Repositorys auf den Runner herunter. -2. Der Schritt `setup-java` konfiguriert das Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. Der Schritt "Build with Maven" führt das Maven-„Target“ (Ziel) `package` im nicht-interaktiven Modus aus, um sicherzustellen, dass der Code gebaut, Tests bestanden und ein Paket erstellt werden kann. Die Standard-Workflow-Vorlagen sind ausgezeichnete Ausgangspunkte beim Erstellen des Build- und Testworkflows, und Du kannst die Vorlage an die Anforderungen Deines Projekts anpassen. @@ -91,9 +92,10 @@ Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder ein anderes Ziel ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Maven verify phase run: mvn --batch-mode --update-snapshots verify ``` @@ -107,10 +109,11 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Maven packages uses: actions/cache@v2 with: @@ -134,7 +137,10 @@ Maven erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeich ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 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 index f6e6a54ec9..a730c9395a 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-net.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: ['3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -81,7 +81,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet: [ '2.2.103', '3.0', '3.1.x' ] + dotnet: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -201,7 +201,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 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 4a3277a3a8..bd38b60242 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 @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -143,9 +144,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -209,9 +211,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to the Maven Central Repository run: gradle publish env: 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 0e3603d37e..ea99697a6a 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 @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -147,9 +148,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: mvn --batch-mode deploy env: @@ -183,9 +185,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java for publishing to Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -195,9 +198,10 @@ jobs: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to GitHub Packages run: mvn --batch-mode deploy env: 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 2959a60a93..f17483ad3c 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,11 +11,16 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' type: 'tutorial' +topics: + - 'Workflows' + - 'CI' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} Jeder Benutzer mit Schreibberechtigung für ein Repository kann mit {% data variables.product.prodname_actions %} eine fortlaufende Integration (CI) einrichten. @@ -29,7 +34,7 @@ Nach der Einrichtung der CI können Sie den Workflow an Ihre Bedürfnisse anpass {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -Sobald ein Push an Ihr Repository erfolgt ist, können Sie den Status und die detaillierten Protokolle Ihres fortlaufenden Integrationsworkflows verfolgen, der auf {% data variables.product.prodname_dotcom %} ausgeführt wird, und angepasste Benachrichtigungen erhalten. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)“ und „[Workflowausführung verwalten](/articles/managing-a-workflow-run)“. +Sobald ein Push an Dein Repository erfolgt ist, kannst Du den Status und die detaillierten Protokolle Deines fortlaufenden Integrationsworkflows verfolgen, der auf {% data variables.product.prodname_dotcom %} ausgeführt wird, und angepasste Benachrichtigungen erhalten. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)“ und „[Workflowausführung verwalten](/articles/managing-a-workflow-run)“. {% data reusables.repositories.actions-workflow-status-badge-into %} diff --git a/translations/de-DE/content/actions/guides/using-github-actions-for-project-management.md b/translations/de-DE/content/actions/guides/using-github-actions-for-project-management.md index d1b1191979..f1f5ee4795 100644 --- a/translations/de-DE/content/actions/guides/using-github-actions-for-project-management.md +++ b/translations/de-DE/content/actions/guides/using-github-actions-for-project-management.md @@ -1,14 +1,14 @@ --- title: Using GitHub Actions for project management -intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.' +intro: You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'übersicht' topics: - - Project management + - 'Project management' --- You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board. 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 e8915fd65e..7456c039f9 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'übersicht' --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -125,7 +125,7 @@ You must ensure that the self-hosted runner has appropriate network access to co For example, if your instance name is `octoghae`, then you will need to allow the self-hosted runner to access `octoghae.github.com`. If you use an IP address allow list for your -{% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. Weitere Informationen findest Du auf „[Zugelassene IP-Adressen für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)." +{% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. Weitere Informationen findest Du auf „[Zugelassene IP-Adressen für Deine Organisation verwalten](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)." {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -145,7 +145,7 @@ pkg-containers.githubusercontent.com pkg-containers-az.githubusercontent.com ``` -If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". +If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". {% else %} diff --git a/translations/de-DE/content/actions/index.md b/translations/de-DE/content/actions/index.md index d1595477fe..55c71f0de8 100644 --- a/translations/de-DE/content/actions/index.md +++ b/translations/de-DE/content/actions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /actions/reference/encrypted-secrets changelog: label: 'actions' - prefix: 'GitHub Actions: ' + prefix: 'GitHub Actions:' product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ 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 6fc2f130c9..e51db55ec2 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'übersicht' topics: - - Fundamentals + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} 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 1a2f254f2d..5beedb4c2a 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 @@ -10,9 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'übersicht' topics: - - Fundamentals + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} 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 a0854e1ab0..cb42484efc 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,13 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: overview + github-ae: '*' +type: 'übersicht' topics: - - Sicherheit + - 'Sicherheit' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### Übersicht @@ -22,9 +24,9 @@ This guide explains how to configure security hardening for certain {% data vari ### Using secrets -Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}. +Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}. -Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps the minimize risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime. +Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps minimize the risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime. To help prevent accidental disclosure, {% data variables.product.product_name %} uses a mechanism that attempts to redact any secrets that appear in run logs. This redaction looks for exact matches of any configured secrets, as well as common encodings of the values, such as Base64. However, because there are multiple ways a secret value can be transformed, this redaction is not guaranteed. As a result, there are certain proactive steps and good practices you should follow to help ensure secrets are redacted, and to limit other risks associated with secrets: @@ -41,7 +43,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %} - **Audit and rotate registered secrets** - Periodically review the registered secrets to confirm they are still required. Remove those that are no longer needed. - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - **Consider requiring review for access to secrets** - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)." {% endif %} @@ -75,7 +77,7 @@ This means that a compromise of a single action within a workflow can be very si ### Considering cross-repository access -{% data variables.product.product_name %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so having the `GITHUB_TOKEN` for one repository grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators. +{% data variables.product.prodname_actions %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so allowing the `GITHUB_TOKEN` for one repository to grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators. We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended. @@ -115,33 +117,68 @@ Some customers might attempt to partially mitigate these risks by implementing s You can use the audit log to monitor administrative tasks in an organization. The audit log records the type of action, when it was run, and which user account performed the action. -For example, you can use the audit log to track the `action:org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png) +For example, you can use the audit log to track the `org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png) -The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." + +{% if currentVersion == "free-pro-team@latest" %} +#### Events for environments + +| Aktion | Beschreibung | +| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `environment.remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Events for configuration changes +| Aktion | Beschreibung | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +{% endif %} #### Events for secret management -| Aktion | Beschreibung | -| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `action:org.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). | -| `action:org.remove_actions_secret` | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:org.update_actions_secret` | Triggered when a organization admin updates a {% data variables.product.prodname_actions %} secret. | -| `action:repo.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). | -| `action:repo.remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:repo.update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret. | +| Aktion | Beschreibung | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `org.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)." | +| `org.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed. | +| `org.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated. | +| `repo.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." | +| `repo.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed. | +| `repo.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated. | #### Events for self-hosted runners -| Aktion | Beschreibung | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.register_self_hosted_runner` | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | -| `action:org.remove_self_hosted_runner` | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | -| `action:repo.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). | -| `action:repo.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). | +| Aktion | Beschreibung | +| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% else %} | | +| `enterprise.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an enterprise](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)." | +| `enterprise.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. | +| `enterprise.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." | +| `enterprise.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI. This event is not included when you export the audit log as JSON data or a CSV file. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" and "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."{% endif %} +| `org.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." | +| `org.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see [Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | +| `org.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." | +| `org.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `org.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)“. | +| `repo.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `repo.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." | +| `repo.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)“. | #### Events for self-hosted runner groups -| Aktion | Beschreibung | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.runner_group_created` | Triggered when an organization admin [creates a self-hosted runner group](/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` | Triggered when an organization admin removes a self-hosted runner group. | -| `action:org.runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | -| `action:org.runner_group_runners_added` | Triggered when an organization admin [adds a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +| Aktion | Beschreibung | +| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `enterprise.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an enterprise](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)." | +| `enterprise.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `enterprise.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. | +| `enterprise.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." | +| `enterprise.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `org.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." | +| `org.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `org.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." | +| `org.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | + +#### Events for workflow activities + +{% data reusables.actions.actions-audit-events-workflow %} diff --git a/translations/de-DE/content/actions/quickstart.md b/translations/de-DE/content/actions/quickstart.md index 4e7fcd24a1..8c0d009947 100644 --- a/translations/de-DE/content/actions/quickstart.md +++ b/translations/de-DE/content/actions/quickstart.md @@ -1,6 +1,6 @@ --- title: Quickstart for GitHub Actions -intro: 'Add a {% data variables.product.prodname_actions %} workflow to an existing repository in 5 minutes or less.' +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates @@ -19,57 +19,58 @@ topics: ### Einführung -You only need an existing {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that lints multiple coding languages using the [{% data variables.product.prodname_dotcom %} Super-Linter action](https://github.com/github/super-linter). The workflow uses Super-Linter to validate your source code every time a new commit is pushed to your repository. +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. + +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. ### Creating your first workflow -1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `superlinter.yml`. Weitere Informationen finden Sie unter „[Neue Dateien erstellen](/github/managing-files-in-a-repository/creating-new-files)“. -2. Copy the following YAML contents into the `superlinter.yml` file. **Note:** If your default branch is not `main`, update the value of `DEFAULT_BRANCH` to match your repository's default branch name. +1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `github-actions-demo.yml`. Weitere Informationen finden Sie unter „[Neue Dateien erstellen](/github/managing-files-in-a-repository/creating-new-files)“. +2. Copy the following YAML contents into the `github-actions-demo.yml` file: {% raw %} ```yaml{:copy} - name: Super-Linter - - # Run this workflow every time a new commit pushed to your repository - on: push - + name: GitHub Actions Demo + 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 + Explore-GitHub-Actions: runs-on: ubuntu-latest - steps: - # Checks out a copy of your repository on the ubuntu-latest machine - - name: Checkout code + - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event." + - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!" + - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}." + - name: Check out repository code uses: actions/checkout@v2 + - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner." + - run: echo "🖥️ The workflow is now ready to test your code on the runner." + - name: List files in the repository + run: | + ls ${{ github.workspace }} + - run: echo "🍏 This job's status is ${{ job.status }}." - # 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. To run your workflow, scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. ![Commit workflow file](/assets/images/commit-workflow-file.png) +3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. ![Commit workflow file](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -Committing the workflow file in your repository triggers the `push` event and runs your workflow. +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. ### Viewing your workflow results {% 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" or currentVersion == "github-ae@latest" %} -1. Under **Jobs** or in the visualization graph, click the **Lint code base** job. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) -{% else %} -1. In the left sidebar, click the **Lint code base** job. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) -{% endif %} -{% data reusables.repositories.view-failed-job-results-superlinter %} +1. Klicke in der linken Seitenleiste auf den Workflow, den Du sehen willst. + + ![Workflow-Liste in der linken Seitenleiste](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +1. From the list of workflow runs, click the name of the run you want to see. + + ![Name der Workflow-Ausführung](/assets/images/help/repository/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. + + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. + + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) ### More workflow templates @@ -77,74 +78,12 @@ Committing the workflow file in your repository triggers the `push` event and ru ### Nächste Schritte: -The super-linter workflow you just added runs each time code is pushed to your repository to help you spot errors and inconsistencies in your code. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}: +The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}: -- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial -- "[Guides](/actions/guides)" for specific uses cases and examples -- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action +- Your repository can contain multiple workflows that trigger different jobs based on different events. +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. - +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial. +- "[Guides](/actions/guides)" for specific uses cases and examples. diff --git a/translations/de-DE/content/actions/reference/environment-variables.md b/translations/de-DE/content/actions/reference/environment-variables.md index 48ec226d16..9485f42775 100644 --- a/translations/de-DE/content/actions/reference/environment-variables.md +++ b/translations/de-DE/content/actions/reference/environment-variables.md @@ -22,6 +22,7 @@ versions: Um benutzerdefinierte Umgebungsvariablen festzulegen, musst Du die Variablen in der Workflow-Datei angeben. 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. Weitere Informationen finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“. +{% raw %} ```yaml jobs: weekday_job: @@ -30,13 +31,14 @@ jobs: DAY_OF_WEEK: Mon steps: - name: "Hello world when it's Monday" - if: env.DAY_OF_WEEK == 'Mon' + if: ${{ env.DAY_OF_WEEK == 'Mon' }} run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" env: FIRST_NAME: Mona middle_name: The Last_Name: Octocat ``` +{% endraw %} To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables. diff --git a/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md b/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md index ba80fd3121..bfe79b906f 100644 --- a/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/de-DE/content/actions/reference/usage-limits-billing-and-administration.md @@ -70,7 +70,7 @@ You can configure the artifact and log retention period for your repository, org Weitere Informationen findest Du unter: - [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your repository](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) -- [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) - [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your enterprise](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) {% endif %} @@ -80,7 +80,7 @@ Weitere Informationen findest Du unter: Weitere Informationen findest Du unter: - "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)" -- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} +- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" for {% data variables.product.prodname_ghe_cloud %}{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} diff --git a/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 09b5a1d061..73ce931d2e 100644 --- a/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/de-DE/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -21,7 +21,7 @@ After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_ma * Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization. * Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}. -For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, 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)." +For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ### Vorrausetzungen diff --git a/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index 8b0780e5f6..cd185408a1 100644 --- a/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/de-DE/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -28,7 +28,7 @@ The provisioning application on your IdP communicates with {% data variables.pro {% data reusables.scim.supported-idps %} -When you set up user provisioning with a supported IdP, you can also assign or unassign the application for {% data variables.product.product_name %} to groups of users. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. 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)." +When you set up user provisioning with a supported IdP, you can also assign or unassign the application for {% data variables.product.product_name %} to groups of users. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. Weitere Informationen findest Du unter „[Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ### Vorrausetzungen diff --git a/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index 6956d32d9f..93319dcfb6 100644 --- a/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/de-DE/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -13,7 +13,7 @@ By default, authorized users can access your enterprise from any IP address. Ent {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -Du kannst auch zugelassene IP-Adressen für eine einzelne Organisation konfigurieren. Weitere Informationen findest Du auf „[Zugelassene IP-Adressen für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +Du kannst auch zugelassene IP-Adressen für eine einzelne Organisation konfigurieren. Weitere Informationen findest Du auf „[Zugelassene IP-Adressen für Deine Organisation verwalten](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance. diff --git a/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md b/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md index ed893a4ac0..8927a7a0fb 100644 --- a/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md +++ b/translations/de-DE/content/admin/enterprise-support/about-github-enterprise-support.md @@ -6,6 +6,8 @@ redirect_from: versions: enterprise-server: '*' github-ae: '*' +topics: + - Unternehmen --- {% note %} @@ -16,32 +18,24 @@ versions: ### Informationen zum {% data variables.contact.enterprise_support %} -{% data variables.product.product_name %} includes {% data variables.contact.enterprise_support %} in English{% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %}. +{% data variables.product.product_name %} includes {% data variables.contact.enterprise_support %} in English{% if enterpriseServerVersions contains currentVersion %} and Japanese{% endif %}. {% if enterpriseServerVersions contains currentVersion %} You can contact {% data variables.contact.enterprise_support %} through {% data variables.contact.contact_enterprise_portal %} for help with: - Installation und Verwendung von {% data variables.product.product_name %} - Identifizierung und Überprüfung der Ursachen von vermuteten Fehlern -{% endif %} -In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.premium_support %}{% else %}support for {% data variables.product.product_name %}{% endif %} offers: +In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} support for {% data variables.product.product_name %} offers: - Schriftlicher Support rund um die Uhr über unser Supportportal - Telefonischer Support rund um die Uhr - - A{% if currentVersion == "github-ae@latest" %}n enhanced{% endif %} Service Level Agreement (SLA) {% if enterpriseServerVersions contains currentVersion %}with guaranteed initial response times{% endif %} -{% if currentVersion == "github-ae@latest" %} - - An assigned Technical Service Account Manager - - Quarterly support reviews - - Managed Admin services -{% else if enterpriseServerVersions contains currentVersion %} + - Service Level Agreement (SLA) mit garantierten Antwortzeiten - Technical account managers - Zugriff auf Premium-Inhalte - Geplante Zustandsprüfungen - Managed Admin hours {% endif %} -{% data reusables.support.government-response-times-may-vary %} - {% if enterpriseServerVersions contains currentVersion %} Weitere Informationen finden Sie unter „[Informationen zum {{ site.data.variables.contact.premium_support }} für {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)“. {% endif %} @@ -52,34 +46,28 @@ Weitere Informationen finden Sie unter „[Informationen zum {{ site.data.variab You can contact {% data variables.contact.enterprise_support %} through {% if enterpriseServerVersions contains currentVersion %}{% data variables.contact.contact_enterprise_portal %}{% elsif currentVersion == "github-ae@latest" %} the {% data variables.contact.ae_azure_portal %}{% endif %} to report issues in writing. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." +{% if enterpriseServerVersions contains currentVersion %} ### Geschäftszeiten -{% if enterpriseServerVersions contains currentVersion %} #### Support auf Englisch -{% endif %} -{% if enterpriseServerVersions contains currentVersion %} Bei nicht dringenden herkömmlichen Probleme bieten wir 24 Stunden am Tag, 5 Tage die Woche, außer an Wochenenden und nationalen Feiertagen in den USA, Support in englischer Sprache. holidays. Die Antwortdauer beträgt in der Regel 24 Stunden. -For urgent issues, we {% else %}We{% endif %} are available 24 hours per day, 7 days per week, even during national U.S. holidays. +Für dringende Probleme stehen wir 24 Stunden am Tag, 7 Tage die Woche zur Verfügung, sogar während der nationalen US-Feiertage. holidays. -{% data reusables.support.government-response-times-may-vary %} - -{% if enterpriseServerVersions contains currentVersion %} #### Support auf Japanisch Bei nicht dringenden Problemen ist der Support auf Japanisch von Montag bis Freitag von 9:00 bis 17:00 Uhr JST verfügbar, außer an nationalen Feiertagen in Japan. For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays. -For a complete list of U.S. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."{% endif %} +For a complete list of U.S. Eine vollständige Liste der vom {% data variables.contact.enterprise_support %} wahrgenommenen nationalen Feiertage in den USA und Japan finden Sie unter „[Feiertagsübersicht](#holiday-schedules)“. -{% if enterpriseServerVersions contains currentVersion %} ### Feiertagsübersicht -For urgent issues, we can help you in English 24 hours per day, 7 days per week, including on U.S. {% if enterpriseServerVersions contains currentVersion %}and Japanese{% endif %} holidays. +For urgent issues, we can help you in English 24 hours per day, 7 days per week, including on U.S. and Japanese holidays. #### Feiertage in den USA -{% data variables.contact.enterprise_support %} beobachtet diese Feiertage in den USA. holidays{% if enterpriseServerVersions contains currentVersion %}, although our global support team is available to answer urgent tickets{% endif %}. +{% data variables.contact.enterprise_support %} beobachtet diese Feiertage in den USA. dessen ungeachtet steht unser Support-Team zur Verfügung, um dringende Tickets zu beantworten. | U.S. Weihnachtsfeiertag | Date observed | | ----------------------- | ------------------------------ | @@ -123,7 +111,6 @@ Wenn Du den {% data variables.contact.enterprise_support %} kontaktierst, kannst ### Weiterführende Informationen {% if enterpriseServerVersions contains currentVersion %} -- [Häufig gestellte Fragen zu {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) - Section 10 on Support in the "[{% data variables.product.prodname_ghe_server %} License Agreement](https://enterprise.github.com/license)"{% endif %} - "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)"{% if enterpriseServerVersions contains currentVersion %} - "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)"{% endif %} diff --git a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md index b00f68e4f8..454fd519b3 100644 --- a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md +++ b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md @@ -37,7 +37,7 @@ Zusätzlich zu den Vorteilen des {% data variables.contact.enterprise_support %} {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %}-Support erreichen](/enterprise/admin/guides/enterprise-support/reaching-github-support)“. +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md index 3759891ac5..1b51de4a38 100644 --- a/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md +++ b/translations/de-DE/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md @@ -35,7 +35,7 @@ Zusätzlich zu den Vorteilen des {% data variables.contact.enterprise_support %} {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %}-Support erreichen](/enterprise/admin/guides/enterprise-support/reaching-github-support)“. +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/de-DE/content/admin/github-actions/index.md b/translations/de-DE/content/admin/github-actions/index.md index 13e7ebdae1..58efda8601 100644 --- a/translations/de-DE/content/admin/github-actions/index.md +++ b/translations/de-DE/content/admin/github-actions/index.md @@ -32,6 +32,7 @@ topics: {% 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 /using-the-latest-version-of-the-official-bundled-actions %} {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} {% topic_link_in_list /advanced-configuration-and-troubleshooting %} 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 e669f24960..7d0ee61af1 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 @@ -28,8 +28,21 @@ The `actions-sync` tool can only download actions from {% data variables.product ### Vorrausetzungen -* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." * You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. Weitere Informationen finden Sie unter "[Erstellen eines persönlichen Zugriffstokens](/github/authenticating-to-github/creating-a-personal-access-token)." +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. + + {% note %} + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + + {% endnote %} + + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." + + ```shell + ghe-org-admin-promote -u USERNAME -o actions + ``` ### Example: Using the `actions-sync` tool diff --git a/translations/de-DE/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/de-DE/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md new file mode 100644 index 0000000000..70148c1250 --- /dev/null +++ b/translations/de-DE/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md @@ -0,0 +1,45 @@ +--- +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '>=2.22' +topics: + - Unternehmen +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server). + +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}. + +Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}: + +- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}. +- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions. + +These options are described in more detail in the following sections. + +### Using actions-sync to update a bundled action + +To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." + +### Using actions from {% data variables.product.prodname_dotcom_the_website %} + +{% data reusables.github-actions.actions-github-connect-requirement %} + +Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file. + +### Using the latest version by removing the specific action's tag + +{% data reusables.github-actions.actions-github-connect-requirement %} + +If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)." + +For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}: + +1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository. +1. Create a workflow that uses `actions/setup-python` with the `v2` tag. + +When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}. 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 69bc8153d2..813bfe9c95 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 @@ -1,6 +1,6 @@ --- title: GitHub Enterprise Server auf Hyper-V installieren -intro: 'Um {% data variables.product.prodname_ghe_server %} auf Hyper-V zu installieren, müssen Sie es auf einem Computer bereitstellen, auf dem Windows Server 2008 bis Windows Server 2016 ausgeführt wird.' +intro: 'Um {% data variables.product.prodname_ghe_server %} auf Hyper-V zu installieren, müssen Sie es auf einem Computer bereitstellen, auf dem Windows Server 2008 bis Windows Server 2019 ausgeführt wird.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v @@ -13,7 +13,7 @@ topics: ### Vorrausetzungen - {% data reusables.enterprise_installation.software-license %} -- Sie müssen über Windows Server 2008 bis Windows Server 2016 mit Hyper-V-Unterstützung verfügen. +- Sie müssen über Windows Server 2008 bis Windows Server 2019 mit Hyper-V-Unterstützung verfügen. - Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). Zur Ersteinrichtung sollten Sie jedoch die Windows PowerShell-Befehlszeilenshell verwenden. Im Folgenden finden Sie Beispiele zur Verwendung der PowerShell. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)." ### Grundlegendes zur Hardware diff --git a/translations/de-DE/content/admin/overview/github-ae-release-notes.md b/translations/de-DE/content/admin/overview/github-ae-release-notes.md index 4feecafcc8..3c8bde0e58 100644 --- a/translations/de-DE/content/admin/overview/github-ae-release-notes.md +++ b/translations/de-DE/content/admin/overview/github-ae-release-notes.md @@ -29,7 +29,7 @@ During this beta, {% data variables.product.prodname_advanced_security %} featur #### Manage teams from your identity provider (IdP) -Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group. 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)." +Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group. Weitere Informationen findest Du unter „[Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." #### IP allow lists beta @@ -37,7 +37,7 @@ Enterprise and organization owners can now use IP allow lists to restrict traffi This functionality is provided in addition to the ability to request network security group changes that filter traffic to the entirety of the {% data variables.product.product_name %} tenant. -For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." #### Pull request auto-merge @@ -47,8 +47,8 @@ With auto-merge, pull requests can be set to merge automatically when all merge #### Developer changes -- [Organization owners can now disable publication](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites. -- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). +- [Organization owners can now disable publication](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites. +- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - When writing an issue or pull request, the list syntax for bullets, numbers, and tasks will now be autocompleted after you press `return` or `enter`. - You can now delete a directory in a repository from the repository page. When navigating to a directory, a new kebab button next to the "Add file" button gives the option to delete the directory. - It’s now easier and faster to [reference issues or pull requests](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), with search across multiple words after the "#". @@ -65,7 +65,7 @@ With auto-merge, pull requests can be set to merge automatically when all merge ##### Default branch renaming -Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[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)." +Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." Existing repositories are unaffected by these settings, and their default branch name will not be changed. diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md index aeda678f08..3bd086943e 100644 --- a/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md +++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md @@ -4,7 +4,7 @@ intro: 'Enterprise owners can enforce policies to manage {% data variables.produ product: '{% data reusables.gated-features.ghas %}' versions: enterprise-server: '>=3.1' - github-ae: '*' + github-ae: 'nächste' --- ### Informationen zu {% data variables.product.prodname_GH_advanced_security %} 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 0ae0c76c59..b78debd924 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 @@ -66,17 +66,16 @@ Mandatory messages have a variety of uses. - 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 %} -{% note %} - -**Note:** After you configure a mandatory message for {% data variables.product.product_location %}, you cannot change or remove the message. - -{% endnote %} - - 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)." +{% note %} + +**Note:** If you change the mandatory message for {% data variables.product.product_location %}, users who have already acknowledged the message will not see the new message. + +{% endnote %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} diff --git a/translations/de-DE/content/code-security/secret-security/about-secret-scanning.md b/translations/de-DE/content/code-security/secret-security/about-secret-scanning.md index e1564097d5..99fb30a73d 100644 --- a/translations/de-DE/content/code-security/secret-security/about-secret-scanning.md +++ b/translations/de-DE/content/code-security/secret-security/about-secret-scanning.md @@ -45,7 +45,7 @@ Wenn {% data variables.product.prodname_secret_scanning %} einen Satz von Anmeld {% 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)." +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](/organizations/keeping-your-organization-secure/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. diff --git a/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md index 3e4b89aa24..410e0a7d95 100644 --- a/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md +++ b/translations/de-DE/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md @@ -70,4 +70,4 @@ Du kannst auch einzelne Warnungen von {% data variables.product.prodname_secret_ ### 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)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md b/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md index 88a106c919..7187060365 100644 --- a/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md +++ b/translations/de-DE/content/code-security/secure-coding/configuring-code-scanning.md @@ -11,7 +11,7 @@ versions: enterprise-server: '>=3.0' github-ae: '*' topics: - - security + - sicherheit --- {% data reusables.code-scanning.beta %} @@ -19,7 +19,7 @@ topics: ### About {% data variables.product.prodname_code_scanning %} configuration -You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." +You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}. @@ -27,36 +27,44 @@ Before you can configure {% data variables.product.prodname_code_scanning %} for {% data reusables.code-scanning.edit-workflow %} -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. +You can write a configuration file for {% data variables.product.prodname_code_scanning %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. -### Editing a {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} saves workflow files in the `.github/workflows` directory of your repository. You can find a workflow you have added by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. Navigiere in Deinem Repository zu der Workflow-Datei, die Du bearbeiten möchtest. +1. Um den Workflow-Editor zu öffnen, klickst Du in der oberen rechten Ecke der Dateiansicht auf {% octicon "pencil" aria-label="The edit icon" %}. ![Schaltfläche zum Editieren der Workflow-Datei](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. ![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." ### Configuring frequency -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +You can scan code on a schedule or when specific events occur in a repository. -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +Scanning code on every push to the repository, and every time a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. #### Scanning on push -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +If you use the default workflow, {% data variables.product.prodname_code_scanning %} will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)“. + +If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." + +{% note %} + +**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below. + +{% endnote %} #### Scanning pull requests -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)“. For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." + #### Avoiding unnecessary scans of pull requests You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. @@ -74,7 +82,7 @@ on: {% note %} -**Notes** +**Hinweise:** * `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." * For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. @@ -85,7 +93,7 @@ For more information about using `on:pull_request:paths-ignore` and `on:pull_req #### Scanning on a schedule -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +The default {% data variables.product.prodname_code_scanning %} workflow uses the `pull_request` event to trigger a code scan on the `HEAD` commit of a pull request. To adjust this schedule, edit the `cron` value in the workflow. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)“. {% note %} @@ -93,7 +101,7 @@ If you use the default {% data variables.product.prodname_codeql_workflow %}, th {% endnote %} -#### Example +#### Beispiel The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. @@ -114,7 +122,7 @@ This workflow scans: ### Specifying an operating system -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} +If your code requires a specific operating system to compile, you can configure this in your workflow. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} @@ -127,7 +135,7 @@ jobs: {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% data variables.product.prodname_code_scanning_capc %} supports the latest versions of macOS, Ubuntu, and Windows. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." {% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} @@ -139,7 +147,7 @@ jobs: The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." -{% data reusables.code-scanning.specify-language-to-analyze %} +{% data variables.product.prodname_code_scanning_capc %} automatically detects and scans code written in the supported languages. If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. @@ -208,7 +216,7 @@ jobs: {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. +To add one or more query suites, add a `queries` section to your configuration file. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. {% raw %} ``` yaml @@ -220,11 +228,11 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu ``` {% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +You can also run additional query suites by specifying these in a configuration file. Query suites are collections of queries, usually grouped by purpose or language. {% data reusables.code-scanning.codeql-query-suites %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +You can run additional queries by specifying these in a configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For examples of configuration files, see "[Example configuration files](#example-configuration-files)." In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. @@ -238,7 +246,7 @@ In the following example, the `+` symbol ensures that the specified additional q ``` {% endraw %} -### Using a custom configuration file +### Using a third-party code scanning tool As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. @@ -281,7 +289,7 @@ For more information about additional queries, see "[Running additional queries] #### Disabling the default queries -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +If you only want to run custom queries, you can disable the default security queries by adding `disable-default-queries: true` to your configuration file. #### Specifying directories to scan @@ -299,14 +307,14 @@ paths-ignore: **Note**: -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. Weitere Informationen findest Du unter „[Workflow-Syntax für {% 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. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. {% endnote %} For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow file. #### Example configuration files @@ -320,4 +328,4 @@ You can quickly analyze small portions of a monorepo when you modify code in spe ### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)." +You can display code analysis from a third-party tool in {% data variables.product.prodname_dotcom %} by adding the `upload-sarif` action to your workflow. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)." diff --git a/translations/de-DE/content/code-security/secure-coding/index.md b/translations/de-DE/content/code-security/secure-coding/index.md index f52bae730b..40f3d97034 100644 --- a/translations/de-DE/content/code-security/secure-coding/index.md +++ b/translations/de-DE/content/code-security/secure-coding/index.md @@ -1,7 +1,7 @@ --- title: Finding security vulnerabilities and errors in your code shortTitle: Secure coding -intro: 'Keep your code secure by using secret scanning to identify and fix potential security vulnerabilities and other errors in your code.' +intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code diff --git a/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md index b4894e1970..2505939476 100644 --- a/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/de-DE/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md @@ -45,7 +45,14 @@ You need write permission to view a summary of all the alerts for a repository o {% 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) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} +1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Liste der Warnungen von {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) @@ -57,7 +64,11 @@ If you have write permission for a repository, you can view fixed alerts by view 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +{% else %} +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} @@ -110,11 +121,19 @@ To dismiss or delete alerts: 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) +{% else %} + ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) +{% endif %} 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Liste der Warnungen von {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) diff --git a/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md index 0567b08941..418588a9fc 100644 --- a/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md +++ b/translations/de-DE/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md @@ -32,7 +32,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -72,7 +72,11 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} {% endnote %} @@ -98,7 +102,11 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% else %} + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) +{% endif %} The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. diff --git a/translations/de-DE/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/editing-a-security-advisory.md index a1993b7835..00cb534408 100644 --- a/translations/de-DE/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/de-DE/content/code-security/security-advisories/editing-a-security-advisory.md @@ -17,6 +17,8 @@ You can credit people who helped discover, report, or fix a security vulnerabili If someone accepts credit, the person's username appears in the "Credits" section of the security advisory. Anyone with read access to the repository can see the advisory and the people who accepted credit for it. +If you believe you should be credited for a security advisory, please contact the person who created the advisory and ask them to edit the advisory to include your credit. Only the creator of the advisory can credit you, so please don't contact GitHub Support about credits for security advisories. + ### Einen Sicherheitshinweis bearbeiten {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/de-DE/content/code-security/security-overview/exploring-security-alerts.md b/translations/de-DE/content/code-security/security-overview/exploring-security-alerts.md index 8a6392e71f..ec09e0a220 100644 --- a/translations/de-DE/content/code-security/security-overview/exploring-security-alerts.md +++ b/translations/de-DE/content/code-security/security-overview/exploring-security-alerts.md @@ -11,7 +11,7 @@ versions: ### About the security overview -You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. Weitere Informationen findest Du unter „[Den Zugriff eines Teams auf ein Repository einer Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository).“ +You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. Weitere Informationen findest Du unter „[Den Zugriff eines Teams auf ein Repository einer Organisation verwalten](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository).“ The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)." diff --git a/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md index eb1e75b7fd..64074bc6a5 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md +++ b/translations/de-DE/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md @@ -49,9 +49,9 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} diff --git a/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md index fd43a744b6..805f985ce8 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md +++ b/translations/de-DE/content/code-security/supply-chain-security/about-dependabot-version-updates.md @@ -12,8 +12,6 @@ topics: - repositorys --- -{% data reusables.dependabot.beta-note %} - ### Informationen zum {% data variables.product.prodname_dependabot_version_updates %} {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. diff --git a/translations/de-DE/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/de-DE/content/code-security/supply-chain-security/about-the-dependency-graph.md index 3f516de9cb..477dc90223 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/about-the-dependency-graph.md +++ b/translations/de-DE/content/code-security/supply-chain-security/about-the-dependency-graph.md @@ -1,5 +1,5 @@ --- -title: About the dependency graph +title: Informationen zum Abhängigkeitsdiagramm intro: 'You can use the dependency graph to identify all your project''s dependencies. The dependency graph supports a range of popular package ecosystems.' redirect_from: - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph @@ -7,8 +7,9 @@ versions: free-pro-team: '*' enterprise-server: '>=3.0' topics: - - repositories + - repositorys --- + ### Dependency graph availability @@ -17,7 +18,7 @@ The dependency graph is available for every{% if currentVersion == "free-pro-tea {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### Informationen zum Abhängigkeitsdiagramm The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: @@ -49,13 +50,13 @@ For public repositories, only public repositories that depend on it or on packag You can use the dependency graph to: - Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} +- View a summary of the dependencies used in your organization's repositories in a single dashboard. Weitere Informationen findest Du unter „[Einblicke für Deine Organisation anzeigen ](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)“.{% endif %} - View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} - See information about vulnerable dependencies in pull requests. 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 %} ### Enabling the dependency graph -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} @@ -65,19 +66,19 @@ You can use the dependency graph to: When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. -### Supported package ecosystems +### Unterstützte Paket-Ökosysteme The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| Paketmanager | Sprachen | Empfohlene Formate | All supported formats | +| ------------ | ------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET-Sprachen (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`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} @@ -85,10 +86,10 @@ The recommended formats explicitly define which versions are used for all direct {% endnote %} -### Further reading +### Weiterführende Informationen - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- „[Einblicke für Ihre Organisation anzeigen ](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)“ +- „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“ - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md index 6266102867..fc295ea906 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md +++ b/translations/de-DE/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md @@ -11,8 +11,6 @@ topics: - repositorys --- -{% data reusables.dependabot.beta-note %} - ### About the *dependabot.yml* file The {% data variables.product.prodname_dependabot %} configuration file, *dependabot.yml*, uses YAML syntax. Wenn Sie bislang noch nicht mit YAML gearbeitet haben, lesen Sie den Artikel „[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)“. @@ -323,7 +321,7 @@ updates: {% note %} -**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. 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-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." +**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." {% endnote %} diff --git a/translations/de-DE/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/de-DE/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md index 0c7c0333e9..5e4fe8b5c7 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md +++ b/translations/de-DE/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md @@ -49,7 +49,7 @@ If security updates are not enabled for your repository and you don't know why, 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)." +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](/organizations/keeping-your-organization-secure/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)." diff --git a/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md index 012d0d120b..c08fffdf9f 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/de-DE/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md @@ -16,7 +16,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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" %} diff --git a/translations/de-DE/content/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/de-DE/content/code-security/supply-chain-security/customizing-dependency-updates.md index 50e2b27a4e..048706b424 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/customizing-dependency-updates.md +++ b/translations/de-DE/content/code-security/supply-chain-security/customizing-dependency-updates.md @@ -10,8 +10,6 @@ topics: - repositorys --- -{% data reusables.dependabot.beta-note %} - ### About customizing dependency updates After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could: diff --git a/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md index 4022abc0e2..5747720dc5 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md +++ b/translations/de-DE/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md @@ -12,8 +12,6 @@ topics: -{% data reusables.dependabot.beta-note-no-link %} - ### About version updates for dependencies You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a *dependabot.yml* configuration file in to your repository's `.github` directory. {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. For each package manager's dependencies that you want to update, you must specify the location of the package manifest files and how often to check for updates to the dependencies listed in those files. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -117,7 +115,7 @@ updates: interval: "daily" # Overwrite any ignores created using `@dependabot ignore` commands ignore: - # Ignore updates to packages that start 'aws' + # Ignore updates to packages that start with 'aws' # Wildcards match zero or more arbitrary characters - dependency-name: "aws*" # Ignore some updates to the 'express' package diff --git a/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md index e80a4c37f0..322ca5c31f 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md +++ b/translations/de-DE/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md @@ -74,7 +74,7 @@ For public repositories, the dependents view shows how the repository is used by Repository administrators can enable or disable the dependency graph for private repositories. -You can also enable or disable the dependency graph 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)." +You can also enable or disable the dependency graph 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -114,7 +114,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ### Weiterführende Informationen - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- „[Einblicke für Ihre Organisation anzeigen ](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)“ +- „[Einblicke für Ihre Organisation anzeigen ](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)“ - „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“ - „[Grundlegendes zur Verwendung und zum Schutz Ihrer Daten durch {% data variables.product.product_name %}](/github/understanding-how-github-uses-and-protects-your-data)“ {% endif %} diff --git a/translations/de-DE/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/de-DE/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md index 38dcf4287a..0068fc3e68 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/de-DE/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md @@ -10,8 +10,6 @@ topics: - repositorys --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot_version_updates %} for actions Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/de-DE/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/de-DE/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md index 570a072a00..48d9d19c50 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md +++ b/translations/de-DE/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md @@ -9,8 +9,6 @@ topics: - repositorys --- -{% data reusables.dependabot.beta-note %} - ### Viewing dependencies monitored by {% data variables.product.prodname_dependabot %} After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." diff --git a/translations/de-DE/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/de-DE/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md index a60c178930..841f4ec49a 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md +++ b/translations/de-DE/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md @@ -9,8 +9,6 @@ topics: - repositorys --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot %} pull requests {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md index 35e2870fa0..e7a7f70b67 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md +++ b/translations/de-DE/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md @@ -11,8 +11,6 @@ topics: - sicherheit --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot %} errors {% data reusables.dependabot.pull-request-introduction %} 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 48202252b2..98a7f8f385 100644 --- a/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/authorizing-oauth-apps.md @@ -86,18 +86,18 @@ Exchange this `code` for an access token: By default, the response takes the following form: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer You can also receive the content in different formats depending on the Accept header: Accept: application/json - {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} + {"access_token":"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} Accept: application/xml bearer repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} #### 3. Use the access token to access the API @@ -207,7 +207,7 @@ Once the user has authorized, the app will receive an access token that can be u ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "user" } @@ -304,3 +304,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} * "[Device flow errors](#errors-for-the-device-flow)" {% endif %} + +### Weiterführende Informationen + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md index 5b73e28e11..769b4e6668 100644 --- a/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/de-DE/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -54,16 +54,18 @@ The person creating the app will be redirected to a GitHub page with an input fi ##### GitHub App Manifest parameters - | Name | Typ | Beschreibung | - | --------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `string` | The name of the GitHub App. | - | `url` | `string` | **Required.** The homepage of your GitHub App. | - | `hook_attributes` | `Objekt` | The configuration of the GitHub App's webhook. | - | `redirect_url` | `string` | The full URL to redirect to after the person installs the GitHub App. | - | `Beschreibung` | `string` | A description of the GitHub App. | - | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | - | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | - | `default_permissions` | `Objekt` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | + | Name | Typ | Beschreibung | + | --------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `string` | The name of the GitHub App. | + | `url` | `string` | **Required.** The homepage of your GitHub App. | + | `hook_attributes` | `Objekt` | The configuration of the GitHub App's webhook. | + | `redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %} + | `callback_url` | `string` | A full URL to redirect to after someone authorizes an installation.{% endif %} + | `Beschreibung` | `string` | A description of the GitHub App. | + | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | + | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | + | `default_permissions` | `Objekt` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | The `hook_attributes` object has the following key: @@ -96,7 +98,10 @@ This example uses a form on a web page with a button that triggers the `POST` re "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -111,10 +116,11 @@ This example uses a form on a web page with a button that triggers the `POST` re }) ``` + This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app. ```html -
+ Create a GitHub App Manifest:
@@ -127,7 +133,10 @@ This example uses a form on a web page with a button that triggers the `POST` re "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -147,11 +156,11 @@ This example uses a form on a web page with a button that triggers the `POST` re When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. Ein Beispiel: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. Ein Beispiel: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 #### 3. You exchange the temporary code to retrieve the app configuration diff --git a/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md index ed4416e7ec..4c1e71adeb 100644 --- a/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/de-DE/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -22,9 +22,15 @@ The person creating the app can edit the preselected values from the {% data var The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: - ``` - {% 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 - ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} +``` +{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite +``` +{% else %} +``` +{% 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 +``` +{% endif %} The complete list of available query parameters, permissions, and events is listed in the sections below. @@ -34,8 +40,9 @@ The complete list of available query parameters, permissions, and events is list | -------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. | | `Beschreibung` | `string` | A description of the {% data variables.product.prodname_github_app %}. | - | `url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage. | - | `callback_url` | `string` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. | + | `url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} + | `callback_url` | `string` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} | `request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. | | `setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation. | | `setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed. | 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 e11159fbf0..d8f2abd4ae 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 @@ -845,7 +845,7 @@ Here are a few common problems and some suggested solutions. If you run into any **A:** If you see the following error, you haven't deleted the checkout of the repository in one or both of the `initiate_check_run` or `take_requested_action` methods: ```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.: + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: ``` Compare your code to the `server.rb` file to ensure you have the same code in your `initiate_check_run` and `take_requested_action` methods. diff --git a/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 2686233c9f..0ec19ba2ea 100644 --- a/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/de-DE/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -94,9 +94,9 @@ By default, the response takes the following form. The response parameters `expi ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -106,7 +106,7 @@ By default, the response takes the following form. The response parameters `expi By default, the response takes the following form: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer {% endif %} @@ -934,3 +934,11 @@ While most of your API interaction should occur using your server-to-server inst * [Get a workflow](/rest/reference/actions#get-a-workflow) * [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Weiterführende Informationen + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md index 713f2bf54e..70796bab6d 100644 --- a/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,9 +42,9 @@ This callback request will send you a new access token and a new refresh token. ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" @@ -73,3 +73,11 @@ If you want your app to use non-expiring user-to-server access tokens, you can d Existing {% data variables.product.prodname_github_app %}s using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app. Enabling expiring user tokens for existing {% data variables.product.prodname_github_app %}s requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Weiterführende Informationen + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md b/translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md index 4fe52d1acf..2f7f2287b8 100644 --- a/translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md +++ b/translations/de-DE/content/developers/github-marketplace/about-marketplace-badges.md @@ -13,7 +13,7 @@ Certain apps on the {% data variables.product.prodname_marketplace %} have the { - Verified ownership of their domain and has a verified badge on their profile - Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization -- Required two-factor authentication for their organization. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)“. +- Required two-factor authentication for their organization. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)“. ![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png) diff --git a/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md index 357a6a3216..7544beaca4 100644 --- a/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md +++ b/translations/de-DE/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -22,8 +22,8 @@ To offer paid plans for your app, the app must be owned by an organization and y 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) 1. Under "Publisher Verification", complete the information in the checklist: - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. - - Ensure that Two-factor authentication is enabled for your organization. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)“. - - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + - Ensure that Two-factor authentication is enabled for your organization. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)“. + - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) diff --git a/translations/de-DE/content/developers/overview/managing-deploy-keys.md b/translations/de-DE/content/developers/overview/managing-deploy-keys.md index 90c2f117c6..06765b5f01 100644 --- a/translations/de-DE/content/developers/overview/managing-deploy-keys.md +++ b/translations/de-DE/content/developers/overview/managing-deploy-keys.md @@ -112,6 +112,36 @@ You can then use the hostname's alias to interact with the repository using SSH, $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` +### Server-to-server tokens + +If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. + +Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps). + +##### Pros + +- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API). +- Dedicated rate limits that grow with your organization. +- Decoupled from GitHub user identities, so they do not consume any licensed seats. +- Never granted a password, so cannot be directly signed in to. + +##### Cons + +- Additional setup is needed to create the GitHub App. +- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code. + +##### Setup + +1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private. +1. Determine the permissions your GitHub App requires, such as read-only access to repository contents. +1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app). +1. Note your GitHub App `id`. +1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key). +1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization. +1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). +1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). +1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client. + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/de-DE/content/developers/overview/secret-scanning.md b/translations/de-DE/content/developers/overview/secret-scanning.md index 2aa723bbf1..64371e9b21 100644 --- a/translations/de-DE/content/developers/overview/secret-scanning.md +++ b/translations/de-DE/content/developers/overview/secret-scanning.md @@ -17,12 +17,6 @@ When a match of your secret format is found in a public repository, a payload is When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. Weitere Informationen findest Du unter „[Warnungen von {% data variables.product.prodname_secret_scanning %} verwalten](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -{% note %} - -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. - -{% endnote %} - This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. ### The {% data variables.product.prodname_secret_scanning %} process diff --git a/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md b/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md index 80431ba77e..2e3adc3a94 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/de-DE/content/developers/webhooks-and-events/github-event-types.md @@ -183,6 +183,20 @@ This event returns an empty `payload` object. {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} +### PullRequestReviewEvent + +{% data reusables.webhooks.pull_request_review_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Event `payload` object + +| Schlüssel | Typ | Beschreibung | +| -------------- | -------- | ----------------------------------------------------- | +| `action` | `string` | die Aktion, die durchgeführt wurde. Can be `created`. | +| `pull_request` | `Objekt` | The pull request the review pertains to. | +| `Review` | `Objekt` | The review that was affected. | + ### PullRequestReviewCommentEvent {% data reusables.webhooks.pull_request_review_comment_short_desc %} @@ -200,6 +214,8 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} +#### Event `payload` object + | Schlüssel | Typ | Beschreibung | | -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `push_id` | `integer` | Unique identifier for the push. | diff --git a/translations/de-DE/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/de-DE/content/developers/webhooks-and-events/securing-your-webhooks.md index 0242269c64..0da0423b7d 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/securing-your-webhooks.md +++ b/translations/de-DE/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -93,4 +93,4 @@ Your language and server implementations may differ from this example code. Howe * Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 13f655ae70..6d7a6eca86 100644 --- a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -19,7 +19,7 @@ With {% data variables.product.prodname_discussions %}, the community for your p You don't need to close a discussion like you close an issue or a pull request. -If a repository administrator or project maintainer enables discussions for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. Weitere Informationen findest Du unter„[Berechtigungsebenen für die Repositorys einer Organisation](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization).“ +If a repository administrator or project maintainer enables discussions for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. Weitere Informationen findest Du unter„[Berechtigungsebenen für die Repositorys einer Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization).“ For more information about management of discussions for your repository, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." diff --git a/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md index 6893e85d5a..23b8778b25 100644 --- a/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -29,7 +29,7 @@ You can use {% data variables.product.prodname_discussions %} to discuss big pic Issues sind nützlich bei der Diskussion spezifischer Details eines Projekts, beispielsweise Fehlerberichte und geplante Verbesserungen. Weitere Informationen findest Du unter „[Informationen zu Issues](/articles/about-issues).“ Mit Pull Requests kannst Du Änderungsvorschläge direkt kommentieren. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/articles/about-pull-requests)“ und „[Pull Requests kommentieren](/articles/commenting-on-a-pull-request).“ -{% data reusables.organizations.team-discussions-purpose %} Weitere Informationen findest Du unter „[Informationen zu Teamdiskussionen](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions).“ +{% data reusables.organizations.team-discussions-purpose %} Weitere Informationen findest Du unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions).“ ### Following contributing guidelines diff --git a/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 1ed259dc09..e8ff04eb05 100644 --- a/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -21,7 +21,7 @@ The most helpful contributors for the past 30 days are highlighted on the {% dat People with triage permissions for a repository can help moderate a project's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." -For more information about repository permission levels and {% data variables.product.prodname_discussions %}, see "[Repository permissions levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +For more information about repository permission levels and {% data variables.product.prodname_discussions %}, see "[Repository permissions levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." ### Step 3: Change permissions levels for top contributors diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index 3fa042c0bb..3afabeec41 100644 --- a/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -12,7 +12,7 @@ versions: {% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." -Organization owners can choose the permissions required to create a discussion for repositories owned by the organization. For more information, see "[Managing discussion creation for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization)." +Organization owners can choose the permissions required to create a discussion for repositories owned by the organization. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)." As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating a code of conduct or contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md index 5712d78d81..2f37e5084c 100644 --- a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -16,3 +16,7 @@ Professoren, Lehrer und Mentoren können die Onlineschulungen von Campus Advisor **Hinweis:** Als Kursleiter kannst Du keine {% data variables.product.prodname_dotcom %}-Konten für Deine Studenten erstellen. Studenten müssen ihre eigenen {% data variables.product.prodname_dotcom %}-Konten erstellen. {% endnote %} + +Teachers can manage a course on software development with {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} allows you to distribute code, provide feedback, and manage coursework using {% data variables.product.product_name %}. For more information, see "[Manage coursework with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)." + +Wenn Sie Schüler, Student oder Lehrkraft sind und Ihre Einrichtung nicht mit {% data variables.product.prodname_dotcom %} als {% data variables.product.prodname_campus_program %}-Einrichtung kooperiert, können Sie trotzdem individuell Rabatte für die Nutzung von {% data variables.product.prodname_dotcom %} beantragen. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" or "[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/)." diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md index 7a9e68fc4d..84cbec299a 100644 --- a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -9,4 +9,6 @@ versions: free-pro-team: '*' --- -Erlernen von Fähigkeiten in den Bereichen öffentliches Reden, technisches Schreiben, Community Leadership und Softwareentwicklung als Campus Experts für {% data variables.product.prodname_dotcom %}. Weitere Informationen findest Du unter „[Campus Experts](https://education.github.com/students/experts).“ +Erlernen von Fähigkeiten in den Bereichen öffentliches Reden, technisches Schreiben, Community Leadership und Softwareentwicklung als Campus Experts für {% data variables.product.prodname_dotcom %}. + +Weitere Informationen zu Schulungsprogrammen für Schüler, Studenten und Lehrer findest Du unter „[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)“ und „[Campus Advisors](https://education.github.com/teachers/advisors).“ diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md new file mode 100644 index 0000000000..ecf8a04d44 --- /dev/null +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Campus Program +intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes: + +- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments +- Lehrerschulung zur Beherrschung von Git und {% data variables.product.prodname_dotcom %} mit unserem Campus Advisors-Programm, +- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners +- automatisierter Zugriff auf die Premiumfunktionen von {% data variables.product.prodname_education %}, wie z. B. das {% data variables.product.prodname_student_pack %}, + +Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join. + +Weitere Informationen findest Du auf der [offiziellen {% data variables.product.prodname_campus_program %}-Seite](https://education.github.com/schools). + +Wenn Sie Schüler, Student oder Lehrkraft sind und Ihre Einrichtung nicht mit {% data variables.product.prodname_dotcom %} als {% data variables.product.prodname_campus_program %}-Einrichtung kooperiert, können Sie trotzdem individuell Rabatte für die Nutzung von {% data variables.product.prodname_dotcom %} beantragen. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" or "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)." diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md index 8294d8dbaf..d81328f8c6 100644 --- a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -13,7 +13,7 @@ versions: ### Inhaltsverzeichnis {% topic_link_in_list /use-github-at-your-educational-institution %} - {% link_in_list /about-github-education %} + {% link_in_list /about-github-campus-program %} {% link_in_list /about-campus-experts %} {% link_in_list /about-campus-advisors %} {% topic_link_in_list /use-github-for-your-schoolwork %} diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index 7c00d5cd5b..0fcf43eedd 100644 --- a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -59,11 +59,11 @@ Weitere Informationen findest Du unter: ### Nicht berechtigter Studentenstatus Du bist nicht für ein {% data variables.product.prodname_student_pack %} berechtigt, falls: -- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. - You're pursuing a degree which will be terminated in the current academic session. - Du weniger als 13 Jahre alt bist. -Dein Kursleiter kann weiterhin einen {% data variables.product.prodname_education %}-Rabatt für die Nutzung in der Ausbildung beantragen. Wenn Du ein Student an einer Codierschule oder in einem Schülercamp bist, hast Du Anspruch auf ein {% data variables.product.prodname_student_pack %}, wenn Deine Bildungseinrichtung dem [{% data variables.product.prodname_dotcom %}-Campus-Programm](https://education.github.com/schools) beitritt. +Dein Kursleiter kann weiterhin einen {% data variables.product.prodname_education %}-Rabatt für die Nutzung in der Ausbildung beantragen. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). ### Weiterführende Informationen diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 7218dd3fbb..9bf6ed9e46 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -17,7 +17,7 @@ When a student accepts a group assignment, the student can create a new team or {% 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 %}. Weitere Informationen finden Sie unter „[Informationen zu Teams](/github/setting-up-and-managing-organizations-and-teams/about-teams)“. +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 %}. For more information, see "[About teams](/organizations/organizing-members-into-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)." 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 33f2037a23..120e6dbb13 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 @@ -20,7 +20,7 @@ redirect_from: After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}. -Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)" and "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom. @@ -34,7 +34,7 @@ When you first share the URL for an assignment with a student, the student must ### Vorrausetzungen -You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." diff --git a/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index 0b8dc0206b..53e4d318ae 100644 --- a/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -26,7 +26,7 @@ Alternativ kannst Du {% data variables.product.prodname_actions %} in Deinem Rep {% note %} -**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise account that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise account that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -47,7 +47,7 @@ You can disable all workflows for a repository or set a policy that configures w {% note %} -**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise account that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." +**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise account that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." {% endif %} diff --git a/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index 1bd205d091..6a331b6e58 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -11,7 +11,11 @@ topics: - repositorys --- -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)." +### About auto-merge + +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." + +### Managing auto-merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 4b46f77899..ffd1b63456 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 @@ -47,7 +47,10 @@ You can choose whether 6. Gib einen Titel und eine Beschreibung für Deinen Release ein. ![Beschreibung der Releases](/assets/images/help/releases/releases_description.png) 7. Um optional binäre Dateien wie kompilierte Programme in Deinen Release einzubinden, ziehe die Dateien mit Drag-and-Drop herüber oder wähle die Dateien manuell im Feld für Binärdateien. ![DMG mit dem Release bereitstellen](/assets/images/help/releases/releases_adding_binary.gif) 8. Um Benutzer darüber zu informieren, dass der Release nicht produktionsbereit und möglicherweise instabil ist, wähle **This is a pre-release** (Dies ist eine Vorabversion). ![Kontrollkästchen für die Markierung eines Release als Vorab-Release](/assets/images/help/releases/prerelease_checkbox.png) -9. Wenn Du Deinen Release publizieren möchtest, klicke auf **Publish release** (Release publizieren). Um den Release später zu bearbeiten, klicke auf **Save draft** (Entwurf speichern). ![Schaltfläche „Publish release“ (Release veröffentlichen) und Schaltfläche zum Speichern als Entwurf](/assets/images/help/releases/release_buttons.png) +{%- if currentVersion == "free-pro-team@latest" %} +1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +9. Wenn Du Deinen Release publizieren möchtest, klicke auf **Publish release** (Release publizieren). Um den Release später zu bearbeiten, klicke auf **Save draft** (Entwurf speichern). ![Schaltfläche „Publish release“ (Veröffentlichung veröffentlichen) und Schaltfläche zum Speichern als Entwurf](/assets/images/help/releases/release_buttons.png) Du kannst auch automatisch einem Release aus der Kommandozeile oder in einem Skript erstellen. For more information, see "[Releases](/rest/reference/repos/#create-a-release)." 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 4e39915f04..bf4f78219e 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 @@ -106,4 +106,4 @@ Organization owners and repository administrators can only grant access to view ### Weiterführende Informationen - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md index 3d0d952898..14ad325f1b 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -16,7 +16,7 @@ Für jedes Repository, das Du auf {% data variables.product.prodname_dotcom %} v Diese Übersicht kann Dir helfen, den Zugriff auf Dein Repository, Onboard- oder Off-Board-Auftragnehmer oder Mitarbeiter zu überwachen und effektiv auf Sicherheitsvorfälle zu reagieren. -Weitere Informationen zu Repository-Berechtigungsstufen findest Du unter „[Berechtigungsstufen für ein Benutzerkonto-Repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" und „[Repository Berechtigungsstufen für eine Organisation](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +Weitere Informationen zu Repository-Berechtigungsstufen findest Du unter „[Berechtigungsstufen für ein Benutzerkonto-Repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" und „[Repository Berechtigungsstufen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." ![Übersicht Zugriffsverwaltung](/assets/images/help/repository/manage-access-overview.png) @@ -53,4 +53,4 @@ Weitere Informationen zu Repository-Berechtigungsstufen findest Du unter „[Ber ### Weiterführende Informationen - „[Sichtbarkeit eines Repositorys festlegen](/github/administering-a-repository/setting-repository-visibility)“ -- „[Basis-Berechtigungen für eine Organisation festlegen](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" +- „[Basis-Berechtigungen für eine Organisation festlegen](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)" diff --git a/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index 5a243685e4..1c577c087b 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -13,7 +13,7 @@ topics: - repositorys --- -An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. Weitere Informationen findest Du unter „[Die Forking-Richtlinie für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)." +An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. Weitere Informationen findest Du unter „[Die Forking-Richtlinie für Deine Organisation verwalten](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)." {% data reusables.organizations.internal-repos-enterprise %} 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 index 04644c1d49..bc15f41e28 100644 --- 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 @@ -4,7 +4,7 @@ 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: '*' - enterprise-server: '>=3.1' + enterprise-server: '>=3.2' topics: - repositorys --- @@ -13,7 +13,9 @@ topics: 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. +When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. + +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. ### Renaming a branch diff --git a/translations/de-DE/content/github/administering-a-repository/renaming-a-repository.md b/translations/de-DE/content/github/administering-a-repository/renaming-a-repository.md index 006af29fca..51e3d084c0 100644 --- a/translations/de-DE/content/github/administering-a-repository/renaming-a-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/renaming-a-repository.md @@ -18,7 +18,7 @@ Wenn Du ein Repository umbenennst, werden mit Ausnahme von Projektwebsite-URLs a * Sterne * Follower -Weitere Informationen zu Projektwebsites findest Du unter „[Über {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Zusätzlich zur Umleitung des Web-Traffic werden auch alle `git clone`, `git fetch`, oder `git push` Operationen, welche auf den vorherigen Standort zielen, weiter funktionieren, wie wenn sie für den neuen Standort gemacht worden wären. Um jedoch Verwirrung zu vermeiden, empfehlen wir ausdrücklich, alle bestehenden lokalen Klone zu aktualisieren, sodass sie auf die neue Repository-URL verweisen. Du kannst dies mit dem Befehl `git remote` auf der Befehlszeile durchführen: @@ -30,7 +30,7 @@ For more information, see "[Managing remote repositories](/github/getting-starte {% if currentVersion == "free-pro-team@latest" %} -Wenn Du vorhast, ein Repository mit einer {% data variables.product.prodname_pages %}-Website umzubenennen, empfehlen wir Dir, eine benutzerdefinierte Domäne für Deine Website zu verwenden. Dadurch wird sichergestellt, dass die URL der Website nicht durch Umbenennung des Repository beeinträchtigt wird. Weitere Informationen findest Du unter „[Über benutzerdefinierte Domänen und {% data variables.product.prodname_pages %}-Websites](/github/working-with-github-pages/about-custom-domains-and-github-pages)." +Wenn Du vorhast, ein Repository mit einer {% data variables.product.prodname_pages %}-Website umzubenennen, empfehlen wir Dir, eine benutzerdefinierte Domäne für Deine Website zu verwenden. Dadurch wird sichergestellt, dass die URL der Website nicht durch Umbenennung des Repository beeinträchtigt wird. Weitere Informationen findest Du unter „[Über benutzerdefinierte Domänen und {% data variables.product.prodname_pages %}-Websites](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)." {% endif %} 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 820a726e2b..aa216bf785 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 @@ -16,7 +16,7 @@ topics: ### Über Änderungen der Repository-Sichtbarkeit -Organisationsinhaber können die Möglichkeit, die Sichtbarkeit des Repositorys zu ändern, auf Organisationsinhaber einschränken. Weitere Informationen findest Du unter „[Einschränken von Änderungen der Repository-Sichtbarkeit in Deiner Organisation](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)." +Organisationsinhaber können die Möglichkeit, die Sichtbarkeit des Repositorys zu ändern, auf Organisationsinhaber einschränken. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." We recommend reviewing the following caveats before you change the visibility of a repository. diff --git a/translations/de-DE/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/de-DE/content/github/authenticating-to-github/about-authentication-to-github.md index 1e6a789976..9708a70bb2 100644 --- a/translations/de-DE/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/de-DE/content/github/authenticating-to-github/about-authentication-to-github.md @@ -55,3 +55,19 @@ You can access repositories on {% data variables.product.product_name %} from th * You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxys might refuse to allow SSH connections. Using SSH requires you to generate an SSH public/private keypair on your local machine and add the public key to your {% data variables.product.product_name %} account. Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." {% if currentVersion == "free-pro-team@latest" %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### {% data variables.product.company_short %}'s token formats + +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. + +| Token type | Prefix | Weitere Informationen | +|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Personal access token | `ghp_` | "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | + +{% endif %} diff --git a/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index 7d1b47d09f..1f019a7f35 100644 --- a/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/de-DE/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -51,5 +51,5 @@ After an enterprise or organization owner enables or enforces SAML SSO for an or ### Weiterführende Informationen -{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} {% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md index 5eb765e764..0accbf2596 100644 --- a/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/de-DE/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -36,8 +36,15 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti ![Token-Scopes auswählen](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} 7. Klicke auf **Generate token** (Token erzeugen). ![Schaltfläche „Generate token“ (Token erzeugen)](/assets/images/help/settings/generate_token.png) -8. Klicke auf {% octicon "clippy" aria-label="The copy to clipboard icon" %}, um das Token in die Zwischenablage zu kopieren. For security reasons, after you navigate off the page, you will not be able to see the token again.{% 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 %} +8. Click +{% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again. + {% if currentVersion == "free-pro-team@latest" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) + {% endif %} {% warning %} diff --git a/translations/de-DE/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/de-DE/content/github/authenticating-to-github/creating-a-strong-password.md index 0475543125..79a5e0396c 100644 --- a/translations/de-DE/content/github/authenticating-to-github/creating-a-strong-password.md +++ b/translations/de-DE/content/github/authenticating-to-github/creating-a-strong-password.md @@ -20,7 +20,7 @@ Für den Schutz Deines Kontos empfehlen wir Dir die folgenden Best Practices: - Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters. - Erzeugen Sie ein eindeutiges Passwort für {% data variables.product.product_name %}. Wenn Sie Ihr {% data variables.product.product_name %}-Passwort auch an anderer Stelle verwenden und dieser Dienst kompromittiert wird, könnten die Angreifer oder andere Personen mit böswilliger Absicht diese Informationen nutzen, um auf Ihr {% data variables.product.product_name %}-Konto zuzugreifen. - Konfiguriere die Zwei-Faktor-Authentifizierung für Dein persönliches Konto. Weitere Informationen findest Du unter „[Informationen zur Zwei-Faktor-Authentifizierung](/articles/about-two-factor-authentication).“ -- Gib Dein Passwort niemals an andere weiter, auch nicht an potenzielle Mitarbeiter. Jede Person sollte ihr eigenes persönliches Konto bei {% data variables.product.product_name %} nutzen. Weitere Informationen zu Möglichkeiten der Zusammenarbeit findest Du unter „[Mitarbeiter in ein persönliches Repository einladen](/articles/inviting-collaborators-to-a-personal-repository)“, „[Informationen über gemeinschaftliche Entwicklungsmodelle](/articles/about-collaborative-development-models/)“ oder „[Mit Gruppen in Organisationen zusammenarbeiten](/articles/collaborating-with-groups-in-organizations/).“ +- Gib Dein Passwort niemals an andere weiter, auch nicht an potenzielle Mitarbeiter. Jede Person sollte ihr eigenes persönliches Konto bei {% data variables.product.product_name %} nutzen. Weitere Informationen zu Möglichkeiten der Zusammenarbeit findest Du unter „[Mitarbeiter in ein persönliches Repository einladen](/articles/inviting-collaborators-to-a-personal-repository)“, „[Informationen über gemeinschaftliche Entwicklungsmodelle](/articles/about-collaborative-development-models/)“ oder „[Mit Gruppen in Organisationen zusammenarbeiten](/organizations/collaborating-with-groups-in-organizations/).“ {% data reusables.repositories.blocked-passwords %} 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 b2260069ef..ca9b8c0040 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 @@ -193,7 +193,7 @@ An overview of some of the most common actions that are recorded as events in th | `sponsored_developer_create` | Wird aufgelöst, wenn Dein {% data variables.product.prodname_sponsors %}-Konto erstellt wird (siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `sponsored_developer_profile_update` | Wird ausgelöst, wenn Du Dein „unterstützter Benutzer"-Profil veränderst (siehe „[Deine Profildetails für {% data variables.product.prodname_sponsors %} verändern](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | | `sponsored_developer_request_approval` | Wird ausgelöst, wenn Du Deine Bewerbung für {% data variables.product.prodname_sponsors %} für die Bewilligung einreichst (siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_tier_description_update` | Wird ausgelöst, wenn Sie die Beschreibung einer Sponsoring-Stufe ändern (siehe „[Sponsoring-Stufen ändern](/articles/changing-your-sponsorship-tiers)“). | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | | `sponsored_developer_update_newsletter_send` | Wird ausgelöst, wenn Sie Ihren Sponsoren eine E-Mail-Aktualisierung senden (siehe „[Sponsoren kontaktieren](/articles/contacting-your-sponsors)“). | | `waitlist_invite_sponsored_developer` | Wird ausgelöst, wenn Du eingeladen wirst, {% data variables.product.prodname_sponsors %} von der Warteliste her beizutreten (siehe „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `waitlist_join` | Wird ausgelöst, wenn Du der Warteliste beitrittst, um ein „unterstützter Entwickler" zu werden (siehe [{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index 188876da2c..45315382c9 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -18,7 +18,7 @@ Du kannst je nach gewünschter Art der Unterhaltung Issues, Pull Requests und Te Issues sind nützlich bei der Diskussion spezifischer Details eines Projekts, beispielsweise Fehlerberichte und geplante Verbesserungen. Weitere Informationen findest Du unter „[Informationen zu Issues](/articles/about-issues).“ Mit Pull Requests kannst Du Änderungsvorschläge direkt kommentieren. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/articles/about-pull-requests)“ und „[Pull Requests kommentieren](/articles/commenting-on-a-pull-request).“ -{% data reusables.organizations.team-discussions-purpose %} Weitere Informationen findest Du unter „[Informationen zu Teamdiskussionen](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions).“ +{% data reusables.organizations.team-discussions-purpose %} Weitere Informationen findest Du unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions).“ ### Auf Ideen in Kommentaren reagieren 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 05fdd695a7..1791b412cd 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 @@ -15,7 +15,7 @@ topics: Nachdem ein Pull-Request geöffnet wurde, kann jeder mit *Lese*-Zugriff die vorgeschlagenen Änderungen überprüfen und kommentieren. Du kannst auch spezifische Änderungen an Codezeilen vorschlagen, die der Autor direkt aus dem Pull-Request anwenden kann. Weitere Informationen findest Du unter „[Vorgeschlagene Änderungen in einem Pull Request überprüfen](/articles/reviewing-proposed-changes-in-a-pull-request).“ -Repository-Inhaber und -Mitarbeiter können von einer bestimmten Person einen Review des Pull Requests anfordern. Organisationsmitglieder können auch einen Review eines Pull Requests von einem Team mit Lesezugriff auf das Repository anfordern. Weitere Informationen findest Du unter „[Einen Pull-Request-Review anfordern](/articles/requesting-a-pull-request-review).“ {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. 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 %} +Repository-Inhaber und -Mitarbeiter können von einer bestimmten Person einen Review des Pull Requests anfordern. Organisationsmitglieder können auch einen Review eines Pull Requests von einem Team mit Lesezugriff auf das Repository anfordern. Weitere Informationen findest Du unter „[Einen Pull-Request-Review anfordern](/articles/requesting-a-pull-request-review).“ {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} Reviews ermöglichen eine Diskussion der vorgeschlagenen Änderungen und tragen dazu bei, dass die Änderungen den Beitragsrichtlinien des Repositorys wie auch anderen Qualitätsstandards entsprechen. Du kannst definieren, welche Personen oder Teams bestimmte Codetypen oder -bereiche in einer CODEOWNERS-Datei besitzen. Wenn durch einen Pull Request Code mit einem definierten Inhaber geändert wird, wird diese Person oder dieses Team automatisch als Reviewer angefordert. Weitere Informationen finden Sie unter „[Informationen zu Codeinhabern](/articles/about-code-owners/)“. diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index ac06b1bbb7..cfed972add 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -14,7 +14,9 @@ topics: If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks. -Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)." +Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} + +After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback). diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index 85cb0e6a8a..2c3cb6e2cc 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -13,7 +13,7 @@ topics: Inhaber und Mitarbeiter eines Repositorys, das einem Benutzerkonto angehört, können Pull Requests zuweisen. Organisationsmitglieder mit Triage-Berechtigungen für ein Repository können einen Pull-Request-Review zuweisen. -Inhaber oder Mitarbeiter können jeder Person, der explizit [Lesezugriff](/articles/access-permissions-on-github) auf ein benutzereigenes Repository gewährt wurde, einen Pull-Request-Review zuweisen. Organisationsmitglieder können jeder Person oder jedem Team mit Lesezugriff auf das Repository einen Pull-Request-Review zuweisen. Der angeforderte Reviewer respektive das angeforderte Team erhält eine Benachrichtigung, dass Du einen Pull-Request-Review von ihm angefordert hast. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. 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 %} +Inhaber oder Mitarbeiter können jeder Person, der explizit [Lesezugriff](/articles/access-permissions-on-github) auf ein benutzereigenes Repository gewährt wurde, einen Pull-Request-Review zuweisen. Organisationsmitglieder können jeder Person oder jedem Team mit Lesezugriff auf das Repository einen Pull-Request-Review zuweisen. Der angeforderte Reviewer respektive das angeforderte Team erhält eine Benachrichtigung, dass Du einen Pull-Request-Review von ihm angefordert hast. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} {% note %} diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index 2ee1fd92c0..d4b45bdb8c 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -79,5 +79,5 @@ If you change the visibility of an internal repository and then delete the repos - „[Sichtbarkeit eines Repositorys festlegen](/articles/setting-repository-visibility)“ - „[Informationen zu Forks](/articles/about-forks)“ - „[Die Forking-Richtlinie für Dein Repository verwalten](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" -- „[Die Forking-Richtlinie für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" - "{% if currentVersion == "free-pro-team@latest" %}[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}" diff --git a/translations/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 596936ed1e..8853d22eb4 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 @@ -23,7 +23,7 @@ Code-Besitzer werden automatisch zur Überprüfung aufgefordert, wenn jemand ein 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 %} +{% 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](/organizations/organizing-members-into-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.22" %} Wenn eine Datei einen Codeinhaber hat, kannst Du sehen, wer der Codeinhaber ist, bevor Du einen Pull Request öffnest. In the repository, you can browse to the file and hover over diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md index a99ff4fef0..46aff9e90d 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -19,7 +19,7 @@ topics: {% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch. -Einige Dateien sind schwer zu identifizieren, und manchmal enthalten Projekte mehr Bibliotheks- und Anbieterdateien als eigenen Primärcode. Wenn Du falsche Ergebnisse erhältst, lies bitte den [Leitfaden zur Fehlerbehebung](https://github.com/github/linguist#troubleshooting) für Linguist. +Einige Dateien sind schwer zu identifizieren, und manchmal enthalten Projekte mehr Bibliotheks- und Anbieterdateien als eigenen Primärcode. Wenn Du falsche Ergebnisse erhältst, lies bitte den [Leitfaden zur Fehlerbehebung](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) für Linguist. ### Markup-Sprachen diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index b4155a7e78..8c2d0e9913 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -22,7 +22,7 @@ Private repositories are only accessible to you, people you explicitly share acc Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." {% endif %} -Organisationsinhaber haben immer Zugriff auf jedes Repository, das in einer Organisation erstellt wurde. Weitere Informationen findest Du unter„[Berechtigungsebenen für die Repositorys einer Organisation](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization).“ +Organisationsinhaber haben immer Zugriff auf jedes Repository, das in einer Organisation erstellt wurde. Weitere Informationen findest Du unter„[Berechtigungsebenen für die Repositorys einer Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization).“ Personen mit Administratorberechtigungen für ein Repository können die Sichtbarkeit eines vorhandenen Repositorys ändern. Weitere Informationen findest Du unter „[Sichtbarkeit eines Repositorys festlegen](/github/administering-a-repository/setting-repository-visibility).“ diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md index 520f8097d1..1766fc4cfb 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -23,13 +23,13 @@ Bevor Du ein Repository duplizierst und zu Deiner neuen Kopie (dem _Spiegel_) de ``` 3. Führe den Spiegel-Push in das neue Repository durch. ```shell - $ cd old-repository.git + $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` 4. Entferne das temporäre lokale Repository, dass Du früher erstellt hast. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Ein Repository spiegeln, das {% data variables.large_files.product_name_long %}-Objekte enthält @@ -41,7 +41,7 @@ Bevor Du ein Repository duplizierst und zu Deiner neuen Kopie (dem _Spiegel_) de ``` 3. Navigiere zu dem Repository, das Du gerade geklont hast. ```shell - $ cd old-repository.git + $ cd old-repository ``` 4. Rufe die {% data variables.large_files.product_name_long %}-Objekte des Repositorys ab. ```shell @@ -58,7 +58,7 @@ Bevor Du ein Repository duplizierst und zu Deiner neuen Kopie (dem _Spiegel_) de 7. Entferne das temporäre lokale Repository, dass Du früher erstellt hast. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Ein Repository an einem anderen Ort spiegeln @@ -72,7 +72,7 @@ Wenn Du ein Repository an einem anderen Ort spiegeln und Aktualisierungen vom Or ``` 3. Lege den Push-Ort auf Deinen Spiegel fest. ```shell - $ cd repository-to-mirror.git + $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index d955079c3e..39912cae42 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > provide shell access. ``` -Wenn das Repository zu einer Organisation gehört und Du einen SSH-Schlüssel verwendest, der von einer OAuth-App generiert wurde, wurde der OAuth-App-Zugriff möglicherweise von einem Organisationsinhaber eingeschränkt. Weitere Informationen findest Du unter „Informationen zu OAuth-App-Zugriffsbeschränkungen.“ +Wenn das Repository zu einer Organisation gehört und Du einen SSH-Schlüssel verwendest, der von einer OAuth-App generiert wurde, wurde der OAuth-App-Zugriff möglicherweise von einem Organisationsinhaber eingeschränkt. For more information, see "About OAuth App access restrictions." Weitere Informationen findest Du unter „[Einen neuen SSH-Schlüssel zum GitHub-Konto hinzufügen](/articles/adding-a-new-ssh-key-to-your-github-account)“. diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md index 1053e300af..d1e5382d2c 100644 --- a/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md +++ b/translations/de-DE/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -1,6 +1,6 @@ --- title: Using Codespaces in Visual Studio -intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vs %} by connecting with your account on {% data variables.product.product_name %}.' +intro: 'This preview has concluded and will no longer be accepting signups.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,50 +10,10 @@ topics: {% note %} -**Hinweis:** {% data variables.product.prodname_codespaces %} befindet sich derzeit in der eingeschränkten Beta-Phase und kann sich jederzeit verändern. Während der Beta-Phase gibt {% data variables.product.prodname_dotcom %} keine Garantie für die Verfügbarkeit von {% data variables.product.prodname_codespaces %} ab. [Sign up for the limited public beta](https://github.com/features/codespaces/signup-vs). Weitere Informationen zum Beitritt zur Beta-Phase findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." +**Hinweis:** {% data variables.product.prodname_codespaces %} befindet sich derzeit in der eingeschränkten Beta-Phase und kann sich jederzeit verändern. Während der Beta-Phase gibt {% data variables.product.prodname_dotcom %} keine Garantie für die Verfügbarkeit von {% data variables.product.prodname_codespaces %} ab. {% endnote %} ### About codespaces in {% data variables.product.prodname_vs %} -You can create a codespace in {% data variables.product.prodname_vs %} to develop applications in a Windows environment. When you use a codespace in {% data variables.product.prodname_vs %}, you can browse source code, build solutions, and commit changes to your repository. - -You must create a codespace in {% data variables.product.prodname_vs %} to use it with the application. Codespaces created outside of {% data variables.product.prodname_vs %} can not currently be used with {% data variables.product.prodname_vs %}. - -### Vorrausetzungen - -Before you configure a codespace in {% data variables.product.prodname_vs %}, you must download the latest version of [{% data variables.product.prodname_vs %} Preview](https://aka.ms/vspreview). - -#### Enabling the connection between {% data variables.product.prodname_vs %} and {% data variables.product.prodname_github_codespaces %} - -Connecting to {% data variables.product.prodname_github_codespaces %} with the {% data variables.product.prodname_vs %} Preview is not enabled by default, so you will first need to enable the Preview Features option. - -1. In {% data variables.product.prodname_vs %} Preview, use the Tools drop-down menu, then click **Options**. -2. Under **Environment**, select **Preview Features** and check the **Connect to {% data variables.product.prodname_github_codespaces %}** preview feature. ![Check the Connect to {% data variables.product.prodname_github_codespaces %} preview feature](/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png) -3. You will need to restart {% data variables.product.prodname_vs %} for the feature to be available. - -### Creating a codespace in {% data variables.product.prodname_vs %} - -1. When you launch {% data variables.product.prodname_vs %}, the Start Window will show a **Connect to a codespace** button under "Get started". ![Visual Studio Start window with Connect to a codespace](/assets/images/help/codespaces/visual-studio-start-window.png) -2. Click **Connect to a codespace**. -3. Click **Sign in to {% data variables.product.prodname_dotcom %}** and follow the prompts, or click **Create one!** to create a new {% data variables.product.prodname_dotcom %} account and sign into the account. ![Visual Studio sign in to {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/visual-studio-sign-in-to-github.png) -4. Under "Codespace details", type the repository's URL you want {% data variables.product.prodname_github_codespaces %} to clone into your codespace. -5. Optionally, use the Instance type and Suspend after drop-down menus to configure more codespace details. ![Visual Studio codespace details](/assets/images/help/codespaces/visual-studio-codespace-details.png) -6. Click **Create and Connect**. {% data variables.product.prodname_github_codespaces %} will begin preparing the codespace and open {% data variables.product.prodname_vs %} after the codespace is ready. The codespace name will appear in the remote indicator in the menu. ![Visual Studio connected to eShopOnWeb repository codespace](/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png) - -### Einen Codespace in {% data variables.product.prodname_vs %} eröffnen - -1. Use the File drop-down menu, and click **Connect to a Codespace**. ![Visual Studio File Connect to a codespace menu item](/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png) -2. Under "{% data variables.product.prodname_github_codespaces %}", click the codespace you want to connect to, then click **Connect**. ![Visual Studio displaying available codespaces and details](/assets/images/help/codespaces/visual-studio-connect-codespace.png) - -### Configuring a codespace for {% data variables.product.prodname_vs %} - -A codespace, created with {% data variables.product.prodname_vs %}, can be customized through a new tool called devinit, a command line tool included with {% data variables.product.prodname_vs %}. - -#### devinit - -[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) lets you install additional frameworks and tools into your Windows development codespaces, modify environment variables, and more. - -devinit supports a configuration file called [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). You can add this file to your project if you want to create a customized and repeatable development environment. When you use devinit with a [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) file, your codespaces will be automatically configured on creation. - -For more information about Windows codespace configuration and devinit, see [Customize a codespace](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces) in the {% data variables.product.prodname_vs %} documentation. For more information about devinit, see [Getting started with devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit). +The private preview for GitHub Codespaces in Visual Studio 2019 has concluded. For more information, see the [Visual Studio 2019 documentation](https://docs.microsoft.com/visualstudio/ide/codespaces/codespaces-overview?view=vs-2019). 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 9684696ef4..108de949de 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 @@ -2,46 +2,44 @@ title: About code scanning intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' 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' + enterprise-server: '2.22' +topics: + - sicherheit --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About {% data variables.product.prodname_code_scanning %} +### Informationen zu {% data variables.product.prodname_code_scanning %} -{% data reusables.code-scanning.about-code-scanning %} +With {% data variables.product.prodname_code_scanning %}, developers can quickly and automatically analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. -If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." +If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use 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 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 "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." -### About {% data variables.product.prodname_codeql %} +### Informationen zu {% data variables.product.prodname_codeql %} -You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. {% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. -{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. +For more information about API endpoints for {% data variables.product.prodname_code_scanning %}, see "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)." {% data reusables.code-scanning.supported-languages %} -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. +You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation. {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### Informationen zur Abrechnung für {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“ {% endif %} @@ -53,7 +51,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### Further reading +### Weiterführende Informationen {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 612c2f6227..1548ea272e 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 @@ -5,8 +5,9 @@ product: '{% data reusables.gated-features.code-scanning %}' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' miniTocMaxHeadingLevel: 4 versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - sicherheit --- {% data reusables.code-scanning.beta %} @@ -14,41 +15,39 @@ versions: ### About {% data variables.product.prodname_code_scanning %} configuration -You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." +You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)." -This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}. -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. +You can write a configuration file for {% data variables.product.prodname_code_scanning %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. -### Editing a {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} saves workflow files in the `.github/workflows` directory of your repository. You can find a workflow you have added by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. Navigiere in Deinem Repository zu der Workflow-Datei, die Du bearbeiten möchtest. +1. Um den Workflow-Editor zu öffnen, klickst Du in der oberen rechten Ecke der Dateiansicht auf {% octicon "pencil" aria-label="The edit icon" %}. ![Schaltfläche zum Editieren der Workflow-Datei](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. ![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." ### Configuring frequency -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +You can scan code on a schedule or when specific events occur in a repository. -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +Scanning code on every push to the repository, and every time a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. #### Scanning on push -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +If you use the default workflow, {% data variables.product.prodname_code_scanning %} will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)“. #### Scanning pull requests -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)“. For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." @@ -69,7 +68,7 @@ on: {% note %} -**Notes** +**Hinweise:** * `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." * For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. @@ -80,7 +79,7 @@ For more information about using `on:pull_request:paths-ignore` and `on:pull_req #### Scanning on a schedule -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +The default {% data variables.product.prodname_code_scanning %} workflow uses the `pull_request` event to trigger a code scan on the `HEAD` commit of a pull request. To adjust this schedule, edit the `cron` value in the workflow. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)“. {% note %} @@ -88,7 +87,7 @@ If you use the default {% data variables.product.prodname_codeql_workflow %}, th {% endnote %} -#### Example +#### Beispiel The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. @@ -99,17 +98,17 @@ on: pull_request: branches: [main] schedule: - - cron: '0 15 * * 0' + - cron: '40 7 * * 2' ``` This workflow scans: * Every push to the default branch and the protected branch * Every pull request to the default branch -* The default branch at 3 P.M. every Sunday +* The default branch every Tuesday at 7:40 UTC ### Specifying an operating system -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} +If your code requires a specific operating system to compile, you can configure this in your workflow. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} @@ -122,7 +121,7 @@ jobs: {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% data variables.product.prodname_code_scanning_capc %} supports the latest versions of macOS, Ubuntu, and Windows. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." {% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} @@ -134,9 +133,9 @@ jobs: The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." -{% data reusables.code-scanning.specify-language-to-analyze %} +{% data variables.product.prodname_code_scanning_capc %} automatically detects and scans code written in the supported languages. -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix. +If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. ```yaml jobs: @@ -203,30 +202,37 @@ jobs: {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. +To add one or more query suites, add a `queries` section to your configuration file. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. +{% raw %} ``` yaml - uses: github/codeql-action/init@v1 with: queries: COMMA-SEPARATED LIST OF PATHS + # Optional. Provide a token to access private repositories. + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +You can also run additional query suites by specifying these in a configuration file. Query suites are collections of queries, usually grouped by purpose or language. {% data reusables.code-scanning.codeql-query-suites %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +You can run additional queries by specifying these in a configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For examples of configuration files, see "[Example configuration files](#example-configuration-files)." In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. +{% raw %} ``` 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 + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -### Using a custom configuration file +### Using a third-party code scanning tool As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. @@ -238,9 +244,19 @@ 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 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_. +{% data reusables.code-scanning.custom-configuration-file %} -The settings in the file are written in YAML format. +If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository. + +{% raw %} +```yaml +uses: github/codeql-action/init@v1 +with: + external-repository-token: ${{ secrets.ACCESS_TOKEN }} +``` +{% endraw %} + +The settings in the configuration file are written in YAML format. #### Specifying additional queries @@ -259,7 +275,7 @@ For more information about additional queries, see "[Running additional queries] #### Disabling the default queries -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +If you only want to run custom queries, you can disable the default security queries by adding `disable-default-queries: true` to your configuration file. #### Specifying directories to scan @@ -277,14 +293,14 @@ paths-ignore: **Note**: -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. Weitere Informationen findest Du unter „[Workflow-Syntax für {% 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. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. {% endnote %} For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow file. #### Example configuration files @@ -296,25 +312,6 @@ You can quickly analyze small portions of a monorepo when you modify code in spe {% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)." -### Accessing private repositories - -If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs..steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." - -For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. - -{% 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 %} - ### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." +You can display code analysis from a third-party tool in {% data variables.product.prodname_dotcom %} by adding the `upload-sarif` action to your workflow. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 14a5c534e5..20c685092f 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -37,7 +37,7 @@ You need write permission to view a summary of all the alerts for a repository o {% 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. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. ![Summary of alerts](/assets/images/enterprise/3.1/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) @@ -49,7 +49,7 @@ If you have write permission for a repository, you can view fixed alerts by view 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. -![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} @@ -102,11 +102,11 @@ To dismiss or delete alerts: 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. - ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![Filter alerts by rule](/assets/images/enterprise/3.1/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. - ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) + ![Open an alert from the summary list](/assets/images/enterprise/3.1/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) diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md index 36352dcffe..2fa92f6528 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -25,7 +25,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -65,7 +65,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endnote %} @@ -91,7 +91,7 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. 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 index 2f6ca59582..cde36a4c82 100644 --- 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 @@ -38,7 +38,7 @@ 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)." {% endif %} -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)." +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](/organizations/keeping-your-organization-secure/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)." {% endif %} @@ -47,7 +47,7 @@ Once your system is set up, you can enable and disable these features at the org For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. -For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}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)."{% endif %} +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)."{% endif %} {% endif %} 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 d8f883822b..a0681b4de8 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 @@ -92,7 +92,7 @@ Zusätzlich zu den mit {% data variables.product.prodname_team %} verfügbaren F - {% data variables.contact.enterprise_support %}. Weitere Informationen findest Du unter „{% data variables.product.prodname_ghe_cloud %}-Support“ und „{% data variables.product.prodname_ghe_cloud %}-Nachtrag.“ - 50.000 {% data variables.product.prodname_actions %}-Minuten - 50 GB {% data variables.product.prodname_registry %}-Speicher -- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime - Die Option, die Richtlinien und Abrechnungen für mehrere {% data variables.product.prodname_dotcom_the_website %}-Organisationen mit Enterprise-Konto zentral zu verwalten. Weitere Informationen findest Du unter "About enterprise accounts" (Über Enterprise-Konten). 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 2983f732dc..2f1539c732 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 @@ -1,6 +1,6 @@ --- -title: Keyboard shortcuts -intro: 'Nearly every page on {% data variables.product.product_name %} has a keyboard shortcut to perform actions faster.' +title: Tastenkürzel +intro: 'Auf nahezu allen Seiten auf {% data variables.product.product_name %} gibt es Tastenkürzel, um Aktionen schneller durchführen zu können.' redirect_from: - /articles/using-keyboard-shortcuts/ - /categories/75/articles/ @@ -13,186 +13,189 @@ versions: --- -### About keyboard shortcuts +### Informationen zu Tastenkürzeln -Typing ? in {% data variables.product.product_name %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate. +Wird ? in {% data variables.product.product_name %} eingegeben, öffnet sich ein Dialogfeld, das die für die jeweilige Seite verfügbaren Tastenkürzel auflistet. Mit diesen Tastenkürzeln kannst Du Aktionen auf der gesamten Website durchführen, ohne Deine Maus zur Navigation verwenden zu müssen. -Below is a list of some of the available keyboard shortcuts. +Im Folgenden findest Du eine Liste mit einigen der verfügbaren Tastenkürzel. -### Site wide shortcuts +### Seitenweite Tastenkürzel -| Keyboard shortcut | Description -|-----------|------------ -|s or / | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/articles/about-searching-on-github)." -|g n | Go to your notifications. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." -|esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in +| Tastenkürzel | Beschreibung | +| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| s oder / | Hiermit fokussierst Du die Suchleiste. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.company_short %}](/articles/about-searching-on-github).“ | +| g n | Gehe zu Deinen Benachrichtigungen. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." | +| esc | Wenn auf eine Benutzer-, Issue- oder Pull-Request-Hovercard (Informationskarte) konzentriert, schließt das Kürzel die Hovercard und konzentriert sich erneut auf das Element, in dem sich die Hovercard befindet | -### Repositories +### Repositorys -| 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)." +| Tastenkürzel | Beschreibung | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| g c | Hiermit wechselst Du zur Registerkarte **Code** | +| g i | Hiermit wechselst Du zur Registerkarte **Issues**. Weitere Informationen findest Du unter „[Informationen zu Issues](/articles/about-issues).“ | +| g p | Hiermit wechselst Du zur Registerkarte **Pull Requests**. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/articles/about-pull-requests).“ | +| g a | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)." | +| g b | Hiermit wechselst Du zur Registerkarte **Projects** (Projekte). Weitere Informationen findest Du unter „[Informationen zu Projektboards](/articles/about-project-boards).“ | +| g w | Hiermit wechselst Du zur Registerkarte **Wiki**. Weitere Informationen findest Du unter „[Informationen zu Wikis](/communities/documenting-your-project-with-wikis/about-wikis).“ | -### Source code editing +### Quellcodebearbeitung -| Keyboard shortcut | Description -|-----------|------------ -|e | Open source code file in the **Edit file** tab -|control f or command f | Start searching in file editor -|control g or command g | Find next -|shift control g or shift command g | Find previous -|shift control f or command option f | Replace -|shift control r or shift command option f | Replace all -|alt g | Jump to line -|control z or command z | Undo -|control y or command y | Redo -|cmd + shift + p | Toggles between the **Edit file** and **Preview changes** tabs +| Tastenkürzel | Beschreibung | +| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | +| e | Öffne Quellcode-Datei in der Registerkarte **Edit file** (Datei anpassen) | +| Steuertaste + f oder Befehlstaste + f | Suchen im Datei-Editor | +| Steuertaste + g oder Befehlstaste + g | Suchen nach dem nächsten Eintrag | +| Umschalttaste + Steuertaste+g oder Umschalttaste + Befehlstaste+g | Suchen nach dem vorherigen Eintrag | +| Umschalttaste + Steuertaste+f oder Befehlstaste + f | Ersetze den Eintrag | +| Umschalttaste + Steuertaste + r oder Umschalttaste + Befehlstaste + f | Ersetze alle Einträge | +| Alt+g | Springe zur entsprechenden Zeile | +| Steuertaste + z oder Befehlstaste + z | Mache die Aktion rückgängig | +| Steuertaste + y oder Befehlstaste + y | Wiederhole Sie die Aktion | +| Befehlstaste + Umschalttaste + p | Umschalten zwischen den Registerkarten **Edit file** (Datei bearbeiten) und **Preview changes** (Änderungsvorschau) | +| control s or command s | Write a commit message | -For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands). +Weitere Tastenkürzel findest Du in der [CodeMirror-Dokumentation](https://codemirror.net/doc/manual.html#commands). -### Source code browsing +### Quellcodedurchsuchung -| Keyboard shortcut | Description -|-----------|------------ -|t | Activates the file finder -|l | Jump to a line in your code -|w | Switch to a new branch or tag -|y | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)." -|i | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)." -|b | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)." +| Tastenkürzel | Beschreibung | +| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| t | Hiermit wird die Dateisuche aktiviert | +| l | Springe zu einer Zeile in Deinem Code | +| w | Wechsle zu einem neuen Branch oder Tag | +| y | Erweitere eine URL auf ihre kanonische Form. Weitere Informationen findest Du unter „[Permalinks zu Dateien abrufen](/articles/getting-permanent-links-to-files)“ | +| i | Zeige Kommentare zu Diffs an oder blende sie aus. Weitere Informationen findest Du unter „[Kommentare zum Diff eines Pull Requests](/articles/commenting-on-the-diff-of-a-pull-request)“ | +| a | Show or hide annotations on diffs | +| b | Öffne die Blame-Ansicht. Weitere Informationen findest Du unter „[Änderungen in einer Datei verfolgen](/articles/tracing-changes-in-a-file)“ | -### Comments +### Kommentare -| Keyboard shortcut | Description -|-----------|------------ -| control b or command b | Inserts Markdown formatting for bolding text -| control i or command i | Inserts Markdown formatting for italicizing text -| control k or command k | Inserts Markdown formatting for creating a link -| control shift p or command shift p| Toggles between the **Write** and **Preview** comment tabs -| control enter | Submits a comment -| control . and then control [saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} -|control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} -| r | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | +| Tastenkürzel | Beschreibung | +| ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Steuertaste + b oder Befehlstaste + b | Hiermit wird die Markdown-Formatierung für den Fettdruck von Text eingefügt. | +| Steuertaste + i oder Befehlstaste + i | Hiermit wird die Markdown-Formatierung für die Kursivsetzung von Text eingefügt. | +| Steuertaste + k oder Befehlstaste + k | Hiermit wird die Markdown-Formatierung zum Erstellen eines Links eingefügt. | +| Steuertaste + Umschalttaste + p oder Befehlstaste + Umschalttaste + p | Hiermit wird zwischen den Kommentar-Registerkarten **Write** (Schreiben) und **Preview** (Vorschau) umgeschaltet | +| Steuertaste + Eingabetaste | Hiermit wird ein Kommentar abgesendet. | +| Steuertaste + . und dann Steuertaste + [Nummer der gespeicherten Antwort] | Hiermit wird das Menü für gespeicherte Antworten geöffnet und im Kommentarfeld automatisch eine gespeicherte Antwort eingetragen. For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} +| Steuertaste + g oder Befehlstaste + g | Hiermit wird ein Vorschlag eingefügt. Weitere Informationen findest Du unter „[Vorgeschlagene Änderungen in einem Pull Request überprüfen](/articles/reviewing-proposed-changes-in-a-pull-request).“ +{% endif %} +| r | Hiermit wird der ausgewählte Text in Deiner Antwort zitiert. Weitere Informationen findest Du unter „[Grundlegende Schreib- und Formatierungssyntax](/articles/basic-writing-and-formatting-syntax#quoting-text).“ | -### Issue and pull request lists +### Issue- und Pull-Request-Listen -| Keyboard shortcut | Description -|-----------|------------ -|c | Create an issue -| control / or command / | Focus your cursor on the issues or pull requests search bar. For more information, see "[Using search to filter issues and pull requests](/articles/using-search-to-filter-issues-and-pull-requests)."|| -|u | Filter by author -|l | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." -| alt and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." -|m | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)." -|a | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)." -|o or enter | Open issue +| Tastenkürzel | Beschreibung | +| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| c | Hiermit wird ein Issue erstellt. | +| Steuertaste + / oder Befehlstaste + / | Hiermit wird der Fokus Deines Cursors auf die Suchleiste mit den Issues oder mit den Pull Requests gelegt. Weitere Informationen findest Du unter „[Issues und Pull Requests mit der Suchfunktion filtern](/articles/using-search-to-filter-issues-and-pull-requests).“| | +| u | Hiermit wird nach Autor gefiltert. | +| l | Hiermit wird nach Kennzeichnungen gefiltert oder werden diese bearbeitet. Weitere Informationen findest Du unter „[Issues und Pull Requests nach Kennzeichnungen filtern](/articles/filtering-issues-and-pull-requests-by-labels).“ | +| Alt und klicken | Hiermit werden Kennzeichnungen beim Filtern nach Kennzeichnungen ausgeschlossen. Weitere Informationen findest Du unter „[Issues und Pull Requests nach Kennzeichnungen filtern](/articles/filtering-issues-and-pull-requests-by-labels).“ | +| m | Hiermit wird nach Meilensteinen gefiltert oder werden diese bearbeitet. Weitere Informationen findest Du unter „[Issues und Pull Requests nach Meilensteinen filtern](/articles/filtering-issues-and-pull-requests-by-milestone).“ | +| a | Hiermit wird nach Bearbeitern gefiltert oder werden diese bearbeitet. Weitere Informationen findest Du unter „[Issues und Pull Requests nach Bearbeitern filtern](/articles/filtering-issues-and-pull-requests-by-assignees).“ | +| o oder Eingabetaste | Hiermit wird ein Issue geöffnet. | -### Issues and pull requests -| Keyboard shortcut | Description -|-----------|------------ -|q | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)." -|m | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)." -|l | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)." -|a | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)." -|cmd + shift + p or control + shift + p | Toggles between the **Write** and **Preview** tabs +### Issues und Pull Requests +| Tastenkürzel | Beschreibung | +| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| q | Hiermit wird ein Reviewer angefordert. Weitere Informationen findest Du unter „[Pull-Request-Review anfordern](/articles/requesting-a-pull-request-review/).“ | +| m | Hiermit wird ein Meilenstein festgelegt. Weitere Informationen findest Du unter „[Meilensteine mit Issues und Pull Requests verknüpfen](/articles/associating-milestones-with-issues-and-pull-requests/).“ | +| l | Hiermit wird eine Kennzeichnung angewendet. Weitere Informationen findest Du unter „[Kennzeichnungen auf Issues und Pull Requests anwenden](/articles/applying-labels-to-issues-and-pull-requests/).“ | +| a | Hiermit wird ein Bearbeiter festgelegt. Weitere Informationen findest Du unter „[Issues und Pull Requests anderen {% data variables.product.company_short %}-Benutzern zuweisen](/articles/assigning-issues-and-pull-requests-to-other-github-users/).“ | +| Befehlstaste + Umschalttaste+p oder Steuertaste + Umschalttaste + p | Hiermit wird zwischen den Registerkarten **Write** (Schreiben) und **Preview** (Vorschau) umgeschaltet. | -### Changes in pull requests +### Änderungen in Pull Requests -| Keyboard shortcut | Description -|-----------|------------ -|c | Open the list of commits in the pull request -|t | Open the list of changed files in the pull request -|j | Move selection down in the list -|k | Move selection up in the list -| cmd + shift + enter | Add a single comment on a pull request diff | -| alt and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| Click, then shift and click | Comment on multiple lines of a pull request by clicking a line number, holding shift, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} +| Tastenkürzel | Beschreibung | +| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | Hiermit wird die Liste der Commits im Pull Request geöffnet. | +| t | Hiermit wird die Liste der geänderten Dateien im Pull Request geöffnet. | +| j | Hiermit verschiebt sich die Auswahl in der Liste nach unten | +| k | Hiermit verschiebt sich die Auswahl in der Liste nach oben | +| Befehlstaste + Umschalttaste + Eingabetaste | Hiermit fügst Du einen einzelnen Kommentar zu einer Pull-Request-Diff hinzu | +| Alt und klicken | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| Klicke, dann Shift und klicke | Kommentiere mehrere Zeilen eines Pull-Requests, indem Du auf eine Zeilennummer klickst, shift gedrückt hältst und dann auf eine andere Zeilennummer klickst. Weitere Informationen findest Du unter „[Einen Pull Request kommentieren](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." +{% endif %} -### Project boards +### Projektboards -#### Moving a column +#### Spalte verschieben -| Keyboard shortcut | Description -|-----------|------------ -|enter or space | Start moving the focused column -|escape | Cancel the move in progress -|enter | Complete the move in progress -|← or h | Move column to the left -|command + ← or command + h or control + ← or control + h | Move column to the leftmost position -|→ or l | Move column to the right -|command + → or command + l or control + → or control + l | Move column to the rightmost position +| Tastenkürzel | Beschreibung | +| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | +| Eingabetaste oder Leertaste | Hiermit wird die fokussierte Spalte verschoben. | +| Esc | Hiermit wird die ausgeführte Verschiebung abgebrochen. | +| Eingabetaste | Hiermit wird die ausgeführte Verschiebung abgeschlossen. | +| ← oder h | Hiermit wird die Spalte nach links verschoben. | +| command + ← or command + h or control + ← or control + h | Hiermit wird die Spalte an die äußerste linke Position verschoben. | +| → oder l | Hiermit wird die Spalte nach rechts verschoben. | +| command + → or command + l or control + → or control + l | Hiermit wird die Spalte an die äußerste rechte Position verschoben. | -#### Moving a card +#### Karte verschieben -| Keyboard shortcut | Description -|-----------|------------ -|enter or space | Start moving the focused card -|escape | Cancel the move in progress -|enter | Complete the move in progress -|↓ or j | Move card down -|command + ↓ or command + j or control + ↓ or control + j | Move card to the bottom of the column -|↑ or k | Move card up -|command + ↑ or command + k or control + ↑ or control + k | Move card to the top of the column -|← or h | Move card to the bottom of the column on the left -|shift + ← or shift + h | Move card to the top of the column on the left -|command + ← or command + h or control + ← or control + h | Move card to the bottom of the leftmost column -|command + shift + ← or command + shift + h or control + shift + ← or control + shift + h | Move card to the top of the leftmost column -|→ | Move card to the bottom of the column on the right -|shift + → or shift + l | Move card to the top of the column on the right -|command + → or command + l or control + → or control + l | Move card to the bottom of the rightmost column -|command + shift + → or command + shift + l or control + shift + → or control + shift + l | Move card to the bottom of the rightmost column +| Tastenkürzel | Beschreibung | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ | +| Eingabetaste oder Leertaste | Hiermit wird die fokussierte Karte verschoben. | +| Esc | Hiermit wird die ausgeführte Verschiebung abgebrochen. | +| Eingabetaste | Hiermit wird die ausgeführte Verschiebung abgeschlossen. | +| ↓ oder j | Hiermit wird die Karte nach unten verschoben. | +| command + ↓ or command + j or control + ↓ or control + j | Hiermit wird die Karte in den unteren Bereich der Spalte verschoben. | +| ↑ oder k | Hiermit wird die Karte nach oben verschoben. | +| command + ↑ or command + k or control + ↑ or control + k | Hiermit wird die Karte in den oberen Bereich der Spalte verschoben. | +| ← oder h | Hiermit wird die Karte in den unteren Bereich der Spalte auf der linken Seite verschoben. | +| shift + ← or shift + h | Hiermit wird die Karte in den oberen Bereich der Spalte auf der linken Seite verschoben. | +| command + ← or command + h or control + ← or control + h | Hiermit wird die Karte in den unteren Bereich der Spalte ganz links verschoben. | +| command + shift + ← or command + shift + h or control + shift + ← or control + shift + h | Hiermit wird die Karte in den oberen Bereich der Spalte ganz links verschoben. | +| → | Hiermit wird die Karte in den unteren Bereich der Spalte auf der rechten Seite verschoben. | +| shift + → or shift + l | Hiermit wird die Karte in den oberen Bereich der Spalte auf der rechten Seite verschoben. | +| command + → or command + l or control + → or control + l | Hiermit wird die Karte in den unteren Bereich der Spalte ganz rechts verschoben. | +| command + shift + → or command + shift + l or control + shift + → or control + shift + l | Hiermit wird die Karte in den unteren Bereich der Spalte ganz rechts verschoben. | #### Previewing a card -| Keyboard shortcut | Description -|-----------|------------ -|esc | Close the card preview pane +| Tastenkürzel | Beschreibung | +| -------------- | --------------------------- | +| esc | Close the card preview pane | {% if currentVersion == "free-pro-team@latest" %} ### {% data variables.product.prodname_actions %} -| 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 +| Tastenkürzel | Beschreibung | +| --------------------------------------------------------- | --------------------------------------------------------------------------- | +| command + space or control + space | Hiermit erhältst Du im Workflow-Editor Vorschläge für Deine Workflow-Datei. | +| g f | Go to the workflow file | +| shift + t or T | Toggle timestamps in logs | +| shift + f or F | Toggle full-screen logs | +| esc | Exit full-screen logs | {% endif %} -### Notifications - +### Benachrichtigungen {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| Keyboard shortcut | Description -|-----------|------------ -|e | Mark as done -| shift + u| Mark as unread -| shift + i| Mark as read -| shift + m | Unsubscribe +| Tastenkürzel | Beschreibung | +| -------------------- | ----------------------- | +| e | Als erledigt markieren | +| shift + u | Als ungelesen markieren | +| shift + i | Als gelesen markieren | +| shift + m | Kündigen | {% else %} -| Keyboard shortcut | Description -|-----------|------------ -|e or I or y | Mark as read -|shift + m | Mute thread +| Tastenkürzel | Beschreibung | +| ------------------------------------------------ | ---------------------------------------- | +| e oder I oder y | Als gelesen markieren | +| shift + m | Hiermit wird der Thread stummgeschaltet. | {% endif %} -### Network graph +### Netzwerkdiagramm -| Keyboard shortcut | Description -|-----------|------------ -|← or h | Scroll left -|→ or l | Scroll right -|↑ or k | Scroll up -|↓ or j | Scroll down -|shift + ← or shift + h | Scroll all the way left -|shift + → or shift + l | Scroll all the way right -|shift + ↑ or shift + k | Scroll all the way up -|shift + ↓ or shift + j | Scroll all the way down +| Tastenkürzel | Beschreibung | +| -------------------------------------------- | -------------------------------------------- | +| ← oder h | Hiermit wird nach links gescrollt. | +| → oder l | Hiermit wird nach rechts gescrollt. | +| ↑ oder k | Hiermit wird nach oben gescrollt. | +| ↓ oder j | Hiermit wird nach unten gescrollt. | +| shift + ← or shift + h | Hiermit wird komplett nach links gescrollt. | +| shift + → or shift + l | Hiermit wird komplett nach rechts gescrollt. | +| shift + ↑ or shift + k | Hiermit wird komplett nach oben gescrollt. | +| shift + ↓ or shift + j | Hiermit wird komplett nach unten gescrollt. | diff --git a/translations/de-DE/content/github/index.md b/translations/de-DE/content/github/index.md index 128daaa19c..4ede7bb06a 100644 --- a/translations/de-DE/content/github/index.md +++ b/translations/de-DE/content/github/index.md @@ -23,7 +23,7 @@ versions: {% link_in_list /managing-subscriptions-and-notifications-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 %} @@ -57,7 +57,6 @@ versions: {% 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 %} 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 fd54fb5ed2..50299e6279 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 @@ -42,9 +42,9 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." -For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} 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 095fac6fe0..b50c278494 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 @@ -13,7 +13,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/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" %} 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 25eaa87121..d1d8e07324 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 @@ -66,7 +66,7 @@ E-Mail-Benachrichtigungen ermöglichen auch Flexibilität bei der Art von Benach ### Über die Teilnahme und das Beobachten von Benachrichtigungen -Wenn Du ein Repository beobachtest, abonnierst Du Aktualisierungen für Aktivitäten in diesem Repository. Ebenfalls, wenn Du die Diskussionen eines bestimmten Teams verfolgst, abonnierst Du alle Aktualisierungen der Unterhaltung auf der Seite dieses Teams. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)“. +Wenn Du ein Repository beobachtest, abonnierst Du Aktualisierungen für Aktivitäten in diesem Repository. Ebenfalls, wenn Du die Diskussionen eines bestimmten Teams verfolgst, abonnierst Du alle Aktualisierungen der Unterhaltung auf der Seite dieses Teams. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“. To see repositories that you're watching, go to your [watching page](https://github.com/watching). Weitere Informationen findest Du unter „[Abonnements und Benachrichtigungen auf GitHub verwalten](/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" %} @@ -78,7 +78,7 @@ You can configure notifications for a repository on the repository page, or on y #### About custom notifications {% data reusables.notifications-v2.custom-notifications-beta %} You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository. -{% endif %} For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)." +{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. #### 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. @@ -248,16 +248,15 @@ You can also schedule when {% data variables.product.prodname_mobile %} will sen 1. In the bottom menu, tap **Profile**. 2. Um deine Einstellungen zu sehen, tippe auf {% octicon "gear" aria-label="The Gear icon" %}. -3. To update your notification settings, tap **Notifications** and then use the toggles to enable or disable your preferred types of push notifications. -4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Receive Notifications**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications. +3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications. +4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications. ### Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %} Du kannst wählen, ob Du ein einzelnes Repository ansehen möchtest oder nicht mehr. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository. -1. On {% data variables.product.prodname_mobile %}, navigate to main page of the repository. +1. Navigieren Sie in {% data variables.product.prodname_mobile %} zur Repository-Hauptseite. 2. Tap **Watch**. ![The watch button on {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-button.png) 3. To choose what activities you receive notifications for, tap your preferred watch settings. ![Watch settings dropdown menu in {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-settings.png) -{% data reusables.notifications-v2.custom-notifications-beta %} {% endif %} diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index b8dd3bdd39..05923eb46a 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -38,7 +38,7 @@ Eine Übersicht Deiner Repository-Abonnements findest Du unter „[Repositorys {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. +**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." {% endtip %} {% endif %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index e010eeacc4..b9c192258c 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -8,6 +8,8 @@ redirect_from: - /articles/discounted-subscriptions-for-github-accounts versions: free-pro-team: '*' +topics: + - Abrechnung --- {% tip %} @@ -18,11 +20,11 @@ versions: ### Rabatte für persönliche Konten -Neben den unbegrenzten öffentlichen und privaten Repositorys für Studenten und Universitätsmitarbeiter mit {% data variables.product.prodname_free_user %} können verifizierte Studenten das {% data variables.product.prodname_student_pack %} beantragen, um zusätzliche Vorteile von {% data variables.product.prodname_dotcom %}-Partnern zu erhalten. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." +Neben den unbegrenzten öffentlichen und privaten Repositorys für Studenten und Universitätsmitarbeiter mit {% data variables.product.prodname_free_user %} können verifizierte Studenten das {% data variables.product.prodname_student_pack %} beantragen, um zusätzliche Vorteile von {% data variables.product.prodname_dotcom %}-Partnern zu erhalten. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)." ### Rabatte für Schulen und Universitäten -Verifizierte akademische Fakultäten können {% data variables.product.prodname_team %} für den Unterricht oder die akademische Forschung beantragen. 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)." Weitere Informationen findest Du unter „[{{ site.data.variables.product.prodname_dotcom }} für Lehre und Forschung nutzen](/articles/using-github-in-your-classroom-and-research)“. Weitere Informationen findest Du unter [{% data variables.product.prodname_education %}](https://education.github.com/). +Verifizierte akademische Fakultäten können {% data variables.product.prodname_team %} für den Unterricht oder die akademische Forschung beantragen. For more information, see "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)." Weitere Informationen findest Du unter „[{{ site.data.variables.product.prodname_dotcom }} für Lehre und Forschung nutzen](/articles/using-github-in-your-classroom-and-research)“. Weitere Informationen findest Du unter [{% data variables.product.prodname_education %}](https://education.github.com/). ### Rabatte für gemeinnützige Organisationen und Bibliotheken diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md index 1e33355f63..c4571f3855 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md @@ -19,14 +19,14 @@ When you downgrade or cancel a sponsorship, the change will become effective on {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Sponsoring beenden {% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} +{% data reusables.user_settings.billing_plans %} {% data reusables.sponsors.billing-switcher %} -{% data reusables.user_settings.subscriptions-tab %} 3. Klicke unter „{% data variables.product.prodname_sponsors %}" rechts neben dem unterstützten Open-Source-Mitwirkenden auf {% octicon "triangle-down" aria-label="The down triangle octicon" %} direkt neben dem geleisteten Betrag, dann klicke **Cancel sponsorship** (Sponsoring beenden). ![Schaltfläche „Cancel sponsorship“ (Sponsoring beenden)](/assets/images/help/billing/edit-sponsor-billing.png) 4. Lies die Informationen zum Beenden des Sponsorings, und klicke dann auf **OK**. ![Feld zum Bestätigen der Beendigung](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md index 04189525db..67bac8c0e6 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md @@ -14,6 +14,8 @@ topics: {% data variables.product.product_name %} kann für eine Zahlung, die vor dem Einlösen eines Gutscheins erfolgt, keine Rückerstattung gewähren. Auch kann ein eingelöster Gutschein weder übertragen noch erneut ausgestellt werden, wenn Du ihn auf das falsche Konto anwendest. Vergewissere Dich daher vor dem Einlösen eines Gutscheins, dass Du ihn für das richtige Konto verwendest. +{% data reusables.dotcom_billing.coupon-expires %} + Gutscheine können nicht auf bezahlte Pläne für {% data variables.product.prodname_marketplace %}-Apps angewendet werden. ### Gutschein für Dein persönliches Konto einlösen diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md index d7569b9594..212330c36a 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md @@ -15,6 +15,8 @@ topics: Wenn Sie Ihr {% data variables.product.product_name %}-Abonnement mit einem Gutschein bezahlen und Ihre Zahlungsmethode für keine [anderen bezahlten Funktionen oder Produkte](/articles/about-billing-on-github) auf {% data variables.product.product_name %} benötigen, können Sie Ihre Kreditkarten- oder PayPal-Daten entfernen. +{% data reusables.dotcom_billing.coupon-expires %} + {% tip %} **Tipp:** Wenn Du [Dein Konto auf ein kostenloses Produkt herabstufst](/articles/downgrading-your-github-subscription) und keine anderen bezahlten Funktionen oder Produkte abonniert hast, werden Deine Zahlungsinformationen automatisch entfernt. diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md index 515d6e82b5..f1a573fc48 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md @@ -19,5 +19,6 @@ Wenn Sie Ihr Sponsoring upgraden, wird die Änderung sofort wirksam. {% data reu {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md index 90cba7b880..ac0d865a50 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -59,7 +59,7 @@ Du kannst Deine Organisation von {% data variables.product.prodname_free_team %} #### Nächste Schritte für Organisationen mit {% data variables.product.prodname_ghe_cloud %} -Nach dem Heraufstufen Deiner Organisation auf {% data variables.product.prodname_ghe_cloud %} kannst Du die Identitäts- und Zugriffsverwaltung für Deine Organisation einrichten. Weitere Informationen findest Du unter „[SAML Single Sign-On für Deine Organisation verwalten](/articles/managing-saml-single-sign-on-for-your-organization).“ +Nach dem Heraufstufen Deiner Organisation auf {% data variables.product.prodname_ghe_cloud %} kannst Du die Identitäts- und Zugriffsverwaltung für Deine Organisation einrichten. Weitere Informationen finden Sie unter „[SAML Single Sign-On für Ihre Organisation verwalten](/organizations/managing-saml-single-sign-on-for-your-organization)“. Wenn Du ein Enterprise-Konto mit {% data variables.product.prodname_ghe_cloud %} benutzen möchtest, kontaktiere bitte {% data variables.contact.contact_enterprise_sales %}. Weitere Informationen findest Du unter „[Informationen zu Enterprise-Konten](/articles/about-enterprise-accounts).“ diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md index 0aa338416e..2a55ae7412 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md @@ -20,5 +20,5 @@ You can check how many seats your license includes and how many of them are curr The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png) 5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 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)." +6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." 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 index bed0049e66..70e177e3d9 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### 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.dotcom-saml-explanation %} Weitere Informationen findest Du unter „[Informationen über Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} 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 88737b8598..f13c6e862b 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 @@ -49,7 +49,7 @@ Enterprise-Inhaber können den Zugriff auf Objekte im Besitz von Organisationen {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -Du kannst auch zugelassene IP-Adressen für eine einzelne Organisation konfigurieren. Weitere Informationen findest Du auf „[Zugelassene IP-Adressen für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +Du kannst auch zugelassene IP-Adressen für eine einzelne Organisation konfigurieren. Weitere Informationen findest Du auf „[Zugelassene IP-Adressen für Deine Organisation verwalten](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." #### Eine zulässige IP-Adresse hinzufügen diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md index 2f2e439368..2e9d05bf55 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md @@ -15,7 +15,7 @@ topics: ### Eine Richtlinie für Teamdiskussionen erzwingen -Für alle Organisationen Deines Enterprise-Kontos kannst Du Teamdiskussionen aktivieren oder deaktivieren oder es Inhabern gestatten, diese Einstellung auf Organisationsebene zu verwalten. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)“. +Für alle Organisationen Deines Enterprise-Kontos kannst Du Teamdiskussionen aktivieren oder deaktivieren oder es Inhabern gestatten, diese Einstellung auf Organisationsebene zu verwalten. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions/)“. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 a3c7ad7d04..fdc1330221 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 @@ -39,7 +39,7 @@ Organization owners can invite new members to an organization by email address. While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. -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)." +For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/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 index 2e4c865b47..1bd16faa19 100644 --- 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 @@ -19,7 +19,7 @@ If you use Azure AD as your IdP, you can enable team synchronization for your en {% 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)." +Du kannst auch die Teamsynchronisation für eine einzelne Organisation konfigurieren und verwalten. Weitere Informationen findest Du unter „[Teamsynchronisation für Deine Organisation verwalten](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." ### Vorrausetzungen diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md index ef87f507d1..b4e30d7a2f 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -11,7 +11,7 @@ topics: ### About email restrictions for your enterprise account -When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization. diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md index e9a91bff05..78f8fded60 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -14,7 +14,7 @@ topics: ### 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. Weitere Informationen findest Du unter „[Domänen Deiner Organisation überprüfen](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain).“ +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. Weitere Informationen findest Du unter „[Domänen Deiner Organisation überprüfen](/organizations/managing-organization-settings/verifying-your-organizations-domain).“ After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %} @@ -22,7 +22,7 @@ Organization owners will be able to verify the identity of organization members After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account to approved domains](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)." -Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." ### Verifying your enterprise account's domain 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 13efaf5c6f..e920bbb6af 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 @@ -53,4 +53,4 @@ Wenn Du SAML Single Sign-On für Dein Enterprise-Konto aktivierst, kann jedes En ### Weiterführende Informationen -- „[SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" +- „[SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md index 6a2123b50c..9cbb1cf941 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -14,7 +14,7 @@ topics: Du kannst optional eine Beschreibung, einen Standort, eine Website und eine E-Mail-Adresse für Deine Organisation hinzufügen und wichtige Repositorys am Anfang der Seite anheften. -{% 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 %}. Weitere Informationen findest Du unter „[Domänen Deiner Organisation überprüfen](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain).“ +{% 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 %}. Weitere Informationen findest Du unter „[Domänen Deiner Organisation überprüfen](/organizations/managing-organization-settings/verifying-your-organizations-domain).“ ![Beispiel einer verifizierten Profilseite einer Organisation](/assets/images/help/profile/org_profile_verified.png) {% else %} @@ -23,4 +23,4 @@ Du kannst optional eine Beschreibung, einen Standort, eine Website und eine E-Ma ### Weiterführende Informationen -- „[Über Organisationen](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" +- „[Informationen zu Organisationen](/organizations/collaborating-with-groups-in-organizations/about-organizations)“ 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 9d9214961f..4d876015ed 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 @@ -25,7 +25,7 @@ Commits werden in Deinem Beteiligungsdiagramm angezeigt, falls sie **alle** folg - In the repository's default branch - im `gh-pages`-Branch vorgenommen (für Repositorys mit Projekt-Websites) -Weitere Informationen zu Projektwebsites findest Du unter „[Über {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Außerdem muss **mindestens eine** der folgenden Voraussetzung erfüllt sein: - Du bist ein Repository-Mitarbeiter oder ein Mitglied der Organisation, welcher das Repository gehört. @@ -66,7 +66,7 @@ Es ist nicht möglich, {% data variables.product.product_name %}-Konten generisc #### Commit wurde weder auf dem Standard- noch auf dem `gh-pages`-Branch durchgeführt -Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Falls sich Deine Commits auf einem Nicht-Standard- oder Nicht-`gh-pages`-Branch befinden und sie auf Deine Beiträge angerechnet werden sollen, musst Du eine der folgenden Aktionen durchführen: - [Öffne einen Pull Request](/articles/creating-a-pull-request), damit Deine Änderungen in den Standardbranch oder in den `gh-pages`-Branch zusammengeführt werden. diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md index 0c57c4b83f..e7d2c0a259 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -52,7 +52,7 @@ Du kannst Dein persönliches Benutzerkonto auch direkt in eine Organisation umwa {% tip %} -**Tipp:** Wenn Du ein Benutzerkonto in eine Organisation umwandelst, fügen wir Mitarbeiter von Repositorys, die zum Konto gehören, als *externe Mitarbeiter* zur neuen Organisation hinzu. Du kannst dann *externe Mitarbeiter* dazu einladen, Mitglieder Deiner neuen Organisation zu werden. Weitere Informationen findest Du unter „[Berechtigungsebenen für eine Organisation](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." +**Tipp:** Wenn Du ein Benutzerkonto in eine Organisation umwandelst, fügen wir Mitarbeiter von Repositorys, die zum Konto gehören, als *externe Mitarbeiter* zur neuen Organisation hinzu. Du kannst dann *externe Mitarbeiter* dazu einladen, Mitglieder Deiner neuen Organisation zu werden. Weitere Informationen findest Du unter „[Berechtigungsebenen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)." {% endtip %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index fcd5e4be22..3acc9d34ab 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -56,4 +56,4 @@ Repositorys, die einer Organisation gehören, können feiner abgestufte Zugriffs - „[Berechtigungsebenen für ein Repository eines Benutzerkontos](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)“ - „[Mitarbeiter aus einem persönlichen Repository entfernen](/articles/removing-a-collaborator-from-a-personal-repository)“ - „[Dich selbst aus dem Repository eines Mitarbeiters entfernen](/articles/removing-yourself-from-a-collaborator-s-repository)“ -- „[Mitglieder in Teams organisieren](/articles/organizing-members-into-teams)“ +- „[Mitglieder in Teams organisieren](/organizations/organizing-members-into-teams)“ diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md index a84cf62fd2..9dcf5feaab 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -25,4 +25,4 @@ When you create a new repository on {% data variables.product.product_location % ### Weiterführende Informationen -- "[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)" +- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md index 88e627e4c9..7cba08cbf6 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -13,7 +13,7 @@ Geplante Erinnerungen werden verwendet, um sicherzustellen, dass Benutzer sich a Für bestimmte Ereignisse kannst Du auch Echtzeit-Alarmierung für geplante Erinnerungen einrichten. Echtzeit-Alarme werden in Deinen Slack-Kanal gesendet, sobald ein wichtiges Ereignis stattfindet, beispielsweise wenn Du einem Review zugewiesen wirst. -Du kannst geplante Erinnerungen für persönliche oder für Team-Review-Anfragen für Pull Requests in Organisationen festlegen, in denen Du Mitglied bist. Bevor Du eine geplante Erinnerung für Dich selbst erstellen kannst, muss ein Organisationsinhaber Deinen Slack-Arbeitsbereich autorisieren. Weitere Informationen findest Du unter „[Geplante Erinnerungen für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)." +Du kannst geplante Erinnerungen für persönliche oder für Team-Review-Anfragen für Pull Requests in Organisationen festlegen, in denen Du Mitglied bist. Bevor Du eine geplante Erinnerung für Dich selbst erstellen kannst, muss ein Organisationsinhaber Deinen Slack-Arbeitsbereich autorisieren. Weitere Informationen findest Du unter „[Geplante Erinnerungen für Deine Organisation verwalten](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)." {% data reusables.reminders.scheduled-reminders-limitations %} @@ -50,5 +50,5 @@ Du kannst geplante Erinnerungen für persönliche oder für Team-Review-Anfragen ### Weiterführende Informationen -- „[Geplante Erinnerungen für Deine Organisation verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" -- „[Geplante Erinnerungen für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" +- „[Geplante Erinnerungen für Deine Organisation verwalten](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- „[Geplante Erinnerungen für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md b/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md index 48cdb91112..f2607f6475 100644 --- a/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/de-DE/content/github/site-policy/github-corporate-terms-of-service.md @@ -125,7 +125,7 @@ Die Nutzung des Produkts durch den Kunden darf keine anwendbaren Gesetze verletz Die Nutzung des Dienstes durch den Kunden muss die [GitHub-Richtlinie für angemessene Nutzung](/articles/github-acceptable-use-policies) und die [GitHub-Community-Richtlinien](/articles/github-community-guidelines) erfüllen. Der Kunde darf den Dienst in keiner Rechtsordnung für rechtwidrige, obszöne, beleidigende oder betrügerische Inhalte oder Aktivitäten nutzen. Dazu zählen unter anderem die Befürwortung oder Verursachung von Schäden, die Störung oder Verletzung der Integrität oder Sicherheit von Netzwerken oder Systemen, die Umgehung von Filtern, das Senden nicht angeforderter, beleidigender oder betrügerischer Nachrichten oder von Viren oder Schadcode und die Verletzung von Rechten Dritter. #### 3. Datenschutz -The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Addendum](/github/site-policy/github-data-protection-addendum) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Natürliche oder juristische Personen oder Dienste, die von dem Dienst Daten erfassen, müssen die GitHub-Datenschutzerklärung einhalten, insbesondere im Zusammenhang mit der Erfassung personenbezogener Daten von Benutzern (gemäß Definition in der GitHub-Datenschutzerklärung). Erfasst der Kunde personenbezogene Daten von Benutzern von GitHub, verwendet er diese ausschließlich für den Zweck, für den der externe Benutzer dies erlaubt hat. Der Kunde sorgt für den angemessenen Schutz entsprechender personenbezogener Daten und beantwortet Beschwerden, Aufforderungen zur Löschung und Kontaktverbote von GitHub oder externen Benutzern umgehend. +The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Agreement](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Natürliche oder juristische Personen oder Dienste, die von dem Dienst Daten erfassen, müssen die GitHub-Datenschutzerklärung einhalten, insbesondere im Zusammenhang mit der Erfassung personenbezogener Daten von Benutzern (gemäß Definition in der GitHub-Datenschutzerklärung). Erfasst der Kunde personenbezogene Daten von Benutzern von GitHub, verwendet er diese ausschließlich für den Zweck, für den der externe Benutzer dies erlaubt hat. Der Kunde sorgt für den angemessenen Schutz entsprechender personenbezogener Daten und beantwortet Beschwerden, Aufforderungen zur Löschung und Kontaktverbote von GitHub oder externen Benutzern umgehend. ### D. Haftung für Inhalte, Eigentumsrechte, Lizenzrechte diff --git a/translations/de-DE/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/de-DE/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md new file mode 100644 index 0000000000..2b7424c400 --- /dev/null +++ b/translations/de-DE/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md @@ -0,0 +1,348 @@ +--- +title: GitHub Data Protection Agreement (Non-Enterprise Customers) +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum +versions: + free-pro-team: '*' +--- + +_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._ + +## INTRODUCTION + +The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products. + +In the event of any conflict or inconsistency between the DPA and any other terms in Customer’s agreements with GitHub, the DPA shall prevail. The provisions of the DPA supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Customer Personal Data as defined herein. For clarity, consistent with Clause 10 of the Standard Contractual Clauses in Attachment 1, the Standard Contractual Clauses prevail over any other terms in the DPA. + + +## GITHUB DATA PROTECTION + +### 1. Begriffsbestimmungen + +1.1 The "**Applicable Data Protection Laws**" means certain laws, regulations, regulatory frameworks, or other legislations relating to the processing and use of Customer Personal Data, as applicable to Customer's use of GitHub and the GitHub Service, including: + + a. die EU-Datenschutz-Grundverordnung 2016/679 (**„DSGVO“**) mit allen Durchführungsvorschriften bzw. entsprechenden gleichwertigen nationalen Gesetzen oder Vorschriften, die in Kraft und anwendbar sind, und + + b. The California Consumer Privacy Act of 2018, Cal. Civ. Code §§1798.100 et seq. (**"CCPA"**); and + + c. The UK Data Protection Act 2018 and implementation of GDPR contained therein. + +1.2 "**Controller**," "**Data Subject**," "**Member State**," "**Personal Data**," "**Personal Data Breach**," "**Processing**," "**Processor**," and "**Supervisory Authority**" have the meanings given to them in the Applicable Data Protection Laws. Bei Widersprüchen haben die Bedeutungen nach der DSGVO Vorrang. + +1.3 „**Personenbezogene Daten von Kundenseite**“ sind alle personenbezogenen Daten, für die der Kunde als Verantwortlicher auftritt, und zwar unabhängig davon, ob der Kunde diese zur Verarbeitung durch GitHub bereitstellt oder ob GitHub diese im Zuge der Erfüllung seiner Pflichten nach dieser Vereinbarung generiert. Dazu zählen Daten wie Abrechnungsinformationen, IP-Adressen, Firmen-E-Mail-Adressen und alle sonstigen personenbezogenen Daten, für die der Kunde als Verantwortlicher auftritt. + +1.4 „**Daten in Kunden-Repositorys**“ sind alle Daten und Informationen, die der Kunde in beliebige seiner privaten Repositorys hochlädt oder dort erstellt. + +1.5 Eine „**Datenschutzverletzung**“ ist eine Verletzung des Schutzes personenbezogener Daten oder jede andere bestätigte oder billigerweise vermutete Verletzung der geschützten Daten von Kundenseite. + +1.6 Ein „**Endbenutzer**“ ist eine bestimmte betroffene Person, die die Kontrolle über ein GitHub-Konto hat und den GitHub-Nutzungsbedingungen zugestimmt hat und deren personenbezogene Daten von GitHub übermittelt, gespeichert oder verarbeitet werden. Beispielsweise sind auch alle Mitarbeiter oder Auftragnehmer des Kunden GitHub-Endbenutzer, die ein GitHub-Konto haben. + +1.7 „**Zulässige Zwecke**“ der Datenverarbeitung sind die beschränkten, spezifischen Zwecke der Bereitstellung des Dienstes nach der Vereinbarung, der GitHub-Datenschutzerklärung und diesem Anhang A oder die Zwecke, für die eine betroffene Person die Nutzung personenbezogener Daten von Kundenseite genehmigt hat. + +1.8 „**Geschützte Daten**“ sind alle personenbezogenen Daten von Kundenseite und alle Daten in Kunden-Repositorys, die GitHub im Namen des Kunden im Rahmen der Vereinbarung verarbeitet. + +1.9 "**Sensitive Data**" means any Customer Personal Data revealing racial or ethnic origin; political opinions, religious or philosophical beliefs or trade union membership; processing of genetic data or biometric data for the purposes of uniquely identifying a natural person; data concerning health, a natural person's sex life or sexual orientation; and data relating to offences, criminal convictions, or security measures. + +### 2. Status und Einhaltung von Vorschriften + +#### 2.1 Data Processing. +GitHub acts as a Processor in regard to any Customer Personal Data it receives in connection with the Agreement, and GitHub will process Customer Personal Data only for Permitted Purposes in accordance with Customer's instructions as represented by the Agreement and other written communications. Für den Fall, dass GitHub nicht in der Lage ist, die Anweisungen des Kunden zu erfüllen, beispielsweise aufgrund von Widersprüchen zu den geltenden Datenschutzvorschriften oder wenn die Verarbeitung nach den geltenden Datenschutzvorschriften oder sonstigen gesetzlichen Anforderungen erforderlich ist, teilt GitHub dem Kunden dies mit, insoweit dies zulässig ist. GitHub verarbeitet alle personenbezogenen Daten von Kundenseite in den Vereinigten Staaten oder in der Europäischen Union. Die Unterauftragsverarbeiter von GitHub verarbeiten Daten jedoch ggf. außerhalb der Vereinigten Staaten oder der Europäischen Union. Des Weiteren tritt GitHub als Auftragsverarbeiter für alle Daten in Kunden-Repositorys auf. + +#### 2.2 Data Controllers. +GitHub receives Customer Personal Data both from Customer and directly from Data Subjects who create End User accounts. Der Kunde tritt ausschließlich für die personenbezogenen Daten von Kundenseite als Verantwortlicher auf, die er direkt an GitHub übermittelt. + +#### 2.3 GitHub Compliance; Data Transfers. +GitHub will comply with Applicable Data Protection Laws in relation to the processing of Customer Personal Data. + +All transfers of Customer Personal Data out of the European Union, European Economic Area, United Kingdom, and Switzerland to provide the Service shall be governed by the Standard Contractual Clauses in Attachment 1 (Standard Contractual Clauses). GitHub will abide by the requirements of European Economic Area and Swiss data protection law regarding the collection, use, transfer, retention, and other processing of Customer Personal Data from the European Economic Area, United Kingdom, and Switzerland. All transfers of Customer Personal Data to a third country or an international organization will be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +In addition, GitHub is certified to the EU-U.S. and Swiss-U.S. In addition, GitHub is certified to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-U.S. Privacy Shield Framework as a legal basis for transfers of Personal Data in light of the judgment of the Court of Justice of the EU in Case C-311/18. GitHub agrees to notify Customer if it makes a determination that it can no longer meet its obligation to provide the same level of protection as is required by the Privacy Shield principles. + + +### 3. Datenschutz + +#### 3.1 Purpose Limitation. +GitHub will process and communicate the Protected Data only for Permitted Purposes, unless the Parties agree in writing to an expanded purpose. + +#### 3.2 Data Quality and Proportionality. +GitHub will keep the Customer Personal Data accurate and up to date, or enable Customer to do so. GitHub ergreift wirtschaftlich zumutbare Maßnahmen, um zu gewährleisten, dass im Namen des Kunden erfasste geschützte Daten bezogen auf die Zwecke, für die sie übermittelt und verarbeitet werden, angemessen, relevant und nicht unverhältnismäßig sind. GitHub erfasst im Namen des Kunden keinesfalls absichtlich sensible Daten. Der Kunde erklärt sich einverstanden, dass der GitHub-Dienst nicht für die Speicherung sensibler Daten vorgesehen ist. Lädt der Kunde sensible Daten in den Dienst hoch, muss er DSGVO Artikel 9 oder die entsprechenden Bestimmungen in den geltenden Datenschutzvorschriften erfüllen. + +#### 3.3 Data Retention and Deletion. +Upon Customer's reasonable request, unless prohibited by law, GitHub will return, destroy, or deidentify all Customer Personal Data and related data at all locations where it is stored after it is no longer needed for the Permitted Purposes within thirty days of request. GitHub kann personenbezogene Daten von Kundenseite und zugehörige Daten in dem durch die geltenden Datenschutzvorschriften geforderten Umfang ausschließlich in dem Umfang und für die Dauer aufbewahren, die durch die geltenden Datenschutzvorschriften gefordert werden, wobei GitHub sicherstellt, dass die personenbezogenen Daten von Kundenseite ausschließlich zu dem in den geltenden Datenschutzvorschriften angegebenen und keinem anderen Zweck verarbeitet werden und die personenbezogenen Daten von Kundenseite weiterhin nach den geltenden Datenschutzvorschriften geschützt sind. + +#### 3.4 Data Processing. +GitHub provides the following information, required by Article 28(3) of the GDPR, regarding its processing of Customer's Protected Data: + +a. *Gegenstand und Laufzeit der Verarbeitung* personenbezogener Daten von Kundenseite werden in der Vereinbarung und diesem Anhang festgelegt. + +b. *Art und Zweck der Verarbeitung* personenbezogener Daten von Kundenseite werden in Abschnitt 3.1 dieses Anhangs beschrieben. + +c. Die *Arten verarbeiteter personenbezogener Daten von Kundenseite* werden in der GitHub-Datenschutzerklärung beschrieben und umfassen personenbezogene Daten von Kundenseite wie Benutzernamen, Passwörter, E-Mail-Adressen und IP-Adressen. GitHub verarbeitet zudem Informationen, die für die Kundenkontoabrechnung benötigt werden. Es werden jedoch keine Kreditkarteninformationen verarbeitet oder gespeichert. Der Kunde kann GitHub wahlweise weitere personenbezogene Daten von Kundenseite bereitstellen, beispielsweise seine Profileinstellungen oder in seine GitHub-Repositorys hochgeladene personenbezogene Daten von Kundenseite. + +d. *Die Kategorien betroffener Personen, auf die sich die personenbezogenen Daten von Kundenseite beziehen*, umfassen den Kunden selbst und seine Endbenutzer. + +e. *Die Pflichten und Rechte des Kunden* sind in der Vereinbarung und diesem Anhang festgelegt. + +### 4. Sicherheits- und Auditpflichten + +#### 4.1 Technical and Organizational Security Measures. +Taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, GitHub will implement appropriate technical and organizational measures to ensure a level of security appropriate to the risks, such as against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure or access, presented by processing the Protected Data. GitHub überwacht regelmäßig die Einhaltung dieser Maßnahmen und ergreift über die Laufzeit der Vereinbarung angemessene Schutzmaßnahmen. + +#### 4.2 Incident Response and Breach Notification. +GitHub will comply with Applicable Data Protection Laws. + +#### 4.3 GitHub Personnel. +GitHub represents and warrants that it will take reasonable steps to ensure that all GitHub personnel processing Protected Data have agreed to keep the Protected Data confidential and have received adequate training on compliance with this Addendum and the Applicable Data Protection Laws. + +#### 4.4 Records. +GitHub will maintain complete, accurate, and up to date written records of all categories of processing activities carried out on behalf of Customer containing the information required under the Applicable Data Protection Laws. Insoweit eine entsprechende Unterstützung die Sicherheit von GitHub oder das Recht auf Privatsphäre bestimmter betroffener Personen nicht gefährdet, stellt GitHub dem Kunden diese Verzeichnisse auf berechtigte Anfrage bereit, beispielsweise, um dem Kunden gegenüber die Einhaltung der geltenden Datenschutzvorschriften nachzuweisen. + +#### 4.5 Assistance. +GitHub will provide reasonable assistance to Customer with concerns such as data privacy impact assessments, Data Subject rights requests, consultations with Supervisory Authorities, and other similar matters, in each case solely in relation to the processing of Customer Personal Data and taking into account the nature of processing. + +### 5. Verwendung und Offenlegung geschützter Daten + +#### 5.1 No Use in Marketing. +GitHub will not use the Protected Data for the purposes of advertising third-party content, and will not sell the Protected Data to any third party except as part of a merger or acquisition. + +#### 5.2 GitHub Privacy Statement. +The GitHub Privacy Statement, publicly available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), provides detailed notice of GitHub's privacy and data use practices, including its use of cookies, its dispute resolution process, and further details about GitHub's GDPR compliance. + +### 6. Unterverarbeitung und Weiterübermittlung + +#### 6.1 Protection of Data. +GitHub is liable for onward transfers of Protected Data to its subprocessors, such as its third-party payment processor. In the event that GitHub does transfer the Protected Data to a third-party subprocessor, or GitHub installs, uses, or enables a third party or third-party services to process the Protected Data on GitHub's behalf, GitHub will ensure that the third-party subprocessor is bound by written agreement that requires them to provide at least the same level of confidentiality, security, and privacy protection as is required of GitHub by this DPA and the Applicable Data Protection Laws. + +#### 6.2 Acceptance of GitHub Subprocessors. +Customer authorizes GitHub to appoint (and permit each subprocessor appointed in accordance with this Section 6 to appoint) subprocessors in accordance with Section 6 and any other restrictions in the Agreement. GitHub kann die gegenwärtig beauftragten Unterauftragsverarbeiter ab dem Datum des Inkrafttretens dieses Anhangs weiterhin beauftragen. + +#### 6.3 General Consent for Onward Subprocessing. +Customer provides a general consent for GitHub to engage onward subprocessors, conditional on GitHub's compliance with the following requirements: + +a. Any onward subprocessor must agree in writing to only process data in a country that the European Commission has declared to have an "adequate" level of protection; or to only process data on terms equivalent to the Standard Contractual Clauses, or pursuant to a Binding Corporate Rules approval granted by competent European data protection authorities, or pursuant to compliant and valid EU-US Privacy Shield and Swiss-U.S. Privacy Shield certifications; and + +b. GitHub beschränkt den Zugriff nachgelagerter Unterauftragsverarbeiter auf personenbezogene Daten von Kundenseite auf das für die Leistungserbringung strikt notwendige Maß, und GitHub untersagt dem Unterauftragsverarbeiter die Verarbeitung personenbezogener Daten von Kundenseite zu allen sonstigen Zwecken. + +#### 6.4 Disclosure of Subprocessor Agreements. +GitHub maintains a list of onward subprocessors it has engaged to process Customer Personal Data at [https://docs.github.com/articles/github-subprocessors-and-cookies](/articles/github-subprocessors-and-cookies), including the categories of Customer Personal Data processed, a description of the type of processing the subprocessor performs, and the location of its processing. GitHub stellt dem Kunden diese Liste der Unterauftragsverarbeiter und die Bedingungen der Verarbeitung der personenbezogenen Daten von Kundenseite auf schriftliche Anfrage zur Verfügung. GitHub kann vertrauliche oder geschäftlich sensible Informationen nach den Geheimhaltungspflichten für Unterauftragsverarbeiter entfernen, bevor dem Kunden die Liste und die Bedingungen bereitgestellt werden. Für den Fall, dass GitHub vertrauliche oder sensible Informationen nicht an den Kunden weitergeben kann, vereinbaren die Parteien, dass GitHub alle Informationen zur Verfügung stellt, die es vertretbarerweise im Zusammenhang mit seinen Unterverarbeitungsvereinbarungen bereitstellen kann. + +#### 6.5 Objection to Subprocessors. +GitHub will provide thirty (30) days' prior written notice of the addition or removal of any subprocessor, including the categories listed in Section 6.4, by announcing changes on its site. Lehnt der Kunde die Beauftragung eines neuen Unterauftragsverarbeiters durch GitHub berechtigt ab, muss er GitHub dies umgehend schriftlich mitteilen. GitHub bemüht sich im wirtschaftlich vertretbaren Umgang nach Möglichkeit um eine alternative Lösung für den betreffenden Dienst, um die Datenverarbeitung durch den abgelehnten Unterauftragsverarbeiter zu vermeiden. Für den Fall, dass es GitHub nicht gelingt, eine alternative Lösung zu finden und die Parteien den Konflikt nicht innerhalb von neunzig Tagen lösen, kann der Kunde die Vereinbarung kündigen. + +### 7. Kündigung + +#### 7.1 Aussetzung +In the event that GitHub is in breach of its obligations to maintain an adequate level of security or privacy protection, Customer may temporarily suspend the transfer of all Customer Personal Data or prohibit collection and processing of Customer Personal Data on Customer's behalf until the breach is repaired or the Agreement is terminated. + +#### 7.2 Termination with Cause. +In addition to any termination rights Customer has under the Agreement, Customer may terminate the Agreement without prejudice to any other claims at law or in equity in the event that: + +a. GitHub teilt dem Kunden mit, dass es seine Datenschutzpflichten nicht mehr erfüllen kann. + +b. Die Übermittlung, Erfassung oder Verarbeitung sämtlicher personenbezogener Daten des Kunden wurde nach Abschnitt 7.1 vorübergehend für länger als einen Monat ausgesetzt. + +c. GitHub verstößt in wesentlicher oder dauerhafter Form gegen Zusicherungen oder Garantien nach diesem Anhang. + +d. GitHub ist nicht mehr geschäftlich tätig, wurde aufgelöst oder steht unter Insolvenzverwaltung oder die Abwicklung von GitHub wird in seinem Namen angeordnet. + +e. Der Kunde lehnt nach Abschnitt 6.5 einen Unterauftragsverarbeiter ab und es gelingt GitHub nicht, innerhalb von neunzig Tagen eine alternative Lösung zu finden. + +#### 7.3 Breach. +Failure to comply with the material provisions of this Addendum is considered a material breach under the Agreement. + +#### 7.4 Failure to perform. +In the event that changes in law or regulation render performance of this Addendum impossible or commercially unreasonable, the Parties may renegotiate the Addendum in good faith. Lässt sich die Unmöglichkeit der Erfüllung durch Nachverhandlung nicht beheben oder erreichen die Parteien keine Einigung, können die Parteien die Vereinbarung nach dreißig Tagen kündigen. + +#### 7.5 Notification. +In the event that GitHub determines that it can no longer meet its privacy obligations under this Addendum, GitHub will notify Customer in writing immediately. + +#### 7.6 Modifications. +GitHub may modify this Addendum from time to time as required by the Applicable Data Protection Laws, with thirty days' notice to Customer. + +#### 7.7 Termination Requirements. +Upon Termination, GitHub must: + +a. angemessene und ausreichende Maßnahmen ergreifen, die die Verarbeitung der personenbezogenen Daten von Kundenseite verhindern, + +b. innerhalb von neunzig Tagen ab Kündigung sämtliche personenbezogenen Daten von Kundenseite löschen oder anonymisieren, die GitHub nach Abschnitt 3.3 im Namen des Kunden speichert, und + +c. den Kunden ausreichende Sicherheiten geben, dass GitHub seine Pflichten nach Abschnitt 7.7 erfüllt hat. + +### 8. Haftung für die Datenverarbeitung + +#### 8.1 Limitations. +Except as limited by the Applicable Data Protection Laws, any claims brought under this Addendum will be subject to the terms of the Agreement regarding Limitations of Liability. + +## Attachment 1 – The Standard Contractual Clauses (Processors) +Execution of the applicable agreement by Customer includes execution of this Attachment 1 to the GitHub Data Protection Addendum, which is countersigned by GitHub, Inc. + +In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. + +For the purposes of Article 46(2) of the General Data Protection Regulation (EU 2016/679) for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +#### Clause 1: Definitions +(a) 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in the General Data Protection Regulation (EU 2016/679) on the protection of individuals with regard to the processing of personal data and on the free movement of such data; + +(b) 'the data exporter' means the controller who transfers the personal data; + +(c) 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 45(2) of the General Data Protection Regulation (EU 2016/679); + +(d) 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract; + +(e) 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established; + +(f) 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing. + +#### Clause 2: Details of the transfer +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +#### Clause 3: Third-party beneficiary clause +1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary. + +2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. + +3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law. + +#### Clause 4: Obligations of the data exporter +The data exporter agrees and warrants: + +(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State; + +(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses; + +(c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below; + +(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation; + +(e) that it will ensure compliance with the security measures; + +(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of the General Data Protection Regulation (EU 2016/679); + +(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension; + +(h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information; + +(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and + +(j) that it will ensure compliance with Clause 4(a) to (i). + +#### Clause 5: Obligations of the data importer +The data importer agrees and warrants: + +(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(c) that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred; + +(d) that it will promptly notify the data exporter about: + +(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation, + +(ii) any accidental or unauthorised access, and + +(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so; + +(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + +(f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; + +(g) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter; + +(h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent; + +(i) that the processing services by the subprocessor will be carried out in accordance with Clause 11; and + +(j) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter. + +#### Clause 6: Liability +1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered. + +2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity. The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities. + +3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +#### Clause 7: Mediation and jurisdiction +1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: + +(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; + +(b) to refer the dispute to the courts in the Member State in which the data exporter is established. + +2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. + +#### Clause 8: Cooperation with supervisory authorities +1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law. + +2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law. + +3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5(b). + +#### Clause 9: Governing Law. +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +#### Clause 10: Variation of the contract +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +#### Clause 11: Subprocessing +1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement. + +2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established. + +4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority. + +#### Clause 12: Obligation after the termination of personal data processing services +1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore. + +2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1. + +### Appendix 1 to the Standard Contractual Clauses +Data exporter: Customer is the data exporter. + +**Data importer:** The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects:** Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal information to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following types of data subjects in the Customer Personal Data: + +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Dependents of the above; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users (e.g., customers, clients, patients, visitors, etc.) and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter; +- Stakeholders or individuals who passively interact with data exporter (e.g., because they are the subject of an investigation, research or mentioned in documents or correspondence from or to the data exporter); or +- Professionals with professional privilege (e.g., doctors, lawyers, notaries, religious workers, etc.). + +**Categories of data:** The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Service. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following categories in the Customer Personal Data: +- Authentication data (for example, username, email, password); +- Contact information (for example, email); +- Unique identification numbers and signatures (IP addresses, unique identifier in tracking cookies or similar technology). +- Other unique identifying information. Data subjects may include more data such as real names, avatar images, and other personal information; + +**Special categories of data (if appropriate):** The data importer does not intentionally collect or process any special categories of data in carrying out its services to the data exporter. + +However, because the data importer provides storage services and does not control the categories of data it stores, the data exporter may choose to transfer special categories of data. Consequently, the data exporter is solely responsible for ensuring that it complies with all obligations imposed by applicable laws and regulations relating to the collection and processing of any special categories of data, including obtaining the explicit consent of the data subject prior to processing sensitive personal data. + +**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontractors: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain Customer Personal Data only to deliver the services the data importer has retained them to provide, and they are prohibited from using Customer Personal Data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +**1. Personnel.** Data importer’s personnel will not process Customer Personal Data without authorization. Personnel are obligated to maintain the confidentiality of any Customer Personal Data and this obligation continues even after their engagement ends. + +**2. Data Privacy Contact.** The data privacy officer of the data importer can be reached at the following address: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA + +**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction. + +Signature of GitHub, Inc. appears below. + +Signing the Standard Contractual Clauses, Appendix 1 and Appendix 2 on behalf of the data importer + +![Screen Shot 2020-07-20 at 2 20 29 PM](/assets/images/help/site-policy/docusign-signature.png) + +Lynn Hashimoto, Head of Product & Regulatory Legal + +GitHub, Inc. diff --git a/translations/de-DE/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/de-DE/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md index 70d4eb12aa..fbc0e4753b 100644 --- a/translations/de-DE/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md +++ b/translations/de-DE/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: GitHub Insights and data protection for your organization -intro: '{% data variables.product.prodname_insights %} analyzes your {% data variables.product.prodname_ghe_server %} data. This data could include personal data of individuals in your organization who may have the right to understand how such personal data is being used.' +title: GitHub Insights und Datenschutz für Ihre Organisation +intro: '{% data variables.product.prodname_insights %} analysiert Ihre {% data variables.product.prodname_ghe_server %}-Daten. Diese Daten können personenbezogene Daten von Personen in Ihrer Organisation umfassen, die möglicherweise das Recht haben zu verstehen, wie diese personenbezogenen Daten verwendet werden.' product: '{% data reusables.gated-features.github-insights %}' redirect_from: - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization @@ -9,40 +9,43 @@ redirect_from: - /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization versions: free-pro-team: '*' +topics: + - policy + - legal --- -For more information about the terms that govern {% data variables.product.prodname_insights %}, see your {% data variables.product.prodname_ghe_one %} subscription agreement. +Weitere Informationen zu den Bedingungen für {% data variables.product.prodname_insights %} finden Sie in Ihrer {% data variables.product.prodname_ghe_one %} Abonnementvereinbarung. -For the avoidance of doubt, none of the foregoing information should be considered legal advice provided by {% data variables.product.prodname_dotcom %}. You are responsible for securing your own legal analysis of the information provided herein and for your compliance with privacy and data protection laws. It is up to you whether to use {% data variables.product.prodname_insights %} to process your employees’ and users’ data, and if you do so, you are solely responsible for conducting such processing in compliance with applicable law. +Zur Klarstellung: Keine der vorstehenden Informationen sollte als Rechtsberatung durch {{% data variables.product.prodname_dotcom %} angesehen werden. Sie sind für die Sicherstellung Ihrer eigenen rechtlichen Analyse der hier bereitgestellten Informationen sowie für die Einhaltung der Datenschutzgesetze verantwortlich. Es liegt in Ihrem alleinigen Ermessen, ob Sie {% data variables.product.prodname_insights %} zur Verarbeitung der Daten Ihrer Mitarbeiter bzw. Benutzer verwenden, und wenn Sie dies tun, sind Sie allein dafür verantwortlich, diese Verarbeitung in Übereinstimmung mit dem geltenden Recht durchzuführen. -### The organization’s roles and responsibilities +### Die Rollen und Verantwortlichkeiten der Organisation -When using {% data variables.product.prodname_insights %}, your organization is the data controller because your organization determines whether, how, and why {% data variables.product.prodname_insights %} will process any individual’s personal data. Your organization is solely responsible for ensuring that you are complying with all applicable laws in processing data with {% data variables.product.prodname_insights %}. +Bei der Verwendung {% data variables.product.prodname_insights %} ist Ihre Organisation der Datenverantwortliche, da Ihre Organisation bestimmt, ob, wie und warum {% data variables.product.prodname_insights %} personenbezogene Daten einer Person verarbeitet. Ihre Organisation ist allein dafür verantwortlich, dass Sie alle anwendbaren Gesetze bei der Datenverarbeitung mit {% data variables.product.prodname_insights %} einhalten. -### Data privacy recommendations +### Datenschutzempfehlungen -You have full control over which metrics, reports, repositories, and contributors to include before beginning use of {% data variables.product.prodname_insights %}. The data you process with {% data variables.product.prodname_insights %} can only be pulled from your installation of {% data variables.product.prodname_ghe_server %}. Consider balancing the risks versus the benefits of analyzing personal data. +Sie haben die volle Kontrolle darüber vor Beginn der Verwendung von {% data variables.product.prodname_insights %} zu bestimmen, welche Metriken, Berichte, Repositorys und Mitwirkenden enthalten sein sollen. Die Daten, die Sie mit {% data variables.product.prodname_insights %} verarbeiten, können nur von Ihrer Installation von {% data variables.product.prodname_ghe_server %} abgerufen werden. Berücksichtigen Sie die Ausgewogenheit zwischen den Risiken und den Vorteilen der Analyse personenbezogener Daten. -- **Develop a clear analysis plan**: You must understand clearly what you want to analyze and why, and then consider how {% data variables.product.prodname_insights %} may help you find those answers. +- **Entwickeln Sie einen klaren Analyseplan**: Sie müssen genau verstehen, was Sie analysieren möchten und warum und überlegen Sie dann, wie {% data variables.product.prodname_insights %} Ihnen helfen kann, diese Antworten zu finden. -- **Consider a data protection impact assessment**: If your proposed use of {% data variables.product.prodname_insights %} involves processing personal data, consider completing a data protection impact assessment or otherwise completing formal legal analysis of your planned use. +- **Erwägen Sie eine Folgenabschätzung zum Datenschutz**: Wenn Ihre vorgeschlagene Verwendung von {% data variables.product.prodname_insights %} die Verarbeitung personenbezogener Daten beinhaltet, erwägen Sie, eine Bewertung der Auswirkungen auf den Datenschutz oder eine formelle rechtliche Analyse Ihrer geplanten Nutzung durchzuführen. -### Decide what data to use +### Bestimmen Sie, welche Daten verwendet werden sollen -- **Decide which repositories to include**: Before you start an analysis in {% data variables.product.prodname_insights %}, consider which repositories to include. Administrators can include repositories when adding organizations and can enable and disable repositories at any time. For more information on adding organizations to {% data variables.product.prodname_insights %}, see "[Managing organizations](/insights/installing-and-configuring-github-insights/managing-organizations)." For more information on enabling and disabling repositories, see "[Managing repositories](/insights/installing-and-configuring-github-insights/managing-repositories)." +- **Bestimmen Sie, welche Repositorys enthalten werden sollen**: Bevor Sie mit einer Analyse in {% data variables.product.prodname_insights %} beginnen, überlegen Sie, welche Repositorys enthalten sein sollen. Administratoren können Beim Hinzufügen von Organisationen Repositorys einschließen und Repositorys jederzeit aktivieren und deaktivieren. Weitere Informationen zum Hinzufügen von Organisationen zu {% data variables.product.prodname_insights %} finden Sie unter "[Organisationen verwalten](/insights/installing-and-configuring-github-insights/managing-organizations). Weitere Informationen zum Aktivieren und Deaktivieren von Repositorys finden Sie unter "[Repositorys verwalten](/insights/installing-and-configuring-github-insights/managing-repositories)." -- **Decide which metrics and reports to include**: Administrators can enable and disable metrics and reports available for all users at any time. Administrators control the {% data variables.product.prodname_insights %} data that users have access to in your installation of {% data variables.product.prodname_ghe_server %}. For more information, see "[Managing available metrics and reports](/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports)." +- **Legen Sie fest, welche Metriken und Berichte eingeschlossen werden sollen**: Administratoren können Metriken und Berichte, die für alle Benutzer verfügbar sind, jederzeit aktivieren und deaktivieren. Administratoren bestimmen die {% data variables.product.prodname_insights %}-Daten, auf die Benutzer in Ihrer Installation von {{{% data variables.product.prodname_ghe_server %} Zugriff haben. Weitere Informationen finden Sie unter „[Verwalten verfügbarer Metriken und Berichte](/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports)." -- **Decide which contributors to include**: Administrators can disable a specific contributor’s data from being processed in the metrics and reports. For more information on managing contributor data, see "[Managing contributors and teams](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)." +- **Legen Sie fest, welche Mitwirkenden ** aufgenommen werden sollen: Administratoren können die Verarbeitung der Daten eines bestimmten Mitwirkenden in den Metriken und Berichten deaktivieren. Weitere Informationen zur Datenverwaltung von Mitwirkenden finden Sie unter "[Verwalten von Mitwirkenden und Teams](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)." -### User rights +### Benutzerrechte -Under various data protection regulations, such as the General Data Protection Regulation (GDPR), users may have the right to request exclusion from processing, access, and correction, or to request deletion of their personal data. As the data controller, your organization should evaluate whether a particular user request is valid and, if appropriate, take action to fulfill the request. +Nach verschiedenen Datenschutzbestimmungen, wie der Datenschutz-Grundverordnung (DSGVO), haben Benutzer möglicherweise das Recht, den Ausschluss von der Verarbeitung, dem Zugriff und der Berichtigung ihrer personenbezogenen Daten oder deren Löschung zu verlangen. Als Datenverantwortlicher sollte Ihre Organisation bewerten, ob eine bestimmte Benutzeranfrage gerechtfertigt ist, und gegebenenfalls Maßnahmen ergreifen, um die Anfrage zu erfüllen. -- **Exclusion of processing**: Users may have the right to have their personal data excluded from being processed. Administrators have the ability to remove a contributor’s data from being processed in {% data variables.product.prodname_insights %}, and the resulting reports and metrics will exclude the contributor’s data accordingly. For more information, see "[Managing contributors and teams](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)." +- **Ausschluss der Datenverarbeitung**: Benutzer haben möglicherweise das Recht, dass ihre personenbezogenen Daten von der Verarbeitung ausgeschlossen werden. Administratoren haben die Möglichkeit, die Daten eines Mitwirkenden von der Verarbeitung in {% data variables.product.prodname_insights %} zu entfernen, sodass die resultierenden Berichte und Metriken die Daten des Mitwirkenden entsprechend ausschließen. Weitere Informationen finden Sie unter „[Verwalten von Mitwirkenden und Teams](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)“. -- **Access**: Users may have the right to demand to see what personal data is being processed. Each metric and report has a detailed description of what personal data is being processed. For more information, see "[Metrics available with {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)." Raw data is available through the {% data variables.product.prodname_enterprise %} API. Your organization is responsible for any decisions to process personal data and for fulfilling any such requests. +- **Zugang**: Benutzer haben möglicherweise das Recht, Einsicht in die personenbezogenen Daten zu verlangen, die aktuell verarbeitet werden. Jede Metrik und jeder Bericht enthält eine detaillierte Beschreibung der Verarbeitung personenbezogener Daten. Weitere Informationen finden Sie unter „[Verfügbare Metriken mit {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)“. Rohdaten sind über das {% data variables.product.prodname_enterprise %} API verfügbar. Ihre Organisation ist für alle Entscheidungen zur Verarbeitung personenbezogener Daten und für die Erfüllung solcher Anfragen verantwortlich. -- **Correction and deletion**: Users may have the right to rectify or delete their personal data. The data used in {% data variables.product.prodname_insights %} is derived from the existing data you add to or generate from your {% data variables.product.prodname_ghe_server %} installation. Correction and deletion should follow your organization's existing process to correct and delete data from {% data variables.product.prodname_ghe_server %}. +- **Korrektur und Löschung**: Benutzer haben ggf. das Recht, ihre personenbezogenen Daten zu berichtigen oder zu löschen. Die in {% data variables.product.prodname_insights %} verwendeten Daten werden von den vorhandenen Daten abgeleitet, die Sie in Ihrer {% data variables.product.prodname_ghe_server %} Installation hinzufügen oder generieren. Die Korrektur und Löschung sollten dem bestehenden Prozess Ihrer Organisation zum Korrigieren und Löschen von Daten in {% data variables.product.prodname_ghe_server %}. -- **Transparency regarding processing**: Each metric and report has a detailed description of what personal data is being processed. For more information, see "[Metrics available with {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)." +- **Transparenz in Bezug auf die Verarbeitung**: Jede Metrik und jeder Bericht enthält eine detaillierte Beschreibung, welche persönlichen Daten verarbeitet werden. Weitere Informationen finden Sie unter „[Verfügbare Metriken mit {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)“. diff --git a/translations/de-DE/content/github/site-policy/github-privacy-statement.md b/translations/de-DE/content/github/site-policy/github-privacy-statement.md index f7e3e3ef73..f33bd348e5 100644 --- a/translations/de-DE/content/github/site-policy/github-privacy-statement.md +++ b/translations/de-DE/content/github/site-policy/github-privacy-statement.md @@ -192,7 +192,7 @@ Ebenso können Projekte auf GitHub öffentlich zugängliche personenbezogene Ben #### Organisationen -Sie können durch Ihre Aktionen auf GitHub angeben, dass Sie bereit sind, Ihre personenbezogenen Benutzerdaten zu teilen. Wenn Sie an einer Organisation mitarbeiten oder Mitglied einer Organisation werden, erhalten die Kontoinhaber möglicherweise Ihre personenbezogenen Benutzerdaten. Wenn Sie eine Einladung zu einer Organisation annehmen, werden Sie über die Arten von Informationen informiert, die Besitzer möglicherweise einsehen können (weitere Informationen finden Sie unter [Informationen zur Organisationsmitgliedschaft](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Wenn Sie eine Einladung zu einer Organisation mit [verifizierter Domäne](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain) annehmen, dann können die Eigentümer dieser Organisation Ihre vollständige(n) E-Mail-Adresse(en) innerhalb der verifizierten Domänen dieser Organisation sehen. +Sie können durch Ihre Aktionen auf GitHub angeben, dass Sie bereit sind, Ihre personenbezogenen Benutzerdaten zu teilen. Wenn Sie an einer Organisation mitarbeiten oder Mitglied einer Organisation werden, erhalten die Kontoinhaber möglicherweise Ihre personenbezogenen Benutzerdaten. Wenn Sie eine Einladung zu einer Organisation annehmen, werden Sie über die Arten von Informationen informiert, die Besitzer möglicherweise einsehen können (weitere Informationen finden Sie unter [Informationen zur Organisationsmitgliedschaft](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Wenn Sie eine Einladung zu einer Organisation mit [verifizierter Domäne](/organizations/managing-organization-settings/verifying-your-organizations-domain) annehmen, dann können die Eigentümer dieser Organisation Ihre vollständige(n) E-Mail-Adresse(en) innerhalb der verifizierten Domänen dieser Organisation sehen. Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization. @@ -321,7 +321,7 @@ Im unwahrscheinlichen Fall, dass es zu einem Streit zwischen Ihnen und GitHub ü ### Änderungen an unserer Datenschutzerklärung -GitHub kann unsere Datenschutzerklärung von Zeit zu Zeit ändern, wobei die meisten Änderungen eher geringfügig sein dürften. Wir werden die Benutzer über unsere Website mindestens 30 Tage vor Inkrafttreten der Änderung über wesentliche Änderungen dieser Datenschutzerklärung informieren, indem wir eine Benachrichtigung auf unserer Homepage veröffentlichen oder E-Mails an die primäre E-Mail-Adresse versenden, die in Ihrem GitHub-Konto angegeben ist. Wir werden auch unser [Websiterichtlinien-Repository](https://github.com/github/site-policy/) aktualisieren, das alle Änderungen an dieser Richtlinie nachverfolgt. 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 kann unsere Datenschutzerklärung von Zeit zu Zeit ändern, wobei die meisten Änderungen eher geringfügig sein dürften. Wir werden die Benutzer über unsere Website mindestens 30 Tage vor Inkrafttreten der Änderung über wesentliche Änderungen dieser Datenschutzerklärung informieren, indem wir eine Benachrichtigung auf unserer Homepage veröffentlichen oder E-Mails an die primäre E-Mail-Adresse versenden, die in Ihrem GitHub-Konto angegeben ist. Wir werden auch unser [Websiterichtlinien-Repository](https://github.com/github/site-policy/) aktualisieren, das alle Änderungen an dieser Richtlinie nachverfolgt. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### Lizenz diff --git a/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/de-DE/content/github/site-policy/github-subprocessors-and-cookies.md index be6ede24d7..488ce97a03 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 @@ -13,7 +13,7 @@ topics: - legal --- -Effective date: **January 29, 2021** +Effective date: **April 2, 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). @@ -33,7 +33,6 @@ Wenn wir Ihre Daten an Unterauftragsverarbeiter, wie z. B. unsere Anbieter und D | 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 | -| Monday.com | Plattform für Teamkollaboration und Projektmanagement | Vereinigte Staaten von Amerika | Israel | | Nexmo | SMS-Benachrichtigungsanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Salesforce.com | Customer Relations-Management | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika | | Sentry.io | Application monitoring provider | 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 636085c8a0..1d47a86c8b 100644 --- a/translations/de-DE/content/github/site-policy/index.md +++ b/translations/de-DE/content/github/site-policy/index.md @@ -16,6 +16,7 @@ topics: {% 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-agreement-non-enterprise-customers %} {% link_in_list /global-privacy-practices %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} {% link_in_list /github-sponsors-additional-terms %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md index a984eb8943..f4c4637e62 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -24,7 +24,9 @@ Du kannst für Dein Sponsoring ein Ziel setzen. Weitere Informationen findest Du ### Sponsoring-Stufen -{% data reusables.sponsors.tier-details %} Weitere Informationen findest Du unter „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)", „[{% data variables.product.prodname_sponsors %} für Deine Organisation aufsetzen](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)" und „[Deine Sponsoring-Stufen ändern](/articles/changing-your-sponsorship-tiers)." +{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)." + +It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. ### Sponsoring-Auszahlungen @@ -34,5 +36,9 @@ Du kannst für Dein Sponsoring ein Ziel setzen. Weitere Informationen findest Du Weitere Informationen findest Du unter „[Auszahlungen von {% data variables.product.prodname_sponsors %} verwalten](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)." +### Feedback zu {% data variables.product.prodname_sponsors %} geben + +{% data reusables.sponsors.feedback %} + ### Weiterführende Informationen - „[Häufig gestellte Fragen mit dem {% data variables.product.prodname_sponsors %}-Team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)“ auf {% data variables.product.prodname_blog %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md index 34ad8088c4..b3796e59a3 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -37,7 +37,7 @@ Um für {% data variables.product.prodname_matching_fund %} berechtigt zu sein, ### Feedback zu {% data variables.product.prodname_sponsors %} geben -Das ist nur der Anfang. Wir würden uns über Deinen Input freuen, um sicherzustellen, dass {% data variables.product.prodname_sponsors %} Deine Bedürfnisse auch in der Zukunft erfüllt. Bitte sende uns Dein Feedback oder Deine Anregungen zu, indem Du Dich bei [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors) meldest. +{% data reusables.sponsors.feedback %} ### Weiterführende Informationen - „[Unterstützung von Open-Source-Mitarbeitern](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md index 455a6f445d..cd03e42305 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -15,6 +15,8 @@ Deine Sponsoren können auswählen, ob sie per E-Mail über Deine Arbeit auf dem For sponsored developer accounts, the update will come from your user account's primary email address. Wenn Du den Datenschutz für E-Mail-Adressen für Dein Benutzerkonto aktiviert hast, wird die E-Mail stattdessen von `noreply@github.com` versendet. For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. Weitere Informationen findest Du unter „[Deine Commit-E-Mail-Adresse festlegen](/articles/setting-your-commit-email-address).“ +You can also contact any one-time sponsors who contributed within the last 30 days and enabled updates. + ### Deine Sponsoren kontaktieren {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/index.md index 67db827a10..4066fdb8f2 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/index.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/index.md @@ -25,7 +25,7 @@ topics: {% 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 /managing-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 %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md index 90cd97765f..2ed927f950 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -13,6 +13,12 @@ You can set a funding goal for your sponsored account and share the goal with yo Du kannst Ziele setzen für die Anzahl der Sponsoren, die Du suchst, oder die finanziellen Beiträge, Du Du jeden Monat erzielen möchtest. Du kannst jeweils nur ein Ziel festlegen. Nachdem du ein Ziel erreicht hast, kannst Du ein neues Ziel setzen. +{% note %} + +**Note:** Goals are intended to help people track momentum so only monthly sponsors contribute toward your goal. + +{% endnote %} + ### Setting a goal {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md new file mode 100644 index 0000000000..af3e019b24 --- /dev/null +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md @@ -0,0 +1,45 @@ +--- +title: Managing your sponsorship tiers +intro: 'Du kannst neue Sponsoring-Stufen hinzufügen, oder eine bestehende Stufe bearbeiten oder zurückziehen.' +redirect_from: + - /articles/changing-your-sponsorship-tiers + - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +topics: + - sponsors +--- + +### Informationen zu Sponsoring-Stufen + +{% data reusables.sponsors.tier-details %} + +{% data reusables.sponsors.maximum-tier %} + +### Eine Stufe hinzufügen + +{% 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 %} + +### Editing or retiring a tier + +{% 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 %} + +### Enabling tiers with custom amounts + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.enable-custom-amounts %} + +### Disabling tiers with custom amounts + +You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired. diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 2a7f6ac2bd..b1e9544e12 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -48,6 +48,7 @@ Um {% data variables.product.prodname_sponsors %} als ein einzelner Mitwirkender {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Deine Bankinformationen einreichen diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index d05851fb31..58c45c1286 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -48,6 +48,7 @@ Nachdem {% data variables.product.prodname_dotcom %} Deine Bewerbung überprüft {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Deine Bankinformationen einreichen diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 332fa6725b..e10e3b5e06 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -1,6 +1,6 @@ --- title: Einen Open-Source-Mitwirkenden unterstützen -intro: 'Du kannst monatlich wiederkehrende Zahlungen an einen Entwickler oder eine Organisation machen, welche ein für Dich wichtiges Open-Source-Projekt entwirft, erstellt oder unterhält.' +intro: 'You can make a one-time or monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' redirect_from: - /articles/sponsoring-a-developer - /articles/sponsoring-an-open-source-contributor @@ -24,11 +24,11 @@ You can sponsor an account on behalf of your user account to invest in projects - 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 pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +You use your normal payment method to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% 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 %} +When you sponsor an account the change is effective immediately, unless you are sponsoring on behalf of an organization that pays by invoice. {% data reusables.sponsors.prorated-sponsorship %} Your sponsorship is included in the next scheduled payment to the sponsored account. {% data reusables.sponsors.manage-updates-for-orgs %} @@ -53,6 +53,7 @@ Before you can sponsor an account, you must have a verified email address. Weite - To sponsor a developer, under the developer's name, click **Sponsor**. ![Schaltfläche „Sponsor“ (Unterstützen)](/assets/images/help/profile/sponsor-button.png) - To sponsor an organization, to the right of the organization's name, click **Sponsor**. ![Schaltfläche „Sponsor“ (Unterstützen)](/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) +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index 1a66878f1a..7cc7d5b57f 100644 --- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -1,9 +1,10 @@ --- -title: About the dependency graph +title: Informationen zum Abhängigkeitsdiagramm intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' versions: - free-pro-team: '*' - enterprise-server: '*' + enterprise-server: '<=2.22' +topics: + - repositorys --- ### Dependency graph availability @@ -12,7 +13,7 @@ The dependency graph is available for every{% if currentVersion == "free-pro-tea {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### Informationen zum Abhängigkeitsdiagramm The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: @@ -22,7 +23,8 @@ The dependency graph is a summary of the manifest and lock files stored in a rep When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. {% if currentVersion == "free-pro-team@latest" %} -When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. 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)." +When you create a pull request containing changes to dependencies that targets the default branch, +{% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. 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 %} ### Dependencies included @@ -44,13 +46,13 @@ For public repositories, only public repositories that depend on it or on packag You can use the dependency graph to: - Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} +- View a summary of the dependencies used in your organization's repositories in a single dashboard. Weitere Informationen findest Du unter „[Einblicke für Deine Organisation anzeigen ](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)“.{% endif %} - View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} - See information about vulnerable dependencies in pull requests. 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 %} ### Enabling the dependency graph -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} @@ -60,19 +62,22 @@ You can use the dependency graph to: When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. -### Supported package ecosystems +### Unterstützte Paket-Ökosysteme The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +{% if currentVersion == "free-pro-team@latest" %}The ecosystems listed below are supported for the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot_security_updates %}.{% endif %} +| +{% if currentVersion ver_gt "enterprise-server@2.21" %}The ecosystems listed below are supported for the dependency graph and {% data variables.product.prodname_dependabot_alerts %}.{% endif %} +| Paketmanager | Sprachen | Empfohlene Formate | All supported formats | +| ------------ | ------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET-Sprachen (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`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} @@ -80,10 +85,10 @@ The recommended formats explicitly define which versions are used for all direct {% endnote %} -### Further reading +### Weiterführende Informationen - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- „[Einblicke für Ihre Organisation anzeigen ](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)“ +- „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“ - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index 3cd8f366fb..8d971303fc 100644 --- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -68,7 +68,7 @@ For public repositories, the dependents view shows how the repository is used by Repository administrators can enable or disable the dependency graph for private repositories. -You can also enable or disable the dependency graph 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)." +You can also enable or disable the dependency graph 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](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -109,7 +109,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ### Weiterführende Informationen - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- „[Einblicke für Ihre Organisation anzeigen ](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)“ +- „[Einblicke für Ihre Organisation anzeigen ](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)“ - „[Angreifbare Abhängigkeiten in Ihrem Repository anzeigen und aktualisieren](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)“ - „[Grundlegendes zur Verwendung und zum Schutz Ihrer Daten durch {% data variables.product.product_name %}](/github/understanding-how-github-uses-and-protects-your-data)“ {% endif %} diff --git a/translations/de-DE/content/github/working-with-github-support/submitting-a-ticket.md b/translations/de-DE/content/github/working-with-github-support/submitting-a-ticket.md index 4852d4bd54..efcb6ade67 100644 --- a/translations/de-DE/content/github/working-with-github-support/submitting-a-ticket.md +++ b/translations/de-DE/content/github/working-with-github-support/submitting-a-ticket.md @@ -11,7 +11,7 @@ topics: Wenn Dein Konto ein kostenpflichtiges {% data variables.product.prodname_dotcom %}-Produkt verwendet, kannst Du Dich direkt an {% data variables.contact.github_support %} wenden. Wenn Dein Konto {% data variables.product.prodname_free_user %} für Benutzerkonten und Organisationen verwendet, kannst Du {% data variables.contact.contact_support %} kontaktieren, um Probleme mit Konten, Sicherheit und Missbrauch zu melden. Weitere Informationen findest Du unter „[Über GitHub Support](/github/working-with-github-support/about-github-support)." -Wenn Du {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %} oder den {% data variables.product.premium_support_plan %} verwendest, musst Du Tickets über das {% data variables.contact.enterprise_portal %} einreichen. +If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)." ### Ticket über das {% data variables.contact.support_portal %} einreichen 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 2ad5485226..40b32099bb 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 @@ -33,7 +33,7 @@ Wenn Dein Websiteadministrator den privaten Modus deaktiviert hat, kannst Du auc In folgenden Fällen erhältst Du eine Benachrichtigung: - Du bist der Autor eines Gists. - Jemand erwähnt Dich in einem Gist. -- Du abonnierst einen Gist, indem Du oben im Gist auf **Subscribe** (Abonnieren) klickst. +- You subscribe to a gist, by clicking **Subscribe** at the top of any gist. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} @@ -55,13 +55,15 @@ Gists unterstützen den Gebrauch von geoJSON-Dateien. Diese Karten werden in ein ### Einen Gist erstellen -Du kannst auch eine Textdatei per Drag-and-Drop von Deinem Desktop direkt in den Gist-Editor ziehen. +Follow the steps below to create a gist. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% note %} 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. +Alternatively, you can drag and drop a text file from your desktop directly into the editor. + {% endnote %} {% endif %} @@ -69,7 +71,7 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. 2. Navigieren Sie zu Ihrer {% data variables.gists.gist_homepage %}. 3. Gib eine optionale Beschreibung und einen Namen für Deinen Gist ein. ![Name und Beschreibung des Gists](/assets/images/help/gist/gist_name_description.png) -4. Gib den Text für den Gist in das Gist-Textfeld ein. ![Gist-Textfeld](/assets/images/help/gist/gist_text_box.png) +4. Type the text of your gist into the gist text box. ![Gist-Textfeld](/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 %} diff --git a/translations/de-DE/content/index.md b/translations/de-DE/content/index.md index 8a144eecbf..8a4e4d5adf 100644 --- a/translations/de-DE/content/index.md +++ b/translations/de-DE/content/index.md @@ -13,5 +13,43 @@ featuredLinks: - /github/getting-started-with-github/managing-remote-repositories - /github/working-with-github-pages versions: '*' +children: + - github + - verwalten + - organisationen + - code-security + - actions + - Pakete + - developers + - rest + - graphql + - insights + - discussions + - Communitys + - Seiten + - education + - desktop + - early-access +externalProducts: + cli: + id: cli + name: GitHub CLI + href: 'https://cli.github.com/manual' + external: true + atom: + id: atom + name: Atom + href: 'https://atom.io/docs' + external: true + electron: + id: electron + name: Electron + href: 'https://electronjs.org/docs' + external: true + codeql: + id: codeql + name: 'CodeQL' + href: 'https://codeql.github.com/docs' + external: true --- diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md new file mode 100644 index 0000000000..c0b9b90adc --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -0,0 +1,33 @@ +--- +title: Informationen zu Organisationen +intro: Organisationen sind gemeinsame Konten, in denen Unternehmen und Open-Source-Projekte übergreifend über mehrere Projekte gleichzeitig zusammenarbeiten können. Inhaber und Administratoren können den Mitgliederzugriff auf Daten und Projekte der Organisation mit komplexen Sicherheits- und Administrationsfunktionen verwalten. +redirect_from: + - /articles/about-organizations + - /github/setting-up-and-managing-organizations-and-teams/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} +### Organisationen und Enterprise-Konten + +Mit Enterprise-Konten können Inhaber Richtlinien und Abrechnungen für mehrere {% data variables.product.prodname_dotcom_the_website %}-Organisationen zentral verwalten. + +Bei Organisationen, die einem Enterprise-Konto angehören, wird die Abrechnung auf der Ebene des Enterprise-Kontos verwaltet, und die Abrechnungseinstellungen sind auf der Organisationsebene nicht verfügbar. Enterprise-Inhaber können Richtlinien für alle Organisationen im Enterprise-Konto festlegen oder den Organisationsinhabern erlauben, die Richtlinien auf Organisationsebene festzulegen. Organisationsinhaber können die für Deine Organisation erzwungenen Einstellungen auf der Ebene des Enterprise-Kontos nicht ändern. Wenn Du Fragen zu einer Richtlinie oder einer Einstellung für Deine Organisation hast, wende Dich an den Inhaber Deines Enterprise-Kontos. + +{% data reusables.gated-features.enterprise-accounts %} + +{% data reusables.organizations.org-ownership-recommendation %} Weitere Informationen findest Du unter „[Die Inhaber-Kontinuität für Deine Organisation aufrechterhalten](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." + +### Nutzungsbedingungen und Datenschutz für Organisationen + +Eine Entität, beispielsweise ein Unternehmen, eine gemeinnützige Organisation oder eine Gruppe, kann die Standardnutzungsbedingungen oder die Unternehmensnutzungsbedingungen für ihre Organisation akzeptieren. Weitere Informationen findest Du unter „[Auf Unternehmensnutzungsbedingungen umstellen](/articles/upgrading-to-the-corporate-terms-of-service).“ + +{% endif %} diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md new file mode 100644 index 0000000000..4d4e843bdc --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -0,0 +1,49 @@ +--- +title: Informationen zum Dashboard Deiner Organisation +intro: 'Als Organisationsmitglied kannst Du jederzeit das Dashboard Deiner Organisation aufrufen, um über die neuesten Aktivitäten auf dem Laufenden zu bleiben und Issues und Pull Requests zu beobachten, die Du in der Organisation bearbeitest oder verfolgst.' +redirect_from: + - /articles/about-your-organization-dashboard + - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### Auf das Dashboard Deiner Organisation zugreifen + +{% data reusables.dashboard.access-org-dashboard %} + +### Neueste Aktivitäten finden + +Im Abschnitt „Recent activity" (Neueste Aktivitäten) Deines Newsfeed kannst Du schnell die zuletzt aktualisierten Issues und Pull Requests in Deiner Organisation finden und weiterverfolgen. + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### Repositorys in Deiner Organisation finden + +Über die linke Seitenleiste Deines Dashboards kannst Du auf die wichtigsten Repositorys Deines Unternehmens zugreifen, in denen Du aktiv bist. + +![Liste der Repositorys, in denen Du in Deiner Organisation am aktivsten bist](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) + +### Über Aktivitäten in der Organisation auf dem Laufenden bleiben + +Im Bereich "Alle Aktivitäten" Deines Newsfeed kannst Du Aktualisierungen von anderen Teams und Repositorys in Deiner Organisation ansehen. + +Der Abschnitt "Alle Aktivitäten" zeigt alle aktuellen Aktivitäten in der Organisation, einschließlich Aktivitäten in Repositorys, die Du nicht abonniert hast, und von Personen, denen Du nicht folgst. 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)." + +Beispielsweise werden im Newsfeed der Organisation Aktualisierungen angezeigt, wenn jemand in der Organisation: + - einen neuen Branch erstellt, + - einen Issue oder Pull Request kommentiert, + - einen Pull-Request-Review-Kommentar absendet, + - ein Repository forkt, + - eine Wiki-Seite erstellt, + - Pushes commits.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - Creates a public repository.{% endif %} + +### Weiterführende Informationen + +- „[Informationen zum persönlichen Dashboard](/articles/about-your-personal-dashboard)“ diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md new file mode 100644 index 0000000000..70b5680cde --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -0,0 +1,26 @@ +--- +title: Informationen zum Newsfeed Deiner Organisation +intro: Mithilfe des Newsfeed Deiner Organisation kannst Du über die neuesten Aktivitäten in Bezug auf die Repositorys dieser Organisation auf dem Laufenden bleiben. +redirect_from: + - /articles/news-feed/ + - /articles/about-your-organization-s-news-feed + - /articles/about-your-organizations-news-feed + - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Im Newsfeed einer Organisation sind die neuesten Aktivitäten in Bezug auf die Repositorys dieser Organisation zu sehen. Über den Newsfeed Deiner Organisation kannst Du sehen, wann jemand einen Issue oder Pull Request öffnet, schließt oder zusammenführt, einen Branch erstellt oder löscht, einen Tag oder eine Veröffentlichung erstellt, Kommentare zu einem Issue, Pull Request oder Commit erstellt oder neue Commits an {% data variables.product.product_name %} freigibt. + +### Auf den Newsfeed Deiner Organisation zugreifen + +1. {% data variables.product.signin_link %} bei Ihrem {% data variables.product.product_name %}-Konto. +2. Öffnen Sie Ihr {% data reusables.user_settings.personal_dashboard %}. +3. Klicke auf den Kontextumschalter des Kontos in der oberen linken Ecke der Seite. ![Kontextumschalter-Schaltfläche in 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 %} +![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md new file mode 100644 index 0000000000..547f51491a --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -0,0 +1,34 @@ +--- +title: Auf die Einstellungen Deiner Organisation zugreifen +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 + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings +intro: 'Auf der Seite mit den Einstellungen für das Organisationskonto gibt es mehrere Möglichkeiten, das Konto zu verwalten, beispielsweise über die Einstellungen für die Abrechnung, die Teammitgliedschaft und die Repositorys.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Tipp:** Nur Organisationsinhaber und Abrechnungsmanager können die Abrechnungsinformationen und Kontoeinstellungen für eine Organisation einsehen und ändern. {% 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/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000..4f38e67b24 --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md @@ -0,0 +1,28 @@ +--- +title: Eine Organisation von Grund auf neu erstellen +intro: Erstelle eine Organisation, um fein abgestufte Zugriffsberechtigungen für Repositorys anzuwenden. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /articles/creating-a-new-organization-from-scratch + - /admin/user-management/creating-organizations + - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch +topics: + - organisationen + - teams +--- + +Wenn Du eine Organisation von Grund auf neu erstellst, sind mit ihr keine Repositorys verknüpft. Weitere Informationen zum Hinzufügen von Repositorys zu einer Organisation findest Du unter „[Neues Repository erstellen](/articles/creating-a-new-repository)“ und „[Ein Repository übertragen](/articles/transferring-a-repository).“ + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Folge den Anweisungen, um Deine Organisation zu erstellen. {% 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 %} + +### Weiterführende Informationen + +{% if currentVersion == "free-pro-team@latest" %} +- „[E-Mail-Adresse für die Abrechnung festlegen](/articles/setting-your-billing-email)“{% endif %} +- „[Informationen zu Organisationen](/articles/about-organizations)“ diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/index.md new file mode 100644 index 0000000000..ea493373a5 --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/index.md @@ -0,0 +1,22 @@ +--- +title: Mit Gruppen in Organisationen zusammenarbeiten +intro: Gruppen von Personen können an mehreren Projekten gleichzeitig in Organisationskonten zusammenarbeiten. +redirect_from: + - /articles/creating-a-new-organization-account/ + - /articles/collaborating-with-groups-in-organizations + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000..1114adce3a --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -0,0 +1,50 @@ +--- +title: Organisationseinblicke anzeigen +intro: 'Organisationseinblicke enthalten Daten zu den Aktivitäten, Beiträgen und Abhängigkeiten Deiner Organisation.' +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/viewing-insights-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Alle Mitglieder einer Organisation können Organisationseinblicke anzeigen. Weitere Informationen finden Sie unter „[Berechtigungsebenen für eine Organisation](/articles/permission-levels-for-an-organization)". + +Mithilfe von Einblicken in Organisationsaktivitäten kannst Du besser nachvollziehen, wie die Mitglieder Deiner Organisation {% data variables.product.product_name %} verwenden, um zusammenzuarbeiten und Code zu erstellen. Mithilfe von Abhängigkeits-Einblicken kannst Du die Open-Source-Nutzung Deiner Organisation nachverfolgen, melden und entsprechend darauf reagieren. + +### Einblicke in Organisationsaktivitäten anzeigen + +{% note %} + +**Hinweis:** Einblicke in Organisationsaktivitäten liegen derzeit als Beta-Funktion vor und können sich jederzeit verändern. + +{% endnote %} + +Mithilfe von Einblicken in Organisationsaktivitäten kannst Du wöchentliche, monatliche und jährliche Datenvisualisierungen Deiner gesamten Organisation oder von spezifischen Repositorys anzeigen. Dazu zählen Issue- und Pull-Request-Aktivitäten, die am häufigsten verwendeten Sprachen sowie kumulative Informationen dahingehend, wo Deine Organisationsmitglieder ihre Zeit aufgewendet haben. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Klicke unter dem Namen Deiner Organisation auf {% octicon "graph" aria-label="The bar graph icon" %} **Insights** (Einblicke). ![Klicke auf die Registerkarte „Insights“ (Einblicke) der Organisation](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Wähle optional in der oberen rechten Ecke der Seite die entsprechende Option aus, um Daten für die letzte **1 Woche**, **1 Monat** oder **1 Jahr** anzuzeigen. ![Auswahl des Zeitraums zum Anzeigen der Organisationseinblicke](/assets/images/help/organizations/org-insights-time-period.png) +5. Wähle optional in der oberen rechten Ecke der Seite die entsprechende Option aus, um Daten für bis zu drei Repositorys anzuzeigen, und klicke auf **Apply** (Anwenden). ![Auswahl von Repositorys zum Anzeigen der Organisationseinblicke](/assets/images/help/organizations/org-insights-repos.png) + +### Organisations-Abhängigkeits-Einblicke anzeigen +Mithilfe von Abhängigkeits-Einblicken kannst Du Schwachstellen, Lizenzen und andere wichtige Informationen für die Open-Source-Projekte anzeigen, von denen Deine Organisation abhängig ist. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Klicke unter dem Namen Deiner Organisation auf {% octicon "graph" aria-label="The bar graph icon" %} **Insights** (Einblicke). ![Registerkarte „Insights“ (Einblicke) auf der Haupt-Navigationsleiste der Organisation](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Klicke zum Anzeigen von Abhängigkeiten für diese Organisation auf **Dependencies** (Abhängigkeiten). ![Registerkarte „Dependencies“ (Abhängigkeiten) unter der Haupt-Navigationsleiste der Organisation](/assets/images/help/organizations/org-insights-dependencies-tab.png) +5. Klicke zum Anzeigen von Abhängigkeits-Einblicken für alle Deine {% data variables.product.prodname_ghe_cloud %}-Organisationen auf **My organizations** (Meine Organisationen). ![Schaltfläche „My organizations“ (Meine Organisationen) unter der Registerkarte „Dependencies“ (Abhängigkeiten)](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) +6. Du kannst auf die Ergebnisse in den Diagrammen **Open security advisories** (Offene Sicherheitshinweise) und **Licenses** (Lizenzen) klicken, um nach einem Schwachstellenstatus, nach einer Lizenz oder nach einer Kombination aus beiden zu filtern. ![My organizations vulnerabilities and licenses graphs](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +7. Neben der jeweiligen Schwachstelle können Sie auf {% octicon "package" aria-label="The package icon" %} **dependents** (Abhängige) klicken, um nachzuvollziehen, welche Abhängigen in Ihrer Organisation jede Bibliothek verwenden. ![Angreifbare Abhängige der eigenen Organisationen](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) + +### Weiterführende Informationen + - „[Informationen zu Organisationen](/organizations/collaborating-with-groups-in-organizations/about-organizations)“ + - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" + - „[Die Sichtbarkeit der Einblicke zu den Abhängigkeiten Ihrer Organisation ändern](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)“ + - „[Eine Richtlinie für Einblicke in die Abhängigkeiten in Ihrem Enterprise-Konto erzwingen](/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)“ diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md new file mode 100644 index 0000000000..0fbac67931 --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -0,0 +1,49 @@ +--- +title: Informationen zu Teamdiskussionen +intro: 'Dein Team kann in Diskussionsbeiträgen auf der Teamseite einer Organisation gemeinsam planen, sich gegenseitig auf den neuesten Stand bringen oder über jedes beliebige Thema sprechen.' +redirect_from: + - /articles/about-team-discussions + - /github/building-a-strong-community/about-team-discussions + - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - community +--- + +{% data reusables.organizations.team-discussions-purpose %} + +Jedes Organisationsmitglied kann Beiträge auf der Seite Deines Teams veröffentlichen oder an einer öffentlichen Diskussion teilnehmen. {% data reusables.organizations.team-discussions-permissions %} + +![Registerkarte mit Diskussionen auf einer Teamseite mit öffentlichen und privaten Diskussionen](/assets/images/help/organizations/team-page-discussions-tab.png) + +Du kannst auf jede Teamdiskussion verknüpfen, um sie an anderer Stelle zu referenzieren. Du kannst wichtige Beiträge an die Seite Deines Teams anheften, um sie später schnell wiederzufinden. Weitere Informationen findest Du unter „[Eine Teamdiskussion anheften](/organizations/collaborating-with-your-team/pinning-a-team-discussion).“ + +![Registerkarte mit angehefteten Diskussionen auf einer Teamseite mit angehefteter Diskussion](/assets/images/help/organizations/team-discussions-pinned.png) + +{% data reusables.organizations.team-discussions-default %}-Inhaber können Teamdiskussionen für die gesamte Organisation deaktivieren. Weitere Informationen findest Du unter „[Teamdiskussionen innerhalb Deiner Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization).“ + +### Benachrichtigungen für Teamdiskussionen + +Wenn jemand eine öffentliche Diskussion auf der Seite eines Teams veröffentlicht oder beantwortet, erhalten Mitglieder des Teams und Mitglieder von untergeordneten Teams E-Mail- oder Webbenachrichtigungen. Wenn jemand eine private Diskussion auf der Seite eines Teams veröffentlicht oder beantwortet, erhalten nur Mitglieder des Teams Benachrichtigungen. + +{% tip %} + +**Tipp:** Abhängig von Deinen Benachrichtigungseinstellungen erhältst Du Updates per E-Mail, über die Seite mit den Webbenachrichtigungen auf {% data variables.product.product_name %} oder beide. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." + +{% endtip %} + +Wenn Dein Benutzername in einer Teamdiskussion erwähnt wird, erhältst Du standardmäßig Benachrichtigungen für den Beitrag, in dem Dein Benutzername erwähnt wird, und alle Antworten auf diesen Beitrag. Außerdem erhältst Du standardmäßig Benachrichtigungen für andere Antworten auf einen von Dir beantworteten Beitrag. + +Um Benachrichtigungen für Teamdiskussionen zu deaktivieren, kannst Du einen bestimmten Diskussionsbeitrag kündigen oder Deine Benachrichtigungseinstellungen so ändern, dass Du die Diskussionen eines bestimmten Teams nicht mehr beobachtest oder vollständig ignorierst. Du kannst Benachrichtigungen für einen bestimmten Diskussionsbeitrag abonnieren, auch wenn Du die Diskussionen dieses Teams nicht beobachtest. + +For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)." + +### Weiterführende Informationen + +- „[Informationen zu Unterhaltungen auf {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)“ +- „[Informationen zu Teams](/articles/about-teams)“ +- „[Eine Teamdiskussion erstellen](/organizations/collaborating-with-your-team/creating-a-team-discussion)“ +- „[Eine Teamdiskussion bearbeiten oder löschen](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)“ diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/de-DE/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md new file mode 100644 index 0000000000..8f4a8b0f6a --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md @@ -0,0 +1,30 @@ +--- +title: Eine Teamdiskussion erstellen +intro: 'Jedes Organisationsmitglied kann einen _öffentlichen_ Teamdiskussionsbeitrag erstellen. Um einen _privaten_ Teamdiskussionsbeitrag zu erstellen, musst Du Mitglied des Teams oder Organisationsinhaber sein.' +redirect_from: + - /articles/creating-a-team-discussion + - /github/building-a-strong-community/creating-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - community +--- + +{% data reusables.organizations.team-discussions-permissions %} Weitere Informationen findest Du unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/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. Gib einen Titel für die Teamdiskussion und einen ersten Kommentar ein, um eine Unterhaltung zu starten. ![Neuer Kommentar zur Teamdiskussion](/assets/images/help/projects/team-discussions-comment.png) +7. Optional kannst Du über das Dropdownmenü auswählen, ob Dein Beitrag privat oder öffentlich sein soll. ![Menü für Datenschutzeinstellungen für Teamdiskussionen](/assets/images/help/projects/team-discussions-privacy-menu.png) +8. Klicke auf **Comment** (Kommentieren). ![Schaltfläche zum Erstellen eines neuen Kommentars zur Teamdiskussion](/assets/images/help/projects/team-discussions-comment-button.png) + +### Weiterführende Informationen + + - „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“ + - „[Eine Teamdiskussion bearbeiten oder löschen](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)“ + - „[Eine Teamdiskussion anheften](/organizations/collaborating-with-your-team/pinning-a-team-discussion)“ diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/de-DE/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000..e0f5e840cd --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,28 @@ +--- +title: Eine Teamdiskussion bearbeiten oder löschen +intro: 'Organisationsmitglieder können Diskussionen auf der Seite eines Teams bearbeiten oder löschen. Wenn Du ein Organisationsmitglied bist, kannst Du eine Diskussion bearbeiten oder löschen.' +redirect_from: + - /articles/editing-or-deleting-a-team-discussion + - /github/building-a-strong-community/editing-or-deleting-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - community +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. Klicke neben der Teamdiskussion, die Du bearbeiten oder löschen möchtest, auf {% octicon "kebab-horizontal" aria-label="The edit icon" %}. +7. Klicke auf **Edit** (Bearbeiten). Optional klicke auf **Delete** (Löschen). ![Schaltfläche „Edit team discussion" (Bearbeiten der Teamdiskussion)](/assets/images/help/projects/edit-team-discussions-button.png) +8. Ändere nach Bedarf den Titel der Teamdiskussion und den Kommentar, und klicke auf **Update comment** (Kommentar aktualisieren). ![Schaltfläche „Update comment“ (Kommentar aktualisieren)](/assets/images/help/projects/update-comment-button.png) + +### Weiterführende Informationen + + - „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“ + - „[Eine Teamdiskussion erstellen](/organizations/collaborating-with-your-team/creating-a-team-discussion)“ + - „[Eine Teamdiskussion anheften](/organizations/collaborating-with-your-team/pinning-a-team-discussion)“ diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/index.md b/translations/de-DE/content/organizations/collaborating-with-your-team/index.md new file mode 100644 index 0000000000..cfc434065f --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-your-team/index.md @@ -0,0 +1,19 @@ +--- +title: Mit Deinem Team zusammenarbeiten +intro: 'Innerhalb einer Organisation kann Dein Team mithilfe von Teamdiskussionen über mehrere Projekte hinweg zusammenarbeiten.' +redirect_from: + - /articles/collaborating-with-your-team + - /github/building-a-strong-community/collaborating-with-your-team + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - community +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/de-DE/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md new file mode 100644 index 0000000000..24801b77b9 --- /dev/null +++ b/translations/de-DE/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +title: Eine Teamdiskussion anheften +intro: 'Du kannst wichtige Diskussionen auf den Teamseiten Deiner Organisation anheften, damit sie schneller zu finden sind, und angeheftete Diskussionen, die nicht mehr relevant sind, wieder entfernen.' +redirect_from: + - /articles/pinning-a-team-discussion + - /github/building-a-strong-community/pinning-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - community +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +5. Klicke neben der Teamdiskussion, die Du anheften möchtest, auf {% octicon "pin" aria-label="The pin icon" %}. Du kannst eine angeheftete Diskussion auch wieder entfernen, indem Du auf das Symbol klickst. ![Eine Diskussion anheften](/assets/images/help/projects/pin-discussion-button.png) + +### Weiterführende Informationen + + - „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“ + - „[Eine Teamdiskussion erstellen](/organizations/collaborating-with-your-team/creating-a-team-discussion)“ + - „[Eine Teamdiskussion bearbeiten oder löschen](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)“ diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000..48cc4ddbc9 --- /dev/null +++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,26 @@ +--- +title: Informationen zur Zwei-Faktor-Authentifizierung und zu SAML Single-Sign-On +intro: Administratoren von Organisationen können sowohl SAML Single-Sign-On als auch die Zwei-Faktor-Authentifizierung aktivieren, um zusätzliche Authentifizierungsmaßnahmen für ihre Organisationsmitglieder hinzuzufügen. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-two-factor-authentication-and-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Die Zwei-Faktor-Authentifizierung (2FA) bietet die grundlegende Authentifizierung für Organisationsmitglieder. Durch die Aktivierung der Zwei-Faktor-Authentifizierung begrenzen Organisationsadministratoren die Wahrscheinlichkeit, dass das {% data variables.product.product_name %}-Konto eines Mitglieds kompromittiert werden könnte. Weitere Informationen zur Zwei-Faktor-Authentifizierung findest Du unter „[Informationen zur Zwei-Faktor-Authentifizierung](/articles/about-two-factor-authentication).“ + +Um zusätzliche Authentifizierungsmaßnahmen hinzuzufügen, können Organisationsadministratoren außerdem [SAML Single-Sign-On (SSO) aktivieren](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), sodass Organisationsmitglieder Single-Sign-On für den Zugriff auf eine Organisation verwenden müssen. Weitere Informationen zu SAML SSO findest Du unter „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on).“ + +Wenn sowohl die Zwei-Faktor-Authentifizierung als auch SAML SSO aktiviert sind, müssen Organisationsmitglieder wie folgt vorgehen: +- Sich mit der Zwei-Faktor-Authentifizierung bei ihrem {% data variables.product.product_name %}-Konto anmelden +- Mit Single Sign-On auf die Organisation zugreifen +- Ein autorisiertes Token für den API- oder Git-Zugriff verwenden und Single-Sign-On zur Autorisierung des Tokens verwenden + +### Weiterführende Informationen + +- „[SAML Single Sign-On für Deine Organisation erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization)“ diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md new file mode 100644 index 0000000000..f305a023bf --- /dev/null +++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -0,0 +1,16 @@ +--- +title: Zugriff auf Deine Organisation mit SAML Single Sign-On gewähren +intro: 'Organisationsadministratoren können den Zugriff auf ihre Organisation mit SAML Single-Sign-On gewähren. Dieser Zugriff kann Organisationsmitgliedern, Bots und Dienstkonten ermöglicht werden.' +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000..d9025473fb --- /dev/null +++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,25 @@ +--- +title: Bots und Dienstkonten mit SAML Single-Sign-On verwalten +intro: Organisationen, für die SAML Single-Sign-On aktiviert ist, können den Zugriff von Bots und Dienstkonten beibehalten. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Um den Zugriff für Bots und Dienstkonten beizubehalten, können die Organisationsadministratoren SAML Single Sign-On für ihre Organisation [aktivieren](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), aber **nicht** [erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization). Wenn Du SAML Single Sign-On für Deine Organisation erzwingen musst, kannst Du eine externe Identität für den Bot oder das Dienstkonto bei Deinem Identitätsanbieter (IdP) erstellen. + +{% warning %} + +**Hinweis:** Wenn Du SAML Single Sign-On für Deine Organisation erzwingst und **keine** externe Identitäten für Bots und Dienstkonten bei Deinem IdP eingerichtet hast, werden die Bots und Dienstkonten aus Deiner Organisation entfernt. + +{% endwarning %} + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000..9ab2964305 --- /dev/null +++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,64 @@ +--- +title: SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten +intro: 'Du kannst die verknüpfte Identität, aktive Sitzungen und autorisierte Anmeldeinformationen eines Organisations-Mitglieds ansehen und widerrufen.' +permissions: Organisationsinhaber können den SAML-Zugriff eines Mitglieds auf eine Organisation ansehen und verwalten. +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +### Über SAML Zugriff auf Deine Organisation + +Wenn Du SAML Single Sign-On für Deine Organisation aktivierst, kann jedes Organisations-Mitglied seine externe Identität auf Deinem Identitätsanbieter (IdP) mit seinem bestehenden {% data variables.product.product_name %}-Konto verknüpfen. Um auf die Ressourcen Deiner Organisation auf {% data variables.product.product_name %} zuzugreifen, muss das Mitglied eine aktive SAML-Sitzung in seinem Browser haben. Um über API und Git auf die Ressourcen Deiner Organisation zugreifen zu können, muss das Mitglied ein persönliches Zugriffstoken oder einen SSH-Schlüssel verwenden, den das Mitglied für die Verwendung mit Deiner Organisation autorisiert hat. + +Du kannst die verknüpfte Identität, die aktiven Sitzungen und die autorisierten Anmeldeinformationen auf der gleichen Seite anzeigen und widerrufen. + +### Eine verknüpfte Identität anschauen und widerrufen + +{% 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 %} + +### Eine aktive SAML-Sitzung ansehen und widerrufen + +{% 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 %} + +### Autorisierte Anmeldeinformationen anschauen und widerrufen + +{% 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 %} + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ +- „[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)" diff --git a/translations/de-DE/content/organizations/index.md b/translations/de-DE/content/organizations/index.md new file mode 100644 index 0000000000..dad2637c88 --- /dev/null +++ b/translations/de-DE/content/organizations/index.md @@ -0,0 +1,32 @@ +--- +title: Organisationen und Teams +shortTitle: Organisationen +intro: Arbeite an zahlreichen Projekten zusammen, verwalte den Zugriff auf Projekte und Daten, und passe die Einstellungen für Deine Organisation an. +redirect_from: + - /articles/about-improved-organization-permissions/ + - /categories/setting-up-and-managing-organizations-and-teams + - /github/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% link_with_intro /collaborating-with-groups-in-organizations %} +{% link_with_intro /managing-membership-in-your-organization %} +{% link_with_intro /managing-peoples-access-to-your-organization-with-roles %} +{% link_with_intro /organizing-members-into-teams %} +{% link_with_intro /collaborating-with-your-team %} +{% link_with_intro /managing-access-to-your-organizations-repositories %} +{% link_with_intro /managing-access-to-your-organizations-project-boards %} +{% link_with_intro /managing-access-to-your-organizations-apps %} +{% link_with_intro /managing-organization-settings %} +{% link_with_intro /restricting-access-to-your-organizations-data %} +{% link_with_intro /keeping-your-organization-secure %} +{% link_with_intro /managing-saml-single-sign-on-for-your-organization %} +{% link_with_intro /granting-access-to-your-organization-with-saml-single-sign-on %} +{% link_with_intro /managing-git-access-to-your-organizations-repositories %} +{% link_with_intro /migrating-to-improved-organization-permissions %} diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md new file mode 100644 index 0000000000..f1af344c8e --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md @@ -0,0 +1,24 @@ +--- +title: Schutz Deiner Organisation +intro: 'Organisationsinhabern stehen mehrere Funktionen zur Verfügung, mit denen sie ihre Projekte und Daten schützen können. 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.' +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure + - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000..bae80f12a6 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Verwaltung erlaubter IP-Adressen für Deine Organisation +intro: Du kannst den Zugriff auf die Objekte Deiner Organisation einschränken, indem Du eine Liste von IP-Adressen konfigurierst, die zu einer Verbindung berechtigt sind. +product: '{% data reusables.gated-features.allowed-ip-addresses %}' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber können erlaubte IP-Adressen für eine Organisation verwalten. + +### Informationen zu zulässigen IP-Adressen + +Du kannst den Zugriff auf Organisations-Objekte beschränken, indem Du eine Genehmigungsliste für bestimmte IP-Adressen konfigurierst. {% 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 %} + +Du kannst erlaubte IP-Adressen auch für die Organisationen in einem Enterprise-Konto konfigurieren. For more information, see {% if currentVersion == "github-ae@latest" %}"[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." {% else %}"[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)."{% endif %} + +### Eine zulässige IP-Adresse hinzufügen + +{% 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 %} + +### Zulässige IP-Adressen aktivieren + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +3. Wähle unter „IP allow list“ (Liste der zulässigen IP-Adressen) **Enable IP allow list** (Liste der zulässigen IP-Adressen aktivieren) aus. ![Kontrollkästchen, um IP-Adressen zuzulassen](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) +4. Klicke auf **Save** (Speichern). + +### Eine zulässige IP-Adresse bearbeiten + +{% 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. Klicke auf **Update** (Aktualisieren). + +### Eine zulässige IP-Adresse löschen + +{% 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 %} + +### {% data variables.product.prodname_actions %} mit einer IP-Zulassungsliste verwenden + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-actions.ip-allow-list-hosted-runners %} + +{% else %} + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +{% endif %} diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000..0b0be0d638 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,143 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### 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. {% 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 %} + +### 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 all security and analysis features for the repositories in your organization. + +{% if currentVersion == "free-pro-team@latest" %}If your organization belongs to an enterprise with 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. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %}If you have 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. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} + +{% if currentVersion == "github-ae@latest" %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features.{% 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)." +2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + !["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 %} + {% if currentVersion == "github-ae@latest" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +3. Optionally, enable the feature by default for new repositories in your organization. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + !["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 %} +4. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% endif %} + {% if currentVersion == "github-ae@latest" %} +3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} + + {% data reusables.security.displayed-information %} + +### 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)." +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% if currentVersion == "github-ae@latest" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Allowing {% data variables.product.prodname_dependabot %} to access private dependencies + +{% 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. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. 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. + +If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." + +To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository: + +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 "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**. ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. Start typing the name of the repository you want to allow. ![Add repositories button](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Click the repository you want to allow. + +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. !["X" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization + +You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization. + +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. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. The size of your license is shown for organization-level licenses. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)." +1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}. +1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}. + +{% note %} + +**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning. + +{% endnote %} + +{% endif %} + +### Weiterführende Informationen + +- "[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 %}{% if currentVersion != "github-ae@latest" %} +- "[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)"{% endif %} diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..098a8646c6 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Auf Erzwingung der Zwei-Faktor-Authentifizierung in Deiner Organisation vorbereiten +intro: 'Bevor Du die Zwei-Faktor-Authentifizierung (2FA) vorschreibst, kannst Du die Benutzer über die anstehende Änderungen informieren und überprüfen, wer die 2FA bereits nutzt.' +redirect_from: + - /articles/preparing-to-require-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +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. + +Wenn Du für Deine Organisation die Zwei-Faktor-Authentifizierung vorschreibst, werden Mitglieder, externe Mitarbeiter und Abrechnungsmanager (einschließlich Bot-Konten), die keine 2FA verwenden, aus der Organisation entfernt und verlieren den Zugriff auf die Repositorys der Organisation. Gleichzeitig verlieren sie auch den Zugriff auf ihre Forks der privaten Repositorys der Organisation. + +Bevor Du die 2FA in Ihrer Organisation vorschreiben, empfehlen wir Dir, Folgendes zu tun: + - [Aktivieren 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) für Dein persönliches Konto + - Bitte Benutzer in Deiner Organisation darum, 2FA für ihre Konten einzurichten + - Überprüfe, ob [Benutzer in Deiner Organisation 2FA aktiviert haben](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/) + - Warne die Benutzer, dass nach der Aktivierung von 2FA diejenigen ohne 2FA automatisch aus der Organisation entfernt werden diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..7c61a34327 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,80 @@ +--- +title: Zwei-Faktor-Authentifizierung in Deiner Organisation erzwingen +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.' +redirect_from: + - /articles/requiring-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +### 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)." + +{% if currentVersion == "free-pro-team@latest" %} + +You can also require two-factor authentication for organizations in an enterprise. 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#requiring-two-factor-authentication-for-organizations-in-your-enterprise-account)." + +{% endif %} + +{% warning %} + +**Warnungen:** + +- 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. Gleichzeitig verlieren sie auch den Zugriff auf ihre Forks der privaten Repositorys der Organisation. Du kannst [die Zugriffsberechtigungen und Einstellungen dieser Personen wiederherstellen](/articles/reinstating-a-former-member-of-your-organization), wenn sie die Zwei-Faktor-Authentifizierung für ihre persönlichen Konten innerhalb einer Frist von drei Monaten ab ihrer Entfernung aus der Organisation aktivieren. +- 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. +- Falls Du der einzige Inhaber einer Organisation bist, bei der die Zwei-Faktor-Authentifizierung verlangt wird, kannst Du die 2FA für Dein persönliches Konto nicht deaktivieren, ohne gleichzeitig die Erzwingung der Zwei-Faktor-Authentifizierung für die Organisation aufzuheben. + +{% endwarning %} + +{% data reusables.two_fa.auth_methods_2fa %} + +### Vorrausetzungen + +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 %}. Weitere Informationen findest Du unter „[Dein Konto durch Zwei-Faktor-Authentifizierung (2FA) schützen](/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. Weitere Informationen findest Du unter „[Überprüfen, ob die Benutzer Deiner Organisation die 2FA aktiviert haben](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled).“ + +### Zwei-Faktor-Authentifizierung in Deiner Organisation erzwingen + +{% 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. Wenn Mitglieder und externe Mitarbeiter aus Deiner Organisation entfernt werden, weil sie keine 2FA verwenden, empfehlen wir Dir, diesen Personen eine Einladung zur Wiedereinsetzung ihrer bisherigen Privilegien und Zugriffsrechte für Deine Organisation zu senden. Vor der Annahme dieser Einladung müssen sie allerdings die Zwei-Faktor-Authentifizierung aktivieren. +{% endif %} + +### Aus Deiner Organisation entfernte Personen anzeigen + +Wenn Sie wissen möchten, welche Personen automatisch aus Ihrer Organisation entfernt wurden, weil sie Ihrer Anforderung der Aktivierung der Zwei-Faktor-Authentifizierung nicht Folge leisteten, können Sie [das Auditprotokoll Ihrer Organisation nach Personen durchsuchen](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log), die aus der Organisation entfernt wurden. Die im Auditprotokoll aufgezeichneten Ereignisse geben an, ob eine Person aufgrund der Nichterfüllung der 2FA-Anforderung aus der Organisation entfernt wurde. + +![Ereignis im Auditprotokoll zur Entfernung eines Benutzers aufgrund der Nichterfüllung der 2FA-Anforderung](/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. Gib Deine Suchabfrage ein. Verwende für Deine Suche die folgenden Abfragen: + - für die Suche nach entfernten Organisationsmitgliedern die Suchabfrage `action:org.remove_member` + - Outside collaborators removed, use `action:org.remove_outside_collaborator` in your search query{% if currentVersion == "free-pro-team@latest" %} + - für die Suche nach entfernten Abrechnungsmanagern die Suchabfrage `action:org.remove_billing_manager`{% endif %} + + Die Suche nach Personen, die aus Deiner Organisation entfernt wurden, kannst Du auch durch Angabe eines [Zeitfensters](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) in der Suchabfrage eingrenzen. + +### Entfernten Organisationsmitgliedern und externen Mitarbeitern den Wiedereintritt zu Deiner Organisation erleichtern + +Organisationsmitglieder und externe Mitarbeiter, die aufgrund der Erzwingung der Zwei-Faktor-Authentifizierung aus Ihrer Organisation entfernt werden, erhalten eine E-Mail-Benachrichtigung zu ihrer Entfernung. In dieser E-Mail wird ihnen empfohlen, die 2FA für ihr persönliches Konto zu aktivieren und anschließend bei einem Organisationsinhaber ihren Wiederbeitritt zur Organisation zu veranlassen. + +### Weiterführende Informationen + +- „[Überprüfen, ob die Benutzer Deiner Organisation die 2FA aktiviert haben](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)“ +- „[Dein Konto durch die Zwei-Faktor-Authentifizierung (2FA) schützen](/articles/securing-your-account-with-two-factor-authentication-2fa)“ +- „[Ehemaliges Mitglied Deiner Organisation wieder einsetzen](/articles/reinstating-a-former-member-of-your-organization)“ +- „[Zugriff eines ehemaligen externen Mitarbeiters auf Deine Organisation wieder einsetzen](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)“ diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000..a5cde4cce1 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,31 @@ +--- +title: E-Mail-Benachrichtigungen auf eine genehmigte Domäne beschränken +intro: 'Um zu verhindern, dass Organisationsinformationen an persönliche Konten weitergegeben werden, können Organisationsinhaber E-Mail-Benachrichtigungen zur Organisationsaktivität auf eine verifizierte Domäne beschränken.' +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +### 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. Weitere Informationen findest Du unter „[Domäne Deiner Organisation verifizieren](/articles/verifying-your-organization-s-domain).“ + +Externe Mitarbeiter unterliegen nicht den Einschränkungen für E-Mail-Benachrichtigungen für verifizierte Domänen. Weitere Informationen zu externen Mitarbeitern findest Du unter „[Berechtigungsebenen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/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)." + +### E-Mail-Benachrichtigungen auf eine genehmigte Domäne beschränken + +{% 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. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000..5b3baff529 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,643 @@ +--- +title: Auditprotokoll Deiner Organisation überprüfen +intro: 'Im Auditprotokoll können die Administratoren einer Organisation die von den Mitgliedern der Organisation durchgeführten Aktionen überprüfen. Es enthält Details wie den Ausführenden, die Art und den Zeitpunkt der Aktionen.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-the-audit-log-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### Zugriff auf das Auditprotokoll + +The audit log lists events triggered by activities that affect your organization within the last 90 days. Nur Organisationsinhaber können auf das Auditprotokoll einer Organisation zugreifen. + +{% 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 %} + +### Auditprotokoll durchsuchen + +{% data reusables.audit_log.audit-log-search %} + +#### Suche nach der Art der durchgeführten Aktion + +Zur Suche nach bestimmten Ereignissen verwende in Deiner Abfrage den Qualifizierer `action`. Die im Auditprotokoll aufgezeichneten Aktionen unterteilen sich in die folgenden Kategorien: + +| Kategoriename | Beschreibung | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`Konto`](#account-category-actions) | Contains all activities related to your organization account. | +| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| [`Abrechnung`](#billing-category-actions) | Contains all activities related to your organization's billing. | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | | +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization. | +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." | +| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. | +| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} +| [`discussion_post (Diskussionsbeitrag)`](#discussion_post-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Diskussionen auf einer Teamseite. | +| [`discussion_post_reply (Antwort auf Diskussionsbeitrag)`](#discussion_post_reply-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Antworten auf Diskussionen auf einer Teamseite. | +| [`Hook`](#hook-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Webhooks. | +| [`integration_installation_request (Antrag zur Installation einer Integration)`](#integration_installation_request-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Anfragen von Organisationsmitgliedern an Organisationsinhaber zur Genehmigung von Integrationen zur Verwendung innerhalb der Organisation. | +| [`Issue`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} +| [`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) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |{% endif %} +| [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`Pakete`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Umfasst alle Aktivitäten in Verbindung mit der Zahlungsmethode Deiner Organisation für GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Umfasst alle Aktivitäten in Verbindung mit dem Profilbild Deiner Organisation. | +| [`project (Projekt)`](#project-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Projektboards. | +| [`protected_branch`](#protected_branch-category-actions) | Umfasst alle Aktivitäten in Verbindung mit geschützten Branches. | +| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | +| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} | | +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| [`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) | Umfasst alle Ereignisse in Verbindung mit Sponsorenschaltflächen (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“).{% endif %} +| [`Team`](#team-category-actions) | Umfasst alle Aktivitäten in Verbindung mit Teams in Ihrer Organisation. | +| [`team_discussions`](#team_discussions-category-actions) | Umfasst Aktivitäten in Verbindung mit der Verwaltung der Teamdiskussionen für eine Organisation. | + +Mit den folgenden Suchbegriffen kannst Du nach bestimmten Aktionsgruppen suchen. Ein Beispiel: + + * `action:team` findet alle Ereignisse innerhalb der Kategorie „Team“. + * `-action:hook` schließt alle Ereignisse aus der Kategorie „Webhook “ aus. + +Each category has a set of associated actions that you can filter on. Ein Beispiel: + + * `action:team.create` findet alle Ereignisse in Verbindung mit der Erstellung eines Teams. + * `-action:hook.events_changed` schließt alle Ereignisse in Verbindung mit geänderten Webhook-Ereignissen aus. + +#### Suche nach dem Zeitpunkt der Aktion + +Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +Ein Beispiel: + + * `created:2014-07-08` findet alle Ereignisse vom 8. Juli 2014. + * `created:>=2014-07-08` findet alle Ereignisse vom und nach dem 8. Juli 2014. + * `created:<=2014-07-08` findet alle Ereignisse vom und vor dem 8. Juli 2014. + * `created:2014-07-01..2014-07-31` findet alle Ereignisse im Juli 2014. + +Das Auditprotokoll enthält Daten der letzten 90 Tage. Mit dem Kennzeichner `created` können Sie jedoch auch nach früheren Ereignissen suchen. + +#### Suche nach Standort + +Using the qualifier `country`, you can filter events in the audit log based on the originating country. Hierzu verwenden Sie den zweistelligen Kurzcode oder den vollständigen Namen des Landes. Ländernamen mit Leerzeichen müssen in Anführungszeichen eingeschlossen sein. Ein Beispiel: + + * `country:de` findet alle Ereignisse, die in Deutschland aufgetreten sind. + * `country:Mexico` findet alle Ereignisse, die in Mexiko aufgetreten sind. + * `country:"United States"` findet alle Ereignisse, die in den USA aufgetreten sind. + +{% if currentVersion == "free-pro-team@latest" %} +### Auditprotokoll exportieren + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### Using the audit log API + +You can interact with the audit log using the GraphQL API{% if currentVersion == "free-pro-team@latest" %} or the REST API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Using the GraphQL API + +{% endif %} + +{% note %} + +**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +To ensure a secure IP and maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audit-log-api-info %} + +{% if currentVersion == "free-pro-team@latest" %} +Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)." +{% endif %} + +Die GraphQL-Antwort kann Daten für bis zu 90 bis 120 Tage beinhalten. + +Sie können beispielsweise eine GraphQL-Anforderung erstellen, die alle Ihrer Organisation neu hinzugefügten Organisationsmitglieder zurückgibt. For more information, see the "[GraphQL API Audit Log](/v4/interface/auditentry/)." + +{% if currentVersion == "free-pro-team@latest" %} + +#### Using the REST API + +{% note %} + +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. + +{% endnote %} + +To ensure a secure IP and maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audit-log-api-info %} +* Git events, such as cloning, fetching, and pushing + +{% data reusables.audit_log.audit-log-git-events-retention %} + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endif %} + +### Audit log actions + +An overview of some of the most common actions that are recorded as events in the audit log. + +{% if currentVersion == "free-pro-team@latest" %} + +#### `account` category actions + +| Aktion | Beschreibung | +| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing_plan_change` | Wird ausgelöst, wenn sich der [Abrechnungszeitraum](/articles/changing-the-duration-of-your-billing-cycle) einer Organisation ändert. | +| `plan_change` | Wird ausgelöst, wenn sich das [Abonnement](/articles/about-billing-for-github-accounts) einer Organisation ändert. | +| `pending_plan_change` | Wird ausgelöst, wenn der Inhaber oder Abrechnungsmanager einer Organisation ein [kostenpflichtiges Abonnement kündigt oder herabstuft](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). | +| `pending_subscription_change` | Wird ausgelöst, wenn eine [auf {% data variables.product.prodname_marketplace %} angebotene kostenlose Testphase startet oder abläuft](/articles/about-billing-for-github-marketplace/). | + +#### `advisory_credit` category actions + +| Aktion | Beschreibung | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `accept` | Triggered when someone accepts credit for a security advisory. Weitere Informationen findest Du unter „[Einen Sicherheitshinweis bearbeiten](/github/managing-security-vulnerabilities/editing-a-security-advisory)." | +| `create` | Triggered when the administrator of a security advisory adds someone to the credit section. | +| `decline` | Triggered when someone declines credit for a security advisory. | +| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. | + +#### `billing` category actions + +| Aktion | Beschreibung | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `change_billing_type` | Wird ausgelöst, wenn Deine Organisation ihre [Zahlungsmethode für {% data variables.product.prodname_dotcom %} ändert](/articles/adding-or-editing-a-payment-method). | +| `change_email` | Wird ausgelöst, wenn Ihre Organisation ihre [E-Mail-Adresse für Abrechnungen](/articles/setting-your-billing-email) ändert. | + +#### `dependabot_alerts` category actions + +| Aktion | Beschreibung | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `aktivieren` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +#### `dependabot_alerts_new_repos` category actions + +| Aktion | Beschreibung | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `aktivieren` | 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 + +| Aktion | Beschreibung | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `deaktivieren` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `aktivieren` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. | + +#### `dependabot_security_updates_new_repos` category actions + +| Aktion | Beschreibung | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `aktivieren` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. | + +#### `dependency_graph` category actions + +| Aktion | Beschreibung | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `aktivieren` | Triggered when an organization owner enables the dependency graph for all existing repositories. | + +#### `dependency_graph_new_repos` category actions + +| Aktion | Beschreibung | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `aktivieren` | Triggered when an organization owner enables the dependency graph for all new repositories. | + +{% endif %} + +#### `discussion_post` category actions + +| Aktion | Beschreibung | +| --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | +| `aktualisieren` | Wird ausgelöst, wenn ein [Beitrag zu einer Teamdiskussion bearbeitet wird](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Wird ausgelöst, wenn ein [Beitrag zu einer Teamdiskussion gelöscht wird](/articles/managing-disruptive-comments/#deleting-a-comment). | + +#### `discussion_post_reply` category actions + +| Aktion | Beschreibung | +| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `aktualisieren` | Wird ausgelöst, wenn eine [Antwort auf einen Beitrag zu einer Teamdiskussion bearbeitet wird](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Wird ausgelöst, wenn eine [Antwort auf einen Beitrag zu einer Teamdiskussion gelöscht wird](/articles/managing-disruptive-comments/#deleting-a-comment). | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### `enterprise` category actions + +{% data reusables.actions.actions-audit-events-for-enterprise %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `environment` category actions + +| Aktion | Beschreibung | +| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `git` category actions + +{% note %} + +**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Aktion | Beschreibung | +| --------- | ----------------------------------------------------- | +| `Klon` | Triggered when a repository is cloned. | +| `abrufen` | Triggered when changes are fetched from a repository. | +| `Push` | Triggered when changes are pushed to a repository. | + +{% endif %} + +#### `hook` category actions + +| Aktion | Beschreibung | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `create` | Wird ausgelöst, wenn einem Repository Ihrer Organisation ein [neuer Hook hinzugefügt wird](/articles/creating-webhooks). | +| `config_changed` | Wird ausgelöst, wenn die Konfiguration eines vorhandenen Hooks geändert wird. | +| `destroy` | Wird ausgelöst, wenn ein vorhandener Hook aus einem Repository entfernt wird. | +| `events_changed` | Wird ausgelöst, wenn sich die Ereignisse eines Hooks ändern. | + +#### `integration_installation_request` category actions + +| Aktion | Beschreibung | +| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Wird ausgelöst, wenn ein Mitglied der Organisation bei einem Organisationsinhaber die Installation einer Integration zur Verwendung innerhalb der Organisation anfordert. | +| `close (schließen)` | Wird ausgelöst, wenn eine Anforderung zur Installation einer Integration zur Verwendung innerhalb der Organisation von einem Organisationsinhaber genehmigt oder abgelehnt wird oder wenn die Anforderung von dem Organisationsmitglied, das die Anfrage gestellt hat, abgebrochen wird. | + +#### `issue` category actions + +| Aktion | Beschreibung | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `destroy` | Wird ausgelöst, wenn ein Organisationsinhaber oder eine Person mit Administratorberechtigungen für ein Repository ein Issue aus einem Repository der Organisation löscht. | + +{% if currentVersion == "free-pro-team@latest" %} + +#### `marketplace_agreement_signature` category actions + +| Aktion | Beschreibung | +| -------- | --------------------------------------------------------------------------------------------------------------- | +| `create` | Wird ausgelöst, wenn Du die {% data variables.product.prodname_marketplace %}-Entwicklervereinbarung signierst. | + +#### `marketplace_listing` category actions + +| Aktion | Beschreibung | +| ------------ | ----------------------------------------------------------------------------------------------------------------------------- | +| `genehmigen` | Wird ausgelöst, wenn Dein Eintrag für die Aufnahme in {% data variables.product.prodname_marketplace %} genehmigt wird. | +| `create` | Wird ausgelöst, wenn Du einen Eintrag für Deine App in {% data variables.product.prodname_marketplace %} erstellst. | +| `delist` | Wird ausgelöst, wenn Ihr Listing von {% data variables.product.prodname_marketplace %} entfernt wird. | +| `redraft` | Wird ausgelöst, wenn Dein Eintrag in den Entwurfsstatus zurückversetzt wird. | +| `reject` | Wird ausgelöst, wenn Dein Eintrag für die Aufnahme in {% data variables.product.prodname_marketplace %} nicht genehmigt wird. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +#### `members_can_create_pages` category actions + +For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." + +| Aktion | Beschreibung | +|:-------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `aktivieren` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | +| `deaktivieren` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | + +{% endif %} + +#### `org` category actions + +| Aktion | Beschreibung | +| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `audit_log_export` | Wird ausgelöst, wenn der Administrator einer Organisation einen [Export des Auditprotokolls der Organisation erstellt](#exporting-the-audit-log). Wenn der Export eine Abfrage enthält, listet das Protokoll diese Abfrage sowie die Anzahl der Auditprotokolleinträge auf, die mit der Abfrage übereinstimmen. | +| `block_user` | Wird ausgelöst, wenn ein Organisationsinhaber [den Zugriff eines Benutzers auf die Repositorys der Organisation blockiert](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization). | +| `cancel_invitation` | Wird ausgelöst, wenn die Einladung zu einer Organisation widerrufen wird. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} |{% if currentVersion == "free-pro-team@latest"%} +| `disable_oauth_app_restrictions` | Wird ausgelöst, wenn ein Inhaber die [{% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen](/articles/disabling-oauth-app-access-restrictions-for-your-organization) für Deine Organisation deaktiviert. | +| `disable_saml` | Wird ausgelöst, wenn ein Organisationsadministrator SAML Single Sign-On für eine Organisation deaktiviert.{% endif %} +| `disable_member_team_creation_permission` | Wird ausgelöst, wenn ein Organisationsinhaber die Möglichkeit der Teamerstellung auf Inhaber beschränkt. Weitere Informationen findest Du unter „[Berechtigungen für die Teamerstellung in Deiner Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization).“ |{% if currentVersion != "github-ae@latest" %} +| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable_oauth_app_restrictions` | Wird ausgelöst, wenn ein Inhaber die [{% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen](/articles/enabling-oauth-app-access-restrictions-for-your-organization) für Deine Organisation aktiviert. | +| `enable_saml` | Wird ausgelöst, wenn ein Organisationsadministrator [SAML Single Sign-On für eine Organisation aktiviert](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization).{% endif %} +| `enable_member_team_creation_permission` | Wird ausgelöst, wenn ein Organisationsinhaber Mitgliedern die Erstellung von Teams erlaubt. Weitere Informationen findest Du unter „[Berechtigungen für die Teamerstellung in Deiner Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization).“ |{% if currentVersion != "github-ae@latest" %} +| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %} +| `invite_member` | Triggered when [a new user was invited to join your organization](/articles/adding-organization-members-to-a-team).{% if currentVersion == "free-pro-team@latest" %} +| `oauth_app_access_approved` | Wird ausgelöst, wenn ein Inhaber [einer {% data variables.product.prodname_oauth_app %} den Zugriff auf die Organisation erteilt](/articles/approving-oauth-apps-for-your-organization/). | +| `oauth_app_access_denied` | Wird ausgelöst, wenn ein Inhaber [einen zuvor genehmigten Zugriff einer {% data variables.product.prodname_oauth_app %} zu Deiner Organisation deaktiviert](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization). | +| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." | +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `remove_billing_manager` | Wird ausgelöst, wenn ein [Inhaber einen Abrechnungsmanager aus der Organisation entfernt](/articles/removing-a-billing-manager-from-your-organization/) oder wenn innerhalb der Organisation die [Zwei-Faktor-Authentifizierung verlangt wird](/articles/requiring-two-factor-authentication-in-your-organization) und ein Abrechnungsmanager keine 2FA verwendet bzw. die 2FA deaktiviert. +{% endif %} +| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Wird auch ausgelöst, wenn ein [Organisationsmitglied sich selbst aus einer Organisation entfernt](/articles/removing-yourself-from-an-organization/). | +| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/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` | Wird ausgelöst, wenn ein Organisationsinhaber die verknüpfte Identität eines Mitarbeiters widerruft. Weitere Informationen findest Du unter „[SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" | +| `revoke_sso_session` | Wird ausgelöst, wenn ein Organisationsinhaber die SAML-Sitzung eines Mitglieds widerruft. Weitere Informationen findest Du unter „[SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/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` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | +| `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | +| `runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% 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` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."{% endif %} +| `update_default_repository_permission` | Wird ausgelöst, wenn ein Inhaber die Standard-Berechtigungsebene für Repositorys für die Organisationsmitglieder ändert. | +| `update_member` | Wird ausgelöst, wenn ein Inhaber die Rolle einer Person von Inhaber in Mitglied oder von Mitglied in Inhaber ändert. | +| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% if currentVersion == "free-pro-team@latest" %} +| `update_saml_provider_settings` | Wird ausgelöst, wenn sich die SAML-Anbietereinstellungen einer Organisation ändern. | +| `update_terms_of_service` | Wird ausgelöst, wenn eine Organisation von den Standardnutzungsbedingungen auf die Nutzungsbedingungen für Unternehmen umsteigt. Weitere Informationen finden Sie unter „[Auf Nutzungsbedingungen für Unternehmen umsteigen](/articles/upgrading-to-the-corporate-terms-of-service)“.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `org_credential_authorization` category actions + +| Aktion | Beschreibung | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `grant` | Wird ausgelöst, wenn ein Mitglied [Anmeldeinformationen zur Verwendung mit SAML Single Sign-On](/github/authenticating-to-github/authenticating-with-saml-single-sign-on) autorisiert. | +| `deauthorized` | Wird ausgelöst, wenn ein Mitglied [die Autorisierung von Anmeldeinformationen zur Verwendung mit SAML Single Sign-On zurückzieht](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `revoke` | Wird ausgelöst, wenn ein Inhaber [autorisierte Anmeldeinformationen widerruft](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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" %} +#### `organization_label` category actions + +| Aktion | Beschreibung | +| --------------- | ---------------------------------------------------------------- | +| `create` | Wird ausgelöst, wenn eine Standardkennzeichnung erstellt wird. | +| `aktualisieren` | Wird ausgelöst, wenn eine Standardkennzeichnung bearbeitet wird. | +| `destroy` | Wird ausgelöst, wenn eine Standardkennzeichnung gelöscht wird. | + +{% endif %} + +#### `oauth_application` category actions + +| Aktion | Beschreibung | +| --------------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Wird ausgelöst, wenn eine neue {% data variables.product.prodname_oauth_app %} erstellt wird. | +| `destroy` | Wird ausgelöst, wenn eine vorhandene {% data variables.product.prodname_oauth_app %} gelöscht wird. | +| `reset_secret` | Wird ausgelöst, wenn das Client-Geheimnis einer {% data variables.product.prodname_oauth_app %} zurückgesetzt wird. | +| `revoke_tokens` | Wird ausgelöst, wenn die Benutzertoken einer {% data variables.product.prodname_oauth_app %} zurückgezogen werden. | +| `übertragen` | Wird ausgelöst, wenn eine vorhandene {% data variables.product.prodname_oauth_app %} auf eine neue Organisation übertragen wird. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +#### `packages` category actions + +| Aktion | Beschreibung | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `package_version_published` | Triggered when a package version is published. | +| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `payment_method` category actions + +| Aktion | Beschreibung | +| --------------- | ------------------------------------------------------------------------------------------------------------------- | +| `clear` | Wird ausgelöst, wenn eine registrierte Zahlungsmethode [entfernt](/articles/removing-a-payment-method) wird. | +| `create` | Wird ausgelöst, wenn eine Zahlungsmethode, beispielsweise eine Kreditkarte oder ein PayPal-Konto, hinzugefügt wird. | +| `aktualisieren` | Wird ausgelöst, wenn eine vorhandene Zahlungsmethode geändert wird. | + +{% endif %} + +#### `profile_picture` category actions +| Aktion | Beschreibung | +| ------------- | --------------------------------------------------------------------------------- | +| aktualisieren | Wird ausgelöst, wenn Sie das Profilbild Ihrer Organisation festlegen oder ändern. | + +#### `project` category actions + +| Aktion | Beschreibung | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Wird bei der Erstellung eines Projektboards ausgelöst. | +| `link` | Wird ausgelöst, wenn ein Repository mit einem Projektboard verknüpft wird. | +| `rename` | Wird ausgelöst, wenn ein Projektboard umbenannt wird. | +| `aktualisieren` | Wird ausgelöst, wenn ein Projektboard geändert wird. | +| `delete` | Wird ausgelöst, wenn ein Projektboard gelöscht wird. | +| `unlink` | Wird ausgelöst, wenn die Verknüpfung eines Repositorys mit einem Projektboard aufgehoben wird. | +| `update_org_permission` | Wird ausgelöst, wenn die Berechtigungen auf Basisebene für alle Organisationsmitglieder geändert oder entfernt werden. | +| `update_team_permission` | Wird ausgelöst, wenn sich die Berechtigungsebene eines Teams für ein Projektboard ändert oder wenn ein Team in einem Projektboard hinzugefügt oder entfernt wird. | +| `update_user_permission` | Wird ausgelöst, wenn ein Organisationsmitglied oder ein externer Mitarbeiter in einem Projektboard hinzugefügt oder entfernt wird oder wenn sich dessen Berechtigungsebene ändert. | + +#### `protected_branch` category actions + +| Aktion | Beschreibung | +| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Wird ausgelöst, wenn für einen Branch der Branch-Schutz aktiviert wird. | +| `destroy` | Wird ausgelöst, wenn für einen Branch der Branch-Schutz deaktiviert wird. | +| `update_admin_enforced` | Wird ausgelöst, wenn der Branch-Schutz für Repository-Administratoren erzwungen wird. | +| `update_require_code_owner_review` | Wird ausgelöst, wenn die Erzwingung erforderlicher Reviews durch einen Codeinhaber für einen Branch akualisiert wird. | +| `dismiss_stale_reviews` | Wird ausgelöst, wenn die Erzwingung des Verwerfens veralteter Pull Requests für einen Branch akualisiert wird. | +| `update_signature_requirement_enforcement_level` | Wird ausgelöst, wenn die Erzwingung der obligatorischen Commit-Signatur für einen Branch akualisiert wird. | +| `update_pull_request_reviews_enforcement_level` | Wird ausgelöst, wenn die Erzwingung erforderlicher Pull-Request-Reviews für einen Branch akualisiert wird. | +| `update_required_status_checks_enforcement_level` | Wird ausgelöst, wenn die Erzwingung erforderlicher Statuschecks für einen Branch akualisiert wird. | +| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | +| `rejected_ref_update` | Wird ausgelöst, wenn eine Branch-Aktualisierung abgelehnt wird. | +| `policy_override` | Triggered when a branch protection requirement is overridden by a repository administrator.{% 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` | Wird ausgelöst, wenn erzwungene Pushes für einen geschützten Branch aktiviert oder deaktiviert werden. | +| `update_allow_deletions_enforcement_level` | Wird ausgelöst, wenn die Branch-Löschung für einen geschützten Branch aktiviert oder deaktiviert wird. | +| `update_linear_history_requirement_enforcement_level` | Wird ausgelöst, wenn der erforderliche lineare Commit-Verlauf für einen geschützten Branch aktiviert oder deaktiviert wird. | +{% endif %} + +#### `repo` category actions + +| Aktion | Beschreibung | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | +| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +| `add_member` | Wird ausgelöst, wenn ein Benutzer eine [Einladung für den Zugriff auf ein Repository als Mitarbeiter](/articles/inviting-collaborators-to-a-personal-repository) akzeptiert. | +| `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" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for 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)." | +| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for 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).".{% endif %} +| `archived` | Wird ausgelöst, wenn ein Repository-Administrator ein [Repository archiviert](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} +| `config.disable_anonymous_git_access` | Wird ausgelöst, wenn für ein öffentliches Repository der [anonyme Git-Lesezugriff deaktiviert](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) wird. | +| `config.enable_anonymous_git_access` | Wird ausgelöst, wenn für ein öffentliches Repository der [anonyme Git-Lesezugriff aktiviert](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) wird. | +| `config.lock_anonymous_git_access` | Wird ausgelöst, wenn für ein Repository die [Einstellung für den anonymen Git-Lesezugriff gesperrt](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access) wird. | +| `config.unlock_anonymous_git_access` | Wird ausgelöst, wenn für ein Repository die [Einstellungssperre für den anonymen Git-Lesezugriff aufgehoben](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access) wird.{% 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 {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} +| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `deaktivieren` | Wird ausgelöst, wenn ein Repository deaktiviert wird (z. B. aufgrund [unzureichender Deckung](/articles/unlocking-a-locked-account)).{% endif %} +| `aktivieren` | 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 {% data variables.product.prodname_actions %} secret is removed.{% 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 new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." |{% endif %} +| `remove_topic` | Wird ausgelöst, wenn ein Repository-Administrator ein Thema aus einem Repository entfernt. | +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `übertragen` | Wird ausgelöst, wenn ein [Repository übertragen](/articles/how-to-transfer-a-repository) wird. | +| `transfer_start` | Wird ausgelöst, wenn die Übertragung eines Repositorys initiiert wurde. | +| `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 {% data variables.product.prodname_actions %} secret is updated.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `repository_advisory` category actions + +| Aktion | Beschreibung | +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `close (schließen)` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | +| `open` | Triggered when someone opens a draft security advisory. | +| `publish` | Triggered when someone publishes a security advisory. | +| `reopen` | Triggered when someone reopens as draft security advisory. | +| `aktualisieren` | Triggered when someone edits a draft or published security advisory. | + +#### `repository_content_analysis` category actions + +| Aktion | Beschreibung | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `aktivieren` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | +| `deaktivieren` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | + +{% endif %}{% if currentVersion != "github-ae@latest" %} + +#### `repository_dependency_graph` category actions + +| Aktion | Beschreibung | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | +| `aktivieren` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### `repository_secret_scanning` category actions + +| Aktion | Beschreibung | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | +| `aktivieren` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### `repository_vulnerability_alert` category actions + +| Aktion | Beschreibung | +| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when {% data variables.product.product_name %} creates a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | | +| `verwerfen` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. | +| `beheben` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### `repository_vulnerability_alerts` category actions + +| Aktion | Beschreibung | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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)." | +| `deaktivieren` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. | +| `aktivieren` | 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" or currentVersion == "github-ae@latest" %} +#### `secret_scanning` category actions + +| Aktion | Beschreibung | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | 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)." | +| `aktivieren` | 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 + +| Aktion | Beschreibung | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | Triggered when an organization owner disables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | +| `aktivieren` | Triggered when an organization owner enables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `sponsors` category actions + +| Aktion | Beschreibung | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo_funding_link_button_toggle` | Wird ausgelöst, wenn Du eine Sponsorenschaltfläche in Deinem Repository aktivierst oder deaktivierst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | +| `repo_funding_links_file_action` | Wird ausgelöst, wenn Du die FUNDING-Datei in Deinem Repository änderst (siehe „[Sponsorenschaltfläche in Deinem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | +| `sponsor_sponsorship_cancel` | Wird ausgelöst, wenn Sie ein Sponsoring beenden (siehe „[Sponsoring herabstufen](/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_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` | Wird ausgelöst, wenn Sie Ihr Sponsoring upgraden oder herabstufen (siehe „[Sponsoring upgraden](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/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 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 "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| sponsored_developer_update_newsletter_send | Wird ausgelöst, wenn Sie Ihren Sponsoren eine E-Mail-Aktualisierung senden (siehe „[Sponsoren kontaktieren](/articles/contacting-your-sponsors)“). | +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `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 %} + +#### `team` category actions + +| Aktion | Beschreibung | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member` | Wird ausgelöst, wenn ein Mitglied einer Organisation [einem Team hinzugefügt](/articles/adding-organization-members-to-a-team) wird. | +| `add_repository` | Wird ausgelöst, wenn ein Team die Kontrolle über ein Repository erhält. | +| `change_parent_team` | Wird ausgelöst, wenn ein untergeordnetes Team erstellt wird oder das [übergeordnete Team eines untergeordneten Teams geändert](/articles/moving-a-team-in-your-organization-s-hierarchy) wird. | +| `change_privacy` | Wird ausgelöst, wenn die Datenschutzstufe eines Teams geändert wird. | +| `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](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/managing-peoples-access-to-your-organization-with-roles/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 + +| Aktion | Beschreibung | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `deaktivieren` | Wird ausgelöst, wenn ein Organisationsinhaber für eine Organisation Teamdiskussionen deaktiviert. Weitere Informationen findest Du unter „[Teamdiskussionen innerhalb Deiner Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization).“ | +| `aktivieren` | Wird ausgelöst, wenn ein Organisationsinhaber für eine Organisation Teamdiskussionen aktiviert. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +#### `workflows` category actions + +{% data reusables.actions.actions-audit-events-workflow %} + +{% endif %} + +### Weiterführende Informationen + +- „[Schutz Ihrer Organisation](/articles/keeping-your-organization-secure)“ diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000..863bddd407 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,25 @@ +--- +title: Installierte Integrationen Deiner Organisation überprüfen +intro: Du kannst die Berechtigungsebenen für die installierten Integrationen Deiner Organisation überprüfen und den Zugriff jeder Integration auf die Repositorys Deiner Organisation konfigurieren. +redirect_from: + - /articles/reviewing-your-organization-s-installed-integrations + - /articles/reviewing-your-organizations-installed-integrations + - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Klicke in der linken Seitenleiste auf **Installed {% data variables.product.prodname_github_app %}s** (Installierte Apps). ![Registerkarte „Installed {% data variables.product.prodname_github_app %}s“ (Installierte Apps) in der Seitenleiste mit den Organisationseinstellungen](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. Klicke neben der {% data variables.product.prodname_github_app %}, die Du überprüfen möchtest, auf **Configure** (Konfigurieren). ![Schaltfläche „Configure“ (Konfigurieren)](/assets/images/help/organizations/configure-installed-integration-button.png) +6. Überprüfe die Berechtigungen und den Repository-Zugriff der {% data variables.product.prodname_github_app %}s. ![Option zur Festlegung des Zugriffs der {% data variables.product.prodname_github_app %} auf alle oder ausgewählte Repositorys](/assets/images/help/organizations/toggle-integration-repo-access.png) + - Soll die {% data variables.product.prodname_github_app %} Zugriff auf alle Repositorys Deiner Organisation haben, klicke auf **All repositories** (Alle Repositorys). + - Soll die Anwendung nur auf bestimmte Repositorys Zugriff haben, wähle **Only select repositories** (Nur ausgewählte Repositorys) aus, und gib einen Repositorynamen ein. +7. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000..48336b6f35 --- /dev/null +++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,30 @@ +--- +title: Überprüfen, ob die Benutzer Deiner Organisation die 2FA aktiviert haben +intro: 'Du kannst anzeigen, welche Organisationsinhaber, Mitglieder und externen Mitarbeiter die Zwei-Faktor-Authentifizierung aktiviert haben.' +redirect_from: + - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled + - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +{% 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. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/articles/requiring-two-factor-authentication-in-your-organization)“. + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Um die Organisationsmitglieder, einschließlich der Organisationsinhaber, anzuzeigen, welche die Zwei-Faktor-Authentifizierung aktiviert oder deaktiviert haben, klicke auf der rechten Seite auf **2FA** (Zwei-Faktor-Authentifizierung), und wähle **Enabled** (Aktiviert) oder **Disabled** (Deaktiviert). ![Organisationsmitglieder nach Zwei-Faktor-Authentifizierung filtern](/assets/images/help/2fa/filter-org-members-by-2fa.png) +5. Wenn Du externe Mitarbeiter in Deiner Organisation anzeigen möchtest, klicke unter der Registerkarte „People“ (Personen) auf **Outside collaborators** (Externe Mitarbeiter). ![Auswahl von externen Mitarbeitern](/assets/images/help/organizations/select-outside-collaborators.png) +6. Um anzuzeigen, welche externen Mitarbeiter die Zwei-Faktor-Authentifizierung aktiviert oder deaktiviert haben, klicke auf der rechten Seite auf **2FA** (Zwei-Faktor-Authentifizierung), und wähle **Enabled** (Aktiviert) oder **Disabled** (Deaktiviert). ![Externe Mitarbeiter nach Zwei-Faktor-Authentifizierung filtern](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) + +### Weiterführende Informationen + +- „[Rollen von Personen in einer Organisation anzeigen](/articles/viewing-people-s-roles-in-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000..9e2ceecf6a --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,40 @@ +--- +title: GitHub App-Manager zu Deiner Organisation hinzufügen +intro: 'Organisationsinhaber können Benutzern die Berechtigung zum Verwalten bestimmter oder aller {% data variables.product.prodname_github_app %}s der Organisation erteilen.' +redirect_from: + - /articles/adding-github-app-managers-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Weitere Informationen zu den Berechtigungen für {% data variables.product.prodname_github_app %}-Manager findest Du unter „[Berechtigungsebenen für eine Organisation](/articles/permission-levels-for-an-organization#github-app-managers).“ + +### Jemandem die Berechtigung zur Verwaltung aller {% data variables.product.prodname_github_app %}s der Organisation erteilen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Gib unter „Management“ (Verwaltung) den Benutzernamen der Person ein, die Du als {% data variables.product.prodname_github_app %}-Manager in der Organisation festlegen möchtest. Klicke anschließend auf **Grant** (Erteilen). ![Einen {% data variables.product.prodname_github_app %}-Manager hinzufügen](/assets/images/help/organizations/add-github-app-manager.png) + +### Jemandem die Berechtigung zur Verwaltung einer einzelnen {% data variables.product.prodname_github_app %} erteilen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Klicken Sie unter „{% data variables.product.prodname_github_app %}s“ auf den Avatar der App, zu der Sie einen {% data variables.product.prodname_github_app %}-Manager hinzufügen möchten. ![{% data variables.product.prodname_github_app %} auswählen](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Gib unter „App managers“ (App-Manager) den Benutzernamen der Person ein, die Du als GitHub App-Manager für die App festlegen möchtest. Klicke anschließend auf **Grant** (Erteilen). ![Einen {% data variables.product.prodname_github_app %}-Manager für eine bestimmte App hinzufügen](/assets/images/help/organizations/add-github-app-manager-for-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Weiterführende Informationen + +- „[Informationen zu {% data variables.product.prodname_dotcom %}-Marketplace](/articles/about-github-marketplace/)“ +{% endif %} diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/index.md new file mode 100644 index 0000000000..e481804141 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -0,0 +1,18 @@ +--- +title: Zugriff auf die Apps Deiner Organisation verwalten +intro: 'Als Organisationsinhaber können Sie es einzelnen Organisationsmitgliedern erlauben, {% data variables.product.prodname_github_app %}s in Ihrer Organisation zu verwalten.' +redirect_from: + - /articles/managing-access-to-your-organization-s-apps + - /articles/managing-access-to-your-organizations-apps + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% link_in_list /adding-github-app-managers-in-your-organization %} +{% link_in_list /removing-github-app-managers-from-your-organization %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000..6c0e600508 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,40 @@ +--- +title: GitHub App-Manager aus Deiner Organisation entfernen +intro: 'Organisationsinhaber können die einem Organisationsmitglied erteilten {% data variables.product.prodname_github_app %}-Managerberechtigungen entziehen.' +redirect_from: + - /articles/removing-github-app-managers-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Weitere Informationen zu den Berechtigungen für {% data variables.product.prodname_github_app %}-Manager findest Du unter „[Berechtigungsebenen für eine Organisation](/articles/permission-levels-for-an-organization#github-app-managers).“ + +### Berechtigungen eines {% data variables.product.prodname_github_app %}-Managers für die gesamte Organisation entfernen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Suche unter „Management“ (Verwaltung) den Benutzernamen der Person, deren {% data variables.product.prodname_github_app %}-Managerberechtigungen Du entziehen möchtest, und klicke auf **Revoke** (Entziehen). ![{% data variables.product.prodname_github_app %}-Managerberechtigungen entziehen](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) + +### Berechtigungen eines {% data variables.product.prodname_github_app %}-Managers für eine einzelne {% data variables.product.prodname_github_app %} entfernen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Klicken Sie unter „{% data variables.product.prodname_github_app %}s“ auf den Avatar der App, für die Sie einen {% data variables.product.prodname_github_app %}-Manager entfernen möchten. ![{% data variables.product.prodname_github_app %} auswählen](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Suche unter „App managers“ (App-Manager) den Benutzernamen der Person, deren {% data variables.product.prodname_github_app %}-Managerberechtigungen Du entziehen möchtest, und klicke auf **Revoke** (Entziehen). ![{% data variables.product.prodname_github_app %}-Managerberechtigungen entziehen](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Weiterführende Informationen + +- „[Informationen zu {% data variables.product.prodname_dotcom %}-Marketplace](/articles/about-github-marketplace/)“ +{% endif %} diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000..bc8b274f46 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Einen externen Mitarbeiter zu einem Projektboard in Deiner Organisation hinzufügen +intro: 'Als Organisationsinhaber oder Projektboard-Administrator kannst du einen externen Mitarbeiter zu einem Projektboard hinzufügen und seine Berechtigungen anpassen.' +redirect_from: + - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Ein externer Mitarbeiter ist eine Person, die nicht explizit Mitglied Deiner Organisation ist, aber auf ein Projektboard in Deiner Organisation zugreifen kann. + +{% 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. Gib unter „Search by username, full name or email address“ (Nach Benutzername, vollständigem Namen oder E-Mail-Adresse suchen) den Namen, den Benutzernamen oder die {% data variables.product.prodname_dotcom %}-E-Mail-Adresse des externen Mitarbeiters ein. ![Der Bereich „Collaborators“ (Mitarbeiter) mit Octocat-Benutzernamen im Suchfeld](/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/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/index.md new file mode 100644 index 0000000000..ad093634f0 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -0,0 +1,22 @@ +--- +title: Zugriff auf die Projektboards Deiner Organisation verwalten +intro: 'Als Organisationsinhaber oder Projektboard-Administrator kannst Du Organisationsmitgliedern, Teams und externen Mitarbeitern unterschiedliche Berechtigungen für den Zugriff auf die Projektboards Deiner Organisation erteilen.' +redirect_from: + - /articles/managing-access-to-your-organization-s-project-boards + - /articles/managing-access-to-your-organizations-project-boards + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000..9064fa762f --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,39 @@ +--- +title: Zugriff auf ein Projektboard für Organisationsmitglieder verwalten +intro: 'Als Organisationsinhaber oder Projektboard-Administrator kannst Du eine standardmäßige Berechtigungsebene für ein Projektboard für alle Organisationsmitglieder festlegen.' +redirect_from: + - /articles/managing-access-to-a-project-board-for-organization-members + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Standardmäßig haben Organisationsmitglieder Schreibzugriff auf die Projektboards ihrer Organisation, sofern die Organisationsinhaber oder Projektboard-Administratoren keine abweichenden Berechtigungen für bestimmte Projektboards festgelegt haben. + +### Eine grundlegende Berechtigungsebene für alle Organisationsmitglieder festlegen + +{% tip %} + +**Tipp:** Du kannst einem Organisationsmitglied höhere Berechtigungen für Projektboards erteilen. Weitere Informationen finden Sie unter „[Projektboardberechtigungen für eine Organisation](/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. Wähle unter „Organization member permission“ (Berechtigung für Organisationsmitglieder) eine grundlegende Berechtigungsebene für alle Organisationsmitglieder aus: **Read** (Lesen), **Write** (Schreiben), **Admin** (Administrator) oder **None** (Keine). ![Optionen für grundlegende Projektboard-Berechtigungen für alle Organisationsmitglieder](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. Klicke auf **Save** (Speichern). + +### Weiterführende Informationen + +- „[Zugriff einer Einzelperson auf das Projektboard einer Organisation verwalten](/articles/managing-an-individual-s-access-to-an-organization-project-board)“ +- „[Teamzugriff auf ein Projektboard einer Organisation verwalten](/articles/managing-team-access-to-an-organization-project-board)“ +- „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..4d621dfc5b --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,62 @@ +--- +title: Zugriff einer Einzelperson auf das Projektboard einer Organisation verwalten +intro: 'Als Organisationsinhaber oder Projektboard-Administrator kannst Du den Zugriff einzelner Mitglieder auf ein Projektboard Deiner Organisation verwalten.' +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-project-board + - /articles/managing-an-individuals-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% note %} + +**Hinweis:** {% data reusables.project-management.cascading-permissions %} Weitere Informationen findest Du unter „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization).“ + +{% endnote %} + +### Einem Organisationsmitglied Zugriff auf ein Projektboard gewähren + +{% 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. Geben Sie unter „Search by username, full name or email address“ (Nach Benutzernamen, vollständigem Namen oder E-Mail-Adresse suchen) den Namen, den Benutzernamen oder die {% data variables.product.prodname_dotcom %}-E-Mail-Adresse des Mitarbeiters ein. ![Der Bereich „Collaborators“ (Mitarbeiter) mit Octocat-Benutzernamen im Suchfeld](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} + +### Den Zugriff eines Organisationsmitglieds auf ein Projektboard ändern + +{% 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 %} + +### Einem Organisationsmitglied den Zugriff auf ein Projektboard entziehen + +Wenn Du einen Mitarbeiter von einem Projektboard entfernst, kann er je nach den Berechtigungen seiner anderen Rollen möglicherweise dennoch weiterhin auf das Projektboard zugreifen. Um den Zugriff auf ein Projektboard komplett zu verhindern, musst Du den Zugriff für jede Rolle dieses Mitarbeiters entfernen. Eine Person kann beispielsweise als Organisationsmitglied oder Teammitglied Zugriff auf das Projektboard haben. Weitere Informationen finden Sie unter „[Projektboardberechtigungen für eine Organisation](/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 %} + +### Weiterführende Informationen + +- „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..82160eee1f --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,52 @@ +--- +title: Teamzugriff auf ein Projektboard einer Organisation verwalten +intro: 'Als Organisationsinhaber oder Projektboard-Administrator kannst Du einem Team Zugriff auf ein Projektboard Deiner Organisation gewähren.' +redirect_from: + - /articles/managing-team-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% warning %} + +**Warnungen:** +- Du kannst die Berechtigungsebene eines Teams ändern, wenn das Team direkten Zugriff auf ein Projektboard hat. Wenn der Zugriff des Teams auf das Projektboard von einem übergeordneten Team übernommen wird, musst Du den Zugriff des übergeordneten Teams auf das Projektboard ändern. +- Wenn Du einem übergeordneten Team den Zugriff auf ein Projektboard gewährst oder entziehst, erhalten oder verlieren auch die untergeordneten Teams den Zugriff auf das Projektboard. Weitere Informationen finden Sie unter „[Informationen zu Teams](/articles/about-teams)“. + +{% endwarning %} + +### Einem Team Zugriff auf ein Projektboard gewähren + +Du kannst einem gesamten Team die gleiche Berechtigungsebene für ein Projektboard zuweisen. + +{% note %} + +**Hinweis:** {% data reusables.project-management.cascading-permissions %} Wenn ein Organisationsinhaber beispielsweise einem Team Leseberechtigung für ein Projektboard erteilt hat und ein Projektboard-Administrator einem Mitglied dieses Teams Administratorberechtigungen als einzelner Mitarbeiter für dieses Projektboard erteilt, würde diese Person Administratorberechtigungen für das Projektboard haben. Weitere Informationen findest Du unter „[Projektboardberechtigungen für eine Organisation](/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. Klicke auf der linken Seitenleiste auf **Teams** (Teams). +9. Um ein Team hinzuzufügen, klicke auf **Add a team: Select team** (Ein Team hinzufügen: Team auswählen). Wähle dann ein Team aus dem Dropdownmenü aus, oder suche nach dem Team, das Du hinzufügen möchtest. ![Dropdownmenü zum Hinzufügen von Teams mit Liste der Teams der Organisation](/assets/images/help/projects/add-a-team.png) +10. Wähle im Dropdownmenü neben dem Teamnamen die gewünschte Berechtigungsebene aus: **Read** (Lesen), **Write** (Schreiben) oder **Admin** (Administrator). ![Dropdownmenü mit Teamberechtigungen mit Lese-, Schreib- und Administrator-Optionen](/assets/images/help/projects/org-project-team-choose-permissions.png) + +### Den Zugriff eines Teams auf ein Projektboard konfigurieren + +Wenn der Zugriff eines Teams auf ein Projektboard von einem übergeordneten Team geerbt wird, musst Du den Zugriff des übergeordneten Teams auf das Projektboard ändern, um den Zugriff für die untergeordneten Teams zu aktualisieren. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. Klicke oberhalb der Unterhaltungen des Teams auf {% octicon "project" aria-label="The Projects icon" %} **Projects** (Projekte). ![Registerkarte mit Team-Repositorys](/assets/images/help/organizations/team-project-board-button.png) +5. Um die Berechtigungsstufen für ein Projektboard anzupassen, benutze das Dropdownmenü rechts neben dem anzupassenden Projektboard. Um ein Projektboard zu entfernen, klicke **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Mülleimer-Schaltfläche zum Entfernen eines Projektboards aus dem Team](/assets/images/help/organizations/trash-button.png) diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000..4167ff5f49 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -0,0 +1,44 @@ +--- +title: Projektboardberechtigungen für eine Organisation +intro: 'Organisationsinhaber und Personen mit Projektboard-Administratorberechtigungen können anpassen, wer Lese-, Schreib- und Administratorberechtigungen für die Projektboards Deiner Organisation hat.' +redirect_from: + - /articles/project-board-permissions-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### Überblick über die Berechtigungen + +Bei Projektboards gibt es für Benutzer und Teams drei Berechtigungsstufen: + +{% data reusables.project-management.project-board-permissions %} + +Organisationsinhaber und Personen mit Administratorberechtigungen können einer Person den Zugriff auf ein Projektboard der Organisation als Einzelperson, als externer Mitarbeiter oder Organisationsmitglied oder über ihre Mitgliedschaft in einem Team oder einer Organisation gewähren. Ein externer Mitarbeiter ist eine Person, die kein Organisationsmitglied ist, aber die Berechtigungen für die Mitarbeit in Deiner Organisation besitzt. + +Organisationsinhaber und Personen mit Administratorberechtigungen für ein Projektboard können außerdem Folgendes tun: +- Standardberechtigungen für das Projektboard für alle Organisationsmitglieder festlegen +- den Zugriff auf das Projektboard für Organisationsmitglieder, Teams und externe Mitarbeiter verwalten Weitere Informationen findest Du unter „[Teamzugriff auf ein Projektboard einer Organisation verwalten](/articles/managing-team-access-to-an-organization-project-board)“, „[Zugriff einer Einzelperson auf das Projektboard einer Organisation verwalten](/articles/managing-an-individual-s-access-to-an-organization-project-board)“ oder „[Zugriff auf ein Projektboard für Organisationsmitglieder verwalten](/articles/managing-access-to-a-project-board-for-organization-members),“ +- die Sichtbarkeit des Projektboards verwalten (siehe „[Zugriff auf ein Projektboard für Organisationsmitglieder verwalten](/articles/managing-access-to-a-project-board-for-organization-members)“) + +### Berechtigungen für Projektboards kaskadieren + +{% data reusables.project-management.cascading-permissions %} + +Wenn ein Organisationsinhaber beispielsweise allen Organisationsmitgliedern Leseberechtigungen für ein Projektboard erteilt hat und ein Projektboard-Administrator einem Organisationsmitglied Schreibberechtigungen als einzelner Mitarbeiter für dieses Projektboard erteilt, würde diese Person Schreibberechtigungen für das Projektboard haben. + +### Sichtbarkeit des Projektboards + +{% 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 + +- „[Sichtbarkeit des Projektboards ändern](/articles/changing-project-board-visibility)“ +- „[Zugriff einer Einzelperson auf das Projektboard einer Organisation verwalten](/articles/managing-an-individual-s-access-to-an-organization-project-board)“ +- „[Teamzugriff auf ein Projektboard einer Organisation verwalten](/articles/managing-team-access-to-an-organization-project-board)“ +- „[Zugriff auf ein Projektboard für Organisationsmitglieder verwalten](/articles/managing-access-to-a-project-board-for-organization-members)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000..f024e5ee0e --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,23 @@ +--- +title: Externen Mitarbeiter von einem Projektboard der Organisation entfernen +intro: 'Als Organisationsinhaber oder Projektboard-Administrator kannst Du den Zugriff eines externen Mitarbeiters auf ein Projektboard entfernen.' +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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/de-DE/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000..94bca7faf8 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,42 @@ +--- +title: Externe Mitarbeiter zu Organisations-Repositorys hinzufügen +intro: 'Ein *externer Mitarbeiter* ist eine Person, die nicht explizit Mitglied Deiner Organisation ist, aber Lese-, Schreib- oder Administratorberechtigungen für mindestens ein Repository in Deiner Organisation besitzt.' +redirect_from: + - /articles/adding-outside-collaborators-to-repositories-in-your-organization + - github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} externe Mitarbeiter zu einem Repository hinzufügen, es sei denn, ein Organisationsinhaber hat die Möglichkeit zum Einladen von Mitarbeitern eingeschränkt. Weitere Informationen findest Du unter „[Berechtigungen zum Hinzufügen von externen Mitarbeitern festlegen](/articles/setting-permissions-for-adding-outside-collaborators)." + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% if currentVersion != "github-ae@latest" %} +Wenn Deine Organisation [die Zwei-Faktor-Authentifizierung für Mitglieder und externe Mitarbeiter vorschreibt](/articles/requiring-two-factor-authentication-in-your-organization), müssen die Benutzer die Zwei-Faktor-Authentifizierung aktivieren, bevor sie Deine Einladung zur Zusammenarbeit an einem Repository der Organisation annehmen können. +{% 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. Beginne im Suchfeld den Namen der Person einzugeben, die Du einladen möchtest, dann klicke in der Liste der Übereinstimmungen auf einen Namen. ![Suchfeld für die Eingabe des Namens der Person, die Du zu einem Repository einladen willst](/assets/images/help/repository/manage-access-invite-search-field.png) +6. Wähle unter „Choose a role" (Wähle eine Rolle) die zu gewährenden Berechtigungen für die Person, dann klicke auf **Add NAME to REPOSITORY** (Füge NAME zum REPOSITORY hinzu). ![Berechtigungen für die Person auswählen](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +{% else %} +5. Klicke auf der linken Seitenleiste auf **Collaborators & teams** (Mitarbeiter und Teams). ![Seitenleiste der Repository-Einstellungen, wobei „Collaborators & Teams“ (Mitarbeiter & Teams) hervorgehoben ist](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. Gib unter „Collaborators“ (Mitarbeiter) den Namen der Person ein, der Du Zugriff auf das Repository gewähren möchtest, und klicke dann auf **Add collaborator** (Mitarbeiter hinzufügen). ![Der Bereich „Collaborators“ (Mitarbeiter) mit Octocat-Benutzernamen im Suchfeld](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. Wähle neben dem Namen des neuen Mitarbeiters die gewünschte Berechtigungsebene aus: *Write* (Schreibberechtigung), *Read* (Leseberechtigung) oder *Admin* (Administratorberechtigungen). ![Die Repository-Berechtigungsauswahl](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +{% endif %} + +### Weiterführende Informationen + +- „[Ein Organisationsmitglied in einen externen Mitarbeiter umwandeln](/articles/converting-an-organization-member-to-an-outside-collaborator)“ +- „[Externen Mitarbeiter von einem Organisations-Repository entfernen](/articles/removing-an-outside-collaborator-from-an-organization-repository)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000..a1ba35d67a --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,24 @@ +--- +title: Eine Einladung zurückziehen, externen Mitarbeiter Deiner Organisation zu werden +intro: Du kannst alle Einladungen für eine Person zurückziehen, externer Mitarbeiter auf Repositorys zu werden, die Deiner Organisation gehören. +permissions: Organisationsinhaber können Einladungen zurückziehen, externer Mitarbeiter in der Organisation zu werden. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Du kannst eine Liste aller Personen mit ausstehenden Einladungen ansehen, externer Mitarbeiter für beliebige Repositorys Deiner Organisation zu werden. + +Für jeden ausstehenden Mitarbeiter kannst Du alle Einladungen zur Teilnahme an Repositorys der Organisation gleichzeitig zurückziehen. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% 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). ![Button to confirm cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000..122ae1e3c1 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,44 @@ +--- +title: Ein Organisationsmitglied in einen externen Mitarbeiter umwandeln +intro: 'Wenn ein aktuelles Mitglied Deiner Organisation nur auf bestimmte Repositorys zugreifen muss, z. B. im Falle von Beratern oder temporären Mitarbeitern, kannst Du ihn in einen *externen Mitarbeiter* umwandeln.' +redirect_from: + - /articles/converting-an-organization-member-to-an-outside-collaborator + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} Organisationsmitglieder in externe Mitarbeiter umwandeln. + +{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} + +Wenn Organisationsmitglieder in externe Mitarbeiter umgewandelt wurden, haben sie nur auf die Repositorys Zugriff, auf die sie entsprechend der aktuellen Teammitgliedschaft zugreifen können. Die Person ist kein explizites Mitglied der Organisation mehr und kann Folgendes nicht mehr tun: + +- Teams erstellen +- Alle Organisationsmitglieder und Teams sehen +- Ein sichtbares Team @erwähnen +- Ein Team-Betreuer sein + +Weitere Informationen findest Du unter „[Berechtigungsebenen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)." + +Wir empfehlen Dir, den Zugriff des Organisationsmitglieds auf Repositorys zu überprüfen, um sicherzustellen, dass dessen Zugriff den Erwartungen entspricht. Weitere Informationen findest Du unter „[Den Zugriff einer Person auf ein Repository einer Organisation verwalten](/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. Weitere Informationen findest Du unter „[Ehemaliges Mitglied Deiner Organisation wieder einsetzen](/articles/reinstating-a-former-member-of-your-organization).“ + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Wähle die Person(en) aus, die Du in externe Mitarbeiter umwandeln möchtest. ![Liste der Mitglieder mit zwei ausgewählten Mitgliedern](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Klicke im Dropdownmenü über der Mitgliederliste auf **Convert to outside collaborator** (In externen Mitarbeiter umwandeln). ![Dropdownmenü mit der Option, Mitglieder in externe Mitarbeiter umzuwandeln](/assets/images/help/teams/user-bulk-management-options.png) +6. Lies die Informationen zum Umwandeln von Mitgliedern in externe Mitarbeiter, und klicke dann auf **Convert to outside collaborator** (In externen Mitarbeiter umwandeln). ![Informationen zu Berechtigungen für externe Mitarbeiter und Schaltfläche „Convert to outside collaborator“ (In externen Mitarbeiter umwandeln)](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) + +### Weiterführende Informationen + +- „[Externe Mitarbeiter zu Organisations-Repositorys hinzufügen](/articles/adding-outside-collaborators-to-repositories-in-your-organization)“ +- „[Externen Mitarbeiter von einem Organisations-Repository entfernen](/articles/removing-an-outside-collaborator-from-an-organization-repository)“ +- „[Externen Mitarbeiter in ein Organisationsmitglied umwandeln](/articles/converting-an-outside-collaborator-to-an-organization-member)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000..2b267dbd5f --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,41 @@ +--- +title: Einen externen Mitarbeiter in ein Organisationsmitglied umwandeln +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization owners can {% if currentVersion == "free-pro-team@latest" %}invite users to join{% else %}add users to{% endif %} an organization.' +topics: + - organisationen + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +Wenn Deine Organisation ein benutzerabhängiges Abonnement abgeschlossen hat, muss eine Lizenz verfügbar sein, bevor Du ein neues Mitglied zur Organisation einladen oder ein ehemaliges Organisationsmitglied wieder einsetzen kannst. Weitere Informationen finden Sie unter „[Informationen zur benutzerabhängigen Preisgestaltung](/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 %} +{% 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. 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**.![Externe Mitarbeiter zur Organisation einladen](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) +{% else %} +5. Klicke rechts neben dem Namen des externen Mitarbeiters, der Mitglied werden soll, auf **Invite to organization** (Zur Organisation einladen).![Externe Mitarbeiter zur Organisation einladen](/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 %} + +### Weiterführende Informationen + +- „[Ein Organisationsmitglied in einen externen Mitarbeiter umwandeln](/articles/converting-an-organization-member-to-an-outside-collaborator)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..49183bfc51 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/index.md @@ -0,0 +1,28 @@ +--- +title: Zugriff auf die Repositorys Deiner Organisation verwalten +intro: Organisationsinhaber können den Zugriff von Einzelpersonen und Teams auf die Repositorys der Organisation verwalten. Team-Betreuer können den Repository-Zugriff eines Teams ebenfalls verwalten. +redirect_from: + - /articles/permission-levels-for-an-organization-repository/ + - /articles/managing-access-to-your-organization-s-repositories + - /articles/managing-access-to-your-organizations-repositories + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000..ccb1c0caff --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,39 @@ +--- +title: Den Zugriff einer Person auf ein Repository einer Organisation verwalten +intro: Du kannst den Zugriff einer Person auf ein Repository Deiner Organisation verwalten. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Personen mit Administratorberechtigungen können den Zugriff von Organisationsmitgliedern und externen Mitarbeitern auf ein Repository der Organisation verwalten. + +### Den Zugriff auf Repositorys entziehen + +Wenn Du einen Mitarbeiter aus einem Repository Deiner Organisation entfernst, verliert er seinen Lese- und Schreibzugriff auf das Repository. Wenn es sich um ein privates Repository handelt und der Mitarbeiter das Repository geforkt hat, wird dieser Fork gelöscht. Der Mitarbeiter behält jedoch alle lokalen Klone Deines Repositorys. + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +### Den Zugriff einer Person auf ein Repository einer Organisation verwalten + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Klicke auf **Members** (Mitglieder) oder **Outside collaborators** (Externe Mitarbeiter), um Benutzer mit unterschiedlichen Arten des Zugriffs zu verwalten. ![Schaltfläche zum Einladen von Mitgliedern oder externen Mitarbeitern zu einer Organisation](/assets/images/help/organizations/select-outside-collaborators.png) +5. Klicken Sie rechts neben dem Namen der Person, deren Zugriff Sie verwalten möchten, im Dropdownmenü {% octicon "gear" aria-label="The Settings gear" %} auf **Manage** (Verwalten). ![Link zur Zugriffsverwaltung](/assets/images/help/organizations/member-manage-access.png) +6. Klicke auf der Seite „Manage access“ (Zugriff verwalten) neben dem Repository auf **Manage access** (Zugriff verwalten). ![Schaltfläche „Manage Access“ (Zugriff verwalten) für ein Repository](/assets/images/help/organizations/repository-manage-access.png) +7. Überprüfe den Zugriff der Person auf ein bestimmtes Repository, z. B., ob sie ein Mitarbeiter ist oder als Teammitglied auf das Repository zugreifen kann. ![Repository-Zugriffsmatrix für den Benutzer](/assets/images/help/organizations/repository-access-matrix-for-user.png) + +### Weiterführende Informationen + +{% if currentVersion == "free-pro-team@latest" %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %} +- „[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000..7f38e490f5 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +title: Den Teamzugriff auf ein Repository einer Organisation verwalten +intro: 'Du kannst einem Team Zugriff auf ein Repository gewähren, einem Team den Zugriff auf ein Repository entziehen oder die Berechtigungsebene eines Teams für ein Repository ändern.' +redirect_from: + - /articles/managing-team-access-to-an-organization-repository-early-access-program/ + - /articles/managing-team-access-to-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Personen mit Administratorzugriff auf ein Repository können den Zugriff eines Teams auf das Repository verwalten. Team-Betreuer können einem Team den Zugriff auf ein Repository entziehen. + +{% warning %} + +**Warnungen:** +- Du kannst die Berechtigungsebene eines Teams ändern, wenn das Team direkten Zugriff auf ein Repository hat. Wenn der Zugriff des Teams auf das Repository von einem übergeordneten Team geerbt wird, musst Du den Zugriff des übergeordneten Teams auf das Repository ändern. +- Wenn Du einem übergeordneten Team den Zugriff auf ein Repository gewährst oder entziehst, erhalten oder verlieren auch die untergeordneten Teams den Zugriff auf das Repository. Weitere Informationen finden Sie unter „[Informationen zu Teams](/articles/about-teams)“. + +{% endwarning %} + +### Einem Team Zugriff auf ein Repository gewähren + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. Klicke oberhalb der Liste der Repositorys auf **Add repository** (Repository hinzufügen). ![Schaltfläche „Add repository“ (Repository hinzufügen)](/assets/images/help/organizations/add-repositories-button.png) +6. Gib den Namen des Repositorys ein, und klicke dann auf **Add repository to team** (Repository zu Team hinzufügen). ![Repository-Suchfeld](/assets/images/help/organizations/team-repositories-add.png) +7. Optional kannst Du im Dropdownmenü rechts neben dem Repository-Namen eine andere Berechtigungsebene für das Team auswählen. ![Dropdownmenü mit Zugriffsebene für Repository](/assets/images/help/organizations/team-repositories-change-permission-level.png) + +### Einem Team den Zugriff auf ein Repository entziehen + +Du kannst einem Team den Zugriff auf ein Repository entziehen, wenn das Team direkten Zugriff auf ein Repository hat. Wenn der Zugriff des Teams auf das Repository von einem übergeordneten Team geerbt wird, musst Du das Repository vom übergeordneten Team entfernen, um es auch von den untergeordneten Teams zu entfernen. + +{% 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. Wähle alle Repositorys aus, die Du vom Team entfernen möchtest. ![Liste der Team-Repositorys mit aktivierten Kontrollkästchen für einige Repositorys](/assets/images/help/teams/select-team-repositories-bulk.png) +6. Klicke im Dropdownmenü oberhalb der Liste der Repositorys auf **Remove from team** (Aus Team entfernen). ![Dropdownmenü mit Option zum Entfernen eines Repositorys von einem Team](/assets/images/help/teams/remove-team-repo-dropdown.png) +7. Prüfe die zum Entfernen ausgewählten Repositorys, und klicke auf **Remove repositories** (Repositorys entfernen). ![Modalfeld mit einer Liste der Repositorys, auf die das Team nicht mehr zugreifen kann](/assets/images/help/teams/confirm-remove-team-repos.png) + +### Weiterführende Informationen + +- „[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000..f4f44c7112 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Zugriff eines ehemaligen externen Mitarbeiters auf Deine Organisation wieder einsetzen +intro: 'You can reinstate a former outside collaborator''s access permissions for organization repositories, forks, and settings.' +redirect_from: + - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization + - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +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. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +Bei der Wiedereinsetzung eines ehemaligen externen Mitarbeiters kannst Du Folgendes wiederherstellen: + - Die früheren Zugriffsberechtigungen des Benutzers auf die Organisationsrepositorys + - Alle privaten Forks der Repositorys der Organisation + - Die Mitgliedschaft innerhalb der Organisationsteams + - Die früheren Zugriffsrechte und Berechtigungen für die Repositorys der Organisation + - Sterne für die Repositorys der Organisation + - Issue-Zuweisungen innerhalb der Organisation + - Repository-Abonnements (Benachrichtigungseinstellungen für das Beobachten, Nichtbeobachten oder Ignorieren der Repository-Aktivitäten) + +{% tip %} + +**Tips**: + - Nur der Organisationsinhaber kann den Zugriff eines externen Mitarbeiters auf seine Organisation wieder einsetzen. Weitere Informationen finden Sie unter „[Berechtigungsebenen für eine Organisation](/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" %} + - Wenn Deine Organisation ein benutzerabhängiges Abonnement abgeschlossen hat, muss eine Lizenz verfügbar sein, bevor Du ein neues Mitglied zur Organisation einladen oder ein ehemaliges Organisationsmitglied wieder einsetzen kannst. Weitere Informationen findest Du unter „[Informationen zu benutzerbasierten Preisen](/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. Klicke auf **Invite and reinstate** (Einladen und wieder einsetzen) oder auf **Invite and start fresh** (Einladen und neu beginnen), um festzulegen, ob Du den externen Mitarbeiter mit seinen früheren Zugriffsberechtigungen innerhalb der Organisation wieder einsetzen möchtest oder ob Du die früheren Berechtigungen löschen und neu festlegen möchtest. + + {% warning %} + + **Warnung:** Wenn Du einen externen Mitarbeiter in ein Mitglied Deiner Organisation umwandeln möchtest, klicke auf **Invite and start fresh** (Einladen und neu starten), und wähle eine neue Rolle für diese Person aus. Wenn Du jedoch seine Rolle und Berechtigungen neu festlegst, gehen seine privaten Forks der Repositorys der Organisation verloren. Sollen bei der Umwandlung des externen Mitarbeiters zu einem Mitglied Deiner Organisation dessen privaten Forks *erhalten bleiben*, wähle stattdessen **Invite and reinstate** (Einladen und wieder einsetzen) aus. Sobald diese Person die Einladung annimmt, kannst Du sie anschließend durch [Einladung zum Organisationsbeitritt als Mitglied](/articles/converting-an-outside-collaborator-to-an-organization-member) in ein Organisationsmitglied umwandeln. + + {% endwarning %} + + ![Auswählen, ob Einstellungen wiederhergestellt werden sollen](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Klicke auf **Add and reinstate** (Hinzufügen und wieder einsetzen) oder auf **Add and start fresh** (Hinzufügen und neu beginnen), um festzulegen, ob Du den externen Mitarbeiter mit seinen früheren Zugriffsberechtigungen innerhalb der Organisation wieder einsetzen möchtest oder ob Du die früheren Berechtigungen löschen und neu festlegen möchtest. + + {% warning %} + + **Warnung:** Wenn Du einen externen Mitarbeiter in ein Mitglied Deiner Organisation umwandeln möchtest, klicke auf **Add and start fresh** (Hinzufügen und neu beginnen), und wähle eine neue Rolle für diese Person aus. Wenn Du jedoch seine Rolle und Berechtigungen neu festlegst, gehen seine privaten Forks der Repositorys der Organisation verloren. Sollen bei der Umwandlung des externen Mitarbeiters zu einem Mitglied Deiner Organisation dessen privaten Forks *erhalten bleiben*, wähle stattdessen **Add and reinstate** (Hinzufügen und wieder einsetzen) aus. Danach kannst Du diese Person durch [Hinzufügen zur Organisation als Mitglied](/articles/converting-an-outside-collaborator-to-an-organization-member) in ein Organisationsmitglied umwandeln. + + {% endwarning %} + + ![Auswählen, ob Einstellungen wiederhergestellt werden sollen](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. Wenn Du die früheren Berechtigungen eines ehemaligen externen Mitarbeiters gelöscht hast, wähle eine neue Rolle für den Benutzer aus, und füge ihn optional zu einem oder mehreren Teams hinzu. Klicke dann auf **Send invitation** (Einladung senden). ![Rollen- und Teamoptionen und Schaltfläche „Send invitation“ (Einladung senden)](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. Wenn Du die früheren Berechtigungen eines ehemaligen externen Mitarbeiters gelöscht hast, wähle eine neue Rolle für den Benutzer aus, und füge ihn optional zu einem oder mehreren Teams hinzu. Klicke dann auf **Add member** (Mitglied hinzufügen). ![Rollen- und Teamoptionen und Schaltfläche „Add member“ (Mitglied hinzufügen)](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +8. Die eingeladene Person erhält per E-Mail eine Einladung zur Organisation. Um externer Mitarbeiter der Organisation zu werden, muss die eingeladene Person die Einladung annehmen. {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Weiterführende Informationen + +- „[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000..667ba34b47 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,57 @@ +--- +title: Externen Mitarbeiter von einem Organisationsrepository entfernen +intro: Organisationsinhaber und Repository-Administratoren können den Zugriff eines externen Mitarbeiters auf ein Repository entfernen. +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Warnung:** +- Beim Entfernen eines externen Mitarbeiters von einem privaten Repository wird die Anzahl der bezahlten Lizenzen nicht automatisch angepasst. Um nach dem Entfernen von Benutzern aus der Organisation für weniger Lizenzen zu bezahlen, folge den Schritten im Artikel „[Die bezahlten Benutzer Deiner Organisation heruntersetzen](/articles/downgrading-your-organization-s-paid-seats)." + +- Sie sind dafür verantwortlich, dass die Personen, denen Sie den Zugriff auf ein Repository entziehen, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen. + +{% endwarning %} + +{% endif %} + +Beim Entfernen eines Mitarbeiters werden zwar dessen Forks privater Repositorys gelöscht, seine lokalen Klone Deiner Repositorys behält er aber. + +### Externe Mitarbeiter von allen Repositorys einer Organisation entfernen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Wähle die externen Mitarbeiter aus, die Du aus der Organisation entfernen möchtest. ![Liste der externen Mitarbeiter mit zwei ausgewählten Mitarbeitern](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) +6. Klicke im Dropdownmenü über der Liste der externen Mitarbeiter auf **Remove from all repositories** (Von allen Repositorys entfernen). ![Dropdownmenü mit Option zum Entfernen externer Mitarbeiter ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) +7. Prüfe die Liste der externen Mitarbeiter, die aus der Organisation entfernt werden, und klicke dann auf **Remove outside collaborators** (Externe Mitarbeiter entfernen). ![Liste der externen Mitarbeiter, die entfernt werden, und Schaltfläche „Remove outside collaborators“ (Externe Mitarbeiter entfernen)](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) + +### Externen Mitarbeiter von einem bestimmten Repository einer Organisation entfernen + +Wenn Du einen externen Mitarbeiter nur von bestimmten Repositorys Deiner Organisation entfernen möchtest, kannst Du dessen Zugriff auf die einzelnen Repositorys nacheinander entziehen. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Klicken Sie rechts neben dem Benutzernamen der Person, die Sie entfernen möchten, im Dropdownmenü {% octicon "gear" aria-label="The Settings gear" %} auf **Manage** (Verwalten). ![Schaltfläche „Manage access“ (Zugriff verwalten)](/assets/images/help/organizations/member-manage-access.png) +6. Klicke rechts neben dem Repository, aus dem Du den externen Mitarbeiter entfernen möchtest, auf **Manage access** (Zugriff verwalten). ![Auswahl der Schaltfläche „Manage access“ (Zugriff verwalten) neben einem Repository, auf das der externe Mitarbeiter Zugriff hat](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) +7. Wenn Du den Zugriff des externen Mitarbeiters auf das Repository vollständig entziehen möchtest, klicke in der rechten oberen Ecke auf **Remove access to this repository** (Zugriff auf dieses Repository entfernen). ![Schaltfläche „Remove access to this repository“ (Zugriff auf dieses Repository entfernen)](/assets/images/help/organizations/remove-access-to-this-repository.png) +8. Klicke zur Bestätigung auf **Remove access** (Zugriff entfernen). ![Bestätigung des Entfernens des externen Mitarbeiters vom Repository](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) + +### Weiterführende Informationen + +- „[Externe Mitarbeiter zu Organisations-Repositorys hinzufügen](/articles/adding-outside-collaborators-to-repositories-in-your-organization)“ +- „[Ein Organisationsmitglied in einen externen Mitarbeiter umwandeln](/articles/converting-an-organization-member-to-an-outside-collaborator)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000..2e52de269e --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -0,0 +1,181 @@ +--- +title: Berechtigungsebenen für die Repositorys einer Organisation +intro: 'Den Zugriff auf die einzelnen Repositorys Deiner Organisation kannst Du durch granulare Berechtigungsebenen anpassen. Auf diese Weise kannst Du Deinen Benutzern Zugriff auf genau die Funktionen und Aufgaben gewähren, die sie tatsächlich benötigen.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Personen mit Administratorberechtigungen können den Zugriff einzelner Benutzer und Teams auf die Repositorys ihrer Organisation steuern. + +### Berechtigungsebenen für die Repositorys einer Organisation + +Du kannst Organisationsmitgliedern, externen Mitarbeitern und Teams unterschiedliche Zugriffsberechtigungen auf die Repositorys einer Organisation erteilen. Die einzelnen Berechtigungsebenen gewähren progressiv mehr Zugriffsrechte auf die Inhalte und Einstellungen eines Repositorys. Wähle die Ebene aus, die am besten zur jeweiligen Benutzer- oder Teamrolle innerhalb Deines Projekts passt, und achte darauf, den Benutzern nicht mehr als den notwendigen Zugriff auf ein Projekt zu geben. + +Vom geringsten zum umfassendsten Zugriff sind die Berechtigungsebenen für die Repositorys einer Organisation wie folgt: +- **Lesen**: Empfohlen für Mitarbeiter, die nicht zum Code beitragen, die aber Ihr Projekt anzeigen und mitsprechen möchten. +- **Triage** (Triage): Empfohlen für Mitarbeiter, die Issues und Pull Requests proaktiv verwalten müssen, aber keinen Schreibzugriff benötigen. +- **Schreiben**: Empfohlen für Mitarbeiter, die aktiv zu Ihrem Projekt beitragen. +- **Maintain** (Betreuen): Empfohlen für Projektmanager, die das Repository verwalten, aber keinen Zugriff auf sensible oder irreversible Aktionen benötigen. +- **Admin** (Verwalten): Empfohlen für Personen, die vollständigen Zugriff auf das Projekt benötigen und auch sensible oder irreversible Aktionen wie die Verwaltung der Sicherheit oder das Löschen eines Repositorys durchführen müssen + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +Weitere Informationen zum Erteilen von Zugriffsberechtigungen für Repositorys findest Du im Abschnitt „[Zugriff auf die Repositorys Deiner Organisation verwalten](/articles/managing-access-to-your-organizations-repositories).“ + +Organisationsinhaber können Basis-Berechtigungen festlegen, die für alle Mitglieder einer Organisation gelten, wenn sie auf eines der Repositorys der Organisation zugreifen. Weitere Informationen findest Du auf „[Basis-Berechtigungen für eine Organisation setzen](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." + +Organisationsinhaber können den Zugriff auf bestimmte Einstellungen und Aktionen innerhalb ihrer Organisation noch weiter einschränken. Weitere Informationen zu den Optionen für bestimmte Einstellungen findest Du im Abschnitt „[Einstellungen einer Organisation verwalten](/articles/managing-organization-settings).“ + +Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben Organisationsinhaber auch vollständigen Zugriff auf jedes Repository ihrer Organisation. Weitere Informationen finden Sie unter „[Berechtigungsebenen für eine Organisation](/articles/permission-levels-for-an-organization)". + +{% warning %} + +**Warnung:** Wenn einem Repository ein Deployment-Schlüssel hinzugefügt wird, kann jede Person, die über den privaten Schlüssel verfügt, in Abhängigkeit der Schlüsseleinstellungen aus dem Repository lesen bzw. in das Repository schreiben, selbst wenn diese Person später aus der Organisation entfernt wird. + +{% endwarning %} + +### Repository-Zugriff der einzelnen Berechtigungsebenen +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** Repository permissions required to use security features are listed in "[Permission requirements for security features](#permission-requirements-for-security-features)" below. + +{% endnote %} + +{% 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](/communities/maintaining-your-safety-on-github/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" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [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](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Blockieren von Unterhaltungen](/communities/moderating-comments-and-conversations/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" or currentVersion == "github-ae@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** | +| | | | | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **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](/communities/moderating-comments-and-conversations/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](/organizations/managing-access-to-your-organizations-repositories/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" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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" %} +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +{% endif %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +#### Permission requirements for security features + +In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_advanced_security %} features. + +| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:| +| {% if currentVersion == "free-pro-team@latest" %} | | | | | | +| 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** | +| [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.22" or currentVersion == "github-ae@latest" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Aktivieren des Abhängigkeitsdiagramms](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) für ein privates Repository | | | | | **X** | +| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| [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@3.0" or currentVersion == 'github-ae@next' %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% if currentVersion == "enterprise-server@3.0" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +[1] Repository writers and maintainers can only see alert information for their own commits. +{% endif %} +{% endif %} + +### Weiterführende Informationen + +- „[Zugriff auf die Repositorys Deiner Organisation verwalten](/articles/managing-access-to-your-organization-s-repositories)“ +- „[Externe Mitarbeiter zu Organisations-Repositorys hinzufügen](/articles/adding-outside-collaborators-to-repositories-in-your-organization)“ +- „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000..57d0c3e247 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -0,0 +1,36 @@ +--- +title: Basisberechtigungen für eine Organisation festlegen +intro: Du kannst Basisberechtigungen für die Repositorys festlegen, die einer Organisation gehören. +permissions: Organisationsinhaber können Basisberechtigungen für eine Organisation festlegen. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### Über Basisberechtigungen für eine Organisation + +Du kannst Basisberechtigungen festlegen, die für alle Mitglieder einer Organisation gelten, wenn sie auf eines der Repositorys der Organisation zugreifen. Basisberechtigungen gelten nicht für externen Mitarbeiter. + +{% if currentVersion == "free-pro-team@latest" %}By default, members of an organization will have **Read** permissions to the organization's repositories.{% endif %} + +Wenn jemand mit Administratorberechtigungen auf die Repositorys einer Organisation einem Mitglied eine höhere Berechtigungsstufe für das Repository gewährt, überschreibt die höhere Berechtigungsstufe die Basisberechtigung. + +### Basisberechtigungen festlegen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Wähle unter „Base permissions" (Basisberechtigungen) das Dropdownmenü, um neue Basisberechtigungen auszuwählen. ![Neue Berechtigungsstufe aus der Dropdownliste der Basisberechtigungen auswählen](/assets/images/help/organizations/base-permissions-drop-down.png) +6. Überprüfen Sie die Änderungen. Klicke zur Bestätigung auf **Change default permission to PERMISSION** (Ändere die Basisberechtigungen in BERECHTIGUNG). ![Überprüfen und Bestätigen der Änderung der Basisberechtigungen](/assets/images/help/organizations/base-permissions-confirm.png) + +### Weiterführende Informationen + +- „[Berechtigungsebenen für die Repositorys einer Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)“ +- „[Externe Mitarbeiter zu Organisations-Repositorys hinzufügen](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)“ diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000..ecd8f0ebdf --- /dev/null +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,41 @@ +--- +title: Personen mit Zugriff auf Dein Repository anzeigen +intro: 'Organisationsinhaber können den Zugriff von Personen auf ein Repository innerhalb einer Organisation anzeigen. Organisationsinhaber mit {% data variables.product.prodname_ghe_cloud %} oder {% data variables.product.prodname_ghe_server %} können zudem eine CSV-Liste der Personen exportieren, die auf ein Repository zugreifen können.' +redirect_from: + - /articles/viewing-people-with-access-to-your-repository + - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Anhand dieser Informationen können Administratoren außenstehende Personen unterstützen, Daten für Compliance-Zwecke erfassen und andere allgemeine Sicherheitsüberprüfungen durchführen. + +![Liste mit Berechtigungen für Personen im Repository](/assets/images/help/repository/repository-permissions-list.png) + +### Personen mit Zugriff auf Dein Repository anzeigen + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Hinweis**: Du kannst auch eine kombinierte Übersicht über Teams und Personen mit Zugriff auf Dein Repository sehen. Weitere Informationen findest Du unter „[Teams und Personen mit Zugriff auf Dein Repository verwalten](/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 %} + +### Liste der Personen mit Zugriff auf Dein Repository exportieren + +Organisationsinhaber auf {% data variables.product.prodname_ghe_cloud %} oder {% data variables.product.prodname_ghe_server %} können eine CSV-Liste der Personen exportieren, die auf ein Repository zugreifen können. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} +4. Klicke auf **Export CSV** (CSV exportieren). ![Registerkarte „People“ (Personen) auf der Repository-Seitenleiste](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000..372e70e304 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -0,0 +1,47 @@ +--- +title: Informationen zu SSH-Zertifizierungsstellen +intro: 'Mit einer SSH-Zertifizierungsstelle kann Deine Organisation oder Dein Enterprise-Konto SSH-Zertifikate bereitstellen, mit denen Mitglieder mit Git auf Deine Ressourcen zugreifen können.' +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/about-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Ein SSH-Zertifikat ist ein Mechanismus, mit dem ein SSH-Schlüssel einen anderen SSH-Schlüssel signieren kann. Wenn Du eine SSH-Zertifizierungsstelle (CA) verwendest, um den Mitgliedern Deiner Organisation signierte SSH-Zertifikate bereitzustellen, kannst Du die Zertifizierungsstelle zu Deinem Enterprise-Konto oder Deiner Organisation hinzufügen, damit die Organisationsmitglieder mit ihren Zertifikaten auf die Ressourcen der Organisation zugreifen können. Weitere Informationen findest Du unter „[SSH-Zertifizierungsstellen Deiner Organisation verwalten](/articles/managing-your-organizations-ssh-certificate-authorities).“ + +Wenn Du eine SSH-Zertifizierungsstelle zu Deiner Organisation oder Deinem Enterprise-Konto hinzugefügt hast, kannst Du mit der Zertifizierungsstelle Client-SSH-Zertifikate für Organisationsmitglieder signieren. Organisationsmitglieder können mit den signierten Zertifikaten mit Git auf die Repositorys Deiner Organisation (und nur auf diese) zugreifen. 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 %} + +Du kannst beispielsweise ein internes System einrichten, das jeden Morgen ein neues Zertifikat für Deine Entwickler herausgibt. Die Entwickler können mit ihrem aktuellen Zertifikat in den Repositorys Ihrer Organisation auf {% data variables.product.product_name %} arbeiten. Am Ende des Tages läuft das Zertifikat automatisch ab. So werden Deine Repositorys geschützt, falls das Zertifikat zu einem späteren Zeitpunkt kompromittiert wird. + +Beim Herausgeben der einzelnen Zertifikate musst Du eine Erweiterung hinzufügen, die festlegt, für welchen {% data variables.product.product_name %}-Benutzer das Zertifikat gedacht ist. Sie können z. B. den OpenSSH-Befehl `ssh-keygen` verwenden und dabei _KEY-IDENTITY_ durch Ihre Schlüssel-Identität und _USERNAME_ einen {% data variables.product.product_name %}-Benutzernamen ersetzen. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +``` + +Mit der Erweiterung `source-address` schränkst Du die IP-Adressen ein, von denen aus ein Organisationsmitglied auf die Ressourcen Deiner Organisation zugreifen kann. Als Erweiterung ist eine bestimmte IP-Adresse oder ein IP-Adressbereich mit CIDR-Notation zulässig. Sollen mehrere Adressen oder Bereiche angegeben werden, trenne sie durch Komma voneinander ab. Weitere Informationen findest Du unter „[Classless Inter-Domain Routing](https://de.wikipedia.org/wiki/Classless_Inter-Domain_Routing)“ auf Wikipedia. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +{% if currentVersion == "free-pro-team@latest" %} + +Organisationsmitglieder können ihre signierten Zertifikate selbst dann zur Authentifizierung nutzen, wenn Sie SAML Single Sign-On erzwingen. Sofern Sie die Verwendung von SSH-Zertifikaten nicht vorschreiben, können Organisationsmitglieder auch weiterhin andere Authentifizierungsmethoden verwenden, um mit Git auf die Ressourcen Ihrer Organisation zuzugreifen, z. B. ihren Benutzernamen und ihr Passwort, persönliche Zugriffstoken und ihre eigenen SSH-Schlüssel. + +{% endif %} + +Als Vorbeugung gegen Authentifizierungsfehler sollten die Organisationsmitglieder spezielle URLs einsetzen, welche die Organisations-ID enthält, wenn sie Repositorys mit signierten Zertifikaten klonen wollen. Alle Benutzer mit Lesezugriff auf das Repository finden diese URL auf der Repository-Seite. Weitere Informationen findest Du unter „[Ein Repository clonen](/articles/cloning-a-repository)“. diff --git a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..50968b61ce --- /dev/null +++ b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -0,0 +1,19 @@ +--- +title: Git-Zugriff auf die Repositorys Deiner Organisation verwalten +intro: Du kannst Deiner Organisation eine SSH-Zertifizierungsstelle (CA) hinzufügen und erlauben, dass Mitglieder über Git mit den von der SSH-Zertifizierungsstelle signierten Schlüsseln auf die Repositorys der Organisation zugreifen können. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% link_in_list /about-ssh-certificate-authorities %} +{% link_in_list /managing-your-organizations-ssh-certificate-authorities %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000..8cdaf2a9f3 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,38 @@ +--- +title: SSH-Zertifizierungsstellen Deiner Organisation verwalten +intro: Du kannst SSH-Zertifizierungsstellen zu Deiner Organisation hinzufügen oder aus dieser entfernen. +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-your-organizations-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber können die SSH-Zertifizierungsstellen (CA) einer Organisation verwalten. + +Du kannst festlegen, dass Mitglieder mithilfe der von Dir bereitgestellten SSH-Zertifikate auf die Repositorys Deiner Organisation zugreifen können, indem Du Deiner Organisation eine SSH-Zertifizierungsstelle hinzufügst. {% data reusables.organizations.can-require-ssh-cert %} Weitere Informationen findest Du unter „[Informationen zu SSH-Zertifizierungsstellen](/articles/about-ssh-certificate-authorities).“ + +### Eine SSH-Zertifizierungsstelle hinzufügen + +{% 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 %} + +### Eine SSH-Zertifizierungsstelle löschen + +{% 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/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md new file mode 100644 index 0000000000..8929f55817 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -0,0 +1,29 @@ +--- +title: Personen zu Deiner Organisation hinzufügen +intro: 'Sie können jede beliebige Person mithilfe ihres {% data variables.product.product_name %}-Benutzernamens oder ihrer E-Mail-Adresse zu einem Mitglied Ihrer Organisation machen.' +redirect_from: + - /articles/adding-people-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization +versions: + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization owners can add people to an organization.' +--- + +{% if currentVersion != "github-ae@latest" %} +Wenn Deine Organisation [die Zwei-Faktor-Authentifizierung für Mitglieder vorschreibt](/articles/requiring-two-factor-authentication-in-your-organization), müssen die Benutzer [die Zwei-Faktor-Authentifizierung aktivieren](/articles/securing-your-account-with-two-factor-authentication-2fa), bevor Du sie zur Organisation hinzufügen kannst. +{% 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 %} + +### Weiterführende Informationen +- „[Organisationsmitglieder zu einem Team hinzufügen](/articles/adding-organization-members-to-a-team)“ diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000..f5d29399c9 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,21 @@ +--- +title: Kann ich Konten für Personen in meiner Organisation erstellen? +intro: 'Zwar kannst Du Benutzer in eine von Dir erstellte Organisation hinzufügen, Du kannst aber keine persönlichen Benutzerkonten für andere Personen erstellen.' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization + - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Da der Zugriff auf eine Organisation durch die Anmeldung bei einem persönlichen Konto erfolgt, benötigt jedes Teammitglied ein persönliches Konto. Wenn Du die Benutzernamen aller Personen hast, die Du zu Deiner Organisation hinzufügen möchtest, kannst Du sie zu Teams hinzufügen. + +### Benutzer zu Deiner Organisation hinzufügen + +1. Stelle allen Personen Anleitungen zum [Erstellen eines persönlichen Kontos](/articles/signing-up-for-a-new-github-account) bereit. +2. Frage alle Personen, die Mitglied Deiner Organisation werden sollen, nach ihrem Benutzernamen. +3. [Lade die neuen persönlichen Konten zum Beitritt](/articles/inviting-users-to-join-your-organization) zu Deiner Organisation ein. Nutze [Organisationsrollen](/articles/permission-levels-for-an-organization) und [Repository-Berechtigungen](/articles/repository-permission-levels-for-an-organization), um den Zugriff der einzelnen Konten einzuschränken. diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000..c6efdbff1f --- /dev/null +++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Eine Einladung zum Beitritt zu Deiner Organisation abbrechen oder bearbeiten +intro: Organisationsinhaber können eine Einladung zum Beitritt zu Deiner Organisation jederzeit abbrechen oder bearbeiten, solange der Benutzer sie noch nicht angenommen hat. +redirect_from: + - /articles/canceling-or-editing-an-invitation-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Klicke auf der Registerkarte „People“ (Personen) auf **Pending invitation** (Ausstehende Einladung). ![Link zu ausstehender Einladung](/assets/images/help/organizations/pending-invitation-link.png) +5. Klicke neben dem Benutzernamen oder der E-Mail-Adresse der Person, deren Einladung Du bearbeiten oder stornieren möchtest, auf **Edit invitation** (Einladung bearbeiten). ![Schaltfläche „Edit invitation“ (Einladung bearbeiten)](/assets/images/help/organizations/edit-invitation-button.png) + + Möglicherweise musst Du unten im Fenster auf **View all invitations** (Alle Einladungen anzeigen) klicken, um die gewünschte Person zu finden. +6. Entscheide, ob Du die Einladung zum Beitritt zu Deiner Organisation bearbeiten oder abbrechen möchtest. ![Schaltflächen „Update invitation“ (Einladung aktualisieren) und „Cancel invitation“ (Einladung zurückziehen)](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) + - Um die Einladung des Benutzers zu bearbeiten, wähle eine andere Rolle oder ein anderes Team aus. Klicke dann auf **Update invitation** (Einladung aktualisieren). + - Um die Einladung des Benutzers abzubrechen, klicke auf **Cancel invitation** (Einladung abbrechen). + +### Weiterführende Informationen + +{% if currentVersion == "free-pro-team@latest" %} +- „[Benutzer zum Beitritt zu Deiner Organisation einladen](/articles/inviting-users-to-join-your-organization)“ +{% endif %} +- „[Organisationsmitglieder zu einem Team hinzufügen](/articles/adding-organization-members-to-a-team)“ diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/index.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/index.md new file mode 100644 index 0000000000..5a856c778a --- /dev/null +++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/index.md @@ -0,0 +1,23 @@ +--- +title: Mitgliedschaft in Deiner Organisation verwalten +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. Du kannst auch Mitglieder aus der Organisation entfernen und ehemalige Mitglieder wieder einsetzen.' +redirect_from: + - /articles/removing-a-user-from-your-organization/ + - /articles/managing-membership-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000..1b7243b394 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Benutzer zum Beitritt zu Deiner Organisation einladen +intro: 'Sie können jede beliebige Person mithilfe ihres {% data variables.product.product_name %}-Benutzernamens oder ihrer E-Mail-Adresse dazu einladen, Mitglied Ihrer Organisation zu werden.' +permissions: Organization owners can invite users to join an organization. +redirect_from: + - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ + - /articles/inviting-users-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% tip %} + +**Tips**: +- Wenn Deine Organisation ein benutzerabhängiges Abonnement abgeschlossen hat, muss eine Lizenz verfügbar sein, bevor Du ein neues Mitglied zur Organisation einladen oder ein ehemaliges Organisationsmitglied wieder einsetzen kannst. Weitere Informationen finden Sie unter „[Informationen zur benutzerabhängigen Preisgestaltung](/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](/organizations/keeping-your-organization-secure/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)." + +{% 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 %} + +### Weiterführende Informationen +- „[Organisationsmitglieder zu einem Team hinzufügen](/articles/adding-organization-members-to-a-team)“ diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000..70082a884b --- /dev/null +++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,63 @@ +--- +title: Ehemaliges Mitglied Deiner Organisation wieder einsetzen +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.' +redirect_from: + - /articles/reinstating-a-former-member-of-your-organization + - /github/setting-up-and-managing-organizations-and-teams/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. +topics: + - organisationen + - teams +--- + +### 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. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +Bei der Wiedereinsetzung eines ehemaligen Organisationsmitglieds kannst Du Folgendes wiederherstellen: + - Die Rolle des Benutzers innerhalb der Organisation + - Alle privaten Forks der Repositorys der Organisation + - Die Mitgliedschaft innerhalb der Organisationsteams + - Die früheren Zugriffsrechte und Berechtigungen für die Repositorys der Organisation + - Sterne für die Repositorys der Organisation + - Issue-Zuweisungen innerhalb der Organisation + - Repository-Abonnements (Benachrichtigungseinstellungen für das Beobachten, Nichtbeobachten oder Ignorieren der Repository-Aktivitäten) + +{% if enterpriseServerVersions contains currentVersion %} +Wenn ein Organisationsmitglied aus der Organisation entfernt wurde, weil es keine Zwei-Faktor-Authentifizierung verwendet, und Deine Organisation nach wie vor von Mitgliedern die 2FA verlangt, muss das ehemalige Mitglied die 2FA aktivieren, damit seine Mitgliedschaft wiederhergestellt werden kann. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Wenn Deine Organisation ein benutzerabhängiges Abonnement hat, muss eine ungenutzte Lizenz verfügbar sein, bevor Du ein ehemaliges Organisationsmitglied wieder einrichten kannst. Weitere Informationen finden Sie unter „[Informationen zur benutzerabhängigen Preisgestaltung](/articles/about-per-user-pricing)“. {% data reusables.organizations.org-invite-expiration %} +{% endif %} + +### Ehemaliges Mitglied Deiner Organisation wieder einsetzen + +{% 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. Klicke auf **Invite and reinstate** (Einladen und wieder einsetzen) oder auf **Invite and start fresh** (Einladen und neu beginnen), um festzulegen, ob Du die Person mit ihren früheren Zugriffsberechtigungen innerhalb der Organisation wieder einsetzen möchtest oder ob Du die früheren Berechtigungen löschen und neu festlegen möchtest. ![Auswählen, ob Informationen wiederhergestellt werden sollen](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Klicke auf **Add and reinstate** (Hinzufügen und wieder einsetzen) oder auf **Add and start fresh** (Hinzufügen und neu beginnen), um festzulegen, ob Du die Person mit ihren früheren Zugriffsberechtigungen innerhalb der Organisation wieder hinzufügen möchtest oder ob Du die früheren Berechtigungen löschen und neu festlegen möchtest. ![Auswählen, ob Berechtigungen wiederhergestellt werden sollen](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. Wenn Du die früheren Berechtigungen eines ehemaligen Organisationsmitglieds gelöscht hast, wähle eine neue Rolle für den Benutzer aus, und füge ihn optional zu einem oder mehreren Teams hinzu. Klicke dann auf **Send invitation** (Einladung senden). ![Rollen- und Teamoptionen und Schaltfläche „Send invitation“ (Einladung senden)](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. Wenn Du die früheren Berechtigungen eines ehemaligen Organisationsmitglieds gelöscht hast, wähle eine neue Rolle für den Benutzer aus, und füge ihn optional zu einem oder mehreren Teams hinzu. Klicke dann auf **Add member** (Mitglied hinzufügen). ![Rollen- und Teamoptionen und Schaltfläche „Add member“ (Mitglied hinzufügen)](/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 %} + +### Weiterführende Informationen + +- „[Ein Organisationsmitglied in einen externen Mitarbeiter umwandeln](/articles/converting-an-organization-member-to-an-outside-collaborator)“ diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000..0bc7621b84 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -0,0 +1,60 @@ +--- +title: Mitglied aus Deiner Organisation entfernen +intro: 'Wenn Mitglieder Deiner Organisation keinen Zugriff mehr auf die Repositorys Deiner Organisation benötigen, kannst Du diese Mitglieder aus der Organisation entfernen.' +redirect_from: + - /articles/removing-a-member-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Nur Organisationsinhaber können Mitglieder aus einer Organisation entfernen. + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Warning:** When you remove members from an organization: +- Die Anzahl der bezahlten Lizenzen wird nicht automatisch heruntergesetzt. Um nach dem Entfernen von Benutzern aus der Organisation für weniger Lizenzen zu bezahlen, folge den Schritten im Artikel „[Die bezahlten Benutzer Deiner Organisation heruntersetzen](/articles/downgrading-your-organization-s-paid-seats)." +- Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. Eine Synchronisation ihrer lokalen Kopien mit den Repositorys Deiner Organisation ist allerdings nicht mehr möglich. Die privaten Forks eines entfernten Benutzers können wiederhergestellt werden, wenn der Benutzer innerhalb von drei Monaten nach dem Entfernen aus der Organisation [wieder als Organisationsmitglied eingesetzt wird](/articles/reinstating-a-former-member-of-your-organization). Es untersteht Deiner Verantwortung, dafür Sorge zu tragen, dass die Personen, denen Du den Zugriff auf ein Repository entziehst, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen. +- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. + +{% endwarning %} + +{% else %} + +{% warning %} + +**Warning:** When you remove members from an organization: + - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. Eine Synchronisation ihrer lokalen Kopien mit den Repositorys Deiner Organisation ist allerdings nicht mehr möglich. Die privaten Forks eines entfernten Benutzers können wiederhergestellt werden, wenn der Benutzer innerhalb von drei Monaten nach dem Entfernen aus der Organisation [wieder als Organisationsmitglied eingesetzt wird](/articles/reinstating-a-former-member-of-your-organization). Es untersteht Deiner Verantwortung, dafür Sorge zu tragen, dass die Personen, denen Du den Zugriff auf ein Repository entziehst, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen. + - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. + +{% endwarning %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +Um einer Person, die Deine Organisation verlässt, den Umstieg zu erleichtern und sicherzustellen, dass sie vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löscht, empfehlen wir Dir die Bereitstellung einer Checkliste mit Best Practices zum Verlassen Deiner Organisation. Ein Beispiel findest Du unter „[Best Practices für das Verlassen Deines Unternehmens](/articles/best-practices-for-leaving-your-company/).“ + +{% endif %} + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} + +### Einem Benutzer die Mitgliedschaft entziehen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Wähle das oder die Mitglieder aus, die Du aus Deiner Organisation entfernen möchtest. ![Liste der Mitglieder mit zwei ausgewählten Mitgliedern](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Klicke im Dropdownmenü über der Mitgliederliste auf **Remove from organization** (Aus Organisation entfernen). ![Dropdownmenü mit Option zum Entfernen von Mitgliedern](/assets/images/help/teams/user-bulk-management-options.png) +6. Prüfe die zum Entfernen ausgewählten Mitglieder, und klicke auf **Remove members** (Mitglieder entfernen). ![Liste der zu entfernenden Mitglieder und Schaltfläche „Remove members" (Mitglieder entfernen)](/assets/images/help/teams/confirm-remove-members-bulk.png) + +### Weiterführende Informationen + +- „[Organisationsmitglieder aus einem Team entfernen](/articles/removing-organization-members-from-a-team)“ diff --git a/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000..84d10f4ed1 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Personen das Löschen von Issues in Deiner Organisation erlauben +intro: Organisationsinhaber können es bestimmten Personen erlauben, Issues in Repositorys zu löschen, die Deiner Organisation gehören. +redirect_from: + - /articles/allowing-people-to-delete-issues-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Standardmäßig können Issues in den Repositorys einer Organisation nicht gelöscht werden. Ein Organisationsinhaber muss diese Funktion erst für alle Repositorys der Organisation aktivieren. + +Nach der Aktivierung können Organisationsinhaber und Personen mit Administratorberechtigungen für ein Repository der Organisation Issues löschen. Zu den Personen mit Administratorberechtigungen für ein Repository gehören Organisationsmitglieder und externe Mitarbeiter mit Administratorberechtigungen. Weitere Informationen findest Du unter „[Repository-Berechtigungsebenen für eine Organisation](/articles/repository-permission-levels-for-an-organization/)“ und „[Einen Issue löschen](/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. Wähle unter „Issue deletion“ (Issue-Löschung) die Option **Allow members to delete issues for this organization** (Mitgliedern das Löschen von Issues für diese Organisation erlauben) aus. ![Kontrollkästchen, um Personen das Löschen von Issues zu erlauben](/assets/images/help/settings/issue-deletion.png) +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000..23263fef05 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,24 @@ +--- +title: Die Sichtbarkeit der Abhängigkeiten-Einblicke Deiner Organisation ändern +intro: Du kannst die Anzeige der Abhängigkeiten-Einblicke Deiner Organisation allen Organisationsmitgliedern gestatten oder sie auf Organisationsinhaber beschränken. +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/changing-the-visibility-of-your-organizations-dependency-insights + - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber können Einschränkungen für die Anzeige der Abhängigkeiten-Einblicke der Organisation festlegen. Standardmäßig können alle Mitglieder einer Organisation die Abhängigkeiten-Einblicke der Organisation anzeigen. + +Enterprise-Inhaber können Einschränkungen für die Anzeige der Abhängigkeiten-Einblicke aller Organisationen im Enterprise-Konto festlegen. Weitere Informationen findest Du unter „[Eine Richtlinie für Abhängigkeiten-Einblicke in Deinem Enterprise-Konto erzwingen](/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. Aktiviere oder deaktiviere unter „Member organization permissions“ (Berechtigungen für Organisationsmitglieder) die Option **Allow members to view dependency insights** (Mitgliedern die Anzeige von Abhängigkeiten-Einblicke erlauben). ![Kontrollkästchen, um Mitgliedern die Anzeige von Einblicken zu gestatten](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000..474469006e --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,22 @@ +--- +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.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} +{% data reusables.organizations.settings-sidebar-actions %} +{% data reusables.github-actions.change-retention-period-for-artifacts-logs %} diff --git a/translations/de-DE/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/de-DE/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000..07c95c3793 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -0,0 +1,33 @@ +--- +title: Eine Organisation in einen Benutzer umwandeln +intro: 'Es ist nicht möglich, eine Organisation in einen Benutzer umzuwandeln. Du kannst jedoch ein neues Benutzerkonto erstellen und die Repositorys der Organisation in das Konto übertragen.' +redirect_from: + - /articles/converting-an-organization-into-a-user + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +1. [Registriere Dich](/articles/signing-up-for-a-new-github-account) für ein neues GitHub-Benutzerkonto. +2. [Ändere die Rolle des Benutzers in einen Inhaber](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} beim neuen Benutzerkonto an. +4. [Übertrage jedes Repository der Organisation](/articles/how-to-transfer-a-repository) in das neue Benutzerkonto. +5. [Lösche die Organisation](/articles/deleting-an-organization-account). +6. [Ändere den Namen des Benutzers](/articles/changing-your-github-username) in den der Organisation. + +{% else %} + +1. Registriere Dich für ein neues GitHub Enterprise-Benutzerkonto. +2. [Ändere die Rolle des Benutzers in einen Inhaber](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} beim neuen Benutzerkonto an. +4. [Übertrage jedes Repository der Organisation](/articles/how-to-transfer-a-repository) in das neue Benutzerkonto. +5. [Lösche die Organisation](/articles/deleting-an-organization-account). +6. [Ändere den Namen des Benutzers](/articles/changing-your-github-username) in den der Organisation. + +{% endif %} diff --git a/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md new file mode 100644 index 0000000000..2e5511a957 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -0,0 +1,34 @@ +--- +title: Organisationskonto löschen +intro: 'Wenn Du eine Organisation löschst, werden alle Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Projekt- respektive Organisationsseiten ebenfalls gelöscht. {% 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 %}' +redirect_from: + - /articles/deleting-an-organization-account + - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**Tipp:** Wenn Du Dein bezahltes Abonnement stornieren möchtest, kannst Du [Deine Organisation zu {% data variables.product.prodname_free_team %} herabstufen](/articles/downgrading-your-github-subscription), anstatt die Organisation und ihre Inhalte zu löschen. + +{% endtip %} + +{% endif %} + +### 1. Sichere die Inhalte Deiner Organisation + +Wenn Du eine Organisation gelöscht hast, kann GitHub **Deine Inhalte nicht wiederherstellen.**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. + +### 2. Lösche die Organisation + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Klicke fast am Ende der Seite mit den Einstellungen der Organisation auf **Delete this organization** (Diese Organisation löschen). ![Schaltfläche „Delete this organization“ (Diese Organisation löschen)](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000..bc5a9122b2 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,85 @@ +--- +title: GitHub Actions für Deine Organisation Deaktivieren oder Einschränken +intro: 'Organisationsinhaber können GitHub Actions für eine Organisation deaktivieren, aktivieren oder einschränken.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Über {% data variables.product.prodname_actions %}-Berechtigungen für Deine Organisation + +{% data reusables.github-actions.disabling-github-actions %} Weitere Informationen zu {% data variables.product.prodname_actions %} findest Du unter „[Über {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." + +Du kannst {% data variables.product.prodname_actions %} für alle Repositories in Deiner Organisation aktivieren. {% data reusables.github-actions.enabled-actions-description %} Du kannst {% data variables.product.prodname_actions %} für alle Repositorys in Deiner Organisation deaktivieren. {% data reusables.github-actions.disabled-actions-description %} + +Alternativ kannst Du {% data variables.product.prodname_actions %} für alle Repository in Deiner Organisation aktivieren, aber die Aktionen limitieren, die ein Workflow ausführen kann. {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### {% data variables.product.prodname_actions %}-Berechtigungen für Deine Organisation verwalten + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Under **Local and third-party Actions**, select an option. ![Aktiviere, deaktiviere oder limitiere die Aktionen für diese Organisation](/assets/images/help/repository/enable-org-actions.png) +1. Klicke auf **Save** (Speichern). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### {% data variables.product.prodname_actions %}-Berechtigungen für Deine Organisation verwalten + +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 %} + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Under **Policies**, select an option. ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png) +1. Klicke auf **Save** (Speichern). + +### Allowing specific actions to run + +{% 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. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Klicke auf **Save** (Speichern). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling workflows for private repository forks + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configuring the private fork policy for an organization + +{% 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/de-DE/content/organizations/managing-organization-settings/index.md b/translations/de-DE/content/organizations/managing-organization-settings/index.md new file mode 100644 index 0000000000..997c30187c --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/index.md @@ -0,0 +1,39 @@ +--- +title: Organisationseinstellungen verwalten +intro: 'Organisationsadministratoren können mehrere Einstellungen ändern, beispielsweise die Namen der Repositorys der Organisation und die Mitgliedschaft im Inhaberteam. Darüber hinaus können Organisationsadministratoren die Organisation und alle ihre Repositorys löschen.' +redirect_from: + - /articles/managing-organization-settings + - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 /entering-a-data-protection-agreement-with-github-for-gdpr-compliance %} +{% 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 /managing-the-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 %} diff --git a/translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000..9c76604442 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,26 @@ +--- +title: Jira in das Projektboard Deiner Organisation integrieren +intro: 'Du kannst Jira Cloud in das Konto Deiner Organisation integrieren, um Commits und Pull Requests zu scannen und relevante Metadaten und Hyperlinks in allen erwähnten Jira-Issues zu erstellen.' +redirect_from: + - /articles/integrating-jira-with-your-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. Klicke auf der linken Seitenleiste unter **Organization settings** (Organisationseinstellungen) auf den Namen Deiner Organisation. ![Organisationsname in Seitenleiste](/assets/images/help/settings/organization-settings-from-sidebar.png) +3. Klicke auf der linken Seitenleiste unter **Developer settings** (Entwicklereinstellungen) auf **OAuth applications** (OAuth-Anwendungen). ![Registerkarte „OAuth applications“ (OAuth-Anwendungen) in der linken Seitenleiste](/assets/images/help/organizations/org-oauth-applications-ghe.png) +4. Klicke auf **Register a new application** (Eine neue Anwendung registrieren). +5. Gib unter **Application name** (Anwendungsname) „Jira“ ein. +6. Gib unter **Homepage URL** (URL für Startseite) die vollständige URL Deiner Jira-Instanz ein. +7. Gib unter **Authorization callback URL** (Autorisierungs-Callback-URL) die vollständige URL Deiner Jira-Instanz ein. +8. Klicke auf **Register application** (Anwendung registrieren). ![Schaltfläche „Register application“ (Anwendung registrieren)](/assets/images/help/oauth/register-application-button.png) +9. Notiere Dir unter **Organization owned applications** (Anwendungen im Besitz der Organisation) die Werte für „Client ID“ (Client-ID) und „Client Secret“ (Client-Geheimnis). ![Client-ID und Client-Geheimnis](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### Weiterführende Informationen + +- [„Jira in Deine persönlichen Projekte integrieren“](/articles/integrating-jira-with-your-personal-projects) +- Jira Cloud mit GitHub verbinden (Atlassian-Dokumentation) diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..4b7f8af41c --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,67 @@ +--- +title: Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten +intro: Du kannst die Kennzeichnungen anpassen, die in jedem neuen Repository Deiner Organisation enthalten sind. +redirect_from: + - /articles/managing-default-labels-for-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber können die Standardkennzeichnungen für Repositorys in der Organisation verwalten. + +Standardkennzeichnungen sind in jedem neuen Repository Deiner Organisation beinhaltet, aber jeder mit Schreibzugriff auf das Repository kann die Kennzeichnungen in diesem Repository später bearbeiten oder löschen. Standardkennzeichnungen hinzuzufügen, zu bearbeiten oder zu löschen wird diese Kennzeichnungen für bestehende Repositorys weder hinzufügen noch bearbeiten oder löschen. + +### Eine Standardkennzeichnung erstellen + +{% 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. Klicke unter „Repository labels" (Repository-Kennzeichnungen) auf **New label** (neue Kennzeichnung). ![Schaltfläche „New label" (Neue Kennzeichnung)](/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 %} + +### Eine Standardkennzeichnung bearbeiten + +{% 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 %} + +### Eine Standardkennzeichnung löschen + +{% 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 %} + +### Weiterführende Informationen + +- „[Informationen zu Kennzeichnungen](/articles/about-labels)“ diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..f18b1926c8 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,30 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% 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. Klicke auf **Save** (Speichern). !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png) + +### Weiterführende Informationen + +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000..898d68fb41 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,66 @@ +--- +title: Geplante Erinnerungen für Deine Organisation verwalten +intro: Du kannst in Slack Erinnerungen für alle Pull Requests erhalten, für die Teams in Deiner Organisation zum Review angefordert wurden. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +### Über geplante Erinnerungen für Pull Requests + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Organisationsinhaber können Erinnerungen für eines oder mehrere Teams in ihrer Organisation planen, für alle Pull Requests, für welche ein Team oder Teams zum Review angefordert wurde(n). + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Eine geplante Erinnerung für eine Organisation erstellen +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/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. Klicke unter „Filter by team assigned to review code" (Filtere nach Team, das für Code-Review zugewiesen ist) auf das Dropdownmenü **Add a team** (Team hinzufügen) und wähle eines oder mehrere Teams aus. Du kannst bis zu 100 Teams auswählen. Wenn das ausgewählte Team keinen Zugriff auf die oben ausgewählten "Tracked Repositories" (verfolgte Repositorys) hat, kannst Du die geplante Erinnerung nicht erstellen. ![Dropdownmenü „Add a team" (Ein Team hinzufügen)](/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 %} + +### Geplante Erinnerungen für eine Organisation verwalten +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Geplante Erinnerungen für eine Organisation löschen +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.delete %} + +### Weiterführende Informationen + +- „[Deine geplanten Erinnerungen verwalten](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" +- „[Geplante Erinnerungen für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..3986f41bf8 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Managing the default branch name for repositories in your organization +intro: 'You can set the default branch name for repositories that members create in your organization.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +permissions: Managing the default branch name for your repositories +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### About the default branch name + +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. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization 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 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)." + +### Setting the default branch name + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. Under "Repository default branch", click **Change default branch name now**. ![Override button](/assets/images/help/organizations/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png) +5. Klicke auf **Update** (Aktualisieren). ![Update button](/assets/images/help/organizations/repo-default-name-update.png) + +### Weiterführende Informationen + +- /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000..18ec83f029 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,28 @@ +--- +title: Anzeige der Mitgliedsnamen in Deiner Organisation verwalten +intro: Du kannst festlegen, dass Mitglieder Deiner Organisation den Profilnamen eines Kommentarverfassers in privaten Repositorys in der Organisation anzeigen können. +product: '{% data reusables.gated-features.display-names %}' +redirect_from: + - /articles/managing-the-display-of-member-names-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber können die Anzeige der Mitgliedsnamen in einer Organisation verwalten. + +![Im Kommentar angezeigter Profilname des Verfassers](/assets/images/help/issues/commenter-full-name.png) + +Jedes Organisationsmitglied kann seinen eigenen Profilnamen in seinen Einstellungen wählen. Weitere Informationen findest Du unter „[Dein Profil personalisieren](/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. Aktiviere oder deaktiviere unter „Admin repository permissions“ (Repository-Administratorberechtigungen) die Option **Allow members to see comment author's profile name in private repositories** (Mitgliedern erlauben, den Profilnamen des Kommentarverfassers in privaten Repositorys anzuzeigen). ![Kontrollkästchen zum Festlegen, dass Mitglieder den vollständigen Namen des Kommentarverfassers in privaten Repositorys anzeigen können](/assets/images/help/organizations/allow-members-to-view-full-names.png) +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000..230c9450cf --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Die Forking-Richtlinie für Deine Organisation verwalten +intro: 'You can can allow or prevent the forking of any private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories owned by your organization.' +redirect_from: + - /articles/allowing-people-to-fork-private-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization +permissions: Organisationsinhaber können die Forking-Richtlinie für eine Organisation verwalten. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +By default, new organizations are configured to disallow the forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories. + +If you allow forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository. Weitere Informationen findest Du unter „[Die Forking-Richtlinie für Dein Repository verwalten](/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. Wähle unter „Repository forking" (Forken eines Repositorys) die Option **Allow forking of private repositories** (das Forken von privaten Repositorys zulassen) oder die Option **Allow forking of private and internal repositories** (Forking von privaten und internen Repositorys zulassen). ![Kontrollkästchen, um das Forking in der Organisation zu erlauben oder zu verbieten](/assets/images/help/repository/allow-disable-forking-organization.png) +6. Klicke auf **Save** (Speichern). + +### Weiterführende Informationen + +- „[Informationen zu Forks](/articles/about-forks)“ +- „[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..a9814c10a9 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization +topics: + - organisationen + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-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 %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Klicke auf **Save** (Speichern). + +### Weiterführende Informationen + +- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..502e257a83 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,28 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +topics: + - organisationen + - teams +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +The developers and organizations that your organization sponsors can send you updates about their work. You can manage the email address that receives these updates. + +You can also disable updates from accounts your organization sponsors. Weitere Informationen finden Sie unter „[Sponsoring verwalten](/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. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. Klicke auf **Update profile** (Profil aktualisieren). ![Schaltfläche „Update profile" (Aktualisieren des Profils)](/assets/images/help/organizations/update-profile-button.png) + +### Weiterführende Informationen + +- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" diff --git a/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md new file mode 100644 index 0000000000..4fa0ad0e64 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -0,0 +1,50 @@ +--- +title: Organisation umbenennen +intro: 'Wenn sich der Name Deines Projekts oder Deines Unternehmens geändert hat, kannst Du den Namen Deiner Organisation entsprechend anpassen.' +redirect_from: + - /articles/what-happens-when-i-change-my-organization-s-name/ + - /articles/renaming-an-organization + - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% tip %} + +**Tipp:** Nur Organisationsinhaber können ihre Organisation umbenennen. {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +### Was geschieht, wenn ich den Namen meiner Organisation ändere? + +Nach der Änderung Deines Organisationsnamens wird Dein alter Organisationsname frei, und jemand anders kann diesen Namen für sich beanspruchen. Die meisten Referenzen auf Deine Repositorys unter dem alten Organisationsnamen werden nach einer Änderung Deines Organisationsnamens automatisch dem neuen Namen angepasst. Einige Links auf Dein Profil werden jedoch nicht automatisch weitergeleitet. + +#### Automatische Änderungen + +- {% data variables.product.prodname_dotcom %} leitet Referenzen auf Ihre Repositorys automatisch weiter. Weblinks auf bestehende **Repositorys** Deiner Organisation funktionieren weiterhin. Allerdings kann diese Anpassung nach der Veranlassung der Änderung einige Minuten dauern. +- Du kannst Deine lokalen Repositorys weiterhin mittels Push auf die bisherige Remote-Tracking-URL übertragen, ohne diese zu aktualisieren. Jedoch wird nach einer Änderung des Organisationsnamens die Aktualiserung der URLs aller vorhandenen Remote-Repositorys empfohlen. Schließlich kann Dein alter Organisationsname nach dessen Änderung von jemand anderem verwendet werden, und es ist durchaus möglich, dass Repositorys einer neuen Organisation mit gleichem Namen die Weiterleitungseinträge für Deine Repositorys überschreiben. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +- Bisherige Git-Commits werden den Benutzern Deiner Organisation korrekt zugeordnet. + +#### Änderungen, die nicht automatisch erfolgen + +Nach der Änderung Deines Organisationsnamens können folgende Probleme auftreten: +- Links auf die bisherige Profilseite Ihrer Organisation, wie `https://{% data variables.command_line.backticks %}/previousorgname`, geben einen 404-Fehler zurück. 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 %}. +- API-Anforderungen mit dem alten Organisationsnamen geben einen 404-Fehler zurück. Wir empfehlen Dir die Aktualisierung Deines alten Organisationsnamens in Deinen API-Anforderungen. +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} + +### Namen Deiner Organisation ändern + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Klicke nahe am Ende der Einstellungsseite unter „Rename organization“ (Organisation umbenennen) auf **Rename Organization** (Organisation umbenennen). ![Schaltfläche „Rename Organization“ (Organisation umbenennen)](/assets/images/help/settings/settings-rename-organization.png) + +### Weiterführende Informationen + +* „[Warum sind meine Commits mit dem falschen Benutzer verknüpft?](/articles/why-are-my-commits-linked-to-the-wrong-user)“ diff --git a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000..af3e95fde9 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,35 @@ +--- +title: Repository-Erstellung in Deiner Organisation einschränken +intro: 'Zum Schutz Deiner Organisationsdaten kannst Du die Berechtigungen für die Erstellung von Repositorys innerhalb Deiner Organisation konfigurieren.' +redirect_from: + - /articles/restricting-repository-creation-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Du kannst wählen, ob Mitglieder in Deiner Organisation Repositorys erstellen können. 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)." + +Organisationsinhaber können immer jede Art von Repository erstellen. + +{% 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 %} + +{% warning %} + +**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/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. Under "Repository creation", select one or more options. ![Optionen für die Repository-Erstellung](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..5372c541d5 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Sichtbarkeitsänderungen von Repositorys in Deiner Organisation einschränken +intro: 'Zum Schutz Deiner Organisationsdaten kannst Du die Berechtigungen für die Änderung der Sichtbarkeit von Repositorys in Deiner Organisation konfigurieren.' +redirect_from: + - /articles/restricting-repository-visibility-changes-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +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 %} + +**Warning**: If enabled, this setting allows people with admin permissions to change an existing repository to any visibility, even if you do not allow that type of repository to be created. For more information about restricting the visibility of repositories during creation, see "[Restricting repository creation in your organization](/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. Deaktiviere unter „Repository visibility change“ (Änderung der Sichtbarkeit von Repositorys) das Kontrollkästchen **Allow members to change repository visibilities for this organization** (Mitgliedern die Änderung der Sichtbarkeit von Repositorys für diese Organisation erlauben). ![Kontrollkästchen zur Erlaubnis der Änderung der Sichtbarkeit von Repositorys durch Mitglieder](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) +6. Klicke auf **Save** (Speichern). + +### Weiterführende Informationen + +- „[Über Sichtbarkeit von Repositorys](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000..5eb0b3cb5e --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,28 @@ +--- +title: Berechtigungen für das Hinzufügen von externen Mitarbeitern festlegen +intro: 'Zum Schutz Deiner Organisationsdaten und der Anzahl der bezahlten Lizenzen in Deiner Organisation kannst Du es ausschließlich Inhabern erlauben, externe Mitarbeiter zu Organisations-Repositorys einzuladen.' +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber und Mitglieder mit Administratorberechtigungen für ein Repository können externe Mitarbeiter einladen, an dem Repository zu arbeiten. Du kannst das Recht, externe Mitarbeiter einzuladen, auf ausschließlich Organisationsinhaber einschränken. + +{% 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. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %} +![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %} +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000..bfbd3f1297 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,24 @@ +--- +title: Berechtigungen zum Löschen oder Übertragen von Repositorys festlegen +intro: 'Du kannst Organisationsmitgliedern mit Administratorberechtigungen für ein Repository das Löschen oder Übertragen des Repositorys erlauben oder Du kannst diese Berechtigung allein auf Organisationsinhaber beschränken.' +redirect_from: + - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ + - /articles/setting-permissions-for-deleting-or-transferring-repositories + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Inhaber können die Berechtigungen zum Löschen oder Übertragen von Repositorys innerhalb einer Organisation festlegen. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Aktiviere oder deaktiviere unter „Repository deletion and transfer“ (Löschen und Übertragen von Repositorys) das Kontrollkästchen **Allow members to delete or transfer repositories for this organization** (Mitgliedern das Löschen oder Übertragen von Repositorys für diese Organisation erlauben). ![Kontrollkästchen zur Erlaubnis des Löschens von Repositorys durch Mitglieder](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000..b57690064a --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Berechtigungen für die Teamerstellung in Deiner Organisation festlegen +intro: Du kannst allen Organisationsmitgliedern erlauben, Teams zu erstellen, oder Du kannst die Möglichkeit der Teamerstellung auf Organisationsinhaber beschränken. +redirect_from: + - /articles/setting-team-creation-permissions-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber können die Berechtigungen für die Teamerstellung festlegen. + +Wenn Du keine Berechtigungen für die Teamerstellung festlegst, dürfen standardmäßig alle Organisationsmitglieder Teams erstellen. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Aktiviere oder deaktiviere unter „Team creation rules“ (Regeln für die Teamerstellung) das Kontrollkästchen **Allow members to create teams** (Mitgliedern die Erstellung von Teams erlauben). ![Kontrollkästchen zur Erlaubnis der Teamerstellung durch Mitglieder](/assets/images/help/organizations/allow-members-to-create-teams.png) +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md new file mode 100644 index 0000000000..6db0c91edd --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -0,0 +1,29 @@ +--- +title: Inhaberschaft an einer Organisation übertragen +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.' +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership + - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +1. Wenn Du das einige Mitglied mit *Inhaber*-Berechtigungen bist, gib einem anderen Organisationsmitglied ebenfalls die Inhaberrolle. Weitere Informationen findest Du unter „[Ernennung eines Organisationsinhabers](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)." +2. Kontaktiere den neuen Inhaber, um sicherzustellen, dass dieser [auf die Organisationseinstellungen zugreifen kann](/articles/accessing-your-organization-s-settings). +{% if currentVersion == "free-pro-team@latest" %} +3. Wenn Du derzeit in Deiner Organisation für die Zahlung der Nutzung von GitHub verantwortlich bist, bitte den neuen Inhaber oder einen [Abrechnungsmanager](/articles/adding-a-billing-manager-to-your-organization/), die Zahlungsinformationen der Organisation zu aktualisieren. Weitere Informationen finden Sie unter „[Zahlungsmethode hinzufügen oder bearbeiten](/articles/adding-or-editing-a-payment-method)“. + + {% warning %} + + **Warnung**: Wenn Du Dich selbst aus der Organisation löschst, werden die für Dein Organisationskonto hinterlegten Abrechnungsinformationen **nicht** automatisch aktualisiert. Der neue Inhaber oder ein Abrechnungsmanager muss die hinterlegten Abrechnungsinformationen aktualisieren, um Deine Kreditkarten- oder PayPal-Daten zu entfernen. + + {% endwarning %} + +{% endif %} +4. [Lösche Dich](/articles/removing-yourself-from-an-organization) aus der Organisation. diff --git a/translations/de-DE/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/de-DE/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000..d4ac453c23 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,24 @@ +--- +title: Auf Unternehmensnutzungsbedingungen umsteigen +intro: Organisationen können ein Hochstufen von den Standardnutzungsbedingungen auf die Unternehmensnutzungsbedingungen vornehmen. +redirect_from: + - /articles/upgrading-to-the-corporate-terms-of-service + - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Die Standardnutzungsbedingungen sind eine Vereinbarung zwischen {% data variables.product.prodname_dotcom %} und Ihnen als Einzelperson. Um im Auftrag einer Entität, beispielsweise eines Unternehmens, einer gemeinnützigen Organisation oder einer Gruppe, eine Vereinbarung mit {% data variables.product.prodname_dotcom %} abzuschließen, können Organisationsinhaber ein Hochstufen auf die Unternehmensnutzungsbedingungen vornehmen. + +1. Wende Dich an {% data variables.contact.contact_support %}, um ein Hochstufen auf die Unternehmensnutzungsbedingungen anzufordern. Dadurch wird ein Banner im Dashboard Ihrer Organisation aktiviert, wodurch Sie die Unternehmensnutzungsbedingungen akzeptieren können. +{% data reusables.dashboard.access-org-dashboard %} +3. Klicke im oberen Bereich der Seite rechts neben dem Banner „Terms of Service“ (Nutzungsbedingungen) auf **Sign now** (Jetzt unterschreiben). ![Schaltfläche „Sign now“ (Jetzt unterschreiben)](/assets/images/help/organizations/sign-now-button.png) +4. Lies die Informationen zu den Unternehmensnutzungsbedingungen. Wähle anschließend **Yes, I want to sign these terms on behalf of my business** (Ja, ich möchte diese Nutzungsbedingungen im Auftrag meines Unternehmens unterschreiben). ![Kontrollkästchen für die Unterschrift im Auftrag Deines Unternehmens](/assets/images/help/organizations/sign-on-behalf-business.png) +5. Gib den Namen des Unternehmens, der gemeinnützigen Organisation oder der Gruppe ein, der das Organisationskonto gehört. Hierbei handelt es sich um die Entität, welche eine Vereinbarung mit {% data variables.product.prodname_dotcom %} abschließt. ![Feld für Unternehmensnamen](/assets/images/help/organizations/business-name-field.png) +6. Klicke auf **Accept terms** (Nutzungsbedingungen akzeptieren), um den Unternehmensnutzungsbedingungen im Auftrag Deiner Entität zuzustimmen. ![Schaltfläche „Accept terms“ (Nutzungsbedingungen akzeptieren)](/assets/images/help/organizations/accept-terms-button.png) + +### Weiterführende Informationen +- „[Unternehmensnutzungsbedingungen für GitHub](/articles/github-corporate-terms-of-service/)“ diff --git a/translations/de-DE/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md b/translations/de-DE/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md new file mode 100644 index 0000000000..2dac35a1f6 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md @@ -0,0 +1,42 @@ +--- +title: Domänen Deiner Organisation überprüfen +intro: 'Sie können die von Ihrer Organisation gesteuerten Domains überprüfen, um die Identität Ihrer Organisation auf {% data variables.product.product_name %} zu bestätigen.' +redirect_from: + - /articles/verifying-your-organization-s-domain + - /articles/verifying-your-organizations-domain + - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +### About domain verification + +Um Domänen auf {% data variables.product.product_name %} zu verifizieren, musst Du in der Organisation über Inhaberberechtigungen verfügen. Weitere Informationen finden Sie unter „[Berechtigungsebenen für eine Organisation](/articles/permission-levels-for-an-organization)". Darüber hinaus benötigst Du Zugriff, um die Domänen-Einträge mit Deinem Domänen-Hosting-Dienst zu ändern. + +Nachdem Du die Inhaberschaft der Domains Deiner Organisation verifiziert hast, wird im Profil der Organisation der Badge „Verified“ (Verifiziert) angezeigt. Wenn Ihre Organisation in {% data variables.product.prodname_ghe_cloud %} vorhanden ist und den Unternehmensnutzungsbedingungen zugestimmt hat, können Organisationsinhaber die Identität der Organisationsmitglieder verifizieren, indem sie die E-Mail-Adresse der jeweiligen Mitglieder in der verifizierten Domain anzeigen. Weitere Informationen findest Du unter „[Informationen zum Profil Deiner Organisation](/articles/about-your-organization-s-profile/)“ und „[Auf Unternehmensnutzungsbedingungen umsteigen](/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)." + +{% data reusables.organizations.verified-domains-details %} + +Auf {% data variables.product.prodname_ghe_cloud %} können Sie nach dem Verifizieren der Inhaberschaft der Domain Ihrer Organisation E-Mail-Benachrichtigungen für die Organisation auf diese Domain beschränken. Weitere Informationen findest Du unter „[E-Mail-Benachrichtigungen auf eine genehmigte Domäne beschränken](/articles/restricting-email-notifications-to-an-approved-domain).“ + +### Domänen Deiner Organisation überprüfen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +5. Klicke auf **Add a domain** (Domäne hinzufügen). ![Schaltfläche „Add a domain“ (Domäne hinzufügen)](/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. In der Befehlsausgabe sollte Ihr neuer TXT-Eintrag aufgelistet werden. + ```shell + $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT + ``` +8. Nachdem Sie bestätigt haben, dass Ihrem DNS-Eintrag der TXT-Eintrag hinzugefügt wurde, sollten Sie in den Einstellungen Ihrer Organisation zur Registerkarte „Verified domains“ (Verifizierte Domains) navigieren. Sie können die Schritte eins bis vier durchführen, um nach der Registerkarte für verifizierte Domains zu suchen. ![Seite mit Einstellungen zu verifizierten Domains mit ausstehender Domain](/assets/images/help/organizations/pending-domain-verification.png) +{% data reusables.organizations.continue-verifying-domain %} +11. Sobald der Badge „Verified“ (Verifiziert) auf der Profilseite Ihrer Organisation sichtbar ist, können Sie den TXT-Eintrag im Domain-Hosting-Dienst optional aus dem DNS-Eintrag löschen.![Badge „Verified“ (Verifiziert)](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000..5028d49396 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,57 @@ +--- +title: Abrechnungsmanager zu Deine Organisation hinzufügen +intro: 'Ein *Abrechnungsmanager* ist ein Benutzer, der die Abrechnungseinstellungen für Deine Organisation verwaltet. Er aktualisiert beispielsweise die Zahlungsinformationen. Es ist eine hilfreiche Option, wenn normale Mitglieder Deiner Organisation typischerweise keinen Zugriff auf Abrechnungsressourcen haben.' +redirect_from: + - /articles/adding-a-billing-manager-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams + - Abrechnung +--- + +Mitglieder vom Team des Inhabers Deiner Organisation können anderen Benutzern *Abrechnungsmanager*-Berechtigungen zuweisen. Wenn ein Benutzer die Einladung, Abrechnungsmanager zu werden, annimmt, kann er weitere Benutzer einladen, Abrechnungsmanager zu werden. + +{% note %} + +**Hinweis:** Abrechnungsmanager nutzen keine bezahlte Lizenz im Abonnement Deiner Organisation. + +{% endnote %} + +### Berechtigungen für Abrechnungsmanager + +Abrechnungsmanager können + +- Das Konto herauf- oder herabstufen, +- Zahlungsmethoden hinzufügen, aktualisieren oder entfernen, +- Den Zahlungsverlauf anzeigen, +- Quittungen herunterladen, +- Abrechnungsmanager anzeigen, einladen und entfernen. + +Zusätzlich erhalten alle Abrechnungsmanager am Abrechnungsdatum der Organisation per E-Mail Abrechnungsquittungen. + +Abrechnungsmanager können **nicht** + +- Repositorys in Deinen Organisationen erstellen oder auf sie zugreifen, +- Die privaten Mitglieder Deiner Organisation sehen, +- In der Liste der Mitglieder der Organisation gesehen werden, +- Abonnements für {% data variables.product.prodname_marketplace %}-Apps erwerben, bearbeiten oder stornieren. + +{% tip %} + +**Tipp:** Wenn Deine Organisation [die Zwei-Faktor-Authentifizierung für Mitglieder, Abrechnungsmanager und externe Mitarbeiter vorschreibt](/articles/requiring-two-factor-authentication-in-your-organization), muss der Benutzer die Zwei-Faktor-Authentifizierung aktivieren, bevor er Deine Einladung, Abrechnungsmanager für die Organisation zu werden, annehmen kann. + +{% endtip %} + +### Abrechnungsmanager einladen + +Der eingeladene Benutzer erhält eine Einladungs-E-Mail, in der er darum gebeten wird, Abrechnungsmanager für Deine Organisation zu werden. Wenn der eingeladene Benutzer in der E-Mail auf den Link zum Annehmen der Einladung klickt, wird er automatisch als Abrechnungsmanager zur Organisation hinzugefügt. Wenn er noch kein GitHub-Konto besitzt, wird er auf eine Seite umgeleitet, auf der er ein Konto erstellen kann. Nach der Erstellung des Kontos wird er automatisch als Abrechnungsmanager zur Organisation hinzugefügt. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Klicke neben den Abrechnungsmanagern auf **Add a billing manager** (Einen Abrechnungsmanager hinzufügen). ![Abrechnungsmanager einladen](/assets/images/help/billing/settings_billing_managers_list.png) +6. Gib den Benutzernamen oder die E-Mail-Adresse des Benutzers ein, den Du hinzufügen möchtest, und klicke auf **Send invitation** (Einladung versenden). ![Seite zum Einladen eines Abrechnungsmanagers](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000..85db916048 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,29 @@ +--- +title: Einem Organisationsmitglied Berechtigungen als „Team-Betreuer“ erteilen +intro: 'Ein Organisationsinhaber kann jedes Mitglied einer Organisation zum *Team-Betreuer* für ein Team ernennen und ihm eine Teilmenge der Berechtigungen erteilen, die Organisationsinhabern zur Verfügung stehen.' +redirect_from: + - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ + - /articles/giving-team-maintainer-permissions-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.organizations.team_maintainers_can %} + +### Ein Organisationsmitglied zum Team-Betreuer ernennen + +Bevor Du ein Organisationsmitglied zum Team-Betreuer ernennen kannst, muss die Person Mitglied des Teams sein. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +4. Wähle die Person(en) aus, die Du zum Team-Betreuer ernennen möchtest. ![Kontrollkästchen neben dem Organisationsmitglied](/assets/images/help/teams/team-member-check-box.png) +5. Klicke im Dropdownmenü über der Liste der Teammitglieder auf **Change role** (Rolle ändern). ![Dropdownmenü mit Option zum Ändern der Rolle](/assets/images/help/teams/bulk-edit-drop-down.png) +6. Wähle eine neue Rolle aus, und klicke dann auf **Change role** (Rolle ändern). ![Optionsfelder für Betreuer- oder Mitglieder-Rollen](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md new file mode 100644 index 0000000000..09beca64ce --- /dev/null +++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -0,0 +1,21 @@ +--- +title: Rollenbasierten Zugriff von Personen auf Deine Organisation verwalten +intro: 'Die Rolle einer Person in Deiner Organisation bestimmt die Ebene ihres Zugriffs auf Deine Organisationen und deren Einstellungen und Deine Daten. Du kannst Personen zu Inhabern, Mitgliedern oder Abrechnungsmanagern für Deine Organisation machen oder ihnen Team-Betreuer-Berechtigungen erteilen.' +redirect_from: + - /articles/managing-people-s-access-to-your-organization-with-roles + - /articles/managing-peoples-access-to-your-organization-with-roles + - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000..04b7ab3d8e --- /dev/null +++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Aufrechterhaltung der Inhaberkontinuität für Deine Organisation +intro: Organisationen können mehr als einen Organisationsinhaber haben, um Inhaberlücken zu vermeiden. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization +permissions: Organisationsinhaber können jedes Mitglied einer Organisation zum Organisationsinhaber befördern. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### Über die Aufrechterhaltung der Inhaberkontinuität für Deine Organisation + +{% data reusables.organizations.org-ownership-recommendation %} + +Organisationsinhaber haben vollen administrativen Zugriff auf die Organisation. {% data reusables.organizations.new-org-permissions-more-info %} + +### Einen Organisationsinhaber ernennen + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Wähle die Person(en) aus, die Du als Inhaber festlegen möchtest. ![Liste der Mitglieder mit zwei ausgewählten Mitgliedern](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Klicke im Dropdownmenü über der Liste der Mitglieder auf **Change role** (Rolle ändern). ![Dropdownmenü mit Option zum Entfernen von Mitgliedern](/assets/images/help/teams/user-bulk-management-options.png) +6. Wähle eine neue Rolle für die Person(en) aus, und klicke dann auf **Change role** (Rolle ändern). ![Optionsfelder mit Inhaber- und Mitgliederrollen und Schaltfläche „Change role“ (Rolle ändern)](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md new file mode 100644 index 0000000000..5bbde26dd0 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -0,0 +1,147 @@ +--- +title: Berechtigungsebenen für eine Organisation +intro: 'Wenn Du [eine Organisation erstellt hast](/articles/creating-a-new-organization-account), solltest Du einer kleinen Anzahl von Benutzern, die das Organisationskonto verwalten werden, Inhaberberechtigungen erteilen.' +redirect_from: + - /articles/permission-levels-for-an-organization-early-access-program/ + - /articles/permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +### Berechtigungsebenen für eine Organisation + +Organization members can have *owner*{% if currentVersion == "free-pro-team@latest" %}, *billing manager*,{% endif %} or *member* roles: + +- **Inhaber** haben vollen administrativen Zugriff auf eine Organisation. Diese Rolle sollte in Deiner Organisation beschränkt verfügbar sein, aber für nicht weniger als zwei Personen. Weitere Informationen findest Du unter „[Die Inhaber-Kontinuität für Deine Organisation aufrechterhalten](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." +{% if currentVersion == "free-pro-team@latest" %} +- **Abrechnungsmanager** können die Abrechnungseinstellungen verwalten. Weitere Informationen findest Du unter „[Abrechnungsmanager zu Deiner Organisation hinzufügen](/articles/adding-a-billing-manager-to-your-organization)“. +{% endif %} +- **Mitglieder** ist die Standardrolle für alle anderen Benutzer. + +{% if currentVersion == "free-pro-team@latest" %} + + +| Aktion in der Organisation | Inhaber | Mitglieder | Abrechnungsmanager | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:----------:|:------------------:| +| Repositorys erstellen (siehe „[Repository-Erstellung in Deiner Organisation einschränken](/articles/restricting-repository-creation-in-your-organization)“) | **X** | **X** | | +| Abrechnungsinformationen anzeigen und bearbeiten | **X** | | **X** | +| Personen zum Beitritt zur Organisation einladen | **X** | | | +| Einladungen zum Beitritt zur Organisation bearbeiten und zurückziehen | **X** | | | +| Mitglied aus der Organisation entfernen | **X** | | | +| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | | +| Benutzer zu **allen Teams** hinzufügen oder wieder entfernen | **X** | | | +| Organisationsmitglieder zu *Team-Betreuern* ernennen | **X** | | | +| Code-Review-Zuweisungen konfigurieren (Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Geplante Erinnerungen setzen (Weitere Informationen findest Du unter „[Geplante Erinnerungen für Pull-Requests verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | +| Mitarbeiter zu **allen Repositorys** hinzufügen | **X** | | | +| Auf das Auditprotokoll der Organisation zugreifen | **X** | | | +| Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“) | **X** | | | +| Die Domänen der Organisation überprüfen (siehe „[Domänen Deiner Organisation überprüfen](/articles/verifying-your-organization-s-domain)“) | **X** | | | +| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | +| **Alle Teams** löschen | **X** | | | +| Das Organisationskonto einschließlich aller Repositorys löschen | **X** | | | +| Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“) | **X** | **X** | | +| [Teams in der Hierarchie einer Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Projektboards erstellen (siehe „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“) | **X** | **X** | | +| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | | +| Ein sichtbares Team @erwähnen | **X** | **X** | | +| Kann *Team-Beteuern* werden | **X** | **X** | | +| Einblicke für die Organisation anzeigen (siehe „[Einblicke für Ihre Organisation anzeigen ](/articles/viewing-insights-for-your-organization)“) | **X** | **X** | | +| Öffentliche Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“) | **X** | **X** | | +| Private Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“) | **X** | | | +| Teamdiskussionen in **allen Teams** bearbeiten und löschen (siehe „[Störende Kommentare verwalten](/communities/moderating-comments-and-conversations/managing-disruptive-comments)“) | **X** | | | +| Kommentare zu Commits, Pull Requests und Issues ausblenden (siehe „[Störende Kommentare verwalten](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)“) | **X** | **X** | | +| Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | | +| Die Anzeige von Einblicken zu den Abhängigkeiten einer Organisation verwalten (siehe „[Die Sichtbarkeit der Einblicke zu den Abhängigkeiten Ihrer Organisation ändern](/articles/changing-the-visibility-of-your-organizations-dependency-insights)“) | **X** | | | +| Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/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](/organizations/managing-organization-settings/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** | | | +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | +| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | +| [SAML Single Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on) aktivieren und erzwingen | **X** | | | +| [Den SAML-Zugriff eines Benutzers auf Deine Organisation verwalten](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Die SSH-Zertifizierungsstellen einer Organisation verwalten (siehe „[SSH-Zertifizierungsstellen Ihrer Organisation verwalten](/articles/managing-your-organizations-ssh-certificate-authorities)“) | **X** | | | +| Repositorys übertragen | **X** | | | +| {% data variables.product.prodname_marketplace %}-Apps erwerben, installieren, kündigen und ihre Abrechnung verwalten | **X** | | | +| Apps auf {% data variables.product.prodname_marketplace %} aufführen | **X** | | | +| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **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** | | | +| [Die Forking-Richtlinie verwalten](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Aktivitäten in öffentlichen Repositorys in einer Organisation einschränken](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | +| Lesen von (pull), Schreiben zu (push) und Kopieren von (clone) *allen Repositorys* der Organisation | **X** | | | +| Organisationsmitglieder in [externe Mitarbeiter](#outside-collaborators) umwandeln | **X** | | | +| [Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Eine Liste der Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | +| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | | | +| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** | | | + +{% else %} + + +| Aktion in der Organisation | Inhaber | Mitglieder | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:------------------------------------------------------------------------------------------------:| +| Personen zum Beitritt zur Organisation einladen | **X** | | +| Einladungen zum Beitritt zur Organisation bearbeiten und zurückziehen | **X** | | +| Mitglied aus der Organisation entfernen | **X** | | | +| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | | +| Benutzer zu **allen Teams** hinzufügen oder wieder entfernen | **X** | | +| Organisationsmitglieder zu *Team-Betreuern* ernennen | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Code-Review-Zuweisungen konfigurieren (Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Mitarbeiter zu **allen Repositorys** hinzufügen | **X** | | +| Auf das Auditprotokoll der Organisation zugreifen | **X** | | +| Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“) | **X** | | | +| **Alle Teams** löschen | **X** | | +| Das Organisationskonto einschließlich aller Repositorys löschen | **X** | | +| Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“) | **X** | **X** | +| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | +| Ein sichtbares Team @erwähnen | **X** | **X** | +| Kann *Team-Beteuern* werden | **X** | **X** | +| Repositorys übertragen | **X** | | +| Die SSH-Zertifizierungsstellen einer Organisation verwalten (siehe „[SSH-Zertifizierungsstellen Ihrer Organisation verwalten](/articles/managing-your-organizations-ssh-certificate-authorities)“) | **X** | | +| Projektboards erstellen (siehe „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“) | **X** | **X** | | +| Öffentliche Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“) | **X** | **X** | | +| Private Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Kommentare zu Commits, Pull Requests und Issues ausblenden (siehe „[Störende Kommentare verwalten](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)“) | **X** | **X** | **X** | +| Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | | +| Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/articles/setting-your-team-s-profile-picture)“) | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | +{% endif %} +| [Teams in der Hierarchie einer Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Lesen von (pull), Schreiben zu (push) und Kopieren von (clone) *allen Repositorys* der Organisation | **X** | | +| Organisationsmitglieder in [externe Mitarbeiter](#outside-collaborators) umwandeln | **X** | | +| [Personen mit Zugriff auf ein Repository der Organisation anzeigen](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Eine Liste der Personen mit Zugriff auf ein Repository der Organisation anzeigen](/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" %} +| Standardkennzeichnungen verwalten (siehe „[Standardkennzeichnungen für Repositorys in Deiner Organisation verwalten](/articles/managing-default-labels-for-repositories-in-your-organization)“) | **X** | +{% endif %} +{% if currentVersion == "github-ae@latest" %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} + +{% endif %} + +### {% data variables.product.prodname_github_app %}-Managers + +Standardmäßig können nur Organisationsinhaber die Einstellungen von {% data variables.product.prodname_github_app %}s einer Organisation verwalten. Um weiteren Benutzern das Verwalten von {% data variables.product.prodname_github_app %}s einer Organisation zu erlauben, kann ein Inhaber ihnen {% data variables.product.prodname_github_app %}-Managerberechtigungen erteilen. + +Wenn Du einen Benutzer zum {% data variables.product.prodname_github_app %}-Manager in Deiner Organisation ernennst, kannst Du ihm Zugriff für die Verwaltung der Einstellungen einzelner oder aller {% data variables.product.prodname_github_app %}s der Organisation gewähren. Weitere Informationen findest Du unter: + +- „[GitHub App-Manager zu Deiner Organisation hinzufügen](/articles/adding-github-app-managers-in-your-organization)“ +- „[GitHub App-Manager aus Deiner Organisation entfernen](/articles/removing-github-app-managers-from-your-organization)“ + +### Externe Mitarbeiter + +To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %} + +### Weiterführende Informationen + +- „[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“ +- „[Informationen zu Teams](/articles/about-teams)“ +- „[Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)“ diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000..f0d2daa7eb --- /dev/null +++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Abrechnungsmanager aus Deiner Organisation entfernen +intro: 'Wenn für eine Person mit der Rolle *Abrechnungsmanager* kein Grund mehr besteht, die Abrechnungsinformationen Deiner Organisation anzuzeigen oder zu ändern, kannst Du deren Zugriff auf die Organisation entfernen.' +redirect_from: + - /articles/removing-a-billing-manager-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams + - Abrechnung +--- + +{% warning %} + +**Hinweis:** {% 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. Klicke in der Liste der Abrechnungsmanager neben dem Namen der Person, die Du entfernen möchtest, auf {% octicon "x" aria-label="X symbol" %}. ![Abrechnungsmanager entfernen](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000..6e81d86a3a --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,62 @@ +--- +title: Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On +intro: 'Wenn Du die Identitäten und Applikationen Deiner Benutzer zentral mit einem Identitätsanbieter (identity provider IdP) verwaltest, kannst Du ''Security Assertion Markup Language'' (SAML) Single Sign-On (SSO) konfigurieren, um die Ressourcen Deiner Organisation auf {% data variables.product.prodname_dotcom %} zu schützen.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/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 +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +### Informationen zu SAML SSO + +{% data reusables.saml.dotcom-saml-explanation %} + +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. + +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 %} + +Bevor Du SAML SSO für Deine Organisation aktivierst, musst Du Deinen IdP mit Deiner Organisation verbinden. Weitere Informationen findest Du unter „[Deinen Identitätsanbieter mit Deiner Organisation verbinden](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization).“ + +SAML SSO kann in einer Organisation entweder deaktiviert, aktiviert aber nicht erzwungen, oder aktiviert und erzwungen sein. Nachdem Du SAML SSO für Deine Organisation aktiviert hast und die Mitglieder Deiner Organisation sich erfolgreich mit Deinem IdP authentifizieren können, kannst Du die SAML SSO Konfiguration erzwingen. Weitere Informationen zur Durchsetzung von SAML SSO für Deine {% data variables.product.prodname_dotcom %}-Organisation findest Du unter „[SAML Single Sign-On für Deine Organisation erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization)." + +Mitglieder müssen sich regelmäßig bei Deinem IdP anmelden, um sich zu authentifizieren und Zugang zu den Ressourcen Deiner Organisation zu erhalten. Die Dauer dieser Anmeldephase wird von Deinem IdP festgelegt und beträgt in der Regel 24 Stunden. Durch diese Verpflichtung zur regelmäßigen Anmeldung wird die Dauer des Zugriffs begrenzt, und die Benutzer müssen sich erneut identifizieren, um fortzufahren. + +Um auf die geschützten Ressourcen der Organisation über das API und Git in der Befehlszeile zuzugreifen, müssen Mitglieder sich mit einem persönlichen Zugangs-Token oder SSH-Schlüssel autorisieren und authentifizieren. Weitere Informationen findest Du unter „[Autorisieren eines persönlichen Zugriffstokens für die Benutzung mit SAML Single Sign-On](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" und „[Autorisieren eines SSH-Schlüssels für die Benutzung mit SAML Single Sign-On](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." + +Beim ersten Mal, wenn ein Mitglied SAML SSO verwendet, um auf Deine Organisation zuzugreifen, erstellt {% data variables.product.prodname_dotcom %} automatisch einen Datensatz, der Deine Organisation, das Konto des Mitglieds auf {% data variables.product.prodname_dotcom %} und das Konto des Mitglieds auf Deinem IdP miteinander verknüpft. Du kannst die verknüpfte SAML-Identität, aktive Sitzungen und autorisierte Anmeldeinformationen für Mitglieder Deiner Organisation oder Deines Enterprise-Kontos anzeigen und widerrufen. Weitere Informationen findest Du unter „[Den SAML-Zugriff eines Mitglieds auf Deine Organisation anzeigen und verwalten](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" und „[Den SAML-Zugriff eines Benutzers auf Dein Enterprise-Konto ansehen und verwalten](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)." + +If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. Weitere Informationen zu Repository-Sichtbarkeiten findest Du unter „[Informationen zur Sichtbarkeit eines Repositorys](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)“. + +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 %} + +Einige IdPs unterstützen die Bereitstellung von Zugriffen auf eine {% data variables.product.prodname_dotcom %}-Organisation über SCIM. Weitere Informationen findest Du unter „[Über SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +### 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 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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### Weiterführende Informationen + +- „[Informationen zur Zwei-Faktor-Authentifizierung und zu SAML Single Sign-On](/articles/about-two-factor-authentication-and-saml-single-sign-on)“ +- „[Informationen zur Authentifizierung mit SAML Single Sign-On](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)“ diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md new file mode 100644 index 0000000000..2a3d9547fb --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -0,0 +1,31 @@ +--- +title: Informationen zu SCIM +intro: 'Mit ''System for Cross-domain Identity Management'' (SCIM, System zur Domänen-übergreifenden Identitätsverwaltung) können Administratoren den Austausch von Benutzeridentitätsinformationen zwischen Systemen automatisieren.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-scim + - /github/setting-up-and-managing-organizations-and-teams/about-scim +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Wenn Sie in Ihrer Organisation [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) verwenden, können Sie SCIM implementieren, um den Zugriff von Organisationsmitgliedern auf {% data variables.product.product_name %} hinzuzufügen, zu verwalten und zu entfernen. Ein Administrator kann beispielsweise die Bereitstellung des Zugriffs eines Organisationsmitglieds mithilfe von SCIM aufheben und das Mitglied automatisch aus der Organisation entfernen. + +Wenn Du SAML SSO verwendest, ohne SCIM zu implementieren, ist die Aufhebung der Bereitstellung nicht automatisiert. Wenn die Sitzungen der Organisationsmitglieder ablaufen, nachdem ihr Zugriff vom IdP entfernt wurde, werden sie nicht automatisch aus der Organisation entfernt. Autorisierte Token gewähren auch nach Ablauf ihrer Sitzungen Zugriff auf die Organisation. Um den Zugriff zu entfernen, können Administratoren entweder manuell das autorisierte Token aus der Organisation entfernen oder seine Entfernung mit SCIM automatisieren. + +These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. Weitere Informationen findest Du unter [SCIM](/rest/reference/scim) in der {% data variables.product.product_name %}-API-Dokumentation. +- 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)." + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ +- „[Deinen Identitätsanbieter (IdP) mit Deiner Organisation verbinden](/articles/connecting-your-identity-provider-to-your-organization)“ +- „[SAML Single Sign-On für Deine Organisation aktivieren und testen](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)“ +- „[Den SAML-Zugriff eines Mitglieds auf Deine Organisation ansehen und verwalten](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000..8061c777f1 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,31 @@ +--- +title: Zugriff auf Deine Organisation bei nicht verfügbarem Identitätsanbieter +intro: 'Administratoren von Organisationen können sich bei {% data variables.product.product_name %} anmelden, auch wenn ihr Identitätsanbieter nicht verfügbar ist, indem sie Single Sign-On umgehen und ihre Wiederherstellungscodes verwenden.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Administratoren von Organisationen können [einen ihrer heruntergeladenen oder gespeicherten Wiederherstellungscodes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) verwenden, um Single-Sign-On zu umgehen. Möglicherweise hast Du diese in einem Passwort-Manager wie [LastPass](https://lastpass.com/), [1Password](https://1password.com/) oder [Keeper](https://keepersecurity.com/) gespeichert. + +{% note %} + +**Hinweis:** Du kannst Wiederherstellungscodes nur einmal und in aufeinanderfolgender Reihenfolge verwenden. Wiederherstellungscodes gewähren den Zugriff für 24 Stunden. + +{% endnote %} + +1. Klicke unten im Single Sign-On-Dialog auf **Use a recovery code** (Wiederherstellungscode verwenden), um Single Sign-On zu umgehen. ![Link zum Eingeben Deines Wiederherstellungscodes](/assets/images/help/saml/saml_use_recovery_code.png) +2. Gib im Feld „Recovery Code“ (Wiederherstellungscode) Deinen Wiederherstellungscode ein. ![Feld zum Eingeben Deines Wiederherstellungscodes](/assets/images/help/saml/saml_recovery_code_entry.png) +3. Klicke auf **Verify** (Bestätigen). ![Schaltfläche zum Bestätigen Deines Wiederherstellungscodes](/assets/images/help/saml/saml_verify_recovery_codes.png) + +Denke daran, dass ein Wiederherstellungscode nicht mehr gültig ist, nachdem Du ihn verwendet hast. Du kannst den Wiederherstellungscode nicht erneut verwenden. + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000..0054bc80c1 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,81 @@ +--- +title: SAML Single Sign-On und SCIM mit Okta konfigurieren +intro: 'Du kannst ''Security Assertion Markup Language'' (SAML) Single Sign-On (SSO) und ''System for Cross-Domain Identity Management'' (SCIM, System zur Identitätsverwaltung über Domänen hinweg) mit Okta verwenden, um den Zugriff auf Deine Organisation automatisch auf {% data variables.product.prodname_dotcom %} zu verwalten.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta +product: '{% data reusables.gated-features.saml-sso %}' +permissions: Organisationseigentümer können SAML SSO und SCIM mit Okta für eine Organisation konfigurieren. +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +### Über SAML und SCIM mit Okta + +Du kannst den Zugriff auf Deine {% data variables.product.prodname_dotcom %}-Organisation und andere Webanwendungen von einer zentralen Schnittstelle aus steuern, indem Du die Organisation so konfigurierst, dass sie SAML SSO und SCIM mit Okta, einem Identitätsanbieter (IdP), nutzt. + +SAML SSO steuert und sichert den Zugriff auf Organisationsressourcen wie Repositorys, Issues und Pull Requests. SCIM fügt bei Änderungen in Okta automatisch den Zugriff von Mitgliedern auf Deine {% data variables.product.prodname_dotcom %}-Organisation hinzu, oder verwaltet und entfernt sie. Weitere Informationen findest du unter „[Über Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" und „[Über SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +Nachdem Du SCIM aktiviert hast, stehen Dir folgende Bereitstellungsfunktionen für alle Benutzer zur Verfügung, denen Du Deine {% data variables.product.prodname_ghe_cloud %}-Anwendung in Okta zuweist. + +| Funktion | Beschreibung | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Push neuer Benutzer | Wenn Du in Okta einen neuen Benutzer erstellst, wird der Benutzer eine E-Mail-Einladung zu Deiner {% data variables.product.prodname_dotcom %}-Organisation erhalten. | +| Push Benutzer-Deaktivierung | Wenn Du einen Benutzer in Okta deaktivierst, wird ihn Okta auch von Deiner {% data variables.product.prodname_dotcom %}-Organisation entfernen. | +| Push Profil-Aktualisierungen | Wenn Du ein Benutzerprofil in Okta aktualisierst, wird Okta die Metadaten für die Mitgliedschaft des Benutzers in Deiner {% data variables.product.prodname_dotcom %}-Organisation aktualisieren. | +| Benutzer reaktivieren | Wenn Du einen Benutzer in Okta reaktivierst, wird Okta dem Benutzer eine E-Mail-Einladung senden, Deiner {% data variables.product.prodname_dotcom %}-Organisation wieder beizutreten. | + +### Vorrausetzungen + +{% data reusables.saml.use-classic-ui %} + +### Die {% data variables.product.prodname_ghe_cloud %}-Anwendung in Okta hinzufügen + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +4. Klicke rechts von „Github Enterprise Cloud - Organization" auf **Add** (Hinzufügen). ![Klicke auf "Add" (Hinzufügen) für die {% data variables.product.prodname_ghe_cloud %}-Anwendung](/assets/images/help/saml/okta-add-ghec-application.png) + +5. Gib im Feld **GitHub Organization** den Namen Deiner {% data variables.product.prodname_dotcom %}-Organisation ein. Wenn zum Beispiel die URL Deiner Organisation https://github.com/octo-org ist, lautet der Name der Organisation `octo-org`. ![Github Organisationsname eingeben](/assets/images/help/saml/okta-github-organization-name.png) + +6. Klicke auf **Done** (Fertig). + +### SAML SSO aktivieren und testen + +{% 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. Aktiviere und teste SAML SSO auf {% data variables.product.prodname_dotcom %} über die Anmelde-URL, die Herausgeber-URL und die öffentlichen Zertifikate aus dem „Wie konfiguriere ich SAML 2.0"-Leitfaden. Weitere Informationen finden Sie unter „[SAML Single Sign-On für Ihre Organisation aktivieren und testen](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)“. + +### Konfigurieren der Zugriffsbereitstellung mit SCIM in 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. Klicke auf **Authenticate with Github Enterprise Cloud - Organization** (Authentisieren mit einer Github Enterprise Cloud-Organisation). ![Schaltfläche "Authenticate with Github Enterprise Cloud - Organization" (mit der Github Enterprise Cloud-Organisation authentifizieren) der Okta-Anwendung](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) + +7. Klicke rechts neben Deinem Organisationsnamen auf **Grant** (Gewähren). ![Schaltfläche "Grant" (Gewähren) um die Okta-SCIM-Integration für Organisationszugriff zu autorisieren](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) + + {% note %} + + **Hinweis**: Wenn Du Deine Organisation nicht in der Liste siehst, gehe zu `https://github. om/orgs/ORGANISATIONS-NAME/sso` in Deinem Browser und authentifiziere Dich mit Deiner Organisation über SAML SSO unter Verwendung Deines Administrator-Kontos auf der IdP. Wenn zum Beispiel der Name Deiner Organisation `octo-org` ist, lautet die URL `https://github.com/orgs/octo-org/sso`. Weitere Informationen findest Du unter „[Über die Authentifizierung mit SAML Single Sign-On](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on).“ + + {% endnote %} +1. Klicke auf **Authorize OktaOAN** (Autorisiere OktaOAN). ![Schaltfläche "Authorize OktaOAN" (autorisiere OktaOAN) um die Okta-SCIM-Integration für Organisationszugriff zu autorisieren](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} + +### Weiterführende Informationen + +- "[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 Deine Organisation verwalten](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" +- [SAML verstehen](https://developer.okta.com/docs/concepts/saml/) in der Okta-Dokumentation +- [SCIM verstehen](https://developer.okta.com/docs/concepts/scim/) in der Okta-Dokumentation diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000..8aa4830154 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Deinen Identitätsanbieter mit Deiner Organisation verbinden +intro: 'Um SAML Single Sign-On und SCIM zu verwenden, musst Du Deinen Identitätsanbieter mit Deiner {% data variables.product.product_name %}-Organisation verbinden.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/connecting-your-identity-provider-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Vor der [Aktivierung von SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) in Ihrer {% data variables.product.product_name %}-Organisation müssen Sie Ihren Identity Provider (IdP) mit Ihrer Organisation verbinden. + +Die SAML- und SCIM-Implementierungsdetails für Deinen IdP findest Du in der IdP-Dokumentation: +- 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) und [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) und [SCIM](http://developer.okta.com/standards/SCIM/) +- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) und [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 %} + +**Hinweis:** Von {% data variables.product.product_name %} unterstützte Identitätsanbieter für SCIM sind Azure AD, Okta und OneLogin. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/articles/about-scim).“ + +{% endnote %} + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ +- „[SAML Single Sign-On für Deine Organisation erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization)“ diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000..48d7703977 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,36 @@ +--- +title: SAML Single Sign-On-Wiederherstellungscodes Deiner Organisation herunterladen +intro: 'Organisationsadministratoren sollten die SAML Single Sign-On-Wiederherstellungscodes ihrer Organisation herunterladen, um sicherzustellen, dass sie auch dann auf {% data variables.product.product_name %} zugreifen können, wenn der Identitätsanbieter für die Organisation nicht verfügbar ist.' +redirect_from: + - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes + - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes + - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Wiederherstellungscode sollten nicht öffentlich gemacht und nicht weitergegeben werden. Wir empfehlen, sie mit einem Passwort-Manager wie [LastPass](https://lastpass.com/), [1Password](https://1password.com/) oder [Keeper](https://keepersecurity.com/) zu speichern. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. Klicke im Hinweis zu Wiederherstellungscodes unter „SAML single sign-on“ (SAML Single Sign-On) auf **Save your recovery codes** (Deine Wiederherstellungscodes speichern). ![Link zum Anzeigen und Speichern Deiner Wiederherstellungscodes](/assets/images/help/saml/saml_recovery_codes.png) +6. Speichere Deine Wiederherstellungscodes, indem Du auf **Download** (Herunterladen), **Print** (Drucken) oder **Copy** (Kopieren) klickst. ![Schaltflächen zum Herunterladen, Drucken oder Kopieren Deiner Wiederherstellungscodes](/assets/images/help/saml/saml_recovery_code_options.png) + + {% note %} + + **Hinweis:** Mithilfe Deiner Wiederherstellungscodes kannst Du trotzdem auf {% data variables.product.product_name %} zugreifen, wenn Dein Identitätsanbieter nicht verfügbar ist. Wenn Du neue Wiederherstellungscodes erzeugst, werden die auf der Seite „Single sign-on recovery codes“ (Single Sign-On-Wiederherstellungscodes) angezeigten Wiederherstellungscodes automatisch aktualisiert. + + {% endnote %} + +7. Wenn Sie einen Wiederherstellungscode genutzt haben, um wieder Zugriff auf {% data variables.product.product_name %} zu erhalten, können Sie diesen Code nicht mehr verwenden. Der Zugriff auf {% data variables.product.product_name %} ist nur 24 Stunden lang verfügbar, bevor Sie dazu aufgefordert werden, sich mit Single Sign-On anzumelden. + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ +- „[Zugriff auf Deine Organisation bei nicht verfügbarem Identitätsanbieter](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)“ diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..3130655a34 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,51 @@ +--- +title: SAML Single Sign-On für Deine Organisation aktivieren und testen +intro: Inhaber und Administratoren von Organisationen können SAML Single-Sign-On aktivieren, um eine zusätzliche Sicherheitsebene für die Organisation zu schaffen. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Du kannst SAML SSO in Deiner Organisation aktivieren, ohne die Verwendung für alle Mitglieder vorzuschreiben. Wenn Du SAML SSO für Deine Organisation aktivierst, aber nicht erzwingst, förderst Du die Annahme dieser Funktion. Sobald die Mehrheit der Organisationsmitglieder SAML SSO verwendet, kannst Du die Nutzung in Deiner Organisation vorschreiben. + +Wenn Du SAML SSO aktivierst, aber nicht erzwingst, können Organisationsmitglieder, die SAML SSO nicht verwenden, trotzdem Mitglieder der Organisation bleiben. Weitere Informationen zur erzwungenen Nutzung von SAML SSO findest Du unter „[SAML Single Sign-On für Deine Organisation erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization).“ + +{% data reusables.saml.outside-collaborators-exemption %} + +Bevor Du SAML SSO in Deiner Organisation erzwingst, stelle sicher, dass Du den Identitätsanbieter (IdP Identity Provider) eingerichtet hast. Weitere Informationen findest Du unter „[Auf die Erzwingung von SAML Single Sign-On in Deiner Organisation vorbereiten](/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. 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/saml/saml_enable.png) + + {% note %} + + **Hinweis** Nachdem Du SAML SSO aktiviert hast, kannst Du Deine Single Sign-On-Wiederherstellungscodes herunterladen, mit denen Du auf Deine Organisation zugreifen kannst, wenn Dein IdP nicht verfügbar ist. Weitere Informationen findest Du unter „[SAML Single Sign-On-Wiederherstellungscodes Deiner Organisation herunterladen](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes).“ + + {% endnote %} + +6. Gib im Feld „Sign on URL“ (Sign-On-URL) den HTTPS-Endpunkt Deines 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.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. Klicken Sie auf {% octicon "pencil" aria-label="The edit icon" %}. Wählen Sie dann in den Dropdownmenüs für „Signature Method“ (Signaturmethode) und „Digest Method“ (Digest-Methode) den von Ihrem SAML-Aussteller verwendeten Hash-Algorithmus aus, um die Integrität der Anforderungen zu verifizieren. ![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 Deine Organisation 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) + + {% tip %} + + **Tipp:** {% data reusables.saml.testing-saml-sso %} + + {% endtip %} +11. Um SAML SSO zu erzwingen und alle Organisationsmitglieder zu entfernen, die sich nicht über Deinen IdP authentifiziert haben, wähle **Require SAML SSO authentication for all members of the _organization name_ organization** (SAML SSO-Authentifizierung für alle Mitglieder der Organisation vorschreiben) aus. Weitere Informationen zur erzwungenen Nutzung von SAML SSO findest Du unter „[SAML Single Sign-On für Deine Organisation erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization).“ ![Kontrollkästchen, um SAML SSO für Deine Organisation vorzuschreiben ](/assets/images/help/saml/saml_require_saml_sso.png) +12. Klicke auf **Save** (Speichern). ![Schaltfläche zum Speichern der SAML SSO-Einstellungen](/assets/images/help/saml/saml_save.png) + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..1e910daf18 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: SAML Single Sign-On für Deine Organisation erzwingen +intro: Inhaber und Administratoren von Organisationen können SAML SSO erzwingen, sodass sich alle Organisationsmitglieder über einen Identitätsanbieter (IdP) authentifizieren müssen. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enforcing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Wenn Du SAML SSO in Deiner Organisation erzwingst, werden alle Mitglieder einschließlich Administratoren, die sich nicht über Deinen SAML-Identitätsanbieter (IdP) authentifiziert haben, aus der Organisation entfernt und über diese Entfernung benachrichtigt. Bots und Dienstkonten, für die beim IdP Deiner Organisation keine externen Identitäten eingerichtet sind, werden ebenfalls entfernt. Weitere Informationen zu Bots und Dienstkonten findest Du unter „[Bots und Dienstkonten mit SAML Single Sign-On verwalten](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)“. Du kannst Organisationsmitglieder wiederherstellen, sobald sie sich erfolgreich mit Single Sign-On angemeldet haben. + +Wenn sich Deine Organisation im Besitz eines Enterprise-Kontos befindet und Du SAML für das Enterprise-Konto aktivierst, wird die SAML-Konfiguration auf Organisationsebene überschrieben. 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)." + +{% tip %} + +**Tipp:** {% data reusables.saml.testing-saml-sso %} + +{% endtip %} + +1. Aktiviere und teste SAML SSO für Deine Organisation. Weitere Informationen zu diesem Vorgang findest Du unter „[SAML Single Sign-On für Deine Organisation aktivieren und testen](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization).“ +2. Nachdem Du **Require SAML SSO authentication for all members of the SAML SSO Org organization** (Authentifizierung mit SAML SSO für alle Mitglieder der SAML-SSO-Organisation vorschreiben) ausgewählt hast, werden Organisationsmitglieder angezeigt, die sich nicht über Deinen IdP authentifiziert haben. Wenn Du SAML SSO erzwingst, werden diese Mitglieder aus der Organisation entfernt. +3. Klicke auf **Enforce SAML SSO** (SAML SSO erzwingen), um SAML SSO zu erzwingen und die aufgeführten Organisationsmitglieder zu entfernen. + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md new file mode 100644 index 0000000000..e91e73ae5a --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -0,0 +1,24 @@ +--- +title: SAML Single Sign-On für Deine Organisation verwalten +intro: Organisationsadministratoren können die Identitäten der Mitglieder ihrer Organisation und den Zugriff auf ihre Organisation mit SAML Single-Sign-On (SSO) verwalten. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% 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 /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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000..bc18b98024 --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,79 @@ +--- +title: Teamsynchronisierung für Deine Organisation verwalten +intro: 'Du kannst die Teamsynchronisierung zwischen Deinem Identitätsanbieter (IdP) und Deiner Organisation auf {% data variables.product.product_name %} aktivieren oder deaktivieren.' +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization +permissions: Organisationsinhaber können die Teamsynchronisierung für eine Organisation verwalten. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Informationen zur Teamsynchronisierung + +Du kannst die Teamsynchronisierung zwischen Deinem IdP und {% data variables.product.product_name %} aktivieren, um es den Organisationsinhabern und Team-Betreuern zu ermöglichen, Teams in Deiner Organisation mit IdP-Gruppen zu verbinden. + +{% 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 %} + +Du kannst die Teamsynchronisierung auch für Organisationen im Besitz eines Enterprise-Kontos aktivieren. 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)." + +### Teamsynchronisierung aktivieren + +Die Schritte zur Aktivierung der Teamsynchronisierung hängen vom IdP ab, den Du verwenden möchtest. Es gibt Voraussetzungen zur Aktivierung der Teamsynchronisierung, die auf jeden IdP zutreffen. Jeder einzelne IdP hat zusätzliche Voraussetzungen. + +#### Vorrausetzungen + +{% data reusables.identity-and-permissions.team-sync-required-permissions %} + +Du musst SAML Single Sign-On für Deine Organisation und Deinen unterstützten IdP aktivieren. Weitere Informationen findest Du unter „[SAML Single Sign-On für Deine Organisation erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization).“ + +Du musst Dich für Deine Organisation mittels SAML SSO und dem unterstützten IdP authentifizieren. Weitere Informationen findest Du unter „[Authentifizierung mit SAML Single Sign-On](/articles/authenticating-with-saml-single-sign-on).“ + +#### Teamsynchronisierung für Azure AD aktivieren + +{% 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. Prüfe die Mandanteninformationen des Identitätsanbieters für Deine Organisation, und 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) + +#### Teamsynchronisierung für Okta aktivieren + +{% 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. Gib unterhalb dem Namen Deiner Organisation einen gültigen SSWS-Token und die URL zu Deiner Okta-Instanz ein. ![Okta Organisationsformular für das Aktivieren der Teamsynchronisierung](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) +6. Überprüfe die Mandanteninformationen des Identitätsanbieters, den Du mit Deiner Organisation verbinden möchtest und klicke auf **Approve** (Genehmigen). ![Schaltfläche „Enable team synchronization" (Teamsynchronisierung aktivieren)](/assets/images/help/teams/confirm-team-synchronization-okta.png) + +### Teamsynchronisierung deaktivieren + +{% 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. Klicke unter „Team synchronization“ (Teamsynchronisierung) auf **Disable team synchronization** (Teamsynchronisierung deaktivieren). ![Deaktivieren der Teamsynchronisierung](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000..4cffdca87f --- /dev/null +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Auf die Erzwingung von SAML Single Sign-On in Deiner Organisation vorbereiten +intro: 'Bevor Du SAML Single Sign-On in Deiner Organisation erzwingen, solltest Du die Mitgliedschaft Deiner Organisation überprüfen und die Verbindungseinstellungen zu Deinem Identitätsanbieter konfigurieren.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Wenn Du [SAML Single Sign-On in Deiner Organisation erzwingst](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), werden alle Mitglieder, die sich nicht über Deinen Identitätsanbieter (IdP) authentifiziert haben, aus der Organisation entfernt und über diese Entfernung benachrichtigt. + +Bevor Du SAML SSO in Deiner Organisation erzwingst, solltest Du Folgendes tun: + +- Mitglieder soweit erforderlich zu Deiner Organisation [hinzufügen](/articles/inviting-users-to-join-your-organization) oder aus Deiner Organisation [entfernen](/articles/removing-a-member-from-your-organization). +- Deinen IdP mit Deiner Organisation verbinden, sofern dies noch nicht getan wurde. Weitere Informationen findest Du unter „[Deinen Identitätsanbieter mit Deiner Organisation verbinden](/articles/connecting-your-identity-provider-to-your-organization).“ +- Sicherstellen, dass Deine Organisationsmitglieder sich angemeldet und ihre Konten mit dem IdP verknüpft haben. + +{% data reusables.saml.outside-collaborators-exemption %} + +### Weiterführende Informationen + +- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single-Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“ diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..b52f64085c --- /dev/null +++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,32 @@ +--- +title: Ein Administratorenteam für verbesserte Organisationsberechtigungen umwandeln +intro: 'Wenn Deine Organisation nach September 2015 erstellt wurde, verfügt sie standardmäßig über verbesserte Organisationsberechtigungen. Organisationen, die vor September 2015 erstellt wurden, müssen ältere Inhaber- und Administratorenteams möglicherweise auf das verbesserte Berechtigungsmodell migrieren. Mitglieder der alten Administratorenteams behalten automatisch die Fähigkeit, Repositorys zu erstellen, bis diese Teams zu dem verbesserten Organisationsberechtigungsmodell migriert wurden.' +redirect_from: + - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ + - /articles/converting-an-admin-team-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +Um Mitgliedern der alten Administratorenteams die Berechtigung zum Erstellen von Repositorys zu entziehen, erstelle ein neues Team für diese Mitglieder, stelle dabei sicher, dass das Team den erforderlichen Zugriff auf die Repositorys der Organisation hat, und lösche dann das alte Administratorenteam. + +Weitere Informationen findest Du unter„[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization/).“ + +{% warning %} + +**Warnungen:** +- Wenn es Mitglieder in Deinem alten Administratorenteam gibt, die keine Mitglieder anderer Teams sind, werden sie beim Löschen des Teams aus der Organisation entfernt. Bevor Du das Team löschst, stelle sicher, dass die Mitglieder bereits direkte Mitglieder der Organisation sind oder Mitarbeiterzugriff auf die benötigten Repositorys haben. +- Um zu verhindern, dass private Forks der Mitglieder des alten Administratorenteams verloren gehen, musst Du die unten stehenden Schritte 1 bis 3 ausführen, bevor Du das alte Administratorenteam löschst. +- Da „admin“ (Administrator) ein Begriff für Organisationsmitglieder mit spezifischem [Zugriff auf bestimmte Repositorys](/articles/repository-permission-levels-for-an-organization) in der Organisation ist, empfehlen wir, ihn nicht für Teamnamen zu verwenden. + +{% endwarning %} + +1. [Erstelle ein neues Team](/articles/creating-a-team). +2. [Füge alle Mitglieder](/articles/adding-organization-members-to-a-team) des alten Administratorenteams zum neuen Team hinzu. +3. [Gewähre dem neuen Team Zugriff](/articles/managing-team-access-to-an-organization-repository) auf die Repositorys, auf die das alte Team zugreifen konnte. +4. [Lösche das alte Administratorenteam](/articles/deleting-a-team). diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..191c4fd637 --- /dev/null +++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,52 @@ +--- +title: Ein Inhaberteam für verbesserte Organisationsberechtigungen umwandeln +intro: 'Wenn Deine Organisation nach September 2015 erstellt wurde, verfügt sie standardmäßig über verbesserte Organisationsberechtigungen. Organisationen, die vor September 2015 erstellt wurden, müssen ältere Inhaber- und Administratorenteams möglicherweise auf das verbesserte Berechtigungsmodell migrieren. Der „Owner“ (Inhaber) ist jetzt eine administrative Rolle, die einzelnen Mitgliedern Deiner Organisation zugewiesen wird. Mitglieder des alten Inhaberteams erhalten automatisch Inhaberberechtigungen.' +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +Du hast mehrere Möglichkeiten, Dein altes Inhaberteam umzuwandeln: + +- Gib dem Team einen neuen Namen, der die Mitglieder kennzeichnet, die einen besonderen Status in der Organisation haben. +- Lösche das Team, nachdem Du sichergestellt hast, dass alle Mitglieder zu Teams hinzugefügt wurden, die den benötigten Zugriff auf die Repositorys der Organisation haben. + +### Dem Inhaberteam einen neuen Namen geben + +{% tip %} + + **Hinweis:** Da „admin“ (Administrator) ein Begriff für Organisationsmitglieder mit spezifischem [Zugriff auf bestimmte Repositorys](/articles/repository-permission-levels-for-an-organization) in der Organisation ist, empfehlen wir, ihn nicht für Teamnamen zu verwenden. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. Lege im Feld für den Teamnamen einen neuen Namen für das Inhaberteam fest. Ein Beispiel: + - Wenn nur sehr wenige Mitglieder Deiner Organisation Mitglieder des Inhaberteams waren, könntest Du das Team beispielsweise „Kern“ nennen. + - Wenn alle Mitglieder Deiner Organisation Mitglieder des Inhaberteams waren, damit sie [Teams @erwähnen](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) konnten, könntest Du das Team „Mitarbeiter“ nennen. ![Das Feld für den Teamnamen mit „Core“ (Kern) als neuen Namen für das Inhaberteam](/assets/images/help/teams/owners-team-new-name.png) +6. Klicke unter der Teambeschreibung auf **Save and continue** (Speichern und fortfahren). ![Schaltfläche „Save and continue“ (Speichern und fortfahren)](/assets/images/help/teams/owners-team-save-and-continue.png) +7. Optional kannst Du [das Team auch *öffentlich* machen](/articles/changing-team-visibility). + +### Das alte Inhaberteam löschen + +{% warning %} + +**Warnung:** Wenn es Mitglieder in Deinem Inhaberteam gibt, die keine Mitglieder anderer Teams sind, werden sie beim Löschen des Teams aus der Organisation entfernt. Bevor Du das Team löschst, stelle sicher, dass die Mitglieder bereits direkte Mitglieder der Organisation sind oder Mitarbeiterzugriff auf die benötigten Repositorys haben. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. Lies unten auf der Seite die Warnung, und klicke dann auf **Delete the Owners team** (Inhaberteam löschen). ![Link zum Löschen des Inhaberteams](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/index.md new file mode 100644 index 0000000000..e1650b3ad4 --- /dev/null +++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/index.md @@ -0,0 +1,20 @@ +--- +title: Zu verbesserten Organisationsberechtigungen migrieren +intro: 'Falls Deine Organisation nach September 2015 erstellt wurde, verfügt sie standardmäßig über optimierte Organisationsberechtigungen. Bei Organisationen, die vor September 2015 erstellt wurden, müssen ältere Inhaber- und Administratorenteams möglicherweise zum optimierten Berechtigungsmodell migrieren.' +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000..baed976eff --- /dev/null +++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,44 @@ +--- +title: Administratorenteams zu verbesserten Organisationsberechtigungen migrieren +intro: 'Wenn Deine Organisation nach September 2015 erstellt wurde, verfügt sie standardmäßig über verbesserte Organisationsberechtigungen. Organisationen, die vor September 2015 erstellt wurden, müssen ältere Inhaber- und Administratorenteams möglicherweise auf das verbesserte Berechtigungsmodell migrieren. Mitglieder der alten Administratorenteams behalten automatisch die Fähigkeit, Repositorys zu erstellen, bis diese Teams zu dem verbesserten Organisationsberechtigungsmodell migriert wurden.' +redirect_from: + - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ + - /articles/migrating-admin-teams-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organisationen + - teams +--- + +Standardmäßig können alle Organisationsmitglieder Repositorys erstellen. Wenn Du die [Berechtigungen zur Repository-Erstellung](/articles/restricting-repository-creation-in-your-organization) auf Organisationsinhaber beschränkst und Deine Organisation unter der alten Struktur der Organisationsberechtigungen erstellt wurde, können Mitglieder der früheren Administratorenteams nach wie vor Repositorys erstellen. + +Frühere Administratorenteams sind Teams, die mit der Administrator-Berechtigungsebene unter der alten Struktur der Organisationsberechtigungen erstellt wurden. Mitglieder dieser Teams konnten Repositorys für die Organisation erstellen, und wir haben diese Fähigkeit in der optimierten Struktur der Organisationsberechtigungen beibehalten. + +Du kannst diese Berechtigung entfernen, indem Du Deine früheren Administratorenteams auf die optimierten Organisationsberechtigungen migrierst. + +Weitere Informationen finden Sie unter„[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“. + +{% warning %} + +**Warnung:** Wenn Deine Organisation [die Berechtigungen zur Repository-Erstellung](/articles/restricting-repository-creation-in-your-organization) für alle Mitglieder deaktiviert hat, verlieren möglicherweise einige Mitglieder der früheren Administratorenteams die Berechtigungen zur Repository-Erstellung. Wenn Deine Organisation die Repository-Erstellung für Mitglieder aktiviert hat, wirkt sich die Migration der früheren Administratorenteams zu den optimierten Organisationsberechtigungen nicht auf die Fähigkeit dieser Teammitglieder aus, Repositorys zu erstellen. + +{% endwarning %} + +### Alle früheren Administratorenteams der Organisation migrieren + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +1. Überprüfe die früheren Administratorenteams Deiner Organisation, und klicke dann auf **Migrate all teams** (Alle Teams migrieren). ![Schaltfläche „Migrate all teams" (Migration aller Teams)](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) +1. Lies die Informationen zu den Änderungen, die sich für die Berechtigungen der Mitglieder dieser Teams möglicherweise ergeben, und klicke dann auf **Migrate all teams** (Alle Teams migrieren). ![Schaltfläche „Confirm migration" (Migration bestätigen)](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) + +### Ein einzelnes Administratorenteam migrieren + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +1. Klicke im Teambeschreibungsfeld auf **Migrate team** (Team migrieren). ![Schaltfläche „Migrate team“ (Team migrieren)](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md b/translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md new file mode 100644 index 0000000000..3e8e339146 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md @@ -0,0 +1,79 @@ +--- +title: Informationen zu Teams +intro: Teams sind Gruppen von Organisationsmitgliedern, welche die Struktur Deines Unternehmens oder Deiner Gruppe mit kaskadierenden Zugriffsberechtigungen und Erwähnungen widerspiegeln. +redirect_from: + - /articles/about-teams + - /github/setting-up-and-managing-organizations-and-teams/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +![Liste der Teams in einer Organisation](/assets/images/help/teams/org-list-of-teams.png) + +Organisationsinhaber und Team-Betreuer können Teams Administrator-, Lese- oder Schreibzugriff auf die Repositorys der Organisation gewähren. Organisationsmitglieder können eine Benachrichtigung an ein ganzes Team senden, indem sie den Namen des Teams erwähnen. Organisationsmitglieder können außerdem eine Benachrichtigung an ein ganzes Team senden, indem sie von diesem Team einen Review anfordern. Organisationsmitglieder können Reviews von bestimmten Teams mit Lesezugriff auf das Repository anfordern, in dem der Pull Request geöffnet ist. Teams können als Inhaber bestimmter Codetypen oder Codebereiche in einer CODEOWNERS-Datei bestimmt werden. + +Weitere Informationen findest Du unter: +- „[Den Teamzugriff auf ein Repository einer Organisation verwalten](/articles/managing-team-access-to-an-organization-repository)“ +- „[Personen und Teams erwähnen](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)“ +- „[Informationen zu Codeinhabern](/articles/about-code-owners/)“ + +![Bild einer Teamerwähnung](/assets/images/help/teams/team-mention.png) + +{% if enterpriseServerVersions contains currentVersion %} + +Sie können außerdem mit LDAP Sync {% data variables.product.product_location %}-Teammitglieder und -Teamrollen mit Ihren bestehenden LDAP-Gruppen synchronisieren. Dadurch können Sie eine rollenbasierte Zugriffskontrolle für Benutzer von Ihrem LDAP-Server aus statt manuell innerhalb von {% data variables.product.product_location %} einrichten. Weitere Informationen finden Sie unter „[LDAP-Synchronisierung aktivieren](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)“. + +{% endif %} + +{% data reusables.organizations.team-synchronization %} + +### Sichtbarkeit eines Teams + +{% data reusables.organizations.types-of-team-visibility %} + +### Teamseiten + +Jedes Team hat seine eigene Seite innerhalb einer Organisation. Auf der Seite eines Teams kannst Du Teammitglieder, untergeordnete Teams und Repositorys des Teams anzeigen. Organisationsinhaber und Team-Betreuer können auf die Teameinstellungen zugreifen und die Beschreibung sowie das Profilbild des Teams über die Seite des Teams aktualisieren. + +Organisationsmitglieder können Diskussionen mit dem Team erstellen und daran teilnehmen. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“. + +![Teamseite mit einer Auflistung der Teammitglieder und Diskussionen](/assets/images/help/organizations/team-page-discussions-tab.png) + +### Verschachtelte Teams + +Du kannst die Hierarchie Deiner Gruppe oder Deines Unternehmens innerhalb Deiner {% data variables.product.product_name %}-Organisation mit mehreren Ebenen von verschachtelten Teams abbilden. Ein übergeordnetes Team kann mehrere untergeordnete Teams haben, wohingegen jedes untergeordnete Team nur ein übergeordnetes Team hat. Nicht öffentliche Teams können nicht verschachtelt werden. + +Für untergeordnete Teams gelten die Zugriffsberechtigungen des übergeordneten Teams, wodurch die Verwaltung von Berechtigungen für große Gruppen vereinfacht wird. Mitglieder von untergeordneten Teams erhalten außerdem Benachrichtigungen, wenn das übergeordnete Team @erwähnt wird, was die Kommunikation mit mehreren Personengruppen vereinfacht. + +Wenn Deine Teamstruktur beispielsweise „Mitarbeiter > Engineering > Application Engineering > Identity“ lautet, bedeutet die Gewährung von Schreibzugriff für Engineering auf ein Repository, dass auch Application Engineering und Identity diesen Zugriff erhalten. Wenn Du das Identity-Team oder ein Team am unteren Ende der Organisationshierarchie @erwähnst, erhält nur dieses Team eine Benachrichtigung. + +![Teamseite mit einem übergeordneten und einem untergeordneten Team](/assets/images/help/teams/nested-teams-eng-example.png) + +Um zu verstehen, wer die Berechtigungen und Erwähnungen eines übergeordneten Teams teilt, kannst Du alle Mitglieder der untergeordneten Teams eines übergeordneten Teams auf der Registerkarte „Members“ (Mitglieder) auf der Seite des übergeordneten Teams sehen. Mitglieder eines untergeordneten Teams sind keine direkten Mitglieder des übergeordneten Teams. + +![Seite eines übergeordneten Teams mit allen Mitgliedern der untergeordneten Teams](/assets/images/help/teams/team-and-subteam-members.png) + +Du kannst beim Erstellen des Teams ein übergeordnetes Team auswählen oder ein Team in der Hierarchie Deiner Organisation später verschieben. Weitere Informationen findest Du unter „[Team innerhalb der Hierarchie Deiner Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy).“ + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +### Die Verschachtelung von Teams in Deiner Organisation vorbereiten + +Wenn in Ihrer Organisation bereits Teams vorhanden sind, sollten Sie die Zugriffsberechtigungen für das Repository jedes Teams überprüfen, bevor Sie Teams über- oder unterordnen. Sie sollten außerdem die neue Struktur berücksichtigen, die Sie für Ihre Organisation implementieren möchten. + +An der Spitze der Teamhierarchie sollten Sie den übergeordneten Teams Zugriffsberechtigungen für das Repository erteilen, die für jedes Mitglied des übergeordneten Teams und seine untergeordneten Teams sicher sind. Wenn Sie sich in der Hierarchie nach unten bewegen, können Sie untergeordneten Teams zusätzlichen, detaillierteren Zugriff auf sensiblere Repositorys gewähren. + +1. Entferne alle Mitglieder aus vorhandenen Teams +2. Überprüfe und bearbeite die Zugriffsrechte für Repositorys für jedes Team, und weise jedem Team ein übergeordnetes Team zu +3. Erstelle alle gewünschten neuen Teams, wähle ein übergeordnetes Team für jedes neue Team, und gewähre seinen Mitgliedern Zugriff auf Repositorys +4. Füge Personen direkt zu Teams hinzu + +### Weiterführende Informationen + +- „[Ein Team erstellen](/articles/creating-a-team)“ +- „[Organisationsmitglieder zu einem Team hinzufügen](/articles/adding-organization-members-to-a-team)“ diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000..ab88a02907 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,32 @@ +--- +title: Organisationsmitglieder zu einem Team hinzufügen +intro: 'Benutzer mit Inhaber- oder Team-Betreuer-Berechtigungen können Organisationsmitglieder zu Teams hinzufügen. 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.' +redirect_from: + - /articles/adding-organization-members-to-a-team-early-access-program/ + - /articles/adding-organization-members-to-a-team + - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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. Klicke oberhalb der Liste der Teammitglieder auf **Add a member** (Ein Mitglied hinzufügen). ![Schaltfläche „Add member“ (Mitglied hinzufügen)](/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 %} + +### Weiterführende Informationen + +- „[Informationen zu Teams](/articles/about-teams)“ +- „[Den Teamzugriff auf ein Repository einer Organisation verwalten](/articles/managing-team-access-to-an-organization-repository)“ diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/de-DE/content/organizations/organizing-members-into-teams/changing-team-visibility.md new file mode 100644 index 0000000000..dd863f14eb --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/changing-team-visibility.md @@ -0,0 +1,29 @@ +--- +title: Sichtbarkeit eines Teams ändern +intro: Team-Betreuer und Organisationsinhaber können festlegen, ob ein Team *sichtbar* oder *geheim* ist. +redirect_from: + - /articles/changing-team-visibility + - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.organizations.types-of-team-visibility %} + +{% tip %} + +**Tipp:** Wenn ein Team [unter- oder übergeordnete Teams](/articles/about-teams) aufweist, kannst Du es nicht als geheimes Team festlegen. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +3. Wähle die Teams aus, deren Sichtbarkeit Du ändern möchtest. ![Liste der Teams mit zwei ausgewählten Teams](/assets/images/help/teams/list-of-teams-selected.png) +4. Klicke im Dropdownmenü über der Liste der Teams auf **Change visibility** (Sichtbarkeit ändern). ![Dropdownmenü mit Option zum Ändern der Teamsichtbarkeit](/assets/images/help/teams/team-bulk-management-options.png) +5. Lege fest, ob die Teams sichtbar oder geheim sein sollen, und klicke dann auf **Change visibility** (Sichtbarkeit ändern). ![Optionsfelder, um ein Team als sichtbar oder geheim festzulegen, und Schaltfläche „Change visibility“ (Sichtbarkeit ändern)](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md new file mode 100644 index 0000000000..953b6f27e7 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -0,0 +1,38 @@ +--- +title: Ein Team erstellen +intro: Du kannst unabhängige oder untergeordnete Teams erstellen, um Repository-Berechtigungen und Erwähnungen für Personengruppen zu verwalten. +redirect_from: + - /articles/creating-a-team-early-access-program/ + - /articles/creating-a-team + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Nur Organisationsinhaber und Betreuer eines übergeordneten Teams können ein neues untergeordnetes Team unter einem übergeordneten Team erstellen. Inhaber können auch die Berechtigungen für die Erstellung aller Teams in einer Organisation einschränken. Weitere Informationen findest Du unter „[Berechtigungen für die Teamerstellung in Deiner Organisation festlegen](/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. Wenn Deine Organisations oder Dein Enterprise-Konto optional die Teamsynchronisierung verwendet, kannst Du für das Verbinden einer Identitätsanbieter-Gruppe mit Deinem Team das Dropdownmenü „Identity Provider Groups" (Identitätsanbieter-Gruppen) benutzen und bis zu 5 Gruppen auswählen. Weitere Informationen findest Du unter „[Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Dropdownmenü zur Auswahl einer Identitätsanbieter-Gruppe](/assets/images/help/teams/choose-an-idp-group.png) +{% endif %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} +9. Optional kannst Du [dem Team Zugriff auf die Repositorys der Organisation gewähren](/articles/managing-team-access-to-an-organization-repository)“. + +### Weiterführende Informationen + +- „[Informationen zu Teams](/articles/about-teams)“ +- „[Team-Sichtbarkeit ändern](/articles/changing-team-visibility)“ +- „[Team innerhalb der Hierarchie Deiner Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy)“ diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/deleting-a-team.md new file mode 100644 index 0000000000..5c2cbdad9c --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/deleting-a-team.md @@ -0,0 +1,27 @@ +--- +title: Ein Team löschen +intro: Organisationsinhaber können jederzeit Teams über die Seite mit den Einstellungen des Teams löschen. +redirect_from: + - /articles/deleting-a-team + - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% tip %} + +**Tipp:** Nur Organisationsinhaber können übergeordnete Teams löschen. Weitere Informationen finden Sie unter „[Informationen zu Teams](/articles/about-teams)“. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Wähle alle Teams aus, die Du löschen möchtest. ![Liste der Teams mit zwei ausgewählten Teams](/assets/images/help/teams/list-of-teams-selected.png) +5. Klicke im Dropdownmenü über der Liste der Teams auf **Delete** (Löschen). ![Dropdownmenü mit Option zum Ändern der Teamsichtbarkeit](/assets/images/help/teams/team-bulk-management-options.png) +6. Überprüfe alle zu löschenden Teams, und klicke dann auf **I understand, delete Teams** (Ich habe verstanden und möchte die Teams löschen). ![Liste der zu löschenden Teams und Schaltfläche zum Löschen der Teams](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000..89913ee3ee --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Teamdiskussionen innerhalb Deiner Organisation deaktivieren +intro: Organisationsinhaber können Teamdiskussionen innerhalb der gesamten Organisation deaktivieren oder aktivieren. +redirect_from: + - /articles/disabling-team-discussions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.organizations.team-discussions-default %} Weitere Informationen zu Teamdiskussionen findest Du unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions).“ + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +5. Hebe unter „Team discussions“ (Teamdiskussionen) die Auswahl von **Enable team discussions for this organization** (Teamdiskussionen für diese Organisation aktivieren) auf. ![Kontrollkästchen zum Aktivieren oder Deaktivieren von Teamdiskussionen für eine Organisation](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) +6. Klicke auf **Save** (Speichern). diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/index.md b/translations/de-DE/content/organizations/organizing-members-into-teams/index.md new file mode 100644 index 0000000000..dcc0d1ca1f --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/index.md @@ -0,0 +1,38 @@ +--- +title: Mitglieder in Teams organisieren +intro: Du kannst Organisationsmitglieder in Teams einteilen, die mit kaskadierenden Zugriffsberechtigungen und Erwähnungen die Struktur Deines Unternehmens oder Deiner Gruppe widerspiegeln. +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 + - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% link_in_list /about-teams %} +{% link_in_list /creating-a-team %} +{% link_in_list /setting-your-teams-profile-picture %} +{% link_in_list /setting-your-teams-profile-picture %} +{% link_in_list /managing-code-review-assignment-for-your-team %} +{% link_in_list /renaming-a-team %} +{% link_in_list /renaming-a-team %} +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000..6cd075158d --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,51 @@ +--- +title: Code-Review-Zuweisung für Dein Team verwalten +intro: Die Zuweisung von Code-Reviews zeigt deutlich an, welche Mitglieder eines Teams einen Review für einen Pull Request einreichen sollen. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Team-Betreuer und Organisationsinhaber können Code-Review-Zuweisungen konfigurieren. + +### Über Code-Review-Zuweisungen + +Jedes mal, wenn Dein Team aufgefordert wird, einen Pull Request zu überprüfen, wird durch die Verwendung von Code-Review-Zuweisungen das Team als Prüfer entfernt und durch eine bestimmte Teilmenge der Teammitglieder ersetzt. Code-Review-Zuweisungen erlauben es Dir zu entscheiden, ob das gesamte Team oder nur eine Teilmenge der Teammitgliedern benachrichtigt wird, wenn ein Team für einen Review angefordert wird. + +Wenn Codeinhaber automatisch zum Review aufgefordert werden, wird das Team trotzdem noch entfernt und durch Einzelpersonen ersetzt. Die Genehmigungen von Einzelpersonen erfüllen die Anforderungen für die Codeinhaber-Genehmigung in einem geschützten Branch nicht. Weitere Informationen findest Du unter „[Über Codeinhaber](/github/creating-cloning-and-archiving-repositories/about-code-owners)." + +### Routing-Algorithmen + +Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. + +Der Round-Robin-Algorithmus wählt die Prüfer basierend auf den Empfängern der letzten Review-Anforderungen aus, und fokussiert auf der abwechselnden Auswahl der Mitarbeiter des Teams, unabhängig von der Anzahl ausstehenden Reviews, die die Teammitglieder momentan haben. + +Der Lastenausgleich-Algorithmus (load balance algorithm) wählt Prüfer basierend auf der Gesamtzahl ihrer neuesten Review-Anforderungen aus und berücksichtigt die Anzahl der ausstehenden Reviews jedes Mitglieds. Der Lastenausgleich-Algorithmus versucht sicherzustellen, dass jedes Teammitglied eine gleiche Anzahl von Pull Requests innerhalb eines Zeitraums von 30 Tagen überprüft. + +### Code-Review-Zuweisungen konfigurieren +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Klicke in der linken Seitenleiste auf **Code review assignment** (Code-Review-Zuweisung). ![Schaltfläche „Code review assignment" (Code-Review-Zuweisung)](/assets/images/help/teams/review-assignment-button.png) +6. Wähle **Enable auto assignment** (Automatische Zuweisung aktivieren). ![Schaltfläche „Code review assignment" (Code-Review-Zuweisung)](/assets/images/help/teams/review-assignment-enable.png) +7. Benutze unter „How many team members should be assigned to review?" (Wie viele Teammitglieder sollen dem Review zugewiesen werden?) das Dropdownmenü und wähle die Anzahl der Prüfer, die jedem Pull Request zugewiesen werden sollen. ![Dropdownmenü „Number of reviewers" (Anzahl der Prüfer)](/assets/images/help/teams/review-assignment-number.png) +8. Benutze unter „Routing algorithm" (Routing-Algorithmen) das Dropdownmenü und wähle den Algorithmus, den Du benutzen möchtest. Weitere Informationen findest Du unter „[Routing-Algorithmen](#routing-algorithms)." ![Dropdownmenü „Routing algorithm" (Routing-Algorithmus)](/assets/images/help/teams/review-assignment-algorithm.png) +9. Um optional bestimmte Teammitglieder immer auszulassen, wähle **Never assign certain team members** (Weise bestimmte Teammitglieder nie zu). Dann wähle eines oder mehrere Teammitglieder, die Du immer auslassen willst. ![Kontrollkästchen und Dropdownmenü „Never assign certain team members" (Weise bestimmte Teammitglieder nie zu)](/assets/images/help/teams/review-assignment-skip-members.png) +10. Um optional nur diejenigen Teammitglieder zu informieren, die durch die Code-Review-Zuweisung für einen Pull-Request-Review betroffen sind, wähle unter „Notifications" (Benachrichtigungen) die Option **If assigning team members, don't notify the entire team** (Benachrichtige bei der Zuweisung einzelner Teammitglieder nicht das gesamte Team). ![Benachrichtigungen „Code review assignment" (Code-Review-Zuweisung)](/assets/images/help/teams/review-assignment-notifications.png) +11. Klicke auf **Save changes** (Änderungen speichern). + +### Code-Review-Zuweisungen deaktivieren +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Wähle **Enable auto assignment** (automatische Zuweisung aktivieren) um das Häkchen zu entfernen. ![Schaltfläche „Code review assignment" (Code-Review-Zuweisung)](/assets/images/help/teams/review-assignment-enable.png) +6. Klicke auf **Save changes** (Änderungen speichern). diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000..980d6b744f --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,69 @@ +--- +title: Geplante Erinnerungen für Dein Team verwalten +intro: Du kannst in Slack Erinnerungen erhalten, wenn auf dein Team Pull-Request-Reviews warten. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +### Über geplante Erinnerungen für Teams + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Team-Betreuer und Organisationsinhaber können geplante Erinnerungen für alle Pull Requests festlegen, für die ein Team zum Review angefordert wurde. Bevor Du eine geplante Erinnerung für Dein Team erstellen kannst, muss ein Organisationsinhaber Deinen Slack-Arbeitsbereich autorisieren. Weitere Informationen findest Du unter „[Geplante Erinnerungen für Deine Organisation verwalten](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)." + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Erstellen einer geplanten Erinnerung für ein Team +{% 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 %} +![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/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 %} + +### Eine geplante Erinnerung für ein Team verwalten +{% 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 %} +![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Eine geplante Erinnerung für ein Team löschen +{% 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 %} +![Schaltfläche „Scheduled reminders" (Geplante Erinnerungen)](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.delete %} + +### Weiterführende Informationen + +- „[Geplante Erinnerungen für Deine Organisation verwalten](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- „[Deine geplanten Erinnerungen verwalten](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/de-DE/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000..6c87b10d4e --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,42 @@ +--- +title: Team innerhalb der Hierarchie Deiner Organisation verschieben +intro: 'Team-Betreuer und Organisationsinhaber können ein Team einem übergeordneten Team unterordnen oder das übergeordnete Team eines untergeordneten Teams ändern oder entfernen.' +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 + - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Organisationsinhaber können das übergeordnete Team jedes Teams ändern. Team-Betreuer können das übergeordnete Team eines Teams ändern, wenn sie sowohl im untergeordneten als auch im übergeordneten Team Betreuer sind. Team-Betreuer ohne Betreuer-Berechtigungen im untergeordneten Team können das Hinzufügen eines übergeordneten oder untergeordneten Teams anfordern. Weitere Informationen findest Du unter „[Hinzufügen oder Ändern eines übergeordneten Teams anfordern](/articles/requesting-to-add-or-change-a-parent-team)“ und „[Hinzufügen eines untergeordneten Teams anfordern](/articles/requesting-to-add-a-child-team).“ + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% tip %} + +**Tipps:** +- Du kannst das übergeordnete Team eines Teams nicht zu einem nichtöffentlichen Team ändern. Weitere Informationen finden Sie unter „[Informationen zu Teams](/articles/about-teams)“. +- Du kannst ein übergeordnetes Team nicht unterhalb eines seiner untergeordneten Teams einordnen. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Klicke in der Liste der Teams auf den Namen des Teams, dessen übergeordnetes Team Du ändern möchtest. ![Liste der Teams der Organisation](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Wähle im Dropdownmenü ein übergeordnetes Team oder, um ein vorhandenes übergeordnetes Team zu entfernen, wähle **Clear selected value** (Ausgewählten Wert löschen) aus. ![Dropdownmenü mit einer Liste der Organisationsteams](/assets/images/help/teams/choose-parent-team.png) +7. Klicke auf **Update** (Aktualisieren). +{% data reusables.repositories.changed-repository-access-permissions %} +9. Klicke auf **Confirm new parent team** (Neues übergeordnetes Team bestätigen). ![Modales Feld mit Informationen zu den Änderungen an den Berechtigungen für den Repositoryzugriff](/assets/images/help/teams/confirm-new-parent-team.png) + +### Weiterführende Informationen + +- „[Informationen zu Teams](/articles/about-teams)“ diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000..9680e1b158 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,23 @@ +--- +title: Organisationsmitglieder aus einem Team entfernen +intro: 'Personen mit *Inhaber-* oder *Team-Betreuer-*Berechtigungen können Teammitglieder aus einem Team entfernen. Dies kann notwendig sein, wenn eine Person keinen Zugriff mehr auf ein Repository braucht, auf das sie durch ihre Teammitgliedschaft Zugriff erhält, oder wenn eine Person nicht mehr mit den Projekten eines Teams beschäftigt ist.' +redirect_from: + - /articles/removing-organization-members-from-a-team-early-access-program/ + - /articles/removing-organization-members-from-a-team + - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% 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. Wähle die Person(en) aus, die Du entfernen möchtest. ![Kontrollkästchen neben dem Organisationsmitglied](/assets/images/help/teams/team-member-check-box.png) +5. Klicke im Dropdownmenü über der Liste der Teammitglieder auf **Remove from team** (Aus Team entfernen). ![Dropdownmenü mit Option zum Ändern der Rolle](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/renaming-a-team.md new file mode 100644 index 0000000000..350d29591d --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/renaming-a-team.md @@ -0,0 +1,21 @@ +--- +title: Team umbenennen +intro: Team-Betreuer und Organisationsinhaber können den Namen und die Beschreibung eines Teams bearbeiten. +redirect_from: + - /articles/renaming-a-team + - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Gib einen neuen Namen für das Team ein oder ändere dessen Beschreibung. ![Felder für Teamname und -beschreibung](/assets/images/help/teams/team-name-description.png) +6. Klicke auf **Update** (Aktualisieren). diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000..2c77b13020 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,36 @@ +--- +title: Hinzufügen eines untergeordneten Teams anfordern +intro: 'Wenn Du in einem Team über Betreuer-Berechtigungen verfügst, kannst Du die Verschachtelung eines vorhandenen Teams innerhalb der Hierarchie Deiner Organisation unter Deinem Team anfordern.' +redirect_from: + - /articles/requesting-to-add-a-child-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Wenn Du das Hinzufügen eines untergeordneten Teams anforderst, wird an die Betreuer dieses Teams eine Anfrage gesendet. Sobald ein Betreuer dieses Teams Deiner Anfrage zustimmt, wird das Team innerhalb der Hierarchie Deiner Organisation unter Deinem Team eingeordnet. + +Wenn Du Organisationsinhaber bist oder über Team-Betreuer-Berechtigungen sowohl im untergeordneten als auch im übergeordneten Team verfügst, kannst Du das untergeordnete Team auch ohne Anforderung einer Genehmigung hinzufügen oder das übergeordnete Team des untergeordneten Teams direkt auf der Einstellungsseite des untergeordneten Teams ändern. Weitere Informationen findest Du unter „[Team innerhalb der Hierarchie Deiner Organisation verschieben](/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. Klicke in der Teamliste auf den Namen des Teams, dem Du das untergeordnete Team hinzufügen möchtest. ![Liste der Teams der Organisation](/assets/images/help/teams/click-team-name.png) +5. Klicke am Anfang der Teamseite auf {% octicon "people" aria-label="The people icon" %} **Teams**. ![Registerkarte „Teams" auf der Teamseite](/assets/images/help/teams/team-teams-tab.png) +6. Klicke auf **Add a team** (Team hinzufügen). ![Schaltfläche zum Hinzufügen eines Teams auf der Teamseite](/assets/images/help/teams/add-a-team.png) +7. Gib den Namen des Teams ein, das Du als untergeordnetes Team hinzufügen möchten, und wähle es aus dem Dropdownmenü aus. ![Textfeld zum Eingeben und Dropdown-Menü zum Auswählen des Namens des untergeordneten Teams](/assets/images/help/teams/type-child-team-name.png) +{% data reusables.repositories.changed-repository-access-permissions %} +9. Klicke auf **Confirm changes** (Änderungen bestätigen), um eine Anfrage zum Hinzufügen des untergeordneten Teams zu senden. ![Modales Feld mit Informationen zu den Änderungen an den Berechtigungen für den Repositoryzugriff](/assets/images/help/teams/confirm-new-parent-team.png) + +### Weiterführende Informationen + +- „[Informationen zu Teams](/articles/about-teams)“ +- „[Team innerhalb der Hierarchie Deiner Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy)“ +- „[Hinzufügen oder Ändern eines übergeordneten Teams anfordern](/articles/requesting-to-add-or-change-a-parent-team)“ diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000..74bbbdd4a2 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,36 @@ +--- +title: Hinzufügen oder Ändern eines übergeordneten Teams anfordern +intro: 'Wenn Du in einem Team über Betreuer-Berechtigungen verfügst, kannst Du die Verschachtelung Deiner Teams innerhalb der Hierarchie Deiner Organisation unter einem übergeordneten Team anfordern.' +redirect_from: + - /articles/requesting-to-add-or-change-a-parent-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Wenn Du das Hinzufügen oder die Änderung Deines übergeordneten Teams anforderst, wird an die Betreuer dieses Teams eine Anfrage gesendet. Sobald ein Betreuer des neuen übergeordneten Teams Deiner Anfrage zustimmt, wird Dein Team innerhalb der Hierarchie Deiner Organisation unter diesem Team eingeordnet. + +Wenn Du Organisationsinhaber bist oder über Team-Betreuer-Berechtigungen sowohl im untergeordneten als auch im übergeordneten Team verfügst, kannst Du das übergeordnete Team auch ohne Anforderung einer Genehmigung hinzufügen oder Dein übergeordnetes Team direkt auf der Einstellungsseite Deines Teams ändern. Weitere Informationen findest Du unter „[Team innerhalb der Hierarchie Deiner Organisation verschieben](/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. Klicke in der Teamliste auf den Namen des Teams, dem Du Dein Team unterordnen möchtest. ![Liste der Teams der Organisation](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Klicke unter „Parent team“ (Übergeordnetes Team) im Dropdownmenü „Select parent team“ (Übergeordnetes Team auswählen) auf den Namen des neuen übergeordneten Teams. ![Dropdownmenü mit einer Liste der Organisationsteams](/assets/images/help/teams/choose-parent-team.png) +7. Klicke auf **Save changes** (Änderungen speichern). +{% data reusables.repositories.changed-repository-access-permissions %} +9. Klicke auf **Confirm changes** (Änderungen bestätigen), um eine Anfrage zum Hinzufügen oder Ändern Deines übergeordneten Teams zu senden. ![Modales Feld mit Informationen zu den Änderungen an den Berechtigungen für den Repositoryzugriff](/assets/images/help/teams/confirm-new-parent-team.png) + +### Weiterführende Informationen + +- „[Informationen zu Teams](/articles/about-teams)“ +- „[Team innerhalb der Hierarchie Deiner Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy)“ +- „[Hinzufügen eines untergeordneten Teams anfordern](/articles/requesting-to-add-a-child-team)“ diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/de-DE/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000..87e6a008c3 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,24 @@ +--- +title: Profilbild Deines Teams festlegen +intro: 'Team-Betreuer und Organisationsinhaber können für Teams Profilbilder festlegen. Das Profilbild wird auf der Seite des Teams angezeigt.' +redirect_from: + - /articles/setting-your-team-s-profile-picture + - /articles/setting-your-teams-profile-picture + - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +Wenn für ein Team kein Profilbild festgelegt ist, wird stattdessen das Profilbild der Organisation angezeigt. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Klicke auf **Upload new picture** (Neues Bild hochladen), und wähle das gewünschte Profilbild aus. ![Neues Bild hochladen](/assets/images/help/teams/org-team-profile-picture-upload.png) +6. Klicke im Bild und ziehe den Mauszeiger, um das Bild nach Bedarf zuzuschneiden. Klicke anschließend auf **Set new team avatar** (Neuen Team-Avatar festlegen). ![Neuen Team-Avatar festlegen](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000..74e1eb7ab9 --- /dev/null +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,99 @@ +--- +title: Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren +intro: 'Du kannst ein {% data variables.product.product_name %}-Team mit einer Identitätsanbieter-Gruppe (IdP-Gruppe) synchronisieren, um Teammitglieder automatisch hinzuzufügen oder zu entfernen.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group +product: '{% data reusables.gated-features.team-synchronization %}' +permissions: 'Organisationsinhaber und Team-Betreuer können ein {% data variables.product.prodname_dotcom %} -Team mit einer IdP-Gruppe synchronisieren.' +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Informationen zur Teamsynchronisierung + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% if currentVersion == "free-pro-team@latest" %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif currentVersion == "github-ae@latest" %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. + +{% if currentVersion == "free-pro-team@latest" %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} + +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. You cannot manage team membership on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} or using the API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} +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).“ +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs. +{% endif %} + +Übergeordnete Teams können nicht mit IdP-Gruppen synchronisiert werden. Wenn das Team, das Du mit einer IdP-Gruppe verbinden möchtest, ein übergeordnetes Team ist, empfehlen wir, ein neues Team zu erstellen oder die verschachtelten Beziehungen zu entfernen, die aus Deinem Team ein übergeordnetes Team machen. Weitere Informationen findest Du unter „[Über Teams](/articles/about-teams#nested-teams)", „[Teams erstellen](/organizations/organizing-members-into-teams/creating-a-team)" und „[Ein Team in der Organisations-Hierarchie verschieben](/articles/moving-a-team-in-your-organizations-hierarchy)." + +Um den Repository-Zugriff für jedes {% data variables.product.prodname_dotcom %}-Team zu verwalten, einschließlich Teams, die mit einer IdP-Gruppe verbunden sind, musst Du Änderungen mit {% data variables.product.product_name %} vornehmen. Weitere Informationen findest Du unter „[Informationen zu Teams](/articles/about-teams)“ und „[Teamzugriff auf ein Organisations-Repository verwalten](/articles/managing-team-access-to-an-organization-repository).“ + +{% if currentVersion == "free-pro-team@latest" %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Anforderungen an Mitglieder synchronisierter Teams + +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.product_name %} only if: +- The person is a member of the organization on {% data variables.product.product_name %}. +- The person has already logged in with their user account on {% data variables.product.product_name %} 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.product_name %} 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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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. 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. 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)." + +{% endif %} + +### Vorrausetzungen + +{% if currentVersion == "free-pro-team@latest" %} +Before you can connect a {% data variables.product.product_name %} 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](/organizations/managing-saml-single-sign-on-for-your-organization/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 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).“ + +{% elsif currentVersion == "github-ae@latest" %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." + +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. For more information, see [Configure automatic user provisioning to GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) in the Microsoft Docs. +{% endif %} + +### Eine IdP-Gruppe mit einem Team verbinden + +When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% if currentVersion == "github-ae@latest" %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Benutze unter "Identity Provider Groups" (Identitätsanbieter-Gruppen) das Dropdownmenü und wähle bis zu 5 Identitätsanbieter-Gruppen aus. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. Klicke auf **Save changes** (Änderungen speichern). + +### Eine IdP-Gruppe von einem Team trennen + +Wenn Du eine IdP-Gruppe von einem {% data variables.product.prodname_dotcom %}-Team trennst, werden Teammitglieder, die dem {% data variables.product.prodname_dotcom %}-Team durch die IdP Gruppe zugewiesen wurden, aus dem Team entfernt. {% if currentVersion == "github-ae@latest" %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Klicke unter „Identity Provider Groups" (Identitätsanbieter-Gruppen) rechts von der IdP-Gruppe, die Du trennen möchtest, auf {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Klicke auf **Save changes** (Änderungen speichern). diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000..7a0d7a6ea7 --- /dev/null +++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -0,0 +1,60 @@ +--- +title: Informationen zu Zugriffsbeschränkungen für OAuth-Apps +intro: 'Organisationen können wählen, welche {% data variables.product.prodname_oauth_app %}s Zugriff auf ihre Repositorys und andere Ressourcen haben, indem sie {% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen aktivieren.' +redirect_from: + - /articles/about-third-party-application-restrictions/ + - /articles/about-oauth-app-access-restrictions + - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Wenn {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen aktiviert sind, können Organisationsmitglieder den {% data variables.product.prodname_oauth_app %}-Zugriff auf Organisationsressourcen nicht autorisieren. Organisationsmitglieder können die Genehmigung des Inhabers für {% data variables.product.prodname_oauth_app %}s beantragen, die sie verwenden möchten, und Organisationsinhaber erhalten eine Benachrichtigung über ausstehende Anfragen. + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% tip %} + +**Tipp**: Wenn eine Organisation keine {% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen eingerichtet hat, kann jede {% data variables.product.prodname_oauth_app %} mit Autorisierung eines Organisationsmitglieds auch auf die privaten Ressourcen der Organisation zugreifen. + +{% endtip %} + +### {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen einrichten + +Wenn ein Organisationsinhaber zum ersten Mal {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen einrichtet, trifft Folgendes zu: + +- **Anwendungen im Besitz der Organisation** erhalten automatisch Zugriff auf die Ressourcen der Organisation. +- **{% data variables.product.prodname_oauth_app %}s** verlieren sofort den Zugriff auf die Ressourcen der Organisation. +- **Vor Februar 2014 erstellte SSH-Schlüssel** verlieren sofort den Zugriff auf die Ressourcen der Organisation (dazu gehören auch Benutzer- und Deployment-Schlüssel). +- **Von {% data variables.product.prodname_oauth_app %}s im oder nach Februar 2014 erstellte SSH-Schlüssel** verlieren sofort den Zugriff auf die Ressourcen der Organisation. +- **Hook-Auslieferungen aus privaten Repositorys der Organisation** werden nicht mehr an nicht genehmigte {% data variables.product.prodname_oauth_app %}s gesendet. +- **API-Zugriff** auf private Ressourcen der Organisation ist für nicht genehmigte {% data variables.product.prodname_oauth_app %}s nicht verfügbar. Darüber hinaus gibt es keine privilegierten Aktionen zum Erstellen, Aktualisieren oder Löschen für öffentliche Ressourcen der Organisation. +- **Von Benutzern erstellte Hooks und vor Mai 2014** erstellte Hooks sind davon nicht betroffen. +- **Private Forks von organisationseigenen Repositorys** unterliegen den Zugriffsbeschränkungen der Organisation. + +### SSH-Zugriffsfehler beheben + +Wenn ein vor Februar 2014 erstellter SSH-Schlüssel den Zugriff auf eine Organisation mit aktivierten {% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen verliert, schlagen nachfolgende SSH-Zugriffsversuche fehl. Benutzern wird eine Fehlermeldung mit einer URL angezeigt, über die sie den Schlüssel genehmigen oder stattdessen einen vertrauenswürdigen Schlüssel hochladen können. + +### Webhooks + +Wenn einer {% data variables.product.prodname_oauth_app %} Zugriff auf die Organisation gewährt wird, nachdem die Einschränkungen aktiviert wurden, werden alle bereits vorhandenen Webhooks, die von dieser {% data variables.product.prodname_oauth_app %} erstellt wurden, weiter versendet. + +Wenn eine Organisation den Zugriff einer zuvor genehmigten {% data variables.product.prodname_oauth_app %} entfernt, werden alle bereits vorhandenen Webhooks, die von dieser Anwendung erstellt wurden, nicht mehr versendet (diese Hooks werden deaktiviert, aber nicht gelöscht). + +### Zugriffsbeschränkungen wieder aktivieren + +Wenn eine Organisation {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen deaktiviert und später wieder aktiviert, erhalten zuvor genehmigte {% data variables.product.prodname_oauth_app %}s automatisch Zugriff auf die Ressourcen der Organisation. + +### Weiterführende Informationen + +- „[{% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen für Deine Organisation aktivieren](/articles/enabling-oauth-app-access-restrictions-for-your-organization)“ +- „[{% data variables.product.prodname_oauth_app %}s für Ihre Organisation genehmigen](/articles/approving-oauth-apps-for-your-organization)“ +- „[Installierte Integrationen Deiner Organisation überprüfen](/articles/reviewing-your-organization-s-installed-integrations)“ +- „[Zugriff einer zuvor genehmigten {% data variables.product.prodname_oauth_app %} für Deine Organisation verweigern](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)“ +- „[{% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen für Deine Organisation deaktivieren](/articles/disabling-oauth-app-access-restrictions-for-your-organization)“ +- „[Von einer Organisation die Genehmigung für {% data variables.product.prodname_oauth_app %}s anfordern](/articles/requesting-organization-approval-for-oauth-apps)“ +- „[{% data variables.product.prodname_oauth_app %}s autorisieren](/articles/authorizing-oauth-apps)“ diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000..4bc2e96f49 --- /dev/null +++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: OAuth-Apps für Deine Organisation genehmigen +intro: 'Wenn ein Organisationsmitglied {% data variables.product.prodname_oauth_app %}-Zugriff auf Organisationsressourcen anfordert, können Organisationsinhaber die Anforderung genehmigen oder ablehnen.' +redirect_from: + - /articles/approving-third-party-applications-for-your-organization/ + - /articles/approving-oauth-apps-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +Wenn Einschränkungen für den {% data variables.product.prodname_oauth_app %}-Zugriff aktiviert sind, müssen Organisationsmitglieder [die Genehmigung von einem Organisationsinhaber anfordern](/articles/requesting-organization-approval-for-oauth-apps), bevor sie eine {% data variables.product.prodname_oauth_app %} autorisieren können, die Zugriff auf die Ressourcen der Organisation hat. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Klicke neben der Anwendung, die Du genehmigen möchtest, auf **Review** (Review). ![Link zum Anfordern eines Reviews](/assets/images/help/settings/settings-third-party-approve-review.png) +6. Wenn Du die Informationen zur angeforderten Anwendung überprüft hast, klicke auf **Grant access** (Zugriff gewähren). ![Schaltfläche „Grant access“ (Zugriff gewähren)](/assets/images/help/settings/settings-third-party-approve-grant.png) + +### Weiterführende Informationen + +- „[Informationen zu Einschränkungen für den {% data variables.product.prodname_oauth_app %}-Zugriff](/articles/about-oauth-app-access-restrictions)“ diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000..c61229af03 --- /dev/null +++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,20 @@ +--- +title: Zugriff einer zuvor genehmigten OAuth-App für Deine Organisation verweigern +intro: 'Wenn eine Organisation eine zuvor genehmigte {% data variables.product.prodname_oauth_app %} nicht mehr benötigt, können die Inhaber den Zugriff der Anwendung auf die Ressourcen der Organisation widerrufen.' +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 + - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Klicken Sie neben der Anwendung, die Sie deaktivieren möchten, auf {% octicon "pencil" aria-label="The edit icon" %}. ![Symbol für Bearbeiten](/assets/images/help/settings/settings-third-party-deny-edit.png) +6. Klicke auf **Deny access** (Zugriff verweigern). ![Schaltfläche „Deny confirmation" (Bestätigen der Verweigerung)](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..60cf10c14b --- /dev/null +++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: OAuth-App-Zugriffsbeschränkungen für Deine Organisation deaktivieren +intro: 'Organisationsinhaber können Einschränkungen für {% data variables.product.prodname_oauth_app %}s aufheben, die Zugriff auf die Ressourcen der Organisation haben.' +redirect_from: + - /articles/disabling-third-party-application-restrictions-for-your-organization/ + - /articles/disabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% danger %} + +**Warnung:** Wenn Du {% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen für Deine Organisation deaktivierst, autorisieren automatisch alle Mitglieder der Organisation den {% data variables.product.prodname_oauth_app %}-Zugriff auf die privaten Ressourcen der Organisation, wenn sie die Nutzung einer Anwendung in den Einstellungen ihrer persönlichen Konten genehmigen. + +{% enddanger %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Klicke auf **Remove restrictions** (Einschränkungen entfernen). ![Schaltfläche „Remove restrictions“ (Beschränkungen entfernen)](/assets/images/help/settings/settings-third-party-remove-restrictions.png) +6. Wenn Du die Informationen zum Deaktivieren der Beschränkungen von Drittanbieter-Anwendungen gelesen hast, klicke auf **Yes, remove application restrictions** (Ja, Anwendungsbeschränkungen entfernen). ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..498253b3b6 --- /dev/null +++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: OAuth-App-Zugriffsbeschränkungen für Deine Organisation aktivieren +intro: 'Organisationsinhaber können {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen aktivieren, um zu verhindern, dass nicht vertrauenswürdige Apps auf die Ressourcen der Organisation zugreifen, und gleichzeitig Organisationsmitgliedern die Nutzung von {% data variables.product.prodname_oauth_app %} für ihre persönlichen Konten zu erlauben.' +redirect_from: + - /articles/enabling-third-party-application-restrictions-for-your-organization/ + - /articles/enabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% warning %} + +**Warnings**: +- Durch die Aktivierung der {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen wird allen zuvor autorisierten {% data variables.product.prodname_oauth_app %}s und SSH-Schlüsseln der Zugriff auf die Organisation entzogen. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen](/articles/about-oauth-app-access-restrictions).“ +- Wenn Sie die {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen eingerichtet haben, stellen Sie sicher, dass Sie alle {% data variables.product.prodname_oauth_app %}s erneut autorisieren, die regelmäßig Zugriff auf die privaten Daten der Organisation benötigen. Alle Organisationsmitglieder müssen neue SSH-Schlüssel erstellen, und die Organisation muss nach Bedarf neue Deployment-Schlüssel erstellen. +- Wenn {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen aktiviert sind, können Anwendungen mit einem OAuth-Token auf Informationen zu {% data variables.product.prodname_marketplace %}-Transaktionen zugreifen. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Klicke unter „Third-party application access policy“ (Zugriffsrichtlinie für Drittanbieter-Anwendungen) auf **Setup application access restrictions** (Zugriffsbeschränkungen für Anwendungen einrichten). ![Schaltfläche „Set up restrictions" (Einrichten von Beschränkungen)](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) +6. Wenn Du die Informationen zu Drittanbieter-Zugriffsbeschränkungen gelesen hast, klicke auf **Restrict third-party application access** (Zugriff von Drittanbieter-Anwendungen beschränken). ![Schaltfläche „Restriction confirmation" (Beschränkungen bestätigen)](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/index.md new file mode 100644 index 0000000000..eb4cb336f2 --- /dev/null +++ b/translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -0,0 +1,19 @@ +--- +title: Zugriff auf die Daten Deiner Organisation einschränken +intro: 'Mit den Zugriffseinschränkungen von {% data variables.product.prodname_oauth_app %} können Organisationsinhaber den Zugriff nicht vertrauenswürdiger Apps auf die Daten der Organisation einschränken. Die Mitglieder der Organisation können dann {% data variables.product.prodname_oauth_app %}s unter ihren persönlichen Benutzerkonten verwenden, ohne die Organisationsdaten einem Risiko auszusetzen.' +redirect_from: + - /articles/restricting-access-to-your-organization-s-data + - /articles/restricting-access-to-your-organizations-data + - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data +versions: + free-pro-team: '*' +topics: + - organisationen + - teams +--- + +{% 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 %} \ No newline at end of file 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 8f9a3f5c6d..ad39378668 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 @@ -8,9 +8,13 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} +{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-self-hosted-runners-notice %} ### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} @@ -19,7 +23,7 @@ versions: You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. {% if currentVersion == "free-pro-team@latest" %} -#### Authenticating to {% data variables.product.prodname_github_container_registry %} +#### Bei {% data variables.product.prodname_github_container_registry %} authentifizieren {% data reusables.package_registry.container-registry-beta %} @@ -33,7 +37,46 @@ For an authentication example, see "[Authenticating with the {% data variables.p {% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The `GITHUB_TOKEN` has `read:packages` and `write:packages` scopes to the current repository. For forks, the token also has the `read:packages` scope for the parent repository. -You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." +You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. Weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". + +### About permissions and package access for repository-owned packages + +{% note %} + +**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`. + +{% endnote %} + +Wenn Sie GitHub Actions aktivieren, installiert GitHub eine GitHub App im Repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. Die Berechtigungen des Tokens sind auf das Repository beschränkt, in dem sich der Workflow befindet. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)." + +{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow. + +{% if currentVersion == "free-pro-team@latest" %} +### About permissions and package access for {% data variables.product.prodname_container_registry %} + +The {% data variables.product.prodname_container_registry %} (`ghcr.io`) allows users to create and administer containers as free-standing resources at the organization level. Containers can be owned by an organization or personal user account and you can customize access to each of your containers separately from repository permissions. + +All workflows accessing the {% data variables.product.prodname_container_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." + +### Default permissions and access settings for containers modified through workflows + +When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well. + +For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then: +- The container inherits the visibility and permissions model of the repository where the workflow is run. +- Repository admins where the workflow is run become the admins of the container once the container is created. + +These are more examples of how default permissions work for workflows that manage packages. + +| {% data variables.product.prodname_actions %} workflow task | Default permissions and access | +| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Download an existing container | - If the container is public, any workflow running in any repository can download the container.
- If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise
- If the container is private, only workflows running in repositories that are given read permission on that container can download the container.
| +| Upload a new version to an existing container | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container. | +| Delete a container or versions of a container | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container. | + +You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." + +{% endif %} ### Publishing a package using an action @@ -45,7 +88,7 @@ The following example demonstrates how you can use {% data variables.product.pro - Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML: {% raw %} - ``` + ```yaml{:copy} name: Create and publish a package on: push: @@ -99,16 +142,14 @@ The following example demonstrates how you can use {% data variables.product.pro with: username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - registry: docker.pkg.github.com + registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %} repository: ${{ github.repository }}/octo-image tag_with_sha: true tag_with_ref: true ``` {% endraw %} - The relevant settings are explained in the following table: - - + The relevant settings are explained in the following table:
@@ -289,7 +328,7 @@ tag_with_sha: true
@@ -251,14 +292,12 @@ password: ${{ secrets.GITHUB_TOKEN }}
-{% raw %} ```yaml -registry: docker.pkg.github.com +registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %} ``` -{% endraw %} - Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. + Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace YOUR-HOSTNAME with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use ghcr.io as the hostname.{% endif %}
- + {% raw %} ```yaml tag_with_ref: true @@ -302,17 +341,95 @@ tag_with_ref: true
-- This new workflow will run automatically every time you push a change to the repository. You can view the progress in the **Actions** tab. +- This new workflow will run automatically every time you push a change to a branch named `release` in 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. -Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %} +Installing packages hosted by the {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% 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` cannot install packages from any private repository besides the repository where the action runs. You cannot currently use `GITHUB_TOKEN` to authenticate to {% data variables.product.prodname_github_container_registry %}. {% endif %} {% data reusables.package_registry.actions-configuration %} + +{% if currentVersion == "free-pro-team@latest" %} +### Upgrading a workflow that accesses `ghcr.io` + +{% data reusables.package_registry.github-token-security-over-pat %} + +Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." + +1. Navigate to your package landing page. +1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) +2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png) + {% note %} + + **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/guides/configuring-access-control-and-visibility-for-container-images#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a container image](/packages/guides/connecting-a-repository-to-a-container-image)." + + {% endnote %} +3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) +5. Open your workflow file. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. + +For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate. + +{% raw %} +```yaml{:copy} +name: Demo Push + +on: + push: + # Publish `master` as Docker `latest` image. + branches: + - master + - seed + + # Publish `v1.2.3` tags as releases. + tags: + - v* + + # Run tests for any PRs. + pull_request: + +env: + IMAGE_NAME: ghtoken_product_demo + +jobs: + # Push image to GitHub Packages. + # See also https://docs.docker.com/docker-hub/builds/ + push: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Build image + run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}" + + - name: Log into registry + # This is where you will update the PAT to GITHUB_TOKEN + run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin + + - name: Push image + run: | + IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME + + # Change all uppercase to lowercase + IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]') + # Strip git ref prefix from version + VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,') + # Strip "v" prefix from tag name + [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//') + # Use Docker `latest` tag convention + [ "$VERSION" == "master" ] && VERSION=latest + echo IMAGE_ID=$IMAGE_ID + echo VERSION=$VERSION + docker tag $IMAGE_NAME $IMAGE_ID:$VERSION + docker push $IMAGE_ID:$VERSION +``` +{% endraw %} + +{% endif %} diff --git a/translations/de-DE/content/packages/index.md b/translations/de-DE/content/packages/index.md index 56deb1e548..5d5b43507f 100644 --- a/translations/de-DE/content/packages/index.md +++ b/translations/de-DE/content/packages/index.md @@ -20,8 +20,8 @@ featuredLinks: - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - label: 'packages' - prefix: 'Packages: ' + label: 'Pakete' + prefix: 'Packages:' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..daffd9939e --- /dev/null +++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -0,0 +1,68 @@ +--- +title: Informationen zu benutzerdefinierten Domänen und GitHub Pages +intro: '{% data variables.product.prodname_pages %} unterstützt die Verwendung benutzerdefinierter Domänen oder das Ändern des Roots Deiner Website-URL vom Standard, beispielsweise ''octocat.github.io'', in jede Domäne, die Dir gehört.' +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 + - /github/working-with-github-pages/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Seiten +--- + +### Unterstützte benutzerdefinierte Domänen + +{% data variables.product.prodname_pages %} unterstützt zwei Domänen-Typen: Subdomänen und Apex-Domänen. Eine Liste der nicht unterstützten benutzerdefinierten Domänen findest Du unter „[Fehlerbehebung bei benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported).“ + +| Unterstützter benutzerdefinierter Domänen-Typ | Beispiel | +| --------------------------------------------- | ------------------ | +| `www`-Subdomäne | `www.example.com` | +| Benutzerdefinierte Subdomäne | `blog.example.com` | +| Apex-Domäne | `example.com` | + +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." + +Wir empfehlen, immer eine `www`-Subdomäne zu verwenden, auch bei Verwendung einer Apex-Domäne. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site).“ + +Nachdem Du einen benutzerdefinierte Domäne für eine Benutzer- oder Organisations-Website konfiguriert hast, wird die benutzerdefinierte Domäne den `.github.io`- oder `.github.io`-Bestandteil der URL für alle dem Konto gehörende Projekt-Websites ersetzen, welche keine benutzerdefinierte Domäne konfiguriert haben. Wenn beispielsweise die benutzerdefinierte Domäne Deiner Benutzer-Website `www.octocat.com` ist und Du eine Projekt-Website besitzt, für die keine benutzerdefinierte Domäne konfiguriert ist und die aus einem Repository namens `octo-project` veröffentlicht wurde, lautet die URL der {% data variables.product.prodname_pages %}-Website dieses Repositorys `www.octocat.com/octo-project`. + +### Eine Subdomäne für Deine {% data variables.product.prodname_pages %}-Website verwenden + +Eine Subdomäne ist der Teil einer URL vor der Root-Domäne. Du kannst Deine Subdomäne als `www` oder als bestimmten Bereich Deiner Website, z. B. `blog.example.com`, konfigurieren. + +Subdomänen werden mit dem Eintrag `CNAME` über Deinen DNS-Provider konfiguriert. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain).“ + +#### `www`-Subdomänen + +Eine `www`-Subdomäne ist der am häufigsten verwendete Subdomänen-Typ. Beispielsweise enthält `www.example.com` eine `www`-Subdomäne. + +`www`-Subdomänen sind die stabilsten benutzerdefinierten Domänen, da `www`-Subdomänen nicht von Änderungen bei den IP-Adressen der Server von {% data variables.product.product_name %} betroffen sind. + +#### Benutzerdefinierte Subdomänen + +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Benutzerdefinierte Subdomänen kommen meistens dann zum Einsatz, wenn Du zwei getrennte Bereiche Deiner Website wünschst. Du kannst beispielsweise eine Website namens `blog.example.com` erstellen und diesen Bereich unabhängig von `www.example.com` gestalten. + +### Eine Apex-Domäne für Deine {% data variables.product.prodname_pages %}-Website verwenden + +Eine Apex-Domäne ist eine benutzerdefinierte Domäne, die keine Subdomäne wie `example.com` enthält. Apex-Domänen sind auch als Basis-, Bare-, Naked-, Root-Apex- oder Zone-Apex-Domänen bekannt. + +Eine Apex-Domäne wird mit einem `A`-, `ALIAS`- oder `ANAME`-Eintrag über Deinen DNS-Provider konfiguriert. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain).“ + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." + +### Benutzerdefinierte Domänen aktualisieren, wenn Deine {% data variables.product.prodname_pages %}-Website deaktiviert ist + +Wenn Ihre {% data variables.product.prodname_pages %}-Website deaktiviert ist, aber eine benutzerdefinierte Domain für sie eingerichtet wurde, sollten sie den DNS-Eintrag bei Ihrem DNS-Provider umgehend aktualisieren oder entfernen, um eine Domain-Übernahme zu verhindern. Wenn Du eine benutzerdefinierte Domäne bei Deinem DNS-Provider konfigurierst, während Deine Website deaktiviert ist, könnte ein Dritter eine Website auf einer Deiner Subdomänen hosten. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site).“ + +Es gibt mehrere Gründe, weshalb Deine Website automatisch deaktiviert sein könnte. + +- Wenn Du ein Herunterstufen von {% data variables.product.prodname_pro %} auf {% data variables.product.prodname_free_user %} durchführst, wird die Veröffentlichung aller {% data variables.product.prodname_pages %}-Websites, die über private Repositorys in Deinem Konto veröffentlicht wurden, rückgängig gemacht. Weitere Informationen findest Du unter „[Den {% data variables.product.prodname_dotcom %}-Abrechnungsplan herunterstufen](/articles/downgrading-your-github-billing-plan).“ +- Wenn Du ein privates Repository zu einem persönlichen Konto überträgst, das {% data variables.product.prodname_free_user %} verwendet, verliert das Repository den Zugriff auf die {% data variables.product.prodname_pages %}-Funktion, und die aktuelle Veröffentlichung der {% data variables.product.prodname_pages %}-Website wird rückgängig gemacht. Weitere Informationen findest Du unter „[Ein Repository übertragen](/articles/transferring-a-repository).“ + +### Weiterführende Informationen + +- „[Fehlerbehebung bei benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)“ diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md new file mode 100644 index 0000000000..b85fe26679 --- /dev/null +++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -0,0 +1,23 @@ +--- +title: Eine benutzerdefinierte Domäne für Deine GitHub Pages-Website konfigurieren +intro: 'Sie können den Domain-Namen Ihrer {% data variables.product.prodname_pages %}-Website anpassen.' +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 + - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Seiten +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000..36f087e85b --- /dev/null +++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,121 @@ +--- +title: Eine benutzerdefinierte Domäne für Deine GitHub Pages-Website verwalten +intro: 'Sie können bestimmte DNS-Datensätze und die Repository-Einstellungen so einrichten oder aktualisieren, dass die Standard-Domain für Ihre {% data variables.product.prodname_pages %}-Website auf eine benutzerdefinierte Domain verweist.' +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 + - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Seiten +--- + +Personen mit Administratorberechtigungen für ein Repository können eine benutzerdefinierte Domäne für eine {% data variables.product.prodname_pages %}-Website konfigurieren. + +### Informationen zur Konfiguration einer benutzerdefinierten Domäne + +Nimm die benutzerdefinierte Domäne zunächst in die {% data variables.product.prodname_pages %} Website auf, bevor Du die benutzerdefinierte Domäne bei Deinem DNS-Provider konfigurierst. Wenn Sie Ihre benutzerdefinierte Domain bei Ihrem DNS-Provider konfigurieren, ohne Ihre benutzerdefinierte Domain zu {% data variables.product.product_name %} hinzuzufügen, könnte ein Dritter eine Website auf einer Ihrer Subdomains hosten. + +{% windows %} + +Der Befehl `dig`, mit dem die korrekte Konfiguration der DNS-Datensätze überprüft wird, ist nicht in Windows enthalten. Bevor Du die korrekte Konfiguration der DNS-Datensätze überprüfen kannst, musst Du [BIND](https://www.isc.org/bind/) installieren. + +{% endwindows %} + +{% note %} + +**Hinweis:** Die Verbreitung von DNS-Änderungen kann bis zu 24 Stunden dauern. + +{% endnote %} + +### Eine Subdomäne konfigurieren + +To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings, which will create a CNAME file in your site’s repository. After that, configure a CNAME record with your DNS provider. + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Unter „Custom domain" (Benutzerdefinierte Domäne) gibst Du Deine benutzerdefinierte Domäne ein, dann klicke auf **Save** (Speichern). Dadurch wird eine Commit erzeugt, der eine _CNAME_-Datei im Stammverzeichnis Deiner Veröffentlichungsquelle hinzufügt. ![Schaltfläche „Save custom domain" (Speichere benutzerdefinierte Domäne)](/assets/images/help/pages/save-custom-subdomain.png) +5. Navigiere zu Deinem DNS-Provider, und erstelle einen `CNAME` Datensatz, welcher Deine Subdomäne auf die Standarddomäne Deiner Website verweist. Soll beispielsweise die Subdomäne `www.example.com` für Deine Benutzer-Website verwendet werden, erstelle einen `CNAME`-Datensatz, mit dem `www.example.com` auf `.github.io` verweist. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `.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 %} + +{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} +{% data reusables.command_line.open_the_multi_os_terminal %} +6. Prüfe die korrekte Konfiguration des DNS-Datensatzes mit dem Befehl `dig`, und ersetze _WWW.EXAMPLE.COM_ dabei durch Deine Subdomäne. +```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 %} + +### Eine Apex-Domäne konfigurieren + +To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider. + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)." + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Unter „Custom domain" (Benutzerdefinierte Domäne) gibst Du Deine benutzerdefinierte Domäne ein, dann klicke auf **Save** (Speichern). Dadurch wird eine Commit erzeugt, der eine _CNAME_-Datei im Stammverzeichnis Deiner Veröffentlichungsquelle hinzufügt. ![Schaltfläche „Save custom domain" (Speichere benutzerdefinierte Domäne)](/assets/images/help/pages/save-custom-apex-domain.png) +5. Navigiere zu Deinem DNS-Provider, und erstelle entweder einen `ALIAS`-, einen `ANAME`- oder einen `A`-Datensatz. {% data reusables.pages.contact-dns-provider %} + - Soll ein `ALIAS`- oder `ANAME`-Datensatz erstellt werden, verweise Deine Apex-Domäne auf die Standarddomäne Deiner Website. {% data reusables.pages.default-domain-information %} + - To create `A` records, point your apex domain to the IP addresses for {% 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. Prüfe die korrekte Konfiguration des DNS-Datensatzes mit dem Befehl `dig`, und ersetze _EXAMPLE.COM_ dabei durch Deine Apex-Domäne. Prüfe, ob die Ergebnisse mit den obigen IP-Adressen für {% data variables.product.prodname_pages %} übereinstimmen. + ```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 %} + +### Configuring an apex domain and the `www` subdomain variant + +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. + +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." + +After you configure the apex domain, you must to configure a CNAME record with your DNS provider. + +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. +```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 +``` +### Removing a custom domain + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain," click **Remove**. ![Schaltfläche „Save custom domain" (Speichere benutzerdefinierte Domäne)](/assets/images/help/pages/remove-custom-domain.png) + +### Weiterführende Informationen + +- „[Fehlerbehebung bei benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)“ diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..225ebe1c11 --- /dev/null +++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,65 @@ +--- +title: Troubleshooting custom domains and GitHub Pages +intro: 'Bei Problemen mit benutzerdefinierten Domänen oder HTTPS für Deine {% data variables.product.prodname_pages %}-Website kannst Du zur Fehlerbehebung nach häufigen Fehlern suchen.' +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 + - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Seiten +--- + +### _CNAME_-Fehler + +Benutzerdefinierte Domänen werden in einer _CNAME_-Datei im Stammverzeichnis der Veröffentlichungsquelle gespeichert. Du kannst diese Datei wahlweise in den Repository-Einstellungen oder manuell hinzufügen oder aktualisieren. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site).“ + +Damit Deine Website in der richtigen Domäne gerendert wird, prüfe, ob die _CNAME_-Datei sich noch im Repository befindet. Zahlreiche Generatoren für statische Websites erzwingen beispielsweise einen Push-Vorgang an das Repository, wodurch allenfalls die _CNAME_-Datei überschrieben wird, die Du beim Konfigurieren der benutzerdefinierten Domäne in das Repository eingefügt hast. Wenn Sie Ihre Website lokal erstellen und generierte Dateien per Push-Vorgang an {% data variables.product.product_name %} übertragen, müssen Sie in jedem Fall zunächst einen Pull-Vorgang für den Commit vornehmen, mit dem die _CNAME_-Datei in das lokale Repository eingefügt wurde, sodass die Datei in den Build aufgenommen wird. + +Prüfe anschließend, ob die _CNAME_-Datei ordnungsgemäß formatiert ist. + +- Der Name der _CNAME_-Datei darf nur Großbuchstaben enthalten. +- Die _CNAME_-Datei darf nur eine Domäne umfassen. Sollen mehrere Domänen auf Deine Website verweisen, lass Dir von Deinem DNS-Provider eine Weiterleitung einrichten. +- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`. +- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. Enthält beispielsweise die _CNAME_-Datei eines anderen Repositorys die Domäne `example.com`, kannst Du `example.com` nicht in die _CNAME_-Datei für Dein Repository aufnehmen. + +### Fehlerhafte DNS-Konfiguration + +Falls Du die Standard-Domäne für Deine Website nicht ohne Weiteres auf die benutzerdefinierte Domäne verweisen kannst, wende Dich an Deinen DNS-Provider. + +Du kannst auch testen, ob die DNS-Einträge Deiner benutzerdefinierten Domäne fehlerfrei konfiguriert sind. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site).“ + +### Nicht unterstützte, benutzerdefinierte Domänen-Namen + +Wird Deine benutzerdefinierte Domäne nicht unterstützt, musst Du Deine Domäne durch eine unterstützte Domäne ersetzen. Du kannst auch bei Deinem DNS-Provider erfragen, ob Weiterleitungsdienste für Domänen-Namen angeboten werden. + +Deine Website darf nicht: +- Mehrere Apex-Domänen umfassen. Beispiel: `example.com` und `anotherexample.com`. +- Mehrere `www`-Subdomänen umfassen. Beispiel: `www.example.com` und `www.anotherexample.com`. +- Sowohl eine Apex-Domäne als auch eine benutzerdefinierte Subdomäne umfassen. Beispiel: `example.com` und `docs.example.com`. + + The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. Weitere Informationen findest Du unter „[Verwalten einer benutzerdefinierten Domäne für Deine {% data variables.product.prodname_pages %}-Website](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)." + +{% data reusables.pages.wildcard-dns-warning %} + +Eine Liste der unterstützten benutzerdefinierten Domänen findest Du unter „[Informationen zu benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains).“ + +### HTTPS-Fehler + +Zugriff über HTTPS ist auf {% data variables.product.prodname_pages %}-Websites mit benutzerdefinierten Domänen, die korrekt mit _CNAME_-, `ALIAS`-, `ANAME`- oder `A`-DNS-Einträgen konfiguriert sind, problemlos möglich. Weitere Informationen finden Sie unter „[Ihre {% data variables.product.prodname_pages %}-Website mit HTTPS schützen](/articles/securing-your-github-pages-site-with-https)“. + +Nach der Konfiguration Deiner benutzerdefinierten Domäne kann es bis zu einer Stunde dauern, bis die Website über HTTPS verfügbar ist. Nach einer Aktualisierung bestehender DNS-Einstellungen musst Du Deine benutzerdefinierte Domäne zudem eventuell aus dem Repository Deiner Website entfernen und erneut dort einfügen, um den Prozess der HTTPS-Aktivierung zu initiieren. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site).“ + +Wenn Du CAA-Einträge (Certification Authority Authorization) verwendest, muss mindestens ein CAA-Eintrag mit dem Wert `letsencrypt.org` vorhanden sein, wenn Deine Website über HTTPS zugänglich sein soll. Weitere Informationen finden Sie in der Let's Encrypt-Dokumentation unter „[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)“. + +### URL-Formatierung unter Linux + +Wenn die URL für Deine Website einen Benutzernamen oder einen Organisationsnamen enthält, der mit einem Bindestrich beginnt oder darauf endet oder aufeinanderfolgende Bindestriche enthält, wird Linux-Benutzern eine Fehlermeldung angezeigt, wenn sie versuchen, die Website aufzurufen. Ändere zum Beheben dieses Problems Deinen {% data variables.product.product_name %}-Benutzernamen, um die nicht alphanumerischen Zeichen zu entfernen. Weitere Informationen findest Du unter „[{% data variables.product.prodname_dotcom %}-Benutzernamen ändern](/articles/changing-your-github-username/).“ + +### Browser-Cache + +Wenn Du Deine benutzerdefinierte Domäne erst vor kurzem geändert oder entfernt hast und in Deinem Browser nicht auf die neue URL zugreifen kannst, solltest Du den Cache Deines Browsers löschen. Die neue URL ist danach vermutlich erreichbar. Informationen zum Löschen Deines Caches findest Du in der Dokumentation Deines Browsers. diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000..8a8b4664cf --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -0,0 +1,150 @@ +--- +title: Informationen zu GitHub Pages +intro: 'Mit {% data variables.product.prodname_pages %} können Sie eine Website zu Ihrer Person, Ihrer Organisation oder Ihrem Projekt direkt aus einem {% data variables.product.product_name %}-Repository hosten.' +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 + - /github/working-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +### Informationen zu {% data variables.product.prodname_pages %} + +{% data variables.product.prodname_pages %} ist ein Hosting-Dienst für statische Websites, der HTML-, CSS- und JavaScript-Dateien direkt aus einem Repository auf {% data variables.product.product_name %} bezieht, diese Dateien optional einem Build-Prozess unterzieht und eine Website veröffentlicht. Beispiele für {% data variables.product.prodname_pages %}-Websites findest Du in der [{% data variables.product.prodname_pages %}-Beispielsammlung](https://github.com/collections/github-pages-examples). + +{% if currentVersion == "free-pro-team@latest" %} +Sie können Ihre Website auf der Domain `github.io` von {% data variables.product.prodname_dotcom %} oder Ihrer eigenen benutzerdefinierten Domain hosten. Weitere Informationen finden Sie unter „[Eine benutzerdefinierte Domain mit {% data variables.product.prodname_pages %} verwenden](/articles/using-a-custom-domain-with-github-pages)“. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +Informationen zu den ersten Schritten findest Du unter „[Eine {% data variables.product.prodname_pages %}-Website erstellen](/articles/creating-a-github-pages-site).“ + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." +{% endif %} + +### Arten von {% data variables.product.prodname_pages %}-Websites + +Es gibt drei Arten von {% data variables.product.prodname_pages %}-Websites: Projekt-, Benutzer- und Organisations-Websites. Projekt-Websites sind mit einem bestimmten Projekt verbunden, das auf {% data variables.product.product_name %} gehostet wird, z. B. einer JavaScript-Bibliothek oder einer Rezeptsammlung. Benutzer- und Organisations-Websites sind mit einem bestimmten {% data variables.product.product_name %}-Konto verbunden. + +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 %} + +Die Quelldateien für eine Projekt-Website werden im selben Repository gespeichert wie das zugehörige Projekt. {% 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" %} +If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Weitere Informationen dazu, wie sich die URL Ihrer Website bei benutzerdefinierten Domains ändert, finden Sie unter „[Informationen zu benutzerdefinierten Domains und {% 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 %}. Für Projekt-Websites gibt es keine Beschränkung, egal, ob sie einer Organisation oder einem Benutzerkonto gehören. + +{% if enterpriseServerVersions contains currentVersion %} +Unter welcher URL Ihre Website erreichbar ist, hängt davon ab, ob die Subdomain-Isolation für {% data variables.product.product_location %} aktiviert ist. + +| Art der Website | Subdomänen-Isolation aktiviert | Subdomänen-Isolation deaktiviert | +| --------------- | ------------------------------ | -------------------------------- | +| | | | + 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///` + +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" %} +{% note %} + +**Note:** Repositories using the legacy `.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://.github.com` to `http(s)://.github.io`. If both a `.github.com` and `.github.io` repository exist, only the `.github.io` repository will be published. + +{% endnote %} +{% endif %} + +### Veröffentlichungsquellen für {% data variables.product.prodname_pages %}-Websites + +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" %} + +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. + +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. Weitere Informationen findest Du unter „[Eine Veröffentlichungsquelle für Deine {% data variables.product.prodname_pages %}-Website konfigurieren](/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`. Weitere Informationen zu _CNAME_-Dateien findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site)“.{% endif %} + +{% else %} + +Die standardmäßige Veröffentlichungsquelle für Benutzer- und Organisations-Websites ist der `master`-Branch. Wenn das Repository Deiner Benutzer- oder Organisations-Website einen `master`-Branch aufweist, wird Deine Website automatisch von diesem Branch veröffentlicht. Du kannst keine andere Veröffentlichungsquelle für Benutzer- oder Organisations-Websites auswählen. + +Die standardmäßige Veröffentlichungsquelle für Projekt-Websites ist der `gh-pages`-Branch. Wenn das Repository Deiner Projekt-Website einen `gh-pages`-Branch aufweist, wird Deine Website automatisch von diesem Branch veröffentlicht. + +Du kannst Projekt-Websites auch vom `master`-Branch oder einem `/docs`-Ordner auf dem `master`-Branch veröffentlichen. Um Deine Website aus einer dieser Quellen zu veröffentlichen, musst Du eine andere Veröffentlichungsquelle konfigurieren. Weitere Informationen findest Du unter „[Eine Veröffentlichungsquelle für Deine {% data variables.product.prodname_pages %}-Website konfigurieren](/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`. Weitere Informationen zu _CNAME_-Dateien findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site)“.{% endif %} + +Du kannst Deine Projekt-Website nicht aus einem anderen Branch veröffentlichen, auch wenn der Standard-Branch nicht `Master` oder `gh-pages` ist. + +{% endif %} + +### Generatoren für statische Websites + +{% data variables.product.prodname_pages %} veröffentlicht alle statische Dateien, die Sie zu Ihrem Repository pushen. Sie können eigene statische Dateien erstellen oder einen Generator für statische Websites verwenden, der die Website für Sie erstellt. Darüber hinaus können Sie Ihren eigenen Build-Prozess lokal oder auf einem anderen Server anpassen. Wir empfehlen Jekyll, einen Generator für statische Websites mit integrierter Unterstützung von {% data variables.product.prodname_pages %} und einem vereinfachten Build-Prozess. Weitere Informationen finden Sie unter „[Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll)“. + +{% data variables.product.prodname_pages %} verwendet standardmäßig Jekyll für die Erstellung Ihrer Website. Wenn Sie einen anderen Generator für statische Websites als Jekyll verwenden möchten, müssen Sie den Jekyll-Build-Prozess deaktivieren. Erstellen Sie dazu im Root Ihrer Veröffentlichungsquelle eine leere Datei mit dem Namen `.nojekyll` und folgen den Anweisungen des gewünschten Generators, um Ihre Website lokal zu erstellen. + +{% data variables.product.prodname_pages %} unterstützt keine serverseitigen Sprachen wie PHP, Ruby oder Python. + +### Richtlinien für die Verwendung von {% data variables.product.prodname_pages %} + +{% if currentVersion == "free-pro-team@latest" %} +- {% data variables.product.prodname_pages %}-Websites, die nach dem 15. Juni 2016 und mittels `github.io`-Domains erstellt wurden, werden über HTTPS bereitgestellt. Wenn Du Deine Website vor dem 15. Juni 2016 erstellt hast, kannst Du die HTTPS-Unterstützung für den Traffic zu Deiner Website aktivieren. Weitere Informationen findest Du unter „[{% data variables.product.prodname_pages %}-Website mit HTTPS schützen](/articles/securing-your-github-pages-site-with-https).“ +- {% data reusables.pages.no_sensitive_data_pages %} +- Ihre Nutzung von {% data variables.product.prodname_pages %} unterliegt den [GitHub-Nutzungsbedingungen](/articles/github-terms-of-service/), einschließlich des Weiterverkaufsverbots. + +#### Nutzungseinschränkungen +{% endif %} +{% data variables.product.prodname_pages %} unterliegen den folgenden Nutzungseinschränkungen: + + - {% 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 %} + - Veröffentlichte {% data variables.product.prodname_pages %}-Websites dürfen nicht größer als 1 GB sein. +{% if currentVersion == "free-pro-team@latest" %} + - {% data variables.product.prodname_pages %}-Websites besitzen eine *weiche* Bandbreitenbegrenzung von 100 GB pro Monat. + - {% data variables.product.prodname_pages %}-Websites besitzen eine *weiche* Begrenzung von 10 Builds pro Stunde. + +Wenn Ihre Website diese Nutzungskontingente überschreitet, kann Ihre Website ggf. nicht bedient werden oder Sie erhalten eine höfliche E-Mail von {% data variables.contact.contact_support %}, in der Strategien vorgeschlagen werden, um die Auswirkung Ihrer Website auf unsere Server zu reduzieren. Dazu zählen das Einsetzen eines Drittanbieter-CDNs (Content Distribution Networks) vor Ihrer Website, die Nutzung anderer {% data variables.product.prodname_dotcom %}-Features, beispielsweise Veröffentlichungen, oder der Wechsel zu einem anderen Hosting-Dienst, der ggf. besser zu Ihren Anforderungen passt. + +#### Verbotene Verwendungen + +{% data variables.product.prodname_pages %} soll oder darf nicht als kostenloser Web-Hosting-Dienst zum Betreiben Ihrer Online-Geschäfts-, E-Commerce-Website oder jeder anderen Website verwendet werden, die in erster Linie darauf ausgerichtet ist, kommerzielle Transaktionen zu erleichtern oder kommerzielle Software-as-a-Service-Lösungen (SaaS) bereitzustellen. + +In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. For a list of prohibited uses, see "[{% data variables.product.prodname_dotcom %}'s Additional Product Terms for {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)." +{% endif %} + +### MIME-Typen auf {% data variables.product.prodname_pages %} + +Ein MIME-Typ ist ein Header, den ein Server an einen Browser übermittelt und der Informationen zur Art und zum Format der Dateien enthält, die der Browser angefordert hat. {% data variables.product.prodname_pages %} unterstützt mehr als 750 MIME-Typen bei Tausenden von Dateierweiterungen. Die Liste der unterstützten MIME-Typen wird aus dem [mime-db-Projekt](https://github.com/jshttp/mime-db) erzeugt. + +Zwar können Sie keine benutzerdefinierten MIME-Typen für einzelne Dateien oder Repositorys festlegen. Sie können jedoch MIME-Typen für die Verwendung auf {% data variables.product.prodname_pages %} hinzufügen oder ändern. Weitere Informationen findest Du in den [Beitragsrichtlinien für mime-db](https://github.com/jshttp/mime-db#adding-custom-media-types). + +### Weiterführende Informationen + +- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) auf {% data variables.product.prodname_learning %} +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/de-DE/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000..915bf2e3b0 --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,46 @@ +--- +title: Ein Design mit dem Theme Chooser zu Deiner GitHub Pages-Website hinzufügen +intro: 'Sie können zu Ihrer {% data variables.product.prodname_pages %}-Website ein Design hinzufügen, um das Aussehen der Website anzupassen.' +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Seiten +--- + +Personen mit Administratorberechtigungen für ein Repository können mit dem Theme Chooser ein Design zu einer {% data variables.product.prodname_pages %}-Website hinzufügen. + +### Informationen zum Theme Chooser + +Der Theme Chooser fügt ein Jekyll-Design zu Deinem Repository hinzu. Weitere Informationen zu Jekyll findest Du unter „[Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll).“ + +Wie der Theme Chooser funktioniert, hängt davon ab, ob Dein Repository öffentlich oder privat ist. + - Wenn {% data variables.product.prodname_pages %} bereits für Dein Repository aktiviert ist, fügt der Theme Chooser Dein Design zur aktuellen Veröffentlichungsquelle hinzu. + - If your repository is public and {% data variables.product.prodname_pages %} is disabled for your repository, using the theme chooser will enable {% data variables.product.prodname_pages %} and configure the default branch as your publishing source. + - Wenn Dein Repository privat und {% data variables.product.prodname_pages %} für Dein Repository deaktiviert ist, musst Du {% data variables.product.prodname_pages %} durch die Konfiguration einer Veröffentlichungsquelle erst aktivieren, bevor Du den Theme Chooser verwenden kannst. + +Weitere Informationen zu Veröffentlichungsquellen findest Du unter „[Informationen zu {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites).“ + +Wenn Du in der Vergangenheit manuell ein Jekyll-Design zu Deinem Repository hinzugefügt hast, werden diese Dateien möglicherweise auch nach der Verwendung des Theme Chooser noch angewendet. Um Konflikte zu vermeiden, solltest Du alle manuell hinzugefügten Design-Ordner und -Dateien entfernen, bevor Du den Theme Chooser verwendest. Weitere Informationen findest Du unter „[Ein Design zur {% data variables.product.prodname_pages %}-Website mit Jekyll hinzufügen](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll).“ + +### Ein Design mit dem Theme Chooser hinzufügen + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Klicke unter „{% data variables.product.prodname_pages %}“ auf **Choose a theme** (Ein Design auswählen) oder **Change theme** (Design ändern). ![Schaltfläche „Choose a theme“ (Ein Design auswählen)](/assets/images/help/pages/choose-a-theme.png) +4. Klicke oben auf der Seite auf das gewünschte Design und anschließend auf **Select theme** (Design auswählen). ![Designoptionen und Schaltfläche „Select theme“ (Design auswählen)](/assets/images/help/pages/select-theme.png) +5. Möglicherweise wirst Du dazu aufgefordert, die *README.md*-Datei Deiner Website zu bearbeiten. + - Um die Datei zu einem späteren Zeitpunkt zu bearbeiten, klicke auf **Cancel** (Abbrechen). ![Link „Cancel“ (Abbrechen) beim Bearbeiten einer Datei](/assets/images/help/pages/cancel-edit.png) + - Wenn Du die Datei jetzt bearbeiten möchtest, findest Du Informationen hierzu unter „[Dateien in Deinem Repository bearbeiten](/articles/editing-files-in-your-repository/).“ + +Das ausgewählte Design wird automatisch auf Markdown-Dateien in Deinem Repository angewendet. Um Dein Design auf die HTML-Dateien in Deinem Repository anzuwenden, musst Du YAML-Frontmatter hinzufügen, um ein Layout für jede Datei festzulegen. Weitere Informationen findest Du unter „[Frontmatter](https://jekyllrb.com/docs/front-matter/)“ auf der Jekyll-Website. + +### Weiterführende Informationen + +- [Designs](https://jekyllrb.com/docs/themes/) auf der Jekyll-Website diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..7c91f47a4e --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +redirect_from: + - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published: + +- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS. +- We use a unique subdomain for the private page to ensure that other repositories in your organization cannot publish content on the same origin as the private page. This protects your private page from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain. + +You can see your site's unique subdomain in the pages tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +To use a shorter and more memorable domain for your private {% data variables.product.prodname_pages %} site, you can configure a custom domain. Weitere Informationen findest Du unter „[Konfigurieren einer benutzerdefinierten Domäne für Deine {% data variables.product.prodname_pages %}-Website](/pages/configuring-a-custom-domain-for-your-github-pages-site)." + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. Um Deine veröffentlichte Website anzuzeigen, klicke unter „{% data variables.product.prodname_pages %}" auf die URL Deiner Website. ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000..f684455175 --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,38 @@ +--- +title: Eine Veröffentlichungsquelle für Deine GitHub Pages-Website konfigurieren +intro: 'Wenn Sie die Standard-Veröffentlichungsquelle für Ihre {% data variables.product.prodname_pages %}-Website verwenden, wird Ihre Website automatisch veröffentlicht. You can also choose to publish your{% if currentVersion ver_lt "enterprise-server@3.0" %} project{% endif %} site from a different branch or folder.' +redirect_from: + - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-your-github-pages-site + - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can configure a publishing source for a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +Weitere Informationen zu Veröffentlichungsquellen findest Du unter „[Informationen zu {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites).“ + +### Eine Veröffentlichungsquelle auswählen + +Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} 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 %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source. ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +4. Optionally, use the drop-down menu to select a folder for your publishing source. ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. Klicke auf **Save** (Speichern). ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %} +3. Wählen Sie unter „{% data variables.product.prodname_pages %}“ im Dropdownmenü „**Source**“ (Quelle) eine Veröffentlichungsquelle aus. ![Dropdownmenü zum Auswählen einer Veröffentlichungsquelle](/assets/images/help/pages/publishing-source-drop-down.png) +{% endif %} + +### Fehler bei der Veröffentlichung Deiner {% data variables.product.prodname_pages %}-Website beheben + +{% 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. Weitere Informationen findest Du unter „[Jekyll-Build-Fehler für {% data variables.product.prodname_pages %}-Websites beheben](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder).“ diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000..9e8c2c83d3 --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Eine benutzerdefinierte 404-Seite für Deine GitHub Pages-Website erstellen +intro: Du kannst eine benutzerdefinierte 404-Fehler-Seite anzeigen lassen, wenn Benutzer versuchen, nicht vorhandene Seiten auf Deiner Website aufzurufen. +redirect_from: + - /articles/custom-404-pages/ + - /articles/creating-a-custom-404-page-for-your-github-pages-site + - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +{% data reusables.files.add-file %} +3. Gib im Feld für den Dateinamen `404.html` oder `404.md` ein. ![Feld für den Dateinamen](/assets/images/help/pages/404-file-name.png) +4. Wenn Du die Datei `404.md` genannt hast, füge den folgenden YAML-Frontmatter am Anfang der Datei hinzu: + ```yaml + --- + permalink: /404.html + --- + ``` +5. Füge unter dem YAML-Frontmatter, so vorhanden, den Inhalt ein, der auf Deiner 404-Seite angezeigt werden soll. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Weiterführende Informationen + +- [Front matter](http://jekyllrb.com/docs/frontmatter) (Frontmatter) in der Jekyll-Dokumentation diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000..941ca78540 --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,63 @@ +--- +title: Creating a GitHub Pages site +intro: 'Sie können eine {% data variables.product.prodname_pages %}-Website in einem neuen oder vorhandenen Repository erstellen.' +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 + - /github/working-with-github-pages/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Ein Repository für eine Website erstellen + +{% data reusables.pages.new-or-existing-repo %} + +{% 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 %} + +### Eine Website erstellen + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.decide-publishing-source %} +3. Wenn Deine ausgewählte Veröffentlichungsquelle bereits vorhanden ist, navigiere zu dieser Quelle. Wenn Deine ausgewählte Veröffentlichungsquelle nicht vorhanden ist, erstelle die Veröffentlichungsquelle. +4. Erstelle im Root der Veröffentlichungsquelle eine neue Datei mit dem Namen `index.md`, die den Inhalt enthält, der auf der Hauptseite Deiner Website angezeigt werden soll. +{% data reusables.pages.configure-publishing-source %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Nächste Schritte: + +Du kannst Deiner Website weitere Seiten hinzufügen, indem Du zusätzliche neue Dateien erstellst. Jede Datei wird auf Deiner Website im selben Verzeichnis verfügbar sein wie Deine Veröffentlichungsquelle. 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.html` verfügbar. + +Du kannst auch ein Design hinzufügen, um das Aussehen der Website anzupassen. 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 %}." + +Um Ihre Website noch weiter anzupassen, können Sie Jekyll verwenden, einen Generator für statische Websites mit integrierter Unterstützung von {% data variables.product.prodname_pages %}. Weitere Informationen finden Sie unter „[Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll)“. + +### Weiterführende Informationen + +- „[Jekyll-Build-Fehler für {% data variables.product.prodname_pages %}-Websites beheben](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)“ +- „[Branches in Ihrem Repository erstellen und löschen](/articles/creating-and-deleting-branches-within-your-repository)“ +- „[Neue Dateien erstellen](/articles/creating-new-files)“ diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/index.md b/translations/de-DE/content/pages/getting-started-with-github-pages/index.md new file mode 100644 index 0000000000..053713655c --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/index.md @@ -0,0 +1,26 @@ +--- +title: Erste Schritte mit GitHub Pages +intro: 'Sie können eine grundlegende {% data variables.product.prodname_pages %}-Website für sich selbst, für Ihre Organisation oder für Ihr Projekt einrichten.' +redirect_from: + - /categories/github-pages-basics + - /articles/additional-customizations-for-github-pages/ + - /articles/getting-started-with-github-pages + - /github/working-with-github-pages/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +{% 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 /changing-the-visibility-of-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 %} \ No newline at end of file diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000..6f6f093cbc --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,55 @@ +--- +title: GitHub Pages-Website mit HTTPS schützen +intro: 'HTTPS fügt eine Verschlüsselungsebene hinzu, die das Ausspionieren oder Manipulieren des Datenverkehrs zu Deiner Website durch Fremde verhindert. Du kannst HTTPS für Deine {% data variables.product.prodname_pages %}-Website erzwingen und so alle HTTP-Anforderungen transparent an HTTPS weiterleiten.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/securing-your-github-pages-site-with-https + - /github/working-with-github-pages/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +topics: + - Seiten +--- + +Personen mit Administratorberechtigungen für ein Repository können HTTPS für eine {% data variables.product.prodname_pages %}-Website erzwingen. + +### Informationen zu HTTPS und {% data variables.product.prodname_pages %} + +Alle {% data variables.product.prodname_pages %}-Websites, auch Websites, die korrekt mit einer benutzerdefinierten Domäne konfiguriert sind, unterstützen HTTPS und die Erzwingung von HTTPS. Weitere Informationen findest Du unter „[Informationen zu benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)“ und „[Fehlerbehebung bei benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors).“ + +{% data reusables.pages.no_sensitive_data_pages %} + +{% data reusables.pages.private_pages_are_public_warning %} + +### HTTPS für Deine {% data variables.product.prodname_pages %}-Website erzwingen + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Wählen Sie unter „{% data variables.product.prodname_pages %}“ die Option **Enforce HTTPS** (HTTPS erzwingen). ![Kontrollkästchen „Enforce HTTPS“ (HTTPS erzwingen)](/assets/images/help/pages/enforce-https-checkbox.png) + +### Probleme bei gemischten Inhalten beheben + +Wenn Sie für Ihre {% data variables.product.prodname_pages %}-Website HTTPS aktivieren, die HTML Ihrer Website aber noch Bilder, CSS oder JavaScript über HTTP referenziert, stellt Ihre Website *gemischte Inhalte* bereit. In diesem Fall ist Deine Website möglicherweise weniger sicher und das Laden dieser Objekte bereitet eventuell Probleme. + +Sollen die gemischten Inhalte Deiner Website entfernt werden, stelle zunächst alle Objekte über HTTPS bereit. Ersetze hierzu `http://` in der HTML Deiner Website durch `https://`. + +Objekte befinden sich meist in den folgenden Speicherorten: +- Wenn Deine Website Jekyll verwendet, befinden sich Deine HTML-Dateien wahrscheinlich im Ordner *_layouts*. +- CSS befindet sich im Allgemeinen im Abschnitt `` Deiner HTML-Dateien. +- JavaScript befindet sich in der Regel im Abschnitt `` oder kurz vor dem schließenden ``-Tag. +- Bilder befinden sich meist im Abschnitt ``. + +{% tip %} + +**Tipp:** Wenn Sie die Assets nicht in den Quelldateien Ihrer Website finden, suchen Sie mit dem Texteditor oder mit {% data variables.product.product_name %} in den Quelldateien nach `http`. + +{% endtip %} + +#### Beispiele für referenzierte Objekte in einer HTML-Datei + +| Objekt-Typ | HTTP | HTTPS | +|:----------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:| +| CSS | `` | `` | +| JavaScript | `` | `` | +| Bild | `Logo` | `Logo` | diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000..e481a47e5a --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Veröffentlichung einer GitHub Pages-Website zurückziehen +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' +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 + - /github/working-with-github-pages/unpublishing-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can unpublish a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +### Veröffentlichung einer Projektwebsite zurückziehen + +{% data reusables.repositories.navigate-to-repo %} +2. Wenn das Repository einen Branch `gh-pages` enthält, lösche den Branch `gh-pages`. Weitere Informationen findest Du unter „[Branches in Deinem Repository erstellen und löschen](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch).“ +3. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. Wählen Sie unter „{% data variables.product.prodname_pages %}“ im Dropdownmenü „**Source**“ (Quelle) die Option **None** (Keine) aus. ![Dropdownmenü zum Auswählen einer Veröffentlichungsquelle](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} + +### Veröffentlichung einer Benutzer- oder Organisations-Website zurückziehen + +{% data reusables.repositories.navigate-to-repo %} +2. Delete the branch that you're using as a publishing source, or delete the entire repository. Weitere Informationen findest Du unter „[Branches in Deinem Repository erstellen und löschen](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)“ und „[Repository löschen](/articles/deleting-a-repository).“ +{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/de-DE/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000..4d0d721270 --- /dev/null +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,24 @@ +--- +title: Using submodules with GitHub Pages +intro: 'Sie können Submodule in {% data variables.product.prodname_pages %} nutzen und damit andere Projekte in den Code Ihrer Website einbinden.' +redirect_from: + - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-github-pages + - /github/working-with-github-pages/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Seiten +--- + +Wenn das Repository für Ihre {% data variables.product.prodname_pages %}-Website Submodule enthält, wird deren Inhalt automatisch beim Erstellen der Website abgerufen. + +Sie können nur Submodule verwenden, die auf öffentliche Repositorys verweisen, da der {% data variables.product.prodname_pages %}-Server nicht auf private Repositorys zugreifen kann. + +Verwende die schreibgeschützte `https://`-URL für Submodule, einschließlich verschachtelter Submodule. Du kannst diese Änderung in Deiner _.gitmodules_-Datei vornehmen. + +### Weiterführende Informationen + +- „[Git-Tools – Submodule](https://git-scm.com/book/en/Git-Tools-Submodules)“ im _Pro Git_-Buch +- „[Jekyll-Build-Fehler für {% data variables.product.prodname_pages %}-Websites beheben](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)“ diff --git a/translations/de-DE/content/pages/index.md b/translations/de-DE/content/pages/index.md new file mode 100644 index 0000000000..a535cebe05 --- /dev/null +++ b/translations/de-DE/content/pages/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages Documentation +shortTitle: GitHub Pages +intro: 'Du kannst eine Website direkt aus einem {% data variables.product.product_name %}-Repository erstellen.' +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 + - /github/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +{% link_with_intro /getting-started-with-github-pages %} +{% link_with_intro /setting-up-a-github-pages-site-with-jekyll %} +{% link_with_intro /configuring-a-custom-domain-for-your-github-pages-site %} \ No newline at end of file diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000..b3faf04a38 --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -0,0 +1,131 @@ +--- +title: Informationen zu GitHub Pages und Jekyll +intro: 'Jekyll ist ein Generator für statische Websites mit integrierter Unterstützung von {% 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 + - /github/working-with-github-pages/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +### Informationen zu Jekyll + +Jekyll ist ein Generator für statische Websites mit integrierter Unterstützung von {% data variables.product.prodname_pages %} und einem vereinfachten Build-Prozess. Jekyll erstellt aus Markdown- und HTML-Dateien eine statische Website und nutzt dabei die von Dir ausgewählten Layouts. Jekyll unterstützt Markdown und Liquid, eine Vorlagensprache, die dynamische Inhalte auf Deiner Website lädt. Weitere Informationen findest Du auf der Website zu [Jekyll](https://jekyllrb.com/). + +Jekyll wird von Windows nicht offiziell unterstützt. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation. + +Wir empfehlen, Jekyll mit {% data variables.product.prodname_pages %} zu verwenden. Wenn Du möchtest, kannst Du aber auch andere Generatoren für statische Websites verwenden oder Deinen eigenen Build-Prozess lokal oder auf einem anderen Server anpassen. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators).“ + +### Jekyll in der {% data variables.product.prodname_pages %}-Website konfigurieren + +Du kannst die meisten Jekyll-Einstellungen konfigurieren, beispielsweise das Design und die Plug-ins Deiner Website, indem Du die Datei *_config.yml* bearbeitest. Weitere Informationen findest Du unter „[Konfiguration](https://jekyllrb.com/docs/configuration/)“ in der Jekyll-Dokumentation. + +Einige Konfigurationseinstellungen können für {% data variables.product.prodname_pages %}-Websites nicht geändert werden. + +```yaml +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 +``` + +Standardmäßig erstellt Jekyll keine Dateien und Ordner, auf die Folgendes zutrifft: +- sie befinden sich in einem Ordner mit dem Namen `/node_modules` oder `/vendor` +- start with `_`, `.`, or `#` +- sie enden mit `~` +- sie werden von der `exclude`-Einstellung in der Konfigurationsdatei ausgeschlossen + +Wenn Du möchtest, dass Jekyll solche Dateien verarbeitet, kannst Du dies mit der `includes`-Einstellung in der Konfigurationsdatei festlegen. + +### Frontmatter + +{% data reusables.pages.about-front-matter %} + +Du kannst `site.github` zu einem Beitrag oder einer Seite hinzufügen, um Repository-Referenz-Metadaten zu Deiner Website hinzuzufügen. Weitere Informationen findest Du unter „[`site.github` verwenden](https://jekyll.github.io/github-metadata/site.github/)“ in der Jekyll-Metadaten-Dokumentation. + +### Designs + +{% data reusables.pages.add-jekyll-theme %} Weitere Informationen findest Du unter „[Themes](https://jekyllrb.com/docs/themes/)“ (Designs) in der Jekyll-Dokumentation. + +{% if currentVersion == "free-pro-team@latest" %} +Sie können zu Ihrer Website auf {% data variables.product.prodname_dotcom %} ein unterstütztes Design hinzufügen. Weitere Informationen findest Du unter „[Unterstützte Designs](https://pages.github.com/themes/)“ auf der {% data variables.product.prodname_pages %}-Website und unter „[Ein Design mit dem Theme-Chooser zur {% data variables.product.prodname_pages %}-Website hinzufügen](/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)." + +Du kannst alle Standardeinstellungen Deines Designs überschreiben, indem Du die Dateien des Designs bearbeitest. Weitere Informationen findest Du in der Dokumentation zu Deinem Design und unter „[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)“ (Standardeinstellungen Deines Designs überschreiben) in der Jekyll-Dokumentation. + +### Plug-ins + +Du kannst Jekyll-Plug-ins herunterladen oder erstellen, um die Funktionalität von Jekyll für Deine Website zu erweitern. Mit dem Plugin [jemoji](https://github.com/jekyll/jemoji) können Sie beispielsweise {% data variables.product.prodname_dotcom %}-Emojis auf allen Seiten Ihrer Website genauso verwenden wie auf {% data variables.product.prodname_dotcom %}. Weitere Informationen findest Du unter „[Plugins](https://jekyllrb.com/docs/plugins/)“ (Plug-ins) in der Jekyll-Dokumentation. + +{% data variables.product.prodname_pages %} verwendet Plug-ins, die standardmäßig aktiviert sind und nicht deaktiviert werden können: +- [`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) + +Du kannst zusätzliche Plug-ins aktivieren, indem Du die Gem des Plug-ins zur `plugins`-Einstellung in der Datei *_config.yml* hinzufügst. Weitere Informationen findest Du unter „[Konfiguration](https://jekyllrb.com/docs/configuration/)“ in der Jekyll-Dokumentation. + +Eine Liste der unterstützten Plug-ins findest Du unter „[Abhängigkeitsversionen](https://pages.github.com/versions/) auf der {% data variables.product.prodname_pages %}-Website. Informationen zur Verwendung eines bestimmten Plug-ins findest Du in der dazugehörigen Dokumentation. + +{% tip %} + +**Tipp:** Um sicherzustellen, dass Sie die aktuellen Versionen aller Plug-ins verwenden, sollten Sie die {% data variables.product.prodname_pages %}-Gem regelmäßig aktualisieren. Weitere Informationen findest Du unter „[GitHub Pages-Website lokal mit Jekyll testen](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)“ und „[Abhängigkeitsversionen](https://pages.github.com/versions/)“ auf der {% data variables.product.prodname_pages %}-Website. + +{% endtip %} + +{% data variables.product.prodname_pages %} kann keine Websites mit nicht unterstützten Plug-ins erstellen. Wenn Sie nicht unterstützte Plug-ins verwenden möchten, müssen Sie Ihre Website lokal erstellen und die statischen Dateien der Website anschließend zu {% data variables.product.product_name %} pushen. + +### Syntaxmarkierung + +Damit Ihre Website leichter lesbar ist, werden Code-Ausschnitte auf {% data variables.product.prodname_pages %}-Websites ebenso markiert wie auf {% data variables.product.product_name %}. Weitere Informationen zur Syntaxmarkierung auf {% data variables.product.product_name %} findest Du unter „[Codeblöcke erstellen und markieren](/articles/creating-and-highlighting-code-blocks).“ + +Standardmäßig werden Codeblöcke auf Deiner Website von Jekyll markiert. Jekyll verwendet den Markierer [Rouge](https://github.com/jneen/rouge), der mit [Pygments](http://pygments.org/) kompatibel ist. Wenn Du in Deiner *_config.yml*-Datei Pygments spezifizierst, wird stattdessen Rouge verwendet. Jekyll kann keinen anderen Syntaxmarkierer verwenden. Wenn Du einen anderen Syntaxmarkierer in der *_config.yml*-Datei angibst, wird eine Build-Warnung für die Website angezeigt. Weitere Informationen findest Du unter „[Informationen zu Jekyll-Build-Fehler für {% data variables.product.prodname_pages %}-Websites](/articles/about-jekyll-build-errors-for-github-pages-sites).“ + +Wenn Du einen anderen Markierer verwenden möchtest, z. B. `highlight.js`, musst Du die Jekyll-Syntaxmarkierung deaktivieren, indem Du die *_config.yml*-Datei Deines Projekts änderst. + +```yaml +kramdown: + syntax_highlighter_opts: + disable : true +``` + +Wenn Ihr Design kein CSS für die Syntaxmarkierung enthält, können Sie das CSS von {% data variables.product.prodname_dotcom %} zur Syntaxmarkierung erzeugen und zur Datei `style.css` des Projekts hinzufügen. + +```shell +$ rougify style github > style.css +``` + +### Website lokal erstellen + +{% data reusables.pages.test-locally %} diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..03a0f8dbbb --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,62 @@ +--- +title: Informationen zu Jekyll-Build-Fehler für GitHub Pages-Websites +intro: 'Wenn beim Erstellen Ihrer {% data variables.product.prodname_pages %}-Website (lokal oder auf {% data variables.product.product_name %}) mit Jekyll ein Fehler auftritt, erhalten Sie eine Fehlermeldung mit weiteren Informationen.' +redirect_from: + - /articles/viewing-jekyll-build-error-messages/ + - /articles/generic-jekyll-build-failures/ + - /articles/about-jekyll-build-errors-for-github-pages-sites + - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +### Informationen zu Jekyll-Build-Fehlern + +Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} +- Der Benutzer, der die Änderungen gepusht hat, hat seine E-Mail-Adresse nicht verifiziert. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/articles/verifying-your-email-address)“.{% endif %} +- Du führst den Push mit einem Deployment-Schlüssel durch. Wenn Du Übertragungen zum Repository Deiner Website automatisieren möchtest, kannst du stattdessen einen Maschinenbenutzer einrichten. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)." +- Du verwendest einen Dienst für die fortlaufende Integration, der nicht zum Erstellen Deiner Veröffentlichungsquelle konfiguriert ist. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. Weitere Informationen findest Du unter „[Build anpassen](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)“ auf Travis CI oder in der Dokumentation Deines Dienstes für die fortlaufende Integration. + +{% note %} + +**Hinweis:** Es kann bis zu 20 Minuten dauern, bis die Änderungen auf Ihrer Website veröffentlicht werden, nachdem Sie die Änderungen zu {% data variables.product.product_name %} gepusht haben. + +{% endnote %} + +Wenn beim Versuch von Jekyll, Deine Website zu erstellen, ein Fehler auftritt, wird eine Build-Fehlermeldung angezeigt. Es gibt zwei Hauptarten an Jekyll-Build-Fehlermeldungen. +- Eine „Page build warning“ (Seiten-Build-Warnung) bedeutet, dass Deine Website erfolgreich erstellt wurde, Du aber Änderungen vornehmen musst, um künftige Probleme zu verhindern. +- Eine Fehlermeldung „Page build failed“ (Seiten-Build fehlgeschlagen) bedeutet, dass Dein Build nicht abgeschlossen werden konnte. Wenn Jekyll einen Grund dafür erkennt, enthält die Fehlermeldung eine Beschreibung der Ursache. + +Weitere Informationen zur Behebung von Build-Fehlern findest Du unter „[Behebung von Jekyll-Build-Fehlern bei {% data variables.product.prodname_pages %}-Websites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites).“ + +### Jekyll-Build-Fehlermeldungen anzeigen + +Wir empfehlen Ihnen, Ihre Website lokal zu testen. Dadurch sehen Sie Build-Fehlermeldungen in der Befehlszeile und können Build-Fehler beheben, bevor Sie die Änderungen zu {% data variables.product.product_name %} pushen. Weitere Informationen findest Du unter „[Deine {% data variables.product.prodname_pages %}-Website lokal mit Jekyll testen](/articles/testing-your-github-pages-site-locally-with-jekyll).“ + +Wenn Sie einen Pull Request erstellen, um Ihre Veröffentlichungsquelle auf {% data variables.product.product_name %} zu aktualisieren, können Sie auf der Registerkarte **Checks** (Prüfungen) des Pull Requests die Build-Fehlermeldungen einsehen. Weitere Informationen findest Du unter „[Informationen zu Statuschecks](/articles/about-status-checks).“ + +Wenn Sie Änderungen zu Ihrer Veröffentlichungsquelle auf {% data variables.product.product_name %} pushen, versucht {% data variables.product.prodname_pages %}, Ihre Website zu erstellen. Wenn der Build fehlschlägt, wird eine E-Mail an Deine primäre E-Mail-Adresse gesendet. Du erhältst auch bei Build-Warnungen E-Mail-Benachrichtigungen. {% data reusables.pages.build-failure-email-server %} + +Build-Fehler (aber keine Build-Warnungen) für Ihre Website können Sie auf {% data variables.product.product_name %} auf der Registerkarte **Settings** (Einstellungen) des Repositorys Ihrer Website sehen. + +Du kannst einen Drittanbieterdienst, beispielsweise [Travis CI](https://travis-ci.org/), so konfigurieren, dass nach jedem Commit Fehlermeldungen angezeigt werden. + +1. Wenn Du dies noch nicht getan hast, füge eine Datei namens _Gemfile_ in das Root-Verzeichnis Deiner Veröffentlichungsquelle ein. Die Gemfile-Datei sollte den folgenden Inhalt aufweisen: + ```ruby + source `https://rubygems.org` + gem `github-pages` + ``` + +2. Konfiguriere das Repository Deiner Website für die gewünschte Test-Dienstleistung. Wenn Du beispielsweise [Travis CI](https://travis-ci.org/) verwenden möchtest, füge eine Datei namens _.travis.yml_ in das Root-Verzeichnis Deiner Veröffentlichungsquelle ein, und zwar mit folgendem Inhalt: + ```yaml + language: ruby + rvm: + - 2.3 + script: "bundle exec jekyll build" + ``` +3. Du musst Dein Repository allenfalls mit dem Drittanbieter-Testdienst aktivieren. Weitere Informationen findest Du in der Dokumentation Deines Test-Dienstleisters. diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..a755bed07e --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,71 @@ +--- +title: Ein Design zur GitHub Pages-Website mit Jekyll hinzufügen +intro: Du kannst Deine Jekyll-Website personalisieren, indem Du ein Design hinzufügst und anpasst. +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +Personen mit Schreibberechtigungen für ein Repository können mit Jekyll ein Design zu einer {% data variables.product.prodname_pages %}-Website hinzufügen. + +{% data reusables.pages.test-locally %} + +### Ein Design hinzufügen + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +2. Navigiere zur Datei *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Füge in der Datei eine neue Zeile mit den Namen des Designs hinzu. + - 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. Eine Liste der unterstützten Designs findest Du unter „[Unterstützte Designs](https://pages.github.com/themes/)“ auf der {% data variables.product.prodname_pages %}-Website. ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png) + - Um ein anderes Jekyll-Design zu verwenden, das auf {% data variables.product.prodname_dotcom %} gehostet wird, gib `remote_theme: THEME-NAME` ein und ersetze dabei „THEME-NAME“ durch den Namen des Designs, der in der README-Datei des Repositorys des Designs aufgeführt ist. ![Unsupported theme in config file](/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 %} + +### Das CSS Deines Designs anpassen + +{% 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. Erstelle eine neue Datei mit den Namen _/assets/css/style.scss_. +2. Füge oben in der Datei den folgenden Inhalt hinzu: + ```scss + --- + --- + + @import "{{ site.theme }}"; + ``` +3. Füge direkt nach der Zeile `@import` das gewünschte benutzerdefinierte CSS oder Sass (einschließlich Importe) hinzu. + +### Das HTML-Layout Deines Designs anpassen + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +1. Navigieren Sie auf {% data variables.product.prodname_dotcom %} zum Quell-Repository Ihres Designs. Das Quell-Repository für Minima ist beispielsweise https://github.com/jekyll/minima. +2. Navigiere im Ordner *_layouts* (Layouts) zur Datei _default.html_ Deines Designs. +3. Kopiere den Inhalt der Datei. +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +6. Erstelle eine Datei mit dem Namen *_layouts/default.html*. +7. Füge den zuvor kopierten Inhalt des Standardlayouts ein. +8. Passe das Layout nach Deinen Vorstellungen an. + +### Weiterführende Informationen + +- „[Neue Dateien erstellen](/articles/creating-new-files)“ diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..b1c4c45a4b --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,72 @@ +--- +title: Inhalte zur GitHub Pages-Website mit Jekyll hinzufügen +intro: 'Sie können zu Ihrer Jekyll-Website auf {% data variables.product.prodname_pages %} eine neue Seite oder einen neuen Beitrag hinzufügen.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/adding-content-to-your-github-pages-site-using-jekyll + - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +Personen mit Schreibberechtigungen für ein Repository können mit Jekyll Inhalte zu einer {% data variables.product.prodname_pages %}-Website hinzufügen. + +### Informationen zu Inhalten von Jekyll-Websites + +Bevor Sie Inhalte zu einer Jekyll-Website auf {% data variables.product.prodname_pages %} hinzufügen können, müssen Sie eine Jekyll-Website erstellen. Weitere Informationen findest Du unter „[Eine {% data variables.product.prodname_pages %}-Website mit Jekyll erstellen](/articles/creating-a-github-pages-site-with-jekyll).“ + +Die hauptsächlichen Arten von Inhalten für Jekyll-Websites sind Seiten und Beiträge. Eine Seite wird für eigenständige Inhalte genutzt, die nicht mit einem bestimmten Datum verknüpft sind, z. B. eine Seite mit Informationen zu Deiner Person oder Organisation. Die standardmäßige Jekyll-Website enthält eine Datei mit dem Namen `about.md`, die als Seite Deiner Website unter `YOUR-SITE-URL/about` angezeigt wird. Du kannst den Inhalt dieser Datei bearbeiten, um Deine Informationsseite zu personalisieren. Die Informationsseite kannst Du außerdem als Vorlage für neue Seiten verwenden. Weitere Informationen findest Du unter „[Pages](https://jekyllrb.com/docs/pages/)“ (Seiten) in der Jekyll-Dokumentation. + +Bei einem Beitrag handelt es sich um einen Blog-Beitrag. Die standardmäßige Jekyll-Website enthält ein Verzeichnis mit dem Namen `_posts`, das eine Standard-Beitragsdatei enthält. Du kannst den Inhalt dieses Beitrags bearbeiten und den Standardbeitrag als Vorlage für neue Beiträge verwenden. Weitere Informationen findest Du unter „[Posts](https://jekyllrb.com/docs/posts/)“ (Beiträge) in der Jekyll-Dokumentation. + +Dein Design umfasst standardmäßige Layouts, Includes und Stylesheets, die automatisch auf neue Seiten und Beiträge auf Deiner Website angewendet werden. Du kannst diese Standardeinstellungen aber überschreiben. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll#themes).“ + +{% data reusables.pages.about-front-matter %} + +{% data reusables.pages.test-locally %} + +### Eine neue Seite zu Deiner Website hinzufügen + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. Erstelle im Root-Verzeichnis Deiner Veröffentlichungsquelle eine neue Datei für Deine Seite mit dem Namen _PAGE-NAME.md_, und ersetze dabei _PAGE-NAME_ durch einen aussagekräftigen Dateinamen für die Seite. +4. Füge den folgenden YAML-Frontmatter oben in der Datei hinzu, und ersetze dabei _PAGE TITLE_ durch den Titel der Seite und _URL-PATH_ durch den gewünschten Pfad für die URL der Seite. Wenn beispielsweise die Basis-URL Deiner Website `https://octocat.github.io` lautet und der URL-Pfad (_URL-PATH_) `/about/contact/` ist, findet sich Deine Seite unter `https://octocat.github.io/about/contact`. + ```shell + layout: page + title: "PAGE TITLE" + permalink: /URL-PATH/ + ``` +5. Füge unterhalb des Frontmatter den Inhalt für Deine Seite hinzu. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Einen neuen Beitrag zu Deiner Website hinzufügen + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. Navigiere zum Verzeichnis `_posts`. +4. Erstelle eine neue Datei mit dem Namen _YYYY-MM-DD-NAME-OF-POST.md_, wobei Du _YYYY-MM-DD_ durch das Datum des Beitrags und _NAME-OF-POST_ durch den Namen des Beitrags ersetzt. +4. Füge den folgenden YAML-Frontmatter oben in der Datei hinzu, und ersetze dabei _POST TITLE_ durch den Titel des Beitrags, _YYYY-MM-DD hh:mm:ss -0000_ durch das Datum und die Uhrzeit für den Beitrag und _CATEGORY-1_ und _CATEGORY-2_ durch so viele Kategorien, wie Dein Beitrag aufweisen soll. + ```shell + layout: post + title: "POST TITLE" + date: YYYY-MM-DD hh:mm:ss -0000 + categories: CATEGORY-1 CATEGORY-2 + ``` +5. Füge unterhalb des Frontmatters den Inhalt für Deinen Beitrag hinzu. +{% 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`. + +### 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/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000..b6fbce8aba --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,116 @@ +--- +title: GitHub Pages-Website mit Jekyll erstellen +intro: 'Sie können mit Jekyll eine {% data variables.product.prodname_pages %}-Website in einem neuen oder vorhandenen Repository erstellen.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/creating-a-github-pages-site-with-jekyll + - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll +permissions: 'Personen mit Administratorberechtigungen für ein Repository können mit Jekyll eine {% data variables.product.prodname_pages %}-Website erstellen.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Vorrausetzungen + +Bevor Sie mit Jekyll eine {% data variables.product.prodname_pages %}-Website erstellen können, müssen Sie Jekyll und Git installieren. Weitere Informationen findest Du unter „[Installation](https://jekyllrb.com/docs/installation/)“ in der Jekyll-Dokumentation und unter „[Git einrichten](/articles/set-up-git).“ + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Ein Repository für eine Website erstellen + +{% data reusables.pages.new-or-existing-repo %} + +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} + +### Eine Website erstellen + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Wenn Du noch keine lokale Kopie Deines Repositorys besitzt, navigiere zu dem Speicherort, an dem Du die Quelldateien Deiner Website speichern möchtest, und ersetze dabei _PARENT-FOLDER_ durch den Ordner, der den Ordner für Dein Repository enthalten soll. + ```shell + $ cd PARENT-FOLDER + ``` +3. Wenn Du dies noch nicht getan hast, initialisiere ein lokales Git-Repository, und ersetzen dabei _REPOSITORY-NAME_ durch den Namen Deines Repositorys. + ```shell + $ git init REPOSITORY-NAME + > Initialized empty Git repository in /Users/octocat/my-site/.git/ + # Erstellt einen neuen Ordner auf Deinem Computer, der als Git-Repository initialisiert wird + ``` + 4. Wechsle in das Verzeichnis des Repositorys. + ```shell + $ cd REPOSITORY-NAME + # Ändert das Arbeitsverzeichnis + ``` +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. + ```shell + $ mkdir docs + # Erstellt einen neuen Ordner mit dem Namen docs + $ cd docs + ``` + Wenn Sie Ihre Website aus dem `gh-pages`-Branch veröffentlichen möchten, erstellen Sie den `gh-pages`-Branch und checken ihn aus. + ```shell + $ git checkout --orphan gh-pages + # Erstellt einen neuen Branch, ohne Verlauf und Inhalte, mit dem namen gh-pages und wechselt zum gh-pages-Branch + ``` +7. To create a new Jekyll site, use the `jekyll new` command: + ```shell + $ jekyll new . + # Erstellt eine Jekyll-Website im aktuellen Verzeichnis + ``` +8. Open the Gemfile that Jekyll created. +1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line. +1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to: + + ```shell + gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins + ``` + + Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)." + + The correct version Jekyll will be installed as a dependency of the `github-pages` gem. +10. Speichere und schließe das Gemfile. +11. From the command line, run `bundle update`. +11. Teste Deine Website optional lokal. Weitere Informationen findest Du unter „[Deine {% data variables.product.prodname_pages %}-Website lokal mit Jekyll testen](/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. +```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. Übertrage das Repository zu {% data variables.product.product_name %}, und ersetze dabei _BRANCH_ durch den Namen des Branches, auf dem Du gerade arbeitest. + ```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.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Nächste Schritte: + +Informationen dazu, wie Sie eine neue Seite oder einen neuen Beitrag zu Ihrer Website hinzufügen, finden Sie unter „[Inhalte zur {% data variables.product.prodname_pages %}-Website mit Jekyll hinzufügen](/articles/adding-content-to-your-github-pages-site-using-jekyll)“. + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md new file mode 100644 index 0000000000..97fa809b6e --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages-Website mit Jekyll einrichten +intro: 'Mit Jekyll, dem beliebten Generator für statische Websites, können Sie Ihre {% data variables.product.prodname_pages %}-Website weiter anpassen.' +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 + - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..c928c8f50a --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,36 @@ +--- +title: Markdown-Prozessor für Deine GitHub Pages-Website mit Jekyll festlegen +intro: 'Mit einem Markdown-Prozessor legst Du fest, wie Markdown auf Deiner {% data variables.product.prodname_pages %}-Website dargestellt wird.' +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 + - /github/working-with-github-pages/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: '*' +topics: + - Seiten +--- + +Personen mit Schreibberechtigungen für ein Repository können den Markdown-Prozessor für eine {% data variables.product.prodname_pages %}-Website festlegen. + +{% 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 %}. Weitere Informationen findest Du unter „[Informationen zum Schreiben und Formatieren bei {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github).“ + +{% data variables.product.prodname_dotcom %} Flavored Markdown eignet sich für beide Prozessoren, wobei jedoch nur der CommonMark-Prozessor die Ergebnisse exakt wie in {% data variables.product.product_name %} darstellt. + +{% data reusables.pages.navigate-site-repo %} +2. Suche in Deinem Repository die Datei *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Suche die Zeile, die mit `markdown:` beginnt, und ändere deren Wert in `kramdown` oder `GFM`. ![Markdown-Einstellung in 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 %} + +### Weiterführende Informationen + +- [Dokumentation zu kramdown](https://kramdown.gettalong.org/documentation.html) +- [{% data variables.product.prodname_dotcom %} Flavored Markdown – Spezifikation](https://github.github.com/gfm/) diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000..ff97f7f418 --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,62 @@ +--- +title: GitHub Pages-Website lokal mit Jekyll testen +intro: 'Sie können Ihre {% data variables.product.prodname_pages %}-Website lokal erstellen und damit eine Vorschau der Änderungen an Ihrer Website zu prüfen und diese Änderungen testen.' +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 + - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +Personen mit Schreibberechtigungen für ein Repository können eine {% data variables.product.prodname_pages %}-Website lokal testen. + +### Vorrausetzungen + +Bevor Du mit Jekyll eine Website testen kannst, müssen folgende Voraussetzungen erfüllt sein: + - Installiere [Jekyll](https://jekyllrb.com/docs/installation/). + - Erstelle eine Jekyll-Website. Weitere Informationen findest Du unter „[Eine {% data variables.product.prodname_pages %}-Website mit Jekyll erstellen](/articles/creating-a-github-pages-site-with-jekyll).“ + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Website lokal erstellen + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.pages.navigate-publishing-source %} +3. Run `bundle install`. +3. Führe Dein Jekyll-Website lokal aus. + ```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. Öffne eine Vorschau der Website im Webbrowser. Navigiere hierzu zu `http://localhost:4000`. + +### Das {% data variables.product.prodname_pages %}-Gem aktualisieren + +Jekyll ist ein aktives Open-Source-Projekt, das regelmäßig aktualisiert wird. Wenn das `github-pages`-Gem auf dem Computer älter ist als das `github-pages`-Gem auf dem {% data variables.product.prodname_pages %}-Server, wird die lokal erstellte Website unter Umständen anders dargestellt als bei der tatsächlichen Veröffentlichung auf {% data variables.product.product_name %}. Damit dieser Fall nicht eintritt, aktualisiere das `github-pages`-Gem auf dem Computer in regelmäßigen Abständen. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Aktualisiere das `github-pages`-Gem. + - Wenn Bundler installiert ist, führe `bundle update github-pages` aus. + - Wenn Du Bundler nicht installiert hast, führe `gem update github-pages` aus. + +### Weiterführende Informationen + +- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in der Jekyll-Dokumentation diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..c88ce92657 --- /dev/null +++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,191 @@ +--- +title: Fehlerbehebung bei Jekyll-Build-Fehlern für GitHub Pages-Websites +intro: 'Mithilfe der Jekyll-Build-Fehlermeldungen können Sie Probleme auf Ihrer {% data variables.product.prodname_pages %}-Website beheben.' +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 + - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Seiten +--- + +### Fehlerbehebung bei Build-Fehlern + +Wenn beim Erstellen Ihrer {% data variables.product.prodname_pages %}-Website (lokal oder auf {% data variables.product.product_name %}) mit Jekyll ein Fehler auftritt, können Sie die Fehlerbehebung mithilfe der Fehlermeldungen durchführen. Weitere Informationen zu Fehlermeldungen und zum Abrufen dieser Meldungen findest Du unter „[Behebung von Jekyll-Build-Fehlern bei {% data variables.product.prodname_pages %}-Websites](/articles/about-jekyll-build-errors-for-github-pages-sites).“ + +Wenn Du eine generische Fehlermeldung erhalten hast, suche nach häufigen Fehlern. +- Du verwendest nicht unterstützte Plug-Ins. 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" %} +- Dein Repository hat die Größenbeschränkung für Repositorys überschritten. Weitere Informationen findest Du unter „[Wie lautet mein Disk-Kontingent?](/articles/what-is-my-disk-quota)“.{% endif %} +- Du hast die `source`-Einstellung in der Datei *_config.yml* geändert. {% data variables.product.prodname_pages %} überschreibt diese Einstellung beim Build-Prozess. +- Ein Dateiname in Deiner Veröffentlichungsquelle enthält einen Doppelpunkt (`:`). Dies wird nicht unterstützt. + +Wenn Du eine spezifische Fehlermeldung erhalten hast, lies die nachfolgenden Informationen zur Fehlerbehebung für die jeweilige Fehlermeldung. + +Wenn Sie einen Fehler behoben haben, übertragen Sie die Änderungen mit einem Push-Vorgang an die Veröffentlichungsquelle der Website, sodass ein neuer Build auf {% data variables.product.product_name %} ausgelöst wird. + +### Fehler bei der Dateikonfiguration + +Dieser Fehler bedeutet, dass der Build Deiner Website fehlgeschlagen ist, da die Datei *_config.yml* Syntaxfehler enthält. + +Zur Fehlerbehebung prüfe, ob die Datei *_config.yml* diesen Regeln entspricht: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +### Datum besitzt ungültiges Datum/Uhrzeit + +Dieser Fehler bedeutet, dass eine Seite der Website einen ungültigen Wert für Datum/Uhrzeit enthält. + +Zur Fehlerbehebung prüfe die in der Fehlermeldung genannte Datei und deren Layouts auf Aufrufe datumsbezogener Liquid-Filter. Prüfe, ob alle Variablen, die an datumsabhängige Liquid-Filter übergeben werden, Werte enthalten und nicht `nil` oder `""` übergeben. Weitere Informationen findest Du unter „[Liquid filters](https://help.shopify.com/en/themes/liquid/filters)“ (Liquid-Filter) in der Liquid-Dokumentation. + +### Datei ist im Verzeichnis „includes“ nicht vorhanden + +Dieser Fehler bedeutet, dass Dein Code auf eine Datei verweist, die sich nicht im Verzeichnis *_includes* befindet. + +{% data reusables.pages.search-for-includes %} Wenn sich referenzierte Dateien nicht im Verzeichnis *_includes* befinden, kopiere oder verschiebe die betreffenden Dateien in das Verzeichnis *_includes*. + +### Datei ist ein Symlink + +Dieser Fehler bedeutet, dass der Code auf eine per Symlink verknüpfte Datei verweist, die sich nicht in der Veröffentlichungsquelle für Deine Website befindet. + +{% data reusables.pages.search-for-includes %} Wenn per Symlink verlinkte Dateien referenziert werden, kopieren oder verschieben Sie die betreffenden Dateien in das Verzeichnis *_includes*. + +### Datei ist nicht ordnungsgemäß UTF-8-codiert + +Dieser Fehler bedeutet, dass Du nicht lateinische Buchstaben wie `日本語` verwendet hast, ohne dem Computer mitzuteilen, dass er diese Symbole erwarten soll. + +Zur Fehlerbehebung erzwinge die UTF-8-Codierung. Trage hierzu die folgende Zeile in die Datei *_config.yml* ein: +```yaml +encoding: UTF-8 +``` + +### Textmarkersprache ungültig + +Dieser Fehler bedeutet, dass Du nicht die Syntaxmarkierer [Rouge](https://github.com/jneen/rouge) oder [Pygments](http://pygments.org/) in der Konfigurationsdatei angegeben hast, sondern einen anderen Markierer. + +Zur Fehlerbehebung aktualisiere die Datei *_config.yml*, und gib [Rouge](https://github.com/jneen/rouge) oder [Pygments](http://pygments.org/) an. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.product_name %} und Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting).“ + +### Ungültiges Beitragsdatum + +Dieser Fehler bedeutet, dass ein Beitrag auf Deiner Website ein ungültiges Datum im Dateinamen oder in der YAML-Frontmatter enthält. + +Zur Fehlerbehebung formatiere alle Datumsangaben als YYYY-MM-DD HH:MM:SS für UTC, und prüfe, ob gültige Kalenderdaten angegeben sind. Soll eine Zeitzone außerhalb der UTC angegeben werden, verwende das Format YYYY-MM-DD HH:MM:SS +/-TTTT, beispielsweise `2014-04-18 11:30:00 +0800`. + +Wenn Du ein Datumsformat in der Datei *_config.yml* festlegst, achte auf das richtige Format. + +### Sass oder SCSS ungültig + +Dieser Fehler bedeutet, dass Dein Repository eine Sass- oder SCSS-Datei mit ungültigem Inhalt enthält. + +Zur Fehlerbehebung prüfe die in der Fehlermeldung genannte Zeilennummer auf ungültige Sass oder SCSS. Damit solche Fehler in Zukunft vermieden werden, installiere einen Sass- oder SCSS-Linter für Deinen meistgenutzten Texteditor. + +### Ungültiges Submodul + +Dieser Fehler bedeutet, dass Dein Repository ein nicht ordnungsgemäß initialisiertes Submodul enthält. + +{% data reusables.pages.remove-submodule %} + +Soll das Submodul dennoch verwendet werden, referenziere das Submodul mit `https://` (nicht mit `http://`), und stelle sicher, dass sich das Submodul in einem öffentlichen Repository befindet. + +### Ungültige YAML in der Datendatei + +Dieser Fehler bedeutet, dass mindestens eine Datei im Ordner *_data* ungültige YAML enthält. + +Zur Fehlerbehebung prüfe, ob die YAML-Dateien im Ordner *_data* diesen Regeln entsprechen: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +Weitere Informationen zu Jekyll-Datendateien findest Du unter „[Data Files](https://jekyllrb.com/docs/datafiles/)“ (Datendateien) in der Jekyll-Dokumentation. + +### Markdown-Fehler + +Dieser Fehler bedeutet, dass Dein Repository Markdown-Fehler enthält. + +Zur Fehlerbehebung verwende einen unterstützten Markdown-Prozessor. Weitere Informationen findest Du unter „[Markdown-Prozessor für Deine {% data variables.product.prodname_pages %}-Website mit Jekyll festlegen](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll).“ + +Prüfe außerdem, ob die in der Fehlermeldung genannte Datei eine gültige Markdown-Syntax umfasst. Weitere Informationen findest Du unter „[Markdown: Syntax](https://daringfireball.net/projects/markdown/syntax)“ bei Daring Fireball. + +### Dokumentordner fehlt + +This error means that you have chosen the `docs` folder on a branch as your publishing source, but there is no `docs` folder in the root of your repository on that branch. + +To troubleshoot, if your `docs` folder was accidentally moved, try moving the `docs` folder back to the root of your repository on the branch you chose for your publishing source. Wenn der Ordner `docs` versehentlich gelöscht wurde, kannst Du wie folgt vorgehen: +- Mache den Löschvorgang mit Git rückgängig. Weitere Informationen findest Du unter „[git-revert](https://git-scm.com/docs/git-revert.html) in der Git-Dokumentation. +- Create a new `docs` folder in the root of your repository on the branch you chose for your publishing source and add your site's source files to the folder. Weitere Informationen finden Sie unter „[Neue Dateien erstellen](/articles/creating-new-files)“. +- Ändere die Veröffentlichungsquelle. Weitere Informationen findest Du unter „[Eine Veröffentlichungsquelle für {% data variables.product.prodname_pages %} konfigurieren](/articles/configuring-a-publishing-source-for-github-pages).“ + +### Submodul fehlt + +Dieser Fehler bedeutet, dass Dein Repository ein nicht vorhandenes oder ein nicht ordnungsgemäß initialisiertes Submodul enthält. + +{% data reusables.pages.remove-submodule %} + +Soll ein Submodul verwendet werden, initialisiere das Submodul. Weitere Informationen findest Du unter „[Git-Tools – Submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules)“ im _Pro Git_-Buch. + +### Relative Permalinks konfiguriert + +Dieser Fehler bedeutet, dass Sie relative Permalinks in der Datei *_config.yml* nutzen, die nicht von {% data variables.product.prodname_pages %} unterstützt werden. + +Permalinks sind permanente URLs, die auf einen bestimmten Beitrag oder eine bestimmte Seite Deiner Website verweisen. Absolute Permalinks beginnen mit dem Root der Website, relative Permalinks dagegen mit dem Ordner, in dem sich die referenzierte Seite befindet. {% data variables.product.prodname_pages %} und Jekyll unterstützen relative Permalinks nicht mehr. Weitere Informationen zu Permalinks findest Du unter „[Permalinks](https://jekyllrb.com/docs/permalinks/)“ in der Jekyll-Dokumentation. + +Zur Fehlerbehebung entferne die Konfigurationsoption `relative_permalinks` aus der Datei *_config.yml* der Website, und ändere alle relativen Permalinks auf der Website in absolute Permalinks. Weitere Informationen findest Du unter „[Dateien in Deinem Repository bearbeiten](/articles/editing-files-in-your-repository).“ + +### Symlink ist im Repository Deiner Website nicht vorhanden + +Dieser Fehler bedeutet, dass die Website einen symbolischen Link (Symlink) enthält, der sich nicht in der Veröffentlichungsquelle für die Website befindet. Weitere Informationen zu Symlinks findest Du unter „[Symbolic Link](https://en.wikipedia.org/wiki/Symbolic_link)“ (Symbolische Verknüpfung) auf Wikipedia. + +Zur Fehlerbehebung prüfe, ob die in der Fehlermeldung genannte Datei für den Build der Website erforderlich ist. Falls nicht (oder falls die Datei kein Symlink sein soll), lösche die Datei. Wenn die Datei, auf die der Symlink verweist, für den Build der Website erforderlich ist, stelle sicher, dass die Datei oder das Verzeichnis, auf das der Symlink verweist, in der Veröffentlichungsquelle der Website vorhanden ist. 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 %} + +### Syntaxfehler in der „for“-Schleife + +Dieser Fehler bedeutet, dass Dein Code ungültige Syntax in einer Liquid-`for`-Schleifen-Deklaration enthält. + +Zur Fehlerbehebung prüfe die Syntax in allen `for`-Schleifen in der Datei, die in der Fehlermeldung genannt ist. Weitere Informationen zur korrekten Syntax für `for`-Schleifen findest Du unter „[Iteration tags](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)“ (Iterations-Tags) in der Liquid-Dokumentation. + +### Tag nicht ordnungsgemäß geschlossen + +Diese Fehlermeldung bedeutet, dass Dein Code ein logisches Tag enthält, das nicht korrekt geschlossen ist. {% raw %}`{% capture example_variable %}` muss beispielsweise mit `{% endcapture %}`{% endraw %} geschlossen werden. + +Zur Fehlerbehebung prüfe, ob alle logischen Tags in der Datei, die in der Fehlermeldung genannt ist, ordnungsgemäß geschlossen sind. Weitere Informationen findest Du unter „[Liquid tags](https://help.shopify.com/en/themes/liquid/tags)“ (Liquid-Tags) in der Liquid-Dokumentation. + +### Tag nicht ordnungsgemäß beendet + +Diese Fehlermeldung bedeutet, dass Dein Code ein Ausgabe-Tag enthält, das nicht korrekt beendet wurde. Beispiel: {% raw %}`{{ page.title }` statt `{{ page.title }}`{% endraw %}. + +Zur Fehlerbehebung prüfe, ob alle Ausgabe-Tags in der Datei, die in der Fehlermeldung genannt ist, mit `}}` beendet wurden. Weitere Informationen findest Du unter „[Liquid objects](https://help.shopify.com/en/themes/liquid/objects)“ (Liquid-Objekte) in der Liquid-Dokumentation. + +### Unbekannter Tag-Fehler + +Dieser Fehler bedeutet, dass Dein Code ein nicht erkanntes Liquid-Tag enthält. + +Zur Fehlerbehebung prüfe, ob alle Liquid-Tags in der Datei, die in der Fehlermeldung genannt ist, den Jekyll-Standardvariablen entsprechen und ob die Tag-Namen korrekt geschrieben sind. For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation. + +Nicht unterstützte Plug-ins sind häufig die Quelle für unbekannte Tags. Wenn Sie ein nicht unterstütztes Plug-in auf der Website verwenden, also die Website lokal erstellen und die statischen Dateien per Push-Verfahren an {% data variables.product.product_name %} übertragen, darf das Plug-in keine Tags umfassen, die nicht in den Jekyll-Standardvariablen aufgeführt sind. Eine Liste der unterstützten Plug-ins findest Du unter „[Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll#plugins).“ diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md index c9a447104c..88d0ebf27b 100644 --- a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md @@ -170,7 +170,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap In the same way, we can [view repositories for the authenticated user][user repos api]: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -207,7 +207,7 @@ Fetching information for existing repositories is a common use case, but the we need to `POST` some JSON containing the details and configuration options. ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -242,7 +242,7 @@ The UI for Issues on {% data variables.product.product_name %} aims to provide ' Just like github.com, the API provides a few methods to view issues for the authenticated user. To [see all your issues][get issues api], call `GET /issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -250,7 +250,7 @@ To get only the [issues under one of your {% data variables.product.product_name /orgs//issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -283,7 +283,7 @@ Now that we've seen how to paginate lists of issues, let's [create an issue][cre To create an issue, we need to be authenticated, so we'll pass an OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON body to the `/issues` path underneath the repository in which we want to create the issue: ```shell -$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ +$ curl -i -H 'Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/de-DE/content/rest/reference/enterprise-admin.md b/translations/de-DE/content/rest/reference/enterprise-admin.md index 6f71914317..b6439cf97f 100644 --- a/translations/de-DE/content/rest/reference/enterprise-admin.md +++ b/translations/de-DE/content/rest/reference/enterprise-admin.md @@ -100,7 +100,7 @@ The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim).“ +**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim).“ {% endnote %} diff --git a/translations/de-DE/content/rest/reference/migrations.md b/translations/de-DE/content/rest/reference/migrations.md index f552f90cbd..3de0570a1b 100644 --- a/translations/de-DE/content/rest/reference/migrations.md +++ b/translations/de-DE/content/rest/reference/migrations.md @@ -16,7 +16,7 @@ topics: ## Organisation -The Migrations API is only available to authenticated organization owners. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." +The Migrations API is only available to authenticated organization owners. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/de-DE/content/rest/reference/repos.md b/translations/de-DE/content/rest/reference/repos.md index 3db9b334cd..6bf9755273 100644 --- a/translations/de-DE/content/rest/reference/repos.md +++ b/translations/de-DE/content/rest/reference/repos.md @@ -193,7 +193,7 @@ The authenticated user will be the author of any merges done through this endpoi ## Pages -The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." +The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." In {% data variables.product.prodname_pages %} API endpoints with a `status` key in their response, the value can be one of: * `null`: The site has yet to be built. @@ -205,7 +205,7 @@ In {% data variables.product.prodname_pages %} API endpoints with a `status` key In {% data variables.product.prodname_pages %} API endpoints that return GitHub Pages site information, the JSON responses include these fields: * `html_url`: The absolute URL (including scheme) of the rendered Pages site. For example, `https://username.github.io`. * `source`: An object that contains the source branch and directory for the rendered Pages site. This includes: - - `branch`: The repository branch used to publish your [site's source files](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. + - `branch`: The repository branch used to publish your [site's source files](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. - `path`: The repository directory from which the site publishes. Will be either `/` or `/docs`. {% for operation in currentRestOperations %} diff --git a/translations/de-DE/content/rest/reference/scim.md b/translations/de-DE/content/rest/reference/scim.md index 809d441d35..5f79fee0ef 100644 --- a/translations/de-DE/content/rest/reference/scim.md +++ b/translations/de-DE/content/rest/reference/scim.md @@ -14,7 +14,7 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim).“ +**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. Weitere Informationen zu SCIM findest Du unter „[Informationen zu SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim).“ {% endnote %} diff --git a/translations/de-DE/content/rest/reference/teams.md b/translations/de-DE/content/rest/reference/teams.md index 9a722278d4..ed9ae6bbf5 100644 --- a/translations/de-DE/content/rest/reference/teams.md +++ b/translations/de-DE/content/rest/reference/teams.md @@ -18,7 +18,7 @@ This API is only available to authenticated members of the team's [organization] ## Discussions -The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. +The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -26,7 +26,7 @@ The team discussions API allows you to get, create, edit, and delete discussion ## Discussion comments -The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." This API is only available to authenticated members of the team's organization. +The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -39,7 +39,7 @@ This API is only available to authenticated members of the team's organization. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "Synchronizing teams between your identity provider and GitHub." +**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "Synchronizing teams between your identity provider and GitHub." {% endnote %} @@ -54,7 +54,7 @@ This API is only available to authenticated members of the team's organization. The Team Synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups. To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "Authorizing a personal access token for use with a SAML single sign-on organization." -You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." +You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} diff --git a/translations/de-DE/data/release-notes/2-20/15.yml b/translations/de-DE/data/release-notes/2-20/15.yml index aa3c664487..651811695b 100644 Binary files a/translations/de-DE/data/release-notes/2-20/15.yml and b/translations/de-DE/data/release-notes/2-20/15.yml differ diff --git a/translations/de-DE/data/release-notes/2-21/18.yml b/translations/de-DE/data/release-notes/2-21/18.yml new file mode 100644 index 0000000000..e27f2fe4a0 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/18.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. + - Security alerts are not reported when pushing to a repository on the command line. diff --git a/translations/de-DE/data/release-notes/2-21/6.yml b/translations/de-DE/data/release-notes/2-21/6.yml index 8638d1d9cd..24127f581c 100644 Binary files a/translations/de-DE/data/release-notes/2-21/6.yml and b/translations/de-DE/data/release-notes/2-21/6.yml differ diff --git a/translations/de-DE/data/release-notes/2-22/10.yml b/translations/de-DE/data/release-notes/2-22/10.yml new file mode 100644 index 0000000000..fd5aa5a1d8 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-22/10.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. diff --git a/translations/de-DE/data/release-notes/3-0/4.yml b/translations/de-DE/data/release-notes/3-0/4.yml new file mode 100644 index 0000000000..b3a39c1743 --- /dev/null +++ b/translations/de-DE/data/release-notes/3-0/4.yml @@ -0,0 +1,25 @@ +--- +date: '2021-04-01' +intro: 'The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - When maintenance mode was enabled, some services continued to be listed as "active processes" even though they were expected to be running, and should not have been listed. + - After upgrading from 2.22.x to 3.0.x with GitHub Actions enabled, the self-hosted runner version was not updated and no self-hosted updates were made. + - Old GitHub Pages builds were not cleaned up leading to increased disk usage. + - '`memcached` was not running on active replicas.' + - Upgrade failed when updating file permissions when GitHub Actions was enabled. + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The `ghe-saml-mapping-csv` command-line utility produced a warning message. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. + - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text. diff --git a/translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md b/translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md index 5879d3847a..120f828128 100644 --- a/translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md @@ -4,5 +4,7 @@ | `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." | | `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)." | | `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)." | +| `disable_workflow` | Triggered when a workflow is disabled. | +| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`. | | `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)." | | `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. Weitere Informationen findest Du unter "[Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows)." | diff --git a/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md index baa32fddac..b6abfe68c7 100644 --- a/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md +++ b/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md @@ -2,4 +2,4 @@ You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose. -Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_advanced_security %} features, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." diff --git a/translations/de-DE/data/reusables/branches/set-default-branch.md b/translations/de-DE/data/reusables/branches/set-default-branch.md index 20d94881f6..61c5fb0903 100644 --- a/translations/de-DE/data/reusables/branches/set-default-branch.md +++ b/translations/de-DE/data/reusables/branches/set-default-branch.md @@ -1 +1 @@ -You can set the name of the default branch for new repositories. 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 %} +You can set the name of the default branch for new repositories. 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](/organizations/managing-organization-settings/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 %} diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md index 3f4f17e1b2..303bb3669b 100644 --- a/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ The repositories for an assignment can be public or private. If you use private repositories, only the student or team can see the feedback you provide. -You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" and "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. diff --git a/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md b/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md index e554d4b605..b005e29ebd 100644 --- a/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) +1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) 1. Type the name for your classroom. ![Text field for typing name of classroom](/assets/images/help/classroom/type-classroom-name.png) 1. Click **Create classroom**. ![Text field for typing name of classroom](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md b/translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md index 347685c60b..87e3050737 100644 --- a/translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md +++ b/translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md @@ -1 +1,6 @@ -1. Under "Code scanning," click the alert you'd like to explore. ![Liste der Warnungen von {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +1. Under "Code scanning," click the alert you'd like to explore. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Liste der Warnungen von {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Liste der Warnungen von {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% 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 7dd8f996d0..c3b22f4515 100644 --- a/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -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-dependencies)." You can configure access to private registries in a repository's _dependabot.yml_ configuration file. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." +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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)." You can configure access to private registries in a repository's _dependabot.yml_ configuration file. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." diff --git a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md index 726c551403..9a73b1efb0 100644 --- a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md +++ b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md @@ -6,7 +6,7 @@ The following table shows, for each package manager: | Paketmanager | YAML value | Supported versions | Private repositories | Private registries | Vendoring | | -------------- | ---------------- | ------------------------------ |:--------------------:|:------------------:|:---------:| -| Bundler | `bundler` | v1 | | **✓** | **✓** | +| Bundler | `bundler` | v1, v2 | | **✓** | **✓** | | Cargo | `cargo` | v1 | **✓** | **✓** | | | Composer | `composer` | v1, v2 | **✓** | **✓** | | | Docker | `docker` | v1 | **✓** | **✓** | | diff --git a/translations/de-DE/data/reusables/dotcom_billing/coupon-expires.md b/translations/de-DE/data/reusables/dotcom_billing/coupon-expires.md new file mode 100644 index 0000000000..71beb790aa --- /dev/null +++ b/translations/de-DE/data/reusables/dotcom_billing/coupon-expires.md @@ -0,0 +1 @@ +If you use a coupon to pay for a subscription, when the coupon expires, your payment method will be charged the full cost of your subscription. If you do not have a saved payment method, your account will be downgraded to {% data variables.product.prodname_free_user %} for user accounts or {% data variables.product.prodname_free_team %} for organizations. diff --git a/translations/de-DE/data/reusables/education/about-github-education-link.md b/translations/de-DE/data/reusables/education/about-github-education-link.md index 89bb45f873..6d2da71cb9 100644 --- a/translations/de-DE/data/reusables/education/about-github-education-link.md +++ b/translations/de-DE/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Bevor Sie einen individuellen Rabatt anwenden, sollten Sie überprüfen, ob Ihre Lerngemeinschaft bereits mit uns als {% data variables.product.prodname_education %}-Bildungseinrichtung zusammenarbeitet. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)." +Bevor Sie einen individuellen Rabatt anwenden, sollten Sie überprüfen, ob Ihre Lerngemeinschaft bereits mit uns als {% data variables.product.prodname_campus_program %}-Bildungseinrichtung zusammenarbeitet. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)." diff --git a/translations/de-DE/data/reusables/github-actions/actions-github-connect-requirement.md b/translations/de-DE/data/reusables/github-actions/actions-github-connect-requirement.md new file mode 100644 index 0000000000..8b36658e05 --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/actions-github-connect-requirement.md @@ -0,0 +1 @@ +To allow {% data variables.product.prodname_ghe_server %} to use actions directly from {% data variables.product.prodname_dotcom_the_website %}, you can use {% data variables.product.prodname_github_connect %}. You will need to enable the setting for "Server can use actions from {% data variables.product.prodname_dotcom_the_website %} in workflows runs," as described in "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." diff --git a/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md b/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md index 170cb9d652..596402fbc2 100644 --- a/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/de-DE/data/reusables/github-actions/java-jvm-architecture.md @@ -2,16 +2,17 @@ Die Starter-Workflowvorlage richtet den `PATH` so ein, dass er OpenJDK 8 für die x64-Plattform enthält. Wenn Du eine andere Java-Version verwenden willst oder auf eine andere Architektur (`x64` oder `x86)` abzielen möchtest, kannst Du die `setup-java` -Aktion verwenden, um eine andere Java-Laufzeitumgebung auszuwählen. -Um beispielsweise Version 9.0.4 des JDK für die x64-Plattform zu verwenden, kannst Du die `setup-java` Aktion verwenden und die `java-version`- und `architecture`-Parameter auf `'9.0.4'` und `x64` konfigurieren. +For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'adopt'` and `x64`. {% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 + - name: Set up JDK 11 for x64 + uses: actions/setup-java@v2 with: - java-version: '9.0.4' + java-version: '11' + distribution: 'adopt' architecture: x64 ``` {% endraw %} 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 index b2c935e893..046848b19c 100644 --- 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 @@ -1,5 +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)." +**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](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endwarning %} diff --git a/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 28ccd39cce..d79fcc6cdf 100644 --- a/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -Nachdem Du die Teamsynchronisierung aktiviert hast, können Team-Betreuer und Organisationsinhaber ein Team auf {% data variables.product.prodname_dotcom %} oder mit dem API zu einer IdP-Gruppe verbinden. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." +Nachdem Du die Teamsynchronisierung aktiviert hast, können Team-Betreuer und Organisationsinhaber ein Team auf {% data variables.product.prodname_dotcom %} oder mit dem API zu einer IdP-Gruppe verbinden. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md index 318345a41b..00f13df0b0 100644 --- a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md +++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md @@ -1 +1 @@ -3. Bestätige, dass SAML SSO aktiviert ist. Weitere Informationen findest Du unter „[SAML Single Sign-On für Deine Organisation verwalten](/articles/managing-saml-single-sign-on-for-your-organization).“ +3. Bestätige, dass SAML SSO aktiviert ist. Weitere Informationen finden Sie unter „[SAML Single Sign-On für Ihre Organisation verwalten](/organizations/managing-saml-single-sign-on-for-your-organization/)“. diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md index 8d49b27a63..f2132e11ef 100644 --- a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md +++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md @@ -1,5 +1,5 @@ Um die Teamsynchronisierung für Okta zu aktivieren, müssen Du oder Dein IdP-Administrator folgendes machen: -- SAML SSO und SCIM für Deine Organisation mit Okta aktivieren. Weitere Informationen findest Du unter „[SAML Single Sign-On und SCIM mit Okta konfigurieren](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)." +- SAML SSO und SCIM für Deine Organisation mit Okta aktivieren. Weitere Informationen findest Du unter „[SAML Single Sign-On und SCIM mit Okta konfigurieren](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)." - Die Mandanten-URL für Deine Okta-Instanz angeben. - Einen gültigen SSWS-Token generieren, der über schreibgeschützte Administratorberechtigungen für Deine Okta-Installation als ein Dienstbenutzer verfügt. Weitere Informationen findest Du unter [Token erstellen](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) und [Dienstbenutzer](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) in der Okta-Dokumentation. diff --git a/translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md index 26bfebd7e7..29eb864d86 100644 --- a/translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md +++ b/translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md @@ -1 +1 @@ -Teamdiskussionen sind nur auf Teamseiten in Organisationen verfügbar. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)“. +Teamdiskussionen sind nur auf Teamseiten in Organisationen verfügbar. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“. diff --git a/translations/de-DE/data/reusables/organizations/team-synchronization.md b/translations/de-DE/data/reusables/organizations/team-synchronization.md index 3862fdccf8..c10a98a56f 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" or currentVersion == "github-ae@latest" %} -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)." +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](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/de-DE/data/reusables/organizations/team_maintainers_can.md b/translations/de-DE/data/reusables/organizations/team_maintainers_can.md index 65f385030c..5eb2f9cb31 100644 --- a/translations/de-DE/data/reusables/organizations/team_maintainers_can.md +++ b/translations/de-DE/data/reusables/organizations/team_maintainers_can.md @@ -11,5 +11,5 @@ Mitglieder mit Team-Betreuer-Berechtigungen können folgende Aktionen durchführ - [Organisationsmitglieder aus dem Team entfernen](/articles/removing-organization-members-from-a-team) - [Ein vorhandenes Teammitglied zum Team-Betreuer hochstufen](/articles/giving-team-maintainer-permissions-to-an-organization-member) - Remove the team's access to repositories{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -- [Manage code review assignment for the team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} +- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [Geplante Erinnerungen für Pull Requests verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md index 3858e98f3b..4c00bfc6cd 100644 --- a/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. Create a new personal access token (PAT) with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token. {% warning %} - **Note:** If you select the `write:packages` scope, deselect the `repo` scope when creating the PAT. Adding a PAT with the `repo` scope as a secret in your repository allows the credential to be accessible to all collaborators in the repository. This gives unnecessary additional access when a PAT with the `repo` scope is used within an action. For more information on security best practices for actions, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." + **Note:** By default, when you select the `write:packages` scope for your personal access token (PAT) in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for GitHub Actions workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://github.com/settings/tokens/new?scopes=write:packages`. {% endwarning %} diff --git a/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index fb85de55b5..666a293400 100644 --- a/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,5 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} +PATs can grant broad access to your account. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}. + To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)." diff --git a/translations/de-DE/data/reusables/pages/choose-visibility.md b/translations/de-DE/data/reusables/pages/choose-visibility.md index bd794a90d7..9ed7fac761 100644 --- a/translations/de-DE/data/reusables/pages/choose-visibility.md +++ b/translations/de-DE/data/reusables/pages/choose-visibility.md @@ -1 +1 @@ -1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md index fc98787aaa..26d5ca7f58 100644 --- a/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md +++ b/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md b/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md index 04d4ddeb1c..e8de190b64 100644 --- a/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} {% endwarning %} diff --git a/translations/de-DE/data/reusables/pages/sidebar-pages.md b/translations/de-DE/data/reusables/pages/sidebar-pages.md new file mode 100644 index 0000000000..91057e4f20 --- /dev/null +++ b/translations/de-DE/data/reusables/pages/sidebar-pages.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +1. Klicke auf der linken Seitenleiste auf **Pages** (Seiten). ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png) +{% endif %} diff --git a/translations/de-DE/data/reusables/pages/update_your_dns_settings.md b/translations/de-DE/data/reusables/pages/update_your_dns_settings.md index 1639bc4d36..f0e0746452 100644 --- a/translations/de-DE/data/reusables/pages/update_your_dns_settings.md +++ b/translations/de-DE/data/reusables/pages/update_your_dns_settings.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" %}1. Wenn für Deine Website eine benutzerdefinierte Domäne aktiviert ist, aktualisiere Deine DNS-Einstellungen, um eine Domänen-Übernahme zu vermeiden. Weitere Informationen findest Du unter „[Konfigurieren einer benutzerdefinierten Domäne für Deine {% data variables.product.prodname_pages %}-Website](/articles/configuring-a-custom-domain-for-your-github-pages-site)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. Wenn für Deine Website eine benutzerdefinierte Domäne aktiviert ist, aktualisiere Deine DNS-Einstellungen, um eine Domänen-Übernahme zu vermeiden. Weitere Informationen findest Du unter „[Konfigurieren einer benutzerdefinierten Domäne für Deine {% data variables.product.prodname_pages %}-Website](/pages/configuring-a-custom-domain-for-your-github-pages-site)."{% endif %} diff --git a/translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md index c84c031d54..2742482dbc 100644 --- a/translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md +++ b/translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md @@ -1 +1 @@ -Wenn Du eine Apex-Domäne als Deine benutzerdefinierte Domäne verwendest, empfehlen wir, auch eine `www`-Subdomäne einzurichten. Wenn Du über Deinen DNS-Anbieter die richtigen Datensätze für jeden Domänentyp konfigurierst, wird {% data variables.product.prodname_pages %} automatisch Umleitungen zwischen den Domänen erstellen. Wenn Du beispielsweise `www.example.com` als Deine benutzerdefinierte Domäne für Deine Website konfigurierst und `ALIAS`- and `CNAME`-Datensätze für die apex- and `www`-Domänen eingerichtet hast, dann wird `example.com` auf `www.example.com` umleiten. Weitere Informationen findest Du unter „[Verwalten einer benutzerdefinierten Domäne für Deine {% data variables.product.prodname_pages %}-Website](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." +Wenn Du eine Apex-Domäne als Deine benutzerdefinierte Domäne verwendest, empfehlen wir, auch eine `www`-Subdomäne einzurichten. Wenn Du über Deinen DNS-Anbieter die richtigen Datensätze für jeden Domänentyp konfigurierst, wird {% data variables.product.prodname_pages %} automatisch Umleitungen zwischen den Domänen erstellen. For example, if you configure `www.example.com` as the custom domain for your site, and you have {% data variables.product.prodname_pages %} DNS records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. Note that automatic redirects only apply to the `www` subdomain. Automatic redirects do not apply to any other subdomains, such as `blog`. diff --git a/translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index 0f85c1d4f3..672dc9e155 100644 --- a/translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -6,6 +6,6 @@ - Wenn Du [bei aktivierter LDAP-Synchronisation](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync) eine Person aus einem Repository entfernst, verliert diese den Zugriff, aber ihre Forks werden nicht gelöscht. Wenn die Person innerhalb von drei Monaten einem Team mit Zugriff auf das ursprüngliche Organisations-Repository hinzugefügt wird, wird ihr Zugriff auf die Forks bei der nächsten Synchronisierung automatisch wiederhergestellt.{% endif %} - Sie sind dafür verantwortlich, dass die Personen, denen Sie den Zugriff auf ein Repository entziehen, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen. -- 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. Weitere Informationen findest Du unter „[Verwalten der Forking-Richtlinie für Deine Organisation](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" und „[Verwalten der Forking-Richtlinie für Dein Repository".](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) +- 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. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} diff --git a/translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md index 8680ea3380..c98ee7705a 100644 --- a/translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ b/translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -1 +1 @@ -1. Klicke in der linken Seitenleiste auf **Code scanning alerts** (Code-Scan-Warnungen). Wähle optional das von Dir verwendete Code-Scan-Werkzeug aus. ![Registerkarte "Code scanning alerts" (Code-Scan-Warnungen)](/assets/images/help/repository/sidebar-code-scanning-alerts.png) +1. Klicke in der linken Seitenleiste auf **Code scanning alerts** (Code-Scan-Warnungen). ![Registerkarte "Code scanning alerts" (Code-Scan-Warnungen)](/assets/images/help/repository/sidebar-code-scanning-alerts.png) diff --git a/translations/de-DE/data/reusables/saml/about-linked-identities.md b/translations/de-DE/data/reusables/saml/about-linked-identities.md index 9512e75675..1254b5131d 100644 --- a/translations/de-DE/data/reusables/saml/about-linked-identities.md +++ b/translations/de-DE/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -Du kannst die Single Sign-On-Identität anzeigen, die ein Mitglied mit seinem {% data variables.product.product_name %}-Konto verknüpft hat. Wenn verfügbar, wird der Eintrag SCIM-Daten enthalten. Weitere Informationen findest Du unter „[Über SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +Du kannst die Single Sign-On-Identität anzeigen, die ein Mitglied mit seinem {% data variables.product.product_name %}-Konto verknüpft hat. Wenn verfügbar, wird der Eintrag SCIM-Daten enthalten. Weitere Informationen findest Du unter „[Über SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." Wenn ein Mitglied die falsche Identität mit seinem {% data variables.product.product_name %}-Konto verknüpft, kannst Du die verknüpfte Identität widerrufen, damit das Mitglied es erneut versuchen kann. diff --git a/translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md b/translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md index 2baec069d6..195714ec88 100644 --- a/translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,5 @@ {% note %} -**Hinweis:** Externe Mitarbeiter müssen sich nicht bei einem IdP authentifizieren, um auf die Ressourcen in einer Organisation mit SAML-SSO zuzugreifen. Weitere Informationen zu externen Mitarbeitern findest Du unter „[Berechtigungsebenen für eine Organisation](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." +**Hinweis:** Externe Mitarbeiter müssen sich nicht bei einem IdP authentifizieren, um auf die Ressourcen in einer Organisation mit SAML-SSO zuzugreifen. Weitere Informationen zu externen Mitarbeitern findest Du unter „[Berechtigungsebenen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)." {% endnote %} 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 index a7ae50fabd..2fb22e8c3c 100644 --- 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 @@ -7,6 +7,7 @@ | 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 | +| Asana | Asana Personal Access Token | asana_personal_access_token | | 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 | @@ -37,8 +38,12 @@ | 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 | +| Grafana | Grafana API Key | grafana_api_key | | Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | | Hubspot | Hubspot API Key | hubspot_api_key | +| Intercom | Intercom Access Token | intercom_access_token | +| Lob | Lob Live API Key | lob_live_api_key | +| Lob | Lob Test API Key | lob_test_api_key | | Mailchimp | Mailchimp API Key | mailchimp_api_key | | Mailgun | Mailgun API Key | mailgun_api_key | | npm | npm Access Token | npm_access_token | @@ -51,6 +56,7 @@ | Proctorio | Proctorio Secret Key | proctorio_secret_key | | Pulumi | Pulumi Access Token | pulumi_access_token | | PyPI | PyPI API Token | pypi_api_token | +| RubyGems | RubyGems API Key | rubygems_api_key | | Samsara | Samsara API Token | samsara_api_token | | Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | | SendGrid | SendGrid API Key | sendgrid_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 index c9a8d65306..ebc268a20d 100644 --- 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 @@ -50,6 +50,7 @@ | Proctorio | Proctorio Secret Key | | Pulumi | Pulumi Access Token | | PyPI | PyPI API Token | +| RubyGems | RubyGems API Key | | Samsara | Samsara API Token | | Samsara | Samsara OAuth Access Token | | Shopify | Shopify App Shared Secret | diff --git a/translations/de-DE/data/reusables/sponsors/choose-updates.md b/translations/de-DE/data/reusables/sponsors/choose-updates.md index ade59cf05b..93f8807013 100644 --- a/translations/de-DE/data/reusables/sponsors/choose-updates.md +++ b/translations/de-DE/data/reusables/sponsors/choose-updates.md @@ -1 +1 @@ -4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) +4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/de-DE/data/reusables/sponsors/click-add-tier.md b/translations/de-DE/data/reusables/sponsors/click-add-tier.md index 9877d001ee..f2e650fb88 100644 --- a/translations/de-DE/data/reusables/sponsors/click-add-tier.md +++ b/translations/de-DE/data/reusables/sponsors/click-add-tier.md @@ -1 +1 @@ -1. Klicke unten auf der Seite auf **Add a tier** (eine Stufe hinzufügen). ![Schaltfläche „Add a tier" (Eine Stufe hinzufügen)](/assets/images/help/sponsors/add-a-tier-button.png) +1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![Schaltfläche „Add a tier" (Eine Stufe hinzufügen)](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/de-DE/data/reusables/sponsors/enable-custom-amounts.md b/translations/de-DE/data/reusables/sponsors/enable-custom-amounts.md new file mode 100644 index 0000000000..1889367cb9 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/enable-custom-amounts.md @@ -0,0 +1,2 @@ +1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png) +1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png) diff --git a/translations/de-DE/data/reusables/sponsors/feedback.md b/translations/de-DE/data/reusables/sponsors/feedback.md new file mode 100644 index 0000000000..44c1bb7d3f --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/feedback.md @@ -0,0 +1 @@ +You can share your feedback about {% data variables.product.prodname_sponsors %} with {% data variables.product.company_short %}. To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)." diff --git a/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md index 0cd08d5382..b47ac0599d 100644 --- a/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md +++ b/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md @@ -1 +1 @@ -You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)." +You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)." diff --git a/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md b/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md index f201de957c..32f6b098f7 100644 --- a/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md +++ b/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md @@ -1 +1 @@ -1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Due today", click **Pay prorated $X.XX today**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file +1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md b/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md index 56a047d867..9e560bf708 100644 --- a/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/de-DE/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. +If you're starting a monthly sponsorship on behalf of your user account, you'll 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/de-DE/data/reusables/sponsors/review-and-publish-tier.md b/translations/de-DE/data/reusables/sponsors/review-and-publish-tier.md index f1344a6556..a84fd2930a 100644 --- a/translations/de-DE/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/de-DE/data/reusables/sponsors/review-and-publish-tier.md @@ -1 +1 @@ -1. Überprüfe die Eingaben für Deine Stufe, dann klicke auf **Publish tier** (Stufe veröffentlichen). ![Schaltfläche „Publish tier" (Stufe veröffentlichen)](/assets/images/help/sponsors/publish-tier-button.png) +1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/de-DE/data/reusables/sponsors/review-tiers-to-select.md b/translations/de-DE/data/reusables/sponsors/review-tiers-to-select.md new file mode 100644 index 0000000000..03f2b68614 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/review-tiers-to-select.md @@ -0,0 +1 @@ +1. Überprüfe rechts auf der Seite unter „Select a tier" (Eine Stufe wählen) die verfügbaren Sponsorship-Stufen. If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png) diff --git a/translations/de-DE/data/reusables/sponsors/select-a-tier.md b/translations/de-DE/data/reusables/sponsors/select-a-tier.md index 2b236e0808..57b41f6c4a 100644 --- a/translations/de-DE/data/reusables/sponsors/select-a-tier.md +++ b/translations/de-DE/data/reusables/sponsors/select-a-tier.md @@ -1 +1 @@ -1. Überprüfe rechts auf der Seite unter „Select a tier" (Eine Stufe wählen) die verfügbaren Sponsorship-Stufen. Dann klicke rechts neben der gewünschten Stufe auf **Select** (Auswählen). ![Kontrollkästchen „Select a tier" (Stufe wählen)](/assets/images/help/sponsors/select-a-tier-box.png) +1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![Kontrollkästchen „Select a tier" (Stufe wählen)](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/de-DE/data/reusables/sponsors/sponsorship-details.md b/translations/de-DE/data/reusables/sponsors/sponsorship-details.md index 6776f06131..99913e7c14 100644 --- a/translations/de-DE/data/reusables/sponsors/sponsorship-details.md +++ b/translations/de-DE/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. Dein Sponsoring wird das bestehende Rechnungsdatum, die Zahlungsmethode und die Bescheinigung Deines Kontos teilen. +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 one-time or monthly payment amounts and benefits that are set by the sponsored account. Dein Sponsoring wird das bestehende Rechnungsdatum, die Zahlungsmethode und die Bescheinigung Deines Kontos teilen. diff --git a/translations/de-DE/data/reusables/sponsors/tier-details.md b/translations/de-DE/data/reusables/sponsors/tier-details.md index b15cc8079b..7ea866edeb 100644 --- a/translations/de-DE/data/reusables/sponsors/tier-details.md +++ b/translations/de-DE/data/reusables/sponsors/tier-details.md @@ -1,3 +1,3 @@ -Du kannst bis zu zehn Sponsoringstufen für Sponsoren einrichten. Jede Stufe hat ihren eigenen monatlichen Zahlungsbetrag in US-Dollar und Vorteile, wie zum Beispiel den frühzeitigen Zugriff auf neue Versionen oder in der README-Datei des Projekts vorgestellt zu werden. +Du kannst bis zu zehn Sponsoringstufen für Sponsoren einrichten. Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). -Once you have published a tier, you can't edit the price of that tier. Stattdessen musst Du die Stufe zurückziehen und einen neue Stufe erstellen. Bestehende Sponsoren bleiben auf der zurückgezogenen Stufe, bis sie ihre Sponsoring-Stufe ändern oder ihr Sponsoring kündigen. +Once you have published a tier, you can't edit the price of that tier. Stattdessen musst Du die Stufe zurückziehen und einen neue Stufe erstellen. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/de-DE/data/reusables/support/accessing-premium-content.md b/translations/de-DE/data/reusables/support/accessing-premium-content.md index 1d2e9efafb..8f3c1a88cf 100644 --- a/translations/de-DE/data/reusables/support/accessing-premium-content.md +++ b/translations/de-DE/data/reusables/support/accessing-premium-content.md @@ -1,4 +1,4 @@ ### Auf Premium-Inhalte zugreifen -Du kannst auf Premium-Inhalte zugreifen, indem Du Dich beim {% data variables.contact.contact_enterprise_portal %} anmeldest. +Du kannst auf Premium-Inhalte zugreifen, indem Du Dich beim {% data variables.contact.contact_landing_page_portal %} anmeldest. diff --git a/translations/de-DE/data/reusables/support/contacting-premium-support.md b/translations/de-DE/data/reusables/support/contacting-premium-support.md index 06ce021dc2..8409b1e855 100644 --- a/translations/de-DE/data/reusables/support/contacting-premium-support.md +++ b/translations/de-DE/data/reusables/support/contacting-premium-support.md @@ -1,4 +1,4 @@ ### {% data variables.contact.premium_support %} kontaktieren -{% data variables.contact.premium_support %}-Kunden können das {% data variables.contact.contact_enterprise_portal %} benutzen, um Issues schriftlich in Englisch melden. Darüber hinaus kannst Du telefonischen Support auf Englisch erhalten. Die {% data variables.contact.premium_support %}-Telefonnummer findest Du unter „[Durchgängiger Telefonsupport](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)“ im {% data variables.contact.enterprise_portal %}. +{% data variables.contact.premium_support %}-Kunden können das {% data variables.contact.contact_landing_page_portal %} benutzen, um Issues schriftlich in Englisch melden. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/user_settings/billing_plans.md b/translations/de-DE/data/reusables/user_settings/billing_plans.md new file mode 100644 index 0000000000..8d26ab1479 --- /dev/null +++ b/translations/de-DE/data/reusables/user_settings/billing_plans.md @@ -0,0 +1 @@ +1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png) diff --git a/translations/de-DE/data/variables/contact.yml b/translations/de-DE/data/variables/contact.yml index 6028e9f928..ef241d751e 100644 --- a/translations/de-DE/data/variables/contact.yml +++ b/translations/de-DE/data/variables/contact.yml @@ -24,9 +24,12 @@ contact_enterprise_portal: '[GitHub Enterprise Supportportal](https://enterprise #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)' -#GitHub Support portal (for dotcom) +#GitHub Support portal (for dotcom - this sends users to a contact form) support_portal: 'GitHub-Supportportal' contact_support_portal: '[GitHub-Supportportal](https://support.github.com/contact)' +#GitHub Support portal (this sends users to the Support landing page) +landing_page_portal: 'GitHub-Supportportal' +contact_landing_page_portal: '[GitHub Support portal](https://support.github.com/)' #The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) community_support: 'GitHub Community Support' #The GitHub Community forum diff --git a/translations/es-ES/content/actions/creating-actions/about-actions.md b/translations/es-ES/content/actions/creating-actions/about-actions.md index 943550ec46..06f4425fb0 100644 --- a/translations/es-ES/content/actions/creating-actions/about-actions.md +++ b/translations/es-ES/content/actions/creating-actions/about-actions.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'resumen' topics: - - Desarrollo de las acciones - - Fundamentos + - 'Desarrollo de las acciones' + - 'Fundamentos' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md index e7c00dab7e..3dd9d05adf 100644 --- a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -58,7 +58,7 @@ inputs: 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`. +For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables. #### `inputs.` @@ -76,6 +76,10 @@ Por ejemplo, si un flujo de trabajo definió las entradas numOctocats y octocatE **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. +#### `inputs..deprecationMessage` + +**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives. + ### `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. @@ -147,7 +151,7 @@ runs: #### `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). +**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. The application specified with the [`using`](#runsusing) syntax will execute this file. 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`: @@ -170,9 +174,9 @@ En este ejemplo, `cleanup.js` se ejecuta únicamente en los ejecutores basados e pre-if: 'runner.os == linux' ``` -#### `post` +#### `publicación` -**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. +**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. The application specified with the [`using`](#runsusing) syntax will execute this file. En este ejemplo, la acción `post:` ejecuta un script llamado `cleanup.js`: @@ -282,7 +286,7 @@ runs: **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. +The application specified with the [`using`](#runsusing) syntax will execute this file. En este ejemplo, la acción `pre.entrypoint:` ejecuta un script llamado `setup.sh`: diff --git a/translations/es-ES/content/actions/guides/about-continuous-integration.md b/translations/es-ES/content/actions/guides/about-continuous-integration.md index 7f033dbf38..a90f04cbc0 100644 --- a/translations/es-ES/content/actions/guides/about-continuous-integration.md +++ b/translations/es-ES/content/actions/guides/about-continuous-integration.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'resumen' topics: - - CI - - DC + - 'CI' + - 'DC' --- {% data reusables.actions.enterprise-beta %} 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 index c207dd9dfa..78fe8c9800 100644 --- 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 @@ -9,9 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'resumen' topics: - - Embalaje + - 'Embalaje' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/guides/about-service-containers.md b/translations/es-ES/content/actions/guides/about-service-containers.md index df0e1971af..dcb4b0fa3f 100644 --- a/translations/es-ES/content/actions/guides/about-service-containers.md +++ b/translations/es-ES/content/actions/guides/about-service-containers.md @@ -9,10 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'resumen' topics: - - Contenedores - - Docker + - 'Contenedores' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} 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 index e57079f624..3525038db9 100644 --- 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Ant run: ant -noinput -buildfile build.xml ``` @@ -70,7 +71,7 @@ jobs: 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. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 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. @@ -91,9 +92,10 @@ Si usas diferentes comandos para construir tu proyecto, o si deseas ejecutar un ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Ant jar target run: ant -noinput -buildfile build-ci.xml jar ``` @@ -109,7 +111,11 @@ Por lo general, Ant crea archivos de salida como JAR, EAR o WAR en el directorio ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ant -noinput -buildfile build.xml - uses: actions/upload-artifact@v2 with: 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 index f03c4c5088..002aa2847c 100644 --- 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Gradle run: ./gradlew build ``` @@ -70,7 +71,7 @@ jobs: 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. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 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. @@ -91,9 +92,10 @@ Si usas diferentes comandos para construir tu proyecto, o si quieres usar una ta ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Gradle package task run: ./gradlew -b ci.gradle package ``` @@ -107,10 +109,11 @@ Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotc ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Gradle packages uses: actions/cache@v2 with: @@ -143,7 +146,11 @@ Por lo general, Gradle creará archivos de salida como JAR, EAR o WAR en el dire ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ./gradlew build - uses: actions/upload-artifact@v2 with: 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 index d340ef6dd9..64312c73e0 100644 --- 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Maven run: mvn --batch-mode --update-snapshots verify ``` @@ -70,7 +71,7 @@ jobs: 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. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 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. @@ -91,9 +92,10 @@ Si usas diferentes comandos para compilar tu proyecto, o si quieres usar un dest ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Maven verify phase run: mvn --batch-mode --update-snapshots verify ``` @@ -107,10 +109,11 @@ Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotc ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Maven packages uses: actions/cache@v2 with: @@ -134,7 +137,10 @@ Por lo general, Maven creará archivos de salida como tarros, orejas o guerras e ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 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 index afc3630406..3cbbae8d49 100644 --- a/translations/es-ES/content/actions/guides/building-and-testing-net.md +++ b/translations/es-ES/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: ['3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -81,7 +81,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet: [ '2.2.103', '3.0', '3.1.x' ] + dotnet: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -201,7 +201,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 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 index d2a782043c..d3d1cdbec8 100644 --- 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 @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -143,9 +144,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -209,9 +211,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to the Maven Central Repository run: gradle publish env: 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 index f7d2223571..16f6e7b066 100644 --- 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 @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -147,9 +148,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: mvn --batch-mode deploy env: @@ -183,9 +185,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java for publishing to Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -195,9 +198,10 @@ jobs: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to GitHub Packages run: mvn --batch-mode deploy env: diff --git a/translations/es-ES/content/actions/guides/using-github-actions-for-project-management.md b/translations/es-ES/content/actions/guides/using-github-actions-for-project-management.md index 49e02aaab6..d0db97eb64 100644 --- a/translations/es-ES/content/actions/guides/using-github-actions-for-project-management.md +++ b/translations/es-ES/content/actions/guides/using-github-actions-for-project-management.md @@ -1,14 +1,14 @@ --- title: Utilizar GitHub Actions para la administración de proyectos -intro: 'Puedes utilizar las {% data variables.product.prodname_actions %} para automatizar muchas de tus tareas de administración de proyectos.' +intro: Puedes utilizar las {% data variables.product.prodname_actions %} para automatizar muchas de tus tareas de administración de proyectos. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'resumen' topics: - - Administración de proyectos + - 'Administración de proyectos' --- Puedes utilizar las {% data variables.product.prodname_actions %} para automatizar tus tareas de administración de proyectos si creas flujos de trabajo. Cada flujo de trabajo contiene una serie de tareas que se llevan a cabo automáticamente cada que se ejecuta el flujo de trabajo. Por ejemplo, puedes crear un flujo de trabajo que se ejecute cada vez que se crea una propuesta para que se agregue una etiqueta, se deje un comentario y se mueva la propuesta a otro tablero de proyecto. diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 1ba4e1b0d6..06c496a62c 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -1,83 +1,90 @@ --- -title: About self-hosted runners -intro: 'You can host your own runners and customize the environment used to run jobs in your {% data variables.product.prodname_actions %} workflows.' +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: 'overview' + github-ae: '*' +type: 'resumen' --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### About self-hosted runners +### Acerca de los ejecutores autoalojados -{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud. +{% data reusables.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. -You can add self-hosted runners at various levels in the management hierarchy: -- Repository-level runners are dedicated to a single repository. -- Organization-level runners can process jobs for multiple repositories in an organization. -- Enterprise-level runners can be assigned to multiple organizations in an enterprise account. +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. -Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs. +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 %} -For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." +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)". -### Differences between {% data variables.product.prodname_dotcom %}-hosted and self-hosted runners +### Diferencias entre ejecutores alojados en {% data variables.product.prodname_dotcom %} y autoalojados -{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted runners are a highly configurable way to run workflows in your own custom environment. +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. -**{% data variables.product.prodname_dotcom %}-hosted runners:** -- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application. -- Are managed and maintained by {% data variables.product.prodname_dotcom %}. -- Provide a clean instance for every job execution. -- Use free minutes on your {% data variables.product.prodname_dotcom %} plan, with per-minute rates applied after surpassing the free minutes. +**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. -**Self-hosted runners:** -- Receive automatic updates for the self-hosted runner application only. You are responsible updating the operating system and all other software. -- Can use cloud services or local machines that you already pay for. -- Are customizable to your hardware, operating system, software, and security requirements. -- Don't need to have a clean instance for every job execution. -- Are free to use with {% data variables.product.prodname_actions %}, but you are responsible for the cost of maintaining your runner machines. +**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. -### Requirements for self-hosted runner machines +### Requisitos para máquinas de ejecutores autoalojados -You can use any machine as a self-hosted runner as long at it meets these requirements: +Puedes usar cualquier máquina como ejecutor autoalojado, siempre que cumpla con estos requisitos: -* You can install and run the self-hosted runner application on the machine. For more information, see "[Supported operating systems for self-hosted runners](#supported-operating-systems-for-self-hosted-runners)." -* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." -* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources. -* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed. +* Puedes instalar y ejecutar la aplicación del ejecutor autoalojado en la máquina. Para obtener más información, consulta la sección "[Arquitecturas y sistemas operativos compatibles para ejecutores auto-hospedados](#supported-architectures-and-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. -### Usage limits +### Límites de uso -There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change. +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 %} -- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete. +- **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 %} -- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %} +- **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %} -### Supported architectures and operating systems for self-hosted runners +### Continuidad de los flujos de trabajo para los ejecutores auto-hospedados -The following operating systems are supported for the self-hosted runner application. +{% data reusables.github-actions.runner-workflow-continuity %} + +### Sistemas operativos y arquitecturas compatibles para los ejecutores auto-hospedados + +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 or later -- Debian 9 or later -- Ubuntu 16.04 or later -- Linux Mint 18 or later -- openSUSE 15 or later -- SUSE Enterprise Linux (SLES) 12 SP2 or later +- 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 @@ -90,59 +97,73 @@ The following operating systems are supported for the self-hosted runner applica #### macOS -- macOS 10.13 (High Sierra) or later +- macOS 10.13 (High Sierra) o posterior -#### Architectures +#### Arquitecturas -The following processor architectures are supported for the self-hosted runner application. +Las siguientes arquitecturas de procesamiento son compatibles para la aplicación del ejecutor auto-hospedado. - `x64` - Linux, macOS, Windows. -- `ARM64` - Linux only. -- `ARM32` - Linux only. +- `ARM64` - Solo Linux. +- `ARM32` - Solo Linux. {% if enterpriseServerVersions contains currentVersion %} -### Supported actions on self-hosted runners +### La comunicación entre ejecutores autoalojados y {{ site.data.variables.product.prodname_dotcom }} -Some extra configuration might be required to use actions from {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_ghe_server %}, or to use the `actions/setup-LANGUAGE` actions with self-hosted runners that do not have internet access. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator. +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 %} -### Communication between self-hosted runners and {% data variables.product.product_name %} +### La comunicación entre ejecutores autoalojados y {% data variables.product.product_name %} -The self-hosted runner polls {% data variables.product.product_name %} to retrieve application updates and to check if any jobs are queued for processing. The self-hosted runner uses a HTTPS _long poll_ that opens a connection to {% data variables.product.product_name %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run {% data variables.product.prodname_actions %} jobs. +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 == "github-ae@latest" %} +Debes asegurarte de que el ejecutor auto-hospedado tenga un acceso adecuado a la red para comunicarse con la +URL de {% data variables.product.prodname_ghe_managed %}. +Por ejemplo, si el nombre de tu instancia es `octoghae`, entonces necesitarás permitir que el ejecutor auto-hospedado acceda a `octoghae.github.com`. +Si utilizas una lista blanca para las direcciones IP para tu + +cuenta empresarial u organizacional 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 en tu organización](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)". +{% endif %} {% if currentVersion == "free-pro-team@latest" %} -You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} URLs listed below. +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 github-releases.githubusercontent.com +github-registry-files.githubusercontent.com codeload.github.com +*.pkg.github.com +pkg-cache.githubusercontent.com +pkg-containers.githubusercontent.com +pkg-containers-az.githubusercontent.com ``` -If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". +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](/organizations/keeping-your-organization-secure/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 %} -You must ensure that the machine has the appropriate network access to communicate with {% data variables.product.product_location %}. +Debes asegurarte de que la máquina tenga el acceso de red adecuado para comunicarse con {% data variables.product.product_location %}. {% endif %} -You can also use self-hosted runners with a proxy server. For more information, see "[Using a proxy server with self-hosted runners](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)." +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)." -### Self-hosted runner security with public repositories +### Seguridad de ejecutores autoalojdados con repositorios públicos {% data reusables.github-actions.self-hosted-runner-security %} -This is not an issue with {% data variables.product.prodname_dotcom %}-hosted runners because each {% data variables.product.prodname_dotcom %}-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution. +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. -Untrusted workflows running on your self-hosted runner poses significant security risks for your machine and network environment, especially if your machine persists its environment between jobs. Some of the risks include: +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: -* Malicious programs running on the machine. -* Escaping the machine's runner sandbox. -* Exposing access to the machine's network environment. -* Persisting unwanted or dangerous data on the machine. +* 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 index e8a3ec454b..f9de2a00e0 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -1,80 +1,84 @@ --- -title: Adding self-hosted runners -intro: 'You can add a self-hosted runner to a repository, an organization, or an enterprise.' +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' + github-ae: '*' type: 'tutorial' --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -You can add a self-hosted runner to a repository, an organization, or an enterprise. +Puedes agregar un ejecutor auto-hospedado a {{ 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. +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. -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)." +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 %} -**Warning:** {% data reusables.github-actions.self-hosted-runner-security %} +**Advertencia:** {% data reusables.github-actions.self-hosted-runner-security %} -For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." +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 %} -### Adding a self-hosted runner to a repository +### Agregar un ejecutor auto-hospedado a un repositorio -You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. +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. Under "Self-hosted runners," click **Add runner**. +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 %} -### Adding a self-hosted runner to an organization +### Agregar un ejecutor auto-hospedado a una organización -You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. +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. Under "Self-hosted runners," click **Add new**, then click **New runner**. +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 %} -### Adding a self-hosted runner to an enterprise +### Agregar un ejecutor auto-hospedado a una empresa -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. +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" %} -To add a self-hosted runner to an enterprise account, you must be an enterprise owner. -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} -To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. +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" or currentVersion == "github-ae@latest" %} +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. Click the **Self-hosted runners** tab. -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)." +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 %} -#### Making enterprise runners available to repositories +#### Hacer que los ejecutores empresariales estén disponibles para los repositorios -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. +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. -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. +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. -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)." +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/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 36a11e07c2..553050db48 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -1,65 +1,68 @@ --- -title: Monitoring and troubleshooting self-hosted runners -intro: You can monitor your self-hosted runners to view their activity and diagnose common issues. +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 + - /Actions/Automating-Your-Workflow-with-GitHub-Actions/Checking-The-status-of-Self-Hosted-Runners versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' type: 'tutorial' defaultPlatform: linux --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### Checking the status of a self-hosted runner +### 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. Under "Self-hosted runners," you can view a list of registered runners, including the runner's name, labels, and status. +1. Debajo de "Ejecutores auto-hospedados", puedes ver una lista de ejecutores registrados, incluyendo su nombre, etiquetas y estado. - ![Runner list](/assets/images/help/settings/actions-runner-list.png) + ![Lista de ejecutores](/assets/images/help/settings/actions-runner-list.png) - The status can be one of the following: + El estado puede ser uno de los siguientes: - * **Idle**: The runner is connected to {% data variables.product.product_name %} and is ready to execute jobs. - * **Active**: The runner is currently executing a job. - * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}. + * **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 %}. -### Reviewing the self-hosted runner application log files +### Revisar los archivos de bitácora de la aplicación del ejecutor auto-hospedado -You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory, and a new one is generated each time the application is started. The filename begins with *Runner_*, and is followed by a UTC timestamp of when the application was started. +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. -For detailed logs on workflow job executions, see the next section describing the *Worker_* files. +Para obtener registros detallados sobre las ejecuciones de jobs en el flujo de trabajo, consulta la siguiente sección que describe los archivos *Worker_*. -### Reviewing a job's log file +### Revisar el archivo de bitácora de un job -The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory, and the filename begins with *Worker_*. +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 %} -### Using journalctl to check the self-hosted runner application service +### Utilizar journalctl para revisar el servicio de la aplicación del ejecutor auto-hospedado -For Linux-based self-hosted runners running the application using a service, you can use `journalctl` to monitor their real-time activity. The default systemd-based service uses the following naming convention: `actions.runner.-..service`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file. For example: +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 ``` -You can use `journalctl` to monitor the real-time activity of the self-hosted runner: +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 ``` -In this example output, you can see `runner01` start, receive a job named `testAction`, and then display the resulting status: +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 @@ -71,23 +74,22 @@ Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: test Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded ``` -To view the systemd configuration, you can locate the service file here: `/etc/systemd/system/actions.runner.-..service`. -If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)." +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 %} -### Using launchd to check the self-hosted runner application service +### Utilizar launchd para revisar el servicio de la aplicación del ejecutor auto-hospedado -For macOS-based self-hosted runners running the application as a service, you can use `launchctl` to monitor their real-time activity. The default launchd-based service uses the following naming convention: `actions.runner.-.`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file in the runner directory: +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 ``` -The `svc.sh` script uses `launchctl` to check whether the application is running. For example: +El script `svc.sh` utiliza `launchctl` para revisar si la aplicación se está ejecutando. Por ejemplo: ```shell $ ./svc.sh status @@ -97,26 +99,25 @@ Started: 379 0 actions.runner.example.runner01 ``` -The resulting output includes the process ID and the name of the application’s launchd service. +La salida generada incluye la ID del proceso y el nombre del servicio launchd de la aplicación. -To view the launchd configuration, you can locate the service file here: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. -If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)." +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 %} -### Using PowerShell to check the self-hosted runner application service +### Utilizar PowerShell para revisar el servicio de la aplicación del ejecutor auto-hospedado -For Windows-based self-hosted runners running the application as a service, you can use PowerShell to monitor their real-time activity. The service uses the naming convention `GitHub Actions Runner (-.)`. You can also find the service's name by checking the _.service_ file in the runner directory: +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 ``` -You can view the status of the runner in the Windows _Services_ application (`services.msc`). You can also use PowerShell to check whether the service is running: +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 @@ -125,7 +126,7 @@ Name Status actions.runner.octo-org-octo-repo.runner01.service Running ``` -You can use PowerShell to check the recent activity of the self-hosted runner. In this example output, you can see the application start, receive a job named `testAction`, and then display the resulting status: +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 @@ -144,34 +145,34 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer {% endwindows %} -### Monitoring the automatic update process +### Monitorear el proceso de actualización automática -We recommend that you regularly check the automatic update process, as the self-hosted runner will not be able to process jobs if it falls below a certain version threshold. The self-hosted runner application automatically updates itself, but note that this process does not include any updates to the operating system or other software; you will need to separately manage these updates. +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. -You can view the update activities in the *Runner_* log files. For example: +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. ``` -In addition, you can find more information in the _SelfUpdate_ log files located in the `_diag` directory. +Adicionalmente, puedes encontrar más información en los archivos de bitácora _SelfUpdate_ ubicados en el directorio `_diag`. {% linux %} -### Troubleshooting containers in self-hosted runners +### Solucionar problemas en los contenedores de los ejecutores auto-hospedados -#### Checking that Docker is installed +#### Revisar que se haya instalado Docker -If your jobs require containers, then the self-hosted runner must be Linux-based and needs to have Docker installed. Check that your self-hosted runner has Docker installed and that the service is running. +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. -You can use `systemctl` to check the service status: +Puedes utilizar `systemctl` para revisar el estado del servicio: ```shell $ sudo systemctl is-active docker.service active ``` -If Docker is not installed, then dependent actions will fail with the following errors: +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' @@ -179,15 +180,15 @@ If Docker is not installed, then dependent actions will fail with the following [2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' ``` -#### Checking the Docker permissions +#### Revisar los permisos de Docker -If your job fails with the following error: +Si tu job falla con el siguiente error: ```shell dial unix /var/run/docker.sock: connect: permission denied ``` -Check that the self-hosted runner's service account has permission to use the Docker service. You can identify this account by checking the configuration of the self-hosted runner in systemd. For example: +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 diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md index 73682bdedb..cbe338f532 100644 --- a/translations/es-ES/content/actions/index.md +++ b/translations/es-ES/content/actions/index.md @@ -22,9 +22,9 @@ featuredLinks: - /actions/reference/environment-variables - /actions/reference/encrypted-secrets changelog: - label: 'actions' - prefix: 'GitHub Actions: ' -product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU' + label: 'acciones' + prefix: 'GitHub Actions:' +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/ 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 index 6cffdf986c..aad049bdb5 100644 --- 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'resumen' topics: - - Fundamentos + - 'Fundamentos' --- {% data reusables.actions.enterprise-beta %} 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 index 53d2eeb163..c55ebe3038 100644 --- 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 @@ -10,9 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'resumen' topics: - - Fundamentos + - 'Fundamentos' --- {% data reusables.actions.enterprise-beta %} 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 index 9343f0cf3d..232baa82b7 100644 --- 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 @@ -8,13 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: overview + github-ae: '*' +type: 'resumen' topics: - - Seguridad + - 'Seguridad' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### Resumen @@ -22,9 +24,9 @@ Esta guía explica cómo configurar el fortalecimiento de seguridad para ciertas ### 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 valores sensibles jamás deben almacenarse como texto simple e archivos de flujo de trabajo, sino más bien como secretos. Se pueden configurar [Secretos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) a nivel de la organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, repositorio o ambiente{% else %} o repositorio{% endif %}, y esto te permitirá 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. +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 excepció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: @@ -41,7 +43,7 @@ Para ayudar a prevenir la divulgación accidental, {% data variables.product.pro - **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" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - **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 %} @@ -75,7 +77,7 @@ Esto significa que el poner en riesgo una sola acción dentro de un flujo de tra ### 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. +{% data variables.product.prodname_actions %} 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, permitir que el `GITHUB_TOKEN` de un repositorio otorgue acceso a otro de ellos impactará el modelo de permisos de {% data variables.product.prodname_dotcom %} si no se implementa con cuidado. 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. @@ -115,33 +117,68 @@ Algunos clientes podrían intentar mitigar estos riesgos parcialmente implementa 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) +Por ejemplo, puedes utilizar la bitácora de auditoría para rastrear el evento `org.update_actions_secret`, el cual rastrea los cambios en 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. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +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](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)". + +{% if currentVersion == "free-pro-team@latest" %} +#### Eventos para los ambientes + +| Acción | Descripción | +| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.create_actions_secret` | Se activa cuando se crea un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | +| `environment.delete` | Se activa cuando se borra un ambiente. Para obtener más información, consulta la sección "[Borrar un ambiente](/actions/reference/environments#deleting-an-environment)". | +| `environment.remove_actions_secret` | Se activa cuando se elimina a un secreto de un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | +| `environment.update_actions_secret` | Se activa cuando se actualiza a un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Eventos para cambios de configuración +| Acción | Descripción | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.actions_enabled` | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no es visible cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)". | +{% endif %} #### 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 %}. | +| Acción | Descripción | +| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org.create_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se crea para una organización. Para obtener más información, consulta la sección "[Crear secretos cifrados para una organización](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)". | +| `org.remove_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se elimina. | +| `org.update_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se actualiza. | +| `repo.create_actions_secret` | Se crea cuando un secreto de {% data variables.product.prodname_actions %} se crea para un repositorio. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". | +| `repo.remove_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se elimina. | +| `repo.update_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se actualiza. | #### 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). | +| Acción | Descripción | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| {% else %} | | +| `enterprise.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una empresa](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)". | +| `enterprise.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. | +| `enterprise.runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". | +| `enterprise.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Puede visualizarse utilizando la API de REST y la IU. Este evento no se incluye cuando exportas la bitácora de auditoría como datos de JSON o como un archivo de CSV. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" y "[Revisar la bitácora de auditoría en tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)".{% endif %} +| `org.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | +| `org.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección [Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | +| `org.runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". | +| `org.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de 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)". | +| `org.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | +| `repo.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | +| `repo.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | +| `repo.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | #### 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. | +| Acción | Descripción | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise.runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una empresa](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)". | +| `enterprise.runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | +| `enterprise.runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. | +| `enterprise.runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover 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)". | +| `enterprise.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de 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)". | +| `org.runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | +| `org.runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | +| `org.runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover 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)". | +| `org.runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | + +#### Eventos para las actividades de los flujos de trabajo + +{% data reusables.actions.actions-audit-events-workflow %} 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 index 753dda70cb..1586a16658 100644 --- 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 @@ -1,36 +1,35 @@ --- -title: Manually running a workflow -intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the REST API or from the Actions tab on {% data variables.product.prodname_dotcom %}.' +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' + github-ae: '*' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### Configuring a workflow to run manually +### Configurar un flujo de trabajo para que se ejecute manualmente -To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". +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)". -### Running a workflow on {% data variables.product.prodname_dotcom %} +### Ejecutar un flujo de trabajo en {% data variables.product.prodname_dotcom %} -To trigger the `workflow_dispatch` event on {% data variables.product.prodname_dotcom %}, your workflow must be in the default branch. Follow these steps to manually trigger a workflow run. +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-write %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. In the left sidebar, click the workflow you want to run. -![actions select workflow](/assets/images/actions-select-workflow.png) -1. Above the list of workflow runs, select **Run workflow**. -![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png) -1. Select the branch where the workflow will run and type the input parameters used by the workflow. Click **Run workflow**. -![actions manually run workflow](/assets/images/actions-manually-run-workflow.png) +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) -### Running a workflow using the REST API +### Ejecutar un flujo de trabajo utilizando la API de REST -When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used. +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. -For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)." +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/quickstart.md b/translations/es-ES/content/actions/quickstart.md index 9602d5bf9a..f3d2e74ab6 100644 --- a/translations/es-ES/content/actions/quickstart.md +++ b/translations/es-ES/content/actions/quickstart.md @@ -1,151 +1,89 @@ --- -title: Quickstart for GitHub Actions -intro: 'Add a {% data variables.product.prodname_actions %} workflow to an existing repository in 5 minutes or less.' -allowTitleToDifferFromFilename: true +title: Guía de inicio rápido para GitHub Actions +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' +allowTitleToDifferFromFilename: verdadero redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' type: 'quick_start' topics: - - 'Fundamentals' + - 'Fundamentos' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### Introduction +### Introducción -You only need an existing {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that lints multiple coding languages using the [{% data variables.product.prodname_dotcom %} Super-Linter action](https://github.com/github/super-linter). The workflow uses Super-Linter to validate your source code every time a new commit is pushed to your repository. +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. -### Creating your first workflow +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. -1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `superlinter.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." -2. Copy the following YAML contents into the `superlinter.yml` file. **Note:** If your default branch is not `main`, update the value of `DEFAULT_BRANCH` to match your repository's default branch name. +### 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 `github-actions-demo.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 `github-actions-demo.yml`: {% raw %} ```yaml{:copy} - name: Super-Linter - - # Run this workflow every time a new commit pushed to your repository - on: push - + name: GitHub Actions Demo + 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 + Explore-GitHub-Actions: runs-on: ubuntu-latest - steps: - # Checks out a copy of your repository on the ubuntu-latest machine - - name: Checkout code + - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event." + - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!" + - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}." + - name: Check out repository code uses: actions/checkout@v2 + - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner." + - run: echo "🖥️ The workflow is now ready to test your code on the runner." + - name: List files in the repository + run: | + ls ${{ github.workspace }} + - run: echo "🍏 This job's status is ${{ job.status }}." - # 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. To run your workflow, scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. - ![Commit workflow file](/assets/images/commit-workflow-file.png) +3. 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**. ![Archivo de flujo de trabajo de la confirmación](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -Committing the workflow file in your repository triggers the `push` event and runs your workflow. +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. -### Viewing your workflow results +### 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. Under **Jobs** or in the visualization graph, click the **Lint code base** job. - ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) -{% else %} -1. In the left sidebar, click the **Lint code base** job. - ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) -{% endif %} -{% data reusables.repositories.view-failed-job-results-superlinter %} +1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieres ver. -### More workflow templates + ![Lista de flujos de trabajo en la barra lateral izquierda](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +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/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. + + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. + + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) + +### Más plantillas de flujo de trabajo {% data reusables.actions.workflow-template-overview %} -### Next steps +### Pasos siguientes -The super-linter workflow you just added runs any time code is pushed to your repository to help you spot errors and inconsistencies in your code. But, this is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}: +The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. Pero esto es solo el inicio de lo que puedes hacer con {% data variables.product.prodname_actions %}: -- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial -- "[Guides](/actions/guides)" for specific uses cases and examples -- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action +- Tu repositorio puede contener varios flujos de trabajo que activen jobs diferentes basándose en eventos diferentes. +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. - +- "[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. diff --git a/translations/es-ES/content/actions/reference/environment-variables.md b/translations/es-ES/content/actions/reference/environment-variables.md index e677e1da02..71ea971989 100644 --- a/translations/es-ES/content/actions/reference/environment-variables.md +++ b/translations/es-ES/content/actions/reference/environment-variables.md @@ -22,6 +22,7 @@ versions: 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)". +{% raw %} ```yaml jobs: weekday_job: @@ -30,13 +31,14 @@ jobs: DAY_OF_WEEK: Mon steps: - name: "Hello world when it's Monday" - if: env.DAY_OF_WEEK == 'Mon' + if: ${{ env.DAY_OF_WEEK == 'Mon' }} run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" env: FIRST_NAME: Mona middle_name: The Last_Name: Octocat ``` +{% endraw %} Para utilizar el valor de una variable de ambiente en un archivo de flujo de trabajo, deberías utilizar el [contexto `env`](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). Si quieres utilizar el valor de una variable de ambiente dentro de un ejecutor, puedes utilizar el método normal del sistema operativo ejecutor para leer las variables de ambiente. 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 index 75ac5f9c93..6f4bfd129b 100644 --- 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 @@ -70,7 +70,7 @@ Puedes configurar el periodo de retenciòn de artefactos y bitàcoras para tu re 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 organizaciòn](/organizations/managing-organization-settings/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 %} @@ -80,7 +80,7 @@ Para obtener más información, consulta: 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" %} +- "[Inhabilitar o limitar {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/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" or currentVersion == "github-ae@latest" %} 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 index 6e5b761333..f45dcd041d 100644 --- 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 @@ -8,7 +8,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' topics: 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 index 4f90dfe2ca..b8d281ba16 100644 --- 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 @@ -21,7 +21,7 @@ Después de que habilitas el SSO de SAML y de SCIM para {% data variables.produc * Asignar la aplicación de {% data variables.product.prodname_ghe_managed %} a un grupo de IdP en Azure AD para que cree y otorgue acceso automáticamente a las cuentas de usuario en {% data variables.product.product_name %} para todos los miembros del grupo de IdP. Adicionalmente, el grupo de IdP estará disponible en {% data variables.product.prodname_ghe_managed %} para que se conecte a un equipo y a sus organizaciones padre. * Desasignar la aplicación de {% data variables.product.prodname_ghe_managed %} desde un grupo de IdP para desactivar las cuentas de usuario de {% data variables.product.product_name %} de todos los usuarios de IdP que tuvieron acceso únicamente a través de este grupo de IdP y eliminar a los usuarios de la organización padre. El grupo de IdP se desconectará de cualquier equipo 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)". Para obtener más información sobre cómo sincronizar equipos con grupos de IdP, 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)". +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)". Para obtener más información sobre cómo sincronizar equipos con grupos de IdP, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". ### Prerrequisitos 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 index a6a2a048bc..abc663192c 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +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-user-provisioning-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index eb18663336..3fa1f48e89 100644 --- 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 @@ -28,7 +28,7 @@ La aplicación de aprovisionamiento en tu IdP se comunica con {% data variables. {% data reusables.scim.supported-idps %} -Cuando configuras el aprovisionamiento de usuarios con un IdP compatible, también puedes asignar o desasignar la aplicación para {% data variables.product.product_name %} a grupos de usuarios. Estos grupos estarán entonces disponibles para que los propietarios de organización y mantenedores de equipo en {% data variables.product.product_location %} los mapeen a los equipos de {% data variables.product.product_name %}. 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)". +Cuando configuras el aprovisionamiento de usuarios con un IdP compatible, también puedes asignar o desasignar la aplicación para {% data variables.product.product_name %} a grupos de usuarios. Estos grupos estarán entonces disponibles para que los propietarios de organización y mantenedores de equipo en {% data variables.product.product_location %} los mapeen a los equipos de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". ### Prerrequisitos 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 index 7e1d074b11..98864a299f 100644 --- 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 @@ -1,8 +1,8 @@ --- 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: true +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-saml.md b/translations/es-ES/content/admin/authentication/using-saml.md index 9ce7104c78..9cfd8f7163 100644 --- a/translations/es-ES/content/admin/authentication/using-saml.md +++ b/translations/es-ES/content/admin/authentication/using-saml.md @@ -1,39 +1,41 @@ --- -title: Using SAML +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 is an XML-based standard for authentication and authorization. {% data variables.product.prodname_ghe_server %} can act as a service provider (SP) with your internal SAML identity provider (IdP).' +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: '*' +topics: + - empresa --- {% data reusables.enterprise_user_management.built-in-authentication %} -### Supported SAML services +### Servicios SAML admitidos {% data reusables.saml.saml-supported-idps %} {% data reusables.saml.saml-single-logout-not-supported %} -### Username considerations with SAML +### Consideraciones sobre el nombre de usuario con SAML -Each {% data variables.product.prodname_ghe_server %} username is determined by one of the following assertions in the SAML response, ordered by priority: +Cada nombre de usuario {% data variables.product.prodname_ghe_server %} lo determina una de las siguientes aserciones en la respuesta SAML, ordenadas por prioridad: -- The custom username attribute, if defined and present -- An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` assertion, if present -- An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` assertion, if present -- The `NameID` element +- 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`. -The `NameID` element is required even if other attributes are present. +Se requiere el elemento `NameID`, incluso si hay otros atributos. -A mapping is created between the `NameID` and the {% data variables.product.prodname_ghe_server %} username, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +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 %} -**Note**: If the `NameID` for a user does change on the IdP, the user will see an error message when they try to sign in to your {% data variables.product.prodname_ghe_server %} instance. {% if currentVersion ver_gt "enterprise-server@2.21" %}To restore the user's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](#updating-a-users-saml-nameid)."{% else %} For more information, see "[Error: 'Another user already owns the account'](#error-another-user-already-owns-the-account)."{% endif %} +**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 %} @@ -44,88 +46,75 @@ A mapping is created between the `NameID` and the {% data variables.product.prod {% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.external_auth_disables_2fa %} -### SAML metadata +### Metadatos SAML -Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. +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`. -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. +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`. -### SAML attributes +### Atributos de SAML -These attributes are available. You can change the attribute names in the [management console](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), with the exception of the `administrator` attribute. +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`. -| Default attribute name | Type | Description | -|-----------------|----------|-------------| -| `NameID` | Required | A persistent user identifier. Any persistent name identifier format may be used. The `NameID` element will be used for a {% data variables.product.prodname_ghe_server %} username unless one of the alternative assertions is provided. | -| `administrator` | Optional | When the value is 'true', the user will automatically be promoted as an administrator. Any other value or a non-existent value will demote the user to a normal user account. | -| `username` | Optional | The {% data variables.product.prodname_ghe_server %} username. | -| `full_name` | Optional | The name of the user displayed on their profile page. Users may change their names after provisioning. | -| `emails` | Optional | The email addresses for the user. More than one can be specified. | -| `public_keys` | Optional | The public SSH keys for the user. More than one can be specified. | -| `gpg_keys` | Optional | The GPG keys for the user. More than one can be specified. | +| 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. | -### Configuring SAML settings +### 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. Select **SAML**. -![SAML authentication](/assets/images/enterprise/management-console/auth-select-saml.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select SAML built-in authentication checkbox](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -5. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP. -![SAML idP SSO](/assets/images/enterprise/management-console/saml-idp-sso.png) +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 %} - **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}. + **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. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.product.product_location %}. -![SAML disable admin config](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) -6. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.product.product_location %} to use internal nameservers](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). -![SAML authentication](/assets/images/enterprise/management-console/saml-single-sign-url.png) -7. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.product.product_location %}. -![SAML issuer](/assets/images/enterprise/management-console/saml-issuer.png) -8. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.product.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu. -![SAML method](/assets/images/enterprise/management-console/saml-method.png) -9. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP. -![SAML authentication](/assets/images/enterprise/management-console/saml-verification-cert.png) -10. Modify the SAML attribute names to match your IdP if needed, or accept the default names. - ![SAML attribute names](/assets/images/enterprise/management-console/saml-attributes.png) +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 inhabilitar administrador de 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" %} -### Updating a user's SAML `NameID` +### Revocar acceso a {{ site.data.variables.product.product_location_enterprise }} {% data reusables.enterprise_site_admin_settings.access-settings %} -2. In the left sidebar, click **All users**. - !["All users" sidebar item in site administrator settings](/assets/images/enterprise/site-admin-settings/all-users.png) -3. In the list of users, click the username you'd like to update the `NameID` mapping for. - ![Username in list of instance user accounts](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) +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. To the right of "Update SAML NameID", click **Edit** . - !["Edit" button under "SAML authentication" and to the right of "Update SAML NameID"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) -6. In the "NameID" field, type the new `NameID` for the user. - !["NameID" field in modal dialog with NameID typed](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) -7. Click **Update NameID**. - !["Update NameID" button under updated NameID value within modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) +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 %} -### Revoking access to {% data variables.product.product_location %} +### Revocar acceso a {% data variables.product.product_location %} -If you remove a user from your identity provider, you must also manually suspend them. Otherwise, they'll continue to be able to authenticate using access tokens or SSH keys. For more information, see "[Suspending and unsuspending users](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". +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)". -### Response message requirements +### Requisitos para los mensajes de respuesta -The response message must fulfill the following requirements: +El mensaje de respuesta debe cumplir con los siguientes requisitos: -- The `` element must be provided on the root response document and match the ACS URL only when the root response document is signed. If the assertion is signed, it will be ignored. -- The `` element must always be provided as part of the `` element. It must match the `EntityId` for {% data variables.product.prodname_ghe_server %}. This is the URL to the {% data variables.product.prodname_ghe_server %} instance, such as `https://ghe.corp.example.com`. -- Each assertion in the response **must** be protected by a digital signature. This can be accomplished by signing each individual `` element or by signing the `` element. -- A `` element must be provided as part of the `` element. Any persistent name identifier format may be used. -- The `Recipient` attribute must be present and set to the ACS URL. For example: +- 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 @@ -145,50 +134,50 @@ The response message must fulfill the following requirements: ``` -### Troubleshooting SAML authentication +### Autenticación SAML -{% data variables.product.prodname_ghe_server %} logs error messages for failed SAML authentication in the authentication log at _/var/log/github/auth.log_. For more information about SAML response requirements, see "[Response message requirements](#response-message-requirements)." +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" -When a user signs in to {% data variables.product.prodname_ghe_server %} for the first time with SAML authentication, {% data variables.product.prodname_ghe_server %} creates a user account on the instance and maps the SAML `NameID` to 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. -When the user signs in again, {% data variables.product.prodname_ghe_server %} compares the account's `NameID` mapping to the IdP's response. If the `NameID` in the IdP's response no longer matches the `NameID` that {% data variables.product.prodname_ghe_server %} expects for the user, the sign-in will fail. The user will see the following message. +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. -The message typically indicates that the person's username or email address has changed on the IdP. {% if currentVersion ver_gt "enterprise-server@2.21" %}Ensure that the `NameID` mapping for the user account on {% data variables.product.prodname_ghe_server %} matches the user's `NameID` on your IdP. For more information, see "[Updating a user's SAML `NameID`](#updating-a-users-saml-nameid)."{% else %}For help updating the `NameID` mapping, contact {% data variables.contact.contact_ent_support %}.{% endif %} +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 %} -#### Error: Recipient in SAML response was blank or not valid +#### 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: -If the `Recipient` does not match the ACS URL for your {% data variables.product.prodname_ghe_server %} instance, one of the following two error messages will appear in the authentication log when a user attempts to authenticate. +Si el `Recipient` no coincide con la URL ACS, se presentará el siguiente mensaje de error en el registro de autenticación: ``` -Recipient in the SAML response must not be blank. +El destinatario en la respuesta SAML no debe estar en blanco. ``` ``` -Recipient in the SAML response was not valid. +El destinatario en la respuesta SAML no era válido. ``` -Ensure that you set the value for `Recipient` on your IdP to the full ACS URL for your {% data variables.product.prodname_ghe_server %} instance. For example, `https://ghe.corp.example.com/saml/consume`. +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" -If your IdP does not sign the SAML response, or the signature does not match the contents, the following error message will appear in the authentication log. +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. ``` -Ensure that you configure signed assertions for the {% data variables.product.prodname_ghe_server %} application on your IdP. +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" -If the IdP's response has a missing or incorrect value for `Audience`, the following error message will appear in the authentication log. +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 -Audience is invalid. Audience attribute does not match https://YOUR-INSTANCE-URL +La audiencia es no válida. Audience attribute does not match https://YOUR-INSTANCE-URL ``` -Ensure that you set the value for `Audience` on your IdP to the `EntityId` for your {% data variables.product.prodname_ghe_server %} instance, which is the full URL to your {% data variables.product.prodname_ghe_server %} instance. For example, `https://ghe.corp.example.com`. +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/configuring-advanced-security-features.md b/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md index 1945d854df..8dfd2acc91 100644 --- a/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md +++ b/translations/es-ES/content/admin/configuration/configuring-advanced-security-features.md @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero redirect_from: - /enterprise/admin/configuration/configuring-advanced-security-features versions: diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings.md b/translations/es-ES/content/admin/configuration/configuring-network-settings.md index 1d7ce98c89..001e1d59a5 100644 --- a/translations/es-ES/content/admin/configuration/configuring-network-settings.md +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings.md @@ -8,7 +8,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' topics: diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md index c65313db32..ce1cc2985b 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise.md @@ -8,7 +8,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' github-ae: '*' 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 index 2249117b2c..169b14e3a7 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +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/ 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 index 78edb7f357..f5988fc2e3 100644 --- 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 @@ -13,7 +13,7 @@ Predeterminadamente, los usuarios autorizados pueden acceder a tu empresa desde {% 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)". +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](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)". Predeterminadamente, las reglas del grupo de seguridad de redes (NSG) de Azure dejan todo el tráfico entrante abierto en los puertos 22, 80, 443 y 25. Los propietarios de las empresas pueden contactar a {% data variables.contact.github_support %} para configurar las restricciones de acceso para tu instancia. diff --git a/translations/es-ES/content/admin/configuration/site-admin-dashboard.md b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md index 6e24da8a36..aab4eb2f84 100644 --- a/translations/es-ES/content/admin/configuration/site-admin-dashboard.md +++ b/translations/es-ES/content/admin/configuration/site-admin-dashboard.md @@ -1,5 +1,5 @@ --- -title: Site admin dashboard +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/ @@ -7,199 +7,200 @@ redirect_from: - /enterprise/admin/configuration/site-admin-dashboard versions: enterprise-server: '*' +topics: + - empresa --- -To access the dashboard, in the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}. -![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +Para acceder al tablero, en la esquina superior derecha de cualquier página, haz clic en {% octicon "rocket" aria-label="The rocket ship" %}. ![Icono de cohete para acceder a la configuración de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% if currentVersion ver_gt "enterprise-server@2.21" %} -### Search +### Buscar -Refer to this section of the site admin dashboard to search for users and repositories, and to query the [audit log](#audit-log). +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 %} -### License info & search +### Información de la licencia & buscar -Refer to this section of the site admin dashboard to check your current {% data variables.product.prodname_enterprise %} license; to search for users and repositories; and to query the [audit log](#audit-log). +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 %} -Here you can launch the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL. +Aquí puedes iniciar la {% data variables.enterprise.management_console %} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL. -### Explore +### Explorar -Data for GitHub's [trending page][] is calculated into daily, weekly, and monthly time spans for both repositories and developers. You can see when this data was last cached and queue up new trending calculation jobs from the **Explore** section. +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)**. - [trending page]: https://github.com/blog/1585-explore-what-is-trending-on-github +### Registro de auditoría -### Audit log +{% data variables.product.prodname_enterprise %} mantiene un registro continuo de las acciones auditadas que puedes consultar. -{% data variables.product.prodname_enterprise %} keeps a running log of audited actions that you can query. +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)." -By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log](/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)". -For more information on audit logging in general, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)." For a full list of audited actions, see "[Audited actions](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)." +### Informes -### Reports +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. -If you need to get information on the users, organizations, and repositories in {% data variables.product.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories. +Específicamente, puedes descargar informes CSV que enumeren a -Specifically, you can download CSV reports that list +- 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 -- all users -- all users who have been active within the last month -- all users who have been inactive for one month or more -- all users who have been suspended -- all organizations -- all repositories +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)". -You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a personal access token with the `site_admin` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." - -For example, here is how you would download the "all users" report using cURL: +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 ``` -To access the other reports programmatically, replace `all_users` with `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, or `all_repositories`. +Para acceder a otros informes mediante programación, reemplaza `all_users` con `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, o `all_repositories`. {% note %} -**Note:** The initial `curl` request will return a 202 HTTP response if there are no cached reports available; a report will be generated in the background. You can send a second request to download the report. You can use a password or an OAuth token with the `site_admin` scope in place of a password. +**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 %} -#### User reports +#### Informes del usuario -Key | Description ------------------:| ------------------------------------------------------------ -`created_at` | When the user account was created (as an ISO 8601 timestamp) -`id` | Account ID for the user or organization -`login` | Account's login name -`email` | Account's primary email address -`role` | Whether the account is an admin or an ordinary user -`suspended?` | Whether the account has been suspended -`last_logged_ip` | Most recent IP address to log into the account -`repos` | Number of repositories owned by the account -`ssh_keys` | Number of SSH keys registered to the account -`org_memberships` | Number of organizations to which the account belongs -`dormant?` | Whether the account is dormant -`last_active` | When the account was last active (as an ISO 8601 timestamp) -`raw_login` | Raw login information (in JSON format) -`2fa_enabled?` | Whether the user has enabled two-factor authentication +| 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 | +| `correo electrónico` | Dirección principal de correo electrónico de la cuenta | +| `rol` | 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 | -#### Organization reports +#### Informes de la organización -Key | Description ---------------:| ------------------------------------ -`id` | Organization ID -`created_at` | When the organization was created -`login` | Organization's login name -`email` | Organization's primary email address -`owners` | Number of organization owners -`members` | Number of organization members -`teams` | Number of organization teams -`repos` | Number of organization repositories -`2fa_required?`| Whether the organization requires two-factor authentication +| 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 | +| `correo electrónico` | 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 | -#### Repository reports +#### Informes del repositorio -Key | Description ----------------:| ------------------------------------------------------------ -`created_at` | When the repository was created -`owner_id` | ID of the repository's owner -`owner_type` | Whether the repository is owned by a user or an organization -`owner_name` | Name of the repository's owner -`id` | Repository ID -`name` | Repository name -`visibility` | Whether the repository is public or private -`readable_size` | Repository's size in a human-readable format -`raw_size` | Repository's size as a number -`collaborators` | Number of repository collaborators -`fork?` | Whether the repository is a fork -`deleted?` | Whether the repository has been deleted +| 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 | +| `visibilidad` | 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 | -### Indexing +### Indexar -GitHub's [code search][] features are powered by [ElasticSearch][]. This section of the site admin dashboard shows you the current status of your ElasticSearch cluster and provides you with several tools to control the behavior of searching and indexing. These tools are split into the following three categories. +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. - [Code Search]: https://github.com/blog/1381-a-whole-new-code-search - [ElasticSearch]: http://www.elasticsearch.org/ +#### Búsqueda de código -#### Code search +Esto te permite habilitar o deshabilitar tanto las operaciones de búsqueda como de indexación en el código fuente. -This allows you to enable or disable both search and index operations on source code. +#### Reparación del índice de búsqueda de código -#### Code search index repair +Esto controla cómo se repara el índice de búsqueda de código. Puedes -This controls how the code search index is repaired. You can +- 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 -- enable or disable index repair jobs -- start a new index repair job -- reset all index repair state +{% 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 -{% data variables.product.prodname_enterprise %} uses repair jobs to reconcile the state of the search index with data stored in a database (issues, pull requests, repositories, and users) and data stored in Git repositories (source code). This happens when +- se crea un nuevo índice de búsqueda; +- faltan datos que se deben reponer; o +- los datos de búsqueda antiguos deben ser actualizados. -- a new search index is created; -- missing data needs to be backfilled; or -- old search data needs to be updated. +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. -In other words, repair jobs are started as needed and run in the background—they are not scheduled by site admins in any way. +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. -Furthermore, repair jobs use a "repair offset" for parallelization. This is an offset into the database table for the record being reconciled. Multiple background jobs can synchronize work based on this offset. +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. -A progress bar shows the current status of a repair job across all of its background workers. It is the percentage difference of the repair offset with the highest record ID in the database. Don't worry about the value shown in the progress bar after a repair job has completed: because it shows the difference between the repair offset and the highest record ID in the database, it will decrease as more repositories are added to {% data variables.product.product_location %} even though those repositories are actually indexed. +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. -You can start a new code-search index repair job at any time. It will use a single CPU as it reconciles the search index with database and Git repository data. To minimize the effects this will have on I/O performance and reduce the chances of operations timing out, try to run a repair job during off-peak hours first. Monitor your system's load averages and CPU usage with a utility like `top`; if you don't notice any significant changes, it should be safe to run an index repair job during peak hours, as well. +#### Reparación de índice de propuestas -#### Issues index repair +Esto controla de qué manera se repara el [índice de propuestas][]. Puedes -This controls how the [Issues][] index is repaired. You can - - [Issues]: https://github.com/blog/831-issues-2-0-the-next-generation - -- enable or disable index repair jobs -- start a new index repair job -- reset all index repair state +- 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" %} -### Enterprise overview +### Todos los usuarios -Refer to this section of the site admin dashboard to manage organizations, people, policies, and settings. +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 %} -### Repositories +### Repositorios -This is a list of the repositories on {% data variables.product.product_location %}. You can click on a repository name and access functions for administering the repository. +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. -- [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) -- [Configuring {% 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) -- [Archiving and unarchiving repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/) +- [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/) -### All users +### Todos los usuarios -Here you can see all of the users on {% data variables.product.product_location %}—, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +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). -### Site admins +### Administrador del sitio -Here you can see all of the administrators on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +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). -### Dormant users +### Usuarios inactivos -Here you can see and [suspend](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: +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: -- Has existed for longer than the dormancy threshold that's set for {% data variables.product.product_location %}. -- Has not generated any activity within that time period. -- Is not a site administrator. +- 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 %} For more information, see "[Managing dormant users](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)." +{% 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)." -### Suspended users +### Usuarios suspendidos -Here you can see all of the users who have been suspended on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +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/enterprise-management/configuring-clustering.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md index cbc19ad7dc..740633a9dc 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering.md @@ -6,7 +6,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' topics: 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 index dc2cd45cf1..ccc05299e7 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability.md @@ -7,7 +7,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' topics: 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 index 00638ec3d9..21505098a7 100644 --- 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 @@ -1,5 +1,5 @@ --- -title: Migrating from GitHub Enterprise 11.10.x to 2.1.23 +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/ @@ -9,88 +9,85 @@ redirect_from: - /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: 'To migrate from {% data variables.product.prodname_enterprise %} 11.10.x to 2.1.23, you''ll need to set up a new appliance instance and migrate data from the previous instance.' +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: '*' +topics: + - empresa --- -Migrations from {% data variables.product.prodname_enterprise %} 11.10.348 and later are supported. Migrating from {% data variables.product.prodname_enterprise %} 11.10.348 and earlier is not supported. You must first upgrade to 11.10.348 in several upgrades. For more information, see the 11.10.348 upgrading procedure, "[Upgrading to the latest release](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)." +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/)." -To upgrade to the latest version of {% data variables.product.prodname_enterprise %}, you must first migrate to {% data variables.product.prodname_ghe_server %} 2.1, then you can follow the normal upgrade process. For more information, see "[Upgrading {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)". +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/)". -### Prepare for the migration +### Prepárate para la migración -1. Review the Provisioning and Installation guide and check that all prerequisites needed to provision and configure {% data variables.product.prodname_enterprise %} 2.1.23 in your environment are met. For more information, see "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)." -2. Verify that the current instance is running a supported upgrade version. -3. Set up the latest version of the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). - - If you have already configured scheduled backups using {% data variables.product.prodname_enterprise_backup_utilities %}, make sure you have updated to the latest version. - - If you are not currently running scheduled backups, set up {% data variables.product.prodname_enterprise_backup_utilities %}. -4. Take an initial full backup snapshot of the current instance using the `ghe-backup` command. If you have already configured scheduled backups for your current instance, you don't need to take a snapshot of your instance. +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 %} - **Tip:** You can leave the instance online and in active use during the snapshot. You'll take another snapshot during the maintenance portion of the migration. Since backups are incremental, this initial snapshot reduces the amount of data transferred in the final snapshot, which may shorten the maintenance window. + **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. Determine the method for switching user network traffic to the new instance. After you've migrated, all HTTP and Git network traffic directs to the new instance. - - **DNS** - We recommend this method for all environments, as it's simple and works well even when migrating from one datacenter to another. Before starting migration, reduce the existing DNS record's TTL to five minutes or less and allow the change to propagate. Once the migration is complete, update the DNS record(s) to point to the IP address of the new instance. - - **IP address assignment** - This method is only available on VMware to VMware migration and is not recommended unless the DNS method is unavailable. Before starting the migration, you'll need to shut down the old instance and assign its IP address to the new instance. -6. Schedule a maintenance window. The maintenance window should include enough time to transfer data from the backup host to the new instance and will vary based on the size of the backup snapshot and available network bandwidth. During this time your current instance will be unavailable and in maintenance mode while you migrate to the new instance. +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. -### Perform the migration +### Realiza la migración -1. Provision a new {% data variables.product.prodname_enterprise %} 2.1 instance. For more information, see the "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" guide for your target platform. -2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license. -3. Set an admin password. -5. Click **Migrate**. -![Choosing install type](/assets/images/enterprise/migration/migration-choose-install-type.png) -6. Paste your backup host access SSH key into "Add new SSH key". -![Authorizing backup](/assets/images/enterprise/migration/migration-authorize-backup-host.png) -7. Click **Add key** and then click **Continue**. -8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance. -![Starting a migration](/assets/images/enterprise/migration/migration-restore-start.png) -9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +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 %} - **Note:** The instance will be unavailable for normal use from this point forward. + **Nota:** la instancia no estará disponible para el uso normal desde este punto en adelante. {% endnote %} -10. On the backup host, run the `ghe-backup` command to take a final backup snapshot. This ensures that all data from the old instance is captured. -11. On the backup host, run the `ghe-restore` command you copied on the new instance's restore status screen to restore the latest snapshot. +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. - RSA key fingerprint is fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1. - Are you sure you want to continue connecting (yes/no)? yes + 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 ... - Restoring GitHub Pages ... - Restoring asset attachments ... - Restoring hook deliveries ... - Restoring MySQL database ... - Restoring Redis database ... - Restoring SSH authorized keys ... - Restoring Elasticsearch indices ... - Restoring SSH host keys ... + 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. Return to the new instance's restore status screen to see that the restore completed. -![Restore complete screen](/assets/images/enterprise/migration/restore-complete-screen.png) -13. Click **Continue to settings** to review and adjust the configuration information and settings that were imported from the previous instance. -![Review imported settings](/assets/images/enterprise/migration/migration-status-complete.png) -14. Click **Save settings**. +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/migration-status-complete.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 %} - **Note:** You can use the new instance after you've applied configuration settings and restarted the server. + **Nota:** puedes usar la nueva instancia después de haber aplicado los parámetros de configuración y restaurar el servidor. {% endnote %} -15. Switch user network traffic from the old instance to the new instance using either DNS or IP address assignment. -16. Upgrade to the latest patch release of {{ currentVersion }}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." +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-your-appliance.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md index 87c350a98e..d1deb66d25 100644 --- a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md +++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance.md @@ -6,7 +6,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' topics: 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 index 280297fd04..7e1f477163 100644 --- 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 @@ -6,7 +6,7 @@ redirect_from: - '/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: true +mapTopic: verdadero versions: enterprise-server: '*' topics: 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 index cf73d829ed..646230a28a 100644 --- 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 @@ -37,7 +37,7 @@ Además de todos los beneficios de {% data variables.contact.enterprise_support {% 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.scope-of-support %} {% data reusables.support.contacting-premium-support %} 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 index 3b5aeb122c..99b8591287 100644 --- 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 @@ -35,7 +35,7 @@ Además de todos los beneficios de {% data variables.contact.enterprise_support {% 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.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/es-ES/content/admin/enterprise-support/overview.md b/translations/es-ES/content/admin/enterprise-support/overview.md index 244ba62881..ec3cec52ca 100644 --- a/translations/es-ES/content/admin/enterprise-support/overview.md +++ b/translations/es-ES/content/admin/enterprise-support/overview.md @@ -1,7 +1,7 @@ --- title: Resumen intro: 'Conoce las opciones de soporte disponibles para {% data variables.product.product_name %}.' -mapTopic: true +mapTopic: verdadero redirect_from: - /enterprise/admin/enterprise-support/overview versions: 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 index afced4bfce..96b15f06e8 100644 --- 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 @@ -4,7 +4,7 @@ intro: 'Puedes contactar a {% data variables.contact.enterprise_support %} para redirect_from: - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support/ - /enterprise/admin/enterprise-support/receiving-help-from-github-support -mapTopic: true +mapTopic: verdadero versions: enterprise-server: '*' github-ae: '*' 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 index efd1136c37..f556417fc1 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero versions: enterprise-server: '>=3.0' topics: 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 index b35ff099ca..7aa5a5c9ab 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero versions: enterprise-server: '>=2.22' topics: diff --git a/translations/es-ES/content/admin/github-actions/index.md b/translations/es-ES/content/admin/github-actions/index.md index 6e13443e8c..688b482dc5 100644 --- a/translations/es-ES/content/admin/github-actions/index.md +++ b/translations/es-ES/content/admin/github-actions/index.md @@ -32,6 +32,7 @@ topics: {% 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 /using-the-latest-version-of-the-official-bundled-actions %} {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} {% topic_link_in_list /advanced-configuration-and-troubleshooting %} 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 index 6771a1e6e5..89bba24d7e 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom versions: 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 index 16e86bb53b..1c05f1191c 100644 --- 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 @@ -28,8 +28,21 @@ La herramienta `actions-sync` solo puede descargar acciones de {% data variables ### 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)". +* 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](/organizations/collaborating-with-groups-in-organizations/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)". +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. + + {% note %} + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + + {% endnote %} + + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." + + ```shell + ghe-org-admin-promote -u USERNAME -o actions + ``` ### Ejemplo: Utilizar la herramienta `actions-sync` diff --git a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae.md b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae.md index 2e4c68a163..eeee07e233 100644 --- a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae.md +++ b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae.md @@ -1,7 +1,7 @@ --- title: Utilizar GitHub Actions en GitHub AE intro: 'Aprende cómo configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_managed %}.' -mapTopic: true +mapTopic: verdadero versions: github-ae: '*' --- diff --git a/translations/es-ES/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/es-ES/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md new file mode 100644 index 0000000000..b7fd1d8126 --- /dev/null +++ b/translations/es-ES/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md @@ -0,0 +1,45 @@ +--- +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '>=2.22' +topics: + - empresa +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server). + +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}. + +Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}: + +- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}. +- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions. + +These options are described in more detail in the following sections. + +### Using actions-sync to update a bundled action + +To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." + +### Using actions from {% data variables.product.prodname_dotcom_the_website %} + +{% data reusables.github-actions.actions-github-connect-requirement %} + +Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file. + +### Using the latest version by removing the specific action's tag + +{% data reusables.github-actions.actions-github-connect-requirement %} + +If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)." + +For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}: + +1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository. +1. Create a workflow that uses `actions/setup-python` with the `v2` tag. + +When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}. 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 index ebe656024f..63896b2d49 100644 --- 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 @@ -1,6 +1,6 @@ --- 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.' +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 2019.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v @@ -13,7 +13,7 @@ topics: ### Prerrequisitos - {% data reusables.enterprise_installation.software-license %} -- Debes tener Windows Server 2008 a través de Windows Server 2016, que admita Hyper-V. +- Debes tener Windows Server 2008 a través de Windows Server 2019, 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 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 index ddd41d3f38..cb285fa5ba 100644 --- 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 @@ -7,7 +7,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' topics: diff --git a/translations/es-ES/content/admin/overview/github-ae-release-notes.md b/translations/es-ES/content/admin/overview/github-ae-release-notes.md index 349f41d1a9..8a5f8a6aaf 100644 --- a/translations/es-ES/content/admin/overview/github-ae-release-notes.md +++ b/translations/es-ES/content/admin/overview/github-ae-release-notes.md @@ -29,7 +29,7 @@ Durante este beta, las características de {% data variables.product.prodname_ad #### Administra equipos desde tu proveedor de identidad (IdP) -Los clientes que utilizan SCIM (Sistema para la Adminsitración de Identidades entre Dominios) ahora pueden sincronizar los grupos de seguridad en Azure Active Directory con los equipos de {% data variables.product.company_short %}. Una vez que un equipo se haya enlazado con un grupo de seguridad, la membercía se actualizará automáticamente en {% data variables.product.product_name %} cuando se agregue o elimine a un suuario de su grupo de seguridad asignado. 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)". +Los clientes que utilizan SCIM (Sistema para la Adminsitración de Identidades entre Dominios) ahora pueden sincronizar los grupos de seguridad en Azure Active Directory con los equipos de {% data variables.product.company_short %}. Una vez que un equipo se haya enlazado con un grupo de seguridad, la membercía se actualizará automáticamente en {% data variables.product.product_name %} cuando se agregue o elimine a un suuario de su grupo de seguridad asignado. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". #### Beta de listas de IP permitidas @@ -37,7 +37,7 @@ Los propietarios de empresas y organizaciones ahora pueden utilizar las listas d Esta funcionalidad se proporciona adicionalmente a la capacidad de solicitar cambios en los grupos de seguridad en redes que filtren el tráfico del inquilino de {% data variables.product.product_name %} integralmente. -Para obtener más información, consulta las secciones "[Restringir el tráfico de red a tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)" y "[Administrar direcciones IP permitidas en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)". +Para obtener más información, consulta las secciones "[Restringir el tráfico de red a tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)" y "[Administrar direcciones IP permitidas en tu organización](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)". #### Fusión automática de solicitudes de cambio @@ -47,8 +47,8 @@ Con la fusión automática, las solicitudes de cambio pueden configurarse para q #### Cambios del desarrollador -- [Los propietarios de organización ahora pueden inhabilitar la publicación](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization) de los sitios de {% data variables.product.prodname_pages %} desde los repositorios en la organización. Esto no dejará de publicar los sitios existentes. -- Los repositorios que utilicen {% data variables.product.prodname_pages %} ahora pueden [crear y desplegar desde cualquier rama](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). +- [Los propietarios de organización ahora pueden inhabilitar la publicación](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) de los sitios de {% data variables.product.prodname_pages %} desde los repositorios en la organización. Esto no dejará de publicar los sitios existentes. +- Los repositorios que utilicen {% data variables.product.prodname_pages %} ahora pueden [crear y desplegar desde cualquier rama](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - Cuando escribes una propuesta o solicitud de cambios, la sintaxis de lista para las viñetas, números y tareas ahora se completará auotmáticamente cuando presiones `return` o `enter`. - Ahora puedes borrar un directorio de un repositorio desde la página de repositorio. Cuando navegues a un directorio, un botón de kebab nuevo junto al botón de "Agergar archivo" te da la opción de borrar el directorio. - Ahora es más fácil y rápido [referenciar las propuestas o solicitudes de cambio](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests) con una búsqueda a través de varias palabras después del "#". @@ -65,7 +65,7 @@ Con la fusión automática, las solicitudes de cambio pueden configurarse para q ##### Renombrar la rama predeterminada -Los propietarios de empresas y organizaciones ahora pueden configurar el nombre de la rama predeterminada para los repositorios nuevos. Los propietarios de empresas también pueden requerir su elección de nombre para las ramas predeterminadas en todas las organizaciones o permitir que cada organización escoja el suyo propio. Para obtener más información, consulta las secciones "[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)" y "[Administrar el nombre de la rama predeterminada para los repositorios de tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)". +Los propietarios de empresas y organizaciones ahora pueden configurar el nombre de la rama predeterminada para los repositorios nuevos. Los propietarios de empresas también pueden requerir su elección de nombre para las ramas predeterminadas en todas las organizaciones o permitir que cada organización escoja el suyo propio. Para obtener más información, consulta las secciones "[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)" y "[Administrar el nombre de la rama predeterminada para los repositorios de tu organización](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)". Estas configuraciones no afectarán a los repositorios existentes y los nombres de sus ramas predeterminadas no cambiarán. diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md index 5923a3861b..f9b7382874 100644 --- a/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md @@ -4,7 +4,7 @@ intro: 'Los propietarios de empresa pueden requerir políticas para adminsitrar product: '{% data reusables.gated-features.ghas %}' versions: enterprise-server: '>=3.1' - github-ae: '*' + github-ae: 'next' --- ### Acerca de {% data variables.product.prodname_GH_advanced_security %} 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 index 5913702849..8d4a496e26 100644 --- 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 @@ -1,6 +1,6 @@ --- title: Requerir políticas para tu empresa -mapTopic: true +mapTopic: verdadero redirect_from: - /enterprise/admin/policies/enforcing-policies-for-your-enterprise versions: 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 index ad4df2506d..cbb16cfc6a 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /enterprise/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy - /enterprise/admin/policies/enforcing-policy-with-pre-receive-hooks diff --git a/translations/es-ES/content/admin/release-notes.md b/translations/es-ES/content/admin/release-notes.md index a1540a8559..b5aa8c8cfc 100644 --- a/translations/es-ES/content/admin/release-notes.md +++ b/translations/es-ES/content/admin/release-notes.md @@ -1,7 +1,7 @@ --- title: Notas de lanzamiento intro: 'Las notas de lanzamiento para {{ allVersions[currentVersion].versionTitle }}.' -layout: release-notes +layout: notas de lanzamiento versions: enterprise-server: '*' topics: 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 index 0a0074ffd4..11d74319a1 100644 --- 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 @@ -66,17 +66,16 @@ Los mensajes obligatorios tienen varios usos. - Decir a los usuarios cómo obtener ayuda con {% data variables.product.product_location %} - Garantizar que todos los usuarios lean tus condiciones de servicio para utilizar {% data variables.product.product_location %} -{% note %} - -**Note:** After you configure a mandatory message for {% data variables.product.product_location %}, you cannot change or remove the message. - -{% endnote %} - - Si incluyes cajas de verificación con lenguaje de marcado en el mensaje, todas ellas deberán seleccionarse antes de que el usuario pueda descartar el mensaje. Por ejemplo, si incluyes tus condiciones de servicio en el mensaje obligatorio, puede que necesites que cada usuario seleccione una casilla para confirmar que leyó dichas condiciones. Cada vez que un usuario vea un mensaje obligatorio, se crea un evento de bitácora de auditoría. El evento incluye la versión del mensaje que vio el usuario. Para obtener más información, consulta la sección "[Acciones auditadas](/admin/user-management/audited-actions)". +{% note %} + +**Note:** If you change the mandatory message for {% data variables.product.product_location %}, users who have already acknowledged the message will not see the new message. + +{% endnote %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} 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 index 65f4a72d76..4c9c8f9936 100644 --- 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 @@ -6,7 +6,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: enterprise-server: '*' github-ae: '*' 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 index e13e7cf0c2..27b0ba7e61 100644 --- 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 @@ -4,7 +4,7 @@ intro: Puedes administrar la configuración disponible para los administradores redirect_from: - /enterprise/admin/user-management/repositories - /enterprise/admin/user-management/managing-repositories-in-your-enterprise -mapTopic: true +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 index ba90130b9e..d202464ceb 100644 --- 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 @@ -6,7 +6,7 @@ redirect_from: - /enterprise/admin/user-management/basic-account-settings - /enterprise/admin/user-management/user-security - /enterprise/admin/user-management/managing-users-in-your-enterprise -mapTopic: true +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 index 08003c073c..43362d474a 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/ - /enterprise/admin/categories/migrations-and-upgrades/ 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 index 06bb7be7b6..5b4fe1ffe8 100644 --- 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 @@ -1,6 +1,6 @@ --- title: Monitorear la actividad en tu empresa -mapTopic: true +mapTopic: verdadero redirect_from: - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise diff --git a/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md b/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md index 53588f3514..26777d62ae 100644 --- a/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-security/about-secret-scanning.md @@ -45,7 +45,7 @@ Actualmente, {% data variables.product.product_name %} escanea los repositorios El {% data variables.product.prodname_secret_scanning_caps %} se encuentra disponible en todos los repositorios que pertenezcan a la organización como parte de la {% data variables.product.prodname_GH_advanced_security %}. No se encuentra disponible en repositorios que pertenezcan a usuarios individuales. {% endif %} -Si eres un administrador de repositorio o un propietario de organización, puedes habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% if currentVersion == "free-pro-team@latest" %} privados{% endif %} que pertenezcan a las organizaciones. Puedes habilitar el {% data variables.product.prodname_secret_scanning %} para todos tus repositorios, o para todos los repositorios nuevos dentro de tu organización.{% if currentVersion == "free-pro-team@latest" %} El {% data variables.product.prodname_secret_scanning_caps %} mp se encuentra disponible para los repositorios privados que pertenezcan a los usuarios individuales.{% endif %} para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" y "[Administrar la configuración de seguridad y análisis para tu organziación](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". +Si eres un administrador de repositorio o un propietario de organización, puedes habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% if currentVersion == "free-pro-team@latest" %} privados{% endif %} que pertenezcan a las organizaciones. 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." Cuando subes tus confirmaciones a un repositorio{% if currentVersion == "free-pro-team@latest" %} privado{% endif %} que tenga habilitado el {% data variables.product.prodname_secret_scanning %}, {% data variables.product.prodname_dotcom %} escanea el contenido de las confirmaciones para encontrar secretos. diff --git a/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md index 69dbda5182..d61e715e92 100644 --- a/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md +++ b/translations/es-ES/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md @@ -70,4 +70,4 @@ También puedes ignorar alertas individuales de {% data variables.product.prodna ### Leer más -- "[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)" +- "[Administrar la seguridad y la configuración de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md index d0bbcb16bc..9872dfb290 100644 --- a/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md +++ b/translations/es-ES/content/code-security/secure-coding/about-code-scanning.md @@ -1,6 +1,6 @@ --- -title: About code scanning -intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' +title: 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 @@ -10,46 +10,45 @@ versions: enterprise-server: '>=3.0' github-ae: '*' topics: - - security + - seguridad --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About {% data variables.product.prodname_code_scanning %} +### Acerca de {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.about-code-scanning %} -You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. +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. -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](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." +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](/code-security/secure-coding/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 monitorear los resultados del {% data variables.product.prodname_code_scanning %} a lo largo de tus repositorios o de tu organización, puedes utilizar webhooks y la API del {% data variables.product.prodname_code_scanning %}. Para obtener más información sobre los webhooks para el {% data variables.product.prodname_code_scanning %}, consulta la sección [Cargas útiles y eventos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". Para obtener más información sobre las terminales de la API, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)". -To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." +Para iniciar con el {% data variables.product.prodname_code_scanning %}, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". -### About {% data variables.product.prodname_codeql %} +### Acerca de {% data variables.product.prodname_codeql %} -You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +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 %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. +{% data variables.product.prodname_ql %}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. -{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. +Para 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 %} -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in the {% data variables.product.prodname_codeql %} documentation. +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://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) en la documentación de {% data variables.product.prodname_codeql %}. {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### Acerca de la facturación para {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data variables.product.prodname_code_scanning_capc %} 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 %} -### About third-party code scanning tools +### Acerca de las herramientas de escaneo de código de terceros {% data reusables.code-scanning.you-can-upload-third-party-analysis %} @@ -57,9 +56,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### Further reading +### Leer más {% 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 %} +- "[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) on the OASIS Committee website +- [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/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md b/translations/es-ES/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md index 0a80083867..7d0a37a979 100644 --- a/translations/es-ES/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md +++ b/translations/es-ES/content/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors.md @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors diff --git a/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md index 88a106c919..cd83b583b5 100644 --- a/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md +++ b/translations/es-ES/content/code-security/secure-coding/configuring-code-scanning.md @@ -1,8 +1,8 @@ --- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' +title: Configurar 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: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' +permissions: 'Las personas con permisos de escritura en un repositorio pueden configurar {% data variables.product.prodname_code_scanning %} para el mismo.' miniTocMaxHeadingLevel: 4 redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning @@ -11,55 +11,63 @@ versions: enterprise-server: '>=3.0' github-ae: '*' topics: - - security + - seguridad --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### About {% data variables.product.prodname_code_scanning %} configuration +### Acerca de la configuración de {% data variables.product.prodname_code_scanning %} -You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." +Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %}, utilizando las {% data variables.product.prodname_actions %}, o desde tu sistema de integración contínua (IC), si utilizas 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 sobre el {% data variables.product.prodname_codeql_runner %}, consulta la sección "[Ejecutar el {% data variables.product.prodname_code_scanning %} en tu sistema de IC](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)". -This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}. +este artículo se trata de ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %}. -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." +Antes de que puedas configurar el {% data variables.product.prodname_code_scanning %} para un repositorio, debes configurar el {% data variables.product.prodname_code_scanning %} agregando un flujo de trabajo de {% data variables.product.prodname_actions %} a este. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". {% data reusables.code-scanning.edit-workflow %} -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. +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 {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} guarda los archivos de flujo de trabajo en el directorio de _.github/workflows_ de tu repositorio. Puedes encontrar un flujo de trabajo que hayas agregado si buscas su nombre de archivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. 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) -For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +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)." -### Configuring frequency +### Configurar la frecuencia -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +Puedes escanear código con cierta programación o cuando ocurren eventos específicos en un repositorio. -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +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. -#### Scanning on push +#### Escanear cuando se carga información -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +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)". -#### Scanning pull requests +If you scan on push, then the results appear in the **Security** tab for your repository. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +{% note %} -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below. -#### Avoiding unnecessary scans of pull requests +{% endnote %} -You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. +#### 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)". + +If you scan pull requests, then the results appear as alerts in a pull request check. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del escaneo de código en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". + +#### 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: @@ -74,28 +82,28 @@ on: {% note %} -**Notes** +**Notas** -* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." -* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. +* `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 %} -For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." +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)". -#### Scanning on a schedule +#### Escanear de forma pre-programada -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +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 %} -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. +**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 %} -#### Example +#### Ejemplo -The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. +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: @@ -107,16 +115,16 @@ on: - cron: '20 14 * * 1' ``` -This workflow scans: -* Every push to the default branch and the protected branch -* Every pull request to the default branch -* The default branch every Monday at 14:20 UTC +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 cada lunes a las 14:20 UTC -### Specifying an operating system +### Especificar un sistema operativo -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} +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 %} -If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} +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: @@ -125,23 +133,23 @@ jobs: runs-on: [self-hosted, ubuntu-latest] ``` -{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Para 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_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% 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" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}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 %} -### Changing the languages that are analyzed +### Cambiar los lenguajes que se analizan -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages. +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 %} -The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +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 %} -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. +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 en el repositorio cuando se configuró el {% data variables.product.prodname_code_scanning %}. Por ejemplo, si el repositorio inicialmente contenía solo JavaScript cuando se configuró 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: @@ -154,7 +162,7 @@ jobs: language: ['javascript', 'python'] ``` -If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. +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 @@ -162,15 +170,15 @@ If your workflow does not contain a matrix called `language`, then {% data varia languages: cpp, csharp, python ``` {% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies +### Analizar las dependencias de Python -For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: +Para 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`: -- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies. +- 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. -- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete. +- 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. -Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract: +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: @@ -204,11 +212,11 @@ jobs: ``` {% endif %} -### Running additional queries +### Ejecutar consultas adicionales {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. +Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. Si las consultas están en un repositorio privado, utiliza el parámetro `external-repository-token` para especificar un token que tenga acceso a este. {% raw %} ``` yaml @@ -220,13 +228,13 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu ``` {% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +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 %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +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)". -In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. +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. {% raw %} ``` yaml @@ -238,11 +246,11 @@ In the following example, the `+` symbol ensures that the specified additional q ``` {% endraw %} -### Using a custom configuration file +### Utilizar una herramienta de escaneo de código de terceros -As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. +Como alternativa 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. -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. +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 @@ -252,7 +260,7 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp {% data reusables.code-scanning.custom-configuration-file %} -If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository. +El archivo de configuración se ubica en un repositorio privado externo, utiliza el parámetro `external-repository-token` de la acción `init` para especificar un token que tenga acceso al repositorio privado. {% raw %} ```yaml @@ -262,11 +270,11 @@ with: ``` {% endraw %} -The settings in the configuration file are written in YAML format. +Los ajustes en el archivo de configuración se escriben en formato YAML. -#### Specifying additional queries +#### Especificar consultas adicionales -You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file. +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: @@ -275,17 +283,17 @@ queries: - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls ``` -Optionally, you can give each array element a name, as shown in the example configuration files below. +Opcionalmente, puedes otorgar un nombre a cada elemento de la matriz, como se muestra en los siguientes ejemplos de archivos de configuración. -For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. +Para obtener más información acerca de las consultas adicionales, puedes ver la siguiente sección "[Ejecutar consultas adicionales](#running-additional-queries)". -#### Disabling the default queries +#### Inhabilitar las consultas predeterminadas -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +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. -#### Specifying directories to scan +#### Especificar directorios para escanear -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. +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: @@ -297,27 +305,27 @@ paths-ignore: {% note %} -**Note**: +**Nota**: -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* 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 %} -For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +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](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +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. -#### Example configuration files +#### Ejemplos de archivos de configuración {% data reusables.code-scanning.example-configuration-files %} -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages +### 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 %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)." +{% data reusables.code-scanning.autobuild-add-build-steps %} Para obtener más información sobre cómo configurar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} para los lenguajes compilados, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)". -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} +### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}. -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)." +{% 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](/code-security/secure-coding/uploading-a-sarif-file-to-github)". diff --git a/translations/es-ES/content/code-security/secure-coding/index.md b/translations/es-ES/content/code-security/secure-coding/index.md index 3cbadf8abc..7e963535f6 100644 --- a/translations/es-ES/content/code-security/secure-coding/index.md +++ b/translations/es-ES/content/code-security/secure-coding/index.md @@ -1,7 +1,7 @@ --- title: Encontrar errores y vulnerabilidades de seguridad en tu código shortTitle: Programación segura -intro: 'Mantén tu código seguro utilizando el escaneo de secretos para identificar y arreglar vulnerabilidades de seguridad potenciales y otros errores en tu código.' +intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code diff --git a/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md b/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md index 15952a8575..5774e95006 100644 --- a/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md +++ b/translations/es-ES/content/code-security/secure-coding/integrating-with-code-scanning.md @@ -2,7 +2,7 @@ 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: true +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 diff --git a/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md index ee1a8ec1d5..af32f6712d 100644 --- a/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/es-ES/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md @@ -45,7 +45,14 @@ Necesitas permisos de escritura para ver un resumen de todas las alertas de un r {% 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) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} +1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +1. Debajo de "{% data variables.product.prodname_code_scanning_capc %}", da clic en la alerta que quisieras explorar. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Resumen de alertas](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) @@ -57,7 +64,11 @@ Si tienes permisos de escritura para un repositorio, puedes ver las alertas arre 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtrar alertas por rama](/assets/images/help/repository/code-scanning-branch-filter.png) +{% else %} +![Filtrar alertas por rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} @@ -110,11 +121,19 @@ Para descartar o borrar una alerta: 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtrar alertas por regla](/assets/images/help/repository/code-scanning-filter-by-rule.png) +{% else %} + ![Filtrar alertas por regla](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) +{% endif %} 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Abrir una alerta desde la lista de sumario](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) diff --git a/translations/es-ES/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md index d409ca16f7..2f34ffe897 100644 --- a/translations/es-ES/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md @@ -1,9 +1,9 @@ --- -title: Setting up code scanning for a repository -shortTitle: Setting up code scanning -intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +title: Configurar el escaneo de código en un repositorio +shortTitle: Configurar el escaneo de código +intro: 'Puedes configurar el {% data variables.product.prodname_code_scanning %} si agregas un flujo de trabajo a tu repositorio.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +permissions: 'Si tienes permisos de escritura en un repositorio, puedes configurar o ajustar el {% data variables.product.prodname_code_scanning %} en él.' redirect_from: - /github/managing-security-vulnerabilities/configuring-automated-code-scanning - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning @@ -14,112 +14,116 @@ versions: enterprise-server: '>=3.0' github-ae: '*' topics: - - security + - seguridad --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### Options for setting up {% data variables.product.prodname_code_scanning %} +### Opciones para configurar el {% data variables.product.prodname_code_scanning %} -You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to 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 %}](/code-security/secure-coding/about-code-scanning#about-codeql)." +Tú decides cómo generar las alertas del {% data variables.product.prodname_code_scanning %} y qué herramientas utilizar a nivel de 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 del {% data variables.product.prodname_codeql %}](/code-security/secure-coding/about-code-scanning#about-codeql)". {% data reusables.code-scanning.enabling-options %} -### Setting up {% data variables.product.prodname_code_scanning %} using actions +### Configurar el {% data variables.product.prodname_code_scanning %} utilizando acciones -{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}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. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} - !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. - !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} -5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. +3. A la derecha de "alertas del {% data variables.product.prodname_code_scanning_capc %}", haz clic en **Configurar el {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Si falta el {% data variables.product.prodname_code_scanning %}, necesitas pedir al propietario de la organización o adminsitrador del repositorio que habilite la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis en tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" o "[Administrar la configuración de seguridad y análisis en tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} ![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. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Los flujos de trabajo solo se muestran si son relevantes para los lenguajes de programación que se detectan en el repositorio. El {% data variables.product.prodname_codeql_workflow %} siempre se muestra, pero el botón de "Configurar este flujo de trabajo" solo se habilita si el análisis de {% data variables.product.prodname_codeql %} es compatible con los lenguajes presentes en el repositorio.{% endif %} +5. Para personalizar la forma en que el {% data variables.product.prodname_code_scanning %} escanea tu còdigo, edita el flujo de trabajo. - Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. + 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. - For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)." -6. Use the **Start commit** drop-down, and type a commit message. - ![Start commit](/assets/images/help/repository/start-commit-commit-new-file.png) -7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request. - ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) -8. Click **Commit new file** or **Propose new file**. + Para obtener más información, consulta "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/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**. -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. +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 set up of {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once 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. +### Configuración del {% data variables.product.prodname_code_scanning %} por lotes +Puedes configurar el {% data variables.product.prodname_code_scanning %} en muchos repositorios al mismo tiempo utilizando un script. Para encontrar un ejemplo de un script que levanta solicitudes de cambio para agregar un flujo de trabajo de {% data variables.product.prodname_actions %} a varios repositorios, consulta el repositorio [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs). -### Viewing the logging output from {% data variables.product.prodname_code_scanning %} +### Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %} -After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. +Después de configurar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones mientras se ejecutan. {% data reusables.repositories.actions-tab %} - 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. + Veràs una lista que incluye una entrada para ejecutar el flujo de trabajo del {% data variables.product.prodname_code_scanning %}. El texto de la entrada es el título que le diste a tu mensaje de confirmación. - ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) + ![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. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. +1. Da clic en la entrada para el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. -1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. +1. Da clic en el nombre del job situado a la izquierda. Por ejemplo, **Analizar (IDIOMA)**. - ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + ![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. Review the logging output from the actions in this workflow as they run. +1. Revisa la salida de registro de las acciones en este flujo de trabajo conforme se ejecutan. -1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." +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](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". {% note %} -**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. +**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 %}. - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} {% endnote %} -### Understanding the pull request checks +### Entender las verificaciones de la solicitud de cambios -Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. +Cada flujo de trabajo del {% data variables.product.prodname_code_scanning %} que configuras para que se utilice en las solicitudes de cambios siempre tiene por lo menos dos entradas listadas en la sección de verificaciones de una solicitud de cambios. 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. -The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code. +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. - ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) + ![Verificaciones de solicitudes de cambios del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +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". - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) + ![Falta el análisis para el mensaje de confirmación](/assets/images/help/repository/code-scanning-missing-analysis.png) -#### Reasons for the "missing analysis" message +#### Razones para recibir un mensaje de "missing analysis" -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Missing analysis for base commit SHA-HASH" message. +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". -There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: +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: -* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed. +* La solicitud de cambios se levantó contra una rama diferente a la predeterminada y ésta no se ha analizado. - To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. + Para verificar 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. - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Elige una rama del menú desplegable de Rama](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% else %} + ![Elige una rama del menú desplegable de Rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) +{% endif %} - The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. + 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. -* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available. +* 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. - Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. + Espera algunos minutos y luego sube un cambio a la solicitud de extracciòn para reactivar el {% data variables.product.prodname_code_scanning %}. -* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available. +* 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. - Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. + 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 %}. -### Next steps +### Pasos siguientes -After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: +Después de configurar el {% data variables.product.prodname_code_scanning %} y permitir que se completen sus acciones, puedes: -- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." -- View any alerts generated for a pull request submitted after you set up {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -- Set up notifications for completed runs. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." -- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)." -- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)." +- 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](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". +- Ver cualquier alerta que se genere para una solicitud de cambios que se emitió después de que configuraste 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](/code-security/secure-coding/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 %}](/code-security/secure-coding/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 %}](/code-security/secure-coding/configuring-code-scanning)". diff --git a/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md b/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md index e1742e3e4a..cf1dd22706 100644 --- a/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md +++ b/translations/es-ES/content/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system.md @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system diff --git a/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md index e48221569f..95e9903f4e 100644 --- a/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md @@ -17,6 +17,8 @@ Puedes dar crédito a las personas que ayudaron a descubrir, reportar, o arregla 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. +If you believe you should be credited for a security advisory, please contact the person who created the advisory and ask them to edit the advisory to include your credit. Only the creator of the advisory can credit you, so please don't contact GitHub Support about credits for security advisories. + ### Editar una asesoría de seguridad {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md b/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md index 036bafe594..f307164fff 100644 --- a/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md +++ b/translations/es-ES/content/code-security/security-overview/exploring-security-alerts.md @@ -11,7 +11,7 @@ versions: ### About the security overview -You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository)". +You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)." diff --git a/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md index f895440ee6..195f7a6f95 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md @@ -49,9 +49,9 @@ Para encontrar una lista de ecosistemas para las cuales {% data variables.produc {% 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)". +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. 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -Para obtener más información sobre los requisitos de permisos para las acciones que se relacionan con las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Niveles de permiso del repositorio para una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)". +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% 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 %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md index 84c7c63516..1ad7434878 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/about-dependabot-version-updates.md @@ -12,8 +12,6 @@ topics: - repositories --- -{% 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. diff --git a/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md index 3f516de9cb..322d227399 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/about-the-dependency-graph.md @@ -1,6 +1,6 @@ --- -title: About the dependency graph -intro: 'You can use the dependency graph to identify all your project''s dependencies. The dependency graph supports a range of popular package ecosystems.' +title: Acerca del gráfico de dependencias +intro: 'Puedes utilizar la gráfica de dependencias para identificar todas las dependencias de tus proyectos. La gráfica de dependencias es compatible con una variedad de ecosistemas de paquetes populares.' redirect_from: - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph versions: @@ -9,86 +9,87 @@ versions: topics: - repositories --- + -### Dependency graph availability +### Disponibilidad de la gráfica de dependencias -The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} +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 %} -### About the dependency graph +### Acerca del gráfico de dependencias -The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: +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" %}: -- Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} +- 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 %} -When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. +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" %} -When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." +Cuando creas una solicitud de cambios que contenga los cambios de las dependencias que apuntan a la rama predeterminada, {% data variables.product.prodname_dotcom %} utiliza la gráfica de dependencias para agregar revisiones de dependencia a la solicitud 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 "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/about-dependency-review)". {% endif %} -### Dependencies included +### Dependencias que se incluyen -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +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: -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- 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 -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +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" %} -### Dependents included +### Dependientes incluídos -For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} +Para 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 %} -### Using the dependency graph +### Utiizar la gráfica de dependencias -You can use the dependency graph to: +Puedes utilizar la gráfica de dependencias para: -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} -- See information about vulnerable dependencies in pull requests. 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 %} +- 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](/code-security/supply-chain-security/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 %} -### Enabling the dependency graph +### Habilitar la gráfica de dependencias -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Para 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" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if enterpriseServerVersions 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" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} 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 %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +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 %}. -### Supported package ecosystems +### Ecosistemas de paquetes compatibles -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +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 %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| 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`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**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 +### Leer más -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia -- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} +- "[Grá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" %} +- "[Ver la información de tu organización](/organizations/collaborating-with-groups-in-organizations/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/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md index 8ac9ade5c5..3a679e66c7 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md @@ -11,8 +11,6 @@ topics: - repositories --- -{% 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)". @@ -323,7 +321,7 @@ updates: {% 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-dependencies)" y "[Solucionar los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)". +**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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" y "[Solucionar los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)". {% endnote %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md index 248ce653e3..da4e5f4a4b 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md @@ -49,7 +49,7 @@ Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sab Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual (ver a continuación). -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)". +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. 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](/organizations/keeping-your-organization-secure/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)". diff --git a/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md index 182e15babb..37683c705a 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md @@ -1,60 +1,60 @@ --- -title: Configuring notifications for vulnerable dependencies -shortTitle: Configuring notifications -intro: 'Optimize how you receive notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.' +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 %}.' redirect_from: -- /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies + - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies versions: free-pro-team: '*' enterprise-server: '>=3.0' topics: - - security + - seguridad --- -### About notifications for vulnerable dependencies +### Acerca de las notificaciones para las dependencias vulnerables -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. -{% endif %} +{% 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" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% 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](/organizations/keeping-your-organization-secure/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" %} -Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +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" %} -By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %} +Predeterminadamente, si tu administrador de sitio configuró el correo electrónico para las notificaciones de tu empresa, recibirás las {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %} por correo electrónico.{% endif %} -{% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if 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" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if 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 %} -### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} +### 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 %} -You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." +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" %} - ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png) + ![Opciones de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/notifications-v2/dependabot-alerts-options.png) {% else %} - ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png) + ![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. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." +**Nota:** Puedes filtrar las notificaciones de {% data variables.product.company_short %} para mostrar 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 %}. 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 %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %} +{% 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 %} -### How to reduce the noise from notifications for vulnerable dependencies +### Cómo reducir el ruido de las notificaciones para las dependencias vulnerables -If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +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 +### Leer más -- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" -- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)" +- "[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/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/customizing-dependency-updates.md index 9c32bf9ab7..f3a81c8028 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/customizing-dependency-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/customizing-dependency-updates.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% 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: diff --git a/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md index 63b48381e8..423bff04b5 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md @@ -12,8 +12,6 @@ topics: -{% 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)". @@ -117,7 +115,7 @@ updates: interval: "daily" # Overwrite any ignores created using `@dependabot ignore` commands ignore: - # Ignore updates to packages that start 'aws' + # Ignore updates to packages that start with 'aws' # Wildcards match zero or more arbitrary characters - dependency-name: "aws*" # Ignore some updates to the 'express' package diff --git a/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md index 60e24d2ba1..908eb5d581 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md +++ b/translations/es-ES/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md @@ -74,7 +74,7 @@ Para los repositorios públicos, la vista de dependientes muestra cómo otros re 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)". +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. 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -114,7 +114,7 @@ Si un archivo de manifiesto o de bloqueo no se procesa, sus dependencias se omit ### Leer más - "[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 la información de tu organización](/organizations/collaborating-with-groups-in-organizations/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"

diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md index 98c92b032b..e449e248f8 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% 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)". diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md index 1f11d671ff..af6a7d44db 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically.md @@ -1,7 +1,7 @@ --- title: Mantener tus dependencias actualizadas automáticamente intro: 'El {% data variables.product.prodname_dependabot %} puede mantener tus dependencias de repositorio automáticamente.' -mapTopic: true +mapTopic: verdadero redirect_from: - /github/administering-a-repository/keeping-your-dependencies-updated-automatically versions: diff --git a/translations/es-ES/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/es-ES/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md index 1751d68969..b56c408962 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% 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)". diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md index faddc8ab40..5add991a6a 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Acerca de las solicitudes de extracción del {% data variables.product.prodname_dependabot %} {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies.md index 2eb433ac60..8881d2aee3 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies.md @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/updating-your-project-s-dependencies/ - /articles/updating-your-projects-dependencies/ diff --git a/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md index d144a99f1a..5b791c8e14 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md +++ b/translations/es-ES/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md @@ -11,8 +11,6 @@ topics: - seguridad --- -{% data reusables.dependabot.beta-note %} - ### Acerca de los errores del {% data variables.product.prodname_dependabot %} {% data reusables.dependabot.pull-request-introduction %} 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 index 8a67d247e8..ff8247faf3 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /desktop/contributing-to-projects/adding-and-cloning-repositories versions: 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 index 1680ae4e48..1430d50319 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +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 index 2e843a2501..abce8123be 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /desktop/contributing-to-projects/making-changes-in-a-branch versions: 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 index 686b336ac3..068be04af0 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise versions: 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 index 6221d9e1d2..98483f273f 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop versions: 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 index 4a33460c71..71b7006814 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Cómo instalar y autenticarse en GitHub Desktop intro: Instalar GitHub Desktop y conectar tus cuentas de GitHub y GitHub Enterprise. -mapTopic: true +mapTopic: verdadero redirect_from: - /desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop versions: 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 index 9e1f79dc7b..a309a06077 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Resumen intro: Conozca GitHub Desktop y cree rápidamente su primer repositorio. -mapTopic: true +mapTopic: verdadero redirect_from: - /desktop/getting-started-with-github-desktop/overview versions: diff --git a/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md index 1c2e7ddd8e..9607e4468a 100644 --- a/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/authorizing-oauth-apps.md @@ -86,18 +86,18 @@ Intercambia este `code` por un token de acceso: Predeterminadamente, la respuesta toma la siguiente forma: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&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"} + {"access_token":"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} Accept: application/xml bearer repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} #### 3. Utiliza el token de acceso para acceder a la API @@ -207,7 +207,7 @@ Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "user" } @@ -304,3 +304,7 @@ Para crear este vínculo, necesitarás el `client_id` de tus Apps de Oauth, el c {% 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 %} + +### Leer más + +- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-ES/content/developers/apps/building-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps.md index 54c2d0156e..3945898fdd 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps.md +++ b/translations/es-ES/content/developers/apps/building-github-apps.md @@ -1,7 +1,7 @@ --- title: Crear GitHub Apps intro: Puedes crar GitHub Apps para ti mismo o para que los utilicen los demás. Aprende como registrar y configurar permisos y opciones de autenticación para GitHub Apps. -mapTopic: true +mapTopic: verdadero redirect_from: - /apps/building-integrations/setting-up-and-registering-github-apps/ - /apps/building-github-apps diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps.md index a3dc8ade22..2e9ee065f9 100644 --- a/translations/es-ES/content/developers/apps/building-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/building-oauth-apps.md @@ -1,7 +1,7 @@ --- title: Crear Apps de OAuth intro: Puedes crear OAuth Apps para ti mismo o para que las utilicen los demás. Aprende como registrar y configurar permisos y opciones de autenticación para Apps de OAuth. -mapTopic: true +mapTopic: verdadero redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/ - /apps/building-oauth-apps 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 index a80cc36d98..5896c535d2 100644 --- 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 @@ -54,16 +54,18 @@ Se redirigirá al creador de la app a una página de GitHub en donde encontrará ##### 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` | `objeto` | 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. | - | `descripción` | `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` | `objeto` | 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`). | + | 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` | `objeto` | La configuración del webhook de la GitHub App. | + | `redirect_url` | `secuencia` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `conjunto de secuencias` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %} + | `callback_url` | `secuencia` | A full URL to redirect to after someone authorizes an installation.{% endif %} + | `descripción` | `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` | `objeto` | 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: @@ -96,7 +98,10 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -111,10 +116,11 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s }) ``` + 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. ```html -
+ Create a GitHub App Manifest:
@@ -127,7 +133,10 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -147,11 +156,11 @@ Este ejemplo utiliza un formato en una página web con un botón que activa la s 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 + https://example.com/redirect?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 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 #### 3. Intercambias el código temporal para recuperar la configuración de la app 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 index a7c280c90d..62d6461269 100644 --- 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 @@ -22,9 +22,15 @@ El creador de la app puede editar los valores preseleccionados desde la página 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 - ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} +``` +{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite +``` +{% else %} +``` +{% 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 +``` +{% endif %} La lista completa de parámetros de consulta, permisos y eventos disponibles se lista en las secciones siguientes. @@ -34,8 +40,9 @@ La lista completa de parámetros de consulta, permisos y eventos disponibles se | -------------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `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. | | `descripción` | `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. | + | `url` | `secuencia` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `conjunto de secuencias` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} + | `callback_url` | `secuencia` | La URL completa a la cual se redirigirá después de que alguien autorice la instalación. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} | `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. | 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 index c9ee80a515..14e583a8f3 100644 --- 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 @@ -845,7 +845,7 @@ Aquí te presentamos algunos problemas comunes y sus soluciones sugeridas. Si te **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.: + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@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`. 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 index 82bb6e0d64..09908b1a09 100644 --- a/translations/es-ES/content/developers/apps/getting-started-with-apps.md +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps.md @@ -1,7 +1,7 @@ --- title: Comenzar con las apps intro: Aprende cómo crear apps y como configurar tu ambiente de desarrollo. -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/es-ES/content/developers/apps/guides.md b/translations/es-ES/content/developers/apps/guides.md index 5c152c8f87..b84a1eda0c 100644 --- a/translations/es-ES/content/developers/apps/guides.md +++ b/translations/es-ES/content/developers/apps/guides.md @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /apps/quickstart-guides versions: 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 index 4f45e08969..97ed2c28f1 100644 --- 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 @@ -94,9 +94,9 @@ Predeterminadamente, la respuesta toma la siguiente forma. Los parámetros de re ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -106,7 +106,7 @@ Predeterminadamente, la respuesta toma la siguiente forma. Los parámetros de re Predeterminadamente, la respuesta toma la siguiente forma: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer {% endif %} @@ -934,3 +934,11 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando * [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Leer más + +- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/es-ES/content/developers/apps/managing-github-apps.md b/translations/es-ES/content/developers/apps/managing-github-apps.md index d8aeb02638..b792b78f2c 100644 --- a/translations/es-ES/content/developers/apps/managing-github-apps.md +++ b/translations/es-ES/content/developers/apps/managing-github-apps.md @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /apps/building-integrations/managing-github-apps/ - /apps/managing-github-apps diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps.md b/translations/es-ES/content/developers/apps/managing-oauth-apps.md index df4808e144..f4af7f3d8a 100644 --- a/translations/es-ES/content/developers/apps/managing-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/managing-oauth-apps.md @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /apps/building-integrations/managing-oauth-apps/ - /apps/managing-oauth-apps 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 index 1883718e9b..452aa3f1e0 100644 --- 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 @@ -42,9 +42,9 @@ Esta solicitud de rellamada te enviará un token de acceso y un token de actuali ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" @@ -73,3 +73,11 @@ Si quieres que tu app utlice tokens de acceso de usuario a servidor sin caducida 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/)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Leer más + +- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md b/translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md index 705f0cd3a5..a4320b4f81 100644 --- a/translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md +++ b/translations/es-ES/content/developers/github-marketplace/about-marketplace-badges.md @@ -13,7 +13,7 @@ Algunas apps en {% data variables.product.prodname_marketplace %} tienen la insi - Propiedad verificada del dominio y tiene una insignia verificada en su perfil - Confirmó su dirección de correo electrónico para que el soporte de {% data variables.product.prodname_dotcom %} pueda contactarla -- Requirió 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)." +- Requirió la autenticación bifactorial. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)". ![Insignia de Marketplace para las GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png) diff --git a/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md index 405a761a06..2313f20f78 100644 --- a/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md +++ b/translations/es-ES/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -22,8 +22,8 @@ Para ofrecer planes de pago para tu app, esta debe pertenecer a una organizació 1. Debajo de "Ajustes de desarrollador", da clic en **Verificación del publicador**. ![Opción de verificación del publicador en la barra lateral de ajustes de la organización](/assets/images/marketplace/publisher-verification-settings-option.png) 1. Debajo de "Verificación del publicador", completa la información de la lista de verificación: - Asegúrate de que tu información de perfil básica está presente y es correcta. También, asegúrate de que hayas incluido la mejor dirección de correo electrónico para recibir soporte y actualizaciones de {% data variables.product.company_short %}. - - Asegúrate de que se encuentre habilitada la autenticación bifactorial para tu organización. 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)." - - Emite un dominio verificado y asegúrate que se muestre la insignia de "Verificado" en el perfil de página de tu organización. Para la información relacionada, consulta la sección "[Verificar el dominio de tu organización](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)". + - Asegúrate de que se encuentre habilitada la autenticación bifactorial para tu organización. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)". + - Emite un dominio verificado y asegúrate que se muestre la insignia de "Verificado" en el perfil de página de tu organización. Para la información relacionada, consulta la sección "[Verificar el dominio de tu organización](/organizations/managing-organization-settings/verifying-your-organizations-domain)". ![Lista de verificación para la verificación del publicador](/assets/images/marketplace/publisher-verification-checklist.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 index 9e0931a987..b8b5d54c0f 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero versions: free-pro-team: '*' topics: diff --git a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md index c0d9dfb944..d32142cbf6 100644 --- a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md +++ b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview.md @@ -1,9 +1,8 @@ --- -title: GitHub Marketplace Overview -intro: 'Learn how you can share your app or action with the {% data variables.product.company_short %} community on {% data variables.product.prodname_marketplace %}.' -mapTopic: true +title: Resumen de GitHub Marketplace +intro: 'Aprende cómo puedes compartir tu app o acción con la comunidad de {% data variables.product.company_short %} en {% data variables.product.prodname_marketplace %}.' +mapTopic: verdadero versions: free-pro-team: '*' --- - 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 index 0c6c17ec9b..ed62983e31 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/ 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 index 8b42b47882..594cb8c52a 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /apps/marketplace/administering-listing-plans-and-user-accounts/ - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/ 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 index 73e8d74d67..5b9e5efe35 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/ diff --git a/translations/es-ES/content/developers/overview/managing-deploy-keys.md b/translations/es-ES/content/developers/overview/managing-deploy-keys.md index 5ff0890c99..80536a1b92 100644 --- a/translations/es-ES/content/developers/overview/managing-deploy-keys.md +++ b/translations/es-ES/content/developers/overview/managing-deploy-keys.md @@ -112,6 +112,36 @@ Entonces podrás utilizar el alias del nombre de host para que interactúe con e $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` +### Server-to-server tokens + +If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. + +Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps). + +##### Pros + +- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API). +- Dedicated rate limits that grow with your organization. +- Decoupled from GitHub user identities, so they do not consume any licensed seats. +- Never granted a password, so cannot be directly signed in to. + +##### Contras + +- Additional setup is needed to create the GitHub App. +- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code. + +##### Configuración + +1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private. +1. Determine the permissions your GitHub App requires, such as read-only access to repository contents. +1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app). +1. Note your GitHub App `id`. +1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key). +1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization. +1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). +1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). +1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client. + ### 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). diff --git a/translations/es-ES/content/developers/overview/secret-scanning.md b/translations/es-ES/content/developers/overview/secret-scanning.md index 8831282c7a..7737811803 100644 --- a/translations/es-ES/content/developers/overview/secret-scanning.md +++ b/translations/es-ES/content/developers/overview/secret-scanning.md @@ -17,12 +17,6 @@ Cuando se encuentra una coincidencia de tu formato secreto en un repositorio pú Cuando se encuentra una coincidencia con tu formato de secreto en un repositorio privado que se haya configurado para el {% data variables.product.prodname_secret_scanning %}, entonces, se alerta a los administradores de repositorio y éstos pueden ver y administrar los resultados del {% data variables.product.prodname_secret_scanning %} en {% data variables.product.prodname_dotcom %}. 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)". -{% note %} - -**Nota:** El {% data variables.product.prodname_secret_scanning_caps %} para los repositorios privados se encuentran actualmente en beta y está sujeto a cambios. - -{% endnote %} - Este artículo describe cómo puedes asociarte con {% data variables.product.prodname_dotcom %} como un proveedor de servicios y unirte al programa del {% data variables.product.prodname_secret_scanning %}. ### El proceso del {% data variables.product.prodname_secret_scanning %} diff --git a/translations/es-ES/content/developers/webhooks-and-events/events.md b/translations/es-ES/content/developers/webhooks-and-events/events.md index 27a34ccc58..f5e48f6d3f 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/events.md +++ b/translations/es-ES/content/developers/webhooks-and-events/events.md @@ -1,7 +1,7 @@ --- title: Eventos intro: 'Tus integraciones pueden suscribirse y reaccionar a los eventos en {% data variables.product.prodname_dotcom %}.' -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 0f4afb3d08..35c0809506 100644 --- 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 @@ -183,6 +183,20 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} +### PullRequestReviewEvent + +{% data reusables.webhooks.pull_request_review_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto de `payload` del evento + +| Clave | Type | Descripción | +| ---------------------- | ----------- | ---------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`. | +| `solicitud_extracción` | `objeto` | The pull request the review pertains to. | +| `revisar` | `objeto` | La revisión que se afectó. | + ### PullRequestReviewCommentEvent {% data reusables.webhooks.pull_request_review_comment_short_desc %} @@ -200,10 +214,12 @@ Este evento devuelve un objeto de `payload` vacío. {% data reusables.webhooks.events_api_payload %} +#### Objeto de `payload` del evento + | Clave | Type | Descripción | | -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `push_id` | `número` | Identificador único para la carga. | -| `size` | `número` | La cantidad de confirmaciones de la carga. | +| `tamaño` | `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`. | | `encabezado` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | 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 index a286fa9372..2f0c318e71 100644 --- 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 @@ -91,6 +91,6 @@ Tus implementaciones de lenguaje y de servidor pueden diferir de esta muestra de * 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. +* **No se recomienda** utilizar un simple operador de `==`. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks.md index 282037ef67..14774a45be 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks.md @@ -1,7 +1,7 @@ --- title: Webhooks intro: 'Aprende a configurar, probar y asegurar los webhooks para integrarte con {% data variables.product.prodname_dotcom %}.' -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index dec48e2f4a..0f40dc86e7 100644 --- 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 @@ -19,7 +19,7 @@ Con los {% data variables.product.prodname_discussions %}, la comunidad de tu pr 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)". +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 "[Niveles de permiso del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/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)". 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 index 7b26b1d12f..2cb29774f5 100644 --- 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 @@ -29,7 +29,7 @@ Puedes utilizar lps {% data variables.product.prodname_discussions %} para debat 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](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)". +{% data reusables.organizations.team-discussions-purpose %} Para obtener más información, consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)". ### Seguir los lineamientos de contribución 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 index f1e00f8c33..339427ccd5 100644 --- 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 @@ -21,7 +21,7 @@ Los colaboradores más útiles en los últimos 30 días se resaltarán en el tab 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)". +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](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". ### Paso 3: Cambia los niveles de permiso para los contribuyentes principales diff --git a/translations/es-ES/content/discussions/index.md b/translations/es-ES/content/discussions/index.md index 9974eb20a2..f6342fdcae 100644 --- a/translations/es-ES/content/discussions/index.md +++ b/translations/es-ES/content/discussions/index.md @@ -1,8 +1,8 @@ --- -title: GitHub Discussions Documentation -beta_product: true +title: Documentación sobre los debates de GitHub +beta_product: verdadero shortTitle: GitHub Discussions -intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Community members can ask and answer questions, share updates, have open-ended conversations, and follow along on decisions affecting the community''s way of working.' +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: @@ -23,7 +23,7 @@ featuredLinks: - /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 changelog: - label: 'discussions' + label: 'debates' product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: @@ -39,19 +39,19 @@ versions: {% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} {% if discussionsCommunityExamples %}
-

Communities using discussions

+

Comunidades que utilizan debates

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

Sorry, there is no result for

-

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

- Add your community {% octicon "arrow-right" %} +

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/managing-discussions-in-your-repository.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index b6ac806fe9..1866bdbe5b 100644 --- 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 @@ -12,7 +12,7 @@ versions: {% 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)". +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](/organizations/managing-organization-settings/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](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y "[Configurar los lineamientos para los contribuyentes de un repositorio](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)". diff --git a/translations/es-ES/content/discussions/quickstart.md b/translations/es-ES/content/discussions/quickstart.md index c8cbf6464c..e5a6278459 100644 --- a/translations/es-ES/content/discussions/quickstart.md +++ b/translations/es-ES/content/discussions/quickstart.md @@ -1,7 +1,7 @@ --- 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: true +allowTitleToDifferFromFilename: verdadero versions: free-pro-team: '*' --- diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md index df8021ed9e..7de6e3aaf5 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -16,3 +16,7 @@ Profesores, maestros y mentores pueden usar la capacitación en línea de Asesor **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 %} + +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)". + +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_campus_program %}, 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/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md index 5355204f0b..5e2f0b577a 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -9,4 +9,6 @@ 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)". +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 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)". diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md new file mode 100644 index 0000000000..85f7a36a19 --- /dev/null +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Campus Program +intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes: + +- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments +- Capacitación para docentes para el Git principal y {% data variables.product.prodname_dotcom %} con nuestro programa Asesores de campus +- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners +- Acceso automatizado a las funciones premium de {% data variables.product.prodname_education %}, como {% data variables.product.prodname_student_pack %} + +Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join. + +Para obtener más información, consulta la página [oficial {% data variables.product.prodname_campus_program %}](https://education.github.com/schools). + +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_campus_program %}, 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/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" o "[Usar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)". diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md index 2214e409b8..9d173de291 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -13,7 +13,7 @@ versions: ### Índice {% topic_link_in_list /use-github-at-your-educational-institution %} - {% link_in_list /about-github-education %} + {% link_in_list /about-github-campus-program %} {% link_in_list /about-campus-experts %} {% link_in_list /about-campus-advisors %} {% topic_link_in_list /use-github-for-your-schoolwork %} diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md index c532b9a6e6..50d72f27df 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution.md @@ -1,7 +1,7 @@ --- -title: Use GitHub at your educational institution -intro: 'Maximize the benefits of using {% data variables.product.prodname_dotcom %} at your institution for your students, instructors, and IT staff with {% data variables.product.prodname_education %} and our various training programs for students and instructors.' -mapTopic: true +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: - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md index 8512b9b548..fd3f268fa9 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork.md @@ -1,7 +1,7 @@ --- -title: Use GitHub for your schoolwork -intro: 'As a student, use {% data variables.product.prodname_dotcom %} to collaborate on your school projects and build real-world experience.' -mapTopic: true +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: - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md index 3dc25db887..b9550d9a46 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research.md @@ -1,7 +1,7 @@ --- -title: Use GitHub in your classroom and research -intro: 'As an educator or researcher, use {% data variables.product.prodname_dotcom %} to collaborate on your work in a classroom, student or research group, and more.' -mapTopic: true +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: - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index d5161a444e..ce05df22a7 100644 --- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -59,11 +59,11 @@ Para obtener más información, consulta: ### 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. +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. - Estás buscando obtener un título que se terminará en la sesión académica actual. - 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). +Tu instructor todavía puede solicitar un descuento para uso escolar {% data variables.product.prodname_education %}. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). ### Leer más diff --git a/translations/es-ES/content/education/guides.md b/translations/es-ES/content/education/guides.md index 50b347ee8e..7127d3cb37 100644 --- a/translations/es-ES/content/education/guides.md +++ b/translations/es-ES/content/education/guides.md @@ -1,45 +1,45 @@ --- -title: Guides for GitHub Education -intro: 'These guides for {% data variables.product.prodname_education %} help you teach and learn both {% data variables.product.product_name %} and software development.' -allowTitleToDifferFromFilename: true +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: '*' --- -### Get started with {% data variables.product.product_name %} +### Inicia con {% data variables.product.product_name %} -Teachers, students, and researchers can use tools from {% data variables.product.product_name %} to enrich a software development curriculum and develop real-world collaboration skills. +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. -- [Sign up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account) -- [Git and {% data variables.product.prodname_dotcom %} quickstart ](/github/getting-started-with-github/quickstart) -- [Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount) -- [Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack) +- [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/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Aplicar un paquete de desarrollo para alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack) -### Run a software development course with {% data variables.product.company_short %} +### Ejecuta un curso de desarrollo de software con {% data variables.product.company_short %} -Administer a classroom, assign and review work from your students, and teach the new generation of software developers with {% data variables.product.prodname_classroom %}. +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 %}. -- [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) -- [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) +- [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) -### Learn to develop software +### Aprende a desarrollar software -Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. +Incorpora a {% data variables.product.prodname_dotcom %} en tu educación y utiliza las mismas herramientas que los profesionales. -- [Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/git-and-github-learning-resources) -- [Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork) -- [Try {% data variables.product.prodname_desktop %}](/desktop) -- [Try {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli) +- [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/explore-the-benefits-of-teaching-and-learning-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) -### Contribute to the community +### Contribuye con la comunidad -Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. +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) -- [About Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) -- [About Campus Advisors](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) +- [Acerca de Expertos en campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts) +- [Acerca de Asesores de campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors) diff --git a/translations/es-ES/content/education/index.md b/translations/es-ES/content/education/index.md index af67dbe66a..e16c532314 100644 --- a/translations/es-ES/content/education/index.md +++ b/translations/es-ES/content/education/index.md @@ -1,7 +1,7 @@ --- 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 %}.' +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: @@ -20,7 +20,7 @@ featuredLinks: - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom changelog: - label: 'education' + label: 'educación' layout: product-landing versions: free-pro-team: '*' 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 index 13ccc0ed65..02abf27024 100644 --- 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 @@ -17,7 +17,7 @@ Cuando un alumno acepta una tarea grupal, los alumnos pueden crear un equipo nue {% 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)." +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 %}. For more information, see "[About teams](/organizations/organizing-members-into-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)". 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 index 0a08baefa7..b7e711bbed 100644 --- 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 @@ -1,8 +1,8 @@ --- title: Inicia con GitHub Classroom shortTitle: Empezar -intro: 'Aprende cómo configurar y utilizar {% data variables.product.prodname_classroom %} para administrar tu curso.' -mapTopic: true +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/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 index c26b923341..e0ece3f059 100644 --- 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 @@ -1,8 +1,8 @@ --- 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: true +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/learn-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md index 2c0e0f80ef..11ad0e7cfa 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +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/manage-classrooms.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/manage-classrooms.md index 5d697d2605..0bd6ef47a7 100644 --- 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 @@ -20,7 +20,7 @@ redirect_from: 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)". +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](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)" y "[Invitar a los usuarios a unirse a tu organización](/organizations/managing-membership-in-your-organization/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. @@ -34,7 +34,7 @@ Cuando compartes la URL de una tarea con un alumno por primera vez, dicho alumno ### 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 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](/organizations/collaborating-with-groups-in-organizations/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)". 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 index e5dbcf02c1..074514c403 100644 --- 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 @@ -1,7 +1,7 @@ --- -title: Teach with GitHub Classroom -intro: Learn how to set up your classroom and assignments. -mapTopic: true +title: Enseña con GitHub Classroom +intro: Aprende cómo configurar tu aula y tus tareas. +mapTopic: verdadero versions: free-pro-team: '*' redirect_from: diff --git a/translations/es-ES/content/education/quickstart.md b/translations/es-ES/content/education/quickstart.md index 95a8171387..4a185f18e6 100644 --- a/translations/es-ES/content/education/quickstart.md +++ b/translations/es-ES/content/education/quickstart.md @@ -1,7 +1,7 @@ --- 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: true +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: '*' --- 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 index 5b9088a3f2..2e5ed92449 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/configuring-pull-request-merges versions: 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 index 4e267ee963..f8734f5946 100644 --- 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 @@ -6,7 +6,7 @@ redirect_from: - /articles/defining-the-mergeability-of-pull-requests - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions product: '{% data reusables.gated-features.protected-branches %}' -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 19826e1393..b21e0daa39 100644 --- 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 @@ -26,7 +26,7 @@ De manera alterna, puedes habilitar {% data variables.product.prodname_actions % {% 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 %} +**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. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -47,7 +47,7 @@ Puedes inhabilitar todos los flujos de trabajo para un repositorio o configurar {% 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)". +**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. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." {% endif %} 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 index 5f762dee7a..c3b83a938a 100644 --- 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 @@ -11,7 +11,11 @@ topics: - repositories --- -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)". +### Acerca de la fusión automática + +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." + +### Managing auto-merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 index 0240f2c10f..14c87195c2 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/managing-branches-in-your-repository versions: 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 index 86463a8f79..48e5149cc1 100644 --- 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 @@ -47,6 +47,9 @@ los objetos de {% data variables.large_files.product_name_long %} ({% data varia 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) +{%- if currentVersion == "free-pro-team@latest" %} +1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} 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)." 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 index 2ebe54141c..aa65a4a8f0 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/managing-repository-settings versions: 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 index 6ff18bde7d..cffa464664 100644 --- 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 @@ -106,4 +106,4 @@ Los propietarios de las organizaciones y administradores de repositorio solo pue ### Leer más - [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)" +- "[Administrar la seguridad y la configuración de análisis para tu organización](/organizations/keeping-your-organization-secure/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 index dfd78f38f4..7a5a7d8416 100644 --- 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 @@ -16,7 +16,7 @@ Puedes ver un resumen de cada equipo o persona con acceso a tu repositorio para 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)." +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](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." ![Resumen de gestión de accesos](/assets/images/help/repository/manage-access-overview.png) @@ -53,4 +53,4 @@ Para obtener más información acerca de los niveles de permiso en los repositor ### Leer más - "[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)" +- "[Configurar los permisos básicos para una organización](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)" 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 index 577a30f77d..652d02afcd 100644 --- 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 @@ -13,7 +13,7 @@ topics: - repositories --- -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)." +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](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)." {% data reusables.organizations.internal-repos-enterprise %} 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 index e2477cdad6..f50b67d311 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /categories/85/articles/ - /categories/releases/ 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 index 175a315d05..74f0637964 100644 --- 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 @@ -4,7 +4,7 @@ intro: Puedes cambiar el nombre de una rama en un repositorio. permissions: Las personas con permisos de escritura en un repositorio pueden renombrar las ramas de éste. Las personas con permisos administrartivos pueden renombrar la rama predeterminada. versions: free-pro-team: '*' - enterprise-server: '>=3.1' + enterprise-server: '>=3.2' topics: - repositories --- @@ -13,7 +13,9 @@ topics: Puedes renombrar una rama en un repositorio de {% data variables.product.product_location %}. Para obtener más información sobre cómo renombrar ramas, consulta la sección "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches)". -Si renombras una rama, {% data variables.product.prodname_dotcom %} redireccionará automáticamente los enlaces en{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} que contengan el nombre anterior de la rama al enlace equivalente en la rama que se renombró. {% data variables.product.prodname_dotcom %} también actualizará las políticas de protección de rama, así como la rama base para las solicitudes de cambios y borradores de lanzamientos. +When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. + +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. ### Renombrar una rama 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 index 42a85e1097..920c5505a4 100644 --- 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 @@ -18,7 +18,7 @@ Cuando cambias el nombre de un repositorio, toda la información existente, a ex * 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)" +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-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: @@ -30,7 +30,7 @@ Para obtener más información, consulta "[Administrar repositorios remotos](/gi {% 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)." +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 %} ](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)." {% endif %} 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 index 37b3a0e9d5..6a6aeae1ba 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Asegurar tu repositorio intro: 'Asegurar las funciones como {% data variables.product.prodname_secret_scanning %} protegen los datos de tu repositorio.' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/securing-your-repository versions: 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 index 76f01a0cdf..e1259515f7 100644 --- 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 @@ -16,7 +16,7 @@ topics: ### 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)." +Los propietarios de las organizaciones pueden restringir la capacidad de cambiar la visibilidad de un repositorio únicamente para otros propietarios de organizaciones. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." Te recomendamos revisar las siguientes consideraciones antes de que cambies la visibilidad de un repositorio. 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 index d981b398bb..0dda1d7424 100644 --- 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 @@ -55,3 +55,19 @@ Puedes acceder a los repositorios en {% data variables.product.product_name %} d * 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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### {% data variables.product.company_short %}'s token formats + +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. + +| Token type | Prefix | Más información | +|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Token de acceso personal | `ghp_` | "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | + +{% 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 index bc744af3e0..1e14ef0e69 100644 --- 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 @@ -51,5 +51,5 @@ Después de que un propietario de empresa u organización habilite o requiera el ### Leer más -{% 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 == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/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/authenticating-with-saml-single-sign-on.md b/translations/es-ES/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md index 273aa392eb..18460dd946 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on/ 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 index 5b939d295a..ac099c725c 100644 --- 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 @@ -10,7 +10,7 @@ redirect_from: - /articles/generating-ssh-keys/ - /articles/generating-an-ssh-key/ - /articles/connecting-to-github-with-ssh -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 3ed585d7f2..058144ba0a 100644 --- 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 @@ -36,8 +36,15 @@ Los tokens de acceso personal (PAT) son una alternativa al uso de contraseñas p ![Seleccionar los alcances del token](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} 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 %} +8. Da clic en +{% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again. + {% if currentVersion == "free-pro-team@latest" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) + {% endif %} {% warning %} 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 index 19d6eddc5e..6fe7a51e68 100644 --- 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 @@ -20,7 +20,7 @@ Para preservar la seguridad de tu cuenta, te recomendamos que sigas estas buenas - Utiliza un administrador de contraseñas, tal como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/), para generar una contraseña de por lo menos 15 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/)". +- 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](/organizations/collaborating-with-groups-in-organizations/)". {% data reusables.repositories.blocked-passwords %} 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 index f5012313fc..03a940e67c 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/keeping-your-account-and-data-secure versions: 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 index 3a55e90681..da84f5e4a7 100644 --- 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 @@ -5,7 +5,7 @@ redirect_from: - /articles/generating-a-gpg-key/ - /articles/signing-commits-with-gpg/ - /articles/managing-commit-signature-verification -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 01aa0036e4..25c8d03aaa 100644 --- 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 @@ -1,6 +1,6 @@ --- -title: Reviewing your security log -intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you. +title: Revisar 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 @@ -8,257 +8,254 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - identidad + - administración de accesos --- -### Accessing your security log +### Acceder a tu registro de seguridad -The security log lists all actions performed within the last 90 days{% if currentVersion ver_lt "enterprise-server@2.20" %}, up to 50{% endif %}. +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. In the user settings sidebar, click **Security log**. - ![Security log tab](/assets/images/help/settings/audit-log-tab.png) +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. Under "Security history," your log is displayed. - ![Security log](/assets/images/help/settings/user_security_log.png) -4. Click on an entry to see more information about the event. - ![Security log](/assets/images/help/settings/user_security_history_action.png) +3. 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" %} -### Searching your security log +### Buscar tu registro de seguridad {% data reusables.audit_log.audit-log-search %} -#### Search based on the action performed +#### Búsqueda basada en la acción realizada {% else %} -### Understanding events in your security log +### Entender los eventos en tu registro de seguridad {% endif %} -The events listed in your security log are triggered by your actions. Actions are grouped into the following categories: +Tus acciones activan los eventos que se listan en tu bitácora de seguridad. Las acciones se agrupan en las siguientes categorías: -| Category name | Description -|------------------|-------------------{% 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`](#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" %} -| [`payment_method`](#payment_method-category-actions) | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your profile picture. -| [`project`](#project-category-actions) | Contains all activities related to project boards. -| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account). -| [`repo`](#repo-category-actions) | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %} -| [`sponsors`](#sponsors-category-actions) | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% if currentVersion != "github-ae@latest" %} -| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %} -| [`user`](#user-category-actions) | Contains all activities related to your account. +| 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) | Contiene todas las actividades relacionadas con los {% 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" %} -### Exporting your security log +### Exportar tu registro de seguridad {% data reusables.audit_log.export-log %} {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Security log actions +### Acciones de la bitácora de seguridad -An overview of some of the most common actions that are recorded as events in the security log. +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" %} -#### `account_recovery_token` category actions +#### acciones de la categoría `account_recovery_token` -| Action | Description -|------------------|------------------- -| `confirm` | Triggered when you successfully [store a new token with a recovery provider](/articles/configuring-two-factor-authentication-recovery-methods). -| `recover` | Triggered when you successfully [redeem an account recovery token](/articles/recovering-your-account-if-you-lose-your-2fa-credentials). -| `recover_error` | Triggered when a token is used but {% data variables.product.prodname_dotcom %} is not able to validate it. +| 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. | -#### `billing` category actions +#### acciones de la categoría `billing` -| Action | Description -|------------------|------------------- -| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}. -| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address). +| 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 +#### acciones de la categoría `codespaces` -| Action | 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). +| Acción | Descripción | +| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `trusted_repositories_access_update` | Se activa cuando cambias la [configuración de acceso y seguridad para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces) de tu cuenta. | -#### `marketplace_agreement_signature` category actions +#### acciones de la categoría `marketplace_agreement_signature` -| Action | Description -|------------------|------------------- -| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. +| Acción | Descripción | +| ---------------- | ----------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando firmas el {% data variables.product.prodname_marketplace %} Acuerdo del programador. | -#### `marketplace_listing` category actions +#### acciones de la categoría `marketplace_listing` -| Action | Description -|------------------|------------------- -| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. -| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. -| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. -| `redraft` | Triggered when your listing is sent back to draft state. -| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. +| 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 %} -#### `oauth_access` category actions +#### acciones de la categoría `oauth_access` -| Action | Description -|------------------|------------------- -| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps). -| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations). +| 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" %} -#### `payment_method` category actions +#### acciones de la categoría `payment_method` -| Action | Description -|------------------|------------------- -| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed. -| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account. -| `update` | Triggered when an existing payment method is updated. +| 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 %} -#### `profile_picture` category actions +#### acciones de la categoría `profile_picture` -| Action | Description -|------------------|------------------- -| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/). +| Acción | Descripción | +| -------- | ------------------------------------------------------------------------------------------------------ | +| `update` | Se activa cuando [estableces o actualizas tu foto de perfil](/articles/setting-your-profile-picture/). | -#### `project` category actions +#### acciones de la categoría `project` -| Action | Description -|--------------------|--------------------- -| `access` | Triggered when a project board's visibility is changed. -| `create` | Triggered when a project board is created. -| `rename` | Triggered when a project board is renamed. -| `update` | Triggered when a project board is updated. -| `delete` | Triggered when a project board is deleted. -| `link` | Triggered when a repository is linked to a project board. -| `unlink` | Triggered when a repository is unlinked from a project board. -| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed. +| 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. | +| `delete` | Se activa cuando se elimina un tablero de proyecto. | +| `link` | 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. | -#### `public_key` category actions +#### acciones de la categoría `public_key` -| Action | Description -|------------------|------------------- -| `create` | Triggered when you [add a new public SSH key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). -| `delete` | Triggered when you [remove a public SSH key to your {% data variables.product.product_name %} account](/articles/reviewing-your-ssh-keys). +| 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). | +| `delete` | Se activa cuando [eliminas una clave SSH pública para tu {% data variables.product.product_name %} cuenta](/articles/reviewing-your-ssh-keys). | -#### `repo` category actions +#### acciones de la categoría `repo` -| Action | Description -|------------------|------------------- -| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa). -| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% if currentVersion == "free-pro-team@latest" %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository. -| `add_topic` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. -| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} -| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). -| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} -| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository). -| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} -| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `enable` | Triggered when a repository is re-enabled.{% endif %} -| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). -| `remove_topic` | Triggered when a repository owner removes a topic from a repository. -| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository). -| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). -| `transfer_start` | Triggered when a repository transfer is about to occur. -| `unarchived` | Triggered when a repository owner unarchives a repository. +| 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" %} -#### `sponsors` category actions +#### acciones de la categoría `sponsors` -| Action | Description -|------------------|------------------- -| `repo_funding_link_button_toggle` | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") -| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/articles/managing-your-sponsorship)") -| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") -| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") -| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)") -| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| 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)` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-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" %} -#### `successor_invitation` category actions +#### acciones de la categoría `successor_invitation` -| Action | Description -|------------------|------------------- -| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") +| 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" %} -#### `team` category actions +#### acciones de la categoría `team` -| Action | Description -|------------------|------------------- -| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team). -| `add_repository` | Triggered when a team you are a member of is given control of a repository. -| `create` | Triggered when a new team in an organization you belong to is created. -| `destroy` | Triggered when a team you are a member of is deleted from the organization. -| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of. -| `remove_repository` | Triggered when a repository is no longer under a team's control. +| 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" %} -#### `two_factor_authentication` category actions +#### acciones de la categoría `two_factor_authentication` -| Action | Description -|------------------|------------------- -| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled. -| `disabled` | Triggered when two-factor authentication is disabled. +| 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 %} -#### `user` category actions +#### acciones de la categoría `user` -| Action | Description -|--------------------|--------------------- -| `add_email` | Triggered when you {% if currentVersion != "github-ae@latest" %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% 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 %} +| Acción | Descripción | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_email (agregar correo electrónico)` | Se activa cuando | +| {% if currentVersion != "github-ae@latest" %}[agregas una dirección de correo electrónico nueva](/articles/changing-your-primary-email-address){% else %}agregas una dirección de correo electrónico nueva{% endif %}.{% if currentVersion == "free-pro-team@latest" %} | | +| `codespaces_trusted_repo_access_granted` | Se activa cuando \[permites que los codespaces que creas para un repositorio accedan a otros repositorios que pertenezcan a tu cuenta de usuario\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. | +| `codespaces_trusted_repo_access_revoked` | Se activa cuando \[dejas de permitir que los codespaces que creas para un repositorio accedan a otros repositorios que pertenezcan a tu cuenta de usuario\](/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` | Se activa cuando ingresas en {% data variables.product.product_location %}.{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -#### `user_status` category actions -| Action | Description -|--------------------|--------------------- -| `update` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)." -| `destroy` | Triggered when you clear the status on your profile. +`mandatory_message_viewed` | Se activa cuando ves un mensaje obligatorio (consulta la sección "[Personalizar los mensajes de usuario](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obtener más detalles) | |{% endif %}| | `failed_login` | Se activa cuando fallas en ingresar con éxito. | `remove_email` | Se activa cuando eliminas una dirección de correo electrónico. | `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](/communities/maintaining-your-safety-on-github/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/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 index bc13efa289..d9b91ccae1 100644 --- 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 @@ -5,7 +5,7 @@ redirect_from: - /categories/84/articles/ - /categories/two-factor-authentication-2fa/ - /articles/securing-your-account-with-two-factor-authentication-2fa -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 1413718434..d50f910c2b 100644 --- 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 @@ -1,37 +1,39 @@ --- -title: Testing your SSH connection -intro: 'After you''ve set up your SSH key and added it to your {% data variables.product.product_name %} account, you can test your connection.' +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: '*' +topics: + - ssh --- -Before testing your SSH connection, you should have: -- [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys) -- [Generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) -- [Added a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account) +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) -When you test your connection, you'll need to authenticate this action using your password, which is the SSH key passphrase you created earlier. For more information on working with SSH key passphrases, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases). +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. Enter the following: +2. Ingresa lo siguiente: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} # Attempts to ssh to {% data variables.product.product_name %} ``` - You may see a warning like this: + Puedes ver una advertencia como la siguiente: ```shell - > The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established. - > RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8. - > Are you sure you want to continue connecting (yes/no)? + > 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`: +3. Verifica que la huella dactilar en el mensaje que ves empate con % if currentVersion == "free-pro-team@latest" %} [aquella de la llave pública de RSA de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} aquella de la llave pública de tu empresa{% endif %}. Si lo hace, entonces teclea `yes`: ```shell > Hi username! You've successfully authenticated, but GitHub does not > provide shell access. @@ -39,16 +41,16 @@ When you test your connection, you'll need to authenticate this action using you {% linux %} - You may see this error message: + Puede que veas el siguiente mensaje de error: ```shell ... - Agent admitted failure to sign using the key. - debug1: No more authentication methods to try. - Permission denied (publickey). + 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). ``` - This is a known problem with certain Linux distributions. For more information, see ["Error: Agent admitted failure to sign"](/articles/error-agent-admitted-failure-to-sign). + 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. Verify that the resulting message contains your username. If you receive a "permission denied" message, see ["Error: Permission denied (publickey)"](/articles/error-permission-denied-publickey). +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 index 15bf7eafe8..38ac56783b 100644 --- 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 @@ -4,7 +4,7 @@ intro: 'Puede que debas solucionar problemas imprevistos que surgen cuando se fi redirect_from: - /articles/troubleshooting-gpg/ - /articles/troubleshooting-commit-signature-verification -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 3a797a7406..60f1cacc6f 100644 --- a/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md +++ b/translations/es-ES/content/github/authenticating-to-github/troubleshooting-ssh.md @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/troubleshooting-ssh versions: 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 index 731143e79c..06fb99d67b 100644 --- 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 @@ -18,7 +18,7 @@ Puedes crear y participar de propuestas, solicitudes de extracción y debates de 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](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)". +{% data reusables.organizations.team-discussions-purpose %} Para obtener más información, consulta "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions)". ### Reaccionar a las ideas en los comentarios 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 index af6d2c3f8a..fee4d9e155 100644 --- 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 @@ -15,7 +15,7 @@ topics: 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 %} +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](/organizations/organizing-members-into-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/)". 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 index b1e746d7ea..d97c5ee33a 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/addressing-merge-conflicts versions: 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 index 39465d1848..309da62e25 100644 --- 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 @@ -14,7 +14,9 @@ topics: 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)". +Antes de que utilices la fusión automática con una solicitud de cambios, esta característica se debe habilitar en el repositorio. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} + +After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} 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). 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 index 47b844d086..a69685c92c 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/collaborating-on-repositories-with-code-quality-features-enabled/ - /articles/collaborating-on-repositories-with-code-quality-features 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 index 74cb28bc15..5171e7ad5a 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/incorporating-changes-from-a-pull-request versions: 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 index d771eecb3d..cd8475b0e5 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 01c7645eed..1fb4a211be 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/proposing-changes-to-your-work-with-pull-requests versions: 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 index 3b68f4e6af..28410bcf63 100644 --- 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 @@ -13,7 +13,7 @@ topics: 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 %} +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](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)".{% endif %} {% note %} 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 index ea3efcaadd..751693361e 100644 --- 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 @@ -4,7 +4,7 @@ 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: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 556c68e436..dd60d6837f 100644 --- 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 @@ -79,5 +79,5 @@ Si cambias la visibilidad de un repositorio interno y luego lo borras, las bifur - "[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)" +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/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 index ce0d3bb010..417bbb7cb2 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Trabajar con bifurcaciones intro: 'Las bifurcaciones se suelen usar en desarrollo de código abierto en {% data variables.product.product_name %}.' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/working-with-forks versions: 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 index bf6e7dfbf2..744b380843 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Crear y editar confirmaciones de cambios intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/creating-and-editing-commits versions: 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 index fb51d9aae5..8d57b5b5f3 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Confirmaciones de solución de problemas intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/troubleshooting-commits versions: 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 index 913a35b3b7..035327d3b6 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Ver y comparar confirmaciones de cambios intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/viewing-and-comparing-commits versions: 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 index 7388125d43..6f4ea240b3 100644 --- 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 @@ -23,7 +23,7 @@ Cuando alguien abre una solicitud de extracción que modifica el código que per 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.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](/organizations/organizing-members-into-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.22" %} 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 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 index 23b1e02b48..1a39ed9f3d 100644 --- 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 @@ -19,7 +19,7 @@ topics: {% 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. +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/blob/master/docs/troubleshooting.md) del Lingüista para obtener ayuda. ### Lenguaje Markup 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 index cc53067a29..9d372983cf 100644 --- 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 @@ -22,7 +22,7 @@ Solo tú, las personas con las que compartes el acceso explícitamente y, para l 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)". +Los propietarios de la organización siempre tiene acceso a todos los repositorios creados en la misma. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/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)". 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 index aceac86724..680b6a2609 100644 --- 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 @@ -5,7 +5,7 @@ redirect_from: - /articles/can-i-archive-a-repository/ - /articles/archiving-a-github-repository - /enterprise/admin/user-management/archiving-and-unarchiving-repositories -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 5487f8cf09..1319abc65f 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/cloning-a-repository-from-github versions: 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 index 7728e4ef01..4ac23472ad 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/creating-a-repository-on-github versions: 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 index 90c6b7f857..6f479a0736 100644 --- 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 @@ -23,13 +23,13 @@ Para que puedas duplicar un repositorio y subirlo a tu nueva copia, o _espejo_ d ``` 3. Sube en espejo al nuevo repositorio. ```shell - $ cd old-repository.git + $ cd old-repository $ 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 + $ rm -rf old-repository ``` ### Replicar un repositorio que contiene objetos de {% data variables.large_files.product_name_long %} @@ -41,7 +41,7 @@ Para que puedas duplicar un repositorio y subirlo a tu nueva copia, o _espejo_ d ``` 3. Dirígete al repositorio que acabas de clonar. ```shell - $ cd old-repository.git + $ cd old-repository ``` 4. Extra los objetos {% data variables.large_files.product_name_long %} del repositorio. ```shell @@ -58,7 +58,7 @@ Para que puedas duplicar un repositorio y subirlo a tu nueva copia, o _espejo_ d 7. Eliminar el repositorio local temporal que creaste previamente. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Replicar un repositorio en otra ubicación @@ -72,7 +72,7 @@ Si quieres replicar un repositorio en otra ubicación, incluido obtener actualiz ``` 3. Establece la ubicación para subir en tu espejo. ```shell - $ cd repository-to-mirror.git + $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` 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 index e4d8a3115c..68dd1d57fa 100644 --- 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 @@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > 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". +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. For more information, see "About OAuth App access restrictions." 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)". 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 index a6146f3952..e446564cd0 100644 --- 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 @@ -1,9 +1,7 @@ --- title: Explorar integraciones -intro: |- - Puedes personalizar y ampliar tu flujo de trabajo de {% data variables.product.product_name %} con herramientas y - servicios diseñados por la comunidad de {% data variables.product.product_name %}. -mapTopic: true +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: 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 index 307ee3a79a..e791c4f627 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/purchasing-and-installing-apps-in-github-marketplace versions: 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 index 050593073f..898b4236e7 100644 --- 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 @@ -1,6 +1,6 @@ --- 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 %}.' +intro: 'This preview has concluded and will no longer be accepting signups.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,50 +10,10 @@ topics: {% 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)". +**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 %}. {% 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). +The private preview for GitHub Codespaces in Visual Studio 2019 has concluded. For more information, see the [Visual Studio 2019 documentation](https://docs.microsoft.com/visualstudio/ide/codespaces/codespaces-overview?view=vs-2019). 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 index bdafef2075..7466005813 100644 --- 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 @@ -1,51 +1,49 @@ --- -title: About code scanning -intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' +title: 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' + enterprise-server: '2.22' +topics: + - seguridad --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About {% data variables.product.prodname_code_scanning %} +### Acerca de {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.about-code-scanning %} -You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. +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. -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)." +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 monitorear los resultados del {% data variables.product.prodname_code_scanning %} a lo largo de tus repositorios o de tu organización, puedes utilizar webhooks y la API del {% data variables.product.prodname_code_scanning %}. Para obtener más información sobre los webhooks para el {% data variables.product.prodname_code_scanning %}, consulta la sección [Cargas útiles y eventos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". Para obtener más información sobre las terminales de la API, consulta la sección "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)". -To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +Para iniciar con el {% data variables.product.prodname_code_scanning %}, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)". -### About {% data variables.product.prodname_codeql %} +### Acerca de {% data variables.product.prodname_codeql %} -You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +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 %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. +{% data variables.product.prodname_ql %}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. -{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. +Para 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 %} -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. +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://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) en la documentación de {% data variables.product.prodname_codeql %}. {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### Acerca de la facturación para {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data variables.product.prodname_code_scanning_capc %} 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 %} -### About third-party code scanning tools +### Acerca de las herramientas de escaneo de código de terceros {% data reusables.code-scanning.you-can-upload-third-party-analysis %} @@ -53,9 +51,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### Further reading +### Leer más {% 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 %} +- "[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) on the OASIS Committee website +- [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/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 index 18f3e9681f..be8791a6f5 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero product: '{% data reusables.gated-features.code-scanning %}' versions: 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 index 612c2f6227..a0d6d01ca6 100644 --- 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 @@ -1,60 +1,59 @@ --- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' +title: Configurar 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: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' +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' + enterprise-server: '2.22' +topics: + - seguridad --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### About {% data variables.product.prodname_code_scanning %} configuration +### Acerca de la configuración de {% data variables.product.prodname_code_scanning %} -You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." +Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %}, utilizando las {% data variables.product.prodname_actions %}, o desde tu sistema de integración contínua (IC), si utilizas 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)". -This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +Este artículo se trata de ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %}. -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +Antes de que puedas configurar el {% data variables.product.prodname_code_scanning %} para un repositorio, debes configurar el {% data variables.product.prodname_code_scanning %} agregando un flujo de trabajo de {% data variables.product.prodname_actions %} a este. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)". {% data reusables.code-scanning.edit-workflow %} -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. +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 {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} guarda los archivos de flujo de trabajo en el directorio de _.github/workflows_ de tu repositorio. Puedes encontrar un flujo de trabajo que hayas agregado si buscas su nombre de archivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. 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) -For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +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)." -### Configuring frequency +### Configurar la frecuencia -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +Puedes escanear código con cierta programación o cuando ocurren eventos específicos en un repositorio. -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +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. -#### Scanning on push +#### Escanear cuando se carga información -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +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)". -#### Scanning pull requests +#### Escanear las solicitudes de extracción -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +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)". -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +Para 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)". -#### Avoiding unnecessary scans of pull requests +#### Evitar escaneos innecesarios en las solicitudes de cambios -You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. +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: @@ -69,28 +68,28 @@ on: {% note %} -**Notes** +**Notas** -* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." -* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. +* `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 %} -For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." +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)". -#### Scanning on a schedule +#### Escanear de forma pre-programada -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +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 %} -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. +**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 %} -#### Example +#### Ejemplo -The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. +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: @@ -99,19 +98,19 @@ on: pull_request: branches: [main] schedule: - - cron: '0 15 * * 0' + - cron: '40 7 * * 2' ``` -This workflow scans: -* Every push to the default branch and the protected branch -* Every pull request to the default branch -* The default branch at 3 P.M. every Sunday +Este 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 cada martes a las 7:40 UTC -### Specifying an operating system +### Especificar un sistema operativo -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} +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 %} -If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} +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: @@ -120,23 +119,23 @@ jobs: runs-on: [self-hosted, ubuntu-latest] ``` -{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Para 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_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% 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" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}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 %} -### Changing the languages that are analyzed +### Cambiar los lenguajes que se analizan -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages. +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 %} -The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +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 %} -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix. +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 en el repositorio cuando se configuró el {% data variables.product.prodname_code_scanning %}. Por ejemplo, si el repositorio inicialmente contenía solo JavaScript cuando se configuró 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: @@ -149,7 +148,7 @@ jobs: language: ['javascript', 'python'] ``` -If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. +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 @@ -157,15 +156,15 @@ If your workflow does not contain a matrix called `language`, then {% data varia languages: cpp, csharp, python ``` {% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies +### Analizar las dependencias de Python -For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: +Para 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`: -- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies. +- 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. -- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete. +- 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. -Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract: +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: @@ -199,38 +198,45 @@ jobs: ``` {% endif %} -### Running additional queries +### Ejecutar consultas adicionales {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. +Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. Si las consultas están en un repositorio privado, utiliza el parámetro `external-repository-token` para especificar un token que tenga acceso a este. +{% raw %} ``` yaml - uses: github/codeql-action/init@v1 with: queries: COMMA-SEPARATED LIST OF PATHS + # Optional. Provide a token to access private repositories. + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +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 %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +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)". -In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. +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. +{% raw %} ``` 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 + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -### Using a custom configuration file +### Utilizar una herramienta de escaneo de código de terceros -As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. +Como alternativa 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. -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. +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 @@ -238,13 +244,23 @@ 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 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_. +{% data reusables.code-scanning.custom-configuration-file %} -The settings in the file are written in YAML format. +El archivo de configuración se ubica en un repositorio privado externo, utiliza el parámetro `external-repository-token` de la acción `init` para especificar un token que tenga acceso al repositorio privado. -#### Specifying additional queries +{% raw %} +```yaml +uses: github/codeql-action/init@v1 +with: + external-repository-token: ${{ secrets.ACCESS_TOKEN }} +``` +{% endraw %} -You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file. +Los ajustes en el archivo de configuración se escriben 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: @@ -253,17 +269,17 @@ queries: - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls ``` -Optionally, you can give each array element a name, as shown in the example configuration files below. +Opcionalmente, puedes otorgar un nombre a cada elemento de la matriz, como se muestra en los siguientes ejemplos de archivos de configuración. -For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. +Para obtener más información acerca de las consultas adicionales, puedes ver la siguiente sección "[Ejecutar consultas adicionales](#running-additional-queries)". -#### Disabling the default queries +#### Inhabilitar las consultas predeterminadas -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +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. -#### Specifying directories to scan +#### Especificar directorios para escanear -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. +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: @@ -275,46 +291,27 @@ paths-ignore: {% note %} -**Note**: +**Nota**: -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* 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 %} -For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +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)". -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +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. -#### Example configuration files +#### Ejemplos de archivos de configuración {% data reusables.code-scanning.example-configuration-files %} -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages +### 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 %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)." +{% data reusables.code-scanning.autobuild-add-build-steps %} Para 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)". -### Accessing private repositories +### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}. -If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs..steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." - -For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. - -{% 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 %} - -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} - -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." +{% 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/integrating-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md index c7df299d69..64f6ca264b 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero product: '{% data reusables.gated-features.code-scanning %}' versions: 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 index 7b061cafaf..05baf7a602 100644 --- 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 @@ -37,7 +37,7 @@ Necesitas permisos de escritura para ver un resumen de todas las alertas de un r {% 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. Debajo de "{% data variables.product.prodname_code_scanning_capc %}", da clic en la alerta que quisieras explorar. ![Resumen de alertas](/assets/images/enterprise/3.1/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) @@ -49,7 +49,7 @@ Si tienes permisos de escritura para un repositorio, puedes ver las alertas arre 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) +![Filtrar alertas por rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} @@ -102,11 +102,11 @@ Para descartar o borrar una alerta: 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) + ![Filtrar alertas por regla](/assets/images/enterprise/3.1/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) + ![Abrir una alerta desde la lista de sumario](/assets/images/enterprise/3.1/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) 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 index b1c62d1323..80718f7b40 100644 --- 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 @@ -1,131 +1,129 @@ --- -title: SARIF support for code scanning -shortTitle: SARIF support -intro: 'To display results from a third-party static analysis tool in your repository on {% data variables.product.prodname_dotcom %}, you''ll need your results stored in a SARIF file that supports a specific subset of the SARIF 2.1.0 JSON schema for {% data variables.product.prodname_code_scanning %}. If you use the default {% data variables.product.prodname_codeql %} static analysis engine, then your results will display in your repository on {% data variables.product.prodname_dotcom %} automatically.' +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' + enterprise-server: '2.22' +topics: + - seguridad --- {% data reusables.code-scanning.beta %} -### About SARIF support +### Acerca del soporte de SARIF -SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) that defines an output file format. The SARIF standard is used to streamline how static analysis tools share their results. {% data variables.product.prodname_code_scanning_capc %} supports a subset of the SARIF 2.1.0 JSON schema. +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. -To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-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). -If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." +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 "[Configurar el {% data variables.product.prodname_code_scanning %} para un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" 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 %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." +{% data variables.product.prodname_dotcom %} 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)". -If you're new to SARIF and want to learn more, see Microsoft's [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) 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. -### Preventing duplicate alerts using fingerprints +### Prevenir alertas duplicadas utilizando huellas dactilares -Each time the results of a new code scan are uploaded, the results are processed and alerts are added to the repository. To prevent duplicate alerts for the same problem, {% data variables.product.prodname_code_scanning %} uses fingerprints to match results across various runs so they only appear once in the latest run for the selected branch. This makes it possible to match alerts to the right line of code when files are edited. +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 %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. +{% 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. -SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% 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)." +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)". -If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)." +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 sobre la API, consulta la sección "[Cargar un análisis como datos de SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)". -### Validating your SARIF file +### Validar tu archivo SARIF -You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/). +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/). {% data reusables.code-scanning.upload-sarif-alert-limit %} -### Supported SARIF output file properties +### Propiedades compatibles de archivo de salida SARIF -If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}. +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 %}. -Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.product.prodname_code_scanning %} will only use the following supported properties. +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. -#### `sarifLog` object +#### Objeto `sarifLog` -| Name | Description | -|----|----| -| `$schema` | **Required.** The URI of the SARIF JSON schema for version 2.1.0. For example, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`. | -| `version` | **Required.** {% data variables.product.prodname_code_scanning_capc %} only supports SARIF version `2.1.0`. -| `runs[]` | **Required.** A SARIF file contains an array of one or more runs. Each run represents a single run of an analysis tool. For more information about a `run`, see the [`run` object](#run-object). +| 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). | -#### `run` object +#### Objeto `run` -{% data variables.product.prodname_code_scanning_capc %} uses the `run` object to filter results by tool and provide information about the source of a result. The `run` object contains the `tool.driver` tool component object, which contains information about the tool that generated the results. Each `run` can only have results for one analysis tool. +{% 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. -| Name | Description | -|----|----| -| `tool.driver.name` | **Required.** The name of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the name on {% data variables.product.prodname_dotcom %} to allow you to filter results by tool. | -| `tool.driver.version` | **Optional.** The version of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. | -| `tool.driver.semanticVersion` | **Optional.** The version of the analysis tool, specified by the Semantic Versioning 2.0 format. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. For more information, see "[Semantic Versioning 2.0.0](https://semver.org/)" in the Semantic Versioning documentation. | -| `tool.driver.rules[]` | **Required.** An array of `reportingDescriptor` objects that represent rules. The analysis tool uses rules to find problems in the code being analyzed. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | -| `results[]` | **Required.** The results of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the results on {% data variables.product.prodname_dotcom %}. For more information, see the [`result` object](#result-object). +| 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). | -#### `reportingDescriptor` object +#### Objeto `reportingDescriptor` -| Name | Description | -|----|----| -| `id` | **Required.** A unique identifier for the rule. The `id` is referenced from other parts of the SARIF file and may be used by {% data variables.product.prodname_code_scanning %} to display URLs on {% data variables.product.prodname_dotcom %}. | -| `name` | **Optional.** The name of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the name to allow results to be filtered by rule on {% data variables.product.prodname_dotcom %}. | -| `shortDescription.text` | **Required.** A concise description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the short description on {% data variables.product.prodname_dotcom %} next to the associated results. -| `fullDescription.text` | **Required.** A description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the full description on {% data variables.product.prodname_dotcom %} next to the associated results. The max number of characters is limited to 1000. -| `defaultConfiguration.level` | **Optional.** Default severity level of the rule. {% data variables.product.prodname_code_scanning_capc %} uses severity levels to help you understand how critical the result is for a given rule. This value can be overridden by the `level` attribute in the `result` object. For more information, see the [`result` object](#result-object). Default: `warning`. -| `help.text` | **Required.** Documentation for the rule using text format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. -| `help.markdown` | **Recommended.** Documentation for the rule using Markdown format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. When `help.markdown` is available, it is displayed instead of `help.text`. -| `properties.tags[]` | **Optional.** An array of strings. {% data variables.product.prodname_code_scanning_capc %} uses `tags` to allow you to filter results on {% data variables.product.prodname_dotcom %}. For example, it is possible to filter to all results that have the tag `security`. -| `properties.precision` | **Recommended.** A string that indicates how often the results indicated by this rule are true. For example, if a rule has a known high false-positive rate, the precision should be `low`. {% data variables.product.prodname_code_scanning_capc %} orders results by precision on {% data variables.product.prodname_dotcom %} so that the results with the highest `level`, and highest `precision` are shown first. Can be one of: `very-high`, `high`, `medium`, or `low`. +| 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 {% data reusables.code-scanning.upload-sarif-alert-limit %} -| Name | Description | -|----|----| -| `ruleId`| **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. -| `ruleIndex`| **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). -| `rule`| **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). -| `level`| **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. -| `message.text`| **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. -| `locations[]`| **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. -| `partialFingerprints`| **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. -| `codeFlows[].threadFlows[].locations[]`| **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). -| `relatedLocations[]`| A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). -| `suppressions[].state`| **Optional.** When the `state` is set to `accepted`, {% data variables.product.prodname_code_scanning %} will update the state of the result to `Closed` on {% data variables.product.prodname_dotcom %}. +| 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, con un máximo de 10. 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). | -#### `location` object +#### Objeto `location` -A location within a programming artifact, such as a file in the repository or a file that was generated during a build. +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. -| Name | Description | -|----|----| -| `location.id` | **Optional.** A unique identifier that distinguishes this location from all other locations within a single result object. -| `location.physicalLocation` | **Required.** Identifies the artifact and region. For more information, see the [`physicalLocation`](#physicallocation-object). -| `location.message.text` | **Optional.** A message relevant to the location. +| 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. | -#### `physicalLocation` object +#### Objeto `physicalLocation` -| Name | Description | -|----|----| -| `artifactLocation.uri`| **Required.** A URI indicating the location of an artifact, usually a file either in the repository or generated during a build. If the URI is relative, it should be relative to the root of the {% data variables.product.prodname_dotcom %} repository being analyzed. For example, main.js or src/script.js are relative to the root of the repository. If the URI is absolute, {% data variables.product.prodname_code_scanning %} can use the URI to checkout the artifact and match up files in the repository. For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. -| `region.startLine` | **Required.** The line number of the first character in the region. -| `region.startColumn` | **Required.** The column number of the first character in the region. -| `region.endLine` | **Required.** The line number of the last character in the region. -| `region.endColumn` | **Required.** The column number of the character following the end of the region. +| 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. | -### SARIF output file examples +### Ejemplos de archivo de salida SARIF -These example SARIF output files show supported properties and example values. +Estos ejemplos de archivos de salida SARIF muestran las propiedades compatibles y los valores de ejemplo. -#### Example with minimum required properties +#### Ejemplo con las propiedades mínimas requeridas -This SARIF output file has example values to show the minimum required properties for {% data variables.product.prodname_code_scanning %} results to work as expected. If you remove any properties or don't include values, this data will not be displayed correctly or sync on {% data variables.product.prodname_dotcom %}. +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 @@ -174,9 +172,9 @@ This SARIF output file has example values to show the minimum required propertie } ``` -#### Example showing all supported SARIF properties +#### Ejemplo que muestra todas las propiedades compatibles con SARIF -This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}. +Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propiedades de SARIF compatibles con {% data variables.product.prodname_code_scanning %}. ```json { diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md index c23538ba91..e07bbe731a 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -1,121 +1,114 @@ --- -title: Setting up code scanning for a repository -shortTitle: Setting up code scanning -intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +title: Configurar el escaneo de código en un repositorio +shortTitle: Configurar el escaneo de código +intro: 'Puedes configurar el {% data variables.product.prodname_code_scanning %} si agregas un flujo de trabajo a tu repositorio.' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' -redirect_from: - - /github/managing-security-vulnerabilities/configuring-automated-code-scanning - - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning - - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +permissions: 'Si tienes permisos de escritura en un repositorio, puedes configurar o ajustar el {% data variables.product.prodname_code_scanning %} en él.' versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - seguridad --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### Options for setting up {% data variables.product.prodname_code_scanning %} +### Opciones para configurar el {% data variables.product.prodname_code_scanning %} -You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to 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)." +Tú decides cómo generar las alertas del {% data variables.product.prodname_code_scanning %} y qué herramientas utilizar a nivel de 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 %} -### Setting up {% data variables.product.prodname_code_scanning %} using actions +### Configurar el {% data variables.product.prodname_code_scanning %} utilizando acciones -{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}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. To the right of "{% data variables.product.prodname_code_scanning_capc %}", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} - !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. - !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) -5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. +3. A la derecha de "alertas del {% data variables.product.prodname_code_scanning_capc %}", haz clic en **Configurar el {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Si falta el {% data variables.product.prodname_code_scanning %}, necesitas pedir al propietario de la organización o adminsitrador del repositorio que habilite la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis en tu organización](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" o "[Administrar la configuración de seguridad y análisis en tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} ![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. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Los flujos de trabajo solo se muestran si son relevantes para los lenguajes de programación que se detectan en el repositorio. El {% data variables.product.prodname_codeql_workflow %} siempre se muestra, pero el botón de "Configurar este flujo de trabajo" solo se habilita si el análisis de {% data variables.product.prodname_codeql %} es compatible con los lenguajes presentes en el repositorio.{% endif %} +5. Para personalizar la forma en que el {% data variables.product.prodname_code_scanning %} escanea tu còdigo, edita el flujo de trabajo. - Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. + 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. - For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." -6. Use the **Start commit** drop-down, and type a commit message. - ![Start commit](/assets/images/help/repository/start-commit-commit-new-file.png) -7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request. - ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) -8. Click **Commit new file** or **Propose new file**. + Para 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**. -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. +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 set up of {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once 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. +### Configuración del {% data variables.product.prodname_code_scanning %} por lotes +Puedes configurar el {% data variables.product.prodname_code_scanning %} en muchos repositorios al mismo tiempo utilizando un script. Para encontrar un ejemplo de un script que levanta solicitudes de cambio para agregar un flujo de trabajo de {% data variables.product.prodname_actions %} a varios repositorios, consulta el repositorio [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs). -### Viewing the logging output from {% data variables.product.prodname_code_scanning %} +### Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %} -After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. +Después de configurar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones mientras se ejecutan. {% data reusables.repositories.actions-tab %} - 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. + Veràs una lista que incluye una entrada para ejecutar el flujo de trabajo del {% data variables.product.prodname_code_scanning %}. El texto de la entrada es el título que le diste a tu mensaje de confirmación. - ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) + ![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. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. +1. Da clic en la entrada para el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. -1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. +1. Da clic en el nombre del job situado a la izquierda. Por ejemplo, **Analizar (IDIOMA)**. - ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + ![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. Review the logging output from the actions in this workflow as they run. +1. Revisa la salida de registro de las acciones en este flujo de trabajo conforme se ejecutan. -1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." +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 %} -**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. +**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 %}. - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endnote %} -### Understanding the pull request checks +### Entender las verificaciones de la solicitud de cambios -Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. +Cada flujo de trabajo del {% data variables.product.prodname_code_scanning %} que configuras para que se utilice en las solicitudes de cambios siempre tiene por lo menos dos entradas listadas en la sección de verificaciones de una solicitud de cambios. 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. -The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code. +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. - ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) + ![Verificaciones de solicitudes de cambios del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +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". - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) + ![Falta el análisis para el mensaje de confirmación](/assets/images/help/repository/code-scanning-missing-analysis.png) -#### Reasons for the "missing analysis" message +#### Razones para recibir un mensaje de "missing analysis" -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Missing analysis for base commit SHA-HASH" message. +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". -There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: +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: -* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed. +* La solicitud de cambios se levantó contra una rama diferente a la predeterminada y ésta no se ha analizado. - To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. + Para verificar 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. - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Elige una rama del menú desplegable de Rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) - The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. + 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. -* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available. +* 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. - Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. + Espera algunos minutos y luego sube un cambio a la solicitud de extracciòn para reactivar el {% data variables.product.prodname_code_scanning %}. -* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available. +* 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. - Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. + 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 %}. -### Next steps +### Pasos siguientes -After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: +Después de configurar el {% data variables.product.prodname_code_scanning %} y permitir que se completen sus acciones, puedes: -- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -- View any alerts generated for a pull request submitted after you set up {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." -- Set up notifications for completed runs. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." -- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)." -- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." +- 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 emitió después de que configuraste 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/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 index 9d46c0c634..b24a52b0d3 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero product: '{% data reusables.gated-features.code-scanning %}' versions: enterprise-server: '2.22' 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 index c4cc5384c5..003f391245 100644 --- 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 @@ -38,7 +38,7 @@ El administrador de sitio debe habilitar la {% data variables.product.prodname_advanced_security %} para {% data variables.product.product_location %} antes de que puedas utilizar estas características. Para obtener más información, consulta la sección "[Configurar las características de la Seguridad Avanzada](/admin/configuration/configuring-advanced-security-features)". {% endif %} -Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas características a nivel de organización o de repositorio. Para obtener más información, consulta las secciones "[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)" y "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas características a nivel de organización o de repositorio. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)." {% endif %} @@ -47,7 +47,7 @@ Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas Para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}, estas características se encuentran activas permanentemente y solo se pueden inhabilitar si cambias la visibilidad del proyecto para que el código ya no sea público. -En el caso de otros repositorios, una vez que tengas una licencia para tu cuenta empresarial, puedes habilitar e inhabilitar estas características a nivel de repositorio u organización. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis de tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" y "[Administrar la configuración y análisis de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} +En el caso de otros repositorios, una vez que tengas una licencia para tu cuenta empresarial, puedes habilitar e inhabilitar estas características a nivel de repositorio u organización. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)."{% endif %} {% endif %} 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 index 22a0e248e9..fe67a3b183 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Explorar proyectos en GitHub intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /categories/stars/ - /categories/87/articles/ diff --git a/translations/es-ES/content/github/getting-started-with-github/getting-started-with-git.md b/translations/es-ES/content/github/getting-started-with-github/getting-started-with-git.md index 128eebb7f0..bf904ddfd5 100644 --- a/translations/es-ES/content/github/getting-started-with-github/getting-started-with-git.md +++ b/translations/es-ES/content/github/getting-started-with-github/getting-started-with-git.md @@ -1,7 +1,7 @@ --- title: Comenzar con Git intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/getting-started-with-git-and-github - /github/using-git/getting-started-with-git-and-github 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 index 577b074442..bee66b678d 100644 --- 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 @@ -92,7 +92,7 @@ Adicionalmente a las características disponibles con {% data variables.product. - {% 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 %} -- Control de acceso para los sitios de {% data variables.product.prodname_pages %}. Para obtener más información, consulta la sección "Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}" +- Control de acceso para los sitios de {% data variables.product.prodname_pages %}. Para obtener más información, consulta la sección "Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}" - 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." 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 index c360605e80..6519e45d1a 100644 --- 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 @@ -52,6 +52,7 @@ A continuación aparece una lista de algunos de los atajos del teclado disponibl | 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) | +| control s or command s | Write a commit message | Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror](https://codemirror.net/doc/manual.html#commands). 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 index b864f1df94..eb2102453f 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Obtener información sobre GitHub intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/learning-about-github versions: 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 index 28d2e37aaf..0dcf6d2170 100644 --- a/translations/es-ES/content/github/getting-started-with-github/quickstart.md +++ b/translations/es-ES/content/github/getting-started-with-github/quickstart.md @@ -1,7 +1,7 @@ --- title: Inicio Rápido intro: 'Inicia rápidamente las tareas comunes en {% data variables.product.prodname_dotcom %}.' -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index a721a81fca..b44e465135 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Registrarse en GitHub intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/signing-up-for-github versions: diff --git a/translations/es-ES/content/github/getting-started-with-github/using-git.md b/translations/es-ES/content/github/getting-started-with-github/using-git.md index 829b3ca6c2..eecfa9a926 100644 --- a/translations/es-ES/content/github/getting-started-with-github/using-git.md +++ b/translations/es-ES/content/github/getting-started-with-github/using-git.md @@ -1,7 +1,7 @@ --- title: Utilizar GitHub intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/using-common-git-commands - /github/using-git/using-common-git-commands 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 index 96f2794bb1..7d0b9c89ba 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Utilizar GitHub intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/using-github versions: 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 index e02c721991..0d32b3d823 100644 --- 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 @@ -7,7 +7,7 @@ redirect_from: - /articles/importing-an-external-git-repo/ - /articles/importing-your-project-to-github/ - /articles/importing-source-code-to-github -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 30540ed45a..cdf2466f61 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Trabajar con Subversion en GitHub intro: Puedes usar clientes de Subversion y algunos flujos de trabajo y propiedades de Subversion con GitHub. -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/working-with-subversion-on-github versions: diff --git a/translations/es-ES/content/github/index.md b/translations/es-ES/content/github/index.md index 2c03364b2b..94af48a4cf 100644 --- a/translations/es-ES/content/github/index.md +++ b/translations/es-ES/content/github/index.md @@ -23,7 +23,7 @@ versions: {% link_in_list /managing-subscriptions-and-notifications-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 %} @@ -57,7 +57,6 @@ versions: {% 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 %} 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 index 8147f5680f..75ac25fe06 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Administrar archivos en GitHub intro: 'En {% data variables.product.product_name %}, puedes crear, editar, mover y eliminar archivos en un repositorio.' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/managing-files-on-github versions: 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 index 60604b67e0..a5a3bfd64c 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/managing-files-using-the-command-line versions: 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 index e6fa16b76a..0275076841 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Trabajar con archivos sin código intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /categories/89/articles/ - /articles/working-with-non-code-files 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 index 56975152c8..0fb017ea41 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Control de versiones de archivos grandes intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/versioning-large-files versions: 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 index 5f9563241c..afe4bf5a85 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/working-with-large-files versions: 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 index 6ca64fe6a1..302fee5ca5 100644 --- 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 @@ -42,9 +42,9 @@ Para encontrar una lista de ecosistemas para las cuales {% data variables.produc {% 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)". +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. 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](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." -Para obtener más información sobre los requisitos de permisos para las acciones que se relacionan con las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Niveles de permiso del repositorio para una organización](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)". +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% 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 %} 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 index b1097a9342..4387c46f9c 100644 --- 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 @@ -1,56 +1,59 @@ --- -title: Configuring notifications for vulnerable dependencies -shortTitle: Configuring notifications -intro: 'Optimize how you receive notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.' +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' + enterprise-server: '>=2.21 <=2.22' +topics: + - seguridad --- -### About notifications for vulnerable dependencies +### Acerca de las notificaciones para las dependencias vulnerables -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. -{% endif %} +{% 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" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% 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. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/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" %} -Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +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" %} -By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %} +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" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if 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" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if 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 %} -### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} +### 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 %} -You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." +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" %} - ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png) + ![Opciones de las {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/notifications-v2/dependabot-alerts-options.png) {% else %} - ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png) + ![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. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." +**Nota:** Puedes filtrar las notificaciones de {% data variables.product.company_short %} para mostrar 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 %}. 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 %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %} +{% 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 %} -### How to reduce the noise from notifications for vulnerable dependencies +### Cómo reducir el ruido de las notificaciones para las dependencias vulnerables -If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +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 +### Leer más -- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" -- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)" +- "[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/managing-vulnerabilities-in-your-projects-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies.md index f2083ff779..a63cc2f49c 100644 --- 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 @@ -1,9 +1,9 @@ --- 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: true +mapTopic: verdadero versions: - enterprise-server: <=2.22 + enterprise-server: '<=2.22' topics: - seguridad --- 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 index 7ec58aa1cf..7d616eeaca 100644 --- 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 @@ -66,7 +66,7 @@ Las notificaciones por correo electrónico también permiten la flexibilidad con ### 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/setting-up-and-managing-organizations-and-teams/about-team-discussions)". +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](/organizations/collaborating-with-your-team/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" %} @@ -78,7 +78,7 @@ Puedes configurar las notificaciones de un repositorio en la página del mismo, #### 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)". +{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. #### 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. @@ -248,16 +248,15 @@ También puedes programar si {% data variables.product.prodname_mobile %} enviar 1. En el menú inferior, pulsa en **Perfil**. 2. Para ver tu configuración, toca en {% octicon "gear" aria-label="The Gear icon" %}. -3. Para actualizar tu configuración de notificaciones, pulsa en **Notificaciones** y luego usa los alternadores para habilitar o inhabilitar tus tipos de notificaciones de subida preferidos. -4. Opcionalmente, para programar cuando {% data variables.product.prodname_mobile %} enviará notificaciones de subida a tu dispositivo móvil, pusla en **Recibir notificaciones**, utiliza el botón para alternar de **Horas laborales personalizadas** y elige entonces cuándo te gustaría recibir notificaciones de subida. +3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications. +4. Opcionalmente, para programar cuando {% data variables.product.prodname_mobile %} enviará notificaciones de subida a tu dispositivo móvil, pusla en **Horas laborales**, utiliza el botón para alternar de **Horas laborales personalizadas** y elige entonces cuándo te gustaría recibir notificaciones de subida. ### Configurar tus ajustes de observación para un repositorio individual con {% data variables.product.prodname_mobile %} 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. -1. En {% data variables.product.prodname_mobile %}, navega a la página principal del repositorio. +1. En {% data variables.product.prodname_mobile %}, visita la página principal del repositorio. 2. Pulsa en **Observar**. ![El botón de observar en {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-button.png) 3. Para elegir para qué actividades recibes notificaciones, pulsa en tus ajustes de observación preferidos. ![Menú desplegable de ajustes de observación en {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-settings.png) -{% data reusables.notifications-v2.custom-notifications-beta %} {% 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 index 449342c9c8..110ad39319 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Administrar suscripciones de actividades en GitHub intro: 'Para mantener notificaciones de flujo de trabajo sostenibles, entender y revisar frecuentemente tus suscripciones.' -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '>=2.21' 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 index 3c37236dd2..84fc22afbf 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/getting-started-with-notifications versions: 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 index 1cc26c8021..de69a8c940 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Ver y clasificar las notificaciones intro: 'Para optimizar el flujo de trabajo de tus notificaciones, puedes personalizar como las visualizas y clasificas.' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/managing-notifications/ - /articles/managing-your-notifications 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 index dff936b92b..47da02a4ca 100644 --- 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 @@ -38,7 +38,7 @@ Para ver un resumen de tus suscripciones a repositorios, consulta la sección "[ {% 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. +**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 las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". {% endtip %} {% endif %} 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 index 13f5efbb29..0b0ed31642 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/finding-information-in-a-repository versions: 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 index 13b747851b..ce549effa8 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/managing-project-boards versions: 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 index 48b3fe3ebb..f41935da4a 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues - /articles/managing-your-work-with-issues 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 index f0b520cf41..1971b2bd14 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/tracking-the-progress-of-your-work-with-milestones versions: 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 index 595e10af65..832d97cd9c 100644 --- 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 @@ -4,7 +4,7 @@ intro: 'Puedes hacer el seguimiento y priorizar tu trabajo en {% data variables. redirect_from: - /articles/tracking-the-progress-of-your-work-with-projects/ - /articles/tracking-the-progress-of-your-work-with-project-boards -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 4526a071bb..9eec6a72e5 100644 --- 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 @@ -1,6 +1,6 @@ --- title: Comenzar con la búsqueda en GitHub -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/getting-started-with-searching-on-github versions: 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 index 770fb9698c..3a12bcae2d 100644 --- 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 @@ -1,6 +1,6 @@ --- title: Buscar en GitHub -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/searching-on-github versions: 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 index 4f1306773f..475193a0cd 100644 --- 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 @@ -1,6 +1,6 @@ --- -title: Discounted subscriptions for GitHub accounts -intro: '{% data variables.product.product_name %} provides discounts to students, educators, educational institutions, nonprofits, and libraries.' +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/ @@ -8,28 +8,30 @@ redirect_from: - /articles/discounted-subscriptions-for-github-accounts versions: free-pro-team: '*' +topics: + - facturación --- {% tip %} -**Tip**: Discounts for {% data variables.product.prodname_dotcom %} do not apply to subscriptions for other paid products and features. +**Sugerencia**: Los descuentos para {% data variables.product.prodname_dotcom %} no se tienen vigencia para las suscripciones de otros productos y características pagos. {% endtip %} -### Discounts for personal accounts +### Descuentos para cuentas personales -In addition to the unlimited public and private repositories for students and faculty with {% data variables.product.prodname_free_user %}, verified students can apply for the {% data variables.product.prodname_student_pack %} to receive additional benefits from {% data variables.product.prodname_dotcom %} partners. For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)." +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/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)". -### Discounts for schools and universities +### Descuentos para escuelas y universidades -Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)." You can also request educational materials goodies for your students. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/). +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/explore-the-benefits-of-teaching-and-learning-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/). -### Discounts for nonprofits and libraries +### Descuentos para bibliotecas y organizaciones sin fines de lucro -{% data variables.product.product_name %} provides free {% data variables.product.prodname_team %} for organizations with unlimited private repositories, unlimited collaborators, and a full feature set to qualifying 501(c)3 (or equivalent) organizations and libraries. You can request a discount for your organization on [our nonprofit page](https://github.com/nonprofit). +{% 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). -If your organization already has a paid subscription, your organization's last transaction will be refunded once your nonprofit discount has been applied. +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 +### Leer más -- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)" +- "[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 index 15b17f5087..0353bba475 100644 --- 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 @@ -19,14 +19,14 @@ Cuando bajas de categoría o cancelas un patrocinio, el cambio entra en vigencia {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% 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.user_settings.billing_plans %} {% 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/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 index 4a881cc225..ca85436f95 100644 --- 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 @@ -6,7 +6,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: free-pro-team: '*' topics: 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 index 961892430d..d924d6aed0 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero versions: free-pro-team: '*' topics: 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 index 69167141e0..d1074be2cd 100644 --- 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 @@ -5,7 +5,7 @@ redirect_from: - /articles/managing-your-personal-account-s-apps/ - /articles/managing-your-organization-s-apps/ - /articles/managing-billing-for-github-marketplace-apps -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' topics: 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 index 956ae9d061..d55d3af292 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero versions: free-pro-team: '*' topics: 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 index b7532ddc04..8abaa80dde 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/managing-billing-for-github-sponsors versions: 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 index b009d46578..9f3107e289 100644 --- 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 @@ -11,7 +11,7 @@ redirect_from: - /categories/3/articles/ - /articles/managing-your-organization-s-paid-seats/ - /articles/managing-billing-for-your-github-account -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' topics: diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md index a76b249b27..e38cd3b13d 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md @@ -1,7 +1,7 @@ --- title: Administrar las licencias para GitHub Advanced Security intro: 'Puedes ver y administrar tu uso de plazas en una licencia de {% data variables.product.prodname_advanced_security %}.' -mapTopic: true +mapTopic: verdadero product: '{% data reusables.gated-features.ghas %}' 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 index aed89ae637..60047145cd 100644 --- 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 @@ -9,7 +9,7 @@ redirect_from: - /categories/paying-for-organization-accounts/articles/ - /categories/99/articles/ - /articles/managing-your-github-billing-settings -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' topics: 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 index fee2c02f04..ae3057806e 100644 --- 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 @@ -14,6 +14,8 @@ topics: {% 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. +{% data reusables.dotcom_billing.coupon-expires %} + No puedes aplicar cupones a planes pagos de {% data variables.product.prodname_marketplace %} apps. ### Canjear un cupón para tu cuenta personal 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 index 01e341d5a7..f6a6d1b78f 100644 --- 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 @@ -15,6 +15,8 @@ topics: 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. +{% data reusables.dotcom_billing.coupon-expires %} + {% 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. 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 index 9f6a2c767a..2abdc21acf 100644 --- 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 @@ -5,7 +5,7 @@ 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: true +mapTopic: verdadero versions: free-pro-team: '*' topics: 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 index 9d049a62a0..71908e400d 100644 --- 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 @@ -19,5 +19,6 @@ Cuando subes de categoría tu nivel de patrocinio, el cambio entrará en vigor d {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} 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 index 2e2abf11fe..0791895af9 100644 --- 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 @@ -59,7 +59,7 @@ Puedes mejorar a tu organización desde {% data variables.product.prodname_free_ #### 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 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](/organizations/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)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md index 2d465add71..2ab62e3541 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md @@ -20,5 +20,5 @@ Puedes verificar cuántas plazas incluye tu licencia y cuántas de ellas se usan La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Si te quedas sin plazas, la sección estará en rojo. Debes ya sea reducir tu uso de {% data variables.product.prodname_GH_advanced_security %} o comprar más plazas. Para obtener más información, consulta la sección "[Acerca del licenciamiento para la licencia empresarial de {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)". ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de licenciamiento empresarial](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. Opcionalmente, para ver un resumen detallado del uso por organización, en la barra lateral izquierda, haz clic en **Facturación**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) En la sección de "{% data variables.product.prodname_GH_advanced_security %}" puedes ver la cantidad de confirmantes y confirmantes únicos de cada organización. ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise.png) 5. Opcionalmente, haz clic en el nombre de una organización que te pertenezca para mostrar la configuración de seguridad y análisis para la organización. ![Organización que te pertenece en la sección de {% data variables.product.prodname_GH_advanced_security %} de la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. En la página de configuración de "Seguridad & análisis", desplázate hacia la sección de "repositorios de {% data variables.product.prodname_GH_advanced_security %}" para ver un resumen detallado del uso de este repositorio en esta organización. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". +6. En la página de configuración de "Seguridad & análisis", desplázate hacia la sección de "repositorios de {% data variables.product.prodname_GH_advanced_security %}" para ver un resumen detallado del uso de este repositorio en esta organización. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". 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 index 2e1d9a2c7b..f45a7c5b75 100644 --- 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 @@ -1,9 +1,11 @@ --- -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. +title: Configurar la administración de accesos e identidades para tu cuenta empresarial +intro: 'Puedes administrar el inicio de sesión único de SAML, aprovisionamiento de usuarios y sincronización de equipos para tu empresa.' product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' +topics: + - empresa --- 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 index 10d54d1ab7..6678f52fce 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### Acerca del inicio de sesión único de SAML para las cuentas empresariales -{% 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.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](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". {% data reusables.saml.about-saml-enterprise-accounts %} 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 index 3cf1eabc61..895078f2c7 100644 --- 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 @@ -49,7 +49,7 @@ Los propietarios de empresa pueden restringir el acceso a los activos que perten {% 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)". +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](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)". #### Agregar una dirección IP permitida 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 index 386c6dac95..03f1c27de8 100644 --- 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 @@ -15,7 +15,7 @@ topics: ### 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 del equipo](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)". +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 del equipo](/organizations/collaborating-with-your-team/about-team-discussions/)". {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 index c6d732ceec..9cb0880b4d 100644 --- 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 @@ -39,7 +39,7 @@ Los propietarios de las organizaciones pueden invitar a miembros nuevos a una or Aunque no es un requisito, te recomendamos que los propietarios de las organizaciones envíen una invitación a la misma dirección de correo electrónico que utilizas para el Nombre Primario de Usuario (UPN) de los suscriptores de {% data variables.product.prodname_vs %}. Cuando la dirección de correo electrónico en {% data variables.product.product_name %} coincida con el UPN del suscriptor, podrás garantizar que ningún otro miembro de la organización será capaz de adjudicarse la licencia de este. -Para obtener más información, consulta las secciones "[Invitar a usuarios para que se unan a tu organización](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)", "[Registrarse para {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)", y "[Administrar las preferencias de correo electrónico](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)". +Para obtener más información, consulta las secciones "[Invitar a usuarios para que se unan a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)", "[Registrarse para {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)", y "[Administrar las preferencias de correo electrónico](/github/setting-up-and-managing-your-github-user-account/managing-email-preferences)". ### Visualizar el licenciamiento de {% data variables.product.prodname_enterprise %} 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 index 622a195c1c..173e1c3a4b 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Administrar organizaciones en tu cuenta de empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: true +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 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 index 481cc32abe..45a4d07a8d 100644 --- 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 @@ -19,7 +19,7 @@ Si utilizas Azure AD como tu IdP, puedes habilitar la sincronización de equipos {% 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)". +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](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". ### Prerrequisitos 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 index 391ea86adf..e3d3cc0031 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Administrar los usuarios en tu empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: true +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 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 index e6e1035f77..62ea39c3f0 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Administrar tu cuenta de empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: true +mapTopic: verdadero redirect_from: - /articles/managing-your-enterprise-account versions: 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 index a1a1df7bf7..7a6f563a42 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### 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)". +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](/organizations/keeping-your-organization-secure/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. 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 index 14e72a060b..13fbe647dd 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Establecer políticas para organizaciones en tu cuenta de empresa product: '{% data reusables.gated-features.enterprise-accounts %}' -mapTopic: true +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 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 index c5a6b30d54..52c81b9334 100644 --- 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 @@ -14,7 +14,7 @@ topics: ### 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)". +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](/organizations/managing-organization-settings/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 %} @@ -22,7 +22,7 @@ Los propietarios de las organizaciones podrán verificar la identidad de los mie 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)". +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](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)". ### Verificar el dominio de tu cuenta empresarial 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 index 4dc6262eb3..cded2903af 100644 --- 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 @@ -53,4 +53,4 @@ Cuando habilitas el inicio de sesión único de SAML para tu cuenta empresarial, ### Leer más -- "[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)" +- "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" 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 index 9409e5a310..ad0c4f2c02 100644 --- 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 @@ -14,7 +14,7 @@ topics: 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)". +{% 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](/organizations/managing-organization-settings/verifying-your-organizations-domain)". ![Muestra de página de perfil de una organización verificada](/assets/images/help/profile/org_profile_verified.png) {% else %} @@ -23,4 +23,4 @@ Opcionalmente, puedes optar por agregar una descripción, una ubicación, un sit ### Leer más -- "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" +- "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)" 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 index 9c3e6592f5..8662b9f907 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/customizing-your-profile versions: 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 index f79af149d3..c792e37f36 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/managing-contribution-graphs-on-your-profile versions: 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 index dd5abef5d2..6f8a8d6cc4 100644 --- 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 @@ -25,7 +25,7 @@ Las confirmaciones aparecerán en tu gráfico de contribución si cumplen **toda - 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)" +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-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. @@ -66,7 +66,7 @@ Las direcciones de correo electrónico generales, tales como `jane@computer.loca #### 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)". +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). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-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`. 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 index 29b6885e07..0ab010ff17 100644 --- 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 @@ -52,7 +52,7 @@ Puedes convertir tu cuenta de usuario personal directamente en una organización {% 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)." +**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](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)." {% endtip %} 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 index f6c6cbe4b2..6f1a2d1e5e 100644 --- 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 @@ -56,4 +56,4 @@ Los repositorios que son propiedad de una organización pueden conceder acceso m - "[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)" +- "[Organizar los miembros en equipos](/organizations/organizing-members-into-teams)" 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 index ad28b837a9..38a8ebfb42 100644 --- 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 @@ -6,7 +6,7 @@ redirect_from: - /categories/managing-repository-collaborators/ - /articles/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index c91c4887ec..e7a0ee44aa 100644 --- 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 @@ -4,7 +4,7 @@ intro: 'Puedes agregar o cambiar las direcciones de correo electrónico asociada redirect_from: - /categories/managing-email-preferences/ - /articles/managing-email-preferences -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 96e81f1de5..516b7e39ae 100644 --- 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 @@ -25,4 +25,4 @@ Cuando creas un repositorio nuevo en {% data variables.product.product_location ### Leer más -- "[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)" +- "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/organizations/managing-organization-settings/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 index b1689c3335..b7965b0e6b 100644 --- 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 @@ -5,7 +5,7 @@ redirect_from: - /categories/29/articles/ - /categories/user-accounts/ - /articles/managing-user-account-settings -mapTopic: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index fc8f7eb48f..6d06b30cb1 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/managing-your-membership-in-organizations versions: 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 index f7bb9b2636..2bcafa12df 100644 --- 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 @@ -13,7 +13,7 @@ Los recordatorios programados se utilizan para garantizar que los usuarios se en 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)". +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](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)". {% data reusables.reminders.scheduled-reminders-limitations %} @@ -50,5 +50,5 @@ Puedes configurar recordatorios programados para solicitudes de revisión a nive ### Leer más -- "[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)" +- "[Administrar los recordatorios programados para tu organización](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- "[Administrar los recordatorios programados para tu equipo](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" 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 index 2cc456c423..734f341335 100644 --- 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 @@ -125,7 +125,7 @@ El uso del cliente de los Productos no debe violar ninguna ley aplicable, incluy 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. Privacidad -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. +The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Agreement](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. 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 diff --git a/translations/es-ES/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/es-ES/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md new file mode 100644 index 0000000000..07ed70c7b6 --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md @@ -0,0 +1,348 @@ +--- +title: GitHub Data Protection Agreement (Non-Enterprise Customers) +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum +versions: + free-pro-team: '*' +--- + +_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._ + +## INTRODUCCIÓN + +The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products. + +En caso de que exista cualquier conflicto o inconsistencia entre la DPA y cualquier otra condición en el acuerdo del cliente con Github, la DPA deberá prevalecer. Las disposiciones de la DPA sustituyen cualquier disposición que entre en conflicto con la Declaración de Privacidad de GitHub que pudiera aplicarse de otra forma al procesamiento de los Datos Personales del Cliente como se define en el presente documento. Para mayor claridad, en apego a la Cláusula 10 de las Cláusulas Contractuales Estándar en el Adjunto 1, las Cláusulas Contractuales Estándar prevalecerán sobre cualquier otra condición en la DPA. + + +## PROTECCIÓN DE DATOS DE GITHUB + +### 1. Definiciones. + +1.1 Las "**Leyes de Protección de Datos Aplicables**" se refiere a ciertas leyes, regulaciones, marcos de trabajo regulatorios, u otras legislaciones que se relacionen con el procesamiento y el uso de los Datos Personales del Cliente, de acuerdo a lo aplicable con el uso de GitHub por parte del cliente y del Servicio de GitHub, incluyendo: + + a. El reglamento general de protección de datos 2016/679 de la UE (**RGPD**), junto con cualquier legislación o reglamentación nacional equivalente que sea de aplicación o correspondiente, una vez que se aplique o sea aplicable; y + + b. La Ley de Privacidad de los Consumidores de California de 2018, Cal. Civ. Code §§1798.100 et seq. (**"CCPA"**); y + + c. La Ley de Protección de Datos del Reino Unido de 2018 y la implementación de RGDP que se contiene en la misma. + +1,2 Las palabras "**Controlador**", "**Titular de los datos**", "**Estado miembro**", "**Datos Personales**", "**Violación a los Datos Personales**, "**Procesamiento**", "**Procesador**", y "**Autoridad de Supervisión**" tienen los significados que se les otorguen en las Leyes de Protección de Datos Aplicables. En el caso de un conflicto, prevalecerán los significados que se les atribuyen en el RGPD. + +1.3 "**Datos personales del Cliente**" se refiere a cualquier Dato personal del cual el Cliente sea Controlador, ya sea suministrado por el Cliente para el procesamiento de GitHub o generado por GitHub durante la realización de sus obligaciones conforme al Acuerdo. Incluye datos como información de la facturación, direcciones IP, direcciones de correo electrónico corporativas y cualquier otro Dato personal del cual el Cliente sea Controlador. + +1.4 "**Datos del Repositorio del Cliente**" se refiere a cualquier dato o información que el Cliente carga o crea en cualquiera de sus Repositorios privados. + +1.5 A "**Violación de datos**" se refiere a una violación de datos personales o cualquier otro incumplimiento confirmado o razonablemente sospechado de los datos protegidos del cliente. + +1.6 "**Usuario final**" se refiere a un Sujeto de datos individual que controla una cuenta de GitHub y aceptó los Términos de servicio de GitHub, y cuyos datos personales están siendo transferidos, almacenados o procesados por GitHub. Por ejemplo, cada empleado o contratista del Cliente que tiene una cuenta de GitHub también es un Usuario final de GitHub. + +1.7 "**Fines permitidos**" para el procesamiento de datos son aquellos fines limitados y específicos de prestación del Servicio según se establece en el Acuerdo, en la Declaración de privacidad de GitHub y en el presente Apéndice A, o los fines para los cuales un Sujeto de datos autorizó el uso de los Datos personales del Cliente. + +1.8 "**Datos protegidos**" incluye cualquier Dato personal del Cliente y cualquier Dato del Repositorio del Cliente procesado por GitHub en nombre del Cliente, según lo dispuesto en el Acuerdo. + +1.9 "**Datos Sensibles**" Significa cualquier tipo de dato personal que revele el origen racial o étnico; las opiniones políticas, las creencias religiosas o filosóficas o afiliaciones a sindicatos; procesamiento de datos genéticos o biométricos para propósitos únicos de identificación de una persona natural; datos pertinentes a la salud, la vida sexual de una persona natural o la orientación sexual de la misma; y los datos pertinentes a las ofensas, convicciones criminales o medidas de seguridad. + +### 2. Estado y cumplimiento. + +#### 2.1 Procesamiento de Datos. +GitHub actúa como un Procesador con respecto a los Datos Personales de los clientes que recibe en conexión con el Acuerdo, y GitHub procesará los Datos Personales del Cliente únicamente para los propósitos permitidos de acuerdo con las instrucciones del Cliente de acuerdo a como se representa en el Acuerdo y en otros comunicados por escrito. En el caso de que GitHub no pueda cumplir con las indicaciones del Cliente, por ejemplo, debido a conflictos con las Leyes aplicables de Protección de datos, o cuando las Leyes aplicables de Protección de datos u otros requisitos legales requieren el procesamiento, GitHub notificará al Cliente en la medida de lo permitido. GitHub procesa todos los Datos personales del Cliente en los Estados Unidos o en la Unión Europea; sin embargo, los subprocesadores de GitHub pueden procesar datos fuera de los Estados Unidos o la Unión Europea. Además, GitHub actúa como Procesador para cualquier Dato del Repositorio del Cliente. + +#### 2.2 Controladores de Datos. +GitHub recibe Datos Personales de los Clientes tanto del Cliente como directamente de los Titulares de los Datos que crean cuentas de Usuario Final. El Cliente es Controlador únicamente de los Datos personales del Cliente que transfiere directamente a GitHub. + +#### 2.3 Cumplimiento de GitHub; Transferencias de Datos. +GitHub cumplirá con las Leyes Aplicables de Protección de Datosen relación con el procesamiento de los Datos Personales del Cliente. + +Todas las transferencias de Datos Personales del Cliente fuera de la Unión Europea, el Área Económica Europea, el Reino Unido y Suiza par aproporcionar el Servicio se regirán por las Cláusulas Contractuales Estándar en el Adjunto 1 (Cláusulas Contractuales Estándar). GitHub cumplirá con los requerimientos del Área Económica Europea y la ley de protección de datos suiza de acuerdo con la recolección, uso, transferencia, retención y otros tipos de procesamiento de Datos Personales de los Clientes desde el Área Económica Europea, el Reino Unido y Suiza. Todas las transferencias de Datos Personales del Cliente a un país tercero o a una organización internacional estarán sujetos a la salvaguarda adecuada de acuerdo a lo descrito en el artículo 46 del RGPD y dichas transferencias y salvaguardas se documentarán de acuerdo con el artículo 30(2) del RGPD. + +Adicionalmente, GitHub está certificado en el Marco del Escudo de Privacidad de U.E. - E.U.A. y de Suiza - E.U.A. y en los compromisos que esto conlleva, aunque GitHub no depende de ellos como base legal para transferencias de datos personales. GitHub acuerda notificar al cliente si hace una determinación de que ya no puede cumplir con su obligación de proporcional el mismo nivel de protección de acuerdo a como se requiere con los principios del Escudo de Privacidad. + + +### 3. Protección de datos. + +#### 3.1 Limitación de propósitos. +GitHub procesará y comunicará los Datos Protegidos únicmente para los Propósitos Permitidos, a menos de que las partes convengan por escrito un propósito ampliado. + +#### 3.2 Calidad y Proporcionalidad de los Datos. +GitHub mantendrá los Datos Personales del Cliente actualizados y exactos, o habilitará al cliente para que lo haga. GitHub seguirá los pasos comercialmente razonables para asegurar que cualquier Dato protegido que recopile en nombre del Cliente sea adecuado, relevante y no excesivo en relación con los fines para los cuales se transfiere y se procesa. En ningún caso GitHub recopilará intencionalmente Datos confidenciales en nombre del Cliente. El Cliente acepta que el Servicio de GitHub no está destinado al almacenamiento de Datos confidenciales. Si el Cliente decide cargar Datos confidenciales en el Servicio, el Cliente debe cumplir con el Artículo 9 del GDPR, o las disposiciones equivalentes de las Leyes aplicables de Protección de datos. + +#### 3.3 Retención y Eliminación de Datos. +Bajo la solicitud razonable del cliente, a menos de que se prohiba por ley, GitHub devolverá, destruirá o desidentificará todos los Datos Personales del Cliente y los datos relacionados en todas las ubicaciones donde se almacenen después de que dejen de requerirse para los Propósitos Permitidos dentro de treinta días de la solicitud. GitHub puede conservar los Datos personales del Cliente y los datos relacionados en la medida que lo exijan las Leyes aplicables de Protección de datos y solo en la medida y por el período que estas lo requieran, siempre que GitHub asegure que los Datos personales del Cliente se procesarán solo si se necesitan para el fin especificado en las Leyes aplicables de Protección de datos y sin ningún otro fin, y los Datos personales del Cliente segruirán protegidos por las Leyes aplicables de Protección de datos. + +#### 3.4 Procesamiento de Datos. +GitHub proporciona la siguiente información, requerida por el Artículo 28(3) del RGPD, con respecto a su procesamiento de los Datos protegidos del Cliente: + +a. *El motivo y la duración del procesamiento* de los Datos personales del Cliente están establecidos en el Acuerdo y en el presente Anexo. + +b. *La naturaleza y el fin del procesamiento* de los Datos personales del Cliente se describen en la Sección 3.1 del presente Anexo. + +c. *Los tipos de Datos personales del Cliente que se procesarán* se describen en la Declaración de privacidad de GitHub e incluyen Datos personales del Cliente, tales como nombres de usuario, contraseñas, direcciones de correo electrónico y direcciones IP. GitHub también procesa la información necesaria para la facturación de la cuenta del Cliente, pero no procesa ni almacena información sobre tarjetas de crédito. El Cliente puede elegir suministrarle a GitHub Datos personales del Cliente, por ejemplo, en los parámetros del perfil del Cliente o al cargar Datos personales del Cliente en sus repositorios de GitHub. + +d. *Las categorías del Sujeto de datos con quien se relacionan los Datos personales del Cliente* son el propio Cliente y sus Usuarios finales. + +e. *Las obligaciones y los derechos del Cliente* están establecidos en el Acuerdo y en el presente Anexo. + +### 4. Seguridad y obligaciones de auditoría. + +#### 4.1 Medidas de Seguridad Técnicas y Organizacionales. +Tomando en cuenta las tecnologías más actuales, los costos de implementación, y la naturaleza, alcance, contexto y propósito de procesamiento, así como el riesgo de variar la probabilidad y severidad de los derechos y libertades de las personas naturales, GitHub implementará medidas técnicas y organizacionales adecuadas para garantizar un nivel de seguridad adecuado para los riesgos, tales como aquellas contra la destrucción accidental o ilegal, o contra la pérdida, alteración, o contra el acceso o divulgación no autorizados que se presenten debido al Procesamiento de los Datos. GitHub supervisará regularmente el cumplimiento de estas medidas y continuará tomando las debidas salvaguardias durante la vigencia del Acuerdo. + +#### 4.2 Respuesta a Incidentes y Notificación de Filtración. +GitHub will comply with Applicable Data Protection Laws. + +#### 4.3 Personal de GitHub. +GitHub representa y garantiza que tomará los pasos razonables para asegurarse de que todo su personal que maneje Datos Protegidos haya acordado mantener dichos datos como confidenciales y haya recibido capacitación adecuada para cumplir con esta Adenda y con las Leyes de Protección de Datos Aplicables. + +#### 4.4 Registros. +GitHub mantendrá los registros por escrito completos, precisos y actualizados para todas las categorías de las actividades de procesamiento que se lleven a cabo en nombre de un Cliente, las cuales contengan la información que se requiere por las Leyes de Protección de Datos Aplicables. En la medida que la asistencia no ponga en riesgo la seguridad de GitHub o los derechos de privacidad de Sujetos de datos individuales, GitHub pondrá a disposición del Cliente estos registros a su solicitud cuando se requieran de manera razonable, por ejemplo, para ayudar al Cliente a demostrar su cumplimiento según lo dispuesto en las Leyes aplicables de Protección de datos. + +#### 4.5 Asistencia. +GitHub proporcionará asistencia considerable a los Clientes con preocupaciones tales como la valoración de impacto de la privacidad de los datos, solicitudes de derechos de los Titulares de los Datos, consultas con las Autoridades Supervisantes, y otros asuntes similares, en cada caso, únicamente para el procesamiento de los Datos Personales del cliente y tomando en cuenta la naturaleza del procesamiento. + +### 5. Uso y divulgación de Datos protegidos. + +#### 5.1 Si Uso para Marketing. +GitHub no utilizará los Datos Protegidos para propósitos de anunciar el contenido de terceros, y no venderá los Datos Protegidos a ningún tercero, excepto como parte de una adquisición o fusión. + +#### 5.2 Declaración de Privacidad de GitHub. +La Declaración de Privacidad de GitHub, la cual está disponible al público en [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), proporciona notificaciones detalladas de las prácticas de uso de datos y de privacidad de GitHub, incluyendo su uso de cookies, su proceso de resolución de disputas, y más detalles sobre el cumplimiento con el RGPD. + +### 6. Subprocesamiento y transferencia ulterior. + +#### 6.1 Protección de los Datos. +GitHub es responsable de las transferencias subsecuentes de los Datos Protegidos a sus subprocesadores, tales como su procesador de pagos tercero. En caso de que GitHub sí transfiera los Datos Protegidos a un subprocesador tercero, o que GitHub instale, use o habilite a un tercero o a un servicio de un tercero para procesar los Datos Protegidos en nombre de GitHub, github garantizará que dicho subprocesador tercero esté vinculado por un contrato escrito que le requiera proporcionar por lo menos el mismo nivel de confidencialidad, seguridad y protección de privacidad de acuerdo a como lo requiere GitHub en esta DPA y conforme a las Leyes de Protección de Datos Aplicables. + +#### 6.2 Aceptación de los Subprocesadores de GitHub. +El cliente autoriza a GitHub para designar (y permitir a cada subprocesador designado de acuerdo con la sección 6 el designar) subprocesadores de acuerdo con la sección 6 y con cualquier otra restricción en el Acuerdo. GitHub puede seguir usando los subprocesadores a los que actualmente recurre a partir de la Fecha de entrada en vigor del presente Anexo. + +#### 6.3 Consentimiento General para el Subprocesamiento Posterior. +El cliente proporciona un consentimiento general para que GitHub incluya subprocesadores posteriores, condicionalmente con el cumplimiento de GitHub con los siguientes requisitos: + +a. Cualquier suprocesador posterior deberá acordar por escrito solo procesar los datos en un país en el que la Comisión Europea haya declarado tener un nivel de protección "adecuado"; o el procesar solo datos en condiciones equivalentes a las Cláusulas Contractuales Estándar, o conforme a una aprobación de Reglas Corporativas de Vinculación que otorgue una autoridad de protección de datos europea competente, o conforme a las certificaciones de Escudo de Privacidad de UE-EUA y Suiza-E.U.A válids. ; y + +b. GitHub restringirá el acceso de los subprocesadores ulteriores a los Datos personales del Cliente solo a lo que resulte estrictamente necesario para prestar sus servicios, y GitHub le prohibirá al subprocesador procesar los Datos personales del Cliente para cualquier otro fin. + +#### 6.4 Divulgación de los Acuerdos de los Subprocesadores. +GitHub mantiene una lista de subprocesadores posteriores que ha contactado para procesar los Datos Personales de los Clientes en [https://docs.github.com/articles/github-subprocessors-and-cookies](/articles/github-subprocessors-and-cookies), incluyendo las categorías de Datos Personales de Clientes que se han procesado, una descripción del tipo de procesamiento que realiza el subprocesador, y la ubicación de su procesamiento. GitHub proporcionará al Cliente, previa solicitud escrita, la lista de subprocesadores y los términos según los cuales procesan los Datos personales del Cliente. Conforme a las restricciones de confidencialidad del subprocesador, GitHub puede eliminar cualquier información confidencial o comercialmente sensible antes de proporcionarle la lista y los términos al Cliente. En el caso de que GitHub no le pueda divulgar información confidencial o sensible al Cliente, las Partes acuerdan que GitHub proporcionará toda la información que razonablemente pueda en conexión con sus acuerdos de subprocesamiento. + +#### 6.5 Objeción a los Subprocesadores. +GitHub proporcionará treinta (30) días de notificación previa por escrito sobre la adición o eliminación de cualquier subprocesador, incluyendo a los de las categorías listadas en la sección 6.4, mediante el anuncio de los cambios en su sitio de . Si el Cliente tiene una objeción razonable sobre la incorporación de un nuevo subprocesador por parte de GitHub, el Cliente se lo debe notificar de inmediato por escrito a GitHub. En lo posible, GitHub hará los esfuerzos comercialmente razonables para proporcionar una solución alternativa al Servicio afectado para evitar el procesamiento de los datos por parte del subprocesador objetable. En el caso de que GitHub no pueda proporcionar una solución alternativa, y las Partes no puedan resolver el conflicto dentro de los noventa días, el Cliente puede poner fin al Acuerdo. + +### 7. Terminación. + +#### 7.1 Suspensión. +En caso de que GitHub se encuentre en una violación de sus obligaciones para mantener un niel adecuado de seguridad o protección de la privacidad, el cliente deberá suspender temporalmente la transferencia de todos los Datos Personales del mismo o prohibir la recolección y procesamiento de estos en nombre del cliente hasta que la violación se repare o hasta que finalice el contrato. + +#### 7.2 Terminación con Causa. +Adicionalmente a cualquier derecho de terminación que tenga el clinte bajo el contrato, dicho cliente puede terminar el contrato sin afectación a ningún otro reclamo en derecho o equidad en caso de que: + +a. GitHub notifica al Cliente que ya no puede cumplir con sus obligaciones de privacidad; + +b. la transferencia, recopilación o procesamiento de todos los Datos personales del Cliente ha sido suspendida de forma temporal por más de un mes en virtud de la Sección 7.1; + +c. GitHub se encuentra en incumplimiento sustancial o persistente de cualquiera de las garantías o manifestaciones según lo dispuesto en el presente Anexo; + +d. GitHub no continúa con su actividad, se disuelve, entra en quiebra o se hace una orden de liquidación a nombre de GitHub; + +e. El Cliente objeta al subprocesador conforme a la Sección 6.5, y GitHub no ha podido proporcionar una solución alternativa dentro de los noventa días. + +#### 7.3 Violación. +El incumplimiento con los aprovisionamientos materiales de esta adenda se considera una violación material bajo el acuerdo. + +#### 7.4 Incapacidad de realización. +En caso de que los cambios a la ley o a las regulaciones se traduzcan en la imposibilidad de hacer valer esta adenda o que el hacerlo sea comercialmente irracional, las partes podrán volver a negociar la adenda de buena fe. Si la renegociación no soluciona la imposibilidad, o si las Partes no pueden llegar a un acuerdo, las Partes pueden terminar el Acuerdo luego de treinta días. + +#### 7.5 Notificación. +En caso de que GitHub determine que ya no puede cumplir con sus obligaciones de privacidad conforme a esta adenda, Github notificará al cliente inmediatamente por escrito. + +#### 7.6 Modificaciones. +GitHub podrá modificar esta adenda de vez en cuando de acuerdo a los requisitos de las Leyes de Protección de Datos Aplicables emitiendo una notificación al Cliente treinta días antes de hacerlo. + +#### 7.7 Requisitos de la Terminación. +Al momento de la Terminación, GitHub Deberá: + +a. tomar las medidas razonables y adecuadas para detener el procesamiento de los Datos personales del Cliente; + +b. dentro de los noventa días posteriores a la terminación, eliminar o anonimizar cualquier Dato personal del Cliente que GitHub almacena en nombre del Cliente en virtud de la Sección 3.3; + +c. proporcionar al Cliente la certeza razonable de que GitHub ha cumplido con sus obligaciones de la Sección 7.7. + +### 8. Responsabilidad por el procesamiento de datos. + +#### 8.1 Limitaciones. +Salvo a las limitaciones que proporcionan las Leyes de Protección de Datos Aplicables, cualquier reclamo que se suscite bajo esta adenda estará sujeto a las condiciones del acuerdo con respecto a las Limitaciiones de Responsabilidades. + +## Adjunto 1 – Las Cláusulas Contractuales Estándar (Procesadores) +La ejecución del presente acuerdo a manes del cliente incluye la ejecución de este Adjunto 1 a la Adenda de Protección de Datos de Github, la cual refrenda GitHub, Inc. + +En los países donde se requiera de aprobación regulatoria para utilizar las Cláusulas Contractuales Estándar, no se podrá depender de éstas bajo la Comisión Europea 2010/87/EU (de febrero de 2010) para legitimar la exportación de datos del país en cuestión, a menos de que el cliente tenga la aprobación regulatoria requerida. + +Para propósitos del artículo 46(2) de la Regulación General de Protección de Datos (EU 2016/679) para la transferencia de datos personales a los procesadores establecidos en países terceros que no garantizan un nivel adecuado de protección de datos, el Cliente (como exportador de datos) y GitHub (como importador de datos, cuya firma aparece debajo), siendo cada uno de ellos una "parte", y en conjunto "las partes", acuerdan cumplir con las siguientes Cláusulas Contractuales (las "Cláusulas" o las "Cláusulas Contractuales Estándar") para citar los salvaguardos adecuados con respecto a la protección de la privacidad y de los derechos y libertades fundamentales de los individuos para la transferencia por parte del exportador de datos al importador de datos que manejará los datos personales especificados en el Apéndice 1. + +#### Cláusula 1: Definiciones +(a) los términos 'datos personales', 'categorías especiales de datos, 'proceso/procesamiento', 'controlador', 'procesador', 'titular de los datos' y 'autoridad supervisora' tendrán el mismo significado que en la Regulación General de Protección de Datos (EU 2016/679) sobre la protección de los individuos con respecto al procesamiento de los datos personales y sobre el movimiento libre de dichos datos; + +(b) 'el exportador de datos' se refiere al controlador que transifere los datos personales; + +(c) 'el importador de datos' se refiere al procesador que acuerda recibir datos personales del exportador, los cuales se pretenden procesar en su nombre después de la transferencia, de acuerdo con sus instrucciones y los términos de las Cláusulas y quien no está sujeto a un sistema de país tercero que garantice la protección adecuada dentro de las disposiciones del artículo 45(2) de la Regulación General para la Protección de Datos (EU 2016/679); + +(d) 'el subprocesador' significa cualquier procesador contactado mediante el importador de datos o mediante cualquier otro subprocesador del importador de datos quien acuerde recibir del importador de datos o de cualquier otro subprocesador de dicho importador los datos personales exclusivos que se pretenden utilizar en actividades de procesamiento que se llevarán acabo en nombre del exportador de datos después de la transferencia de acuerdo con sus instrucciones, las condiciones de las Cláusulas y las de el subcontrato por escrito; + +(e) 'la ley de protección de datos aplicable' se refiere a la legislación que protege los derechos fundamentales y las libertades de los individuos y, particularmente, su derecho a la privacidad con respecto al procesamiento de los datos personales aplicables al controlador de datos en el Estado Miembro en el cual se establece el exportador de datos; + +(f) 'medidas de seguridad técnicas y organizacionales' se refiere a aquellas medidas que se enfocan en proteger los datos contra una pérdida accidental o una destrucción ilegal, alteraciones, diseminación no autorizada o acceso, particularmente donde el procesamiento involucre la transmisión de datos a través de una red, y contra todo el resto de formas ilegales de procesamiento. + +#### Cláusula 2: Detalles de la transferencia +Los detalles de la transferencia y, en particular, de las categorías especiales de datos personales en donde sean aplicables se especifican en el Apéndice 1 que se encuentra más adelante, el cual forma una parte integral de las Cláusulas. + +#### Cláusula 3: Cláusula de beneficiario tercero +1. El titular de los datos podrá hacer valer la ley contra el exportador de datos en esta Cláusula, la Cláusula 4(b) a (i), la Cláusula 5(a) a (e), y de (g) a (j), la Cláusula 6(1) y (2), la Cláusula 8(2), y las Cláusulas 9 a 12 como beneficiario tercero. + +2. El titular de los datos podrá hacer valer la ley contra el importador de datos en esta Cláusula, la Cláusula 5(a) a (e) y (g), la Cláusula 6, Cláusula 7, Clúsula 8(2) y las Cláusulas 9 a 12, en los casos en donde el exportador de los datos haya desaparecido realmente o haya dejado de existir en la ley a menos de que alguna entidad de sucesión haya asumido las obligaciones legales integrales del exportador de datos mediante onctrato o mediante la operación legal, como resultado de que lo que asume en los derechos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos podrá hacer valor esto contra dicha entidad. + +3. El sujeto de los datos puede aplicar la ley en contra del subprocesador de esta Cláusula, la Cláusula 5(a) a (e) y (g), Cláusula 6, Cláusula 7, Cláusula 8(2) y Cláusulas 9 a 12, en casos en donde tanto el exportador como el importador de los datos hayan desaparecido realmente o dejado de existir en la ley o se hayan declarado insolventes, a menos de que cualquier entidad sucesora haya asumido todas las obligaciones del exportador de los datos contractualmente o conforme a derecho que resulte en la toma de derchos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos puede aplicar la ley en contra de dicha entidad. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas. + +4. Las partes no se oponen a que un titular de los datos se represente mediante una asociación o cualquier otro cuerpo si dicho titular así lo desea expresamente y si la ley nacional lo permite. + +#### Cláusula 4: Las obligaciones del exportador de los datos +El exportador de los datos acuerda y garantiza: + +(a) que el procesamiento, incluyendo la transferencia misma de los datos personales, se ha estado llevando a cabo y se seguirá haciendo de acuerdo con las disposiciones generales de la ley de protección de datos aplicable (y, cuando sea aplicable, se ha notificado a las autoridades relevantes del Estado Miembro en donde se establece el exportador de los datos) y no viola las disposiciones generales relevantes de dicho estado; + +(b) que se ha instruido y, a través de la duración de los servicios de procesamiento de datos personales, se instuirá al importador de los datos para procesar los datos personales transferidos únicamente en nombre del exportador de los datos de acuerdo con la ley de protección de datos personales y con las Cláusulas; + +(c) Que el importador de los datos proporcionará garantía suficiente con respecto a las medidas de seguridad técnicas y organizacionales especificadas en el Apéndice 2 descrito posteriormente; + +(d) que después de la valoración de los requisitos para la ley de protección de datos aplicable, las medidas de seguridad son adecuadas para proteger los datos personales contra la destrucción accidental o ilegal o contra la pérdida, alteración, divulgación no autorizada o acceso accidentales, particularmente en donde el procesamiento involucre la transmisión de datos a través de una red, y contra cualquier otra forma ilegal de procesamiento, y que estas medidas garantizan un nivel de seguridad adecuado para los riesgos que se presentan mediante el procesamiento y por la naturaleza de los datos que se protegerán con respecto a las tecnologías más recientes y el costo de su implementación; + +(e) que garantizará el cumplimiento con las medidas de seguridad; + +(f) que, si la transferencia involucra categorías especiales de datos, se ha informado o se informará previamente al titular de los datos, o se hará tan pronto como sea posible posteriormente, sobre que la transferencia de sus datos puede realizarse a un país tercero que no proporciona protección adecuada dentro de las estipulaciones de la Regulación General para la Protección de los Datos (EU 2016/679); + +(g) reenviar cualquier notificación que se recibe de un importador de datos o de cualquier subprocesador de acuerdo con la Cláusula 5(b) y la Cláusula 8(3) a la autoridad supervisora de protección de datos si el exportador de los datos decide continuar con la transferencia o levantar la suspeción; + +(h) poner a disposición una copia de las Cláusulas para los titulares de los datos por solicitud, con la exepción del Apéndice 2, y un resúmen descriptivo de las medidas de seguridad, así como una copia de cualquier contrato para los servicios de subprocesamiento que se tiene que hacer de acuerdo con las Cláusulas, a menos de que las Cláusulas o el contrato contengan información comercial, en cuyo caso se podrá eliminar dicha información comercial; + +(i) que, en caso de subprocesamiento, la actividad de procesamiento se llevará a cabo de acuerdo con la Cláusula 11 mediante un subprocesador que proporcione por lo menos el mismo nivel de protección para los datos personales y para los derechos del titual de los datos como importador de los mismos bajo las Cláusulas; y + +(j) que garantizará el cumplimiento con la Cláusula 4(a) a la (j). + +#### Cláusula 5: Obligaciones del importador de los datos +El importador de los datos acuerda y garantiza: + +(a) procesar los datos personales únicamente en nombre del exportador de los datos y en cumplimiento con sus instrucciones y con las Cláusulas; si no puede proporcionar dicho cumplimiento por cualquier razón, acuerda informar de manera oportuna al exportador de los datos de dicha incapacidad, en cuyo caso, el exportador de los datos tendrá derecho a suspender al trasnferencia de los mismos o de terminar el contrato; + +(b) que no hay razón para creer que la legislación aplicable a ello les previene de completar las instrucciones recibidas del exportador de datos y sus obligaciones contractuales y que en caso de un cambio a dicha legislación, el cual probablemente tenga un efecto adverso sobre las garantías y obligaciones que proporcionan las Cláusulas, se notificará oportunamente sobre el cambio al exportador de los datos tan pronto sea de su conocimiento, en cuyo caso, el exportador de los datos tendrá derecho para suspender la transferencia de los mismos y/o de terminar el contrato; + +(c) que ha implementado las medidas de seguridad técnicas y organizacionales especificadas en el Apéndice 2 antes de procesar los datos personales transferidos; + +(d) que notificará oportunamente al exportador de los datos sobre: + +(i) cualquier solicitud legalmente vinculante para la divulgación de los datos personales mediante una autoridad legal a menos de que se prohiba de otro modo, tal como una prohibición bajo leyes judiciales para preservar la confidencialidad de una investigación legal, + +(ii) cualquier acceso accidental o no autorizado, y + +(iii) cualquier solicitud recibida directamente de los titulares de los datos sin responder a dicha solicitud, a menos de que se haya autorizado de otra forma; + +(e) lidiar oportuna y adecuadamente con todas las investigaciones de exportador de datos que se relacionen con su procesamiento de los datos personales sujetos a transferencia y cumplir con los consejos de la autoridad supervisante con respecto al procesamiento de los datos transferidos; + +(f) bajo solicitud del exportador de los datos, emitir sus medios de procesamiento de datos para su auditoría de actividades de procesamiento que se cubren en las cláusulas, lo cual se deberá llevar a cabo por medio del exportador de los datos o mediante un cuerpo de inspección compuesto de miembros independientes y en posesión de las certificaciones profesionales requeridas y ligadas por deber o confidencialidad, seleccionadas por el exportador de los datos, cuando sea aplicable, de acuerdo con la autoridad supervisora; + +(g) poner a disposición para el titular de los datos bajo solicitud una copia de las Cláusulas, o de cualquier contrato existente para el subprocesamiento, a menos de que dichas Cláusulas o contrato contengan información compercial, en cuyo caso pudiera eliminar dicha información comercial, con excepción del Apéndice 2, el cual se deberá reemplazar con un resumen descriptivo de las medidas de seguridad en esos casos donde el titular de los datos no puede obtener una copia del exportador de los datos; + +(h) que, en caso de subprocesamiento, se ha informado previamente al exportador de los datos y se ha obtenido una aprobación previa por escrito; + +(i) que los servicios de procesamiento del subprocesador se llevarán acabo de acuerdo con la Cláusula 11; y + +(j) enviar al exportador de los datos oportunamente una copia de cualquier contrato de subprocesamiento que se concluya bajo las Cláusulas. + +#### Cláusula 6: Responsabilidades +1. Las partes concuerdan que cualquier titular de los datos que haya sufrido daños como resultado de cualquier violación a las obligaciones descritas en la Cláusula 3 o en la Cláusula 11 por parte de cualquier subprocesador tiene derecho a recibir una compensación del exportador de los datos por dicho daño sufrido. + +2. Si algún titular de los datos no puede presentr un reclamo de indemnización en contra del exportador de los datos de acuerdo con el párrafo 1, la cual se derive de una violación por parte del importador de los datos o de su subprocesador o de cualquiera de sus obligaciones que se describen en la Cláusula 3 o en la Cláusula 11, debido a que el exportador de los datos ha desaparecido realmente o dejado de existir ante la ley, o se ha declarado insolvente, el importador de los datos acuerda que el titular de los datos puede emitir un reclamo contra el importador de los datos como si fuera el exportador de los mismos, a menos de que alguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador de los datos contractualmente o mediante la aplicación de la ley, en cuyo caso, el sujeto de los datos puede hacer valer sus derechos contra dicha entidad. El importador de los datos podría no depender de que exista una violación por parte de un subprocesador de sus obligaciones para evitar las suyas propias. + +3. Si un titular de los datos no puede presentar un reclamo en contra del exportador o importador de los datos a los cuales se hace referencia en los párrafos 1 y 2, derivado de una violación por parte del subprocesador o por cualquiera de sus obligaciones explicadas en la Cláusula 2 o en la Cláusula 11 ya que ambos, importador y exportador, hayan desaparecido realmente o dejado de existir ante la ley, o se hayan declarado insolventes, el subprocesador acuerda que el titular de los datos podrá emitir un reclamo contra el subprocesador de los datos con respecto a sus propias operaciones de procesamiento bajo las Cláusulas como si fuera el exportador o importador de los mismos, a menos de que cualquier entidad sucesora haya asumido las obligaciones íntegras del exportador o importador de los datos contractualmente o por aplicación de la ley, en cuyo caso, el titular de los datos puede hacer valer sus derechos en contra de dicha entidad. La responsabilidad del subprocesador deberá limitarse a sus propias operaciones de procesamiento bajo las Cláusulas. + +#### Cláusula 7: Mediación y Jurisdicción +1. El iimportador de los datos acuerda que si el titular de los datos apelase en contra de sus derechos de beneficiario tercero y/o reclama una compensación por daños bajo las Cláusulas, el importador de los datos aceptará la decisión del titular de los datos: + +(a) para referir la disputa de mediación, mediante una persona independiente o, cuando sea aplicable, mediante la autoridad supervisora; + +(b) referir la disputa en las cortes del Estado Miembro en el cual se establece el exportador de los datos. + +2. Las partes acuerdan que la elección que haga el titular de los datos no perjudicará sus derechos sustantivos o procesales para buscar remedios de acuerdo con otras disposiciones de la ley internacional o nacional. + +#### Cláusula 8: Cooperación con las autoridades supervisantes +1. El exportador de los datos acuerda depositar una copia de este contrato con la autoridad supervisora si así lo requiere o si dicho depósito se requiere bajo la ley de protección de datos aplicable. + +2. Las partes concuerdan que la autoridad supervisora tiene el derecho de conducir una auditoría del importador de los datos, y de cualquier subprocesador, la cual tiene el mismo alcance y está sujeta a las mismas condiciones que aplcarían en una auditoría del exportador de los datos bajo la ley de protección de datos aplicable. + +3. El importador de los datos deberá informar de manera oportuna al exportador de los datos acerca de la existencia de la legislación aplicable a éste o a cualquier subprocesador, previniendo la conducción de una auditoría al importador de los datos o a cualquier subprocesador de acuerdo con el párrafo 2. En dado caso, el exportador de los datos tenga derecho a tomar las medidas previstas en la Cláusula 5(b). + +#### Cláusula 9: Ley Aplicable. +Las Cláusulas deberán regirse por medio de la ley del Estado Miembro en el cual se establece el exportador de los datos. + +#### Cláusula 10: Variación del contrato +Las partes se comprometen a no variar o modificar las Cláusulas. Esto no impide que las partes agreguen cláusulas sobre los asuntos relacionados con los negocios conforme se requieran mientras que éstas no contradigan la Cláusula. + +#### Cláusula 11: Subprocesamiento +1. El importador de los datos no deberá subcontratar ninguna de sus operaciones de procesamiento que se realicen en nombre del exportador de los datos bajo las Cláusulas sin el consentimiento previo y por escrito del exportador de los datos. En caso de que el importador de los datos subcontrate sus obligaciones debajo de las Cláusulas, con el consentimiento del exportador de los datos, deberá hacerlo únicamente por medio de un contrato por escrito con el subprocesador, el cual imponga las mismas obligaciones en el subprocesador que se impusieron en el importador de los datos bajo las Cláusulas. Donde sea que el subprocesador incumpla con sus obligaciones de protección de datos bajo dicho contrato por escrito, el importador de los datos deberá ser plenamente responsable del exportador de los datos por el cumplimiento de las obligaciones del subprocesador bajo dicho contrato. + +2. El contrato escrito previo entre el importador de los datos y el subprocesador también deberá proporcionar una cláusula de terceros beneficiarios de acuerdo con lo asentado en la Cláusula 3 para los casos en donde el titular de los datos no pueda preentar una reclamación de compensación como se refiere en el párrafo 1 de la Cláusula 6 en contra del exportador o del importador de los datos debido a que han desaparecido realmente o han dejado de existir ante la ley o se hayan declarado insolventes y ninguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador o importador de los datos contractualmente o mediante la ley aplicable. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas. + +3. Las disposiciones que se relacionan con los aspectos de protección de datos para el subprocesamiento del cntracto al cual se refiere en el párrafo 1 deberán regirse por la ley del Estado Miembro en el cual se establezca el exportador de los datos. + +4. El exportador de los datos deberá mantener una lista de contratos de subprocesamiento que se celebren bajo las Cláusulas y que el importador de los datos notifique de acuerdo con la Cláusula 5 (j), la cual se debe actualizar por lo menos una vez al año. La lista deberá estar disponible para la autoridad supervisora de protección de datos del exportador de los datos. + +#### Cláusula 12: Obligaciones después de la terminación de los servicios de procesamiento de datos personales +1. Las partes acuerdan que, en la terminación de la prestación de los servicios de procesamiento de datos, el importador y subprocesador de los mismos deberá, a elección del exportador, regresar todos los datos personales transferidos y las copias de los mismos al exportador de los datos o deberá destruir todos los dtos personales y certificar ante el exportador de los datos que así lo ha hecho, a menos de que la legislación impuesta en el importador de los datos impida que regrese o destrulla todos o parte de los datos personales transferidos. En dado caso, el importador de los datos justifica que garantizará la confidencialidad de los datos personales transferidos y que ya no procesará activamente dichos datos personales. + +2. El importador de los datos y el subprocesador garantizan que, bajo solicitud del exportador de los datos y/o de la autoridad supervisora, emitirán sus instalaciones de procesamiento de datos para auditoría de las medidas descritas en el párrafo 1. + +### Apéndice 1 para las Cláusulas Contractuales Estándar +Exportador de los datos: El cliente es el exportador de los datos. + +**Importador de los datos:** El importador de los datos es GitHub, Inc., un productor global de software y servicios. + +**Titulares de los datos:** Los titulares de los datos incluyen a los representantes de los exportadores de datos y a los usuarios finales, incluyendo a los empleados, consultores, colaboradores, y clientes del exportador de los datos. Los titulares de los datos también podrían incluir a aquellos individuos que intentan comunicarse o transferir información personal a los usuarios de los servicios proporcionados por el importador de los datos. GitHub reconoce que, dependiendo de el uso del Servicio que tenga el Cliente, éste puede elegir el incluir los datos personales de cualquiera de los siguientes tipos de titulares de datos en los Datos Personales del Cliente: + +- Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos; +- Dependientes de los antes listados; +- Consultores/personas de contacto del exportador de datos (personas naturales) o los empleados, consultores o trabajadores temporales de la entidad legal de las personas de contacto/consultores (actuales, futuros, pasados); +- Usuarios (por ejemplo, clientes, pacientes, visitantes, etc.) y otros titulares de los datos que sean usuarios de los servicios del exportador de los datos; +- Socios, interesados o individuos que colaboren, se comuniquen o interactuen activamente de otra forma con los empleados del exportador de los datos y/o que utilicen herramientas de comunicación tales como apps y sitios web que proporcione el exportador de los datos; +- Los interesados o los individuos que interactuen pasivamente con el exportador de los datos (por ejemplo, porque son el titular de una inspección, investigación o que se mencionan en documentos o en correspondencia dirigida a o proviniente del exportador de los datos); o +- Profesionales con privilegios de profesionista (por ejemplo, doctores, abogados, notarios, trabajadores religiosos, etc.). + +**Categorías de los datos:** Los datos personales transferidos que se incluyen en los correos electrónicos, documentos y en otros tipos de datos en forma electrónica o en el contexto del Servicio. GitHub reconoce que, dependiendo del uso que el Cliente de al Servicio, éste puede elegir incluir datos personales de cualquiera de las siguientes categorías dentro de los Datos Personales del Cliente: +- Datos de autenticación (por ejemplo, nombre de usuario, correo electrónico, contraseña); +- Información de contacto (por ejemplo, correo electrónico); +- Números de identificación única y firmas (direcciones IP, identificadores únicos en cookies de rastreo o tecnologías similares). +- Otra información de identificación única. Los titulares de los datos podrían incluir más datos tales como nombres reales, imágenes de avatar, y otra información personal; + +**Categorías especiales de los datos (si corresponde):** El importador de los datos no recolecta procesa intencionalmente ninguna categoría especial de datos para llevar a cabo sus servicios para el exportador de los mismos. + +Sin embargo, ya que el importador de los dtos proporciona servicios de almacenamiento y no controla las categorías de los datos que almacena, el exportador de los datos podría elegir transferir las categorías especiales de los datos. Por consiguiente, el exportador de los datos es el único responsable de garantizar que cumple con todas las obligaciones impuestas por las leyes y regulaciones aplicables relacionadas con la recolección y procesamiento de cualquier categoría de datos, incluyendo el obtener el consentimiento explícito del titular de los datos antes de procesar datos personales sensibles. + +**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontratistas: De acuerdo con la DPA, el importador de los datos podrá contratar a otras compañías para proporcionar servicios limitados en nombre del importador de los datos, tales como proporcionar soporte al cliente. Cualquier subcontratista de este tipo tendrá permiso de obtener los Datos Personales del Cliente únicamente para entregar los servicios para los cuales lo contrató el importador de los mismos, y se les prohibe utilizar los Datos Personales del Cliente para cualquier otro propósito. + +### Apéndice 2 para las Cláusulas Contractuales Estándar +Descripción de las medidas de seguridad técnicas y organizacionales implementadas por el importador de los datos de acuerdo con las Cláusulas 4(d) y 5(c): + +**1. Personal.** El personal del importador de los datos no procesará los Datos Personales del Cliente sin autorización. El personal está obligado a mantener la confidencialidad de cualquier Dato Personal del Cliente y esta obligación continúa aún después de que la relación termine. + +**2. Contacto de Privacidad de los Datos.** El director de privacidad para el importador de los datos puede contactarse en la siguiente dirección: GitHub, Inc. Atención: Privacidad 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA + +**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction. + +La Firma de GitHub, Inc. se muestra a continuación. + +Se firman las Cláusulas Contractuales Estándar, Apéndice 1 y Apéndice 2 en nombre del importador de los datos + +![Impresión de pantalla 2020-07-20 a las 2 20 29 PM](/assets/images/help/site-policy/docusign-signature.png) + +Lynn Hashimoto, Jefe de Producto & Regulación Legal + +GitHub, Inc. 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 index aad0b6f2eb..66e80c3054 100644 --- a/translations/es-ES/content/github/site-policy/github-privacy-statement.md +++ b/translations/es-ES/content/github/site-policy/github-privacy-statement.md @@ -192,7 +192,7 @@ Del mismo modo, los proyectos en GitHub pueden incluir Información Personal de #### 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. +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](/organizations/managing-organization-settings/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. @@ -321,7 +321,7 @@ En el improbable caso de que surja una disputa entre tú y GitHub con respecto a ### 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. +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/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) o a revisar el repositorio de nuestra política del sitio con frecuencia. ### Licencia 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 index 6afe6495eb..46a063266c 100644 --- 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 @@ -13,7 +13,7 @@ topics: - legal --- -Fecha de entrada en vigor: **29 de enero de 2021** +Effective date: **April 2, 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. Para este propósito, proporcionamos esta página, la cual detalla [nuestros subprocesadores](#github-subprocessors) y cómo utilizamos las [cookies](#cookies-on-github). @@ -33,7 +33,6 @@ Cuando compartimos tu información con subprocesadores de terceros, como nuestro | 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 | | Sentry.io | Proveedor de monitoreo de aplicaciones | Estados Unidos | Estados Unidos | diff --git a/translations/es-ES/content/github/site-policy/index.md b/translations/es-ES/content/github/site-policy/index.md index 384fa7c7d7..c77a63708e 100644 --- a/translations/es-ES/content/github/site-policy/index.md +++ b/translations/es-ES/content/github/site-policy/index.md @@ -16,6 +16,7 @@ topics: {% 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-agreement-non-enterprise-customers %} {% link_in_list /global-privacy-practices %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} {% link_in_list /github-sponsors-additional-terms %} 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 index 9124b3d237..57e78fb8a9 100644 --- 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 @@ -24,7 +24,9 @@ Puedes configurar una meta para tus patrocinios. Para obtener más información, ### 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)". +{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)." + +It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. ### Pagos de patrocinios @@ -34,5 +36,9 @@ Puedes configurar una meta para tus patrocinios. Para obtener más información, 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)". +### Intercambiar opiniones acerca de {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.feedback %} + ### Leer más - "[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 index 743806c5f5..118f46d086 100644 --- 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 @@ -37,7 +37,7 @@ Para ser elegible para el {% data variables.product.prodname_matching_fund %}, d ### 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). +{% data reusables.sponsors.feedback %} ### Leer más - "[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/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 index 0642129e9e..52bd94849b 100644 --- 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 @@ -15,6 +15,8 @@ Tus patrocinadores pueden elegir si desean recibir actualizaciones por correo el 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)". +You can also contact any one-time sponsors who contributed within the last 30 days and enabled updates. + ### Comunicarse con tus patrocinadores {% data reusables.sponsors.navigate-to-sponsors-dashboard %} 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 index cf20f10f12..313b2fe767 100644 --- 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 @@ -25,7 +25,7 @@ topics: {% 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 /managing-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 %} 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 index c05c140159..a11e713eae 100644 --- 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 @@ -13,6 +13,12 @@ Puedes configurar una meta de financiamiento para tu cuenta patrocinada y compar 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. +{% note %} + +**Note:** Goals are intended to help people track momentum so only monthly sponsors contribute toward your goal. + +{% endnote %} + ### Configurar una meta {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md new file mode 100644 index 0000000000..eaa3190c74 --- /dev/null +++ b/translations/es-ES/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md @@ -0,0 +1,45 @@ +--- +title: Managing your sponsorship tiers +intro: 'Puedes agregar un nuevo nivel de patrocinio o editar o retirar un nivel existente.' +redirect_from: + - /articles/changing-your-sponsorship-tiers + - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +topics: + - sponsors +--- + +### 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 %} + +### Enabling tiers with custom amounts + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.enable-custom-amounts %} + +### Disabling tiers with custom amounts + +You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired. 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 index c98f5592f0..998ebf0c59 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero versions: free-pro-team: '*' topics: 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 index 27d3551022..f5846546d3 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +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 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 index e62d3b892e..5c3fd75c5e 100644 --- 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 @@ -48,6 +48,7 @@ Para unirte a {% data variables.product.prodname_sponsors %} como un colaborador {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Emitir tu información bancaria 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 index 72d6a37371..1b85ae5a59 100644 --- 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 @@ -48,6 +48,7 @@ Una vez que {% data variables.product.prodname_dotcom %} revise tu aplicación, {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Emitir tu información bancaria 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 index 1308cf5441..2a6eda44cb 100644 --- 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 @@ -1,6 +1,6 @@ --- 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.' +intro: 'You can make a one-time or monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' redirect_from: - /articles/sponsoring-a-developer - /articles/sponsoring-an-open-source-contributor @@ -24,11 +24,11 @@ Puedes patrocinar una cuenta en nombre de tu cuenta de usuario para invertir en - 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 quiere pagar por factura, [contáctanos](https://support.github.com/contact/org-sponsors-waitlist). +You use your normal payment method to sponsor an account on {% data variables.product.product_name %}. Si tu organización quiere pagar por 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 %} +When you sponsor an account the change is effective immediately, unless you are sponsoring on behalf of an organization that pays by invoice. {% data reusables.sponsors.prorated-sponsorship %} Your sponsorship is included in the next scheduled payment to the sponsored account. {% data reusables.sponsors.manage-updates-for-orgs %} @@ -53,6 +53,7 @@ Antes de que puedas patrocinar una cuenta, debes tener una dirección de correo - 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 una organización, a la derecha del nombre de esta, haz 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.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} 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 index c6f8b28739..c83fbd2e0d 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/sponsoring-open-source-developers - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers 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 index 1a66878f1a..642f36c299 100644 --- 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 @@ -1,89 +1,94 @@ --- -title: About the dependency graph -intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' +title: 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: '*' + enterprise-server: '<=2.22' +topics: + - repositories --- -### Dependency graph availability +### Disponibilidad de la gráfica de dependencias -The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} +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 %} -### About the dependency graph +### Acerca del gráfico de dependencias -The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: +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" %}: -- Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} +- 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 %} -When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. +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" %} -When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. 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)." +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 %} -### Dependencies included +### Dependencias que se incluyen -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +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: -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- 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 -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +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" %} -### Dependents included +### Dependientes incluídos -For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} +Para 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 %} -### Using the dependency graph +### Utiizar la gráfica de dependencias -You can use the dependency graph to: +Puedes utilizar la gráfica de dependencias para: -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} -- See information about vulnerable dependencies in pull requests. 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 %} +- 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 %} -### Enabling the dependency graph +### Habilitar la gráfica de dependencias -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Para 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" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if enterpriseServerVersions 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" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} 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 %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +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 %}. -### Supported package ecosystems +### Ecosistemas de paquetes compatibles -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +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 %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +{% if currentVersion == "free-pro-team@latest" %}Los ecosistemas que se listan a continuación son compatibles con la gráfica de dependencias, con las {% data variables.product.prodname_dependabot_alerts %}, y con las {% data variables.product.prodname_dependabot_security_updates %}.{% endif %} +| +{% if currentVersion ver_gt "enterprise-server@2.21" %}Los ecosistemas que se listan a continuación son compatibles con la gráfica de dependencias y con las {% data variables.product.prodname_dependabot_alerts %}.{% 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`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**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 +### Leer más -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia -- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} +- "[Grá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" %} +- "[Ver la información de tu organización](/organizations/collaborating-with-groups-in-organizations/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 index f39def9710..366b33f8ac 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/accessing-basic-repository-data versions: 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 index 4610567d54..b0514875c1 100644 --- 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 @@ -5,7 +5,7 @@ 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: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index f08ea2bc59..719781a031 100644 --- 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 @@ -68,7 +68,7 @@ Para los repositorios públicos, la vista de dependientes muestra cómo otros re 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)". +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](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -109,7 +109,7 @@ Si un archivo de manifiesto o de bloqueo no se procesa, sus dependencias se omit ### Leer más - "[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 la información de tu organización](/organizations/collaborating-with-groups-in-organizations/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"

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 index cd4d90fdf5..441e811405 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/understanding-connections-between-repositories versions: 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 index 62f23be68e..fcdeccf257 100644 --- 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 @@ -11,7 +11,7 @@ topics: 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 %}. +If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)." ### Emitir un ticket utilizando el {% data variables.contact.support_portal %} 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 index 5732551eae..8bcb104b48 100644 --- a/translations/es-ES/content/github/writing-on-github/creating-gists.md +++ b/translations/es-ES/content/github/writing-on-github/creating-gists.md @@ -33,7 +33,7 @@ Si el administrador de tu sitio ha inhabilitado el modo privado, también puedes 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. +- You subscribe to a gist, by clicking **Subscribe** at the top of any gist. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} @@ -55,13 +55,15 @@ Git admite la asignación de archivos GeoJSON. Estas asignaciones se muestran co ### Crear un gist -También puedes arrastrar y soltar un archivo de texto desde tu escritorio directamente en el editor de gist. +Follow the steps below to create a 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 %}. +Alternatively, you can drag and drop a text file from your desktop directly into the editor. + {% endnote %} {% endif %} @@ -69,7 +71,7 @@ También puedes crear un gist si utilizas el {% data variables.product.prodname_ 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) +4. Type the text of your gist into the gist text box. ![Cuadro de texto para el gist](/assets/images/help/gist/gist_text_box.png) 5. Opcionalmente, para crear un gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}, da clic en {% octicon "triangle-down" aria-label="The downwards triangle icon" %} y luego en **Crear gist {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}**. ![Menú desplegable para seleccionar la visibilidad de un gist]{% 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 %} 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 index 63d06647bc..89a6332bdb 100644 --- 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 @@ -1,7 +1,7 @@ --- title: Editar y compartir contenido con gists intro: '' -mapTopic: true +mapTopic: verdadero redirect_from: - /categories/23/articles/ - /categories/gists/ 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 index b29eb5eee4..7fbb9e2f3a 100644 --- 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 @@ -5,7 +5,7 @@ redirect_from: - /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: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '*' 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 index 6ce3ec040c..34a24c3e57 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/working-with-advanced-formatting versions: 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 index b83cce9e9d..c211c9df3e 100644 --- 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 @@ -1,7 +1,7 @@ --- 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: true +mapTopic: verdadero redirect_from: - /articles/working-with-saved-replies versions: diff --git a/translations/es-ES/content/index.md b/translations/es-ES/content/index.md index 2e8cfbb529..36e535d714 100644 --- a/translations/es-ES/content/index.md +++ b/translations/es-ES/content/index.md @@ -13,5 +13,43 @@ featuredLinks: - /github/getting-started-with-github/managing-remote-repositories - /github/working-with-github-pages versions: '*' +children: + - github + - admin + - organizations + - code-security + - acciones + - paquetes + - developers + - rest + - graphql + - insights + - debates + - comunidades + - páginas + - educación + - desktop + - early-access +externalProducts: + cli: + id: cli + name: CLI de GitHub + href: 'https://cli.github.com/manual' + external: verdadero + atom: + id: átomo + name: Atom + href: 'https://atom.io/docs' + external: verdadero + electron: + id: electron + name: Electron + href: 'https://electronjs.org/docs' + external: verdadero + codeql: + id: codeql + name: 'CodeQL' + href: 'https://codeql.github.com/docs' + external: verdadero --- 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 index a197db333d..a473d34dc3 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero versions: enterprise-server: '*' --- 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 index e0dde80446..1b60b5dc95 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero versions: enterprise-server: '*' --- 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 index 8e98d085ff..f512c60d89 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero redirect_from: - /github/installing-and-configuring-github-insights/managing-data-in-github-insights versions: diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md new file mode 100644 index 0000000000..76ab6c5c68 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -0,0 +1,33 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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](/organizations/managing-peoples-access-to-your-organization-with-roles/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/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md new file mode 100644 index 0000000000..5e03ae0d08 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -0,0 +1,49 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +### 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/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md new file mode 100644 index 0000000000..069325b08e --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -0,0 +1,26 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md new file mode 100644 index 0000000000..0ab1d8452c --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -0,0 +1,34 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/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: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000..fdf58e7675 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md @@ -0,0 +1,28 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch +topics: + - organizations + - equipos +--- + +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 %} + +### Leer más + +{% 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/organizations/collaborating-with-groups-in-organizations/index.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/index.md new file mode 100644 index 0000000000..30961b7443 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/index.md @@ -0,0 +1,22 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000..3f34853cf1 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -0,0 +1,50 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + - "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/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](/organizations/managing-organization-settings/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/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md new file mode 100644 index 0000000000..4d3f2cb638 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -0,0 +1,49 @@ +--- +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 + - /github/building-a-strong-community/about-team-discussions + - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidad +--- + +{% 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](/organizations/collaborating-with-your-team/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)". + +### Leer más + +- "[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](/organizations/collaborating-with-your-team/creating-a-team-discussion)" +- "[Editar o eliminar un debate de equipo](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/es-ES/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/es-ES/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md new file mode 100644 index 0000000000..d49c18878d --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md @@ -0,0 +1,30 @@ +--- +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 + - /github/building-a-strong-community/creating-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidad +--- + +{% data reusables.organizations.team-discussions-permissions %}Para obtener más información, consulta "[Acerca de los debates del equipo](/organizations/collaborating-with-your-team/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) + +### Leer más + + - "[Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Editar o eliminar un debate de equipo](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" + - "[Anclar un debate del equipo](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/es-ES/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/es-ES/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000..13789c4757 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,28 @@ +--- +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 + - /github/building-a-strong-community/editing-or-deleting-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidad +--- + +{% 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) + +### Leer más + + - "[Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Crear un debate de equipo](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Anclar un debate del equipo](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/es-ES/content/organizations/collaborating-with-your-team/index.md b/translations/es-ES/content/organizations/collaborating-with-your-team/index.md new file mode 100644 index 0000000000..f8cc41a7c4 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-your-team/index.md @@ -0,0 +1,19 @@ +--- +title: Colaborar con tu equipo +intro: 'Dentro de una organización, tu equipo puede trabajar en varios proyectos usando los debates de equipo.' +redirect_from: + - /articles/collaborating-with-your-team + - /github/building-a-strong-community/collaborating-with-your-team + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidad +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/es-ES/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md new file mode 100644 index 0000000000..fa0caf5625 --- /dev/null +++ b/translations/es-ES/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +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 + - /github/building-a-strong-community/pinning-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidad +--- + +{% 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) + +### Leer más + + - "[Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Crear un debate de equipo](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Editar o eliminar un debate de equipo](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000..58ba1526e4 --- /dev/null +++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,26 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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. + +### Leer más + +- "[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/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md new file mode 100644 index 0000000000..073c9d9108 --- /dev/null +++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -0,0 +1,16 @@ +--- +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.' +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000..1260ad9f32 --- /dev/null +++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,25 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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 %} + +### Leer más + +- "[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/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000..902e105ff8 --- /dev/null +++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,64 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +### 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 %} + +### Leer más + +- "[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/organizations/index.md b/translations/es-ES/content/organizations/index.md new file mode 100644 index 0000000000..928b4e4ae9 --- /dev/null +++ b/translations/es-ES/content/organizations/index.md @@ -0,0 +1,32 @@ +--- +title: Organizaciones y equipos +shortTitle: Organizaciones +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 + - /github/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% link_with_intro /collaborating-with-groups-in-organizations %} +{% link_with_intro /managing-membership-in-your-organization %} +{% link_with_intro /managing-peoples-access-to-your-organization-with-roles %} +{% link_with_intro /organizing-members-into-teams %} +{% link_with_intro /collaborating-with-your-team %} +{% link_with_intro /managing-access-to-your-organizations-repositories %} +{% link_with_intro /managing-access-to-your-organizations-project-boards %} +{% link_with_intro /managing-access-to-your-organizations-apps %} +{% link_with_intro /managing-organization-settings %} +{% link_with_intro /restricting-access-to-your-organizations-data %} +{% link_with_intro /keeping-your-organization-secure %} +{% link_with_intro /managing-saml-single-sign-on-for-your-organization %} +{% link_with_intro /granting-access-to-your-organization-with-saml-single-sign-on %} +{% link_with_intro /managing-git-access-to-your-organizations-repositories %} +{% link_with_intro /migrating-to-improved-organization-permissions %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md new file mode 100644 index 0000000000..cffddff455 --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/index.md @@ -0,0 +1,24 @@ +--- +title: Mantener segura tu organización +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.' +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure + - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000..0b3152f225 --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,76 @@ +--- +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 %}' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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 {% if currentVersion == "github-ae@latest" %}"[Restringir el tráfico de red para tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)". {% else %}"[Requerir una configuración 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)."{% endif %} + +### 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 + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-actions.ip-allow-list-hosted-runners %} + +{% else %} + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +{% endif %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000..9d248979a0 --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,143 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +topics: + - organizations + - equipos +--- + +### 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" %}Si tienes una licencia para {% data variables.product.prodname_GH_advanced_security %}, entonces también podrás administrar el acceso a estas características. {% 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 %} + +La página que se muestra te permite habilitar o inhabilitar todas las características de seguridad y de análisis para los repositorios de tu organización. + +{% if currentVersion == "free-pro-team@latest" %}Si tu organización pertenece a una empresa que tiene una licencia para {% data variables.product.prodname_GH_advanced_security %}, la págna también contendrá opciones para habilitar e inhabilitar las características de {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %}Si tienes una licencia para {% data variables.product.prodname_GH_advanced_security %}, la página también contendrá opciones para habilitar e inhabilitar las características de {% data variables.product.prodname_advanced_security %}. Cualquier repositorio que utilice {% data variables.product.prodname_GH_advanced_security %} se listará en la parte inferior de la página.{% endif %} + +{% if currentVersion == "github-ae@latest" %}La página también contendrá opciones para habilitar e inhabilitar las características de la {% data variables.product.prodname_advanced_security %}.{% endif %} + +### Habilitar o inhabilitar una característica para todos los repositorios existentes + +Puedes habilitar o inhabilitar las características para todos los repositorios. {% if currentVersion == "free-pro-team@latest" %}El impacto de tus cambios en los repositorios de tu organización se determina de acuerdo con su visibilidad: + +- **Gráfica de dependencias** - Tus cambios solo afectan a repositorios privados porque la característica siempre está habilitada para los repositorios públicos. +- **{% data variables.product.prodname_dependabot_alerts %}** - Tus cambios afectan a todos los repositorios. +- **{% data variables.product.prodname_dependabot_security_updates %}** - Tus cambios afectan a todos los repositorios. +- **{% data variables.product.prodname_GH_advanced_security %}** - Tus cambios afectan únicamente a los repositorios privados, ya que la {% data variables.product.prodname_GH_advanced_security %} y las características relacionadas siempre se encuentran habilitadas para los repositorios públicos. +- **{% data variables.product.prodname_secret_scanning_caps %}** - Tus cambios afectan únicamente a los repositorios privados en donde la {% data variables.product.prodname_GH_advanced_security %} también se encuentra habilitada. El {% data variables.product.prodname_secret_scanning_caps %} siempre se encuentra habilitado para los repositorios públicos.{% 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)". +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %}El control para "{% data variables.product.prodname_GH_advanced_security %}" se encontrará inhabilitado si no tienes plazas disponibles en tu licencia de {% data variables.product.prodname_GH_advanced_security %}.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% if currentVersion == "github-ae@latest" %} + ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +3. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} +4. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% endif %} + {% if currentVersion == "github-ae@latest" %} +3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Botón para habilitar característica para todos los repositorios elegibles de la organización](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} + + {% data reusables.security.displayed-information %} + +### Habilitar o inhabilitar una característica automáticamente cuando se agregan repositorios nuevos + +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)". +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% if currentVersion == "github-ae@latest" %} + ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Permitir que el {% data variables.product.prodname_dependabot %} acceda a las dependencias privadas + +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. Para hacerlo, el {% data variables.product.prodname_dependabot %} debe tener acceso a todos los archivos de dependencia que sean el objetivo. Habitualmente, las actualizaciones de versión fallarán si una o más dependencias son inaccesibles. Para obtener más información, consulta la sección "[Acerca de las actualizaciones de versión del {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)". + +Predeterminadamente, el {% data variables.product.prodname_dependabot %} no puede actualizar las dependencias que se ubican en los repositorios o en los registros de paquetes 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. + +Si tu código depende de paquetes en un registro privado, puedes permitir que el {% data variables.product.prodname_dependabot %} actualice las versiones de estas dependencias si configuras esto a nivel del repositorio. Puedes hacer esto si agregas los detalles de autenticación al archivo _dependabot.yml_ para el repositorio. 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#configuration-options-for-private-registries)". + +Para permitir que el {% data variables.product.prodname_dependabot %} acceda a un repositorio privado de {% data variables.product.prodname_dotcom %}: + +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 "Acceso del {% data variables.product.prodname_dependabot %} a repositorios privados", haz clic en **Agregar repositorios privados** o **Agregar repositorios internos y privados**. ![Botón para agregar repositorios](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. Comienza a teclear el nombre del repositorio que quieras permitir. ![Botón para agregar repositorios](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Haz clic en el repositorio que quieras permitir. + +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. ![Botón "X" para eliminar un repositorio](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### Eliminar el acceso a {% data variables.product.prodname_GH_advanced_security %} desde los repositorios individuales de una organización + +Puedes administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} para un repositorio desde su pestaña de "Configuración". 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)". Sin embargo, también puedes inhabilitar las características de la {% data variables.product.prodname_GH_advanced_security %} para un reositorio desde la pestaña de "Configuración" de la organización. + +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. Para encontrar una lista de todos los repositorios de tu organización que tengan habilitada la {% data variables.product.prodname_GH_advanced_security %}, desplázate hasta la sección "repositorios con {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) La tabla lista la cantidad de confirmantes únicos para cada repositorio. Esta es la cantidad de plazas que puedes liberar en tus licencias si eliminas el acceso a {% data variables.product.prodname_GH_advanced_security %}. El tamaño de tu licencia se muestra para las licencias a nivel organizacional. Para obtener más información, consulta la sección "[Acerca de las licencias para {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)". +1. Para eliminar el acceso a la {% data variables.product.prodname_GH_advanced_security %} desde un repositorio y liberar plazas que utilice cualquier confirmante y que son únicas en ese repositorio, haz clic en el {% octicon "x" aria-label="X symbol" %} adyacente. +1. En el diálogo de confirmación, da clic en **Eliminar repositorio** para eliminar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %}. + +{% note %} + +**Nota:** Si eliminas el acceso de un repositorio a la {% data variables.product.prodname_GH_advanced_security %}, deberás comunicarte con el equipo de desarrollo afectado para que sepan que este cambio se hizo apropósito. Esto garantiza que no pierdan tiempo en depurar las ejecuciones fallidas del escaneo de código. + +{% endnote %} + +{% endif %} + +### Leer más + +- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" +- "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Mantener tus dependencias actualizadas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}{% if currentVersion != "github-ae@latest" %} +- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[Administrar las vulnerabilidades en tus dependencias de proyecto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..1d4e9567bc --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,23 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +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/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..2971ee1fba --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,80 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +### 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](/organizations/keeping-your-organization-secure/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. + +### Leer más + +- "[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/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000..3f838e8323 --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,31 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +### 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](/organizations/managing-peoples-access-to-your-organization-with-roles/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/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000..98b885a861 --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,643 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +### 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" %} +| [`cuenta`](#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)". | +| [`facturación`](#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. | +| [`gancho`](#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. | +| [`propuesta`](#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 con listar aplicaciones en {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contiene todas las actividades relacionadas con administrar 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 "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-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" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`paquetes`](#packages-category-actions) | Contiene todas las actividades relacionadas con el {% data variables.product.prodname_registry %}.{% endif %}{% 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" or currentVersion == "github-ae@latest" %} | | +| [`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" or currentVersion == "github-ae@latest" %} +| [`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 %} +| [`equipo`](#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. Para recuperar eventos de Git, utiliza mejor la API de REST. Para obtener más información, consulta las "[acciones de la categoría `git`](#git-category-actions)". +{% 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 %} + +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. + +{% 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 %} + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% 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 | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | 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 | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | Se activa cuando un propietario de organización habilita las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %}nuevos. | + +#### Acciones de la categoría `dependabot_security_updates` + +| Acción | Descripción | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | 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 | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | 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 | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | 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 | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | 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 | +| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- | +| `actualización` | 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 | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `actualización` | 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" or currentVersion ver_gt "enterprise-server@2.21" %} +#### acciones de la categoría `enterprise` + +{% data reusables.actions.actions-audit-events-for-enterprise %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### acciones de la categoría `environment` + +| Acción | Descripción | +| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create_actions_secret` | Se activa cuando se crea un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | +| `delete` | Se activa cuando se borra un ambiente. Para obtener más información, consulta la sección "[Borrar un ambiente](/actions/reference/environments#deleting-an-environment)". | +| `remove_actions_secret` | Se activa cuando se elimina a un secreto de un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | +| `update_actions_secret` | Se activa cuando se actualiza a un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". | +{% endif %} + +{% 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. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Acción | Descripción | +| ----------- | -------------------------------------------------------- | +| `clon` | Se activa cuando se clona un repositorio. | +| `recuperar` | Se activa cuando se recuperan cambios de un repositorio. | +| `subir` | 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 | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------ | +| `aprobar` | 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@3.0" %} + +#### Acciones de la categoría `members_can_create_pages` + +Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". + +| Acción | Descripción | +|:------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `habilitar` | 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. | +| `inhabilitar` | 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" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_policy_selected_member_disabled` | Se activa cuando un propietario de empresa previene que las carcaterísticas de la {% data variables.product.prodname_GH_advanced_security %} se habiliten para los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Se activa cuando un propietario de empresa permite que se habiliten las características de la {% data variables.product.prodname_GH_advanced_security %} en los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `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](/communities/maintaining-your-safety-on-github/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 secreto de {% data variables.product.prodname_actions %} se crea para una organización. Para obtener más información, consulta la sección "[Crear secretos cifrados para una organización](/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 crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | +| `remove_actions_secret` | Se activa cuando se 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 se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de una organización](/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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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 se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/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 se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | +| `runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de 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)". | +| `runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección [Mover 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_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | +| `runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. 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#about-self-hosted-runners)".{% endif %} +| `unblock_user` | Se acvita cuando el propietario de una organización [desbloquea a un usuario de la misma](/communities/maintaining-your-safety-on-github/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 se 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](/organizations/managing-organization-settings/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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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. | +| `actualización` | 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 %}. | +| `transferencia` | Se activa cuando se transfiere una {% data variables.product.prodname_oauth_app %} existente a una organización nueva. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +#### Acciones de la categoría `packages` + +| Acción | Descripción | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `package_version_published` | Se activa cuando se publica una versión del paquete. | +| `package_version_deleted` | Se activa cuando se borra una versión de paquete específica. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | +| `package_deleted` | Se activa cuando se borra un paquete completo. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | +| `package_version_restored` | Se activa cuando se borra una versión de paquete específica. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | +| `package_restored` | Se activa cuando se restablece un paquete completo. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | + +{% endif %} + +{% 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. | +| `actualización` | Se activa cuando se actualiza un método de pago existente. | + +{% endif %} + +#### acciones de la categoría `profile_picture` +| Acción | Descripción | +| ------------- | ------------------------------------------------------------------------------ | +| actualización | 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. | +| `link` | Se activa cuando un repositorio se vincula a un tablero de proyecto. | +| `rename (renombrar)` | Se activa cuando se renombra un tablero de proyecto. | +| `actualización` | Se activa cuando se actualiza un tablero de proyecto. | +| `delete` | 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. | +| `actions_enabled` | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no se incluye cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)". | +| `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)` | Se activa cuando un administrador de un repositorio [agrega un tema](/articles/classifying-your-repository-with-topics) a este.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_disabled` | Se activa cuando un adminsitrador de repositorio inhabilita las características de {% data variables.product.prodname_GH_advanced_security %} en este. 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` | Se activa cuando un administrador de repositorio habilita las características de la {% data variables.product.prodname_GH_advanced_security %} para este. 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)".{% 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 crea cuando un secreto de {% data variables.product.prodname_actions %} se crea para un repositorio. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/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" %} +| `inhabilitar` | Se activa cuando se inhabilita un repositorio (p. ej., por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %} +| `habilitar` | 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 se 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 crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | +| `remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/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 vuelve a nombrar a un repositorio](/articles/renaming-a-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. 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#about-self-hosted-runners)".{% endif %} +| `transferencia` | 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 se 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. | +| `actualización` | 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 | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `habilitar` | 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). | +| `inhabilitar` | 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 | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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)". | +| `habilitar` | 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" or currentVersion == "github-ae@latest" %} +#### Acciones de la categoría `repository_secret_scanning` + +| Acción | Descripción | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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). | +| `habilitar` | 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)". | +| `descartar` | 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. | +| `resolver` | 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)". | +| `inhabilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo a este inhabilita las {% data variables.product.prodname_dependabot_alerts %}. | +| `habilitar` | 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" or currentVersion == "github-ae@latest" %} +#### Acciones de la categoría `secret_scanning` + +| Acción | Descripción | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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). | +| `habilitar` | 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 | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `inhabilitar` | 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). | +| `habilitar` | 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)` | Se activa cuando la cuenta de {% data variables.product.prodname_sponsors %} se crea (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)") | +| `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)` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-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)` | Se activa cuando se crea un equipo nuevo.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`demote_maintainer` | Se activa cuando se baja de categoría a un usuario de mantenedor de equipo a miembro de equipo. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/managing-peoples-access-to-your-organization-with-roles/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` | Se activa cuando un repositorio ya no está bajo el control de un equipo. + +#### acciones de la categoría `team_discussions` + +| Acción | Descripción | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `inhabilitar` | 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)". | +| `habilitar` | Se activa cuando un propietario de la organización habilita los debates de equipo para una organización. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +#### Acciones de la categoría `workflows` + +{% data reusables.actions.actions-audit-events-workflow %} + +{% endif %} + +### Leer más + +- "[Mantener segura tu organización](/articles/keeping-your-organization-secure)" diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000..695d4b4f19 --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,25 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000..689d157d19 --- /dev/null +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,30 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +{% 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) + +### Leer más + +- "[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/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000..894d0d923a --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,40 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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", haz clic en el avatar de la app a la que quieres agregarle 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" %} +### Leer más + +- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/index.md new file mode 100644 index 0000000000..ce82bfd465 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -0,0 +1,18 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% link_in_list /adding-github-app-managers-in-your-organization %} +{% link_in_list /removing-github-app-managers-from-your-organization %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000..cb2eb3186d --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,40 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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", haz clic en el avatar de la app de la que quieres eliminar un administrador {% 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 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" %} +### Leer más + +- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000..71c3a302be --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,27 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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 "Search by username, full name or email address" (Buscar por nombre de usuario, nombre completo o dirección de correo electrónico), escribe el nombre, nombre de usuario o correo electrónico del colaborador externo {% 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/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/index.md new file mode 100644 index 0000000000..0c04b088da --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -0,0 +1,22 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000..c15bd59c44 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,39 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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). + +### Leer más + +- "[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/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..1ac39e168c --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,62 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 "Search by username, full name or email address" (Buscar por nombre de usuario, nombre completo o dirección de correo electrónico), escribe el nombre, el nombre de usuario o el correo electrónico del colaborador {% 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 %} + +### Leer más + +- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..76ca7369a0 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,52 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000..a54a608dd4 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -0,0 +1,44 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +### 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 %} puedes cambiar la visibilidad del tablero de proyecto de privado a {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} y de vuelta. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". + +### Leer más + +- "[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/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000..4a21adc755 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,23 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000..46975f5f23 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,42 @@ +--- +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 + - github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} + +### Leer más + +- "[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/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000..e8f3e0c8ea --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,24 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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**. ![Botón para confirmar la cancelación](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000..2d096e27ef --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,44 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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](/organizations/managing-peoples-access-to-your-organization-with-roles/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) + +### Leer más + +- "[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/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000..24629e6cca --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,41 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/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.' +topics: + - organizations + - equipos +--- + +{% 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 deben [habilitar la autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de que puedan aceptar la invitación.{% else %}deben [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. 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**.![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 %} + +### Leer más + +- "[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/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..064e97deba --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/index.md @@ -0,0 +1,28 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000..05b923c825 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,39 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + +{% 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/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000..8be5366b06 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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) + +### 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/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000..9a0447632f --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,76 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000..6874150e3f --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,57 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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) + +### Leer más + +- "[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/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000..e4660c5611 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -0,0 +1,181 @@ +--- +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.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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](/organizations/managing-access-to-your-organizations-repositories/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 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Nota:** Los permisos del repositorio que se requieren para utilizar las características de seguridad se listan en la sección "[Requisitos de los permisos para las características de seguridad](#permission-requirements-for-security-features)" que se encuentra más adelante. + +{% endnote %} + +{% endif %} +| Acción del repositorio | Read | Clasificación | 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 ellos mismos abrieron | **X** | **X** | **X** | **X** | **X** | +| Reabrir propuestas que ellos mismos cerraron | **X** | **X** | **X** | **X** | **X** | +| Recibir la asignación de una propuesta | **X** | **X** | **X** | **X** | **X** | +| Enviar solicitudes de extracción desde las bifurcaciones de los repositorios asignados del equipo | **X** | **X** | **X** | **X** | **X** | +| Enviar revisiones sobre solicitudes de extracción | **X** | **X** | **X** | **X** | **X** | +| Ver los 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](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Aplicar/descartar etiquetas | | **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" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [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](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Bloquear conversaciones](/communities/moderating-comments-and-conversations/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" or currentVersion == "github-ae@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** | +| | | | | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar paquetes](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **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](/communities/moderating-comments-and-conversations/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](/organizations/managing-access-to-your-organizations-repositories/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" or currentVersion ver_gt "enterprise-server@3.0" %} +| Renombrar la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Renombrar una rama diferente a la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** +{% endif %} +| Administrar webhooks y desplegar llaves | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [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** +{% 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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +#### Requisitos de permisos para características de seguridad + +En esta sección, puedes encontrar los niveles de permisos de los repositorios que se requieren para las características de seguridad, tales como las de las características de la {% data variables.product.prodname_advanced_security %}. + +| Acción del repositorio | Read | Clasificación | Escritura | Mantenimiento | Admin | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:| +| {% if currentVersion == "free-pro-team@latest" %} | | | | | | +| 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** | +| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| Administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} (consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Habilitar el gráfico de dependencias](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) de un repositorio privado | | | | | **X** | +| [Ver las revisiones de las dependencias](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| [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@3.0" or currentVersion == 'github-ae@next' %} +| [Ver las alertas del {% data variables.product.prodname_secret_scanning %} en un repositorio](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | +| [Resolver, revocar o reabrir las alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% if currentVersion == "enterprise-server@3.0" %} +| [Ver las alertas del {% data variables.product.prodname_secret_scanning %} en un repositorio](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Resolver, revocar o reabrir las alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [Designar personas o equipos adicionales para recibir alertas del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) en los repositorios | | | | | **X** +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +[1] Los escritores y mantenedores de los repositorios solo pueden ver la información de las alertas de sus propias confirmaciones. +{% endif %} +{% endif %} + +### Leer más + +- [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/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000..f2629a3f7d --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -0,0 +1,36 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +### 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) + +### Leer más + +- [Niveles de permiso de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" +- "[Agregar colaboradores externos a repositorios de tu organización](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000..e85e694481 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,41 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000..9442a2dcb6 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -0,0 +1,47 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +Para emitir un certificado para alguien que utilice SSH para acceder a varios productos de {% data variables.product.company_short %}, puedes incluir dos extensiones de inicio de sesión para especificar el nombre de usuario para cada producto. Por ejemplo, el siguiente comando emitirá un certificado para el _USERNAME-1_ de la cuenta de {% data variables.product.prodname_ghe_cloud %} del usuario, y para el _USERNAME-2_ de la cuenta de {% data variables.product.prodname_ghe_managed %} del usuario o de {% data variables.product.prodname_ghe_server %} en _HOSTNAME_. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./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@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +{% if currentVersion == "free-pro-team@latest" %} + +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. + +{% endif %} + +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/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..9d173f9100 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -0,0 +1,19 @@ +--- +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. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% link_in_list /about-ssh-certificate-authorities %} +{% link_in_list /managing-your-organizations-ssh-certificate-authorities %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000..46014c4e97 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,38 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md new file mode 100644 index 0000000000..250c779df0 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -0,0 +1,29 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/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 %} + +### Leer más +- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000..375e1a92db --- /dev/null +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,21 @@ +--- +title: '¿Puedo crear cuentas para personas en mi organización?' +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.' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization + - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000..78d819b76e --- /dev/null +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,30 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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). + +### Leer más + +{% 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/organizations/managing-membership-in-your-organization/index.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md new file mode 100644 index 0000000000..50ebf53102 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md @@ -0,0 +1,23 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000..f3122ebdde --- /dev/null +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -0,0 +1,36 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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](/organizations/keeping-your-organization-secure/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 %} + +### Leer más +- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000..17aba4271a --- /dev/null +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,63 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/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. +topics: + - organizations + - equipos +--- + +### 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 %} + +### Leer más + +- "[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/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000..186131c5bf --- /dev/null +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -0,0 +1,60 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + +- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000..75f0f2acaf --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,25 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/es-ES/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000..941c0b1d2f --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,24 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000..72f1470c15 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,22 @@ +--- +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.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000..2d2d370a32 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -0,0 +1,33 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md new file mode 100644 index 0000000000..030fa3af22 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -0,0 +1,34 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000..21ebc97339 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,85 @@ +--- +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.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-organization-settings/index.md b/translations/es-ES/content/organizations/managing-organization-settings/index.md new file mode 100644 index 0000000000..d01195df7b --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/index.md @@ -0,0 +1,39 @@ +--- +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.' +redirect_from: + - /articles/managing-organization-settings + - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 /managing-the-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 %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000..bafa749af6 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,26 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/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 %} + +### Leer más + +- ["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/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..c4cd6740ec --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,67 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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 %} + +### Leer más + +- "[Acerca de las etiquetas](/articles/about-labels)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..4ae922bec8 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,30 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization +permissions: Los propietarios de las organizaciones pueden administrar la creación de debates para los repositorios que pertenecen a éstas. +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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) + +### Leer más + +- "[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/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000..d925233c31 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,66 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +### 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. + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### 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 %} + +### Leer más + +- "[Administrar tus recordatorios programados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" +- "[Administrar los recordatorios programados para tu equipo](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..96442ca76b --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,36 @@ +--- +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 %}.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +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: '*' +topics: + - organizations + - equipos +--- + +### 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) + +### Leer más + +- "[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/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000..7263474262 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,28 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000..2ca4bb2b26 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,34 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-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: '*' +topics: + - organizations + - equipos +--- + +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). + +### Leer más + +- "[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/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..17f5e0197d --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Administrar la publicación de sitios de GitHub Pages de tu organización +intro: 'Puedes controlar si los miembros de tu organización pueden publicar sitios de {% data variables.product.prodname_pages %} desde los repositorios que le pertenecen{% if currentVersion == "free-pro-team@latest" %} y restringir las visibilidades que estos eligen para dichos sitios{% endif %}.' +permissions: 'Los propietarios de las organizaciones pueden administrar la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios que les pertenezcan.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization +topics: + - organizations + - equipos +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. De lo contrario, puedes elegir permitir o dejar de permitir las publicaciones al público en general. Para obtener más información acerca del control de accesos de los sitios de {% data variables.product.prodname_pages %}, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". +{% endif %} + +Si dejas de permitir la publicación de sitios de {% data variables.product.prodname_pages %}, cualquier sitio que ya se haya 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 %}](/pages/getting-started-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 %}{% if currentVersion == "free-pro-team@latest" %} +1. Debajo de "Creación de páginas", selecciona las visibilidades que quieras permitir y deselecciona aquellas que quieres dejar de permitir. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Debajo de "Creación de páginas", selecciona y deselecciona **Permitir a los miembros publicar sitios**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Haz clic en **Save ** (guardar). + +### Leer más + +- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..f0b75aacd2 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,28 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors +versions: + free-pro-team: '*' +permissions: Los propietarios de las organizaciones pueden administrar las actualizaciones de las cuentas que patrocinan dichas organizaciones. +topics: + - organizations + - equipos +--- + +{% 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. ![Casilla de texto para ingresar una dirección de correo electrónico para recibir actualizaciones de las cuentas patrocinadas](/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) + +### Leer más + +- "[Apoyar a la comunidad de código abierto con {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md new file mode 100644 index 0000000000..084f9dfadc --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -0,0 +1,50 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)." +- 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. +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} + +### 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) + +### Leer más + +* "[¿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/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000..4fac0a7f80 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,35 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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](/organizations/managing-organization-settings/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/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..9beb9b3776 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,34 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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). + +### Leer más + +- "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000..e7eb3e7e79 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,28 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000..a3a17883da --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,24 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000..e095347ba5 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,25 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md new file mode 100644 index 0000000000..2a60852776 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -0,0 +1,29 @@ +--- +title: Transferir la propiedad de la organización +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.' +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership + - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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](/organizations/managing-peoples-access-to-your-organization-with-roles/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/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/es-ES/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000..980abe6e7e --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,24 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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. Contáctate con {% data variables.contact.contact_support %} para solicitar un aumento de categoría a los Términos de servicio corporativos. 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) + +### Leer más +- "[Términos de servicio corporativos de GitHub](/articles/github-corporate-terms-of-service/)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md b/translations/es-ES/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md new file mode 100644 index 0000000000..9d9d7e4269 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md @@ -0,0 +1,42 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +### 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/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000..9c9291edee --- /dev/null +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,57 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos + - facturación +--- + +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/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000..bb175e0f87 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,29 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md new file mode 100644 index 0000000000..05ca381111 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -0,0 +1,21 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000..0a29cae587 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,32 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization +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: '*' +topics: + - organizations + - equipos +--- + +### 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/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md new file mode 100644 index 0000000000..447ee2ab49 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -0,0 +1,147 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +### 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](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/organizing-members-into-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](/organizations/keeping-your-organization-secure/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](/organizations/collaborating-with-your-team/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](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | | | +| Editar y eliminar debates de equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" para obtener más detalles) | **X** | | | +| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/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** | | | +| 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** | | | +| 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](/organizations/managing-organization-settings/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** | | | +| Administra la publicación de páginas de {% data variables.product.prodname_pages %} desde los repositorios de la organización (consulta "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" para obtener 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](/organizations/keeping-your-organization-secure/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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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** | | | +| 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** | | | +| [Administrar la política de bifurcación](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limitar la actividad en repositorios públicos en una organización](/communities/moderating-comments-and-conversations/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](/organizations/managing-organization-settings/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](/organizations/managing-saml-single-sign-on-for-your-organization/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](/organizations/organizing-members-into-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](/organizations/collaborating-with-your-team/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](/organizations/collaborating-with-your-team/about-team-discussions)" para obtener más detalles) | **X** | | | +| Editar y eliminar debates de equipo en **todos los equipos** (para obtener más información consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/communities/moderating-comments-and-conversations/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@3.0" %} +| Administra la publicación de páginas de {% data variables.product.prodname_pages %} desde los repositorios de la organización (consulta "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" para obtener 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 %} +{% if currentVersion == "github-ae@latest" %}| Administrar listas de IP permitidas (Consulta la sección "[Restringir el tráfico de red a tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **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 %} + +### Leer más + +- "[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/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000..cedead0393 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,25 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos + - facturación +--- + +{% 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/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000..80c99cde4c --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,62 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +### 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. + +Los propietarios de las organizaciones pueden requerir el SSO de SAML para una organización individual o para todas las organizaciones en una cuenta empresarial. 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](/organizations/managing-saml-single-sign-on-for-your-organization/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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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](/organizations/managing-saml-single-sign-on-for-your-organization/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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### Leer más + +- "[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/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md new file mode 100644 index 0000000000..c06b412863 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -0,0 +1,31 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-scim +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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 %} Para obtener más información, consulta la sección "[Acerca de el aprovisionamiento de usuarios en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". + +### Leer más + +- "[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/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000..afd29a8ea8 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,31 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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. + +### Leer más + +- [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/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000..61553e83a3 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,81 @@ +--- +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 %}.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta +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: '*' +topics: + - organizations + - equipos +--- + +### 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](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" y "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/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 más información, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/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 %} + +### Leer más + +- "[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](/organizations/managing-saml-single-sign-on-for-your-organization/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/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000..183ad0e168 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,34 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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 %} + +### Leer más + +- "[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/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000..77e33eab3c --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,36 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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. + +### Leer más + +- "[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/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..90f629f1c0 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,52 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + +- "[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/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..ab4da5bffb --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,31 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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. + +### Leer más + +- "[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/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md new file mode 100644 index 0000000000..3f300efc8b --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -0,0 +1,24 @@ +--- +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. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000..5804ba1983 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,79 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization +permissions: Los propietarios de las organizaciones pueden administrar la sincronización de equipos a una organización. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000..0147f11715 --- /dev/null +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,27 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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 %} + +### Leer más + +- "[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/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..5f50a53cb6 --- /dev/null +++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,32 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +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/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..18b2995c9c --- /dev/null +++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,52 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +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/organizations/migrating-to-improved-organization-permissions/index.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/index.md new file mode 100644 index 0000000000..72f8d07565 --- /dev/null +++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/index.md @@ -0,0 +1,20 @@ +--- +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.' +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000..d0e5e859fb --- /dev/null +++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,44 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - equipos +--- + +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/organizations/organizing-members-into-teams/about-teams.md b/translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md new file mode 100644 index 0000000000..e1ee10fe3e --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md @@ -0,0 +1,79 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +![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](/organizations/collaborating-with-your-team/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. + +### Leer más + +- "[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/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000..5ed9b97320 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,32 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} + +### Leer más + +- [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/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/es-ES/content/organizations/organizing-members-into-teams/changing-team-visibility.md new file mode 100644 index 0000000000..8397772d74 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/changing-team-visibility.md @@ -0,0 +1,29 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/organizing-members-into-teams/creating-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md new file mode 100644 index 0000000000..ba58ece389 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -0,0 +1,38 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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](/organizations/organizing-members-into-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). + +### Leer más + +- [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/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/deleting-a-team.md new file mode 100644 index 0000000000..9a0dea943e --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/deleting-a-team.md @@ -0,0 +1,27 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/es-ES/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000..70ae3b96dd --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,23 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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](/organizations/collaborating-with-your-team/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/organizations/organizing-members-into-teams/index.md b/translations/es-ES/content/organizations/organizing-members-into-teams/index.md new file mode 100644 index 0000000000..af0b43a8c9 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/index.md @@ -0,0 +1,38 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000..5461877677 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,51 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000..5218a2f3fd --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,69 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +### 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](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)". + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### 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 %} + +### Leer más + +- "[Administrar los recordatorios programados para tu organización](/organizations/managing-organization-settings/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/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/es-ES/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000..a6f3a0f0e0 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,42 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + +- [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000..03b58a5e5a --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,23 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/renaming-a-team.md new file mode 100644 index 0000000000..aac3f95e05 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/renaming-a-team.md @@ -0,0 +1,21 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000..2a0beb2ea7 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,36 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + +- [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/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000..608905865c --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,36 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + +- [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/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/es-ES/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000..71e2ff4aac --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,24 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +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/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000..9acf8a8c85 --- /dev/null +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,99 @@ +--- +title: Sincronizar un equipo con un grupo de proveedor de identidad +intro: 'Puedes sincronizar un equipo de {% data variables.product.product_name %} con un grupo de proveedor de identidad (IdP) para agregar y eliminar miembros del grupo automáticamente.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group +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: '*' + github-ae: '*' +topics: + - organizations + - equipos +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Acerca de la sincronización de equipo + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% if currentVersion == "free-pro-team@latest" %}Puedes conectar hasta cinco grupos de IdP a un equipo de {% data variables.product.product_name %}.{% elsif currentVersion == "github-ae@latest" %}Puedes conectar a un equipo de {% data variables.product.product_name %} a un grupo de IdP. Todos los usuarios en el grupo se agregan automáticamente al equipo y también a la organización padre como miembros. Cuando desconectas a un grupo de un equipo, los usuarios que se convirtieron en miembros de la organización a través de una membrecía de equipo se eliminan de dicha organización.{% endif %} Puedes asignar un grupo de IdP a varios equipos de {% data variables.product.product_name %}. + +{% if currentVersion == "free-pro-team@latest" %}La sincronización de equipos no es compatible con grupos de IdP con más de 5000 miembros.{% endif %} + +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 las membrecías de equipo en {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} ni utilizando la API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} +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)." +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Cualquier solicitud que cambie la membrecía de organización o equipo de {% data variables.product.prodname_dotcom %} se registrará en la bitácora de auditoría como cambios que realizó la cuenta que se utilizó para configurar el aprovisionamiento de usuarios. Para obtener más información sobre esta cuenta, consulta la sección "[Configurar el aprovisionamiento de usuarios para tu empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obtener más información acerca de los itinerarios de solicitudes de SCIM, consulta la sección "[Verificar el estado del aprovisionamiento de usuarios](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" en Microsoft Docs. +{% endif %} + +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](/organizations/organizing-members-into-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)." + +{% if currentVersion == "free-pro-team@latest" %}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)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Requisitos para los miembros de los equipos sincronizados + +Después de que conectas un equipo a un grupo de IdP, la sincronización de equipos agregará a cada miembro del grupo de IdP al equipo correspondiente en {% data variables.product.product_name %} únicamente si: +- La persona es un miembro de la organización en {% data variables.product.product_name %}. +- La persona ya ingresó con su cuenta de usuario en {% data variables.product.product_name %} y se autenticó en la cuenta organizacional o empresarial a través del inicio de sesión único de SAML por lo menos una vez. +- La identidad de SSO de la persona es miembro del grupo de IdP. + +Los equipos o miembros del grupo existentes que no cumplan con estos criterios se eliminarán automáticamente del equipo en {% data variables.product.product_name %} y perderán acceso a los repositorios. El revocar la identidad ligada a un usuario también eliminará a dicho usuario de cualquier equipo que se encuentre mapeado en los grupos de IdP. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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. Para obtener más información, consulta las secciones "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" y "[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)". + +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. Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". + +{% endif %} + +### Prerrequisitos + +{% if currentVersion == "free-pro-team@latest" %} +Before you can connect a {% data variables.product.product_name %} 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](/organizations/managing-saml-single-sign-on-for-your-organization/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)". + +{% elsif currentVersion == "github-ae@latest" %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (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)". + +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. Para obtener más información, consulta la sección de [Configurar el aprovisionamiento automático de usuarios en GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) en los Microsoft Docs. +{% endif %} + +### Conectar un grupo de IdP a tu equipo + +Cuando conectas un grupo de IdP a un equipo de {% data variables.product.product_name %}, todos los usuarios en el grupo se agregan automáticamente al equipo. {% if currentVersion == "github-ae@latest" %}Cualquier usuario que no fuera un miembro de aquellos de la organización desde antes también se agregará a esta.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Debajo de "Grupos del Proveedor de Identidad", utiliza el menú desplegable y selecciona hasta 5 grupos del proveedor de identidad. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Debajo de "Grupo del Proveedor de Identidad", utiliza el menú desplegable y selecciona un grupo de proveedor de identidad de la lista. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. 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. {% if currentVersion == "github-ae@latest" %} Cualquier usuario que fuera miembro de la organización padre únicamente debido a esa conexión de equipo también se eliminará de la organización.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +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" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Debajo de "Grupo del Proveedor de Identidad", a la derecha del grupo de IdP que quieras desconectar, da clic en {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Haz clic en **Guardar cambios**. diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000..40e5591568 --- /dev/null +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -0,0 +1,60 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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 . + +### Leer más + +- "[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/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000..0492ec7994 --- /dev/null +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,26 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +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) + +### Leer más + +- "[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/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000..ea8c863503 --- /dev/null +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,20 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..79ed3af61e --- /dev/null +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,26 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..0ec6c3c586 --- /dev/null +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,31 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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/organizations/restricting-access-to-your-organizations-data/index.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/index.md new file mode 100644 index 0000000000..0a90f9909e --- /dev/null +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -0,0 +1,19 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data +versions: + free-pro-team: '*' +topics: + - organizations + - equipos +--- + +{% 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 %} \ No newline at end of file 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 index 7a6984309c..6b19737e2b 100644 --- a/translations/es-ES/content/packages/guides/about-github-container-registry.md +++ b/translations/es-ES/content/packages/guides/about-github-container-registry.md @@ -1,8 +1,8 @@ --- -title: About GitHub Container Registry -intro: 'You can use {% data variables.product.prodname_github_container_registry %} to seamlessly host and manage Docker container images in your organization or personal user account on {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_github_container_registry %} allows you to configure who can manage and access packages using fine-grained permissions.' +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: +redirect_from: - /packages/getting-started-with-github-container-registry/about-github-container-registry - /packages/managing-container-images-with-github-container-registry versions: @@ -11,85 +11,84 @@ versions: {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." +**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 %} -### About {% data variables.product.prodname_github_container_registry %} +### Acerca de {% data variables.product.prodname_github_container_registry %} {% data reusables.package_registry.container-registry-feature-highlights %} -To share context about your package's use, you can link a repository to your container image on {% data variables.product.prodname_dotcom %}. For more information, see "[Connecting a repository to a container image](/packages/guides/connecting-a-repository-to-a-container-image)." +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)". -{% data variables.product.prodname_github_container_registry %} has different hosting locations, permission, and visibility than other package registries. +El {% data variables.product.prodname_github_container_registry %} tiene ubicaciones de hospedaje, permisos y visibilidades diferentes a las de otros registros de paquete. -| | Package registries | {% data variables.product.prodname_github_container_registry %} | -|----|----|----| -| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. | -| Permissions | Each package inherits the permissions of the repository where the package is hosted.

For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. -Visibility | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | -Anonymous access | N/A | You can access public container images anonymously. +| | 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. -For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." +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)". -### Supported formats +### Formatos compatibles -The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: +El {% data variables.product.prodname_container_registry %} es actualmente compatible con los siguientes formatos de contenedores de imagen: -* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) -* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) +* [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) -The {% data variables.product.prodname_github_container_registry %} hosts containers at `ghcr.io/OWNER/IMAGE-NAME`. +El {% data variables.product.prodname_github_container_registry %} hospeda los contenedores en `ghcr.io/OWNER/IMAGE-NAME`. -| Package client | Language | Package format | Description | -| --- | --- | --- | --- | -| Docker CLI | N/A | `Dockerfile` | Docker container support. | +| Cliente del paquete | Lenguaje | Formato del paquete | Descripción | +| ------------------- | -------- | ------------------- | ----------------------- | +| docker | N/A | `Dockerfile` | Gestor de paquetes Node | -#### Manifest Lists/Image Indexes +#### Índices de Listas/Imágenes de Manifiesto -{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. +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. -### Visibility and access permissions for container images +### Permisos de visibilidad y acceso para las imágenes de contenedor -If you have admin permissions to a container image, you can set the container image to private or public. Public images allow anonymous access and can be pulled without authentication or signing in via the CLI. +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. -As an admin, you can also grant access permissions for a container image that are separate from the permissions you've set at the organization and repository levels. +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. -For container images published and owned by a user account, you can give any person an access role. For container images published and owned by an organization, you can give any person or team in the organization an access role. +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. -| Permission role | Access description | -|-----|----| -| Read | Can download package.
Can read package metadata. | -| Write | Can upload and download this package.
Can read and write package metadata. | -| Admin | Can upload, download, delete, and manage this package.
Can read and write package metadata.
Can grant package permissions. +| 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. | -For more information, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." +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)". -### About scopes and permissions for {% data variables.product.prodname_github_container_registry %} +### Sobre tokens -To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. +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. -| Scope | Description | -| --- | --- | -|`read:packages`| Download and install container images from {% data variables.product.prodname_github_container_registry %} | -|`write:packages`| Upload and publish container images to {% data variables.product.prodname_github_container_registry %} | -| `delete:packages` | Delete specified versions of private or public container images from {% data variables.product.prodname_github_container_registry %}. For more information, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." | +| Á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 y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)". | -To learn about available scopes and permissions for container images, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." +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)". -For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)" and "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)." +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)". -### About billing for {% data variables.product.prodname_github_container_registry %} +### Acerca de la facturación para {% data variables.product.prodname_github_container_registry %} {% data reusables.package_registry.billing-for-container-registry %} -### Contacting support +### Contactar con soporte técnico -If you have feedback or feature requests for {% data variables.product.prodname_github_container_registry %}, use the [feedback form](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages). +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). -Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_github_container_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if: +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: -* You experience anything that contradicts the documentation. -* You encounter vague or unclear errors. -* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally-identifying information. +* 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-rubygems-for-use-with-github-packages.md b/translations/es-ES/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md index 4b2465e06d..bf19f85365 100644 --- 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 @@ -10,9 +10,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-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. @@ -59,6 +61,8 @@ Para instalar gemas, necesitas autenticarte en el {% data variables.product.prod - `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 %}. +{% elsif currentVersion == "github-ae@latest" %} + - `REGISTRY-URL` con la URL para el registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}. {% endif %} Si no tienes un archivo *~/.gemrc*, crea un nuevo archivo *~/.gemrc* usando este ejemplo. @@ -75,7 +79,7 @@ Si no tienes un archivo *~/.gemrc*, crea un nuevo archivo *~/.gemrc* usando este ``` -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 %} +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`. En cualquiera de los casos, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %}Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %} ```shell $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN @@ -96,7 +100,7 @@ $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygem ```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 %} +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`. En cualquiera de los casos, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %}Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %} ```shell $ gem push --key github \ @@ -106,7 +110,7 @@ $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygem ### 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 %} +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 %} empata el repositorio con base en este valor en vez de utilizar el nombre de la gema.% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Reemplaza a *HOSTNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %} ```ruby gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } @@ -117,7 +121,7 @@ gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@ 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 %} +1. 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`. En cualquiera de los casos, reemplaza *HOSTNAME* con el nombre de host de tu instancia de {% data variables.product.prodname_ghe_server %}.{% elsif currentVersion == "github-ae@latest" %}Reemplaza `REGISTRY-URL` con la URL del registro de Rubygems de tu instancia, `rubygems.HOSTNAME`. Reemplaza *HOTSNAME* con el nombre de host de {% data variables.product.product_location %}.{% endif %} ```ruby source "https://rubygems.org" @@ -146,4 +150,4 @@ Puedes usar gemas desde {% data variables.product.prodname_registry %} al igual ### Leer más -- "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" +- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}" 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 index 5554ef9693..2e552b431a 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '>=2.22' 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 index 0639d1fc71..76685f9d72 100644 --- 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 @@ -2,7 +2,7 @@ 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: true +mapTopic: verdadero versions: free-pro-team: '*' enterprise-server: '>=2.22' 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 index 8f9a3f5c6d..4d76d3fd65 100644 --- 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 @@ -1,6 +1,6 @@ --- -title: Using GitHub Packages with GitHub Actions -intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.' +title: Usar 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 @@ -8,44 +8,87 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} +{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-self-hosted-runners-notice %} -### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} +### 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 %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." -You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. +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" %} -#### Authenticating to {% data variables.product.prodname_github_container_registry %} +#### 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 %} -For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)." +Para 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 %} -#### Authenticating to package registries on {% data variables.product.prodname_dotcom %} +#### Autenticarse en los registros de paquetes en {% data variables.product.prodname_dotcom %} -{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The `GITHUB_TOKEN` has `read:packages` and `write:packages` scopes to the current repository. For forks, the token also has the `read:packages` scope for the parent repository. +{% if currentVersion == "free-pro-team@latest" %}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. -You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." +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)." -### Publishing a package using an action +### Acerca de los permisos y acceso a los paquetes para los paquetes que pertenecen a los repositorios -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 %}. +{% note %} + +**Nota:** Los paquetes que pertenecen a los repositorios incluyen paquetes de RubyGems, npm, Apache Maven, NuGet, Gradle, y Docker que utilizan el espacio de nombres `docker.pkg.github.com`. + +{% endnote %} + +Cuando habilitas las Acciones de GitHub, GitHub instala una App GitHub en tu repositorio. El secreto del `GITHUB_TOKEN` es un token de acceso a la instalación de GitHub App. Puedes utilizar el token de acceso a la instalación para autenticarte en nombre de la GitHub App instalada 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 la sección "[Permisos para el GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)". + +El {% data variables.product.prodname_registry %} te permite subir y extraer paquetes mediante el `GITHUB_TOKEN` que está disponible para un flujo de trabajo de {% data variables.product.prodname_actions %}. + +{% if currentVersion == "free-pro-team@latest" %} +### Acerca de los permisos y el acceso de paquetes para el {% data variables.product.prodname_container_registry %} + +El {% data variables.product.prodname_container_registry %} (`ghcr.io`) permite a los usuarios crear y administrar contenedores como recursos independientes a nivel organizacional. Los contenedores pueden pertenecer a una organización o a una cuenta de usuario personal y puedes personalizar el acceso para cada uno de tus contenedores por aparte de los permisos del repositorio. + +Todos los flujos de trabajo que accedan al {% data variables.product.prodname_container_registry %} deben utilizar el `GITHUB_TOKEN` en vez de un token de acceso personal. 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/learn-github-actions/security-hardening-for-github-actions#using-secrets)". + +### Configuración de acceso y permisos predeterminados para los contenedores que se modifican a través de los flujos de trabajo + +Cuando creas, instalas, modificas o borras un contenedor a través de un flujo de trabajo, hay algunos permisos y configuraciones de acceso predeterminados que se utilizan para garantizar que los administradores tengan acceso al fluljo de trabajo. También puedes ajustar esta configuración de acceso. + +Por ejemplo, predeterminadamente, si un flujo de trabajo crea un contenedor que utilice el `GITHUB_TOKEN`, entonces: +- El contenedor hereda la visibilidad el modelo de permisos del repositorio en donde se ejecuta el flujo de trabajo. +- Los administradores de repositorio donde se ejecuta el flujo de trabajo se convierten en los administradores del contenedor una vez que este se cree. + +Estos son más ejemplos de cómo funcionan los permisos predeterminados para los flujos de trabajo que administran paquetes. + +| Tarea de flujo de trabajo de {% data variables.product.prodname_actions %} | Acceso y permisos predeterminados | +| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Descargar un contenedor existente | - Si el contenedor es público, cualquier flujo de trabajo que se ejecute en cualquier repositorio puede descargar el contenedor.
- Si el contenedor es interno, entonces todos los flujos de trabajo que se ejecuten en un repositorio que pertenezca a la cuenta empresarial podrá descargarlo. Para las organziaciones que pertenecen a una empresa, puedes leer cualquier repositorio en la empresa
- Si el contenedor es privado, solo los flujos de trabajo que se ejecuten en los repositorios a los que se les otorga permiso de lectura en dicho contenedor podrán descargarlo.
| +| Carga una versión nueva a un contenedor existente | - Si el contenedor es privado, interno, o público, solo los flujos de trabajo que se ejecuten en repositorios que tengan el permiso de escritura en dicho contenedor podrán cargar versiones nuevas de este. | +| Borrar un contenedor o versiones de un contenedor | - Si el contenedor es privado, interno o público, solo los flujos de trabajo que se ejecuten en los repositorios a los que se les otorga permiso de borrado podrán borrar las versiones existentes de este. | + +También puedes ajustar el acceso a los contenedores de forma más granular o ajustar el comportamiento de algunos de los permisos predeterminados. 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)". + +{% endif %} + +### Publicar un paquete mediante una acción + +Puedes utilizar {% data variables.product.prodname_actions %} para publicar paquetes automáticamente como parte de tu flujo de integración contínua (IC). Este acercamiento a los despliegues contínuos (DC) te permite automatizar la creación de nuevas versiones de los paquetes si el código cumple con tus estándares de calidad. Por ejemplo, podrías crear un flujo de trabajo que ejecute pruebas de IC cada vez que un desarrollador suba código a alguna rama en particular. Si estas pruyebas pasan, el flujo de trabajo puede publicar una versión nueva del paquete en el {% 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 %}: +El siguiente ejemplo ilustra cómo puedes utilizar las {% data variables.product.prodname_actions %} para crear y probar tu app, y luego crear atuomáticamente una imagen de Docker y publicarla en el {% 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: +- Crea un archivo de flujo de trabajo nuevo en tu repositorio (tal como `.github/workflows/deploy-image.yml`), y agrega el siguiente YAML: {% raw %} - ``` + ```yaml{:copy} name: Create and publish a package on: push: @@ -99,16 +142,14 @@ The following example demonstrates how you can use {% data variables.product.pro with: username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - registry: docker.pkg.github.com + registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %} repository: ${{ github.repository }}/octo-image tag_with_sha: true tag_with_ref: true ``` {% endraw %} - The relevant settings are explained in the following table: - - + La configuración relevante se explica en la siguiente tabla:
@@ -145,7 +186,7 @@ on: {% endraw %} @@ -180,7 +221,7 @@ on: {% endraw %} @@ -193,7 +234,7 @@ on: {% endraw %} @@ -206,7 +247,7 @@ uses: docker/build-push-action@v1 {% endraw %} @@ -219,7 +260,7 @@ with: {% endraw %} @@ -232,7 +273,7 @@ username: ${{ github.actor }} {% endraw %} @@ -245,20 +286,18 @@ password: ${{ secrets.GITHUB_TOKEN }} {% endraw %} @@ -271,7 +310,7 @@ repository: ${{ github.repository }}/octo-image {% endraw %} @@ -284,12 +323,12 @@ tag_with_sha: true {% endraw %}
@@ -121,7 +162,7 @@ on: {% endraw %} - Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. + Configura el flujo de trabajo de Create and publish a package para que se ejecute cada que se suba un cambio a la rama que se llama release.
- This job installs NPM and uses it to build the app. + Este job instala NPM y lo utiliza para crear la app.
- 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. + Este job utiliza npm test para probar el código. El comando needs: run-npm-build hace que este job dependa del job run-npm-build.
- 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. + Crea un paso nuevo que se llama Build container image. Este paso se ejecuta como parte del job build-and-push-image. El comando needs: run-npm-test hace que este job dependa del job run-npm-test.
- 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 %}. + Utiliza la acción build-push-action de Docker para crear la imagen, basándose en el Dockerfile de tu repositorio. Si la compilación es exitosa, sube la imagen al {% data variables.product.prodname_registry %}.
- Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. + Envía los parámetros requeridas a la acción build-push-action. Este se define en las línas siguientes.
- Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. + Define la cuenta de usuario que publicará los paquetes. Una vez que se publica, los paquetes pertenecerán a la cuenta que se define aquí.
- Defines the password that is used to access {% data variables.product.prodname_registry %}. + Define la contraseña que se utiliza para acceder al {% data variables.product.prodname_registry %}.
-{% raw %} ```yaml -registry: docker.pkg.github.com +registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %} ``` -{% endraw %} - Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. + Deifne el registro que hospedará los paquetes resultantes. Este ejemplo utiliza el {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Reemplaza a YOUR-HOSTNAME con el nombre de tu empresa.{% endif %} {% if currentVersion == "free-pro-team@latest" %} Si estás utilizando el {% data variables.product.prodname_container_registry %}, entonces utiliza ghcr.io como nombre de host.{% endif %}
- 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. + Deifne qué repositorio hospedará el paquete resultante y configura el nombre del paquete publicado. Reemplaza a octo-image con el nombre que quieres para tu paquete.
- Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. + Etiqueta el paquete publicado con los siete caracteres principales del SHA de la confirmación. Por ejemplo, sha-2f2d842.
- + {% raw %} ```yaml tag_with_ref: true @@ -297,22 +336,100 @@ 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. + Etiqueta el paquete publicado con la referencia de git. Esta puede ser el nombre de la rama que se utilizó para crear el paquete.
-- 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)." +- Este flujo de trabajo nuevo se ejecutará automáticamente cada que subas un cambio a una rama que se llame `release` en el repositorio. Puedes ver el progreso en la pestaña de **Acciones**. +- Unos minutos después de que se complete el flujo de trabajo, el paquete nuevo podrá visualizarse en tu repositorio. Para encontrar tus paquetes disponibles, consulta la sección "[Visualizar los paquetes de un repositorio](/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. +### Instalar un paquete mediante una acción -Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %} +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 los 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` cannot install packages from any private repository besides the repository where the action runs. You cannot currently use `GITHUB_TOKEN` to authenticate to {% data variables.product.prodname_github_container_registry %}. {% endif %} {% data reusables.package_registry.actions-configuration %} + +{% if currentVersion == "free-pro-team@latest" %} +### Actualizar un flujo de trabajo que tiene acceso a `ghcr.io` + +{% data reusables.package_registry.github-token-security-over-pat %} + +El utilizar el `GITHUB_TOKEN` en vez de un PAT, el cual incluya el alcance de `repo`, incrementa la seguridad de tu repositorio, ya que no necesita sutilizar un PAT de vida extendida que ofrezca acceso innecesario al repositorio en donde se ejecuta tu flujo de trabajo. 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/learn-github-actions/security-hardening-for-github-actions#using-secrets)". + +1. Navega a la página de llegada de tu paquete. +1. En la barra lateral izquierda, haz clic en **Acceso a las acciones**. ![Opción "Acceso a las acciones" en el menú izquierdo](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) +2. Para asegurarte de que tu paquete de contenedor tenga acceso a tu flujo de trabajo, debes agregar el repositorio en donde se almacena el flujo de trabajo a tu contenedor. Haz clic en **Agregar repositorio** y busca el repositorio que quieres agregar. ![Botón "Agregar repositorio"](/assets/images/help/package-registry/add-repository-button.png) + {% note %} + + **Nota:** Agregar un repositorio a tu contenedor a través de la opción de menú **Acceso de las acciones** es diferente que conectar tu contenedor a un repositorio. Para obtener más información, consulta las secciones "[Garantizar a tu paquete acceso a los flujos de trabajo](/packages/guides/configuring-access-control-and-visibility-for-container-images#ensuring-workflow-access-to-your-package)" y "[Conectar un repositorio a una imagen de contenedor](/packages/guides/connecting-a-repository-to-a-container-image)". + + {% endnote %} +3. Opcionalmente, utiliza el menú desplegable de "rol", selecciona el nivel de acceso predeterminado que te gustaría que tuviera el repositorio en tu imagen de contenedor. ![Niveles de acceso de permisos para otorgar a los repositorios](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) +5. Abre tu archivo de flujo de trabajo. En la línea en donde ingresas a `ghcr.io`, reemplaza tu PAT con {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. + +Por ejemplo, este flujo de trabajo publica un contenedor de Docker utilizando {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} para autenticarse. + +{% raw %} +```yaml{:copy} +name: Demo Push + +on: + push: + # Publish `master` as Docker `latest` image. + branches: + - master + - seed + + # Publish `v1.2.3` tags as releases. + tags: + - v* + + # Run tests for any PRs. + pull_request: + +env: + IMAGE_NAME: ghtoken_product_demo + +jobs: + # Push image to GitHub Packages. + # See also https://docs.docker.com/docker-hub/builds/ + push: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Build image + run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}" + + - name: Log into registry + # This is where you will update the PAT to GITHUB_TOKEN + run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin + + - name: Push image + run: | + IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME + + # Change all uppercase to lowercase + IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]') + # Strip git ref prefix from version + VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,') + # Strip "v" prefix from tag name + [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//') + # Use Docker `latest` tag convention + [ "$VERSION" == "master" ] && VERSION=latest + echo IMAGE_ID=$IMAGE_ID + echo VERSION=$VERSION + docker tag $IMAGE_NAME $IMAGE_ID:$VERSION + docker push $IMAGE_ID:$VERSION +``` +{% endraw %} + +{% endif %} diff --git a/translations/es-ES/content/packages/index.md b/translations/es-ES/content/packages/index.md index a1b56f5806..e50249856e 100644 --- a/translations/es-ES/content/packages/index.md +++ b/translations/es-ES/content/packages/index.md @@ -20,8 +20,8 @@ featuredLinks: - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - label: 'packages' - prefix: 'Packages: ' + label: 'paquetes' + prefix: 'Paquetes:' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry 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 index 203df83f4e..22df8cabbb 100644 --- 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 @@ -1,6 +1,6 @@ --- -title: About GitHub Packages -intro: '{% data variables.product.prodname_registry %} is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects.' +title: Acerca de GitHub Packages +intro: '{% data variables.product.prodname_registry %} es un paquete de software que hospeda el servicio que te permite hospedar tus paquetes de software de forma privada {% if currentVersion == "github-ae@latest" %} para los usuarios específicos o internamente para tu empresa{% else %}o públicamente{% endif %} y utiliza los paquetes como dependencias en tus proyectos.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/about-github-package-registry @@ -10,164 +10,148 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} -### About {% data variables.product.prodname_registry %} +### Acerca de {% data variables.product.prodname_registry %} -{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management and billing, so you can centralize your software development on {% data variables.product.product_name %}. +{% 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 paquetes en un solo lugar para proporcionar una administración de permisos {% if currentVersion != "github-ae@latest" %}y facturación {% endif %}integradas, para que puedas centralizar tu desarrollo de software en {% data variables.product.product_name %}. -You can integrate {% data variables.product.prodname_registry %} with {% data variables.product.product_name %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions. +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. -{% data variables.product.prodname_registry %} offers different package registries for commonly used packages, such as for Node, RubyGems, Apache Maven, Gradle, and Nuget. +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 %} +![Diagrama ue muestra la compatibilidad de paquetes para npm, RubyGems, Apache Maven, Nuget y Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% 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)." +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 %} -#### Viewing packages +#### Visualizar paquetes -You can review the package's README, some metadata like licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)." +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)". -#### About package permissions and visibility +#### Acerca de los permisos y la visibilidad de los paquetes -| | Package registries | -|----|----| -| Hosting locations | You can host multiple packages in one repository. | -| Permissions | Each package inherits the permissions of the repository where the package is hosted.

For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | -| Visibility | {% data reusables.package_registry.public-or-private-packages %} | +| | 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" %} -### About billing for {% data variables.product.prodname_registry %} +### 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 %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." +{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} Para obtner más información, consulta la sección "[Acerca de la facturación para el {% 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 %} -### Supported clients and formats +### Formatos y clientes admitidos -{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions. -#### Support for package registries +{% 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" %} -Package registries use `PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL, replacing `PACKAGE-TYPE` with the Package namespace. For example, your Gemfile will be hosted at `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`. - -{% else %} - -The package types supported on {% data variables.product.product_location %} may vary since your site administrator can enable or disable support for different package types. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." - -If {% data variables.product.product_location %} has subdomain isolation enabled, then package registries will use `PACKAGE-TYPE.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL, replacing `PACKAGE-TYPE` with the Package namespace. For example, your Dockerfile will be hosted at `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME`. - -If {% data variables.product.product_location %} has subdomain isolation disabled, then package registries will use `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL. For example, your Gemfile will be hosted at `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME`, replacing *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance. - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -| Language | Description | Package format | Package client | Package namespace | -| --- | --- | --- | --- | --- | -| JavaScript | Node package manager | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` -| Ruby | RubyGems package manager | `Gemfile` | `gem` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` -| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` -| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` -| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` - -{% else %} - -With subdomain isolation enabled on {% data variables.product.product_location %}: - -| Language | Description | Package format | Package client | Package namespace | -| --- | --- | --- | --- | --- | -| JavaScript | Node package manager | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` -| Ruby | RubyGems package manager | `Gemfile` | `gem` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` -| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` -| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` -| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` -| N/A | Docker container management | `Dockerfile` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` - -With subdomain isolation disabled on {% data variables.product.product_location %}: - -| Language | Description | Package format | Package client | Package namespace | -| --- | --- | --- | --- | --- | -| JavaScript | Node package manager | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` -| Ruby | RubyGems package manager | `Gemfile` | `gem` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` -| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` -| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` -| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` +| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | +| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | +| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | +| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gem` | +| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | +| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | +| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | +| N/A | Plataforma de administración del contenedor Docker | `Dockerfile` | `Docker` | +{% if currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Note:** Docker is not supported when subdomain isolation is disabled. +**Nota:** Docker no es compatible cuando inhabilitas el aislamiento de subdominios. {% endnote %} -For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." +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 %} -For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Package client guides for {% data variables.product.prodname_registry %}](/packages/guides/package-client-guides-for-github-packages)." +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" %} -For more information about Docker and {% data variables.product.prodname_github_container_registry %}, see "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)." +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 %} -### Authenticating to {% data variables.product.prodname_registry %} +### Autenticarte en {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -### About scopes and permissions for package registries +### Administrar paquetes -To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. +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. -For example: -- To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permissions for the repository. -- To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)." +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. +- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}Para borrar un paquete en {% data variables.product.product_name %}, tu token deberá tener por lo menos los alcances de `delete:packages` y `read:packages`. El alcance de `repo` también se requiere para los paquetes con dicho alcance.{% elsif currentVersion ver_lt "enterprise-server@3.1" %}Para borrar una versión específica de un paquete privado en {% data variables.product.product_name %}, tu token debe tener el alcance `delete:packages` y `repo`. Los paquetes públicos no se pueden borrar.{% elsif currentVersion == "github-ae@latest" %}Para borrar una versión específica de un paquete en {% data variables.product.product_name %}, tu token debe tener los alcances de `delete:packages` y `repo`.{% endif %} Para obtener más información, consulta la sección "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}". -| Scope | Description | Repository permissions | -| --- | --- | --- | -|`read:packages`| Download and install packages from {% data variables.product.prodname_registry %} | read | -|`write:packages`| Upload and publish packages to {% data variables.product.prodname_registry %} | write | -| `delete:packages` | Delete specified versions of private packages from {% data variables.product.prodname_registry %} | admin | -| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write, or admin | +| Á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` | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Borrar paquetes de {% data variables.product.prodname_registry %} {% elsif currentVersion ver_lt "enterprise-server@3.1" %} Borrar versiones específicas de paquetes privados en el {% data variables.product.prodname_registry %}{% elsif currentVersion == "github-ae@latest" %} Borrar versiones específicas de paquetes en el {% data variables.product.prodname_registry %} {% endif %} | | | +| admin | | | +| `repo` | Carga y borra los paquetes (junto con los `write:packages`, o los `delete:packages`) | escritura o admin | -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. +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. -For more information, see: -- "[Using {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}](/packages/using-github-packages-with-your-projects-ecosystem/)" -- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)" -- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)" +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 -### Managing packages - -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)." - -### Contacting support +### Administrar paquetes {% if currentVersion == "free-pro-team@latest" %} -If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use the [feedback form for {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages). +Puedes borrar un paquete en la +interface de usuario de {% data variables.product.product_name %} o utilizando la API de REST. Para obtener más información, consulta la sección "[API del {% data variables.product.prodname_registry %}](/rest/reference/packages)". +{% endif %} -Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if: +{% if currentVersion ver_gt "enterprise-server@3.0" %} +Puedes borrar un paquete público o privado en la +interfaz de usuario de {% data variables.product.product_name %}. O, para los paquetes con alcance de repo, puedes borrar una versión de un paquete privado utilizando GraphQL. +{% endif %} -* You experience anything that contradicts the documentation -* You encounter vague or unclear errors -* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information +{% if currentVersion ver_lt "enterprise-server@3.1" %} +Puedes borrar una versión de un paquete privado en la +interface de usuario de {% data variables.product.product_name %} o utilizando la API de GraphQL. +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +Puedes borrar una versión de un paquete en la +interface de usuario de {% data variables.product.product_name %} o utilizando la API de GraphQL. +{% endif %} + +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 "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}" y "[Formar llamados 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 %} -If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators. +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/quickstart.md b/translations/es-ES/content/packages/quickstart.md index 4b1c6f0287..fca2a186d9 100644 --- a/translations/es-ES/content/packages/quickstart.md +++ b/translations/es-ES/content/packages/quickstart.md @@ -1,7 +1,7 @@ --- title: Guía de inciio rápido para GitHub Packages intro: 'Publica en el {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %}.' -allowTitleToDifferFromFilename: true +allowTitleToDifferFromFilename: verdadero versions: free-pro-team: '*' enterprise-server: '>=2.22' diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..c057fd3acc --- /dev/null +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -0,0 +1,68 @@ +--- +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 + - /github/working-with-github-pages/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - páginas +--- + +### 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` | + +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." + +Recomendamos siempre usar un subdominio `www`, incluso si también usas un dominio apex. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. 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)". + +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 %}. + +#### Subdominios personalizados + +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. 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 %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." + +### 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)". + +### Leer más + +- "[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/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md new file mode 100644 index 0000000000..9351ab1d61 --- /dev/null +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -0,0 +1,23 @@ +--- +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 + - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - páginas +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000..4cbda80ea8 --- /dev/null +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,121 @@ +--- +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 + - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - páginas +--- + +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 subdominio personalizado o de `www` tal como `www.example.com` o `blog.example.com`, debes agregar tu dominio en la configuración de repositorio, el cual creará un archivo de CNAME en el repositorio de tu sitio. Después de esto, configura un registro de CNAME con tu proveedor de DNS. + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. 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-subdomain.png) +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 + +To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider. + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)." + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. 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-apex-domain.png) +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 %} + - To create `A` records, point your apex domain to the IP addresses for {% 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 %} + +### Configuring an apex domain and the `www` subdomain variant + +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. + +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." + +After you configure the apex domain, you must to configure a CNAME record with your DNS provider. + +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. +```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 +``` +### Removing a custom domain + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain," click **Remove**. ![Botón de guardar dominio personalizado](/assets/images/help/pages/remove-custom-domain.png) + +### Leer más + +- "[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/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..c656374302 --- /dev/null +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,65 @@ +--- +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 + - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - páginas +--- + +### 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. +- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`. +- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. 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`. + + The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. 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-an-apex-domain)". + +{% 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/pages/getting-started-with-github-pages/about-github-pages.md b/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000..b47c4f9923 --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -0,0 +1,152 @@ +--- +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 + - /github/working-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +### 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 alojar 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 %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} Para obtener más información, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". +{% 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@3.0" %} +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 "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-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" %} +Si publicas tu sitio de forma privada, la URL de éste será diferente. Para obtener más información, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% 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 donde tu sitio está disponible depende de si el aislamiento del subdominio está habilitado 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 la sección "[Habilitar el aislamiento del subdominio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" o contacta a tu administrador de 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 `master`. Si el repositorio para tu sitio de usuario u organización tiene una rama `master`, 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 `master` 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). + +In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. Para encontrar una lista de usos prohibidos, consulta la sección "[Condiciones adicionales de producto de {% data variables.product.prodname_dotcom %} para las {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)". +{% 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). + +### Leer más + +- [{% 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/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000..de71bfbec2 --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,46 @@ +--- +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - páginas +--- + +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 %} +{% data reusables.pages.sidebar-pages %} +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. + +### Leer más + +- [Temas](https://jekyllrb.com/docs/themes/) en el sitio de Jekyll diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..6b0f25831e --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: Cambiar la visibilidad de tu sitio de GitHub Pages +intro: 'Puedes administrar el control de acceso para tu sitio de proyecto si lo publicas de forma pública o privada.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: Las personas con permisos administrativos en un repositorio pueden cambiar la visibilidad de un sitio de {% data variables.product.prodname_pages %}. +redirect_from: + - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site +--- + +### Acerca del control de acceso para los sitios de {% data variables.product.prodname_pages %} + +Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. Con el control de acceso puedes elegir publicar el sitio de forma pública para cualquiera en internet o de forma privada para las personas con acceso de lectura en tu repositorio. Un sitio que se publica de forma privada puede utilizarse para compartir tu documentación o base de conocimientos internos con los miembros de tu empresa. No puedes administrar el control de accesos para el sitio de una organización. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Los sitios que se publican de forma privada se encuentran disponibles en un subdominio diferente que el de aquellos sitios que se publican de forma pública. Esto garantiza que tu sitio de {% data variables.product.prodname_pages %} es seguro desde el momento en el que se publica: + +- Aseguramos cada dominio de `*.pages.github.io` automáticamente con un certificado TLS y requerimos HSTS para garantizar que los buscadores siempre sirvan la página a través de HTTPS. +- Utilizamos un subdominio único para la página privada para garantizar que otros repositorios en tu organización no puedan publicar contenido en el mismo origen que la página privada. Esto protege a tu página privada de que tenga un ataque de "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". También es por esto que no hospedamos sitios de {% data variables.product.prodname_pages %} en el dominio `github.com`. + +Puedes ver el subdominio único de tu sitio en la pestaña de páginas de la configuración de tu repositorio. Si estás utilizando un generador estático que se configuró para compilar el sitio con el nombre de repositorio como ruta, podrías necesitar actualizar la configuración para el generador de sitio estático cuando cambies el sitio a privado. Para obtener más información, consulta la sección "[Configurar a Jekyll en tu sitio de {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" o la documentación de tu generador de sitio estático. + +Para utilizar un dominio más corto y memorable para tu sitio privado de {% data variables.product.prodname_pages %}, puedes configurar un dominio personalizado. Para obtener más información, consulta la sección "[Configurar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site)". + +### Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Debajo de "{% data variables.product.prodname_pages %}", selecciona el menú desplegable de **visibilidad de {% data variables.product.prodname_pages %}** y luego da clic en una visibilidad. ![Menú desplegable para elegir la visibilidad para tu sitio](/assets/images/help/pages/public-or-private-visibility.png) +4. Para ver tu sitio publicado, debajo de "{% data variables.product.prodname_pages %}", da clic en la URL del mismo. ![URL de tu sitio publicado de forma privada](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000..fa5c07f8ac --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,38 @@ +--- +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@3.0" %} 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 + - /github/working-with-github-pages/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: '*' +topics: + - páginas +--- + +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 + +Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} 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 %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% 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). ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %} +3. Debajo de "{% data variables.product.prodname_pages %}", usa el menú desplegable **Source** (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/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000..8bd58d023f --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,35 @@ +--- +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 + - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +{% 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: + ```yaml + --- + 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 %} + +### Leer más + +- [Texto preliminar](http://jekyllrb.com/docs/frontmatter) en la documentación de Jekyll diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000..960ae9fe4e --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,63 @@ +--- +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 + - /github/working-with-github-pages/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Crear un repositorio para tu sitio + +{% data reusables.pages.new-or-existing-repo %} + +{% 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.private_pages_are_public_warning %} + +{% 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.sidebar-pages %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% 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.html`. + +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)". + +### Leer más + +- "[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/pages/getting-started-with-github-pages/index.md b/translations/es-ES/content/pages/getting-started-with-github-pages/index.md new file mode 100644 index 0000000000..f0f80c2e7c --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/index.md @@ -0,0 +1,26 @@ +--- +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 + - /github/working-with-github-pages/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +{% 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 /changing-the-visibility-of-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 %} \ No newline at end of file diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000..57efa06318 --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,55 @@ +--- +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 + - /github/working-with-github-pages/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +topics: + - páginas +--- + +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)". + +{% 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 %} +{% data reusables.pages.sidebar-pages %} +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/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000..ca97aebcd0 --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Anular la publicación de un sitio de Páginas de GitHub +intro: 'Puedes publicar tu sitio de {% data variables.product.prodname_pages %} para que éste deje de estar disponible.' +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 + - /github/working-with-github-pages/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: '*' +topics: + - páginas +--- + +### 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. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. Debajo de "{% data variables.product.prodname_pages %}", usa el menú desplegable **Source** (Fuente) y seleccionar **None** (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/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/es-ES/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000..b1ec9205c4 --- /dev/null +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,24 @@ +--- +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 + - /github/working-with-github-pages/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - páginas +--- + +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_. + +### Leer más + +- "[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/pages/index.md b/translations/es-ES/content/pages/index.md new file mode 100644 index 0000000000..3d719c5fe7 --- /dev/null +++ b/translations/es-ES/content/pages/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages Documentation +shortTitle: Páginas de GitHub +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 + - /github/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +{% link_with_intro /getting-started-with-github-pages %} +{% link_with_intro /setting-up-a-github-pages-site-with-jekyll %} +{% link_with_intro /configuring-a-custom-domain-for-your-github-pages-site %} \ No newline at end of file diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000..9951f82ed2 --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -0,0 +1,131 @@ +--- +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 + - /github/working-with-github-pages/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +### 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. + +```yaml +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` +- start with `_`, `.`, or `#` +- 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 soportado 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*. + +```yaml +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/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..712f9528b2 --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,62 @@ +--- +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 + - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +### 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 creará la rama `gh-pages` a menos de que agregues 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: + ```ruby + 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: + ```yaml + 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/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..cd1abd601c --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,71 @@ +--- +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +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: + ```scss + --- + --- + + @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. + +### Leer más + +- "[Crear archivos nuevos](/articles/creating-new-files)" diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..4b5253b2e4 --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,72 @@ +--- +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 + - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +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 %} + +¡Ahora tu publicación debería estar disponible en tu sitio! Si la URL base de tu sitio es `https://octocat.github.io`, entonces tu publicación nueva se ubicará en `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/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000..0fb8295197 --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,116 @@ +--- +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 + - /github/working-with-github-pages/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: '*' +topics: + - páginas +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### 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.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.pages.private_pages_are_public_warning %} + +{% 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 nuevo de Jekyll, utiliza el comando `jekyll new`: + ```shell + $ jekyll new . + # Creates a Jekyll site in the current directory + ``` +8. Abre el Gemfile que creó Jekyll. +1. Agrega "#" en el inicio de la línea que comienza con `gem "jekyll"` para comentar esta línea. +1. Agrega la gema `github-pages` editando la línea que comienza con `# gem "github-pages"`. Cambia la línea a: + + ```shell + gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins + ``` + + Reemplaza _GITHUB-PAGES-VERSION_ con la última versión compatible de la gema `github-pages`. Puedes encontrar esta versión aquí: "[Versiones de la dependencia](https://pages.github.com/versions/)". + + La versión correcta de Jekyll se instalará como una dependencia de la gema `github-pages`. +10. Guarda y cierra el Gemfile. +11. Desde la línea de comandos, ejecuta `bundle update`. +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.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md new file mode 100644 index 0000000000..37001c0b3e --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md @@ -0,0 +1,25 @@ +--- +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 + - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..f12d85a403 --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,36 @@ +--- +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 + - /github/working-with-github-pages/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: '*' +topics: + - páginas +--- + +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 %} + +### Leer más + +- [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/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000..f479302358 --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,62 @@ +--- +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 + - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +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. Run `bundle install`. +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`. + +### Leer más + +- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) en la documentación de Jekyll diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..1ffa26ecf6 --- /dev/null +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,191 @@ +--- +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 + - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - páginas +--- + +### 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*: +```yaml +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/rest/guides/getting-started-with-the-rest-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md index 8afe6d6681..430c784124 100644 --- 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 @@ -170,7 +170,7 @@ $ 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" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -207,7 +207,7 @@ API de {% data variables.product.product_name %} es compatible con la creación necesitamos hacer `POST` en algunos JSON que contengan los detalles y las opciones de configuración. ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -242,7 +242,7 @@ La IU de informe de problemas en {% data variables.product.product_name %} prete 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" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -250,7 +250,7 @@ Para obtener únicamente los [informes de problemas bajo alguna de tus organizac /orgs//issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -283,7 +283,7 @@ Ahora que hemos visto cómo paginar las listas de informes de problemas, vamos a 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' \ +$ curl -i -H 'Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md index 1f8fda8b12..44cc689ed3 100644 --- a/translations/es-ES/content/rest/reference/enterprise-admin.md +++ b/translations/es-ES/content/rest/reference/enterprise-admin.md @@ -1,6 +1,6 @@ --- -title: GitHub Enterprise administration -allowTitleToDifferFromFilename: true +title: Administración de GitHub Enterprise +allowTitleToDifferFromFilename: verdadero redirect_from: - /v3/enterprise-admin - /v3/enterprise @@ -8,51 +8,50 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- -You can use these endpoints to administer your enterprise. +You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints to administer your enterprise account. {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu. +**Nota:** Este artículo aplica a {% data variables.product.prodname_ghe_cloud %}. Para ver la versión de {% data variables.product.prodname_ghe_managed %} o de {% data variables.product.prodname_ghe_server %}, utiliza el menú desplegable de **{% data ui.pages.article_version %}**. {% endnote %} {% endif %} -### Endpoint URLs +### URL de las Terminales -REST API endpoints{% if enterpriseServerVersions contains currentVersion %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: +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/ +{% data variables.product.api_url_pre %} ``` {% if enterpriseServerVersions contains currentVersion %} -[Management Console](#management-console) API endpoints are only prefixed with a hostname: +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 %} -### Authentication +### Autenticación -Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% if enterpriseServerVersions contains currentVersion %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} -OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %} +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 %} -Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% if enterpriseServerVersions contains currentVersion %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. +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 %} -### Version information +### Información de la versión -The current version of your enterprise is returned in the response header of every API: -`X-GitHub-Enterprise-Version: {{currentVersion}}.0` -You can also read the current version by calling the [meta endpoint](/rest/reference/meta/). +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 %} @@ -62,7 +61,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% if currentVersion == "free-pro-team@latest" %} -## Audit log +## Registro de auditoría {% for operation in currentRestOperations %} {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} @@ -71,7 +70,7 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% endif %} {% if currentVersion == "free-pro-team@latest" %} -## Billing +## Facturación {% for operation in currentRestOperations %} {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %} @@ -79,9 +78,11 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ## GitHub Actions +{% data reusables.actions.ae-beta %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} {% endfor %} @@ -91,46 +92,46 @@ You can also read the current version by calling the [meta endpoint](/rest/refer {% if currentVersion == "free-pro-team@latest" %} ## SCIM -### SCIM Provisioning for Enterprises +### Aprovisionamiento de SCIM para Empresas -SCIM-enabled Identity Providers (IdPs) can use the SCIM API to automate the provisioning of enterprise membership. The {% data variables.product.product_name %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). +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/). -The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/{enterprise}/` as the SCIM endpoint. +El IdP debe utilizar `{% data variables.product.api_url_code %}/scim/v2/enterprises/{enterprise}/` como la terminal de SCIM. {% note %} -**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". {% endnote %} -### Authenticating calls to the SCIM API +### Autenticar las llamadas a la API de SCIM -You must authenticate as an owner of a {% data variables.product.product_name %} enterprise to use its SCIM API. The API expects an [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) token to be included in the `Authorization` header. You may also use a personal access token, but you must first [authorize it for use with your SAML SSO enterprise](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). +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). -### Mapping of SAML and SCIM data +### Mapeo de los datos de SAML y de SCIM -The SAML IdP and the SCIM client must use matching `NameID` and `userName` values for each user. This allows a user authenticating through SAML to be linked to their provisioned SCIM identity. +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. -SCIM groups are matched with {% data variables.product.product_name %} organizations that have the exact same name, and are owned by the enterprise account. +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. -The SAML IdP and SCIM client must be configured to exactly match the `displayName` of the SCIM group with the name of the corresponding {% data variables.product.product_name %} organization. This allows {% data variables.product.product_name %} to link the SCIM group with the {% data variables.product.product_name %} organization membership. +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 %}. -### Supported SCIM User attributes +### Atributos de Usuario de SCIM compatibles -Name | Type | Description ------|------|-------------- -`userName`|`string` | The username for the user. -`name.givenName`|`string` | The first name of the user. -`name.lastName`|`string` | The last name of the user. -`emails` | `array` | List of user emails. -`externalId` | `string` | This identifier is generated by the SAML provider, and is used as a unique ID by the SAML provider to match against a GitHub user. You can find the `externalID` for a user either at the SAML provider, or using the [List SCIM provisioned identities for an enterprise](#list-scim-provisioned-identities-for-an-enterprise) endpoint and filtering on other known attributes, such as a user's GitHub username or email address. -`id` | `string` | Identifier generated by the GitHub SCIM endpoint. -`active` | `boolean` | Used to indicate whether the identity is active (true) or should be deprovisioned (false). -`groups` | `array` | Optional list of SCIM group IDs the user is a member of. +| 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 %} -**Note:** Endpoint URLs for the SCIM API are case sensitive. For example, the first letter in the `Users` endpoint must be capitalized: +**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} @@ -138,12 +139,12 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} {% endnote %} -### Supported SCIM Group attributes +### Atributos del Grupo de SCIM compatibles -Name | Type | Description ------|------|-------------- -`displayName` | `string` | The name of the SCIM group, which must exactly match the name of the corresponding {% data variables.product.product_name %} organization. For example, if the URL of the organization is `https://github.com/octo-org`, the group name must be `octo-org`. -`members`| `array` | List of SCIM user IDs that are members of the group. +| 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 %} @@ -153,10 +154,9 @@ Name | Type | Description {% if currentVersion == "github-ae@latest" %} -## Encryption at rest +## Cifrado estático -You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. -For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)." +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 %} @@ -165,9 +165,9 @@ For more information, see "[Configuring data encryption for your enterprise](/ad {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## Admin stats +## Estadísticas de los Administradores -The Admin Stats API provides a variety of metrics about your installation. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. +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 %} @@ -177,9 +177,9 @@ The Admin Stats API provides a variety of metrics about your installation. *It i {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -## Announcements +## Anuncios -The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." +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 %} @@ -189,11 +189,11 @@ The Announcements API allows you to manage the global announcement banner in you {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## Global webhooks +## Webhooks globales -Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types. +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). -*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks). +*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 %} @@ -205,9 +205,9 @@ Global webhooks are installed on your enterprise. You can use global webhooks to ## LDAP -You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization. +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. -With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled. +Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, por sus siglas en inglés) al cual mapea un usuario o equipo. Toma en cuenta que las terminales de LDAP generalmente solo son efectivas si tu aplicativo de {% data variables.product.product_name %} [habilitó la sincronización con LDAP](/enterprise/admin/authentication/using-ldap). La terminal de [mapeo de LDAP para actualización para un usuario](#update-ldap-mapping-for-a-user) puede utilizarse cuando se habilita LDAP, aún si la sincronización con LDAP está inhabilitada. {% for operation in currentRestOperations %} {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %} @@ -217,9 +217,9 @@ With the LDAP mapping endpoints, you're able to update the Distinguished Name (D {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## License +## Licencia -The License API provides information on your Enterprise license. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. +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 %} @@ -229,31 +229,31 @@ The License API provides information on your Enterprise license. *It is only ava {% if enterpriseServerVersions contains currentVersion %} -## Management console +## Consola de administración -The Management Console API helps you manage your {% data variables.product.product_name %} installation. +La API de la Consola de Administración te ayuda a administrar tu instalación de {% data variables.product.product_name %}. {% tip %} -You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`. +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`. -If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects. +Si no quieres proporcionar un número de puerto, necesitarás configurar tu herramienta para seguir automáticamente las redirecciones. -You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/). +Podría que también necesites agregar el [marcador `-k`](http://curl.haxx.se/docs/manpage.html#-k) cuando utilices `curl`, ya que {% data variables.product.product_name %} utiliza un certificado auto-firmado antes de que [agregues tu propio certificado TLS](/enterprise/admin/guides/installation/configuring-tls/). {% endtip %} -### Authentication +### Autenticación -You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license). +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). -Use the `api_key` parameter to send this token with each request. For example: +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' ``` -You can also use standard HTTP authentication to send this token. For example: +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' @@ -266,9 +266,9 @@ $ curl -L 'https://api_key:your-amazing-password@hostname: {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## Organizations +## Organizaciones -The Organization Administration API allows you to create organizations on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. +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 %} @@ -278,25 +278,22 @@ The Organization Administration API allows you to create organizations on your e {% if enterpriseServerVersions contains currentVersion %} -## Organization pre-receive hooks +## Ganchos de Pre-recepción de la Organización -The Organization Pre-receive Hooks API allows you to view and modify -enforcement of the pre-receive hooks that are available to an organization. +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. -### Object attributes +### Atributos de objeto -| Name | Type | Description | -|----------------------------------|-----------|-----------------------------------------------------------| -| `name` | `string` | The name of the hook. | -| `enforcement` | `string` | The state of enforcement for the hook on this repository. | -| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. | -| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | +| 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. | -Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject -any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. +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` may be a link to this endpoint or this hook's global -configuration. Only site admins are able to access the global configuration. +`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 %} @@ -306,31 +303,31 @@ configuration. Only site admins are able to access the global configuration. {% if enterpriseServerVersions contains currentVersion %} -## Pre-receive environments +## Ambientes de pre-recepción -The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. +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. -### Object attributes +### Atributos de objeto -#### Pre-receive Environment +#### Ambiente de pre-recepción -| Name | Type | Description | -|-----------------------|-----------|----------------------------------------------------------------------------| -| `name` | `string` | The name of the environment as displayed in the UI. | -| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. | -| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. | -| `download` | `object` | This environment's download status. | -| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. | +| 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. | +| `download` | `objeto` | El estado de descarga de este ambiente. | +| `hooks_count` | `número` | La cantidad de ganchos de pre-recepción que utilizan este ambiente. | -#### Pre-receive Environment Download +#### Descarga del Ambiente de Pre-recepción -| Name | Type | Description | -|-----------------|----------|---------------------------------------------------------| -| `state` | `string` | The state of the most recent download. | -| `downloaded_at` | `string` | The time when the most recent download started. | -| `message` | `string` | On failure, this will have any error messages produced. | +| 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. | -Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`. +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 %} @@ -339,26 +336,24 @@ Possible values for `state` are `not_started`, `in_progress`, `success`, `failed {% endif %} {% if enterpriseServerVersions contains currentVersion %} -## Pre-receive hooks +## Ganchos de pre-recepción -The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks. *It is only available to -[authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. +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. -### Object attributes +### Atributos de objeto -#### Pre-receive Hook +#### Ganchos de pre-recepción -| Name | Type | Description | -|----------------------------------|-----------|-----------------------------------------------------------------| -| `name` | `string` | The name of the hook. | -| `script` | `string` | The script that the hook runs. | -| `script_repository` | `object` | The GitHub repository where the script is kept. | -| `environment` | `object` | The pre-receive environment where the script is executed. | -| `enforcement` | `string` | The state of enforcement for this hook. | -| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. | +| Nombre | Type | Descripción | +| -------------------------------- | ----------- | ----------------------------------------------------------------------------------- | +| `name (nombre)` | `secuencia` | El nombre del gancho. | +| `script` | `secuencia` | El script que ejecuta el gancho. | +| `script_repository` | `objeto` | El repositorio de GitHub en donde se mantiene el script. | +| `environment` | `objeto` | El ambiente de pre-recepción en donde se ejecuta el script. | +| `enforcement` | `secuencia` | El estado de las imposiciones para este gancho. | +| `allow_downstream_configuration` | `boolean` | Si las imposiciones pueden o no ignorarse a nivel de organización o de repositorio. | -Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject -any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. +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 %} @@ -368,22 +363,21 @@ any pushes that result in a non-zero status. `testing` means the script will run {% if enterpriseServerVersions contains currentVersion %} -## Repository pre-receive hooks +## Ganchos de pre-recepción del repositorio -The Repository Pre-receive Hooks API allows you to view and modify -enforcement of the pre-receive hooks that are available to a repository. +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. -### Object attributes +### Atributos de objeto -| Name | Type | Description | -|---------------------|----------|-----------------------------------------------------------| -| `name` | `string` | The name of the hook. | -| `enforcement` | `string` | The state of enforcement for the hook on this repository. | -| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | +| 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. | -Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. +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` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level. +`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 %} @@ -392,9 +386,9 @@ Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disab {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} -## Users +## Usuarios -The User Administration API allows you to suspend{% if enterpriseServerVersions contains currentVersion %}, unsuspend, promote, and demote{% endif %}{% if currentVersion == "github-ae@latest" %} and unsuspend{% endif %} users on your enterprise. *It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it. +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 %} diff --git a/translations/es-ES/content/rest/reference/git.md b/translations/es-ES/content/rest/reference/git.md index 4ec22073b9..d14914225a 100644 --- a/translations/es-ES/content/rest/reference/git.md +++ b/translations/es-ES/content/rest/reference/git.md @@ -1,6 +1,6 @@ --- title: Base de datos de Git -allowTitleToDifferFromFilename: true +allowTitleToDifferFromFilename: verdadero redirect_from: - /v3/git versions: diff --git a/translations/es-ES/content/rest/reference/migrations.md b/translations/es-ES/content/rest/reference/migrations.md index 6eca9446b4..d90eccfa81 100644 --- a/translations/es-ES/content/rest/reference/migrations.md +++ b/translations/es-ES/content/rest/reference/migrations.md @@ -16,7 +16,7 @@ topics: ## Organización -La API de Migraciones solo está disponible para los propietarios autenticados de la organización. Para obtener más información, consulta las secciones "[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)". +La API de Migraciones solo está disponible para los propietarios autenticados de la organización. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/es-ES/content/rest/reference/orgs.md b/translations/es-ES/content/rest/reference/orgs.md index 8616e4a883..53dc4aee90 100644 --- a/translations/es-ES/content/rest/reference/orgs.md +++ b/translations/es-ES/content/rest/reference/orgs.md @@ -1,6 +1,6 @@ --- title: Organizaciones -allowTitleToDifferFromFilename: true +allowTitleToDifferFromFilename: verdadero redirect_from: - /v3/orgs versions: diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md index 8b233f654a..44501ffc68 100644 --- a/translations/es-ES/content/rest/reference/repos.md +++ b/translations/es-ES/content/rest/reference/repos.md @@ -1,6 +1,6 @@ --- title: Repositorios -allowTitleToDifferFromFilename: true +allowTitleToDifferFromFilename: verdadero redirect_from: - /v3/repos versions: @@ -193,7 +193,7 @@ El usuario autenticado será el autor de cualquier fusión que se realice a trav ## 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. Solo los propietarios autenticados pueden acceder a la información sobre el sitio y sobre las compilaciones{% if currentVersion != "github-ae@latest" %}, incluso si los sitios web son públicos{% endif %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-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. Solo los propietarios autenticados pueden acceder a la información sobre el sitio y sobre las compilaciones{% if currentVersion != "github-ae@latest" %}, incluso si los sitios web son públicos{% endif %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". En las terminales de la API de {% data variables.product.prodname_pages %} que llevan una clave de `status` en su respuesta, el valor puede ser uno de entre los siguientes: * `null`: El sitio aún tiene que crearse. @@ -205,7 +205,7 @@ En las terminales de la API de {% data variables.product.prodname_pages %} que l 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_. + - `branch`: La rama del repositorio que se utilizó para publicar los [archivos de código fuente de tu sitio](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por ejemplo, _main_ o _gh-pages_. - `path`: El directorio del repositorio desde el cual publica el sitio. Podría ser `/` o `/docs`. {% for operation in currentRestOperations %} diff --git a/translations/es-ES/content/rest/reference/scim.md b/translations/es-ES/content/rest/reference/scim.md index f35263a480..dd41a29c3f 100644 --- a/translations/es-ES/content/rest/reference/scim.md +++ b/translations/es-ES/content/rest/reference/scim.md @@ -14,7 +14,7 @@ Los proveedores de identidad (IdP) habilitados para SCIM utilizan la API de SCIM {% 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)". +**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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". {% endnote %} diff --git a/translations/es-ES/content/rest/reference/teams.md b/translations/es-ES/content/rest/reference/teams.md index 7356ad82d0..e7e0fdce3e 100644 --- a/translations/es-ES/content/rest/reference/teams.md +++ b/translations/es-ES/content/rest/reference/teams.md @@ -18,7 +18,7 @@ Esta API solo está disponible para los miembros autenticados de la [organizatio ## Debates -La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer las publicaciones de debates públicos. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)". Para aprender más sobre cómo comentar en una publicación de debate, consulta la [API de comentarios para debates de equipo](/rest/reference/teams#discussion-comments). Esta API solo está disponible para los miembros autenticados de la organization del equipo. +La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer las publicaciones de debates públicos. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender más sobre cómo comentar en una publicación de debate, consulta la [API de comentarios para debates de equipo](/rest/reference/teams#discussion-comments). Esta API solo está disponible para los miembros autenticados de la organization del equipo. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -26,7 +26,7 @@ La API de debates de equipo te permite obtener, crear, editar y borrar las publi ## Comentarios de debate -La API de comentarios para debates de equipo te permite obtener, crear, editar y borrar los comentarios del debate en una publicación de un [debate de equipo](/rest/reference/teams#discussions). Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer los comentarios de un debate público. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)". Esta API solo está disponible para los miembros autenticados de la organization del equipo. +La API de comentarios para debates de equipo te permite obtener, crear, editar y borrar los comentarios del debate en una publicación de un [debate de equipo](/rest/reference/teams#discussions). Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer los comentarios de un debate público. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API solo está disponible para los miembros autenticados de la organization del equipo. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -39,7 +39,7 @@ Esta API solo está disponible para los miembros autenticados de la organization {% 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". +**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 %} @@ -54,7 +54,7 @@ Esta API solo está disponible para los miembros autenticados de la organization 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". +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 %} diff --git a/translations/es-ES/data/release-notes/2-20/11.yml b/translations/es-ES/data/release-notes/2-20/11.yml index f76f87c961..58c9d5e5cb 100644 --- a/translations/es-ES/data/release-notes/2-20/11.yml +++ b/translations/es-ES/data/release-notes/2-20/11.yml @@ -1,4 +1,5 @@ -date: '2020-07-09' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-20/12.yml b/translations/es-ES/data/release-notes/2-20/12.yml index 548dc7d854..84a499fe65 100644 --- a/translations/es-ES/data/release-notes/2-20/12.yml +++ b/translations/es-ES/data/release-notes/2-20/12.yml @@ -1,4 +1,5 @@ -date: '2020-07-21' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-20/15.yml b/translations/es-ES/data/release-notes/2-20/15.yml index aa3c664487..ea9c2f763c 100644 Binary files a/translations/es-ES/data/release-notes/2-20/15.yml 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 index c660f62685..fbab7d0c79 100644 --- a/translations/es-ES/data/release-notes/2-20/16.yml +++ b/translations/es-ES/data/release-notes/2-20/16.yml @@ -1,8 +1,9 @@ -date: '2020-09-08' +--- +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 %}' + - "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 %}' diff --git a/translations/es-ES/data/release-notes/2-20/17.yml b/translations/es-ES/data/release-notes/2-20/17.yml index fa9a189fff..153edb5399 100644 --- a/translations/es-ES/data/release-notes/2-20/17.yml +++ b/translations/es-ES/data/release-notes/2-20/17.yml @@ -1,4 +1,5 @@ -date: '2020-09-23' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-20/18.yml b/translations/es-ES/data/release-notes/2-20/18.yml index 373eabb7a4..cd73fbc9be 100644 --- a/translations/es-ES/data/release-notes/2-20/18.yml +++ b/translations/es-ES/data/release-notes/2-20/18.yml @@ -1,4 +1,5 @@ -date: '2020-10-09' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-20/5.yml b/translations/es-ES/data/release-notes/2-20/5.yml index 69aede8d38..f196773ea1 100644 --- a/translations/es-ES/data/release-notes/2-20/5.yml +++ b/translations/es-ES/data/release-notes/2-20/5.yml @@ -1,4 +1,5 @@ -date: '2020-04-07' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-20/7.yml b/translations/es-ES/data/release-notes/2-20/7.yml index 9ed217f7af..79ee352ed5 100644 --- a/translations/es-ES/data/release-notes/2-20/7.yml +++ b/translations/es-ES/data/release-notes/2-20/7.yml @@ -1,4 +1,5 @@ -date: '2020-05-05' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-21/0.yml b/translations/es-ES/data/release-notes/2-21/0.yml index 93816fbe08..24b0032636 100644 --- a/translations/es-ES/data/release-notes/2-21/0.yml +++ b/translations/es-ES/data/release-notes/2-21/0.yml @@ -1,4 +1,5 @@ -date: '2020-06-09' +--- +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 %}' @@ -13,13 +14,13 @@ sections: 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 %}' + - "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 %}' + - "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 %}' @@ -69,4 +70,4 @@ sections: - '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 %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error. + - "El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error." diff --git a/translations/es-ES/data/release-notes/2-21/18.yml b/translations/es-ES/data/release-notes/2-21/18.yml new file mode 100644 index 0000000000..3e32e614bf --- /dev/null +++ b/translations/es-ES/data/release-notes/2-21/18.yml @@ -0,0 +1,16 @@ +--- +date: '01-04-2021' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Los paquetes se actualizaron a las últimas versiones de seguridad. + bugs: + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. + - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. + - 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. + - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres. + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com. + - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos. diff --git a/translations/es-ES/data/release-notes/2-21/2.yml b/translations/es-ES/data/release-notes/2-21/2.yml index c7bb2098c5..87f3708598 100644 --- a/translations/es-ES/data/release-notes/2-21/2.yml +++ b/translations/es-ES/data/release-notes/2-21/2.yml @@ -1,4 +1,5 @@ -date: '2020-07-09' +--- +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 %}' @@ -17,4 +18,4 @@ sections: - '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 %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error. + - "El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error." diff --git a/translations/es-ES/data/release-notes/2-21/3.yml b/translations/es-ES/data/release-notes/2-21/3.yml index 1261970097..1c3225e758 100644 --- a/translations/es-ES/data/release-notes/2-21/3.yml +++ b/translations/es-ES/data/release-notes/2-21/3.yml @@ -1,11 +1,12 @@ -date: '2020-07-21' +--- +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 %}' + - "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 %}' @@ -14,4 +15,4 @@ sections: - '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 %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error. + - "El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error." diff --git a/translations/es-ES/data/release-notes/2-21/6.yml b/translations/es-ES/data/release-notes/2-21/6.yml index 8638d1d9cd..889993d011 100644 Binary files a/translations/es-ES/data/release-notes/2-21/6.yml 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 index 6ec30ff084..9afc786b39 100644 --- a/translations/es-ES/data/release-notes/2-21/7.yml +++ b/translations/es-ES/data/release-notes/2-21/7.yml @@ -1,9 +1,10 @@ -date: '2020-09-08' +--- +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 %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` ya no falla. + - "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 %}" + - "El configurar el permiso de un repositorio en `Triage` or `Maintain` ya no falla." 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 %}' diff --git a/translations/es-ES/data/release-notes/2-21/8.yml b/translations/es-ES/data/release-notes/2-21/8.yml index c65ab25fcb..c858a25338 100644 --- a/translations/es-ES/data/release-notes/2-21/8.yml +++ b/translations/es-ES/data/release-notes/2-21/8.yml @@ -1,4 +1,5 @@ -date: '2020-09-23' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-21/9.yml b/translations/es-ES/data/release-notes/2-21/9.yml index 29713346d8..28190bfce8 100644 --- a/translations/es-ES/data/release-notes/2-21/9.yml +++ b/translations/es-ES/data/release-notes/2-21/9.yml @@ -1,4 +1,5 @@ -date: '2020-10-09' +--- +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 %}' diff --git a/translations/es-ES/data/release-notes/2-22/0.yml b/translations/es-ES/data/release-notes/2-22/0.yml index 9e52b64b34..639f60af63 100644 --- a/translations/es-ES/data/release-notes/2-22/0.yml +++ b/translations/es-ES/data/release-notes/2-22/0.yml @@ -1,72 +1,85 @@ +--- intro: GitHub se emociona en presentar GitHub Enterprise Server 2.22.0. -date: '2020-09-23' +date: '23-09-2020' sections: features: - - heading: GitHub Actions Beta + - + heading: GitHub Actions Beta notes: - | [GitHub Actions](https://github.com/features/actions) es una solución flexible y poderosa para IC/DC y para la automatización de flujos de trabajo. GitHub Actions en Enterprise Server incluye herramientas que te ayudan a administrar el servicio, incluyendo las métricas clave para la Consola de Administración, bitácoras de auditoría y controles de acceso para ayudarte a controlar los lanzamientos. Necesitarás proporcionar tu propio [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) y ejecturores para las GitHub Actions. AWS S3, Azure Blob Storage y MinIO son compatibles. 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 las GitHub Actions. 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/775 {% endcomment %} - - heading: GitHub Packages Beta + - + 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 + - + 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 + - + 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 + - + 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 + - + 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 + - + 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 + - + 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 %}' + - 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 %}' + - 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 + - + 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 + - 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 %}' + - 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 %}' + - 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 + - + 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 + - + heading: Cambios a la API notes: - | #### Vistas previas graduadas @@ -78,7 +91,8 @@ sections: #### 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: Cambios en el Controlador de VMware Network + - + heading: Cambios en el Controlador de VMware Network notes: - | El adaptador de red predeterminado de GitHub Enterprise Server para los clientes de VMware se cambió de E1000 a VMXNET3, comenzando con el lanzamiento 2.22.0. Cuando se actualiza desde una versión anterior a la 2.22.0 o superior, si se detecta un adaptador de red E1000 durante la verificación de pre-mejora, se mostrará el siguiente mensaje en la línea de comandos: @@ -90,36 +104,40 @@ sections: ``` El administrador puede elegir actualizar el tipo de adaptador de red a VMXNET3 ya sea antes o después de que se mejore el GitHub Enterprise Server. El aplicativo virtual necesitará apagarse para este cambio. Los clientes deben seguir los pasos recomendados de VMware para [cambiar la configuración del adaptador de red de la máquina virtual](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) a VMXNET3. Por favor, nota que `VMXNET3`no será una opción si la versión del SO para el aplicativo virtual se configura en `Other Linux (64-bit)`. En este caso, primero se tendrá que cambiar la versión del SO de `Other Linux (64-bit)` a `Other 2.6.x Linux (64-bit)` o, en caso de que esté disponible, a `Debian GNU/Linux 9` . Te recomendamos probar estos cambios en una [instancia de montaje](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) antes de que se mueva a un ambiente productivo de 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 %}' + - 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 + - + 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 + - + 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 + - + 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 + - + 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/).' + - 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 requiere por lo menos las [Utilidades de Respaldo de GitHub Enterprise](https://github.com/github/backup-utils) 2.22.0 para hacer [Respaldos y Recuperación de Desastres](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/).' + - GitHub Enterprise Server 2.22 requiere por lo menos las [Utilidades de Respaldo de GitHub Enterprise](https://github.com/github/backup-utils) 2.22.0 para hacer [Respaldos y Recuperación de Desastres](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 %}' + - 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 %}' + - 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 index 392f2e211a..9eee290911 100644 --- a/translations/es-ES/data/release-notes/2-22/1.yml +++ b/translations/es-ES/data/release-notes/2-22/1.yml @@ -1,4 +1,5 @@ -date: '2020-10-09' +--- +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 %}' @@ -55,16 +56,16 @@ sections: - | 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 %}' + - 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 %}' + - 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/10.yml b/translations/es-ES/data/release-notes/2-22/10.yml new file mode 100644 index 0000000000..ac78f003c5 --- /dev/null +++ b/translations/es-ES/data/release-notes/2-22/10.yml @@ -0,0 +1,16 @@ +--- +date: '01-04-2021' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Los paquetes se actualizaron a las últimas versiones de seguridad. + bugs: + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. + - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. + - 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. + - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres. + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com. diff --git a/translations/es-ES/data/release-notes/3-0/0.yml b/translations/es-ES/data/release-notes/3-0/0.yml index 4ca7dae402..8f5cb46410 100644 --- a/translations/es-ES/data/release-notes/3-0/0.yml +++ b/translations/es-ES/data/release-notes/3-0/0.yml @@ -1,10 +1,12 @@ -date: '2021-02-16' +--- +date: '16-02-2021' intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".' sections: security_fixes: - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en {% data variables.product.prodname_ghe_server %} que podría aprovecharse al compilar un sitio de {% data variables.product.prodname_pages %}. La configuración controlada por el usuario de los analizadores subyacentes que utiliza {% data variables.product.prodname_pages %} no se restringió lo suficiente y permitió que se ejecutaran comandos en la instancia de {% data variables.product.prodname_ghe_server %}. Para aprovechar esta vulnerabilidad, un atacante necesitaría permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. A esta vulnerabilidad se le asignó un CVE-2020-10519 y se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' features: - - heading: GitHub Actions + - + heading: GitHub Actions notes: - | [{% data variables.product.prodname_actions %}](https://github.com/features/actions) ahora se encuentra comunmente disponible en {% data variables.product.prodname_ghe_server %} 3.0+. Crea, prueba y despliega tu código desde {% data variables.product.prodname_dotcom %}. Emite revisiones de código, administración de ramas y el trabajo de clasificación de propuestas como quieras. @@ -25,7 +27,8 @@ sections: - Las [Plantillas de flujo de trabajo para las organizaciones](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) simplifican y promueven las mejores prácticas y la consistencia a lo largo de tu organización. Las {% data variables.product.prodname_actions %} no son actualmente compatibles para las empresas que utilizan configuraciones de agrupamiento. - - heading: Registro del paquete de GitHub + - + heading: Registro del paquete de GitHub notes: - | El [{% data variables.product.prodname_registry %}](https://github.com/features/packages) es un servicio de hospedaje de paquetes que se integra nativamente con las API, acciones y webhooks de GitHub. Crea un [flujo de trabajo de DevOps de extremo a extremo](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) que incluye soluciones para tu código, la integración contínua y el despliegue. @@ -35,45 +38,53 @@ sections: Cuando publicas paquetes en NuGet, los usuarios ahora pueden utilizar la opción `--api-key` para pasar su token de autenticación en vez de escribirlo en un archivo. Para obtener más información, consulta la sección [Configurar el CLI de dotnet para utilizarlo con GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) Actualmente, el {% data variables.product.prodname_registry %} no es compatible para las empresas que utilizan configuraciones de agrupamiento. - - heading: GitHub Mobile beta + - + heading: GitHub Mobile beta notes: - | El beta de [{% data variables.product.prodname_mobile %}](https://github.com/features/) te permite clasificar las notificaciones y administrar las propuestas y solicitudes de cambio desde tu dispositivo. Puedes firmarte simultáneamente en la aplicación móvil con una cuenta de usuario de {% data variables.product.prodname_dotcom_the_website %} y con una de {% data variables.product.prodname_ghe_server %}. El beta de {% data variables.product.prodname_mobile %} ahora se encuentra disponible para {% data variables.product.prodname_ghe_server %}. Ingresa con nuestras apps de [Android](https://play.google.com/store/apps/details?id=com.github.android) y de [iOS](https://apps.apple.com/app/github/id1477376905) para clasificar las notificaciones y adminsitrar las propuestas y solicitudes de cambio al vuelo. Los administradores pueden inhabilitar la compatibilidad con la versión móvil para su empresa si utilizan la consola de administración o si ejecutan `ghe-config app.mobile.enabled false`. - - heading: Escaneo de Secretos de Advanced Security beta + - + heading: Escaneo de Secretos de Advanced Security beta notes: - | El [Escaneo de Secretos beta](https://github.com/features/security) escanea los repositorios públicos y privados para las credenciales confirmadas, encuentra secretos, y notifica al proveedor de secretos o al administrador en el momento en el que éstos se confirman en un repositorio. Los administradores que utilizan la {% data variables.product.prodname_GH_advanced_security %} pueden [habilitar y configurar](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) el escaneo de secretos de {% data variables.product.prodname_GH_advanced_security %}. Puedes revisar los [requisitos mínimos actualizados para tu plataforma](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) antes de habilitar el escaneo de secretos de {% data variables.product.prodname_GH_advanced_security %}. - - heading: Escaneo de Código de Advanced Security + - + heading: Escaneo de Código de Advanced Security notes: - | [El escaneo de código de GitHub Advanced Security](https://github.com/features/security) ahora está comunmente disponible en GitHub Enterprise Server. Las organizaciones que hayan comprado Advanced Security pueden utilizar esta característica para realizar pruebas de seguridad de análisis estático contra su código y pueden prevenir que las vulnerabilidades lleguen a su código productivo utilizando CodeQL, nuestro motor de análisis semántico. Para obtener más información, consulta la sección "[Configurar el escaneo de código en tu aplicativo](/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 + - + heading: Cambios en la administración notes: - - 'El sistema de entrega de eventos de webhook se ha renovado en su arquitectura para tener un rendimiento mayor y menos retraso en los mensajes. También utiliza menos memoria y CPU en {% data variables.product.prodname_ghe_server %} 3.0+.' - - 'Los propietarios de empresas y organizaciones ahora pueden ver a qué miembros del equipo se ha promovido o degradado hacia o desde su puesto como mantenedor de equipo en la bitácora de auditoría a través de los nuevos eventos de bitácora de auditoría `team.promote_maintainer` y `team.demote_maintainer`. Para obtener más información, consulta la sección "[Acciones auditadas](/enterprise-server@3.0/admin/user-management/audited-actions)".' + - El sistema de entrega de eventos de webhook se ha renovado en su arquitectura para tener un rendimiento mayor y menos retraso en los mensajes. También utiliza menos memoria y CPU en {% data variables.product.prodname_ghe_server %} 3.0+. + - Los propietarios de empresas y organizaciones ahora pueden ver a qué miembros del equipo se ha promovido o degradado hacia o desde su puesto como mantenedor de equipo en la bitácora de auditoría a través de los nuevos eventos de bitácora de auditoría `team.promote_maintainer` y `team.demote_maintainer`. Para obtener más información, consulta la sección "[Acciones auditadas](/enterprise-server@3.0/admin/user-management/audited-actions)". - 'Los mantenedores de repositorio con sitios de {% data variables.product.prodname_pages %} existentes pueden [actualizar fácilmente el nombre de rama predeterminado anterior](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' - - 'Se requiere de recursos adicionales de hardware para ejecutar {% data variables.product.prodname_ghe_server %} que tenga habilitadas acciones, paquetes o seguridad avanzada. Para obtener más información sobre los recursos mínimos requeridos para cada plataforma de soporte, consulta la sección "[Configurar una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)".' - - 'Los administradores ahora pueden [publicar un mensaje](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), que todos los usuarios deben aceptar. Esto te puede ayudar a incorporar usuarios nuevos y hacer notar otras políticas e información específica de la organización.' - - heading: Cambios de seguridad + - Se requiere de recursos adicionales de hardware para ejecutar {% data variables.product.prodname_ghe_server %} que tenga habilitadas acciones, paquetes o seguridad avanzada. Para obtener más información sobre los recursos mínimos requeridos para cada plataforma de soporte, consulta la sección "[Configurar una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)". + - Los administradores ahora pueden [publicar un mensaje](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), que todos los usuarios deben aceptar. Esto te puede ayudar a incorporar usuarios nuevos y hacer notar otras políticas e información específica de la organización. + - + heading: Cambios de seguridad notes: - - 'Los propietarios de las organizaciones ahora pueden inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} de los repositorios de la organización. El inhabilitar a {% data variables.product.prodname_pages %} para la organización impedirá que los miembros creen páginas nuevas pero no dejará de publicar los sitios existentes. Para obtener más información, consulta la sección "[Inhabilitar la publicación de los sitios de {% data variables.product.prodname_pages %} para tu organización](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)".' + - Los propietarios de las organizaciones ahora pueden inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} de los repositorios de la organización. El inhabilitar a {% data variables.product.prodname_pages %} para la organización impedirá que los miembros creen páginas nuevas pero no dejará de publicar los sitios existentes. Para obtener más información, consulta la sección "[Inhabilitar la publicación de los sitios de {% data variables.product.prodname_pages %} para tu organización](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)". - Se debe definir explícitamente un centro de datos en todos los nodos antes de habilitar una réplica activa. - - 'Todo uso de huellas dactilares de SSH se ha cambiado para utilizar huellas dactilares SHA256 como también se utilizan con OpenSSH desde la versión 6.8. Esto aplica a la interface web y también a la API en donde las huellas dactilares se devuelven, tal como en GraphQL. Las huellas dactilares siguen el formato de OpenSSH.' + - Todo uso de huellas dactilares de SSH se ha cambiado para utilizar huellas dactilares SHA256 como también se utilizan con OpenSSH desde la versión 6.8. Esto aplica a la interface web y también a la API en donde las huellas dactilares se devuelven, tal como en GraphQL. Las huellas dactilares siguen el formato de OpenSSH. - Los encabezados de firma SHA-1 y SHA-256 (dos encabezados) se envían en webhooks. - - heading: Cambios de desarrollador + - + heading: Cambios de desarrollador notes: - - 'La mayoría de los servicios que se ejecutan en {% data variables.product.prodname_ghe_server %} 3.0+ ahora se encuentran en contenedores que habilitan internamente a GitHub para iterar rapido y para enviar lanzamientos de alta calidad' - - 'El sistema de entrega de eventos de webhook renovó su arquitectura para tener un rendimiento mayor, entregas más rápidas y menos retrasos en los mensajes.' - - heading: Cambios a la API + - La mayoría de los servicios que se ejecutan en {% data variables.product.prodname_ghe_server %} 3.0+ ahora se encuentran en contenedores que habilitan internamente a GitHub para iterar rapido y para enviar lanzamientos de alta calidad + - El sistema de entrega de eventos de webhook renovó su arquitectura para tener un rendimiento mayor, entregas más rápidas y menos retrasos en los mensajes. + - + heading: Cambios a la API notes: - 'Los administradores ahora pueden configurar y administrar el letrero de anuncio de todo el sitio a través de la API de REST. Para obtener más información, consulta las terminales de "[administración de GitHub Enterprise](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)".' - 'Una nueva terminal de la API permite el intercambio de un token de usuario a servidor para aquellos que tengan alcance de los repositorios específicos. Para obtener más información, consulta las "[Apps](/enterprise-server@3.0/rest/reference/apps#create-a-scoped-access-token)" en la documentación de la API de REST de {% data variables.product.prodname_dotcom %}.' - - heading: Renombrar la rama predeterminada + - + heading: Renombrar la rama predeterminada notes: - | Los administradores de organizaciones y empresas ahora pueden configurar el nombre de la rama predeterminada para los repositorios nuevos. Los administradores de empresas también pueden hacer cumplir su elección de nombre de rama predeterminada a través de todas las organizaciones para permitir que cada una de ellas elija su propio nombre. @@ -88,10 +99,12 @@ sections: Este cambio es uno de los muchos que GitHub está realizando para apoyar a los proyectos y mantenedores que quieren renombrar su rama predeterminada. Para aprender más sobre los cambios que estamos haciendo, consulta la sección [github/renaming](https://github.com/github/renaming). bugs: - - heading: Correcciones para los problemas conocidos de los Candidatos a Lanzamiento + - + heading: Correcciones para los problemas conocidos de los Candidatos a Lanzamiento notes: - - 'Todos los problemas que se conocen del Candidato a Lanzamiento 1 y 2 se han corregido, con excepción de las que se listan en la siguiente sección de problemas conocidos.' - - heading: Correcciones para otros problemas + - Todos los problemas que se conocen del Candidato a Lanzamiento 1 y 2 se han corregido, con excepción de las que se listan en la siguiente sección de problemas conocidos. + - + heading: Correcciones para otros problemas notes: - Los problemas con las migraciones y mejoras a la versión 3.0.0 se arreglaron. - El versionamiento de utilidades de respaldo ahora funciona para las versiones de candidatos de lanzamiento. @@ -100,44 +113,50 @@ sections: - La casilla de verificación para habilitar las GitHub Actions en la consola de administración ahora se puede ver con cualquier método de autenticación. - Las GitHub Actions podrían estar habilitadas si también se configuró el almacenamiento necesario. - '`ghe-repl-status` podría fallar silenciosamente si no se configuró la replicación de MSSQL.' - - 'El formato de varios archivos de bitácora ha cambiado, incluyendo la adición de un PID para los tipos de bitácora diferentes. Esto no afecta cómo GitHub Enterprise Support utiliza paquetes de soporte para la solución de problemas.' + - El formato de varios archivos de bitácora ha cambiado, incluyendo la adición de un PID para los tipos de bitácora diferentes. Esto no afecta cómo GitHub Enterprise Support utiliza paquetes de soporte para la solución de problemas. - El hacer una solicitud de PATCH a la API de configuración de webhooks ya no borra el secreto del webhook. - Algunos tipos de ganchos de pre-recepción estaban fallando. - 'El servicio de Paquetes NuGet ahora normaliza las versiones semánticas al publicar. Los clientes de NuGet no pueden descargar una versión semántica inválida (por ejemplo: v1.0.0.0.0.0) y, por lo tanto, se espera que un servicio de NuGet normalice esas versiones (por ejemplo: v1.0.0.0.0.0 --> v1.0.0). Cualquier versión original sin normalizar estará disponible en el campo `verbatimVersion`. No se requiere de ningún cambio a las configuraciones del cliente.' known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo. - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) se agregaron incorrecta y directamente al repositorio.' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - 'Cuando se habilita el modo de mantenimiento, algunos servicios siguen listándose como "procesos activos". Se espera que los servicios que se identificaron se ejecuten durante el modo de mantenimiento. Si estás experimentando este problema y no sabes cómo proceder, contacta a {% data variables.contact.contact_ent_support %}.' - - 'Cuando habilitas las GitHub Actions, utiliza ''`ghe-maintenance -u`'' para dejar de configurar el modo de mantenimiento.' + - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) se agregaron incorrecta y directamente al repositorio. + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com. + - Cuando se habilita el modo de mantenimiento, algunos servicios siguen listándose como "procesos activos". Se espera que los servicios que se identificaron se ejecuten durante el modo de mantenimiento. Si estás experimentando este problema y no sabes cómo proceder, contacta a {% data variables.contact.contact_ent_support %}. + - Cuando habilitas las GitHub Actions, utiliza '`ghe-maintenance -u`' para dejar de configurar el modo de mantenimiento. - 'El registro duplicado hacia `/var/log/messages`, `/var/log/syslog`, y `/var/log/user.log` da como resultado una utilización incrementada del volúmen raíz.' - Los usuarios pueden descartar un mensaje obligatorio sin verificar todas las casillas. - '[Los scripts de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks) no pueden escribir archivos temporales, los cuales pueden causar que falle la ejecución del script. Los usuarios que utilizan ganchos de pre-recepción deberían hacer pruebas en un ambiente de pruebas para ver si dichos scripts requieren de acceso de escritura.' - - 'Las [llaves de despliegue] de repositorio(/developers/overview/managing-deploy-keys) no pueden utilizarse con repositorios que contengan objetos LFS.' + - Las [llaves de despliegue] de repositorio(/developers/overview/managing-deploy-keys) no pueden utilizarse con repositorios que contengan objetos LFS. - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar. - - 'La gráfica de dependencias falla en interpretar los archivos de manifiesto de Python `setup.py`, lo cual resultó en errores HTTP 500 en las bitácoras. Esto, en combinación con el problema de bitácoras duplicadas, dio como resultado un incremento en la utilización del volúmen raíz.' + - La gráfica de dependencias falla en interpretar los archivos de manifiesto de Python `setup.py`, lo cual resultó en errores HTTP 500 en las bitácoras. Esto, en combinación con el problema de bitácoras duplicadas, dio como resultado un incremento en la utilización del volúmen raíz. - Una condición de carrera puede causar que las migraciones de la base de datos de la dependencia parezcan fallar. - Las instancias con la zona horaria personalizada que se mejoraron desde un lanzamiento anterior de GitHub Enterprise Server podrían tener marcas de tiempo incorrectas en la IU web. - - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).' + - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). deprecations: - - heading: Obsoletización de GitHub Enterprise Server 2.19 + - + heading: Obsoletización de GitHub Enterprise Server 2.19 notes: - '**{% data variables.product.prodname_ghe_server %} 2.19 se encontrará obsoletizado desde el 12 de noviembre de 2020**. Eso significa que no se harán lanzamientos de parches, ni siquiera para los problemas críticos de seguridad, después de esta fecha. Para obtener un rendimiento mejor, mejorar la seguridad y tener nuevas características, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_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 + - + heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps notes: - - 'Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, dos eventos de webhook relacionados con GitHub Apps se obsoletizaron y eliminaron en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Los eventos obsoletizados de `integration_installation` and `integration_installation_repositories` tienen eventos equivalentes que serán compatibles. Puedes encontrar más información en la [publicación del blog acerca de los anuncios de obsoletización](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 + - Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, dos eventos de webhook relacionados con GitHub Apps se obsoletizaron y eliminaron en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Los eventos obsoletizados de `integration_installation` and `integration_installation_repositories` tienen eventos equivalentes que serán compatibles. Puedes encontrar más información en la [publicación del blog acerca de los anuncios de obsoletización](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: - - 'Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, la terminal tradicional de GitHub Apps para crear tokens de acceso a las instalaciones se obsoletizó y se eliminará en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Puedes encontrar 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-create-installation-access-token-endpoint/).' - - heading: Obsoletización de la API de aplicaciones OAuth + - Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, la terminal tradicional de GitHub Apps para crear tokens de acceso a las instalaciones se obsoletizó y se eliminará en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Puedes encontrar 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-create-installation-access-token-endpoint/). + - + heading: Obsoletización de la API de aplicaciones OAuth notes: - - 'GitHub ya no es compatible con las terminales de la aplicación de OAuth que contengan `access_token` como parámetro de ruta. Hemos incluído terminales nuevas que te permiten administrar los tokens para las apps de OAuth de forma segura al mover a `access_token` al cuerpo de solicitud. Aunque se hayan obsoletizado, aún se puede acceder a las terminales en esta versión. Intentamos eliminar estas terminales en la versión 3.4 de {% data variables.product.prodname_ghe_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/).' - - heading: Obsoletización de compatibilidad con Semiotic + - GitHub ya no es compatible con las terminales de la aplicación de OAuth que contengan `access_token` como parámetro de ruta. Hemos incluído terminales nuevas que te permiten administrar los tokens para las apps de OAuth de forma segura al mover a `access_token` al cuerpo de solicitud. Aunque se hayan obsoletizado, aún se puede acceder a las terminales en esta versión. Intentamos eliminar estas terminales en la versión 3.4 de {% data variables.product.prodname_ghe_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/). + - + heading: Obsoletización de compatibilidad con Semiotic notes: - El servicio era compatible con una experiencia de "Encontrar por símbolo" en la vista de solicitud de cambios que no se utilizaba ampliamente. - - heading: Obsoletización de los comandos de flujo de trabajo + - + heading: Obsoletización de los comandos de flujo de trabajo notes: - 'Los comandos de flujo de trabajo de `set-env` y `add-path` de {% data variables.product.prodname_actions %} se obsoletizaron. Para obtener más información, consulta el [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' backups: diff --git a/translations/es-ES/data/release-notes/3-0/4.yml b/translations/es-ES/data/release-notes/3-0/4.yml new file mode 100644 index 0000000000..9ef9321a1e --- /dev/null +++ b/translations/es-ES/data/release-notes/3-0/4.yml @@ -0,0 +1,25 @@ +--- +date: '01-04-2021' +intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Los paquetes se actualizaron a las últimas versiones de seguridad. + bugs: + - When maintenance mode was enabled, some services continued to be listed as "active processes" even though they were expected to be running, and should not have been listed. + - After upgrading from 2.22.x to 3.0.x with GitHub Actions enabled, the self-hosted runner version was not updated and no self-hosted updates were made. + - Old GitHub Pages builds were not cleaned up leading to increased disk usage. + - '`memcached` was not running on active replicas.' + - Upgrade failed when updating file permissions when GitHub Actions was enabled. + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The `ghe-saml-mapping-csv` command-line utility produced a warning message. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. + - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. + - 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. + - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres. + - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com. + - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar. diff --git a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md index 72802db369..c8788cd168 100644 --- a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md @@ -4,5 +4,7 @@ | `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. 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)". | | `created_workflow_run` | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Crear un flujo de trabajo de ejemplo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)". | | `delete_workflow_run` | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)". | +| `disable_workflow` | Triggered when a workflow is disabled. | +| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`. | | `rerun_workflow_run` | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow)". | | `prepared_workflow_job` | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". | diff --git a/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md index d59fab94a0..d3f00a2048 100644 --- a/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md +++ b/translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md @@ -2,4 +2,4 @@ Puedes requerir una política que controle si se les permite a los administradores de repositorio habilitar características para {% data variables.product.prodname_advanced_security %} en los repositorios de una organización. Puedes configurar una política para todas las organizaciones que le pertenezcan a tu cuenta empresarial o para las organizaciones individuales que elijas. -El dejar de permitir la {% data variables.product.prodname_advanced_security %} para una organización previene que los administradores de repositorio habiliten las características de la {% data variables.product.prodname_advanced_security %} para los repositorios adicionales, pero no inhabilita las características para los repositorios en donde estas ya se hayan habilitado. Para obtener más información acerca de la configuración de las características de {% data variables.product.prodname_advanced_security %}, 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)" o "[Administrar la configuración de análisis y seguridad para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +El dejar de permitir la {% data variables.product.prodname_advanced_security %} para una organización previene que los administradores de repositorio habiliten las características de la {% data variables.product.prodname_advanced_security %} para los repositorios adicionales, pero no inhabilita las características para los repositorios en donde estas ya se hayan habilitado. Para obtener más información acerca de la configuración de las características de {% data variables.product.prodname_advanced_security %}, consulta la sección "[Administrar la configuración de análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" o "[Administrar la configuración de análisis y seguridad para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". diff --git a/translations/es-ES/data/reusables/branches/set-default-branch.md b/translations/es-ES/data/reusables/branches/set-default-branch.md index 44c00b5fc9..58297a9caf 100644 --- a/translations/es-ES/data/reusables/branches/set-default-branch.md +++ b/translations/es-ES/data/reusables/branches/set-default-branch.md @@ -1 +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 %} +Puedes configurar el nombre de la rama predeterminada para los repositorios nuevos. 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](/organizations/managing-organization-settings/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 %} 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 index cb79652e03..20b4b99d97 100644 --- a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ 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)". +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](/organizations/managing-access-to-your-organizations-repositories/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**. 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 index c3dc7d8330..2fe7e27638 100644 --- a/translations/es-ES/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/es-ES/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +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. 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](/organizations/collaborating-with-groups-in-organizations/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/code-scanning/click-alert-in-list.md b/translations/es-ES/data/reusables/code-scanning/click-alert-in-list.md index 360a6f80cd..103d7545ed 100644 --- 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 @@ -1 +1,6 @@ -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) +1. Debajo de "Code scanning", da clic en la alerta que quieras explorar. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/dependabot/private-dependencies-note.md b/translations/es-ES/data/reusables/dependabot/private-dependencies-note.md index 2a6da4c213..03135127fa 100644 --- a/translations/es-ES/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/es-ES/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -Cuando ejecutas actualizaciones de versión o de seguridad, algunos ecosistemas deberán poder resolver todas las dependencias de su fuente para verificar que las actualizaciones sean exitosas. Si tus archivos de manifiesto o de bloqueo contienen cualquier dependencia privada, el {% data variables.product.prodname_dependabot %} deberá poder acceder a la ubicación en la que se hospedan dichas dependencias. Los propietarios de las organizaciones pueden otorgar acceso al {% data variables.product.prodname_dependabot %} para los repositorios privados que contengan dependencias para un proyecto dentro de la misma organización. 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-dependencies)". Puedes configurar el acceso a los registros privados en el archivo de configuración _dependabot.yml_ de un repositorio. 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#configuration-options-for-private-registries)". +Cuando ejecutas actualizaciones de versión o de seguridad, algunos ecosistemas deberán poder resolver todas las dependencias de su fuente para verificar que las actualizaciones sean exitosas. Si tus archivos de manifiesto o de bloqueo contienen cualquier dependencia privada, el {% data variables.product.prodname_dependabot %} deberá poder acceder a la ubicación en la que se hospedan dichas dependencias. Los propietarios de las organizaciones pueden otorgar acceso al {% data variables.product.prodname_dependabot %} para los repositorios privados que contengan dependencias para un proyecto dentro de la misma organización. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". Puedes configurar el acceso a los registros privados en el archivo de configuración _dependabot.yml_ de un repositorio. 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#configuration-options-for-private-registries)". diff --git a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md index fca605b688..1d04b6d65f 100644 --- a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md +++ b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md @@ -6,7 +6,7 @@ La siguiente tabla muestra, para cada administrador de paquetes: | Administración de paquetes | El valor de YAML | Las versiones compatibles | Los repositorios privados | Registros privados | Delegamiento a proveedores | | -------------------------- | ---------------- | ------------------------------- |:-------------------------:|:------------------:|:--------------------------:| -| Bundler | `bundler` | v1 | | **✓** | **✓** | +| Bundler | `bundler` | v1, v2 | | **✓** | **✓** | | Cargo | `cargo` | v1 | **✓** | **✓** | | | Composer | `composer` | v1, v2 | **✓** | **✓** | | | Docker | `docker` | v1 | **✓** | **✓** | | diff --git a/translations/es-ES/data/reusables/dotcom_billing/coupon-expires.md b/translations/es-ES/data/reusables/dotcom_billing/coupon-expires.md new file mode 100644 index 0000000000..71beb790aa --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/coupon-expires.md @@ -0,0 +1 @@ +If you use a coupon to pay for a subscription, when the coupon expires, your payment method will be charged the full cost of your subscription. If you do not have a saved payment method, your account will be downgraded to {% data variables.product.prodname_free_user %} for user accounts or {% data variables.product.prodname_free_team %} for organizations. 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 index 872fa5dd7a..699c1e5da9 100644 --- a/translations/es-ES/data/reusables/education/about-github-education-link.md +++ b/translations/es-ES/data/reusables/education/about-github-education-link.md @@ -1 +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/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)". +Antes de solicitar un descuento individual, comprueba si tu comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_campus_program %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)". diff --git a/translations/es-ES/data/reusables/gated-features/actions-shared.md b/translations/es-ES/data/reusables/gated-features/actions-shared.md index 57b1ab7a7d..b92f17688d 100644 --- a/translations/es-ES/data/reusables/gated-features/actions-shared.md +++ b/translations/es-ES/data/reusables/gated-features/actions-shared.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %}, and {% data variables.product.prodname_ghe_one %}. {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. +El {% data variables.product.prodname_actions %} 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 %}, {% data variables.product.prodname_ghe_one %}, and {% data variables.product.prodname_ghe_managed %}. {% 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/github-actions/actions-github-connect-requirement.md b/translations/es-ES/data/reusables/github-actions/actions-github-connect-requirement.md new file mode 100644 index 0000000000..8b36658e05 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/actions-github-connect-requirement.md @@ -0,0 +1 @@ +To allow {% data variables.product.prodname_ghe_server %} to use actions directly from {% data variables.product.prodname_dotcom_the_website %}, you can use {% data variables.product.prodname_github_connect %}. You will need to enable the setting for "Server can use actions from {% data variables.product.prodname_dotcom_the_website %} in workflows runs," as described in "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 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 index a148c339ce..e17c17aadf 100644 --- a/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/es-ES/data/reusables/github-actions/java-jvm-architecture.md @@ -2,16 +2,17 @@ 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`. +For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'adopt'` and `x64`. {% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 + - name: Set up JDK 11 for x64 + uses: actions/setup-java@v2 with: - java-version: '9.0.4' + java-version: '11' + distribution: 'adopt' architecture: x64 ``` {% endraw %} 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 index 3b2872e027..5c15906c48 100644 --- 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 @@ -1,5 +1,5 @@ {% warning %} -**Advertencia:** Si tu organización utiliza la sincronización de equipos, el revocar la identidad de SSO de una persona eliminará a dicha persona de los equipos que se mapearon en los grupos de IdP. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". +**Advertencia:** Si tu organización utiliza la sincronización de equipos, el revocar la identidad de SSO de una persona eliminará a dicha persona de los equipos que se mapearon en los grupos de IdP. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". {% endwarning %} 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 index 0b9fef580c..94ef9de0e5 100644 --- 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 @@ -1 +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)". +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](/organizations/organizing-members-into-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-confirm-saml.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-confirm-saml.md index e25f3ba376..a36eaa9f15 100644 --- 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 @@ -1 +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)". +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](/organizations/managing-saml-single-sign-on-for-your-organization/)". 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 index 2dc429da1e..f5606862aa 100644 --- 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 @@ -1,5 +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)". +- 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](/organizations/managing-saml-single-sign-on-for-your-organization/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/organizations/team-discussions-are-for-orgs.md b/translations/es-ES/data/reusables/organizations/team-discussions-are-for-orgs.md index 4ca4971174..5357717526 100644 --- 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 @@ -1 +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](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)". +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](/organizations/collaborating-with-your-team/about-team-discussions)". diff --git a/translations/es-ES/data/reusables/organizations/team-synchronization.md b/translations/es-ES/data/reusables/organizations/team-synchronization.md index 171982a98e..423828795f 100644 --- a/translations/es-ES/data/reusables/organizations/team-synchronization.md +++ b/translations/es-ES/data/reusables/organizations/team-synchronization.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} -Puedes utilizar la sincronización de equipos para eliminar y agregar automáticamente a los miembros de la organización a los equipos mediante un proveedor de identidad. 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)". +Puedes utilizar la sincronización de equipos para eliminar y agregar automáticamente a los miembros de la organización a los equipos mediante un proveedor de identidad. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". {% endif %} diff --git a/translations/es-ES/data/reusables/organizations/team_maintainers_can.md b/translations/es-ES/data/reusables/organizations/team_maintainers_can.md index b5c7888e43..0c3bee48d0 100644 --- a/translations/es-ES/data/reusables/organizations/team_maintainers_can.md +++ b/translations/es-ES/data/reusables/organizations/team_maintainers_can.md @@ -11,5 +11,5 @@ Los miembros con permisos de mantenedor del equipo pueden hacer lo siguiente: - [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" %} +- [Administra la tarea de revisión de código para el equipo](/organizations/organizing-members-into-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/package_registry/authenticate-packages.md b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md index 64b208d748..be39335c2f 100644 --- a/translations/es-ES/data/reusables/package_registry/authenticate-packages.md +++ b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md @@ -1,9 +1,14 @@ -You need an access token to publish, install, and delete packages. You can use a personal access token to authenticate with your username directly to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs. +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" %} -To authenticate using a {% data variables.product.prodname_actions %} workflow: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com`), you can use a `GITHUB_TOKEN`. -- For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you must use a personal access token. +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 del contenedor (`ghcr.io/OWNER/IMAGE-NAME`), puedes utilizar un `GITHUB_TOKEN` o un token de acceso personal. Es muy recomendable que utilices un `GITHUB_TOKEN` para evitar el acceso innecesario a tus repositorios. + +Para obtener más información acerca del `GITHUB_TOKEN` que se utiliza en los flujos de trabajo de {% data variables.product.prodname_actions %}, consulta las secciones de "[Secretos cifrados"](/actions/reference/encrypted-secrets)" y "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)". + {% else %} -To authenticate to {% data variables.product.prodname_registry %} using a {% data variables.product.prodname_actions %} workflow, you must use `GITHUB_TOKEN`. +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-to-container-registry-steps.md b/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md index 3411c5301c..bba75037ea 100644 --- 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 @@ -1,7 +1,7 @@ 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)". + **Note:** By default, when you select the `write:packages` scope for your personal access token (PAT) in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for GitHub Actions workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://github.com/settings/tokens/new?scopes=write:packages`. {% endwarning %} 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 index 789d340571..1f5ec021f1 100644 --- 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 @@ -1,5 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} +Los PAT pueden otorgar accesos amplios a tu cuenta. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}. + Para autenticarte en el {% data variables.product.prodname_github_container_registry %} dentro de un flujo de trabajo de {% data variables.product.prodname_actions %}, utiliza el `GITHUB_TOKEN` para tener la mejor experiencia y seguridad. Para obtener orientación sobre cómo actualizar tus flujos de trabajo que se autentican en `ghcr.io` con un token de acceso personal, consulta la sección "[Mejorar un flujo de trabajo que acceda a `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)". diff --git a/translations/es-ES/data/reusables/pages/choose-visibility.md b/translations/es-ES/data/reusables/pages/choose-visibility.md index 809229a819..b4d1a584e3 100644 --- a/translations/es-ES/data/reusables/pages/choose-visibility.md +++ b/translations/es-ES/data/reusables/pages/choose-visibility.md @@ -1 +1 @@ -1. Opcionalmente, si estás publicando un sitio de proyecto desde un repositorio interno o privado que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, elige la visibilidad de tu sitio. Debajo de "{% data variables.product.prodname_pages %}", selecciona el menú desplegable de **visibilidad de {% data variables.product.prodname_pages %}** y luego da clic en una visibilidad. Para obtener más información, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Menú desplegable para seleccionar la visibilidad de tu sitio](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file +1. Opcionalmente, si estás publicando un sitio de proyecto desde un repositorio interno o privado que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, elige la visibilidad de tu sitio. Debajo de "{% data variables.product.prodname_pages %}", selecciona el menú desplegable de **visibilidad de {% data variables.product.prodname_pages %}** y luego da clic en una visibilidad. Para obtener más información, consulta la sección "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Menú desplegable para seleccionar la visibilidad de tu sitio](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md index 5d8a8f5019..62fce3bd51 100644 --- a/translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md +++ b/translations/es-ES/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Nota:** Los propietarios de la organización pueden restringir la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios que le pertenezcan a dicha organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %}](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)". +**Nota:** Los propietarios de la organización pueden restringir la publicación de sitios de {% data variables.product.prodname_pages %} desde los repositorios que le pertenezcan a dicha organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %}](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". {% endnote %} {% endif %} \ No newline at end of file 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 index 848bce56e7..e030fa91f7 100644 --- 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 @@ -1,5 +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{% if currentVersion == "free-pro-team@latest" %} predeterminadamente{% endif %}, aún si el repositorio del sitio es privado o interno.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} De otra forma, si {% else %} Si{% endif %} tienes datos sensibles en el repositorio de tu sitio, puede que quieras eliminarlos antes de publicarlos. 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 de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" y "[Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)".{% else %}".{% endif %} +**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{% if currentVersion == "free-pro-team@latest" %} predeterminadamente{% endif %}, aún si el repositorio del sitio es privado o interno.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} De otra forma, si {% else %} Si{% endif %} tienes datos sensibles en el repositorio de tu sitio, puede que quieras eliminarlos antes de publicarlos. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} {% endwarning %} diff --git a/translations/es-ES/data/reusables/pages/sidebar-pages.md b/translations/es-ES/data/reusables/pages/sidebar-pages.md new file mode 100644 index 0000000000..fb1c3dcd79 --- /dev/null +++ b/translations/es-ES/data/reusables/pages/sidebar-pages.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +1. En la barra lateral izquierda, da clic en **Páginas**. ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png) +{% endif %} 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 index 33f05b7544..12753ba031 100644 --- a/translations/es-ES/data/reusables/pages/update_your_dns_settings.md +++ b/translations/es-ES/data/reusables/pages/update_your_dns_settings.md @@ -1 +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 %} +{% 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 %}](/pages/configuring-a-custom-domain-for-your-github-pages-site)".{% endif %} 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 index 23c373719c..4c0999ddc5 100644 --- 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 @@ -1 +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)". +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. For example, if you configure `www.example.com` as the custom domain for your site, and you have {% data variables.product.prodname_pages %} DNS records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. Note that automatic redirects only apply to the `www` subdomain. Automatic redirects do not apply to any other subdomains, such as `blog`. 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 index 04cde59f3b..85efad2b34 100644 --- 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 @@ -6,6 +6,6 @@ - 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)". +- 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. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} 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 index 133c7dd251..6297062631 100644 --- a/translations/es-ES/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ b/translations/es-ES/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -1 +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) +1. En la barra lateral izquierda, da clic en **alertas de escaneo de código**. ![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/saml/about-linked-identities.md b/translations/es-ES/data/reusables/saml/about-linked-identities.md index af16354569..9e249437cc 100644 --- a/translations/es-ES/data/reusables/saml/about-linked-identities.md +++ b/translations/es-ES/data/reusables/saml/about-linked-identities.md @@ -1,3 +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)". +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](/organizations/managing-saml-single-sign-on-for-your-organization/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/outside-collaborators-exemption.md b/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md index a464f145b6..f1b9dc96c5 100644 --- a/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/es-ES/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +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)". +**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](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)". {% endnote %} 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 index 00bf61a6fe..01fbab29b2 100644 --- 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 @@ -7,8 +7,9 @@ | Alibaba Cloud | Secreto de Clave de Acceso a la Nube de Alibaba | alibaba_cloud_access_key_secret | | Amazon Web Services (AWS) | ID de Clave de Acceso de AWS de Amazon | aws_access_key_id | | Amazon Web Services (AWS) | Clave de Acceso Secreta de AWS de Amazon | aws_secret_access_key | +| Asana | Asana Personal Access Token | asana_personal_access_token | | Atlassian | Token de API de Atlassian | atlassian_api_token | -| Atlassian | Token Web de JSON de Atlassian | atlassian_jwt | +| Atlassian | Token Web de JSOn de Atlazzian | atlassian_jwt | | Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token | | Azure | Token de Azure SAS | azure_sas_token | | Azure | Certificado de Administración de Servicios de Azure | azure_management_certificate | @@ -37,8 +38,12 @@ | GoCardless | Token de Acceso de GoCardless Sandbox | gocardless_sandbox_access_token | | Google Cloud | Clave de API de Google | google_api_key | | Google Cloud | ID de Clave Privada de Google Cloud | google_cloud_private_key_id | +| Grafana | Grafana API Key | grafana_api_key | | Hashicorp Terraform | Token de API de Terraform Cloud / Enterprise | terraform_api_token | | Hubspot | Clave de API de Hubspot | hubspot_api_key | +| Intercom | Intercom Access Token | intercom_access_token | +| Lob | Lob Live API Key | lob_live_api_key | +| Lob | Lob Test API Key | lob_test_api_key | | Mailchimp | Clave de API de Mailchimp | mailchimp_api_key | | Mailgun | Clave de API de Mailgun | mailgun_api_key | | npm | Token de Acceso de npm | npm_access_token | @@ -51,6 +56,7 @@ | Proctorio | Clave de Secreto de Proctorio | proctorio_secret_key | | Pulumi | Token de Acceso de Pulumi | pulumi_access_token | | PyPI | Token de la API de PyPI | pypi_api_token | +| RubyGems | RubyGems API Key | rubygems_api_key | | Samsara | Token de API de Samsara | samsara_api_token | | Samsara | Token de Acceso de OAuth de Samsara | samsara_oauth_access_token | | SendGrid | Clave de la API de SendGrid | sendgrid_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 index df312b1aa7..8f0841d137 100644 --- 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 @@ -50,6 +50,7 @@ | Proctorio | Clave de Secreto de Proctorio | | Pulumi | Token de Acceso de Pulumi | | PyPI | Token de la API de PyPI | +| RubyGems | RubyGems API Key | | Samsara | Token de API de Samsara | | Samsara | Token de Acceso de OAuth de Samsara | | Shopify | Secreto Compartid de la App de Shopify | diff --git a/translations/es-ES/data/reusables/sponsors/choose-updates.md b/translations/es-ES/data/reusables/sponsors/choose-updates.md index f6ee9116cf..18048b6321 100644 --- a/translations/es-ES/data/reusables/sponsors/choose-updates.md +++ b/translations/es-ES/data/reusables/sponsors/choose-updates.md @@ -1 +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) +4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![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 index a224aba3ac..3f13de06bc 100644 --- a/translations/es-ES/data/reusables/sponsors/click-add-tier.md +++ b/translations/es-ES/data/reusables/sponsors/click-add-tier.md @@ -1 +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) +1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![Botón de agregar nivel](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/enable-custom-amounts.md b/translations/es-ES/data/reusables/sponsors/enable-custom-amounts.md new file mode 100644 index 0000000000..1889367cb9 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/enable-custom-amounts.md @@ -0,0 +1,2 @@ +1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png) +1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png) diff --git a/translations/es-ES/data/reusables/sponsors/feedback.md b/translations/es-ES/data/reusables/sponsors/feedback.md new file mode 100644 index 0000000000..f3fccb232d --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/feedback.md @@ -0,0 +1 @@ +Puedes compartir tu retroalimentación sobre los {% data variables.product.prodname_sponsors %} con {% data variables.product.company_short %}. To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)." 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 index a7eaaf6393..aac5d4e334 100644 --- a/translations/es-ES/data/reusables/sponsors/manage-updates-for-orgs.md +++ b/translations/es-ES/data/reusables/sponsors/manage-updates-for-orgs.md @@ -1 +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)". +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](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)". diff --git a/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md b/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md index d0d6f06baf..1d03b474df 100644 --- a/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md +++ b/translations/es-ES/data/reusables/sponsors/pay-prorated-amount.md @@ -1 +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 +1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![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/prorated-sponsorship.md b/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md index 6e8d08c906..a21ee5edfc 100644 --- a/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/es-ES/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +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. +If you're starting a monthly sponsorship on behalf of your user account, you'll immediately be charged a prorated amount for the time until your next regular billing date. 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/review-and-publish-tier.md b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md index 837f5bfa7f..a84fd2930a 100644 --- a/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/es-ES/data/reusables/sponsors/review-and-publish-tier.md @@ -1 +1 @@ -1. Revisa tu nivel y da clic en **Publicar nivel**. ![Botón de publicar nivel](/assets/images/help/sponsors/publish-tier-button.png) +1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/es-ES/data/reusables/sponsors/review-tiers-to-select.md b/translations/es-ES/data/reusables/sponsors/review-tiers-to-select.md new file mode 100644 index 0000000000..12da8b2767 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/review-tiers-to-select.md @@ -0,0 +1 @@ +1. En el lado derecho de la página, debajo de "Selecciona un nivel", revisa los niveles de patrocinio disponibles. If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.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 index 9e6cbb42ae..ca2905c799 100644 --- a/translations/es-ES/data/reusables/sponsors/select-a-tier.md +++ b/translations/es-ES/data/reusables/sponsors/select-a-tier.md @@ -1 +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) +1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![Caja de selección de nivel](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/es-ES/data/reusables/sponsors/sponsorship-details.md b/translations/es-ES/data/reusables/sponsors/sponsorship-details.md index 0549a3f417..54ae4f2bd8 100644 --- a/translations/es-ES/data/reusables/sponsors/sponsorship-details.md +++ b/translations/es-ES/data/reusables/sponsors/sponsorship-details.md @@ -1 +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. +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. You can choose from multiple sponsorship tiers, with one-time or monthly payment amounts and benefits that are set by the sponsored account. 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/tier-details.md b/translations/es-ES/data/reusables/sponsors/tier-details.md index 81961f5c24..5ce3b0deee 100644 --- a/translations/es-ES/data/reusables/sponsors/tier-details.md +++ b/translations/es-ES/data/reusables/sponsors/tier-details.md @@ -1,3 +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. +Puedes crear hasta diez niveles de patrocinio que podrán escoger los patrocinadores. Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). -Una vez que hayas publicado un nivel, no podrás editar el precio de este. 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. +Una vez que hayas publicado un nivel, no podrás editar el precio de este. En vez de eso, deberás retirar el nivel y crear uno nuevo. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/es-ES/data/reusables/support/accessing-premium-content.md b/translations/es-ES/data/reusables/support/accessing-premium-content.md index dfb86f1060..9c982c612a 100644 --- a/translations/es-ES/data/reusables/support/accessing-premium-content.md +++ b/translations/es-ES/data/reusables/support/accessing-premium-content.md @@ -1,4 +1,4 @@ ### Acceder a contenido prémium -Puedes acceder al contenido premium iniciando sesión en el {% data variables.contact.contact_enterprise_portal %}. +Puedes acceder al contenido premium iniciando sesión en el {% data variables.contact.contact_landing_page_portal %}. diff --git a/translations/es-ES/data/reusables/support/contacting-premium-support.md b/translations/es-ES/data/reusables/support/contacting-premium-support.md index df17b4d8de..4b2660837d 100644 --- a/translations/es-ES/data/reusables/support/contacting-premium-support.md +++ b/translations/es-ES/data/reusables/support/contacting-premium-support.md @@ -1,4 +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 %}. +Los clientes de {% data variables.contact.premium_support %} pueden utilizar el {% data variables.contact.contact_landing_page_portal %} para reportar problemas por escrito, en inglés. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/billing_plans.md b/translations/es-ES/data/reusables/user_settings/billing_plans.md new file mode 100644 index 0000000000..8d26ab1479 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/billing_plans.md @@ -0,0 +1 @@ +1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png) diff --git a/translations/es-ES/data/variables/contact.yml b/translations/es-ES/data/variables/contact.yml index c93b9272c1..5097793f26 100644 --- a/translations/es-ES/data/variables/contact.yml +++ b/translations/es-ES/data/variables/contact.yml @@ -24,9 +24,12 @@ contact_enterprise_portal: '[Portal de Soporte de GitHub Enterprise](https://ent #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) +#GitHub Support portal (for dotcom - this sends users to a contact form) support_portal: 'Portal de soporte de GitHub' contact_support_portal: '[GitHub Support portal](https://support.github.com/contact)' +#GitHub Support portal (this sends users to the Support landing page) +landing_page_portal: 'Portal de soporte de GitHub' +contact_landing_page_portal: '[GitHub Support portal](https://support.github.com/)' #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 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 6a916fe256..97c350752d 100644 --- a/translations/ja-JP/content/actions/creating-actions/about-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/about-actions.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概要' topics: - - Action 開発 - - 基本 + - 'Action 開発' + - '基本' --- {% data reusables.actions.enterprise-beta %} 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 0e6cc9b58e..d7e20145d0 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 @@ -1,14 +1,14 @@ --- title: 複合実行ステップ アクションの作成 -intro: このガイドでは、複合実行ステップ アクションを構築する方法について説明します。 +intro: 'このガイドでは、複合実行ステップ アクションを構築する方法について説明します。' product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - Action 開発 + - 'Action 開発' --- {% data reusables.actions.enterprise-beta %} 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 fbc043c5d4..ed49790ab0 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 @@ -1,6 +1,6 @@ --- title: Docker コンテナのアクションを作成する -intro: このガイドでは、Docker コンテナのアクションを作成するために最低限必要なステップを案内します。 +intro: 'このガイドでは、Docker コンテナのアクションを作成するために最低限必要なステップを案内します。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - Action 開発 - - Docker + - 'Action 開発' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} 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 fbd03a79fc..e9404f7124 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 @@ -1,6 +1,6 @@ --- title: JavaScript アクションを作成する -intro: このガイドでは、アクションツールキットを使って JavaScript アクションをビルドする方法について学びます。 +intro: 'このガイドでは、アクションツールキットを使って JavaScript アクションをビルドする方法について学びます。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-javascript-action @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - Action 開発 - - JavaScript + - 'Action 開発' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} 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 18d48dd40f..0cee845008 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 @@ -1,7 +1,7 @@ --- title: GitHub ActionsのためのDockerfileサポート shortTitle: Docker -intro: Dockerコンテナアクション用の`Dockerfile`を作成する際には、いくつかのDockerの命令がGitHub Actionsやアクションのメタデータファイルとどのように関わるのかを知っておく必要があります。 +intro: 'Dockerコンテナアクション用の`Dockerfile`を作成する際には、いくつかのDockerの命令がGitHub Actionsやアクションのメタデータファイルとどのように関わるのかを知っておく必要があります。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/building-actions/dockerfile-support-for-github-actions @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'リファレンス' --- {% data reusables.actions.enterprise-beta %} 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 68531d3484..905f721e6d 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 @@ -12,7 +12,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'リファレンス' --- {% data reusables.actions.enterprise-beta %} @@ -58,7 +58,7 @@ inputs: ワークフローファイル内で、あるいはデフォルトの入力値を使ってアクションに入力を指定すると、{% data variables.product.prodname_dotcom %}はその入力に対応して`INPUT_`という名前の環境変数を生成します。 生成される環境変数では、入力の名前を大文字にして、空白を`_`に変換します。 -たとえば、ワークフローがnumOctocats及びoctocatEyeColorという入力を定義すると、アクションのコードはこれらの入力の値を`INPUT_NUMOCTOCATS`及び`INPUT_OCTOCATEYECOLOR`という環境変数で読み取れます。 +For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables. #### `inputs.` @@ -76,6 +76,10 @@ inputs: **オプション** デフォルト値を示す`文字列`。 デフォルト値は、入力パラメーターがワークフローファイルで指定されたなかった場合に使われます。 +#### `inputs..deprecationMessage` + +**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives. + ### `outputs` **オプション** アクションが設定するデータを宣言できる出力パラメータ。 ワークフローで後に実行されるアクションは、先行して実行されたアクションが設定した出力データを利用できます。 たとえば、2つの入力を加算(x + y = z)するアクションがあれば、そのアクションは他のアクションが入力として利用できる合計値(z)を出力できます。 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 48326bbde7..7a0b3490e6 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 @@ -9,9 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概要' topics: - - パッケージ化 + - 'パッケージ化' --- {% data reusables.actions.enterprise-beta %} 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 1227049523..507e3e6526 100644 --- a/translations/ja-JP/content/actions/guides/about-service-containers.md +++ b/translations/ja-JP/content/actions/guides/about-service-containers.md @@ -1,6 +1,6 @@ --- title: サービスコンテナについて -intro: サービスコンテナを使って、データベース、Webサービス、メモリキャッシュ、あるいはその他のツールをワークフローに接続できます。 +intro: 'サービスコンテナを使って、データベース、Webサービス、メモリキャッシュ、あるいはその他のツールをワークフローに接続できます。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/automating-your-workflow-with-github-actions/about-service-containers @@ -9,10 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概要' topics: - - コンテナ - - Docker + - 'コンテナ' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md b/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md index 9a7dbf06e7..73916e5322 100644 --- a/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md +++ b/translations/ja-JP/content/actions/guides/adding-labels-to-issues.md @@ -1,15 +1,15 @@ --- title: Adding labels to issues -intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.' +intro: You can use {% data variables.product.prodname_actions %} to automatically label issues. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー - - Project management + - 'ワークフロー' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 fc67ed6d9c..b2b4ae586f 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CI - - Java - - Ant + - 'CI' + - 'Java' + - 'Ant' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Ant run: ant -noinput -buildfile build.xml ``` @@ -70,7 +71,7 @@ jobs: このワークフローは以下のステップを実行します。 1. `checkout`ステップは、ランナーにリポジトリのコピーをダウンロードします。 -2. `setup-java`ステップは、Java 1.8 JDKを設定します。 +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. "Build with Ant"ステップは、`build.xml`中のデフォルトターゲットを非インタラクティブモードで実行します。 デフォルトのワークフローテンプレートは、ビルドとテストのワークフローを構築する際の素晴らしい出発点であり、プロジェクトの要求に合わせてこのテンプレートをカスタマイズできます。 @@ -91,9 +92,10 @@ jobs: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Ant jar target run: ant -noinput -buildfile build-ci.xml jar ``` @@ -109,7 +111,11 @@ Antは通常、JAR、EAR、WARのような出力ファイルを`build/jar`ディ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ant -noinput -buildfile build.xml - uses: actions/upload-artifact@v2 with: 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 98186457cb..3ad502397d 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CI - - Java - - Gradle + - 'CI' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Gradle run: ./gradlew build ``` @@ -70,7 +71,7 @@ jobs: このワークフローは以下のステップを実行します。 1. `checkout`ステップは、ランナーにリポジトリのコピーをダウンロードします。 -2. `setup-java`ステップは、Java 1.8 JDKを設定します。 +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. "Build with Gradle"ステップは、ラッパースクリプトの`gradlew`を実行し、コードがビルドされ、テストをパスし、パッケージが作成できることを保証します。 デフォルトのワークフローテンプレートは、ビルドとテストのワークフローを構築する際の素晴らしい出発点であり、プロジェクトの要求に合わせてこのテンプレートをカスタマイズできます。 @@ -91,9 +92,10 @@ jobs: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Gradle package task run: ./gradlew -b ci.gradle package ``` @@ -107,10 +109,11 @@ steps: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Gradle packages uses: actions/cache@v2 with: @@ -123,7 +126,7 @@ steps: - name: Build with Gradle run: ./gradlew build - name: Cleanup Gradle Cache - # GitHub ActionsでキャッシュされないようにいくつかのファイルをGradleのキャッシュから削除 + # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions. # これらのファイルをGitHub Actionsのキャッシュからリストアすると、将来のビルドで問題が生じるかもしれない。 run: | rm -f ~/.gradle/caches/modules-2/modules-2.lock @@ -143,7 +146,11 @@ Gradleは通常、JAR、EAR、WARのような出力ファイルを`build/libs` ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ./gradlew build - uses: actions/upload-artifact@v2 with: 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 6f1e0f244a..78d1b486da 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CI - - Java - - Maven + - 'CI' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Maven run: mvn --batch-mode --update-snapshots verify ``` @@ -70,7 +71,7 @@ jobs: このワークフローは以下のステップを実行します。 1. `checkout`ステップは、ランナーにリポジトリのコピーをダウンロードします。 -2. `setup-java`ステップは、Java 1.8 JDKを設定します。 +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. "Build with Maven"ステップは、Mavenの`package`ターゲットを非インタラクティブモードで実行し、コードがビルドされ、テストをパスし、パッケージが作成できることを保証します。 デフォルトのワークフローテンプレートは、ビルドとテストのワークフローを構築する際の素晴らしい出発点であり、プロジェクトの要求に合わせてこのテンプレートをカスタマイズできます。 @@ -91,9 +92,10 @@ jobs: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Maven verify phase run: mvn --batch-mode --update-snapshots verify ``` @@ -107,10 +109,11 @@ steps: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Maven packages uses: actions/cache@v2 with: @@ -134,7 +137,10 @@ Mavenは通常、JAR、EAR、WARのような出力ファイルを`target`ディ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 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 index 71f244c914..c54b4a7f1f 100644 --- a/translations/ja-JP/content/actions/guides/building-and-testing-net.md +++ b/translations/ja-JP/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: ['3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -81,7 +81,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet: [ '2.2.103', '3.0', '3.1.x' ] + dotnet: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -89,7 +89,7 @@ jobs: uses: actions/setup-dotnet@v1.7.2 with: dotnet-version: ${{ matrix.dotnet-version }} - # 現在の dotnet バージョンを出力してマトリックスをテストする + # You can test your matrix by printing the current dotnet version - name: Display dotnet version run: dotnet --version ``` @@ -201,7 +201,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -218,7 +218,7 @@ jobs: with: name: dotnet-results-${{ matrix.dotnet-version }} path: TestResults-${{ matrix.dotnet-version }} - # always() を使用して常にこのステップを実行し、テストが失敗したときにテスト結果を公開する + # Use always() to always run this step to publish test results when there are test failures if: ${{ always() }} ``` {% 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 3c67ffe364..4695930b1d 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 @@ -9,11 +9,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CI - - ノード - - JavaScript + - 'CI' + - 'ノード' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} 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 e299769982..d971101056 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 @@ -8,10 +8,10 @@ versions: github-ae: '*' authors: - potatoqualitee -type: tutorial +type: 'チュートリアル' topics: - - CI - - Powershell + - 'CI' + - 'Powershell' --- {% data reusables.actions.enterprise-beta %} 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 f67344e88f..e8e7687caa 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 @@ -8,10 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CI - - Python + - 'CI' + - 'Python' --- {% data reusables.actions.enterprise-beta %} 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 c145d56ef5..ff6154466d 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 @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CI - - Ruby + - 'CI' + - 'Ruby' --- {% data reusables.actions.enterprise-beta %} 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 5df4e8ee71..24fba7dbce 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 @@ -1,7 +1,7 @@ --- title: 依存関係をキャッシュしてワークフローのスピードを上げる shortTitle: 依存関係のキャッシング -intro: ワークフローを高速化して効率を上げるために、依存関係や広く再利用されるファイルに対するキャッシュを作成して利用できます。 +intro: 'ワークフローを高速化して効率を上げるために、依存関係や広く再利用されるファイルに対するキャッシュを作成して利用できます。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows @@ -9,9 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー + - 'ワークフロー' --- {% data reusables.actions.ae-beta %} diff --git a/translations/ja-JP/content/actions/guides/closing-inactive-issues.md b/translations/ja-JP/content/actions/guides/closing-inactive-issues.md index 1391aeea79..e9a563dfd4 100644 --- a/translations/ja-JP/content/actions/guides/closing-inactive-issues.md +++ b/translations/ja-JP/content/actions/guides/closing-inactive-issues.md @@ -1,15 +1,15 @@ --- title: Closing inactive issues -intro: 'You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time.' +intro: You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー - - Project management + - 'ワークフロー' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md index 95ca52d538..623d6341ab 100644 --- a/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/ja-JP/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md @@ -1,15 +1,15 @@ --- title: Commenting on an issue when a label is added -intro: 'You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied.' +intro: You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー - - Project management + - 'ワークフロー' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 0360471112..879b5cc739 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - コンテナ - - Docker + - 'コンテナ' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} 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 c9c0c26adf..dc20133471 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - コンテナ - - Docker + - 'コンテナ' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} 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 16afce1eb8..eeac55ee5f 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 @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CD - - コンテナ - - Amazon ECS + - 'CD' + - 'コンテナ' + - 'Amazon ECS' --- {% data reusables.actions.enterprise-beta %} 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 abdbcaeb3c..0a896186a5 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 @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CD - - コンテナ - - Azure App Service + - 'CD' + - 'コンテナ' + - 'Azure App Service' --- {% data reusables.actions.enterprise-beta %} 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 446dc5c643..5b2906c5db 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 @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CD - - コンテナ - - Google Kubernetes Engine + - 'CD' + - 'コンテナ' + - 'Google Kubernetes Engine' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/ja-JP/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 54fa561dab..221353f493 100644 --- a/translations/ja-JP/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/ja-JP/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CI - - Xcode + - 'CI' + - 'Xcode' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/moving-assigned-issues-on-project-boards.md b/translations/ja-JP/content/actions/guides/moving-assigned-issues-on-project-boards.md index cea32ca026..8f775f5227 100644 --- a/translations/ja-JP/content/actions/guides/moving-assigned-issues-on-project-boards.md +++ b/translations/ja-JP/content/actions/guides/moving-assigned-issues-on-project-boards.md @@ -1,15 +1,15 @@ --- title: Moving assigned issues on project boards -intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.' +intro: You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー - - Project management + - 'ワークフロー' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 680978444d..d0b7784934 100644 --- a/translations/ja-JP/content/actions/guides/publishing-docker-images.md +++ b/translations/ja-JP/content/actions/guides/publishing-docker-images.md @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - パッケージ化 - - 公開 - - Docker + - 'パッケージ化' + - '公開' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} 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 ebec61cefe..6e7495ca4e 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - パッケージ化 - - 公開 - - Java - - Gradle + - 'パッケージ化' + - '公開' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -143,9 +144,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -209,9 +211,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to the Maven Central Repository run: gradle publish env: 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 667b311112..4a64e00f4c 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - パッケージ化 - - 公開 - - Java - - Maven + - 'パッケージ化' + - '公開' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -147,9 +148,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: mvn --batch-mode deploy env: @@ -183,9 +185,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java for publishing to Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -195,9 +198,10 @@ jobs: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to GitHub Packages run: mvn --batch-mode deploy env: 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 181f71a548..a6e2e4cab8 100644 --- a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md @@ -9,12 +9,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - パッケージ化 - - 公開 - - ノード - - JavaScript + - 'パッケージ化' + - '公開' + - 'ノード' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index 1031c08804..584248c480 100644 --- a/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/ja-JP/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -1,15 +1,15 @@ --- title: Removing a label when a card is added to a project board column -intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board.' +intro: You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー - - Project management + - 'ワークフロー' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md b/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md index a8a8da9905..44fd1c6eb4 100644 --- a/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md +++ b/translations/ja-JP/content/actions/guides/scheduling-issue-creation.md @@ -1,15 +1,15 @@ --- title: Scheduling issue creation -intro: 'You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews.' +intro: You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー - - Project management + - 'ワークフロー' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 07c0c7fd53..30f9587ccb 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 @@ -12,10 +12,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー - - CI + - 'ワークフロー' + - 'CI' --- {% data reusables.actions.enterprise-beta %} 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 7c9fb1e195..7c34e28e65 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 @@ -12,9 +12,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - ワークフロー + - 'ワークフロー' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/guides/using-github-actions-for-project-management.md b/translations/ja-JP/content/actions/guides/using-github-actions-for-project-management.md index d1b1191979..2e60e4a73e 100644 --- a/translations/ja-JP/content/actions/guides/using-github-actions-for-project-management.md +++ b/translations/ja-JP/content/actions/guides/using-github-actions-for-project-management.md @@ -1,14 +1,14 @@ --- title: Using GitHub Actions for project management -intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.' +intro: You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概要' topics: - - Project management + - 'Project management' --- You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board. 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 ace965de1f..6edd1dd588 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概要' --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -125,7 +125,7 @@ The self-hosted runner polls {% data variables.product.prodname_dotcom %} to ret たとえば、インスタンス名が `octoghae` の場合、セルフホストランナーが `octoghae.github.com` にアクセスできるようにする必要があります。 IP アドレス許可リストを -{% data variables.product.prodname_dotcom %} Organization または Enterprise アカウントで使用する場合は、セルフホストランナーの IP アドレスを許可リストに追加する必要があります。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)」を参照してください。 +{% data variables.product.prodname_dotcom %} Organization または Enterprise アカウントで使用する場合は、セルフホストランナーの IP アドレスを許可リストに追加する必要があります。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)」を参照してください。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -145,7 +145,7 @@ pkg-containers.githubusercontent.com pkg-containers-az.githubusercontent.com ``` -{% data variables.product.prodname_dotcom %} OrganizationあるいはEnterpriseアカウントでIPアドレス許可リストを使うなら、セルフホストランナーのIPアドレスを許可リストに追加しなければなりません。 詳しい情報については「[Organizationの許可IPアドレスの管理](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)」あるいは「[Enterpriseアカウントでのセキュリティ設定の適用](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)」を参照してください。 +{% data variables.product.prodname_dotcom %} OrganizationあるいはEnterpriseアカウントでIPアドレス許可リストを使うなら、セルフホストランナーのIPアドレスを許可リストに追加しなければなりません。 詳しい情報については「[Organizationの許可IPアドレスの管理](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)」あるいは「[Enterpriseアカウントでのセキュリティ設定の適用](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)」を参照してください。 {% else %} 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 ac2fd4d642..a04e3e8869 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 @@ -1,6 +1,6 @@ --- title: セルフホストランナーの追加 -intro: リポジトリ、Organization、Enterpriseにセルフホストランナーを追加できます。 +intro: 'リポジトリ、Organization、Enterpriseにセルフホストランナーを追加できます。' redirect_from: - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners - /actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 d59c69742f..4fbadab150 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' defaultPlatform: linux --- 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 63e17f8877..b7021ab74d 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 0cf61e9b67..5b31baa4ea 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,12 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' + github-ae: '*' +type: 'チュートリアル' defaultPlatform: linux --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### {{ 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 c1b9982dd3..fe5564f855 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 dacb0d3a0e..243d9a850e 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 05297ebf07..174601654b 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 @@ -5,7 +5,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 116eaa7461..ee7f47ab9c 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 @@ -1,17 +1,20 @@ --- title: ワークフローでのセルフホストランナーの利用 -intro: ワークフローでセルフホストランナーを使うには、ラベルを使ってジョブのためのランナーの種類を指定できます。 +intro: 'ワークフローでセルフホストランナーを使うには、ラベルを使ってジョブのためのランナーの種類を指定できます。' 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 + github-ae: '*' +type: 'チュートリアル' --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} カスタム及びデフォルトラベルの作成に関する情報については「[セルフホストランナーでのラベルの利用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)」を参照してください。 @@ -29,7 +32,7 @@ type: tutorial * `self-hosted`: セルフホストランナーに適用されるデフォルトのラベル。 * `linux`、`windows`、`macOS`: オペレーティングシステムに基づいて適用されます。 -* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. +* `x64`、`ARM`、または `ARM64`: ハードウェアアーキテクチャに基づいて適用されます。 ワークフローのYAMLを使って、これらのラベルの組み合わせに対してジョブを送信できます。 この例では、3つのラベルすべてにマッチするセルフホストランナーが、ジョブを実行する資格を持つことになります。 @@ -66,7 +69,7 @@ runs-on: [self-hosted, linux, x64, gpu] ジョブをセルフホストランナーにルーティングする際に、{% data variables.product.prodname_dotcom %}はジョブの`runs-on`ラベルにマッチするランナーを探します。 -1. {% data variables.product.prodname_dotcom %}ま、まずリポジトリレベルで、続いてOrganizationのレベルで{% if currentVersion ver_gt "enterprise-server@2.21" %}、そしてEnterpriseのレベルで{% endif %}ランナーを探します。 +1. {% data variables.product.prodname_dotcom %} は、最初にリポジトリレベル、次に組織レベル、その次に Enterprise レベルでランナーを検索します{% endif %}。 2. ジョブは最初にマッチした、オンラインでアイドル状態のランナーに送信されます。 - マッチしたすべてのランナーがビジーだった場合、ジョブはマッチしたオンラインのランナーが最も多いレベルでキューイングされます。 - マッチしたランナーがすべてオフラインだった場合、ジョブはマッチしたオフラインのランナーが最も多いレベルでキューイングされます。 diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md index 20ff4725c5..bbf7d29456 100644 --- a/translations/ja-JP/content/actions/index.md +++ b/translations/ja-JP/content/actions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /actions/reference/encrypted-secrets changelog: label: 'actions' - prefix: 'GitHub Actions: ' + prefix: 'GitHub Actions:' product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ 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 429b289f46..70571fcad8 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概要' topics: - - 基本 + - '基本' --- {% data reusables.actions.enterprise-beta %} 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 09c66d82e7..c100f4529a 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 @@ -10,9 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概要' topics: - - 基本 + - '基本' --- {% data reusables.actions.enterprise-beta %} 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 48bcf4b41f..3e325f251f 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - Azure Pipelines - - 移行 - - CI - - CD + - 'Azure Pipelines' + - '移行' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 e0e3a8cf85..4109a71d5a 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 @@ -1,18 +1,18 @@ --- title: CircleCIからGitHub Actionsへの移行 -intro: GitHub ActionsとCircleCIには設定に相似点があるので、GitHub Actionsへの移行は比較的単純明快です。 +intro: 'GitHub ActionsとCircleCIには設定に相似点があるので、GitHub Actionsへの移行は比較的単純明快です。' redirect_from: - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - CircleCI - - 移行 - - CI - - CD + - 'CircleCI' + - '移行' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 6d5316075a..9f912a8331 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 @@ -5,12 +5,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - GitLab - - 移行 - - CI - - CD + - 'GitLab' + - '移行' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 24ca1e0c0e..9a123a629c 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - Jenkins - - 移行 - - CI - - CD + - 'Jenkins' + - '移行' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 95fad66e3b..66dad72a1c 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'チュートリアル' topics: - - Travis CI - - 移行 - - CI - - CD + - 'Travis CI' + - '移行' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 06bba3a522..68890607b9 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,13 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: overview + github-ae: '*' +type: '概要' topics: - - セキュリティ + - 'セキュリティ' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### 概要 @@ -22,9 +24,9 @@ topics: ### シークレットを使用する -機密性の高い値は、平文としてワークフローファイルに保存するのではなく、シークレットとして保存してください。 [シークレット](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)は、Organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、リポジトリ、あるいは環境{% else %}あるいはリポジトリ{% endif %}のレベルで設定でき、機密情報を{% data variables.product.product_name %}に保存できるようになります。 +機密性の高い値は、平文としてワークフローファイルに保存するのではなく、シークレットとして保存してください。 [シークレット](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)は、Organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、リポジトリ、環境{% else %}、またはリポジトリ{% endif %}レベルで設定でき、機密情報を {% data variables.product.product_name %} に保存できます。 -シークレットは [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) を使用するため、{% data variables.product.product_name %} に到達する前に暗号化されます。 これは、[UI を使用](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository)して、または [REST API](/rest/reference/actions#secrets) を介してシークレットが送信されたときに発生します。 このクライアント側の暗号化により、{% data variables.product.product_name %} のインフラストラクチャ内での偶発的なログ（例外ログやリクエストログなど）に関連するリスクを最小限に抑えることができます。 シークレットがアップロードされると、{% data variables.product.product_name %} はそれを復号化して、ワークフローランタイムに挿入できるようになります。 +シークレットは [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) を使用するため、{% data variables.product.product_name %} に到達する前に暗号化されます。 これは、[UI を使用](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository)して、または [REST API](/rest/reference/actions#secrets) を介してシークレットが送信されたときに発生します。 This client-side encryption helps minimize the risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. シークレットがアップロードされると、{% data variables.product.product_name %} はそれを復号化して、ワークフローランタイムに挿入できるようになります。 偶発的な開示を防ぐために、{% data variables.product.product_name %} は、実行ログに表示されるシークレットを編集しようとするメカニズムを使用しています。 この編集は、設定されたシークレットの完全一致、および Base64 などの値の一般的なエンコーディングを検索します。 ただし、シークレットの値を変換する方法は複数あるため、この編集は保証されません。 そのため、シークレットを確実に編集し、シークレットに関連する他のリスクを制限するために実行する必要がある、特定の予防的ステップと推奨事項は次のとおりです。 @@ -41,7 +43,7 @@ topics: - **登録されたシークレットの監査とローテーション** - 登録されたシークレットを定期的に確認して、現在も必要であることを確認します。 不要になったものは削除してください。 - シークレットを定期的にローテーションして、不正使用されたシークレットが有効である期間を短縮します。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - **シークレットへのアクセスのレビューを必須とすることを検討する** - 必須のレビュー担当者を使って環境のシークレットを保護できます。 レビュー担当者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 緩急尾へのシークレットの保存、あるいは環境にレビュー担当者を必須とすることの詳細については、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」及び「[環境](/actions/reference/environments)」を参照してください。 {% endif %} @@ -75,7 +77,7 @@ topics: ### リポジトリ間のアクセスを検討する -{% data variables.product.product_name %} は、意図的に一度に単一のリポジトリに対してスコープされます。 `GITHUB_TOKEN` は、書き込みアクセスユーザと同じレベルのアクセスを許可します。書き込みアクセスを持つユーザは、ワークフローファイルを作成または変更することによってこのトークンにアクセスできるためです。 ユーザはリポジトリごとに特定の権限を持っているため、1 つのリポジトリの `GITHUB_TOKEN` に別のリポジトリへのアクセスを許可すると、慎重に実装しない場合 {% data variables.product.prodname_dotcom %} 権限モデルに影響します。 同様に、{% data variables.product.prodname_dotcom %} 認証トークンをワークフローに追加する場合は注意が必要です。これは、コラボレータに誤って広範なアクセスを付与することにより、{% data variables.product.prodname_dotcom %} アクセス許可モデルにも影響を与える可能性があるためです。 +{% data variables.product.prodname_actions %} は、意図的に一度に単一のリポジトリに対してスコープされます。 `GITHUB_TOKEN` は、書き込みアクセスユーザと同じレベルのアクセスを許可します。書き込みアクセスを持つユーザは、ワークフローファイルを作成または変更することによってこのトークンにアクセスできるためです。 ユーザはリポジトリごとに特定の権限を持っているため、1 つのリポジトリの `GITHUB_TOKEN` に別のリポジトリへのアクセスを許可すると、慎重に実装しない場合 {% data variables.product.prodname_dotcom %} 権限モデルに影響します。 同様に、{% data variables.product.prodname_dotcom %} 認証トークンをワークフローに追加する場合は注意が必要です。これは、コラボレータに誤って広範なアクセスを付与することにより、{% data variables.product.prodname_dotcom %} アクセス許可モデルにも影響を与える可能性があるためです。 [{% data variables.product.prodname_dotcom %} ロードマップ](https://github.com/github/roadmap/issues/74)では、{% data variables.product.product_name %} 内のリポジトリ間アクセスを可能にするフローをサポートする計画がありますが、この機能はまだサポートされていません。 現在、権限のあるリポジトリ間のやり取りを実行する唯一の方法は、ワークフロー内に {% data variables.product.prodname_dotcom %} 認証トークンまたは SSH キーをシークレットとして配置することです。 多くの認証トークンタイプでは特定のリソースへの詳細なアクセスが許可されていないことから、意図したものよりはるかに広範なアクセスを許可できるため、間違ったトークンタイプを使用すると重大なリスクが生じます。 @@ -103,7 +105,7 @@ topics: そのため、{% data variables.product.product_name %} の[パブリックリポジトリにセルフホストランナーを使用することはほとんどありません](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)。これは、任意のユーザがリポジトリに対してプルリクエストを開き、環境を危険にさらす可能性があるためです。 同様に、プライベートリポジトリでセルフホストランナーを使用する場合は注意してください。リポジトリをフォークして PR を開くことができるユーザ（一般にリポジトリへの読み取りアクセス権を持つユーザ）は、シークレットへのアクセスと、リポジトリへの書き込みアクセス許可を付与する、より特権的な `GITHUB_TOKEN` を取得することを含め、セルフホストのランナー環境を危険にさらすことができるためです。 -セルフホストランナーがOrganizationもしくはEnterpriseのレベルで定義されているなら、{% data variables.product.product_name %}は同じランナー上で複数のリポジトリからのワークフローをスケジューリングするかもしれません。 したがって、これらの環境へのセキュリティ侵害は、大きな影響をもたらす可能性があります。 侵害の範囲を狭めるために、セルフホストランナーを個別のグループにまとめることで、境界を作ることができます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスの管理](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 +セルフホストランナーがOrganizationもしくはEnterpriseのレベルで定義されているなら、{% data variables.product.product_name %}は同じランナー上で複数のリポジトリからのワークフローをスケジューリングするかもしれません。 したがって、これらの環境へのセキュリティ侵害は、大きな影響をもたらす可能性があります。 侵害の範囲を狭めるために、セルフホストランナーを個別のグループにまとめることで、境界を作ることができます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 次のように、セルフホストランナーマシンの環境も考慮する必要があります。 - セルフホストランナーとして設定されたマシンにはどのような機密情報が存在するか。 たとえば、SSH 秘密鍵、API アクセストークンなどです。 @@ -115,33 +117,68 @@ topics: Organizationの管理タスクをモニタするために、監査ログを使用できます。 監査ログは、アクションの種類、実行された時刻、実行したユーザアカウントを記録します。 -たとえば、監査ログを使って`action:org.update_actions_secret`イベントを追跡できます。これは、Organizationのシークレットの変更を追跡します。 ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png) +たとえば、監査ログを使用して、Organization のシークレットへの変更を追跡する `org.update_actions_secret` イベントを追跡できます。 ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png) -以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 監査ログの使用に関する詳しい情報については、「[Organization の監査ログのレビュー](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" %} +#### Events for environments + +| アクション | 説明 | +| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `environment.remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Events for configuration changes +| アクション | 説明 | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +{% endif %} #### シークレット管理のイベント -| アクション | 説明 | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.create_actions_secret` | Organizationの管理者が[{% data variables.product.prodname_actions %}シークレットを作成](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)したときにトリガーされます。 | -| `action:org.remove_actions_secret` | Organizationの管理者が{% data variables.product.prodname_actions %}シークレットを削除したときにトリガーされます。 | -| `action:org.update_actions_secret` | Organizationの管理者が{% data variables.product.prodname_actions %}シークレットを更新したときにトリガーされます。 | -| `action:repo.create_actions_secret` | リポジトリ管理者が[{% data variables.product.prodname_actions %}シークレットを作成](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)したときにトリガーされます。 | -| `action:repo.remove_actions_secret` | リポジトリ管理者が{% data variables.product.prodname_actions %}シークレットを削除したときにトリガーされます。 | -| `action:repo.update_actions_secret` | リポジトリ管理者が{% data variables.product.prodname_actions %}シークレットを更新したときにトリガーされます。 | +| アクション | 説明 | +| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org.create_actions_secret` | Organization に対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。 | +| `org.remove_actions_secret` | {% data variables.product.prodname_actions %} シークレットが削除されたときにトリガーされます。 | +| `org.update_actions_secret` | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。 | +| `repo.create_actions_secret` | リポジトリに対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[リポジトリに対して暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。 | +| `repo.remove_actions_secret` | {% data variables.product.prodname_actions %} シークレットが削除されたときにトリガーされます。 | +| `repo.update_actions_secret` | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。 | #### セルフホストランナーのイベント -| アクション | 説明 | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.register_self_hosted_runner` | Organizationのオーナーが[新しいセルフホストランナーを登録](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)したときにトリガーされます。 | -| `action:org.remove_self_hosted_runner` | Organizationのオーナーが[セルフホストランナーを削除](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)したときにトリガーされます。 | -| `action:repo.register_self_hosted_runner` | リポジトリ管理者が[新しいセルフホストランナーを登録](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)したときにトリガーされます。 | -| `action:repo.remove_self_hosted_runner` | リポジトリ管理者が[セルフホストランナーを削除](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)したときにトリガーされます。 | +| アクション | 説明 | +| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% else %} | | +| `enterprise.register_self_hosted_runner` | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については「[Enterpriseへのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)」を参照してください。 | +| `enterprise.remove_self_hosted_runner` | セルフホストランナーが削除されたときにトリガーされます。 | +| `enterprise.runner_group_runners_updated` | ランナーグループのメンバーリストが更新されたときにトリガーされます。 詳しい情報については「[Organizationのグループ内にセルフホストランナーをセットする](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。 | +| `enterprise.self_hosted_runner_updated` | ランナーアプリケーションが更新されたときにトリガーされます。 Can be viewed using the REST API and the UI. This event is not included when you export the audit log as JSON data or a CSV file. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" and "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."{% endif %} +| `org.register_self_hosted_runner` | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。 | +| `org.remove_self_hosted_runner` | セルフホストランナーが削除されたときにトリガーされます。 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。 | +| `org.runner_group_runners_updated` | ランナーグループのメンバーリストが更新されたときにトリガーされます。 詳しい情報については「[Organizationのグループ内にセルフホストランナーをセットする](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。 | +| `org.runner_group_updated` | セルフホストランナーグループの設定が変更されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 | +| `org.self_hosted_runner_updated` | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。 | +| `repo.register_self_hosted_runner` | 新しいセルフホストランナーが登録されたときにトリガーされます。 For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `repo.remove_self_hosted_runner` | セルフホストランナーが削除されたときにトリガーされます。 For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." | +| `repo.self_hosted_runner_updated` | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。 | #### セルフホストランナーグループのイベント -| アクション | 説明 | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.runner_group_created` | Organizationの管理者が[セルフホストランナーグループを作成](/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` | Organizationの管理者がセルフホストランナーグループを削除したときにトリガーされます。 | -| `action:org.runner_group_renamed` | Organizationの管理者がセルフホストランナーグループの名前を変更したときにトリガーされます。 | -| `action:org.runner_group_runners_added` | Organizationの管理者が[セルフホストランナーをグループに追加](/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` | Organizationの管理者がセルフホストランナーをグループから削除したときにトリガーされます。 | +| アクション | 説明 | +| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise.runner_group_created` | セルフホストランナーグループが作成されたときにトリガーされます。 詳しい情報については、「[Enterprise のセルフホストランナーグループを作成する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)」を参照してください。 | +| `enterprise.runner_group_removed` | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。 | +| `enterprise.runner_group_runner_removed` | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 | +| `enterprise.runner_group_runners_added` | セルフホストランナーがグループに追加されたときにトリガーされます。 詳しい情報については、「[セルフホストランナーをグループに移動する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。 | +| `enterprise.runner_group_updated` | セルフホストランナーグループの設定が変更されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 | +| `org.runner_group_created` | セルフホストランナーグループが作成されたときにトリガーされます。 For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." | +| `org.runner_group_removed` | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。 | +| `org.runner_group_runners_added` | セルフホストランナーがグループに追加されたときにトリガーされます。 詳しい情報については、「[セルフホストランナーをグループに移動する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。 | +| `org.runner_group_runner_removed` | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | + +#### ワークフローアクティビティのイベント + +{% data reusables.actions.actions-audit-events-workflow %} diff --git a/translations/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md index d0cd39c60a..2057ccf2ed 100644 --- a/translations/ja-JP/content/actions/quickstart.md +++ b/translations/ja-JP/content/actions/quickstart.md @@ -1,6 +1,6 @@ --- title: GitHub Actions のクイックスタート -intro: '{% data variables.product.prodname_actions %} ワークフローを 5 分以内に既存のリポジトリに追加します。' +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates @@ -19,57 +19,58 @@ topics: ### はじめに -{% data variables.product.prodname_actions %} ワークフローを作成して実行するには、既存の {% data variables.product.prodname_dotcom %} リポジトリのみが必要です。 このガイドでは、[{% data variables.product.prodname_dotcom %} Super-Linter アクション](https://github.com/github/super-linter)を使用して複数のコーディング言語の文法チェックを行うワークフローを追加します。 ワークフローは Super-Linter を使用して、新しいコミットがリポジトリにプッシュされるたびにソースコードを検証します。 +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. + +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. ### 最初のワークフローを作成する -1. {% data variables.product.prodname_dotcom %} のリポジトリから、`superlinter.yml` という名前の新しいファイルを `.github/workflows` ディレクトリに作成します。 詳細は「[新しいファイルを作成する](/github/managing-files-in-a-repository/creating-new-files)」を参照してください。 -2. 次の YAML コンテンツを `superlinter.yml` ファイルにコピーします。 **注釈:** デフォルトブランチが `main` でない場合は、リポジトリのデフォルトブランチ名と一致するように `DEFAULT_BRANCH` の値を更新してください。 +1. {% data variables.product.prodname_dotcom %} のリポジトリから、`github-actions-demo.yml` という名前の新しいファイルを `.github/workflows` ディレクトリに作成します。 詳細は「[新しいファイルを作成する](/github/managing-files-in-a-repository/creating-new-files)」を参照してください。 +2. Copy the following YAML contents into the `github-actions-demo.yml` file: {% raw %} ```yaml{:copy} - name: Super-Linter - - # 新しいコミットがリポジトリにプッシュされるたびにこのワークフローを実行する - on: push - + name: GitHub Actions Demo + on: [push] jobs: - # ジョブキーを設定する。 ジョブ名が指定されていない場合、 - # キーはジョブ名として表示される - super-lint: - # ジョブ名を付ける - name: Lint code base - # 実行するマシンのタイプを設定する + Explore-GitHub-Actions: runs-on: ubuntu-latest - steps: - # ubuntu-latest マシンでリポジトリのコピーをチェックアウトする - - name: Checkout code + - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event." + - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!" + - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}." + - name: Check out repository code uses: actions/checkout@v2 + - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner." + - run: echo "🖥️ The workflow is now ready to test your code on the runner." + - name: List files in the repository + run: | + ls ${{ github.workspace }} + - run: echo "🍏 This job's status is ${{ job.status }}." - # Super-Linter アクションを実行する - - name: Run Super-Linter - uses: github/super-linter@v3 - env: - DEFAULT_BRANCH: main - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` {% endraw %} -3. ワークフローを実行するには、ページの一番下までスクロールし、[**Create a new branch for this commit and start a pull request**] を選択します。 次に、[**Propose new file**] をクリックしてPull Requestを作成します。 ![ワークフローファイルのコミット](/assets/images/commit-workflow-file.png) +3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. 次に、[**Propose new file**] をクリックしてPull Requestを作成します。 ![ワークフローファイルのコミット](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -リポジトリ内のワークフローファイルをコミットすると、`push` イベントがトリガーされ、ワークフローが実行されます。 +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. ### ワークフローの結果を表示する {% 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" or currentVersion == "github-ae@latest" %} -1. **Jobs（ジョブ）**の下、もしくは可視化グラフ内で、**Lint code base**ジョブをクリックしてください。 ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) -{% else %} -1. 左サイドバーで、[**Lint code base**] をクリックします。 ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job.png) -{% endif %} -{% data reusables.repositories.view-failed-job-results-superlinter %} +1. 左のサイドバーで、表示させたいワークフローをクリックしてください。 + + ![左サイドバーのワークフローのリスト](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +1. From the list of workflow runs, click the name of the run you want to see. + + ![ワークフローの実行の名前](/assets/images/help/repository/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. + + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. + + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) ### さらなるワークフローテンプレート @@ -77,74 +78,12 @@ topics: ### 次のステップ -追加した super-linter ワークフローは、コードがリポジトリにプッシュされるたびに実行され、コードのエラーや不整合を見つけます。 ただし、これは {% data variables.product.prodname_actions %} でできることの一部にすぎません。 リポジトリには、さまざまなイベントに基づいてさまざまなジョブをトリガーする複数のワークフローを含めることができます。 {% data variables.product.prodname_actions %} は、アプリケーション開発プロセスのほぼすべての要素を自動化するのに役立ちます。 始める準備はできましたか？ {% data variables.product.prodname_actions %} で次のステップに進む際に役立つ、以下のようなリソースを参照してください。 +The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}: -- 詳細なチュートリアルは、「[{% data variables.product.prodname_actions %}を学ぶ](/actions/learn-github-actions)」をご覧ください -- 特定の使用例とサンプルについては、「[ガイド](/actions/guides)」 -- Super-Linter アクションの設定の詳細については、[github/super-linter](https://github.com/github/super-linter) +- リポジトリには、さまざまなイベントに基づいてさまざまなジョブをトリガーする複数のワークフローを含めることができます。 +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. - +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial. +- "[Guides](/actions/guides)" for specific uses cases and examples. diff --git a/translations/ja-JP/content/actions/reference/encrypted-secrets.md b/translations/ja-JP/content/actions/reference/encrypted-secrets.md index 50548c7671..a5ad135900 100644 --- a/translations/ja-JP/content/actions/reference/encrypted-secrets.md +++ b/translations/ja-JP/content/actions/reference/encrypted-secrets.md @@ -9,19 +9,21 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.environments-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### 暗号化されたシークレットについて -シークレットは暗号化された環境変数で、Organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} リポジトリ、あるいはリポジトリ環境{% else %}あるいはリポジトリ{% endif %}に作成できます。 作成したシークレットは、{% data variables.product.prodname_actions %}ワークフローで利用できます。 {% data variables.product.prodname_dotcom %}はシークレットが{% data variables.product.prodname_dotcom %}に到達する前に暗号化され、ワークフローで使用されるまで暗号化されたままになっていることを確実にするのを助けるために[libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)を使います。 +シークレットは暗号化された環境変数で、Organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、リポジトリ、またはリポジトリ環境{% else %} またはリポジトリで作成できます{% endif %}。 作成したシークレットは、{% data variables.product.prodname_actions %}ワークフローで利用できます。 {% data variables.product.prodname_dotcom %}はシークレットが{% data variables.product.prodname_dotcom %}に到達する前に暗号化され、ワークフローで使用されるまで暗号化されたままになっていることを確実にするのを助けるために[libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)を使います。 {% data reusables.github-actions.secrets-org-level-overview %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} 環境レベルで保存されたシークレットについては、それらへのアクセスを制御するために必須のレビュー担当者を有効化することができます。 必須の承認者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 {% endif %} @@ -33,9 +35,9 @@ versions: * シークレット名の最初を `GITHUB_` プレフィックスにすることはできません。 * シークレット名の最初を数字にすることはできません。 * シークレット名は大文字と小文字を区別しません。 -* シークレット名は、作成されたレベルで一意である必要があります。 たとえば {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}環境のレベルで作成されたシークレットはその環境内でユニークな名前になっていなければならず、{% endif %}リポジトリのレベルで作成されたシークレットはそのリポジトリ内でユニークな名前になっていなければならず、Organizationのレベルで作成されたシークレットはそのレベルでユニークな名前になっていなければなりません。 +* シークレット名は、作成されたレベルで一意である必要があります。 たとえば、環境レベルで作成されたシークレットには、その環境で一意の名前である必要があり、{% endif %}リポジトリレベルで作成されたシークレットは、そのリポジトリ内で一意の名前である必要があり、Organization レベルで作成されたシークレットは、そのレベルで一意である必要があります。 - 複数のレベルで同じ名前のシークレットが存在する場合、低いレベルのシークレットが優先されます。 たとえば、Organizationレベルのシークレットがリポジトリレベルのシークレットと同じ名前を持っているなら、リポジトリレベルのシークレットが優先されます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}同様に、Organization、リポジトリ、環境のすべてのレベルで同じ名前のシークレットがあるなら、環境レベルのシークレットが優先されます。{% endif %} + 複数のレベルで同じ名前のシークレットが存在する場合、低いレベルのシークレットが優先されます。 たとえば、Organization レベルのシークレットがリポジトリレベルのシークレットと同じ名前である場合、リポジトリレベルのシークレットが優先されます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} 同様に、Organization、リポジトリ、および環境がすべて同じ名前のシークレットがある場合、環境レベルのシークレットが優先されます。{% endif %} {% data variables.product.prodname_dotcom %} がログのシークレットを確実に削除するよう、シークレットの値として構造化データを使用しないでください。 たとえば、JSONやエンコードされたGit blobを含むシークレットは作成しないでください。 @@ -43,7 +45,7 @@ versions: シークレットをアクションが使用できるようにするには、ワークフローファイルでシークレットを入力または環境変数に設定する必要があります。 アクションに必要な入力および環境変数については、アクションのREADMEファイルを確認します。 詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)」を参照してください。 -ワークフローファイルを編集するアクセス権を持っていれば、ワークフローファイル中の暗号化されたシークレットを使い、読み取ることができます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/github/getting-started-with-github/access-permissions-on-github)」を参照してください。 +ファイルを編集するアクセス権を持っていれば、ワークフローファイル中の暗号化されたシークレットを使い、読み取ることができます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/github/getting-started-with-github/access-permissions-on-github)」を参照してください。 {% warning %} @@ -51,7 +53,7 @@ versions: {% endwarning %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} Organization及びリポジトリのシークレットはワークフローの実行がキューイングされた時点で読まれ、環境のシークレットは環境を参照しているジョブが開始された時点で読まれます。 {% endif %} @@ -59,7 +61,7 @@ REST API を使用してシークレットを管理することもできます #### 認証情報のアクセス許可を制限する -認証情報を生成する際には、可能な限り最小限の権限だけを許可することをおすすめします。 たとえば、個人の認証情報を使う代わりに、[デプロイキー](/developers/overview/managing-deploy-keys#deploy-keys)あるいはサービスアカウントを使ってください。 必要なのが読み取りだけであれば、読み取りのみの権限を許可すること、そしてアクセスをできるかぎり限定することを考慮してください。 個人アクセストークン（PAT）を生成する際には、必要最小限のスコープを選択してください。 +クレデンシャルを生成する際には、可能な限り最小限の権限だけを許可することをおすすめします。 たとえば、個人の認証情報を使う代わりに、[デプロイキー](/developers/overview/managing-deploy-keys#deploy-keys)あるいはサービスアカウントを使ってください。 必要なのが読み取りだけであれば、読み取りのみの権限を許可すること、そしてアクセスをできるかぎり限定することを考慮してください。 個人アクセストークン（PAT）を生成する際には、必要最小限のスコープを選択してください。 ### リポジトリの暗号化されたシークレットの作成 @@ -73,9 +75,15 @@ REST API を使用してシークレットを管理することもできます 1. シークレットの値を入力します。 1. [**Add secret（シークレットの追加）**] をクリックします。 -リポジトリが{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}環境のシークレットを持っているか{% endif %}親のOrganizationのシークレットにアクセスできるなら、それらのシークレットもこのページにリストされます。 +リポジトリに{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0"or currentVersion == "github-ae@latest" %}環境のシークレットがある場合、または{% endif %}親 Organization のシークレットにアクセスできる場合は、それらのシークレットもこのページに一覧表示されます。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**注釈:** コラボレータアクセスを持つユーザは、REST API を使用してリポジトリのシークレットを管理できます。 詳しい情報については「[{% data variables.product.prodname_actions %}シークレットAPI](/rest/reference/actions#secrets)」を参照してください。 + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" } ### 環境の暗号化されたシークレットの生成 {% data reusables.github-actions.permissions-statement-secrets-environment %} @@ -177,7 +185,7 @@ steps: ### シークレットの制限 -Organizationには最大1,000個のシークレットを{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、リポジトリには100個のシークレットを、環境には100個のシークレットを{% else %}、リポジトリには100個のシークレットを{% endif %}保存できます。 ワークフローは最大で100個のOrganizationのシークレットと100個のリポジトリシークレットを利用できます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 加えて、環境を参照するジョブは最大で100個の環境のシークレットを利用できます。{% endif %} +Organization ごとに最大 1,000 個のシークレット{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、リポジトリごとに 100 個のシークレット、環境ごとに 100 個のシークレット{% else %}、リポジトリごとに 100 個のシークレット{% endif %} を保存できます。 ワークフローでは、最大 100 個の Organization のシークレットと 100 個のリポジトリのシークレットを使用できます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} さらに、環境を参照するジョブは、最大で 100 個の環境のシークレットを使用できます。{% endif %} シークレットの容量は最大64 KBです。 64 KBより大きなシークレットを使うには、暗号化されたシークレットをリポジトリ内に保存して、復号化パスフレーズを{% data variables.product.prodname_dotcom %}に保存します。 たとえば、{% data variables.product.prodname_dotcom %}のリポジトリにファイルをチェックインする前に、`gpg`を使って認証情報をローカルで暗号化します。 詳しい情報については、「[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)」を参照してください。 diff --git a/translations/ja-JP/content/actions/reference/environment-variables.md b/translations/ja-JP/content/actions/reference/environment-variables.md index 8b2755b527..9ebd71d378 100644 --- a/translations/ja-JP/content/actions/reference/environment-variables.md +++ b/translations/ja-JP/content/actions/reference/environment-variables.md @@ -22,6 +22,7 @@ versions: カスタムの環境変数を設定するには、ワークフローファイル中でその変数を指定しなければなりません。 [`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)、[`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)といったキーワードを使って、ステップ、ジョブ、あるいはワークフロー全体の環境変数を定義できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)」を参照してください。 +{% raw %} ```yaml jobs: weekday_job: @@ -30,13 +31,14 @@ jobs: DAY_OF_WEEK: Mon steps: - name: "Hello world when it's Monday" - if: env.DAY_OF_WEEK == 'Mon' + if: ${{ env.DAY_OF_WEEK == 'Mon' }} run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" env: FIRST_NAME: Mona middle_name: The Last_Name: Octocat ``` +{% endraw %} 環境変数の値をワークフローファイル内で使うには、[`env`コンテキスト](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)を使わなければなりません。 環境変数の値をランナー内で使いたいなら、ランナーのオペレーティングシステムで環境変数を読む通常の方法が使えます。 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 d36e2232e1..75ae8ba311 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 @@ -70,7 +70,7 @@ GitHub アクションの使用は、 詳しい情報については、以下を参照してください。 - [リポジトリ内の成果物とログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) -- [Organization 内の成果物とログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [Organization 内の成果物とログの {% data variables.product.prodname_actions %} の保持期間を設定する](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) - [Enterprise 内の成果物とログの {% data variables.product.prodname_actions %} の保持期間を設定する](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) {% endif %} @@ -80,7 +80,7 @@ GitHub アクションの使用は、 詳しい情報については、以下を参照してください。 - 「[リポジトリの {% data variables.product.prodname_actions %} を無効化または制限する](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)」 -- 「[Organization の {% data variables.product.prodname_actions %} を無効化または制限する](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)」{% if currentVersion == "free-pro-team@latest" %} +- 「[Organization の {% data variables.product.prodname_actions %} を無効化または制限する](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)」{% if currentVersion == "free-pro-team@latest" %} - {% data variables.product.prodname_ghe_cloud %} の「[Enterprise アカウントでの {% data variables.product.prodname_actions %} ポリシーを適用する](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)」{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index e881b0e656..6fe5fff9ec 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -21,7 +21,7 @@ Azure AD を使用して {% data variables.product.prodname_ghe_managed %} に * {% data variables.product.prodname_ghe_managed %} アプリケーションを Azure AD の IdP グループに割り当てて、IdP グループのすべてのメンバーの {% data variables.product.product_name %} 上のユーザアカウントを自動的に作成し、アクセスを許可します。 さらに、IdP グループは {% data variables.product.prodname_ghe_managed %} で利用でき、Team とその親 Organization に接続できます。 * IdP グループから {% data variables.product.prodname_ghe_managed %} アプリケーションの割り当てを解除して、その IdP グループを介してのみアクセスできるすべての IdP ユーザの {% data variables.product.product_name %} ユーザアカウントを非アクティブ化し、親 Organization からユーザを削除します。 IdP グループは {% data variables.product.product_name %} のどの Team からも切断されます -{% data variables.product.product_location %} での Enterprise のアイデンティティとアクセスの管理の詳細については、「[Enterprise のアイデンティティとアクセスを管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise)」を参照してください。 Team を IdP グループと同期する方法について詳しくは、「[アイデンティティプロバイダグループとTeamの同期](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 +{% data variables.product.product_location %} での Enterprise のアイデンティティとアクセスの管理の詳細については、「[Enterprise のアイデンティティとアクセスを管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise)」を参照してください。 Team を IdP グループと同期する方法について詳しくは、「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 ### 必要な環境 diff --git a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index 6d7670cbdb..a6b56d4113 100644 --- a/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -28,7 +28,7 @@ IdP のプロビジョニングアプリケーションは、Enterprise 向け {% data reusables.scim.supported-idps %} -サポートされている IdP を使用してユーザプロビジョニングを設定する場合、{% data variables.product.product_name %} のアプリケーションをユーザのグループに割り当てたり、割り当てを解除したりすることもできます。 これらのグループは、{% data variables.product.product_location %} の Organization のオーナーとチームメンテナが {% data variables.product.product_name %} Team にマッピングできるようになります。 詳しい情報については「[Team をアイデンティティプロバイダグループと同期する](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 +サポートされている IdP を使用してユーザプロビジョニングを設定する場合、{% data variables.product.product_name %} のアプリケーションをユーザのグループに割り当てたり、割り当てを解除したりすることもできます。 これらのグループは、{% data variables.product.product_location %} の Organization のオーナーとチームメンテナが {% data variables.product.product_name %} Team にマッピングできるようになります。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 ### 必要な環境 diff --git a/translations/ja-JP/content/admin/authentication/using-saml.md b/translations/ja-JP/content/admin/authentication/using-saml.md index 0a5b1e7e25..af74380961 100644 --- a/translations/ja-JP/content/admin/authentication/using-saml.md +++ b/translations/ja-JP/content/admin/authentication/using-saml.md @@ -8,6 +8,8 @@ redirect_from: intro: 'SAML は認証と認可のための XML ベースの標準です。 {% data variables.product.prodname_ghe_server %} は、内部的な SAML アイデンティティプロバイダ (IdP) とサービスプロバイダ (SP) として動作できます。' versions: enterprise-server: '*' +topics: + - enterprise --- {% data reusables.enterprise_user_management.built-in-authentication %} @@ -29,7 +31,7 @@ versions: `NameID`要素は、他の属性が存在する場合でも必須です。 -A mapping is created between the `NameID` and the {% data variables.product.prodname_ghe_server %} username, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +`NameID` と {% data variables.product.prodname_ghe_server %} ユーザ名の間にマッピングが作成されるため、`NameID` は永続的で一意でなければならず、ユーザのライフサイクルにおいて変更にさらされないようにする必要があります。 {% note %} @@ -46,7 +48,7 @@ A mapping is created between the `NameID` and the {% data variables.product.prod ### SAMLのメタデータ -Your {% data variables.product.prodname_ghe_server %} instance's service provider metadata is available at `http(s)://[hostname]/saml/metadata`. +{% data variables.product.prodname_ghe_server %} インスタンスのサービスプロバイダメタデータは、`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/restricting-network-traffic-to-your-enterprise.md b/translations/ja-JP/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index 3b07038419..e65553d3e6 100644 --- a/translations/ja-JP/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -13,7 +13,7 @@ versions: {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -許可 IP アドレスを、Organization ごとに設定することもできます。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)」を参照してください。 +許可 IP アドレスを、Organization ごとに設定することもできます。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)」を参照してください。 既定では、Azure ネットワークセキュリティグループ (NSG) ルールで、ポート 22、80、443、および 25 ですべてのインバウンドトラフィックが開いたままになります。 Enterprise オーナーは {% data variables.contact.github_support %} に問い合わせて、インスタンスのアクセス制限を設定できます。 diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md index 2cfaf44bc4..7a19e323d1 100644 --- a/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md +++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-cluster-nodes.md @@ -6,6 +6,8 @@ redirect_from: - /enterprise/admin/enterprise-management/monitoring-cluster-nodes versions: enterprise-server: '*' +topics: + - enterprise --- ### クラスタのステータスの手動でのチェック @@ -44,24 +46,25 @@ admin@ghe-data-node-0:~$ ghe-cluster-status | grep error ``` {% danger %} + {{#danger}} **セキュリティの警告:** パスフレーズを持たない SSH キーは、ホストへの完全なアクセスを承認されていた場合、セキュリティリスクになることがあります。 このキーの承認は、単一の読み取りのみのコマンドに限定してください。 {% enddanger %} {% note %} - **Note:** If you're using a distribution of Linux that doesn't support the Ed25519 algorithm, use the command: + **注釈:** Ed25519 アルゴリズムをサポートしていない Linux ディストリビューションを使用している場合は、次のコマンドを使用します。 ```shell nagiosuser@nagios:~$ ssh-keygen -t rsa -b 4096 ``` {% endnote %} -2. Copy the private key (`id_ed25519`) to the `nagios` home folder and set the appropriate ownership. +2. 秘密鍵 (`id_ed25519`) を `nagios` ホームフォルダにコピーし、適切な所有権を設定します。 ```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. `ghe-cluster-status -n` コマンド*のみ*を実行するために公開鍵を認証するには、`/data/user/common/authorized_keys` ファイル中で `command=` プレフィックスを使ってください。 任意のノードの管理シェルから、このファイルを変更してステップ1で生成した公開鍵を追加してください。 For example: `command="/usr/local/bin/ghe-cluster-status -n" ssh-ed25519 AAAA....` +3. `ghe-cluster-status -n` コマンド*のみ*を実行するために公開鍵を認証するには、`/data/user/common/authorized_keys` ファイル中で `command=` プレフィックスを使ってください。 任意のノードの管理シェルから、このファイルを変更してステップ1で生成した公開鍵を追加してください。 例: `command="/usr/local/bin/ghe-cluster-status -n" ssh-ed25519 AAAA....` 4. `/data/user/common/authorized_keys` ファイルを変更したノード上で `ghe-cluster-config-apply` を実行し、設定を検証してクラスタ内の各ノードにコピーしてください。 diff --git a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md index 70ce0e39c1..f02b6c4b24 100644 --- a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md @@ -37,7 +37,7 @@ topics: {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} 詳細は「[{% data variables.product.prodname_ghe_server %} Supportへの連絡](/enterprise/admin/guides/enterprise-support/reaching-github-support)」を参照してください。 +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md index 524d96c477..ba37c97f44 100644 --- a/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md +++ b/translations/ja-JP/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md @@ -35,7 +35,7 @@ topics: {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} 詳細は「[{% data variables.product.prodname_ghe_server %} Supportへの連絡](/enterprise/admin/guides/enterprise-support/reaching-github-support)」を参照してください。 +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/ja-JP/content/admin/github-actions/index.md b/translations/ja-JP/content/admin/github-actions/index.md index d2232303b5..c1e4387a66 100644 --- a/translations/ja-JP/content/admin/github-actions/index.md +++ b/translations/ja-JP/content/admin/github-actions/index.md @@ -32,6 +32,7 @@ topics: {% 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 /using-the-latest-version-of-the-official-bundled-actions %} {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} {% topic_link_in_list /advanced-configuration-and-troubleshooting %} 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 aec2211476..33cda8aac0 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 @@ -28,8 +28,21 @@ topics: ### 必要な環境 -* `actions-sync` ツールを使用する前に、すべての宛先 Organization が Enterprise インスタンスにすでに存在していることを確認する必要があります。 次の例は、Enterprise インスタンスの `synced-actions` という名前の Organization にアクションを同期する方法を示しています。 詳しい情報については、「[新しい Organization をゼロから作成する](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)」を参照してください。 +* `actions-sync` ツールを使用する前に、すべての宛先 Organization が Enterprise インスタンスにすでに存在していることを確認する必要があります。 次の例は、Enterprise インスタンスの `synced-actions` という名前の Organization にアクションを同期する方法を示しています。 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。 * Enterprise インスタンスに、宛先 Organization のリポジトリを作成して書き込むことができる個人アクセストークン (PAT) を作成する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。 +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. + + {% note %} + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + + {% endnote %} + + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." + + ```shell + ghe-org-admin-promote -u USERNAME -o actions + ``` ### 例: `actions-sync` ツールを使用する diff --git a/translations/ja-JP/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ja-JP/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md new file mode 100644 index 0000000000..ae208f091b --- /dev/null +++ b/translations/ja-JP/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md @@ -0,0 +1,45 @@ +--- +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '>=2.22' +topics: + - enterprise +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server). + +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}. + +Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}: + +- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}. +- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions. + +These options are described in more detail in the following sections. + +### Using actions-sync to update a bundled action + +To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." + +### Using actions from {% data variables.product.prodname_dotcom_the_website %} + +{% data reusables.github-actions.actions-github-connect-requirement %} + +Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file. + +### Using the latest version by removing the specific action's tag + +{% data reusables.github-actions.actions-github-connect-requirement %} + +If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)." + +For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}: + +1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository. +1. Create a workflow that uses `actions/setup-python` with the `v2` tag. + +When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}. 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 306fb07843..ca0142ae6b 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 @@ -1,6 +1,6 @@ --- title: Hyper-V で GitHub Enterprise Server をインストールする -intro: '{% data variables.product.prodname_ghe_server %} を Hyper-V にインストールするには、Windows Server 2008 から Windows Server 2016 までを実行しているマシンに配備する必要があります。' +intro: '{% data variables.product.prodname_ghe_server %} を Hyper-V にインストールするには、Windows Server 2008 から Windows Server 2019 までを実行しているマシンに配備する必要があります。' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v @@ -13,7 +13,7 @@ topics: ### 必要な環境 - {% data reusables.enterprise_installation.software-license %} -- Hyper-VをサポートしているWindows Server 2008からWindows Server 2016を持っている必要があります。 +- Hyper-VをサポートしているWindows Server 2008からWindows Server 2019を持っている必要があります。 - 仮想マシン（VM）の作成に必要なほとんどのアクションは、 [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts)を使っても行えます。 とはいえ、初期セットアップのためにはWindows PowerShellコマンドラインシェルを使うことをおすすめします。 以下の例ではPowerShellを使っています。 詳細については、Microsoft ガイド「[Windows PowerShell 入門](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)」を参照してください。 ### ハードウェアについて diff --git a/translations/ja-JP/content/admin/overview/github-ae-release-notes.md b/translations/ja-JP/content/admin/overview/github-ae-release-notes.md index 51061be479..d34bda8f04 100644 --- a/translations/ja-JP/content/admin/overview/github-ae-release-notes.md +++ b/translations/ja-JP/content/admin/overview/github-ae-release-notes.md @@ -29,7 +29,7 @@ During this beta, {% data variables.product.prodname_advanced_security %} featur #### アイデンティティプロバイダ (IdP) での Team の管理 -SCIM (System for Cross-domain Identity Management) を使用しているお客様は、Azure Active Directory のセキュリティグループを {% data variables.product.company_short %} Team と同期できるようになりました。 チームがセキュリティグループにリンクされると、ユーザが割り当てられたセキュリティグループに追加または削除されたときに、メンバーシップは {% data variables.product.product_name %} で自動的に更新されます。 詳しい情報については「[Team をアイデンティティプロバイダグループと同期する](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 +SCIM (System for Cross-domain Identity Management) を使用しているお客様は、Azure Active Directory のセキュリティグループを {% data variables.product.company_short %} Team と同期できるようになりました。 チームがセキュリティグループにリンクされると、ユーザが割り当てられたセキュリティグループに追加または削除されたときに、メンバーシップは {% data variables.product.product_name %} で自動的に更新されます。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 #### IP 許可リストベータ @@ -37,18 +37,18 @@ Enterprise and organization owners can now use IP allow lists to restrict traffi This functionality is provided in addition to the ability to request network security group changes that filter traffic to the entirety of the {% data variables.product.product_name %} tenant. -For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." #### Pull request auto-merge -With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements (like missing approvals or pending or failing required status checks). For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." +With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements (like missing approvals or pending or failing required status checks). 詳しい情報については「[Pull Requestの自動マージ](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)」を参照してください。 ### 変更 #### 開発者に関する変更 -- Organization のオーナーは、Organization 内のリポジトリからの {% data variables.product.prodname_pages %} サイトの[公開を無効化](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)できるようになりました。 これにより、既存のサイトが非公開になることはありません。 -- {% data variables.product.prodname_pages %} を使用するリポジトリは、[任意のブランチからビルドおよびデプロイ](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)できるようになりました。 +- Organization のオーナーは、Organization 内のリポジトリからの {% data variables.product.prodname_pages %} サイトの[公開を無効化](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)できるようになりました。 これにより、既存のサイトが非公開になることはありません。 +- {% data variables.product.prodname_pages %} を使用するリポジトリは、[任意のブランチからビルドおよびデプロイ](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)できるようになりました。 - Issue またはプルリクエストを作成するときに、`return` キーまたは `enter` キーを押すと、箇条書き、番号、およびタスクのリスト構文がオートコンプリートされるようになりました。 - リポジトリページからリポジトリ内のディレクトリを削除できるようになりました。 ディレクトリに移動するとき、[Add file] ボタンの横にある新しいケバブボタンで、ディレクトリを削除できます。 - 「#」の後に複数の単語を検索することで、[Issue やプルリクエストの参照](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests)がより簡単かつ迅速になりました。 @@ -65,7 +65,7 @@ With auto-merge, pull requests can be set to merge automatically when all merge ##### デフォルトブランチの名称変更 -Enterprise および Organization のオーナーは、新しいリポジトリのデフォルトブランチ名を設定できるようになりました。 Enterprise のオーナーは、すべての Organization でデフォルトブランチ名の選択を強制したり、個々の Organization が独自のブランチ名を選択できるようにすることもできます。 For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[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)." +Enterprise および Organization のオーナーは、新しいリポジトリのデフォルトブランチ名を設定できるようになりました。 Enterprise のオーナーは、すべての Organization でデフォルトブランチ名の選択を強制したり、個々の Organization が独自のブランチ名を選択できるようにすることもできます。 For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." 既存のリポジトリはこれらの設定の影響を受けず、デフォルトのブランチ名は変更されません。 diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md index ada1aa9d20..5a14c073bc 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md @@ -4,7 +4,7 @@ intro: 'Enterprise owners can enforce policies to manage {% data variables.produ product: '{% data reusables.gated-features.ghas %}' versions: enterprise-server: '>=3.1' - github-ae: '*' + github-ae: '次' --- ### {% data variables.product.prodname_GH_advanced_security %} について 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 bb12b0920c..48d727a1df 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 @@ -66,17 +66,16 @@ topics: - {% data variables.product.product_location %} のヘルプの取得方法をユーザに伝える - すべてのユーザが {% data variables.product.product_location %} を使用時の利用規約を確実に読むようにする -{% note %} - -**Note:** After you configure a mandatory message for {% data variables.product.product_location %}, you cannot change or remove the message. - -{% endnote %} - - メッセージに Markdown チェックボックスを含める場合、ユーザがメッセージを閉じる前に、すべてのチェックボックスを選択する必要があります。 たとえば、必須メッセージに利用規約を含める場合、各ユーザにチェックボックスを選択して、ユーザが利用規約を読んだことを確認するように要求できます。 ユーザに必須メッセージが表示されるたびに、監査ログイベントが作成されます。 イベントには、ユーザが表示したメッセージのバージョンが含まれます。 詳しい情報については、「[監査されたアクション](/admin/user-management/audited-actions)」を参照してください。 +{% note %} + +**Note:** If you change the mandatory message for {% data variables.product.product_location %}, users who have already acknowledged the message will not see the new message. + +{% endnote %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} diff --git a/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md b/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md index 9b0df9d8d1..aafa404c1e 100644 --- a/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-security/about-secret-scanning.md @@ -45,7 +45,7 @@ Service providers can partner with {% data variables.product.company_short %} to {% data variables.product.prodname_secret_scanning_caps %} は、{% data variables.product.prodname_GH_advanced_security %} の一環として、Organization が所有するリポジトリ全てで使用できます。 ユーザ所有のリポジトリでは使用できません。 {% endif %} -リポジトリの管理者または Organization のオーナーは、Organization が所有する{% if currentVersion == "free-pro-team@latest" %}プライベートな{% endif %}リポジトリで {% data variables.product.prodname_secret_scanning %} を有効化できます。 全てのリポジトリ、または Organization 内の全ての新しいリポジトリに対して、{% 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)」および「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 +リポジトリの管理者または Organization のオーナーは、Organization が所有する{% if currentVersion == "free-pro-team@latest" %}プライベートな{% endif %}リポジトリで {% data variables.product.prodname_secret_scanning %} を有効化できます。 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data variables.product.prodname_secret_scanning %}が有効化されている{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリにコミットをプッシュすると、{% data variables.product.prodname_dotcom %} はコミットの内容をスキャンしてシークレットを探します。 diff --git a/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md index 51ace64ad1..96f48a1cb3 100644 --- a/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md +++ b/translations/ja-JP/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md @@ -70,4 +70,4 @@ topics: ### 参考リンク -- 「[Organization のセキュリティと分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」 +- 「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」 diff --git a/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md b/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md index 88a106c919..d97b58d93e 100644 --- a/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md +++ b/translations/ja-JP/content/code-security/secure-coding/configuring-code-scanning.md @@ -1,8 +1,8 @@ --- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' +title: コードスキャンを設定する +intro: '{% data variables.product.prodname_dotcom %} がプロジェクトのコードをスキャンして脆弱性やエラーを検出する方法を設定できます。' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' +permissions: 'リポジトリへの書き込み権限を持つユーザは、リポジトリの {% data variables.product.prodname_code_scanning %} を設定できます。' miniTocMaxHeadingLevel: 4 redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning @@ -11,15 +11,15 @@ versions: enterprise-server: '>=3.0' github-ae: '*' topics: - - security + - セキュリティ --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### About {% data variables.product.prodname_code_scanning %} configuration +### {% data variables.product.prodname_code_scanning %} の設定について -You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." +You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. {% data variables.product.prodname_actions %} に関する詳しい情報については、「[{% data variables.product.prodname_actions %} について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。 For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}. @@ -29,33 +29,41 @@ Before you can configure {% data variables.product.prodname_code_scanning %} for {% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. -### Editing a {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} は、リポジトリの _.github/workflows_ ディレクトリにワークフローファイルを保存します。 You can find a workflow you have added by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. リポジトリで、編集したいワークフローファイルにアクセスします。 +1. ファイルビューの右上隅の {% octicon "pencil" aria-label="The edit icon" %}をクリックしてワークフローエディタを開きます。 ![ワークフローファイルの編集ボタン](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. ファイルを編集したら、[**Start commit**] をクリックして、[Commit changes] フォームに入力します。 現在のブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択できます。 ![codeql.yml ワークフローの更新をコミットする](/assets/images/help/repository/code-scanning-workflow-update.png) For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -### Configuring frequency +### 頻度を設定する -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +スケジュール設定されているときや、リポジトリで特定のイベントが発生したときに、コードをスキャンできます。 -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +リポジトリへのプッシュごと、およびプルリクエストが作成されるたびにコードをスキャンすることで、開発者がコードに新しい脆弱性やエラーをもたらすことを防ぎます。 スケジュールに従ってコードをスキャンすると、開発者がリポジトリを積極的に維持していない場合でも、{% data variables.product.company_short %}、セキュリティ研究者、コミュニティが発見した最新の脆弱性とエラーが通知されます。 -#### Scanning on push +#### プッシュ時にスキャンする -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +デフォルトのワークフローを使用する場合、{% data variables.product.prodname_code_scanning %} は、イベントによってトリガーされるスキャンに加えて、リポジトリ内のコードを週に1回スキャンします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#on)」を参照してください。 -#### Scanning pull requests +If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +{% note %} -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below. + +{% endnote %} + +#### プルリクエストをスキャンする + +The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)」を参照してください。 + +`pull_request` イベントに関する詳しい情報については、「"[{% data variables.product.prodname_actions %}のためのワークフローの構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)」を参照してください。 + +If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." #### Avoiding unnecessary scans of pull requests @@ -74,7 +82,7 @@ on: {% note %} -**Notes** +**注釈** * `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." * For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. @@ -83,17 +91,17 @@ on: For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -#### Scanning on a schedule +#### スケジュールに従ってスキャンする -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`pull_request` イベントを使用して、プルリクエストの `HEAD` コミットでコードスキャンをトリガーします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onschedule)」を参照してください。 {% note %} -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. +**注釈**: {% data variables.product.prodname_dotcom %} は、デフォルトのブランチのワークフローにあるスケジュール設定されたジョブのみを実行します。 他のブランチのワークフローでスケジュールを変更しても、ブランチをデフォルトブランチにマージするまで影響はありません。 {% endnote %} -#### Example +#### サンプル The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. @@ -112,7 +120,7 @@ This workflow scans: * Every pull request to the default branch * The default branch every Monday at 14:20 UTC -### Specifying an operating system +### オペレーティングシステムを指定する If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} @@ -127,7 +135,7 @@ jobs: {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% data variables.product.prodname_code_scanning_capc %} は、macOS、Ubuntu、Windows の最新バージョンをサポートしています。 Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." {% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} @@ -162,7 +170,7 @@ If your workflow does not contain a matrix called `language`, then {% data varia languages: cpp, csharp, python ``` {% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies +### 追加のクエリを実行する For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: @@ -204,11 +212,11 @@ jobs: ``` {% endif %} -### Running additional queries +### 追加のクエリを実行する {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. +1つ以上のクエリスイートを追加するには、設定ファイルに `queries` セクションを追加します。 If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. {% raw %} ``` yaml @@ -220,11 +228,11 @@ To add one or more queries, add a `with: queries:` entry within the `uses: githu ``` {% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +設定ファイルでこれらを指定して、追加のクエリスイートを実行することもできます。 クエリスイートはクエリのコレクションであり、通常は目的または言語ごとにグループ化されています。 {% data reusables.code-scanning.codeql-query-suites %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. 設定ファイルの例については、「[Example configuration files](#example-configuration-files)」を参照してください。 In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. @@ -238,11 +246,11 @@ In the following example, the `+` symbol ensures that the specified additional q ``` {% endraw %} -### Using a custom configuration file +### サードパーティのコードスキャンツールを使用する As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. +In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. この例では、設定ファイル _./.github/codeql/codeql-config.yml_ を読み込みます。 ``` yaml - uses: github/codeql-action/init@v1 @@ -279,11 +287,11 @@ Optionally, you can give each array element a name, as shown in the example conf For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. -#### Disabling the default queries +#### デフォルトのクエリを無効にする -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +カスタムクエリのみを実行する場合は、構成ファイルに `disable-default-queries: true` を追加して、デフォルトのセキュリティクエリを無効にすることができます。 -#### Specifying directories to scan +#### スキャンするディレクトリを指定する For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. @@ -297,27 +305,27 @@ paths-ignore: {% note %} -**Note**: +**ノート**: -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. 詳細については、「[{% 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. たとえば、`foo/**`、`**/foo`、および `foo/**/bar` はすべて使用できる構文ですが、`**foo` は使用できません。 ただし、例に示すように、単一の * を他の文字と一緒に使用できます。 You'll need to quote anything that contains a `*` character. {% endnote %} -For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. ビルドからディレクトリを除外するために使用するコマンドは、ビルドシステムによって異なります。 For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +特定のディレクトリのコードを変更すると、monorepo の一部をすばやく分析できます。 ビルドステップでディレクトリを除外し、ワークフローファイルで [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) の`paths-ignore` および `paths` キーワードを使用する必要があります。 -#### Example configuration files +#### 設定ファイルの例 {% data reusables.code-scanning.example-configuration-files %} -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages +### コンパイルされた言語の {% data variables.product.prodname_code_scanning %} を設定する {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} {% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)." -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} +### {% data variables.product.prodname_code_scanning %} 用の設定ファイルを作成できます。 -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)." +{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. ワークフローに `upload-sarif` アクションを追加することで、{% data variables.product.prodname_dotcom %} のサードパーティツールからのコード分析を表示できます。 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/code-security/secure-coding/uploading-a-sarif-file-to-github)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/secure-coding/index.md b/translations/ja-JP/content/code-security/secure-coding/index.md index 2021d48c36..e242d6a4f9 100644 --- a/translations/ja-JP/content/code-security/secure-coding/index.md +++ b/translations/ja-JP/content/code-security/secure-coding/index.md @@ -1,7 +1,7 @@ --- title: コード内のセキュリティの脆弱性とエラーを検出する shortTitle: Secure coding -intro: 'Keep your code secure by using secret scanning to identify and fix potential security vulnerabilities and other errors in your code.' +intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code diff --git a/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md index 8f1547b4c4..a294bde524 100644 --- a/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ja-JP/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md @@ -45,7 +45,14 @@ You need write permission to view a summary of all the alerts for a repository o {% 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) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} +1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) @@ -57,7 +64,11 @@ If you have write permission for a repository, you can view fixed alerts by view 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +{% else %} +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} @@ -110,11 +121,19 @@ To dismiss or delete alerts: 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) +{% else %} + ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) +{% endif %} 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) diff --git a/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md index 228fbffbc5..2109842226 100644 --- a/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md +++ b/translations/ja-JP/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md @@ -32,7 +32,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -72,7 +72,11 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} {% endnote %} @@ -98,7 +102,11 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% else %} + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) +{% endif %} The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. diff --git a/translations/ja-JP/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/ja-JP/content/code-security/security-advisories/editing-a-security-advisory.md index 856b85147c..2dcbb6d5ed 100644 --- a/translations/ja-JP/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/ja-JP/content/code-security/security-advisories/editing-a-security-advisory.md @@ -17,6 +17,8 @@ topics: 相手がクレジットを受け入れると、そのユーザのユーザ名がセキュリティアドバイザリの [Credits] セクションに表示されます。 リポジトリへの読み取りアクセスを持つユーザは、アドバイザリとそれに対するクレジットを受け入れたユーザを確認することができます。 +If you believe you should be credited for a security advisory, please contact the person who created the advisory and ask them to edit the advisory to include your credit. Only the creator of the advisory can credit you, so please don't contact GitHub Support about credits for security advisories. + ### セキュリティアドバイザリを編集する {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/ja-JP/content/code-security/security-overview/exploring-security-alerts.md b/translations/ja-JP/content/code-security/security-overview/exploring-security-alerts.md index 9fbd111c14..70a7c6ef28 100644 --- a/translations/ja-JP/content/code-security/security-overview/exploring-security-alerts.md +++ b/translations/ja-JP/content/code-security/security-overview/exploring-security-alerts.md @@ -11,7 +11,7 @@ versions: ### About the security overview -You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. 詳しい情報については「[OrganizationリポジトリへのTeamのアクセス管理](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository)」を参照してください。 +You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. 詳しい情報については「[OrganizationリポジトリへのTeamのアクセス管理](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)」を参照してください。 The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)." diff --git a/translations/ja-JP/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md index 6e385e03eb..6e7c0a08c1 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md @@ -1,6 +1,6 @@ --- -title: About alerts for vulnerable dependencies -intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.' +title: 脆弱性のある依存関係に関するアラートについて +intro: '{% data variables.product.product_name %} は、リポジトリに影響を与える脆弱性を検出すると、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を送信します。' redirect_from: - /articles/about-security-alerts-for-vulnerable-dependencies - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies @@ -9,91 +9,92 @@ versions: free-pro-team: '*' enterprise-server: '>=3.0' topics: - - security + - セキュリティ --- + -### About vulnerable dependencies +### 脆弱性のある依存関係について {% data reusables.repositories.a-vulnerability-is %} -When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it. +セキュリティ上の脆弱性があるパッケージにコードが依存している場合、この脆弱性のある依存関係により、プロジェクトまたはそれを使用するユーザにさまざまな問題が発生する可能性があります。 -### Detection of vulnerable dependencies +### 脆弱性のある依存関係の検出 - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} は脆弱性のある依存関係を検出し、{% data variables.product.prodname_dependabot_alerts %}を送信します{% else %}{% data variables.product.product_name %} は脆弱性のある依存関係を検出し、次の場合にセキュリティアラート{% endif %}を送信します。 {% if currentVersion == "free-pro-team@latest" %} -- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %} -- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}."{% endif %} -- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +- {% data variables.product.prodname_advisory_database %} に新しい脆弱性が追加されたとき。 詳しい情報については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ脆弱性を参照する](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)」を参照してください。{% else %} +- 新しいアドバイザリデータが {% data variables.product.prodname_dotcom_the_website %} から 1 時間ごとに {% data variables.product.prodname_ghe_server %} に同期されたとき。 アドバイザリデータに関する詳しい情報については、「{% data variables.product.prodname_advisory_database %} のセキュリティ脆弱性を参照する」を参照してください。{% endif %} +- リポジトリの依存関係グラフが変更されたとき。 たとえば、コントリビューターがコミットをプッシュして、依存しているパッケージまたはバージョンを変更したとき{{% if currentVersion == "free-pro-team@latest" %}、またはいずれかの依存関係のコードが変更されたときなどです{% endif %}。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 {% data reusables.repositories.dependency-review %} -For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +{% data variables.product.product_name %} が脆弱性と依存関係を検出できるエコシステムのリストについては、「[サポートされているパッケージエコシステム](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)」を参照してください。 {% note %} -**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use. +**注釈:** マニフェストとロックファイルを最新の状態に保つことが重要です。 依存関係グラフが現在の依存関係とバージョンを正確に反映していない場合、使用する脆弱性のある依存関係のアラートを見逃す可能性があります。 また、使用しなくなった依存関係のアラートを受け取る場合もあります。 {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %} -### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies +### 脆弱性のある依存関係の {% data variables.product.prodname_dependabot %} アラート {% else %} -### Security alerts for vulnerable dependencies +### 脆弱性のある依存対象に関するセキュリティアラート {% endif %} {% data reusables.repositories.enable-security-alerts %} -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} は、_パブリック_リポジトリ内の脆弱性のある依存関係を検出し、デフォルト設定で {% data variables.product.prodname_dependabot_alerts %} を生成します。 プライベートリポジトリの所有者、または管理アクセス権を持つユーザは、リポジトリの依存関係グラフと {% data variables.product.prodname_dependabot_alerts %} を有効にすることで、{% data variables.product.prodname_dependabot_alerts %} を有効化できます。 -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +ユーザアカウントまたは Organization が所有するすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にすることもできます。 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." -{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." +{% data variables.product.product_name %} は依存関係グラフの生成をすぐに開始し、脆弱性のある依存関係が特定されるとすぐにアラートを生成します。 グラフは通常数分以内に入力されますが、多くの依存関係を持つリポジトリの場合は時間がかかる場合があります。 詳しい情報については、「[プライベートリポジトリのデータ使用を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)」を参照してください。 {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)." +When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. アラートには、プロジェクト内で影響を受けるファイルへのリンクと、修正バージョンに関する情報が含まれています。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。 詳しい情報については、「[脆弱性のある依存関係に対する通知を設定する](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)」を参照してください。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +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. 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。 {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. +When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. {% endif %} {% warning %} -**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary. +**注釈**: {% data variables.product.product_name %} のセキュリティの機能は、すべての脆弱性を捕捉するものではありません。 当社は常に脆弱性データベースを更新し、最新の情報でアラートを生成するよう努力していますが、一定の期間内にすべてをの問題を把握したり、既知の脆弱性について通知したりすることはできません。 これらの機能は、それぞれの依存関係の潜在的な脆弱性やその他の問題に関する人によるレビューを置き換えるものではなく、必要な場合にはセキュリティサービスによるコンサルティングや、総合的な脆弱性レビューを行うことをおすすめします。 {% endwarning %} -### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts +### {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}セキュリティ{% endif %}アラートへのアクセス -You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +特定のプロジェクト{% if currentVersion == "free-pro-team@latest" %}に影響を与えるすべてのアラートは、リポジトリの [Security] タブ{% endif %}またはリポジトリの依存関係グラフで確認できます。{% if currentVersion == "free-pro-team@latest" %}詳細については、「[リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」を参照してください。{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. {% data variables.product.prodname_dependabot_alerts %} を、自分が所有または管理者権限を持っているリポジトリで作業している追加のユーザや Team に表示することもできます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. +デフォルトでは、影響を受けるリポジトリで管理者権限を持つ人々にセキュリティアラートが送られます。 {% data variables.product.product_name %} は、特定のリポジトリに対して特定された脆弱性を公表することはありません。 {% endif %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)."{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)." +{% if currentVersion == "free-pro-team@latest" %} +You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. 詳しい情報については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ脆弱性を参照する](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)」を参照してください。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -### Further reading +### 参考リンク -- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} +- 「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」 +- [リポジトリ内の脆弱な依存関係を表示・更新する](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository) +- [{% data variables.product.product_name %} によるデータの利用方法と保護方法を理解する](/categories/understanding-how-github-uses-and-protects-your-data){% endif %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md index 89dbd60d06..36c3ccdc8b 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/about-dependabot-version-updates.md @@ -12,8 +12,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### {% data variables.product.prodname_dependabot_version_updates %} について {% data variables.product.prodname_dependabot %} は、依存関係を維持する手間を省きます。 これを使用して、リポジトリが依存するパッケージおよびアプリケーションの最新リリースに自動的に対応できるようにすることができます。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md index 3f516de9cb..2f24adfc62 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/about-the-dependency-graph.md @@ -1,5 +1,5 @@ --- -title: About the dependency graph +title: 依存関係グラフについて intro: 'You can use the dependency graph to identify all your project''s dependencies. The dependency graph supports a range of popular package ecosystems.' redirect_from: - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph @@ -9,19 +9,20 @@ versions: topics: - repositories --- + -### Dependency graph availability +### 依存関係グラフの利用 The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### 依存関係グラフについて The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: -- Dependencies, the ecosystems and packages it depends on +- 依存関係、エコシステム、それが依存しているパッケージ - Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. @@ -30,65 +31,65 @@ When you push a commit to {% data variables.product.product_name %} that changes When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -### Dependencies included +### 含まれる依存関係 -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +依存関係グラフには、サポートされているエコシステムについてマニフェストおよびロックファイル、または同等のもので詳細に定義されているリポジトリの依存関係がすべて含まれています。 これは以下のものが含まれます。 -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- マニフェストまたはロックファイルで明示的に定義されている、直接依存関係 +- 直接依存関係の間接依存関係。推移的な依存関係、または下位の依存関係とも言う。 -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. 最も信頼性の高いグラフを得るには、ロックファイル (または同等のもの) を使用してください。直接および間接の依存関係のうち現在どのバージョンを使用しているかが正確に定義されているからです。 If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. {% if currentVersion == "free-pro-team@latest" %} ### Dependents included For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} -### Using the dependency graph +### 依存関係グラフの使用 -You can use the dependency graph to: +依存関係グラフを使用する目的は、次のとおりです。 -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} +- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. 詳しい情報については、「[リポジトリの依存関係を調べる](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} +- Organization のリポジトリで使用されている依存関係のサマリーを 1 つのダッシュボードで確認すること。 詳細は「[Organization のインサイトを表示する](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)」を参照してください。{% endif %} +- リポジトリの脆弱な依存関係を表示・更新すること。 For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} - See information about vulnerable dependencies in pull requests. 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 %} -### Enabling the dependency graph +### 依存関係グラフの有効化 -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. 依存関係グラフは、パブリックリポジトリに対しては常に自動的に生成され、プライベートリポジトリに対しては有効化を選択することができます。 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" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. 詳しい情報については、「[{% data variables.product.prodname_ghe_server %}の脆弱性のある依存関係に関するセキュリティアラートの有効化](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。 {% endif %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +依存関係グラフを初めて有効化すると、サポートされているエコシステムのマニフェストおよびロックファイルがすぐに解析されます。 グラフは通常数分以内に入力されますが、多くの依存関係を持つリポジトリの場合は時間がかかる場合があります。 Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. -### Supported package ecosystems +### サポートされているパッケージエコシステム -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +推奨されるフォーマットでは、直接および間接の依存関係すべてに使用されるバージョンを明示的に定義しています。 これらのフォーマットを使用したほうが、依存関係グラフは正確になります。 It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| パッケージマネージャー | 言語 | 推奨されるフォーマット | サポートされているすべてのフォーマット | +| ------------ | ---------------------- | -------------------------------------------------- | -------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET 言語 (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`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`、`Gemfile`、`*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`、`yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**メモ:** `setup.py` ファイルで Python の依存関係をリストする場合、プロジェクトの依存関係すべてを解析してリストすることはできない場合があります。 {% endnote %} -### Further reading +### 参考リンク -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia +- Wikipedia の「[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)」 - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- [Organization のインサイトを表示する](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization) +- [リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md index ca7fb315e9..da3c28d5ac 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md @@ -11,8 +11,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### *dependabot.yml* ファイルについて {% data variables.product.prodname_dependabot %} の設定ファイルである *dependabot.yml* では YAML 構文を使用します。 YAMLについて詳しくなく、学んでいきたい場合は、「[Learn YAML in five minutes (5分で学ぶYAML)](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)」をお読みください。 @@ -323,7 +321,7 @@ updates: {% note %} -**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. 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-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." +**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." {% endnote %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md index 0d63effa62..c099b08736 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md @@ -49,7 +49,7 @@ topics: 個別のリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効または無効にできます（下記参照）。 -ユーザアカウントまたは 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)」を参照してください。 +ユーザアカウントまたは Organization が所有するすべてのリポジトリの {% data variables.product.prodname_dependabot_security_updates %} を有効または無効にすることもできます。 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data variables.product.prodname_dependabot_security_updates %} には特定のリポジトリ設定が必要です。 詳しい情報については、「[サポートされているリポジトリについて](#supported-repositories)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md index 51e6db2a89..75d3b73c8f 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md @@ -16,7 +16,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} がリポジトリ内にある脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} アラートを生成し、リポジトリの [Security] タブに表示します。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。{% else %}{% data variables.product.product_name %} がリポジトリ内の脆弱性のある依存関係を検出すると、セキュリティアラートを送信します。{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} は、すべてのパブリックリポジトリでデフォルト設定で有効になっています。 {% data variables.product.prodname_dependabot_alerts %} の場合、デフォルト設定では、特定の脆弱性ごとにグループ化された {% data variables.product.prodname_dependabot_alerts %} をメールで受信します。 {% endif %} -{% if currentVersion == "free-pro-team@latest" %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/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)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/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" %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/customizing-dependency-updates.md index 84c5a7b520..ada26b3e15 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/customizing-dependency-updates.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/customizing-dependency-updates.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### 依存関係の更新のカスタマイズについて バージョン更新を有効にしてから、*dependabot.yml* ファイルにさらにオプションを追加することで、{% data variables.product.prodname_dependabot %} が依存関係を維持する方法をカスタマイズできます。 たとえば、次のような方法を使用します。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md index 5fbb9d1813..9529f56dca 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md @@ -12,8 +12,6 @@ topics: -{% data reusables.dependabot.beta-note-no-link %} - ### 依存関係のバージョン更新について {% data variables.product.prodname_dependabot_version_updates %} を有効にするには、リポジトリの `.github` ディレクトリにある *dependabot.yml* 構成ファイルをチェックします。 {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. 更新するパッケージマネージャーの依存関係ごとに、パッケージマニフェストファイルの場所と、それらのファイルにリストされている依存関係の更新をチェックする頻度を指定する必要があります。 For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -97,32 +95,32 @@ updates: 以下の *dependabot.yml* ファイルの例には、一部の依存関係の更新を無効にし、他の更新を続行できるようにするさまざまな方法が含まれています。 ```yaml -# Docker で無効および npm で制限された -# 更新を含む dependabot.yml ファイル +# dependabot.yml file with updates +# disabled for Docker and limited for npm version: 2 updates: - # Dockerfile の構成 + # Configuration for Dockerfile - package-ecosystem: "docker" directory: "/" schedule: interval: "weekly" - # Docker 依存関係のすべてのプルリクエストを無効にする + # Disable all pull requests for Docker dependencies open-pull-requests-limit: 0 - # npm の構成 + # Configuration for npm - package-ecosystem: "npm" directory: "/" schedule: interval: "daily" - # 「@dependabot ignore」コマンドを使用して作成された無視指定を上書きする + # Overwrite any ignores created using `@dependabot ignore` commands ignore: - # 「aws」で始まるパッケージの更新を無視する - # ワイルドカードを 0 文字以上の任意の文字に一致させる + # Ignore updates to packages that start with 'aws' + # Wildcards match zero or more arbitrary characters - dependency-name: "aws*" - # 「express」パッケージの更新を無視する + # Ignore some updates to the 'express' package - dependency-name: "express" - # 4.x および 5.x の新しいバージョンのみを無視する + # Ignore only new versions for 4.x and 5.x versions: ["4.x", "5.x"] ``` diff --git a/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md index e78c5bb725..a24d00389e 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md @@ -74,7 +74,7 @@ Any direct and indirect dependencies that are specified in the repository's mani リポジトリ管理者は、プライベートリポジトリに対して依存関係グラフを有効または無効にすることができます。 -You can also enable or disable the dependency graph for all repositories owned by your user account or organization. 詳しい情報については、「[ユーザーアカウントのセキュリティおよび分析設定を管理する](/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)」を参照してください。 +You can also enable or disable the dependency graph 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -114,7 +114,7 @@ The "Used by" section represents a single package from the repository. If you ha ### 参考リンク - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- [Organization のインサイトを表示する](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization) +- [Organization のインサイトを表示する](/organizations/collaborating-with-groups-in-organizations/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) {% endif %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md index c293799556..886abe5a42 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### {% data variables.product.prodname_dependabot_version_updates %} のアクションについて 多くの場合、アクションはバグ修正と新機能で更新され、自動プロセスの信頼性、速度、安全性が向上しています。 {% data variables.product.prodname_actions %} に対して {% data variables.product.prodname_dependabot_version_updates %} を有効にすると、{% data variables.product.prodname_dependabot %} は、リポジトリの *workflow.yml* ファイル内のアクションへのリファレンスが最新の状態に保たれるようにします。 {% data variables.product.prodname_dependabot %} は、ファイル内のアクションごとに、アクションのリファレンス（通常、アクションに関連付けられているバージョン番号またはコミット ID）を最新バージョンと照合します。 より新しいバージョンのアクションが使用可能な場合、{% data variables.product.prodname_dependabot %} は、ワークフローファイル内のリファレンスを最新バージョンに更新するプルリクエストを送信します。 {% data variables.product.prodname_dependabot_version_updates %} の詳細については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/ja-JP/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md index 7df69dd1bf..7cb54e70d8 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### {% data variables.product.prodname_dependabot %} によって監視されている依存関係を表示する バージョン更新を有効にした後、リポジトリの依存関係グラフの [**{% data variables.product.prodname_dependabot %}**] タブで、設定が正しいかどうかを確認できます。 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md index f3b9c3b4c1..bd8c6d77bf 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### {% data variables.product.prodname_dependabot %} のプルリクエストについて {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md index c251f126d1..40691c8883 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md @@ -11,8 +11,6 @@ topics: - セキュリティ --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot %} errors {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md index fceb45e45e..154afda508 100644 --- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md +++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md @@ -1,6 +1,6 @@ --- -title: Creating a default community health file -intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any public repository owned by the account that does not contain its own file of that type.' +title: デフォルトのコミュニティ健全性ファイルを作成する +intro: 'CONTRIBUTING や CODE_OF_CONDUCT など、デフォルトのコミュニティ健全性ファイルを作成できます。 デフォルトのファイルは、そのような独自ファイルを持たないあらゆるパブリックリポジトリに使用されます。' 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 @@ -9,46 +9,44 @@ versions: free-pro-team: '*' enterprise-server: '*' topics: - - community + - コミュニティ --- -### About default community health files +### デフォルトのコミュニティ健全性ファイルについて -You can add default community health files to the root of a public repository called `.github` that is owned by an organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. +Organization {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}またはユーザアカウント{% endif %}が所有する `.github` というパブリックリポジトリのルートにデフォルトのコミュニティ健全性ファイルを追加できます。 -{% data variables.product.product_name %} will use and display default files for any public repository owned by the account that does not have its own file of that type in any of the following places: -- the root of the repository -- the `.github` folder -- the `docs` folder +{% data variables.product.product_name %}は、次のいずれかの場所にそのタイプの独自のファイルがないアカウントのパブリックリポジトリについては、デフォルトファイルを使用および表示します。 +- リポジトリのルート +- `.github` フォルダ +- `docs` フォルダ -For example, anyone who creates an issue or pull request in a public repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used. +たとえば、独自の CONTRIBUTING ファイルを持たないパブリックリポジトリに Issue やプルリクエストを作成する人は誰でも、デフォルトの CONTRIBUTING ファイルへのリンクが見られます。 リポジトリの独自の `.github/ISSUE_TEMPLATE` フォルダ内に +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}、Issue テンプレートや *config.yml* ファイルなど{% endif %}がある場合、デフォルトの `.github/ISSUE_TEMPLATE` フォルダにあるコンテンツは使用されません。 -Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository. +デフォルトのファイルは `.github` リポジトリにのみ格納されるものであって、クローン、パッケージ、リポジトリ個別のダウンロードには含まれません。 -### Supported file types +### サポートされているファイルの種類 -You can create defaults in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} for the following community health files: +Organization {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} またはユーザアカウント{% endif %} で、次のコミュニティ健全性ファイルを作成できます。 -Community health file | Description ---- | ---{% if currentVersion == "free-pro-team@latest" %} -*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %} -*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% if currentVersion == "free-pro-team@latest" %} -*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %} -Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% if currentVersion == "free-pro-team@latest" %} -*SECURITY.md* | A SECURITY file gives instructions for how to responsibly report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/articles/adding-a-security-policy-to-your-repository)."{% endif %} -*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)." +| コミュニティ健全性ファイル | 説明 | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| *CODE_OF_CONDUCT.md* | CODE_OF_CONDUCT ファイルは、コミュニティへの関わり方についての基準を定義します。 詳しい情報については、「[プロジェクトへの行動規範の追加](/articles/adding-a-code-of-conduct-to-your-project/)」を参照してください。{% endif %} +| *CONTRIBUTING.md* | CONTRIBUTING ファイルは、人々がプロジェクトにどのように貢献すべきかを伝えます。 詳しい情報については、「[リポジトリコントリビューターのためのガイドラインを定める](/articles/setting-guidelines-for-repository-contributors/)」を参照してください。{% if currentVersion == "free-pro-team@latest" %} +| *FUNDING.yml* | FUNDING ファイルは、あなたのオープンソースプロジェクトに対する資金提供のオプションについての認知度を高める目的で、リポジトリにスポンサーボタンを表示するためのものです。 詳細は「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照してください。{% endif %} +| Issue とプルリクエストのテンプレート{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} および *config.yml*{% endif %} | Issue およびプルリクエストのテンプレートは、リポジトリで Issue およびプルリクエストを開くときに含める情報をカスタマイズして標準化します。 詳しい情報については「[Issue およびプルリクエストテンプレートについて](/articles/about-issue-and-pull-request-templates/)」を参照してください。{% if currentVersion == "free-pro-team@latest" %} +| *SECURITY.md* | SECURITY ファイルには、プロジェクトのセキュリティ脆弱性について責任を持って報告する方法が記載されています。 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/articles/adding-a-security-policy-to-your-repository)」を参照してください。{% endif %} +| *SUPPORT.md* | SUPPORT ファイルは、プロジェクトについて支援を受ける方法を伝えるためのものです。 詳しい情報については"[プロジェクトへのサポートリソースの追加](/articles/adding-support-resources-to-your-project/)"を参照してください。 | -You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded. +デフォルトのライセンスファイルを作成することはできません。 ライセンスファイルは、プロジェクトのクローン時、パッケージ時、またはダウンロード時に含められるよう、個々のリポジトリに追加する必要があります。 -### Creating a repository for default files +### デフォルトのファイル用にリポジトリを作成 {% data reusables.repositories.create_new %} -2. Use the **Owner** drop-down menu, and select the organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} you want to create default files for. - ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png) -3. Type **.github** as the name for your repository, and an optional description. - ![Create repository field](/assets/images/help/repository/default-file-repository-name.png) -4. Make sure the repository status is set to **Public** (a repository for default files cannot be private). - ![Radio buttons to select private or public status](/assets/images/help/repository/create-repository-public-private.png) +2. [**Owner**] ドロップダウンメニューを使用して、デフォルトファイルを作成する Organization またはユーザアカウント{% endif %}を選択します。 ![[Owner] ドロップダウンメニュー](/assets/images/help/repository/create-repository-owner.png) +3. リポジトリの名前として **.github** と入力し、任意で説明を入力します。 ![リポジトリ作成フィールド](/assets/images/help/repository/default-file-repository-name.png) +4. リポジトリのステータスが **Public** に設定されていることを確認してください (デフォルトファイルのリポジトリをプライベートにすることはできません)。 ![プライベートまたはパブリックのステータスを選択するラジオボタン](/assets/images/help/repository/create-repository-public-private.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -7. In the repository, create one of the supported community health files. Issue templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files must be in the root of the repository. For more information, see "[Creating new files](/articles/creating-new-files/)." +7. リポジトリの中に、サポートされているコミュニティ健全性ファイルの 1 つを作成します。 Issue テンプレートとその設定ファイル{% endif %}は、`.github/ISSUE_TEMPLATE` というフォルダ内になければなりません。 その他のサポートされているファイルは、リポジトリのルートにある必要があります。 詳細は「[新しいファイルを作成する](/articles/creating-new-files/)」を参照してください。 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 0f7c420996..cde4c39bcf 100644 --- a/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/authorizing-oauth-apps.md @@ -86,18 +86,18 @@ GitHub Appが`login`パラメータを指定すると、ユーザに対して利 デフォルトでは、レスポンスは以下の形式になります。 - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer Acceptヘッダに応じて、異なる形式でコンテンツを受け取ることもできます。 Accept: application/json - {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} + {"access_token":"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} Accept: application/xml bearer repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} #### 3. アクセストークンを使ったAPIへのアクセス @@ -207,7 +207,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "user" } @@ -304,3 +304,7 @@ OAuthアプリケーションへの認可情報へリンクし、ユーザがア {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} * 「[デバイスフローのエラー](#errors-for-the-device-flow)」 {% endif %} + +### 参考リンク + +- "[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md index aa938f1445..e53fdfdde8 100644 --- a/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ja-JP/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -54,16 +54,18 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ ##### GitHub App Manifest のパラメータ - | 名前 | 種類 | 説明 | - | --------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | - | `name` | `string` | GitHub App の名前。 | - | `url` | `string` | **必須。**GitHub App のホームページ。 | - | `hook_attributes` | `オブジェクト` | GitHub App の webhook の構成。 | - | `redirect_url` | `string` | GitHub App をインストール後にユーザをリダイレクトする完全な URL。 | - | `説明` | `string` | GitHub App の説明。 | - | `public` | `boolean` | GitHub App を公開する場合には `true` に、アプリケーションの所有者のみがアクセスできるようにするには `false` を設定。 | - | `default_events` | `array` | GitHub App がサブスクライブする[イベント](/webhooks/event-payloads)のリスト。 | - | `default_permissions` | `オブジェクト` | GitHub App が必要とする[権限](/rest/reference/permissions-required-for-github-apps)のセット。 オブジェクトのフォーマットでは、キーの権限名 (`issues` など) と、値のアクセスタイプ (`write` など) を使用します。 | + | 名前 | 種類 | 説明 | + | --------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `string` | GitHub App の名前。 | + | `url` | `string` | **必須。**GitHub App のホームページ。 | + | `hook_attributes` | `オブジェクト` | GitHub App の webhook の構成。 | + | `redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %} + | `callback_url` | `string` | A full URL to redirect to after someone authorizes an installation.{% endif %} + | `説明` | `string` | GitHub App の説明。 | + | `public` | `boolean` | GitHub App を公開する場合には `true` に、アプリケーションの所有者のみがアクセスできるようにするには `false` を設定。 | + | `default_events` | `array` | GitHub App がサブスクライブする[イベント](/webhooks/event-payloads)のリスト。 | + | `default_permissions` | `オブジェクト` | GitHub App が必要とする[権限](/rest/reference/permissions-required-for-github-apps)のセット。 オブジェクトのフォーマットでは、キーの権限名 (`issues` など) と、値のアクセスタイプ (`write` など) を使用します。 | `hook_attributes` オブジェクトは、以下のキーを持っています。 @@ -96,7 +98,10 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -111,10 +116,11 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ }) ``` + この例では、ウェブページ上に Organization アカウントに対して `POST` リクエストをトリガするボタンがあるフォームを使用します。 `ORGANIZATION` は、アプリケーションを作成する場所の Organization アカウントの名前に置き換えます。 ```html -
+ Create a GitHub App Manifest:
@@ -127,7 +133,10 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -147,11 +156,11 @@ GitHub App Manifest フローを実装するには、以下の 3 つのステッ **Create GitHub App** をクリックすると、GitHub はコードパラメータに一時的 `code` を付けて `redirect_url` にリダイレクトして戻します。 例: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 `state` パラメータを指定した場合、`redirect_url` にもそのパラメータが表示されます。 例: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 #### 3. 一時コードをやり取りして、アプリケーションの構成を取得する 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 95686b8889..2fd44551e1 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 @@ -22,9 +22,15 @@ topics: 以下の URL は、説明とコールバック URL が事前設定された、`octocat-github-app` という新しい公開アプリケーションを作成します。 また、この URL は`checks` の読み取りおよび書き込み権限を選択し、`check_run` および `check_suite` webhook イベントにサブスクライブし、インストール時にユーザの認可 (OAuth) をリクエストするオプションを選択します。 - ``` - {% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite - ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} +``` +{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite +``` +{% else %} +``` +{% 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 +``` +{% endif %} 使用可能なクエリパラメータ、権限、およびイベントの完全なリストを、以下のセクションに記載します。 @@ -34,8 +40,9 @@ topics: | -------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | `string` | {% data variables.product.prodname_github_app %} の名前。 アプリケーションには簡潔で明快な名前を付けましょう。 アプリケーションの名前は、既存の GitHub ユーザと同じ名前にできません。ただし、その名前があなた自身のユーザ名や Organization 名である場合は例外です。 インテグレーションが動作すると、ユーザインターフェース上にアプリケーション名のスラッグが表示されます。 | | `description` | `string` | {% data variables.product.prodname_github_app %} の説明。 | - | `url` | `string` | {% data variables.product.prodname_github_app %} のホームページの完全な URL。 | - | `callback_url` | `string` | インストールの承認後にリダイレクトする完全な URL。 この URL は、アプリケーションがユーザからサーバへのリクエストを識別して承認する必要がある場合に使用されます。 | + | `url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} + | `callback_url` | `string` | インストールの承認後にリダイレクトする完全な URL。 This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} | `request_oauth_on_install` | `boolean` | アプリケーションが OAuth フローを使用してユーザを認可する場合、このオプションを `true` にして、インストール時にアプリケーションを認可し、ステップを省略するように設定できます。 このオプションを選択した場合、`setup_url` が利用できなくなり、アプリケーションのインストール後はあなたが設定した `callback_url` にリダイレクトされます。 | | `setup_url` | `string` | {% data variables.product.prodname_github_app %} アプリケーションをインストール後に追加セットアップが必要な場合に、リダイレクトする完全な URL。 | | `setup_on_update` | `boolean` | `true` に設定すると、たとえばリポジトリが追加や削除された後など、インストールしたアプリケーションが更新された場合に、ユーザをセットアップ URL にリダイレクトします。 | @@ -43,7 +50,7 @@ topics: | `webhook_url` | `string` | webhook イベントペイロードを送信する完全な URL。 | | `webhook_secret` | `string` | webhook を保護するためのシークレットを指定できます。 詳細は「[webhook を保護する](/webhooks/securing/)」を参照。 | | `events` | `array of strings` | webhook イベント. 一部の webhook イベントでは、新しい {% data variables.product.prodname_github_app %} を登録する際、イベントを選択するために`read` または `write` 権限が必要です。 利用可能なイベントと、それに必要な権限については、「[{% data variables.product.prodname_github_app %} webhook イベント](#github-app-webhook-events)」セクションを参照してください。 クエリ文字列では、複数のイベントを選択できます。 たとえば、`events[]=public&events[]=label` とできます。 | - | `domain` | `string` | コンテンツ参照の URL。 | + | `ドメイン` | `string` | コンテンツ参照の URL。 | | `single_file_name` | `string` | これは、アプリケーションが任意のリポジトリの単一のファイルにアクセスできるようにするための、スコープの狭い権限です。 `single_file` 権限を `read` または `write` に設定すると、このフィールドは {% data variables.product.prodname_github_app %} が扱う単一のファイルへのパスを指定します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}複数のファイルを扱う必要がある場合、以下の `single_file_paths` を参照してください。 {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} | `single_file_paths` | `array of strings` | アプリケーションが、リポジトリ内の指定した最大 10 ファイルにアクセスできるようにします。 `single_file` 権限を `read` または `write` に設定すると、この配列は {% data variables.product.prodname_github_app %} が扱う最大 10 個のファイルへのパスを格納できます。 これらのファイルには、それぞれ別々の権限があたえられるでのではなく、すべて `single_file` が設定したものと同じ権限が与えられます。 2 つ以上のファイルが設定されている場合、API は `multiple_single_files=true` を返し、それ以外の場合は `multiple_single_files=false` を返します。{% endif %} 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 50569eaf15..2e2223a359 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 @@ -845,7 +845,7 @@ end **A:** 以下のエラーが表示される場合、`initiate_check_run` と `take_requested_action` メソッドのいずれかのリポジトリでチェックアウトを削除していません。 ```shell - 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:v1.9b2080277016f797074c4debd350745f4257f8dd@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: ``` コードを `server.rb` ファイルと比較し、`initiate_check_run` および `take_requested_action` メソッドと同じコードがあることを確認してください。 diff --git a/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 528f58b25c..4d110662cd 100644 --- a/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -94,9 +94,9 @@ GitHub Appが`login`パラメータを指定すると、ユーザに対して利 ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -106,7 +106,7 @@ GitHub Appが`login`パラメータを指定すると、ユーザに対して利 デフォルトでは、レスポンスは以下の形式になります。 - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer {% endif %} @@ -934,3 +934,11 @@ While most of your API インタラクションのほとんどは、サーバー * [ワークフローの取得](/rest/reference/actions#get-a-workflow) * [ワークフロー利用状況の取得](/rest/reference/actions#get-workflow-usage) {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### 参考リンク + +- "[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md index bc2825dc1c..bd1b906920 100644 --- a/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,9 +42,9 @@ topics: ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" @@ -73,3 +73,11 @@ topics: ユーザからサーバーへの認可トークンを使用する既存の{% data variables.product.prodname_github_app %}は、アプリケーションのオーナーが期限になるユーザトークンをアプリケーションに対して有効化した場合にのみ、この新しいフローの影響を受けます。 既存の{% data variables.product.prodname_github_app %}に対して期限切れになるユーザトークンを有効化するためには、8時間で期限切れになる新しいユーザトークンを再発行するためにOAuthフローを通じてユーザを送信し、リフレッシュトークンを使って新しいアクセストークンとリフレッシュトークンを取得するためのリクエストを発行する必要があります。 詳しい情報については「[GitHub Appのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### 参考リンク + +- "[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md b/translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md index 49700ecf20..7f36831ce7 100644 --- a/translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md +++ b/translations/ja-JP/content/developers/github-marketplace/about-marketplace-badges.md @@ -13,7 +13,7 @@ Certain apps on the {% data variables.product.prodname_marketplace %} have the { - Verified ownership of their domain and has a verified badge on their profile - Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization -- Required two-factor authentication for their organization. 詳しい情報については [Organization で 2 要素認証を要求する](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)を参照してください。 +- Required two-factor authentication for their organization. 詳しい情報については [Organization で 2 要素認証を要求する](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)を参照してください。 ![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png) diff --git a/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md index 0d5911b856..d7eeea471c 100644 --- a/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md +++ b/translations/ja-JP/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -22,8 +22,8 @@ To offer paid plans for your app, the app must be owned by an organization and y 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) 1. Under "Publisher Verification", complete the information in the checklist: - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. - - Ensure that Two-factor authentication is enabled for your organization. 詳しい情報については [Organization で 2 要素認証を要求する](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)を参照してください。 - - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + - Ensure that Two-factor authentication is enabled for your organization. 詳しい情報については [Organization で 2 要素認証を要求する](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)を参照してください。 + - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) diff --git a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md index 053f52d8f9..7b11678fbe 100644 --- a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md +++ b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md @@ -112,6 +112,36 @@ Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` +### Server-to-server tokens + +If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. + +Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps). + +##### 長所 + +- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API). +- Dedicated rate limits that grow with your organization. +- Decoupled from GitHub user identities, so they do not consume any licensed seats. +- Never granted a password, so cannot be directly signed in to. + +##### 短所 + +- Additional setup is needed to create the GitHub App. +- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code. + +##### セットアップ + +1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private. +1. Determine the permissions your GitHub App requires, such as read-only access to repository contents. +1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app). +1. Note your GitHub App `id`. +1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key). +1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization. +1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). +1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). +1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client. + ### マシンユーザ サーバーが複数のリポジトリにアクセスしなければならないのであれば、自動化専用に使われる新しい{% data variables.product.product_name %}アカウントを作成し、SSHキーを添付できます。 この{% data variables.product.product_name %}アカウントは人によって使われることはないので、_マシンユーザ_と呼ばれます。 マシンユーザは、個人リポジトリには[コラボレータ][collaborator]として（読み書きのアクセスを許可）、Organizationのリポジトリには[外部のコラボレータ][outside-collaborator]として（読み書き及び管理アクセスを許可）、あるいは自動化する必要があるリポジトリへのアクセスを持つ[Team][team]に（そのTeamの権限を許可）追加できます。 diff --git a/translations/ja-JP/content/developers/overview/secret-scanning.md b/translations/ja-JP/content/developers/overview/secret-scanning.md index 6c7c95b9d1..60dad326a1 100644 --- a/translations/ja-JP/content/developers/overview/secret-scanning.md +++ b/translations/ja-JP/content/developers/overview/secret-scanning.md @@ -17,12 +17,6 @@ topics: When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/github/administering-a-repository/managing-alerts-from-secret-scanning)」を参照してください。 -{% note %} - -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. - -{% endnote %} - This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. ### The {% data variables.product.prodname_secret_scanning %} process diff --git a/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md b/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md index d1a36843db..856e346d11 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/github-event-types.md @@ -183,6 +183,20 @@ Link: ; rel="next", {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} +### PullRequestReviewEvent + +{% data reusables.webhooks.pull_request_review_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### イベントの`payload`オブジェクト + +| キー | 種類 | 説明 | +| -------------- | -------- | ---------------------------------------- | +| `action` | `string` | 実行されたアクション. `created `になりうる。 | +| `pull_request` | `オブジェクト` | The pull request the review pertains to. | +| `レビュー` | `オブジェクト` | The review that was affected. | + ### PullRequestReviewCommentEvent {% data reusables.webhooks.pull_request_review_comment_short_desc %} @@ -200,6 +214,8 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} +#### イベントの`payload`オブジェクト + | キー | 種類 | 説明 | | -------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `push_id` | `integer` | プッシュの一意の識別子。 | diff --git a/translations/ja-JP/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/securing-your-webhooks.md index 960eb2bb06..dff38748d9 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/securing-your-webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -91,6 +91,6 @@ end{% endif %} * どの実装を使用する場合でも、ハッシュ署名は {% 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 %} で始まり、シークレットトークンのキーとペイロード本体を使用します。 -* プレーンな `==` 演算子を使用することは**お勧めしません**。 [`secure_compare`][secure_compare] のようなメソッドは、「一定時間」の文字列比較を実行します。これは、通常の等式演算子に対する特定のタイミング攻撃を軽減するのに役立ちます。 +* プレーンな `==` 演算子を使用することは**お勧めしません**。 A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 6b3ad28c11..df1517d965 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -19,7 +19,7 @@ versions: Issue やプルリクエストをクローズするように、ディスカッションをクローズする必要はありません。 -リポジトリ管理者またはプロジェクトメンテナがリポジトリのディスカッションを有効にすると、リポジトリにアクセスするすべての人がリポジトリのディスカッションを作成して参加できます。 リポジトリ管理者とプロジェクトメンテナは、リポジトリ内のディスカッションとディスカッションカテゴリを管理し、ディスカッションを固定してディスカッションの可視性を高めることができます。 モデレータとコラボレータは、コメントを回答としてマークしたり、ディスカッションをロックしたり、Issue をディスカッションに変換したりすることができます。 詳細は「[Organization のリポジトリ権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)」を参照してください。 +リポジトリ管理者またはプロジェクトメンテナがリポジトリのディスカッションを有効にすると、リポジトリにアクセスするすべての人がリポジトリのディスカッションを作成して参加できます。 リポジトリ管理者とプロジェクトメンテナは、リポジトリ内のディスカッションとディスカッションカテゴリを管理し、ディスカッションを固定してディスカッションの可視性を高めることができます。 モデレータとコラボレータは、コメントを回答としてマークしたり、ディスカッションをロックしたり、Issue をディスカッションに変換したりすることができます。 詳細は「[Organization のためのリポジトリ権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)」を参照してください。 リポジトリのディスカッションの管理の詳細については、「[リポジトリでのディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)」を参照してください。 diff --git a/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md index cd6badeba9..6a30032357 100644 --- a/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -29,7 +29,7 @@ Issue のオープンおよびディスカッションの相互参照につい Issueは、バグレポートや計画された改善など、プロジェクトの特定の詳細についての議論に役立ちます。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 プルリクエストでは、提案された変更に直接コメントできます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests)及び[プルリクエストへコメントする](/articles/commenting-on-a-pull-request)を参照してください。 -{% data reusables.organizations.team-discussions-purpose %}詳しい情報については「[Team ディスカッションについて](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)」を参照してください。 +{% data reusables.organizations.team-discussions-purpose %}詳しい情報については「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照してください。 ### コントリビューションガイドラインに従う diff --git a/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 8a4da0bff7..2484d3c7f5 100644 --- a/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -21,7 +21,7 @@ versions: リポジトリのトリアージ権限を持つユーザは、コメントを回答としてマークし、役に立たなくなった、またはコミュニティに損害を与えているディスカッションをロックし、アイデアがまだ開発の初期段階にあるときに Issue をディスカッションに変換することで、プロジェクトのディスカッションをモデレートするのに役立ちます。 詳しい情報については、「[ ディスカッションをモデレートする](/discussions/managing-discussions-for-your-community/moderating-discussions)」を参照してください。 -リポジトリの権限レベルおよび {% data variables.product.prodname_discussions %} に関する詳しい情報については、「[Organization のリポジトリの権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)」を参照してください。 +リポジトリの権限レベルおよび {% data variables.product.prodname_discussions %} に関する詳しい情報については、「[Organization のリポジトリの権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)」を参照してください。 ### ステップ 3: 上位コントリビューターのアクセス権限レベルを変更する diff --git a/translations/ja-JP/content/discussions/index.md b/translations/ja-JP/content/discussions/index.md index 2c05f15c6c..6a71436caf 100644 --- a/translations/ja-JP/content/discussions/index.md +++ b/translations/ja-JP/content/discussions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /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 changelog: - label: 'discussions' + label: 'ディスカッション' product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index b0ea3d575c..169d87e7a5 100644 --- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -12,7 +12,7 @@ versions: {% data reusables.discussions.about-discussions %}ディスカッションに関する詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。 -Organization のオーナーは、Organization が所有するリポジトリのディスカッションを作成するために必要な権限を選択できます。 詳しい情報については、「[Organization 内のリポジトリのディスカッションの作成を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization)」を参照してください。 +Organization のオーナーは、Organization が所有するリポジトリのディスカッションを作成するために必要な権限を選択できます。 詳しい情報については、「[Organization 内のリポジトリのディスカッションの作成を管理する](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)」を参照してください。 ディスカッションのメンテナとして、コミュニティリソースを作成して、プロジェクト全体の目標に沿ったディスカッションを促し、コラボレータのための親しみやすいオープンフォーラムを維持できます。 コラボレータが従う行動規範またはコントリビューションガイドラインを作成することは、協力的で生産的なフォーラムを促進するのに役立ちます。 コミュニティリソースの作成について詳しくは、「[プロジェクトに行動規範を追加する](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」および 「[リポジトリコントリビューター向けのガイドラインを設定する](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)」を参照してください。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md index 01e91613f8..c8b16a7c3d 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -16,3 +16,7 @@ versions: **ノート：**インストラクターとして、学生のために{% data variables.product.prodname_dotcom %}のアカウントを作成することはできません。 学生は自分の{% data variables.product.prodname_dotcom %}アカウントを作成しなければなりません。 {% endnote %} + +教師は{% data variables.product.prodname_education %}でソフトウェア開発のコースを管理できます。 {% data variables.product.prodname_classroom %}では、{% data variables.product.product_name %}を使用してコードの配布、フィードバックの提供、コースワークの管理が行えます。 詳しい情報については、「[{% data variables.product.prodname_classroom %}でのコースワーク管理](/education/manage-coursework-with-github-classroom)」を参照してください。 + +あなたの学校が {% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_campus_program %} スクールとしてパートナーになっていない場合は、個別に {% data variables.product.prodname_dotcom %} の利用の割引を申請できます。 詳しい情報については、「[学校の勉強での {% data variables.product.prodname_dotcom %} の使用](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)」または「[クラスや勉強での {% data variables.product.prodname_dotcom %} の使用](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)」を参照してください。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md index 556c770423..586b7004cc 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -9,4 +9,6 @@ versions: free-pro-team: '*' --- -{% data variables.product.prodname_dotcom %}Campus Expertsとして、公の場でのスピーチのスキル、テクニカルライティング、コミュニティのリーダーシップ、ソフトウェア開発のスキルを学んでください。 詳しい情報については[Campus Experts](https://education.github.com/students/experts)を参照してください。 +{% data variables.product.prodname_dotcom %}Campus Expertsとして、公の場でのスピーチのスキル、テクニカルライティング、コミュニティのリーダーシップ、ソフトウェア開発のスキルを学んでください。 + +学生のリーダー及び教師に対するトレーニングプログラムについて詳しく学ぶには、[{% data variables.product.prodname_dotcom %}Campus Experts](https://education.github.com/students/experts)及び[ Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md new file mode 100644 index 0000000000..7a43d09ebb --- /dev/null +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Campus Program +intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes: + +- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments +- 弊社の Campus Advisor プログラムと合わせて Git と {% data variables.product.prodname_dotcom %} をマスターするための教師トレーニング +- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners +- {% data variables.product.prodname_student_pack %} のような、プレミアムの {% data variables.product.prodname_education %} の機能への自動化されたアクセス + +Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join. + +詳しい情報については[公式{% data variables.product.prodname_campus_program %}](https://education.github.com/schools)ページを参照してください。 + +あなたの学校が {% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_campus_program %} スクールとしてパートナーになっていない場合は、個別に {% data variables.product.prodname_dotcom %} の利用の割引を申請できます。 詳しい情報については、「[学校の勉強での {% data variables.product.prodname_dotcom %} の使用](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)」または「[クラスや勉強での {% data variables.product.prodname_dotcom %} の使用](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)」を参照してください。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md index 899cdee38d..ce0d941398 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -13,7 +13,7 @@ versions: ### 目次 {% topic_link_in_list /use-github-at-your-educational-institution %} - {% link_in_list /about-github-education %} + {% link_in_list /about-github-campus-program %} {% link_in_list /about-campus-experts %} {% link_in_list /about-campus-advisors %} {% topic_link_in_list /use-github-for-your-schoolwork %} diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index 85132cd5cd..25767de5af 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -59,11 +59,11 @@ versions: ### 対象外の学生ステータス 以下の場合、{% data variables.product.prodname_student_pack %} の対象外となります: -- [{% data variables.product.prodname_dotcom %} キャンパスプログラム](https://education.github.com/schools)の一部ではない非公式の学習プログラムに登録していて、学位または卒業証書を授与するコースに現在在籍していない場合。 +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. - 取得を目指している学位が、現学期で終わる場合。 - 13 歳未満の場合。 -インストラクターは、教室での使用に対して、{% data variables.product.prodname_education %} 割引を適用できます。 コーディングスクールやブートキャンプの学生は、学校が[{% data variables.product.prodname_dotcom %} キャンパスプログラム](https://education.github.com/schools)に参加した場合、{% data variables.product.prodname_student_pack %} を利用できるようになります。 +インストラクターは、教室での使用に対して、{% data variables.product.prodname_education %} 割引を適用できます。 If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). ### 参考リンク 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 92951b641e..823f3c1b6d 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 @@ -17,7 +17,7 @@ redirect_from: {% data reusables.classroom.about-assignments %} -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)」を参照してください。 +1つの課題に取り組むチームの数と、各Teamのメンバーの数を決めることができます。 学生が課題ために作成する各グループは、{% data variables.product.product_name %}のOrganization内のTeamです。 Teamの可視性はシークレットとなります。 {% data variables.product.product_name %}上で作成したTeamは、{% data variables.product.prodname_classroom %}では表示されません。 For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." グループ課題作成の方法を説明する動画については、「[{% data variables.product.prodname_classroom %}の設定の基本](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)」を参照してください。 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 100ad32def..bf234d49f9 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 @@ -20,7 +20,7 @@ redirect_from: クラスルームの作成後、{% data variables.product.prodname_classroom %}はクラスルームにティーチングアシスタント (TA) と管理者を招待するよう促します。 各クラスルームには複数の管理者を置くことができます。 管理者には教師、TA、その他{% data variables.product.prodname_classroom %}でクラスルームの管理をさせたいコース管理者がなることができます。 -TAおよび管理者をクラスルームに招待するには、{% data variables.product.product_name %}のユーザアカウントを、あなたのOrganizationにOrganizationのオーナーとして招待し、クラスルームのURLを共有します。 Organizationのオーナーは、Organizationの任意のクラスルームを管理できます。 詳しい情報については、「[Organizationの権限レベル](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)」および「[Organizationに参加するようユーザを招待する](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)」を参照してください +TAおよび管理者をクラスルームに招待するには、{% data variables.product.product_name %}のユーザアカウントを、あなたのOrganizationにOrganizationのオーナーとして招待し、クラスルームのURLを共有します。 Organizationのオーナーは、Organizationの任意のクラスルームを管理できます。 詳しい情報については、「[Organizationの権限レベル](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)」および「[Organizationに参加するようユーザを招待する](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)」を参照してください クラスルームの使用を終えたら、後でクラスルーム、名簿、課題を参照するためにクラスルームをアーカイブできます。また、クラスルームが今後不要な場合は、クラスルームを削除できます。 @@ -34,7 +34,7 @@ TAおよび管理者をクラスルームに招待するには、{% data variabl ### 必要な環境 -{% data variables.product.prodname_classroom %}でクラスルームを管理するには、{% data variables.product.product_name %}でOrganizationアカウントが必要です。 詳しい情報については、「[{% data variables.product.company_short %}アカウントの種類](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)」および「[新しいOrganizationをゼロから作成する](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)」を参照してください。 +{% data variables.product.prodname_classroom %}でクラスルームを管理するには、{% data variables.product.product_name %}でOrganizationアカウントが必要です。 詳しい情報については、「[{% data variables.product.company_short %}アカウントの種類](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)」および「[新しいOrganizationをゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。 Organizationアカウントのクラスルームを管理するには、Organizationの{% data variables.product.prodname_classroom %}用OAuth Appを認証する必要があります。 詳しい情報については、「[OAuth App を認証する](/github/authenticating-to-github/authorizing-oauth-apps)」を参照してください。 diff --git a/translations/ja-JP/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md index 475803c758..83a2693d43 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository.md @@ -11,6 +11,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - repositories --- {% data reusables.notifications.outbound_email_tip %} @@ -25,7 +27,7 @@ versions: - コミットの一部として変更されたファイル群 - コミットメッセージ -リポジトリへのプッシュに対して受け取るメール通知はフィルタリングできます。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)」{% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications)」を参照してください。 プッシュのメール通知を無効にすることもできます。 詳しい情報については、「[通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}」を参照してください。 +リポジトリへのプッシュに対して受け取るメール通知はフィルタリングできます。 詳しい情報については、% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)」{% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications)」を参照してください。 プッシュのメール通知を無効にすることもできます。 詳しい情報については、「[通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}」を参照してください。 ### リポジトリへのプッシュに対するメール通知の有効化 @@ -33,8 +35,8 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} 5. 最大で 2 個まで、通知の送信先にしたいメールアドレスを空白で区切って入力します。 2 つを超える数のアカウントにメールを送信させたい場合は、メールアドレスの 1 つをグループメールアドレスにしてください。 ![メールアドレスのテキストボックス](/assets/images/help/settings/email_services_addresses.png) -6. 自分のサーバーを運用している場合は、**Secret** トークンでメールの整合性を検証できます。 このトークンは `Approved` ヘッダとしてメールとともに送信されます。 `Approved`ヘッダが、あなたが送信したトークンにマッチすれば、そのメールが {% data variables.product.product_name %} からのものであると信頼できます。 ![メールのシークレットテキストボックス](/assets/images/help/settings/email_services_token.png) -7. **Save settings（設定の保存）**をクリックしてください。 ![設定保存のボタン](/assets/images/help/settings/save_notification_settings.png) +1. 自分のサーバーを運用している場合は、**Approved ヘッダ**を介してメールの整合性を確認できます。 **Approved ヘッダ**は、このフィールドに入力するトークンまたはシークレットであり、メールで送信されます。 メールが `Approved` ヘッダが、送信したトークンにマッチする場合、そのメールが {% data variables.product.product_name %} からのものであると信頼できます。 ![Approved ヘッダのテキストボックスをメールで送信](/assets/images/help/settings/email_services_approved_header.png) +7. [**Setup notifications**] をクリックします。 ![設定通知ボタン](/assets/images/help/settings/setup_notifications_settings.png) ### 参考リンク {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} 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 38223bd4ff..58c55d1125 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 @@ -26,7 +26,7 @@ topics: {% note %} -**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -47,7 +47,7 @@ You can disable all workflows for a repository or set a policy that configures w {% note %} -**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." +**注釈:** Organization に優先ポリシーがあるか、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." {% endif %} diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index cfdbd3bb6d..a443af374d 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -11,7 +11,11 @@ topics: - repositories --- -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)." +### 自動マージについて + +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." + +### Managing auto-merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 8f7b3f2b59..87c6699346 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 @@ -47,6 +47,9 @@ You can also publish an action from a specific release in {% data variables.prod 6. リリースのタイトルと説明を入力します。 ![リリースの説明](/assets/images/help/releases/releases_description.png) 7. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif) 8. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png) +{%- if currentVersion == "free-pro-team@latest" %} +1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} 9. リリースを公開する準備ができている場合は、[**Publish release**] をクリックします。 リリースの作業を後でする場合は、[**Save draft**] をクリックします。 ![[Publish release] と [Save draft] ボタン](/assets/images/help/releases/release_buttons.png) コマンドラインから、またはスクリプトでリリースを自動的に作成することもできます。 詳しい情報については、「[リリース](/rest/reference/repos/#create-a-release)」を参照してください。 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 c7cea9ed12..c8526a2077 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 @@ -106,4 +106,4 @@ Organization owners and repository administrators can only grant access to view ### 参考リンク - 「[リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository)」 -- 「[Organization のセキュリティと分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」 +- 「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」 diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md index c37de9afd2..ac5de5076b 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -16,7 +16,7 @@ topics: この概要は、リポジトリ、オンボードまたはオフボードの独立契約者または従業員へのアクセスを監査し、セキュリティインシデントに効果的に対応するのに役立ちます。 -リポジトリの権限レベルについての詳細は、「[ユーザアカウントのリポジトリ権限レベル](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)」および「[Organization のリポジトリ権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)」を参照してください。 +リポジトリの権限レベルについての詳細は、「[ユーザアカウントのリポジトリの権限レベル](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)」および「[Organization のリポジトリの権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)」を参照してください。 ![アクセス管理の概要](/assets/images/help/repository/manage-access-overview.png) @@ -53,4 +53,4 @@ topics: ### 参考リンク - 「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」 -- 「[Organization の基本レベルの権限の設定](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)」 +- 「[Organization の基本レベルの権限の設定](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)」 diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index 7835ea6ba5..2190dbcb54 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -13,7 +13,7 @@ topics: - repositories --- -An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. 詳細は「[Organization のフォークポリシーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)」を参照してください。 +An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. 詳細は「[Organization のフォークポリシーを管理する](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)」を参照してください。 {% data reusables.organizations.internal-repos-enterprise %} 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 index 72604410c9..190210ca02 100644 --- 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 @@ -4,7 +4,7 @@ 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: '*' - enterprise-server: '>=3.1' + enterprise-server: '>=3.2' topics: - repositories --- @@ -13,7 +13,9 @@ topics: 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. +When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. + +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. ### Renaming a branch diff --git a/translations/ja-JP/content/github/administering-a-repository/renaming-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/renaming-a-repository.md index 6906aa88bf..fc01d15726 100644 --- a/translations/ja-JP/content/github/administering-a-repository/renaming-a-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/renaming-a-repository.md @@ -18,7 +18,7 @@ topics: * Star * フォロワー -プロジェクトサイトに関する詳しい情報については「[{% data variables.product.prodname_pages %}について](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)」を参照してください。 +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Web トラフィックのリダイレクトに加え、前の場所をターゲットにしたすべての `git clone`、`git fetch`、または `git push` 操作は、引き続き新しい場所に対して行われているように機能します。 ただし、混乱を低減するため、既存のローカルクローンが新しいリポジトリ URL を指すよう更新することを強く推奨します。 これを行うには、コマンドラインで `git remote` を使用します。 @@ -30,7 +30,7 @@ For more information, see "[Managing remote repositories](/github/getting-starte {% if currentVersion == "free-pro-team@latest" %} -{% data variables.product.prodname_pages %}サイトを持つリポジトリの名前を変更する場合は、サイトにカスタムドメインを使用することをお勧めします。 これにより、リポジトリの名前を変更してもサイトの URL は影響を受けません。 詳細は「[カスタムドメインおよび{% data variables.product.prodname_pages %}サイトについて](/github/working-with-github-pages/about-custom-domains-and-github-pages)」を参照してください。 +{% data variables.product.prodname_pages %}サイトを持つリポジトリの名前を変更する場合は、サイトにカスタムドメインを使用することをお勧めします。 これにより、リポジトリの名前を変更してもサイトの URL は影響を受けません。 詳細は「[カスタムドメインおよび{% data variables.product.prodname_pages %}サイトについて](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)」を参照してください。 {% endif %} 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 17db68132e..f2dc29b67f 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 @@ -16,7 +16,7 @@ topics: ### リポジトリの可視性の変更について -Organization のオーナーは、リポジトリの可視性を変更する機能を Organization のオーナーのみに制限できます。 詳しい情報については「[Organization 内でリポジトリの可視性の変更を制限する](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)」を参照してください。 +Organization のオーナーは、リポジトリの可視性を変更する機能を Organization のオーナーのみに制限できます。 For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." リポジトリの可視性を変更する前に、次の注意点を確認することをお勧めします。 diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md index e1ac2aaa4c..161f348ee5 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-authentication-to-github.md @@ -55,3 +55,19 @@ IdP を使用して、ブラウザ {% if currentVersion == "github-ae@latest" %} * SSH 接続はファイアウォールとプロキシから許可されない場合がありますが、SSH 経由で {% data variables.product.product_name %} 上のすべてのリポジトリを操作できます。 SSH を使用するには、ローカルマシンで SSH 公開鍵/秘密鍵ペアを生成し、公開鍵を {% data variables.product.product_name %} アカウントに追加する必要があります。 Git を使用して {% data variables.product.product_name %} で認証するたびに、[キーを保存](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)していない限り、SSH キーのパスフレーズの入力を求められます。 詳しい情報については、「[新しい SSH キーを生成して ssh-agent に追加する](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} 個人アクセストークンまたは SSH キーを使用して、SAML シングルサインオンを使用する Organization が所有するリソースにアクセスするには、個人トークンまたは SSH キーも承認する必要があります。 詳しい情報については、[SAML シングルサインオンで利用するために個人アクセストークンを認証する](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」または「[SAML シングルサインオンで使用するために SSH キーを認証する](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### {% data variables.product.company_short %}'s token formats + +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. + +| Token type | Prefix | 詳細情報 | +|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 個人アクセストークン | `ghp_` | [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token) | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | + +{% endif %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/ja-JP/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index fd16a10fde..94a4b9c993 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,47 +1,55 @@ --- -title: About authentication with SAML single sign-on -intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}' +title: SAMLのシングルサインオンでの認証について +intro: 'アイデンティティプロバイダ (IdP) を介して SAML シングルサインオン (SSO) {% endif %}で認証することにより、SAML シングルサインオン (SSO) {% endif %} を使用する Organization の {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %} にアクセスできます。{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} から正常に IdP に認証されたら、Organization のリソースにアクセスさせたい個人アクセストークン、SSH キー、または {% data variables.product.prodname_oauth_app %} を認証する必要があります。{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on versions: free-pro-team: '*' github-ae: '*' +topics: + - sso --- +### SAML SSO での認証について + {% if currentVersion == "github-ae@latest" %} -SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. +SAML SSO を使用すると、Enterprise のオーナーは、SAML IdP から {% data variables.product.product_name %} へのアクセスを一元的に制御して保護できます。 ブラウザで {% data variables.product.product_location %} にアクセスすると、{% data variables.product.product_name %} が認証のために IdP にリダイレクトします。 IdP のアカウントで正常に認証されると、IdP によって {% data variables.product.product_location %} にリダイレクトされます。 {% data variables.product.product_name %} は、IdP からのレスポンスを検証してから、アクセスを許可します。 {% data reusables.saml.you-must-periodically-authenticate %} -If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. +{% data variables.product.product_name %} にアクセスできない場合は、担当の Enterprise のオーナーまたは管理者に {% data variables.product.product_name %} についてお問い合わせください。 {% data variables.product.product_name %} のページの下部にある [**Support**] をクリックすると、Enterprise の連絡先情報を確認することができます。 {% data variables.product.company_short %} および {% data variables.contact.github_support %} は IdP にアクセスできず、認証の問題をトラブルシューティングできません。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. +{% data reusables.saml.dotcom-saml-explanation %}Organization のオーナーは、{% data variables.product.prodname_dotcom %}でユーザアカウントを SAML SSO を使用する Organization に招待できます。これにより、Organization に貢献することができ、{% data variables.product.prodname_dotcom %}の既存の ID とコントリビューションを保持できます。 -When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. +SAML SSO を使用する Organization のリソースにアクセスすると、{% data variables.product.prodname_dotcom %}は認証のために Organization の SAML IdP にリダイレクトします。 IdP でアカウントが正常に認証されると、IdP は{% data variables.product.prodname_dotcom %}に戻り、Organization のリソースにアクセスできます。 {% data reusables.saml.outside-collaborators-exemption %} -If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. +最近ブラウザで Organization の SAML IdP が認証された場合、SAML SSO を使う {% data variables.product.prodname_dotcom %} の Organization へのアクセスは自動的に認可されます。 最近ブラウザで Organization の SAML IdP が認証されていない場合は、Organization にアクセスする前に SAML IdP で認証を受ける必要があります。 {% data reusables.saml.you-must-periodically-authenticate %} -To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. {% data variables.product.prodname_oauth_app %} access tokens are authorized by default. +SAML SSL を要求する Organization 内の保護されたコンテンツにアクセスするために API またはコマンドライン上の Git を利用するには、認可された個人のアクセストークンを HTTPS 経由で使うか、認可された SSH キーを使う必要があります。 -If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +個人のアクセストークンあるいは SSH キーを持っていない場合、コマンドライン用の個人のアクセストークンを作成するか、新しい SSH キーを生成できます。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」または「[新しい SSH キーを生成して ssh-agent へ追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。 -To use a new or existing personal access token or SSH key with an organization that enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +新しい、または既存の個人のアクセストークンか SSH キーを、SAML SSO を使用または要求する Organization で利用するには、SAML SSO Organization で使うためにそのトークンや SSH キーを認可する必要があります。 詳しい情報については、[SAMLシングルサインオンで利用するために個人アクセストークンを認可する](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」または「[SAML シングルサインオンで使用するために SSH キーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。 -You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %}. +### {% data variables.product.prodname_oauth_apps %} と SAML SSO について + +SAML SSO を使用または要求する Organization にアクセスする {% data variables.product.prodname_oauth_app %} を認証するたびにアクティブなSAML セッションが必要です。 + +Enterprise または Organization のオーナーが Organization の SAML SSO を有効化または要求したら、Organization にアクセスするには以前に認可した {% data variables.product.prodname_oauth_app %} を再度認可する必要があります。 {% data variables.product.prodname_oauth_app %} を認可または再認可した {% data variables.product.prodname_oauth_apps %} を確認するには、[{% data variables.product.prodname_oauth_apps %} ページ](https://github.com/settings/applications)にアクセスしてください。 {% endif %} -### Further reading +### 参考リンク -{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} -{% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% if currentVersion == "github-ae@latest" %}- 「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/admin/authentication/about-identity-and-access-management-for-your-enterprise)」{% endif %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md index e9855bb6dc..df8530e078 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/ja-JP/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -36,8 +36,14 @@ topics: ![トークンスコープの選択](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} 7. [**Generate token**] をクリックします。 ![[Generate token] ボタン](/assets/images/help/settings/generate_token.png) -8. {% octicon "clippy" aria-label="The copy to clipboard icon" %}をクリックしてトークンをクリップボードにコピーします。 セキュリティ上の理由により、ページの外に移動すると、再びこのトークンを見ることはできません。{% 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 %} +8. {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again. + {% if currentVersion == "free-pro-team@latest" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) + {% endif %} {% warning %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/ja-JP/content/github/authenticating-to-github/creating-a-strong-password.md index 2aa9d31d8f..8a11ceb0e5 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/creating-a-strong-password.md +++ b/translations/ja-JP/content/github/authenticating-to-github/creating-a-strong-password.md @@ -20,7 +20,7 @@ topics: - [LastPass](https://lastpass.com/) や [1Password](https://1password.com/) などのパスワードマネージャを使用して、15 文字以上のパスワードを生成すること。 - {% data variables.product.product_name %}用に独自のパスワードを生成すること。 {% data variables.product.product_name %} パスワードを他でも使用していて、そのサービスが危険にさらされると、攻撃者や悪意のある者がその情報を使用して {% data variables.product.product_name %} アカウントにアクセスする可能性があります。 - 個人アカウントに 2 要素認証を設定する。 詳しい情報については「[2 要素認証について](/articles/about-two-factor-authentication)」を参照してください。 -- 潜在的なコラボレーターであっても誰であっても、パスワードは決して共有しないでください。 {% data variables.product.product_name %}では一人ひとりが自分の個人アカウントを使用すべきです。 コラボレートする方法の詳しい情報については、「[コラボレーターを個人リポジトリに招待する](/articles/inviting-collaborators-to-a-personal-repository)」、「[共同開発モデルについて](/articles/about-collaborative-development-models/)」、または「[Organization のグループでコラボレーションする](/articles/collaborating-with-groups-in-organizations/)」を参照してください。 +- 潜在的なコラボレーターであっても誰であっても、パスワードは決して共有しないでください。 {% data variables.product.product_name %}では一人ひとりが自分の個人アカウントを使用すべきです。 コラボレートする方法の詳しい情報については、「[コラボレーターを個人リポジトリに招待する](/articles/inviting-collaborators-to-a-personal-repository)」、「[共同開発モデルについて](/articles/about-collaborative-development-models/)」、または「[Organization のグループでコラボレーションする](/organizations/collaborating-with-groups-in-organizations/)」を参照してください。 {% data reusables.repositories.blocked-passwords %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/error-permission-denied-publickey.md b/translations/ja-JP/content/github/authenticating-to-github/error-permission-denied-publickey.md index 6057153d6b..246a832bb3 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/error-permission-denied-publickey.md +++ b/translations/ja-JP/content/github/authenticating-to-github/error-permission-denied-publickey.md @@ -1,69 +1,71 @@ --- title: 'Error: Permission denied (publickey)' -intro: 'A "Permission denied" error means that the server rejected your connection. There could be several reasons why, and the most common examples are explained below.' +intro: '「Permission denied」エラーは、サーバーが接続を却下したことを示します。 原因はいくつか考えられますが、最も一般的な例を説明します。' redirect_from: - /articles/error-permission-denied-publickey versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - ssh --- -### Should the `sudo` command be used with Git? +### `sudo` コマンドを Git で使用すべきか -You should not be using the `sudo` command with Git. If you have a *very good reason* you must use `sudo`, then ensure you are using it with every command (it's probably just better to use `su` to get a shell as root at that point). If you [generate SSH keys](/articles/generating-an-ssh-key) without `sudo` and then try to use a command like `sudo git push`, you won't be using the same keys that you generated. +`sudo` コマンドは Git で使用するべきではありません。 `sudo` を使用しなければならない*特別な理由*がある場合は、各コマンドで使用するようにしてください (その時点で、シェルを root として取得するために `su` を使用するほうがおそらくベターです)。 `sudo` なしで [SSH キー](/articles/generating-an-ssh-key)を使用し、`sudo git push` などのコマンドの使用を試す場合は、生成したのと同じキーを使用しないでしょう。 -### Check that you are connecting to the correct server +### 正しいサーバーに接続していることを確認する -Typing is hard, we all know it. Pay attention to what you type; you won't be able to connect to "githib.com" or "guthub.com". In some cases, a corporate network may cause issues resolving the DNS record as well. +キーボードで入力するというのは骨の折れる作業です。 入力内容に注意を払ってください。「githib.com」や「guthub.com」に接続することはできません。 一部の場合、企業ネットワークによって DNS レコードの解決の問題も発生します。 -To make sure you are connecting to the right domain, you can enter the following command: +正しいドメインに接続していることを確かめるには、以下のコマンドを入力します: ```shell $ ssh -vT git@{% data variables.command_line.codeblock %} -> OpenSSH_8.1p1, LibreSSL 2.7.3 +> OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 > 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. +> debug1: Reading configuration data /etc/ssh_config +> debug1: Applying options for * +> debug1: Connecting to {% data variables.command_line.codeblock %} [IP ADDRESS] port 22. ``` -The connection should be made on port 22{% if currentVersion == "free-pro-team@latest" %}, unless you're overriding settings to use [SSH over HTTPS](/articles/using-ssh-over-the-https-port){% endif %}. +{% if currentVersion == "free-pro-team@latest" %}設定を[HTTPS を介した SSH](/articles/using-ssh-over-the-https-port)を使用するようオーバーライドしていない限り、{% endif %}接続はポート 22で行われるはずです。 -### Always use the "git" user +### 常に「git」ユーザを使用する -All connections, including those for remote URLs, must be made as the "git" user. If you try to connect with your {% data variables.product.product_name %} username, it will fail: +リモート URL 向けを含むすべての接続は、「git」ユーザとして行われる必要があります。 {% data variables.product.product_name %} のユーザ名で接続しようとすると、失敗します: ```shell $ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %} > Permission denied (publickey). ``` -If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/articles/changing-a-remote-s-url/). +接続が失敗し、{% data variables.product.product_name %}のユーザ名でリモート URL を使用している場合は、[「git」ユーザを使用するようリモート URL を変更](/github/getting-started-with-github/managing-remote-repositories)できます。 -You should verify your connection by typing: +以下を入力して接続を確認します: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} > Hi username! You've successfully authenticated... ``` -### Make sure you have a key that is being used +### 使用中のキーを持っていることを確認する {% mac %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +2. プライベートキーを生成し SSH に読み込ませていることを確認します。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7 以前を使用している場合: ```shell - # start the ssh-agent in the background + # バックグラウンドで ssh-agent を起動する $ 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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```shell - # start the ssh-agent in the background + # バックグラウンドでssh-agentを起動する $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add -l -E md5 @@ -71,29 +73,20 @@ $ ssh -T git@{% data variables.command_line.codeblock %} ``` {% else %} ```shell - # start the ssh-agent in the background + # バックグラウンドで ssh-agent を起動する $ 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 %} + $ 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) {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +2. プライベートキーを生成し 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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```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) @@ -109,18 +102,18 @@ $ ssh -T git@{% data variables.command_line.codeblock %} {% linux %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +2. プライベートキーを生成し 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 + # バックグラウンドで ssh-agent を起動する $ 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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```shell - # start the ssh-agent in the background + # バックグラウンドでssh-agentを起動する $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add -l -E md5 @@ -128,28 +121,14 @@ $ ssh -T git@{% data variables.command_line.codeblock %} ``` {% 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 %}. + $ 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) 何もプリントされない場合は、新しい SSH キーを生成して {% 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. +**Tip**: On most systems the default private keys (`~/.ssh/id_rsa` and `~/.ssh/identity`) are automatically added to the SSH authentication agent. プライベートキーを生成し SSH に読み込ませていることを確認します。 -{% 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 %} -> ... +git@{% data variables.command_line.backticks %} への接続を試して、キーが使用されていることを確認することもできます。 > 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 @@ -162,8 +141,21 @@ $ ssh -vT git@{% data variables.command_line.codeblock %} > debug1: No more authentication methods to try. > Permission denied (publickey). ``` + への接続を試して、キーが使用されていることを確認することもできます。 +> 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). + -In that example, we did not have any keys for SSH to use. The "-1" at the end of the "identity file" lines means SSH couldn't find a file to use. Later on, the "Trying private key" lines also indicate that no file was found. If a file existed, those lines would be "1" and "Offering public key", respectively: +この例では、SSH が使用するキーはありませんでした。 「identity file」行の最後の「-1」は、SSH が使用するファイルを見つけることができなかったことを示します。 その後、「Trying private key」の行でもファイルが見つからなかったことが示されています。 ファイルが存在する場合は、これらの行はそれぞれ「1」と「Offering public key」になります。 ```shell $ ssh -vT git@{% data variables.command_line.codeblock %} @@ -175,25 +167,25 @@ $ ssh -vT git@{% data variables.command_line.codeblock %} > debug1: Offering RSA public key: /Users/you/.ssh/id_rsa ``` -### Verify the public key is attached to your account +### 公開鍵がアカウントに添付されていることを確認する -You must provide your public key to {% data variables.product.product_name %} to establish a secure connection. +公開鍵を {% data variables.product.product_name %} に提供して、安全な接続を確立する必要があります。 {% mac %} -1. Open Terminal. -2. Start SSH agent in the background. +1. ターミナルを開きます。 +2. バックグラウンドで SSH エージェントを開始します。 ```shell $ eval "$(ssh-agent -s)" > Agent pid 59566 ``` -3. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +3. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7 以前を使用している場合: ```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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```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) @@ -206,26 +198,25 @@ You must provide your public key to {% data variables.product.product_name %} to {% 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. Open the command line. -2. Start SSH agent in the background. - ```shell +6. SSH キーのリストを、ssh-add コマンドの出力と比較します。 +{% data variables.product.product_name %} の SSH キーのリスト コマンドラインを開きます。 +2. バックグラウンドで SSH エージェントを開始します。 $ ssh-agent -s > Agent pid 59566 ``` -3. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: + コマンドの出力と比較します。 +{% data variables.product.product_name %} の SSH キーのリスト コマンドラインを開きます。 +2. バックグラウンドで SSH エージェントを開始します。 + $ ssh-agent -s + > Agent pid 59566 + +3. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7 以前を使用している場合: ```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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```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) @@ -238,26 +229,27 @@ You must provide your public key to {% data variables.product.product_name %} to {% 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. Open Terminal. -2. Start SSH agent in the background. +6. SSH キーのリストを、ssh-add コマンドの出力と比較します。 +{% data variables.product.product_name %} の SSH キーのリスト ターミナルを開きます。 +2. バックグラウンドで SSH エージェントを開始します。 ```shell $ eval "$(ssh-agent -s)" > Agent pid 59566 ``` -3. Find and take a note of your public key fingerprint. If you're using OpenSSH 6.7 or older: + コマンドの出力と比較します。 +{% data variables.product.product_name %} の SSH キーのリスト ターミナルを開きます。 +2. バックグラウンドで SSH エージェントを開始します。 + ```shell + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + +3. 自分の公開鍵のフィンガープリントを見つけてメモします。 OpenSSH 6.7 より前のバージョンを使用している場合: ```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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```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) @@ -265,15 +257,14 @@ You must provide your public key to {% data variables.product.product_name %} to {% 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) +6. SSH キーのリストを、`ssh-add` コマンドの出力と比較します。 ![{% data variables.product.product_name %} の SSH キーのリスト](/assets/images/help/settings/ssh_key_listing.png) {% endlinux %} -If you don't see your public key in {% data variables.product.product_name %}, you'll need to [add your SSH key to {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account) to associate it with your computer. +{% data variables.product.product_name %} で公開鍵が見つからない場合は、[{% data variables.product.product_name %} に SSH キーを追加](/articles/adding-a-new-ssh-key-to-your-github-account)してコンピュータと関連付ける必要があります。 {% warning %} -**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %}, for further help. An unidentified public key may indicate a possible security concern. For more information, see "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)." +**警告**: 見慣れない SSH キーが {% data variables.product.product_name %} で見つかった場合は、すぐにそれを削除し、さらに支援が必要な場合は {% data variables.contact.contact_support %} に問い合わせてください。 確認できない公開鍵は、潜在的なセキュリティ上の問題を示している可能性があります。 詳細は「[SSH キーをレビューする](/articles/reviewing-your-ssh-keys)」を参照してください。 {% endwarning %} 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 5972726bb1..122dcb8158 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 @@ -193,7 +193,7 @@ topics: | `sponsored_developer_create` | {% 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)」を参照） | | `sponsored_developer_profile_update` | スポンサード開発者のプロフィールを編集するとトリガーされます（「[{% 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` | 承認のために{% 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)」を参照） | -| `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を変更する](/articles/changing-your-sponsorship-tiers)」を参照) | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | | `sponsored_developer_update_newsletter_send` | スポンサーにメールで最新情報を送信したときにトリガーされます (「[スポンサーに連絡する](/articles/contacting-your-sponsors)」を参照) | | `waitlist_invite_sponsored_developer` | 待ちリストから{% 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)」を参照） | | `waitlist_join` | スポンサード開発者になるために待ちリストに参加するとトリガーされます（「[ユーザアカウントに{% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照） | diff --git a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md index ba3e70593d..738aea12fe 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md +++ b/translations/ja-JP/content/github/authenticating-to-github/reviewing-your-ssh-keys.md @@ -1,6 +1,6 @@ --- -title: Reviewing your SSH keys -intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your {% data variables.product.product_name %} account.' +title: SSH キーをレビューする +intro: '認証情報を安全に保つには、SSH キーを定期的に監査し、キーをデプロイし、自分の {% data variables.product.product_name %} アカウントにアクセスする許可されたアプリケーションをレビューしてください。' redirect_from: - /articles/keeping-your-application-access-tokens-safe/ - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/ @@ -9,34 +9,36 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - アイデンティティ + - アクセス管理 --- -You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid. +許可されていない (あるいは侵害された可能性のある) SSH キーを削除することで、攻撃者が以後自分のリポジトリにアクセスすることを防止できます。 有効な既存の SSH キーを承認することもできます。 {% mac %} {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -3. On the SSH Settings page, take note of the SSH keys associated with your account. 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) +3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[**Delete**] をクリックします。 残しておきたい有効な SSH キーがある場合は、[**Approve**] をクリックします。 ![SSH キーのリスト](/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. + **メモ:** Git 操作が失敗したために SSH キーを監査している場合は、 [SSH キー監査エラー](/articles/error-we-re-doing-an-ssh-key-audit)の原因となった未検証のキーが SSH キーのリストで強調表示されます。 {% endtip %} -4. Open Terminal. +4. ターミナルを開きます。 5. {% data reusables.command_line.start_ssh_agent %} -6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +6. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7 以前を使用している場合: ```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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```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) @@ -47,7 +49,7 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an > 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. +7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致していなければなりません 。 {% endmac %} @@ -55,28 +57,28 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -3. On the SSH Settings page, take note of the SSH keys associated with your account. 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) +3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[Delete] をクリックします。 残しておきたい有効な SSH キーがある場合は、[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. + **注釈:** Git 操作が失敗したために SSH キーを監査している場合は、[SSH キー監査エラー] (/articles/error-we-re-doing-an-ssh-key-audit) の原因となった未検証のキーが SSH キーのリストで強調表示されます。 {% endtip %} -4. Open Git Bash. If you're using Git Shell, which is included in {% data variables.product.prodname_desktop %}, open Git Shell and skip to step 6. +4. Git Bash を開きます。 {% data variables.product.prodname_desktop %} に収納されている Git Shell を使用している場合は、Git Shell を開き、ステップ 6 に進みます。 5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} -6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +6. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7以前を使用している場合: ```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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```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) @@ -87,7 +89,7 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an > 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. +7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致していなければなりません 。 {% endwindows %} @@ -95,42 +97,40 @@ You can delete unauthorized (or possibly compromised) SSH keys to ensure that an {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.ssh %} -3. On the SSH Settings page, take note of the SSH keys associated with your account. 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) +3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[Delete] をクリックします。 残しておきたい有効な SSH キーがある場合は、[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. + **注釈:** Git 操作が失敗したために SSH キーを監査している場合は、[SSH キー監査エラー] (/articles/error-we-re-doing-an-ssh-key-audit) の原因となった未検証のキーが SSH キーのリストで強調表示されます。 {% endtip %} -4. Open Terminal. +4. ターミナルを開きます。 5. {% data reusables.command_line.start_ssh_agent %} -6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +6. 自分の公開鍵のフィンガープリントを見つけてメモします。 {% if currentVersion ver_lt "enterprise-server@3.0" %}OpenSSH 6.7以前を使用している場合: ```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) ``` - If you're using OpenSSH 6.8 or newer: + OpenSSH 6.8 以降を使用している場合: ```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 %} +```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. +7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致して*いなければなりません* 。 {% endlinux %} {% warning %} -**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern. +**警告**: 見慣れない SSH キーが {% data variables.product.product_name %} で見つかった場合は、すぐにそれを削除し、さらに支援が必要な場合は {% data variables.contact.contact_support %} に問い合わせてください。 確認できない公開鍵は、潜在的なセキュリティ上の問題を示している可能性があります。 {% endwarning %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index 81be60dcce..f0bc643e62 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -18,7 +18,7 @@ topics: Issueは、バグレポートや計画された改善など、プロジェクトの特定の詳細についての議論に役立ちます。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 プルリクエストでは、提案された変更に直接コメントできます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests)及び[プルリクエストへコメントする](/articles/commenting-on-a-pull-request)を参照してください。 -{% data reusables.organizations.team-discussions-purpose %}詳しい情報については「[Team ディスカッションについて](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)」を参照してください。 +{% data reusables.organizations.team-discussions-purpose %}詳しい情報については「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照してください。 ### コメント中のアイデアへの反応 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 a9dcb78f85..3c5f69ed3e 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 @@ -15,7 +15,7 @@ topics: プルリクエストがオープンになった後、*読み取り*アクセスを持つすべてのユーザは、提案された変更をレビューしてコメントできます。 また、作者がプルリクエストから直接適用できるコード行への特定の変更を提案することもできます。 詳細は「[プルリクエストで提案された変更をレビューする](/articles/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 -リポジトリオーナーとコラボレーターは、特定の人物にプルリクエストのレビューをリクエストできます。 また、Organization メンバーは、リポジトリの読み取りアクセス権を持つ Team にプルリクエストのレビューをリクエストできます。 詳細は「[プルリクエストのレビューをリクエストする](/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" %} Team 全体の代わりに自動的に割り当てられる Team メンバーのサブセットを指定できます。 詳しい情報については、「[Team のコードレビューの割り当てを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} +リポジトリオーナーとコラボレーターは、特定の人物にプルリクエストのレビューをリクエストできます。 また、Organization メンバーは、リポジトリの読み取りアクセス権を持つ Team にプルリクエストのレビューをリクエストできます。 詳細は「[プルリクエストのレビューをリクエストする](/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" %} Team 全体の代わりに自動的に割り当てられる Team メンバーのサブセットを指定できます。 詳しい情報については、「[Team のコードレビューの割り当てを管理する](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} レビューにより、提案された変更についての議論がなされ、その変更がリポジトリのコントリビューションのガイドラインやその他の品質標準を満たすことを保証しやすくなります。 コードの特定の種類や領域に対して、どの個人や Team をオーナーとするかを、CODEOWNERS ファイルで定義できます。 プルリクエストが、定義されたオーナーを持っているコードを変更するものである場合、オーナーである個人あるいはTeam がレビューを担当するよう、自動的にリクエストされます。 詳細は「[コードオーナーについて](/articles/about-code-owners/)」を参照してください。 diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 06edc95d1e..c3bc85de5e 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -14,7 +14,9 @@ topics: プルリクエストの自動マージを有効にすると、必要なすべてのレビューを満たし、ステータスチェックに合格すると、プルリクエストが自動的にマージされます。 自動マージにより、要件が満たされるのを待つ必要がなくなるため、他のタスクに進むことができます。 -プルリクエストで自動マージを使用する前に、リポジトリで自動マージを有効にする必要があります。 詳しい情報については、「[リポジトリ内のプルリクエストの自動マージを管理する](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)」を参照してください。 +プルリクエストで自動マージを使用する前に、リポジトリで自動マージを有効にする必要があります。 For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} + +After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} 自動マージに関するフィードバックがある場合は、[お問い合わせ](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback)にご連絡ください。 diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index cbfc52f73c..2750335da7 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -13,7 +13,7 @@ topics: ユーザアカウントが所有しているリポジトリのオーナーとコラボレータは、プルリクエストのレビューを割り当てることができます。 リポジトリに対するトリアージ権限を持つ Organization メンバーは、プルリクエストのレビューを割り当てることができます。 -オーナーまたはコラボレータは、ユーザ所有のリポジトリに明示的に[読み取りアクセス](/articles/access-permissions-on-github)を付与された人にプルリクエストのレビューを割り当てることができます。 Organization メンバーは、リポジトリの読み取りアクセス権を持つ人や Team にプルリクエストのレビューを割り当てることができます。 リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Team にレビューをリクエストし、コードレビューの割り当てが有効になっている場合、特定のメンバーがリクエストされ、Team はレビュー担当者として削除されます。 詳しい情報については、「[Team のコードレビューの割り当てを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} +オーナーまたはコラボレータは、ユーザ所有のリポジトリに明示的に[読み取りアクセス](/articles/access-permissions-on-github)を付与された人にプルリクエストのレビューを割り当てることができます。 Organization メンバーは、リポジトリの読み取りアクセス権を持つ人や Team にプルリクエストのレビューを割り当てることができます。 リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Team にレビューをリクエストし、コードレビューの割り当てが有効になっている場合、特定のメンバーがリクエストされ、Team はレビュー担当者として削除されます。 詳しい情報については、「[Team のコードレビューの割り当てを管理する](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} {% note %} 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 f219bb6cca..f0e61e3bfe 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 @@ -34,7 +34,7 @@ topics: {% 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)." +プルリクエストに依存関係への変更が含まれている場合は、マニフェストまたはロックファイルの依存関係のレビューを使用して、何が変更されたかを確認し、変更によるセキュリティの脆弱性の発生の有無を確認できます。 詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。 {% data reusables.repositories.changed-files %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index e2baa4574c..c9491ff1b8 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -79,5 +79,5 @@ Enterprise のポリシーでフォークが許可されている場合、内部 - 「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」 - [フォークについて](/articles/about-forks) - 「[リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)」 -- 「[Organization のフォークポリシーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)」 +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" - 「{% if currentVersion == "free-pro-team@latest" %}[Enterprise アカウントでリポジトリ管理ポリシーを施行する](/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 %}「[Enterprise でリポジトリ管理ポリシーを施行する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}」 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 5603738e0e..b31ee59e83 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 @@ -23,7 +23,7 @@ topics: 管理者あるいはオーナー権限を持つ誰かがレビュー必須を有効化した場合、作者がリポジトリ中でプルリクエストをマージできるための条件としてコードオーナーからの承認を必須とすることもできます。 詳しい情報については[保護されたブランチについて](/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 %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Team がコードレビューの割り当てを有効にしている場合、個々の承認は、保護されたブランチでのコードオーナーの承認要件を満たしません。 詳しい情報については、「[Team のコードレビューの割り当てを管理する](/organizations/organizing-members-into-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.22" %} ファイルにコードオーナーがいる場合、プルリクエストをオープンする前にコードオーナーを確認できます。 リポジトリでは、ファイルを参照して diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md index cb12bef163..7b0b4fbb01 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -19,7 +19,7 @@ topics: {% data variables.product.product_name %} は、オープンソースの [Linguist ライブラリ](https://github.com/github/linguist)を使用して、 構文の強調表示とリポジトリ統計のファイル言語を決定します。 デフォルトブランチに変更をプッシュすると、言語統計が更新されます。 -ファイルによっては特定しにくいものもあります。また、プロジェクトによっては、主たるコード以外のライブラリやベンダーファイルが含まれていることもあります。 誤った結果が返される場合は、Linguist の [トラブルシューティングガイド](https://github.com/github/linguist#troubleshooting)を調べてみてください。 +ファイルによっては特定しにくいものもあります。また、プロジェクトによっては、主たるコード以外のライブラリやベンダーファイルが含まれていることもあります。 誤った結果が返される場合は、Linguist の [トラブルシューティングガイド](https://github.com/github/linguist/blob/master/docs/troubleshooting.md)を調べてみてください。 ### マークアップ言語 diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index 0f595199db..86dcf48ced 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -22,7 +22,7 @@ If パブリックリポジトリには、インターネット上のすべてのユーザがアクセスできます。 プライベートリポジトリには、自分、明示的にアクセスを共有するユーザ、および Organization リポジトリの場合は特定の Organization メンバーのみがアクセスできます。 内部リポジトリには、Enterprise メンバーがアクセスできます。 詳しい情報については、「[内部リポジトリについて](#about-internal-repositories)」を参照してください。 {% endif %} -Organization のオーナーは、Organization 内で作成されたすべてのリポジトリにいつでもアクセスできます。 詳細は「[Organization のリポジトリ権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)」を参照してください。 +Organization のオーナーは、Organization 内で作成されたすべてのリポジトリにいつでもアクセスできます。 詳細は「[Organization のためのリポジトリ権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)」を参照してください。 リポジトリの管理者権限を持つユーザは、既存のリポジトリの可視性を変更できます。 詳細は「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」を参照してください。 diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md index a4ca8c2009..15b84fbfd7 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -23,13 +23,13 @@ topics: ``` 3. 新しいリポジトリをミラープッシュします。 ```shell - $ cd old-repository.git + $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` 4. 先ほど作成した一時ローカルリポジトリを削除します。 ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### {% data variables.large_files.product_name_long %} オブジェクトを含むリポジトリをミラーする @@ -41,7 +41,7 @@ topics: ``` 3. クローンしたリポジトリに移動します。 ```shell - $ cd old-repository.git + $ cd old-repository ``` 4. リポジトリの {% data variables.large_files.product_name_long %} オブジェクトをプルします。 ```shell @@ -58,7 +58,7 @@ topics: 7. 先ほど作成した一時ローカルリポジトリを削除します。 ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### 別の場所にあるリポジトリをミラーする @@ -72,7 +72,7 @@ topics: ``` 3. プッシュの場所をミラーに設定します。 ```shell - $ cd repository-to-mirror.git + $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index 99cf592bcc..62219a3233 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > provide shell access. ``` -リポジトリが Organization に属し、OAuth App によって生成された SSH キーを使用している場合、OAuth App へのアクセスは Organization のオーナーによって制限されている可能性があります。 詳しい情報については、「OAuth App のアクセス制限について」を参照してください。 +リポジトリが Organization に属し、OAuth App によって生成された SSH キーを使用している場合、OAuth App へのアクセスは Organization のオーナーによって制限されている可能性があります。 For more information, see "About OAuth App access restrictions." 詳細は「[GitHub アカウントに新しい GPG キーを追加する](/articles/adding-a-new-gpg-key-to-your-github-account)」を参照してください。 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 e4619e0a4c..d740d4053b 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 @@ -1,94 +1,96 @@ --- -title: Licensing a repository -intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.' +title: リポジトリのライセンス +intro: 'GitHub のパブリックリポジトリは、オープンソース ソフトウェアの共有にも頻繁に利用されています。 リポジトリを真にオープンソースにしたければ、他のユーザが自由にそのソフトウェアを使用でき、変更や配布もできるように、ライセンスを付与する必要があります。' redirect_from: - /articles/open-source-licensing/ - /articles/licensing-a-repository versions: free-pro-team: '*' enterprise-server: '*' +topics: + - repositories --- -### Choosing the right license +### 適切なライセンスを選択する -We created [choosealicense.com](http://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision. +コードのライセンスについて理解しやすいように、[choosealicense.com](http://choosealicense.com) のページを用意しました。 ソフトウェアのライセンスは、ソースコードに対して許可されることとされないことを規定するものなので、十分な情報に基づいて決定することが重要です。 -You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project. +ライセンスの選択は義務ではありませんが、 ライセンスがない場合はデフォルトの著作権法が適用されます。つまり、ソースコードについては作者があらゆる権利を留保し、ソースコードの複製、配布、派生物の作成は誰にも許可されないということです。 オープンソースのプロジェクトを作成する場合は、オープンソース ライセンスを設定することを強くおすすめします。 プロジェクトに適したライセンスの選択に関する詳細な手引きは、[オープンソース ガイド](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project)に記載されています。 {% note %} -**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% if currentVersion == "free-pro-team@latest" %}according to the [Terms of Service](/articles/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." +**注釈:** [利用規約](/articles/github-terms-of-service)に従って、{% data variables.product.product_name %} のパブリックリポジトリにソースコードを公開すると、{% endif %}{% data variables.product.product_location %} の他のユーザにリポジトリを表示してフォークする権限を与えることになります。 すでにリポジトリを作成していて、ユーザによるリポジトリへのアクセスを禁止する場合は、リポジトリをプライベートにすることができます。 リポジトリの表示をプライベートに変更しても、他のユーザによって作成された既存のフォークまたはローカルコピーは存続します。 詳細は「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」を参照してください。 {% endnote %} -### Determining the location of your license +### ライセンスの置かれている場所を確認する -Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). +多くの場合、ライセンステキストはリポジトリのルートにある `LICENSE.txt` (または `LICENSE.md` か `LICENSE.rst`) というファイルに書かれています。 [Hubot の例をこちらに示します](https://github.com/github/hubot/blob/master/LICENSE.md) -Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license." +プロジェクトによっては、ライセンスに関する情報は README に記載されています。 たとえばプロジェクトの README には、「当ライセンスは MIT ライセンスの規約に基づいて付与されています」などの文言が書かれていることがあります。 -As a best practice, we encourage you to include the license file with your project. +ベスト プラクティスとして、プロジェクトにはライセンス ファイルを含めることをお勧めします。 -### Searching GitHub by license type +### ライセンス別に GitHub を検索する -You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword: +`license` 修飾子と、正確なライセンス キーワードを使用すると、ライセンスまたはライセンス ファミリーに基づいてリポジトリをフィルタリングできます。 -License | License keyword ---- | --- -| 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` | +| ライセンス | ライセンス キーワード | +| ----- | ------------------------------------------------------------- | +| | Academic Free License v3.0 | `afl-3.0` | +| | Apache ライセンス 2.0 | `apache-2.0` | +| | Artistic ライセンス 2.0 | `artistic-2.0` | +| | Boost Software License 1.0 | `bsl-1.0` | +| | BSD 2-Clause "Simplified" ライセンス | `bsd-2-clause` | +| | BSD 3-Clause "New" または "Revised" ライセンス | `bsd-3-clause` | +| | BSD 3-Clause Clear ライセンス | `bsd-3-clause-clear` | +| | Creative Commons ライセンス ファミリー | `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 ファミリー | `gpl` | +| | GNU General Public License v2.0 | `gpl-2.0` | +| | GNU General Public License v3.0 | `gpl-3.0` | +| | GNU Lesser General Public License ファミリー | `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` | -When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/articles/searching-for-repositories/#search-by-license)." +ファミリー ライセンス別で検索すると、結果にはそのファミリーのライセンスがすべて含まれます。 たとえば、`license:gpl` というクエリを実行した結果には、GNU General Public License v2.0 と GNU General Public License v3.0 でライセンスされているリポジトリが含まれます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-by-license)を参照してください。 -### Detecting 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). +[オープンソースの Ruby Gem Licensee](https://github.com/licensee/licensee) は、リポジトリの *LICENSE* ファイルを、既知のライセンスの候補リストと比較します。 Licensee には [ライセンス API](/rest/reference/licenses) も用意されており、 {% data variables.product.product_name %} のリポジトリがどのようにライセンスされているかを[深く理解できます](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 自分のリポジトリで使用しているライセンスが、[ライセンス選択のウェブサイト](http://choosealicense.com/appendix/)にリストされていない場合は、[ライセンスの追加をリクエストする](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)ことができます。 -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. +自分のリポジトリで使用しているライセンスが、ライセンス選択のウェブサイトにはリストされていて、リポジトリ ページのトップに明示的に表示されていない場合には、複数のライセンスが含まれるなど、複雑な状況が考えられます。 ライセンスを見つけてもらうために、*LICENSE* ファイルは単純にし、リポジトリの *README* ファイルなど、どこかでその複雑さに言及してください。 -### Applying a license to a repository with an existing license +### 既存のライセンスでリポジトリにライセンスを適用する -The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)." +ライセンスを選択できるのは、GitHub で新しいプロジェクトを作成するときだけです。 ブラウザを使って、手動でライセンスを追加できます。 リポジトリへのライセンスの追加についての詳しい情報は、「[リポジトリにライセンスを追加する](/articles/adding-a-license-to-a-repository)」を参照してください。 -![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png) +![GitHub.com でのライセンス選択のスクリーンショット](/assets/images/help/repository/repository-license-picker.png) -### Disclaimer +### 免責事項 -The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an “as-is” basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional. +GitHub がオープンソース ライセンスへの取り組みで目指しているのは、ユーザが十分な情報に基づいて選択できるように基盤を作ることです。 GitHub は、オープンソース ライセンスとそれを使用しているプロジェクトについての情報をユーザが取得できるように、ライセンス情報を掲載しています。 その情報がお役に立つことを願っていますが、GitHub は法律の専門家ではなく、誤りがないとは言えません。 そのため、GitHub は情報を「現状有姿」で提供するものであり、GitHub で、または GitHub を通じて提供する情報またはライセンスについては何らの保証もせず、かかるライセンス情報の利用に起因する損害については責任を負いません。 コードに適したライセンスや、ライセンスに関する他の法的な問題について不明な点がある場合は、必ず専門家にご相談ください。 -### Further reading +### 参考リンク -- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% if currentVersion == "free-pro-team@latest" %} +- オープンソースガイドのセクション「[オープンソースの法的な側面](https://opensource.guide/legal/)」{% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md index e0c8fcc02f..322a4a5efd 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -1,6 +1,6 @@ --- title: Visual Studio で Codespaces を使用する -intro: '{% data variables.product.product_name %} のアカウントに接続することにより、{% data variables.product.prodname_vs %} の Codespaces で直接開発できます。' +intro: 'This preview has concluded and will no longer be accepting signups.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,50 +10,10 @@ topics: {% note %} -**注釈:** {% data variables.product.prodname_codespaces %} は現在限定パブリックベータであり、変更されることがあります。 ベータ期間中、{% data variables.product.prodname_dotcom %}は{% data variables.product.prodname_codespaces %}の可用性について保証しません。 [限定パブリックベータにサインアップする](https://github.com/features/codespaces/signup-vs) を参照してください。 ベータへの参加に関する詳しい情報については「[{% data variables.product.prodname_codespaces %}について](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)」を参照してください。 +**注釈:** {% data variables.product.prodname_codespaces %} は現在限定パブリックベータであり、変更されることがあります。 ベータ期間中、{% data variables.product.prodname_dotcom %}は{% data variables.product.prodname_codespaces %}の可用性について保証しません。 {% endnote %} ### About codespaces in {% data variables.product.prodname_vs %} -{% data variables.product.prodname_vs %} で Codespaces を作成して、Windows 環境でアプリケーションを開発できます。 {% data variables.product.prodname_vs %} で Codespaces を使用すると、ソースコードの参照、ソリューションの構築、リポジトリへの変更をコミットできます。 - -アプリケーションで使用するには、{% data variables.product.prodname_vs %} で Codespaces を作成する必要があります。 {% data variables.product.prodname_vs %} 外で作成された Codespaces は、現在 {% data variables.product.prodname_vs %} では使用できません。 - -### 必要な環境 - -{% data variables.product.prodname_vs %} で Codespaces を設定する前に、最新バージョンの [{% data variables.product.prodname_vs %} Preview](https://aka.ms/vspreview) をダウンロードする必要があります。 - -#### {% data variables.product.prodname_vs %} と {% data variables.product.prodname_github_codespaces %} 間の接続を有効にする - -{% data variables.product.prodname_vs %} Preview を使用した {% data variables.product.prodname_github_codespaces %} への接続はデフォルトでは有効になっていないため、最初に [Preview Features] オプションを有効にする必要があります。 - -1. {% data variables.product.prodname_vs %} Preview で、[Tools] ドロップダウンメニューを使用し、[**Options**] をクリックします。 -2. [**Environment**] で、[**Preview Features**] を選択し、[**Connect to {% data variables.product.prodname_github_codespaces %}**] プレビュー機能を確認します。 ![[Connect to {% data variables.product.prodname_github_codespaces %}] プレビュー機能を確認](/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png) -3. この機能を利用するには、{% data variables.product.prodname_vs %} を再起動する必要があります。 - -### {% data variables.product.prodname_vs %} で Codespaces を作成する - -1. {% data variables.product.prodname_vs %} を起動すると、スタートウィンドウの「Get started」の下に [**Connect to a codespace**] ボタンが表示されます。 ![Codespaces に接続する Visual Studio の開始ウィンドウ](/assets/images/help/codespaces/visual-studio-start-window.png) -2. [**Connect to a codespace**] をクリックします。 -3. [**Sign in to {% data variables.product.prodname_dotcom %}**] をクリックしてプロンプトに従うか、[**Create one!**] をクリックして新しい {% data variables.product.prodname_dotcom %} アカウントを作成し、アカウントにサインインします。 ![{% data variables.product.prodname_dotcom %} への Visual Studio サインイン](/assets/images/help/codespaces/visual-studio-sign-in-to-github.png) -4. 「Codespace details」の下に、{% data variables.product.prodname_github_codespaces %} が Codespaces にクローンするリポジトリの URL を入力します。 -5. 必要に応じて、ドロップダウンメニューの後にインスタンスタイプと中断を使用して、Codespaces の詳細を設定します。 ![Visual Studio Codespaces の詳細](/assets/images/help/codespaces/visual-studio-codespace-details.png) -6. [**Create and Connect**] をクリックします。 {% data variables.product.prodname_github_codespaces %} は Codespaces の準備を開始し、Codespaces の準備ができたら {% data variables.product.prodname_vs %} を開きます。 Codespaces 名は、メニューのリモートインジケーターに表示されます。 ![eShopOnWeb リポジトリ Codespaces に接続された Visual Studio](/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png) - -### {% data variables.product.prodname_vs %} で codespace を開く - -1. [File] ドロップダウンメニューを使用して、[**Connect to a Codespace**] をクリックします。 ![Codespaces メニュー項目への Visual Studio ファイル接続](/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png) -2. [{% data variables.product.prodname_github_codespaces %}] の下で、接続する Codespaces をクリックしてから、[**Connect**] をクリックします。 ![Visual Studio で利用可能な Codespacesと詳細を表示](/assets/images/help/codespaces/visual-studio-connect-codespace.png) - -### {% data variables.product.prodname_vs %} の Codespaces を設定する - -{% data variables.product.prodname_vs %} で作成された Codespaces は、{% data variables.product.prodname_vs %} に含まれているコマンドラインツールの devinit という新しいツールを使用してカスタマイズできます。 - -#### devinit - -[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) を使用すると、Windows の開発 Codespaces への追加のフレームワークとツールのインストールや環境変数の変更などができます。 - -devinit は、[devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json) という設定ファイルをサポートしています。 カスタマイズされた繰り返し可能な開発環境を作成する場合は、このファイルをプロジェクトに追加します。 [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) ファイルで devinit を使用すると、Codespaces は作成時に自動的に設定されます。 - -Windows の Codespaces の設定と devinit の詳細については、{% data variables.product.prodname_vs %} ドキュメントの「[Codespaces のカスタマイズ](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces)」を参照してください。 devinit の詳細については、「[devinit 入門](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit)」を参照してください。 +The private preview for GitHub Codespaces in Visual Studio 2019 has concluded. For more information, see the [Visual Studio 2019 documentation](https://docs.microsoft.com/visualstudio/ide/codespaces/codespaces-overview?view=vs-2019). 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 9684696ef4..eebed61539 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -1,51 +1,49 @@ --- -title: About code scanning -intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' +title: コードスキャンニングについて +intro: '{% data variables.product.prodname_code_scanning %} を使用して、{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードからセキュリティの脆弱性とエラーを見つけることができます。' product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/managing-security-vulnerabilities/about-automated-code-scanning versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - セキュリティ --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About {% data variables.product.prodname_code_scanning %} +### {% data variables.product.prodname_code_scanning %} について {% data reusables.code-scanning.about-code-scanning %} -You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. +{% data variables.product.prodname_code_scanning %} を使用して、コード内の既存の問題の修正を検索し、トリアージして、優先順位を付けることができます。 また、{% data variables.product.prodname_code_scanning_capc %} は、開発者による新しい問題の発生も防ぎます。 スキャンを特定の日時にスケジュールしたり、プッシュなどの特定のイベントがリポジトリで発生したときにスキャンをトリガーしたりすることができます。 -If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." +{% data variables.product.prodname_code_scanning %} がコードに潜在的な脆弱性またはエラーを見つけた場合、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。 アラートを引き起こしたコードを修正すると、{% data variables.product.prodname_dotcom %}はそのアラートを閉じます。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use 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 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 "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." -### About {% data variables.product.prodname_codeql %} +### {% data variables.product.prodname_codeql %} について -You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +デフォルトでは、{% data variables.product.prodname_code_scanning %} はセマンティックコード分析エンジンである {% data variables.product.prodname_codeql %} を使用します。 {% data variables.product.prodname_codeql %} はコードをデータとして扱い、コードの潜在的な脆弱性を従来の静的分析よりも高い精度で見つけることができます。 -{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. +{% data variables.product.prodname_ql %} は {% data variables.product.prodname_codeql %} を動作させるクエリ言語です。 {% data variables.product.prodname_ql %} はオブジェクト指向ロジックプログラミング言語です。 {% data variables.product.company_short %}、言語の専門家、セキュリティ研究者が {% data variables.product.prodname_code_scanning %} に使用するクエリを作成します。クエリはオープンソースです。 コミュニティはクエリを維持および更新して、分析を改善し、誤検出を減らします。 詳しい情報については、GitHub Security Lab Web サイトの「[{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)」を参照してください。 -{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. +{% data variables.product.prodname_code_scanning %} の API エンドポイントについての詳細は、「[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)」を参照してください。 {% data reusables.code-scanning.supported-languages %} -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. +[`github/codeql`](https://github.com/github/codeql)リポジトリで {% data variables.product.prodname_code_scanning %} のクエリを表示して貢献できます。 詳しい情報については、 {% data variables.product.prodname_codeql %} ドキュメントの「[{% data variables.product.prodname_codeql %} クエリ](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### {% data variables.product.prodname_code_scanning %}の支払いについて -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data variables.product.prodname_code_scanning_capc %} は {% data variables.product.prodname_actions %} を使用し、{% data variables.product.prodname_code_scanning %} ワークフローの実行ごとに {% data variables.product.prodname_actions %} に数分かかります。 詳しい情報については、[{% data variables.product.prodname_actions %}の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)を参照してください。 {% endif %} -### About third-party code scanning tools +### サードパーティのコードスキャンツールについて {% data reusables.code-scanning.you-can-upload-third-party-analysis %} @@ -53,9 +51,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### Further reading +### 参考リンク {% if currentVersion == "free-pro-team@latest" 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 +- 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 612c2f6227..ecbc13b693 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 @@ -1,56 +1,55 @@ --- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' +title: コードスキャンを設定する +intro: '{% data variables.product.prodname_dotcom %} がプロジェクトのコードをスキャンして脆弱性やエラーを検出する方法を設定できます。' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' +permissions: 'リポジトリへの書き込み権限を持つユーザは、リポジトリの {% data variables.product.prodname_code_scanning %} を設定できます。' miniTocMaxHeadingLevel: 4 versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - セキュリティ --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### About {% data variables.product.prodname_code_scanning %} configuration +### {% data variables.product.prodname_code_scanning %} の設定について -You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." +You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. {% data variables.product.prodname_actions %} に関する詳しい情報については、「[{% data variables.product.prodname_actions %} について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。 For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)." -This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}. -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} {% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. -### Editing a {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} は、リポジトリの _.github/workflows_ ディレクトリにワークフローファイルを保存します。 You can find a workflow you have added by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. リポジトリで、編集したいワークフローファイルにアクセスします。 +1. ファイルビューの右上隅の {% octicon "pencil" aria-label="The edit icon" %}をクリックしてワークフローエディタを開きます。 ![ワークフローファイルの編集ボタン](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. ファイルを編集したら、[**Start commit**] をクリックして、[Commit changes] フォームに入力します。 現在のブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択できます。 ![codeql.yml ワークフローの更新をコミットする](/assets/images/help/repository/code-scanning-workflow-update.png) For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -### Configuring frequency +### 頻度を設定する -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +スケジュール設定されているときや、リポジトリで特定のイベントが発生したときに、コードをスキャンできます。 -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +リポジトリへのプッシュごと、およびプルリクエストが作成されるたびにコードをスキャンすることで、開発者がコードに新しい脆弱性やエラーをもたらすことを防ぎます。 スケジュールに従ってコードをスキャンすると、開発者がリポジトリを積極的に維持していない場合でも、{% data variables.product.company_short %}、セキュリティ研究者、コミュニティが発見した最新の脆弱性とエラーが通知されます。 -#### Scanning on push +#### プッシュ時にスキャンする -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +デフォルトのワークフローを使用する場合、{% data variables.product.prodname_code_scanning %} は、イベントによってトリガーされるスキャンに加えて、リポジトリ内のコードを週に1回スキャンします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#on)」を参照してください。 -#### Scanning pull requests +#### プルリクエストをスキャンする -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)」を参照してください。 -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +`pull_request` イベントに関する詳しい情報については、「"[{% data variables.product.prodname_actions %}のためのワークフローの構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)」を参照してください。 #### Avoiding unnecessary scans of pull requests @@ -69,7 +68,7 @@ on: {% note %} -**Notes** +**注釈** * `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." * For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. @@ -78,17 +77,17 @@ on: For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -#### Scanning on a schedule +#### スケジュールに従ってスキャンする -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`pull_request` イベントを使用して、プルリクエストの `HEAD` コミットでコードスキャンをトリガーします。 このスケジュールを調整するには、ワークフローで `cron` 値を編集します。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onschedule)」を参照してください。 {% note %} -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. +**注釈**: {% data variables.product.prodname_dotcom %} は、デフォルトのブランチのワークフローにあるスケジュール設定されたジョブのみを実行します。 他のブランチのワークフローでスケジュールを変更しても、ブランチをデフォルトブランチにマージするまで影響はありません。 {% endnote %} -#### Example +#### サンプル The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. @@ -99,15 +98,15 @@ on: pull_request: branches: [main] schedule: - - cron: '0 15 * * 0' + - cron: '40 7 * * 2' ``` This workflow scans: * Every push to the default branch and the protected branch * Every pull request to the default branch -* The default branch at 3 P.M. every Sunday +* The default branch every Tuesday at 7:40 UTC -### Specifying an operating system +### オペレーティングシステムを指定する If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} @@ -122,7 +121,7 @@ jobs: {% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% data variables.product.prodname_code_scanning_capc %} は、macOS、Ubuntu、Windows の最新バージョンをサポートしています。 Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." {% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} @@ -136,7 +135,7 @@ The default {% data variables.product.prodname_codeql_workflow %} file contains {% data reusables.code-scanning.specify-language-to-analyze %} -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix. +If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. ```yaml jobs: @@ -157,7 +156,7 @@ If your workflow does not contain a matrix called `language`, then {% data varia languages: cpp, csharp, python ``` {% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies +### 追加のクエリを実行する For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: @@ -199,38 +198,45 @@ jobs: ``` {% endif %} -### Running additional queries +### 追加のクエリを実行する {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. +1つ以上のクエリスイートを追加するには、設定ファイルに `queries` セクションを追加します。 If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. +{% raw %} ``` yaml - uses: github/codeql-action/init@v1 with: queries: COMMA-SEPARATED LIST OF PATHS + # Optional. Provide a token to access private repositories. + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +設定ファイルでこれらを指定して、追加のクエリスイートを実行することもできます。 クエリスイートはクエリのコレクションであり、通常は目的または言語ごとにグループ化されています。 {% data reusables.code-scanning.codeql-query-suites %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. 設定ファイルの例については、「[Example configuration files](#example-configuration-files)」を参照してください。 In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. +{% raw %} ``` 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 + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -### Using a custom configuration file +### サードパーティのコードスキャンツールを使用する As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. +In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. この例では、設定ファイル _./.github/codeql/codeql-config.yml_ を読み込みます。 ``` yaml - uses: github/codeql-action/init@v1 @@ -238,9 +244,19 @@ 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 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_. +{% data reusables.code-scanning.custom-configuration-file %} -The settings in the file are written in YAML format. +If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository. + +{% raw %} +```yaml +uses: github/codeql-action/init@v1 +with: + external-repository-token: ${{ secrets.ACCESS_TOKEN }} +``` +{% endraw %} + +The settings in the configuration file are written in YAML format. #### Specifying additional queries @@ -257,11 +273,11 @@ Optionally, you can give each array element a name, as shown in the example conf For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. -#### Disabling the default queries +#### デフォルトのクエリを無効にする -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +カスタムクエリのみを実行する場合は、構成ファイルに `disable-default-queries: true` を追加して、デフォルトのセキュリティクエリを無効にすることができます。 -#### Specifying directories to scan +#### スキャンするディレクトリを指定する For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. @@ -275,46 +291,27 @@ paths-ignore: {% note %} -**Note**: +**ノート**: -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. 詳細については、「[{% 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. たとえば、`foo/**`、`**/foo`、および `foo/**/bar` はすべて使用できる構文ですが、`**foo` は使用できません。 ただし、例に示すように、単一の * を他の文字と一緒に使用できます。 You'll need to quote anything that contains a `*` character. {% endnote %} -For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. ビルドからディレクトリを除外するために使用するコマンドは、ビルドシステムによって異なります。 For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +特定のディレクトリのコードを変更すると、monorepo の一部をすばやく分析できます。 ビルドステップでディレクトリを除外し、ワークフローファイルで [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) の`paths-ignore` および `paths` キーワードを使用する必要があります。 -#### Example configuration files +#### 設定ファイルの例 {% data reusables.code-scanning.example-configuration-files %} -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages +### コンパイルされた言語の {% data variables.product.prodname_code_scanning %} を設定する {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} {% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)." -### Accessing private repositories +### {% data variables.product.prodname_code_scanning %} 用の設定ファイルを作成できます。 -If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs..steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." - -For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. - -{% 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 %} - -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} - -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." +{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. ワークフローに `upload-sarif` アクションを追加することで、{% data variables.product.prodname_dotcom %} のサードパーティツールからのコード分析を表示できます。 詳しい情報については、「[SARIF ファイルを GitHub にアップロードする](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)」を参照してください。 diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 28e716d495..b0cb3e0284 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -37,7 +37,7 @@ You need write permission to view a summary of all the alerts for a repository o {% 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. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. ![Summary of alerts](/assets/images/enterprise/3.1/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) @@ -49,7 +49,7 @@ If you have write permission for a repository, you can view fixed alerts by view 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. -![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} @@ -102,11 +102,11 @@ To dismiss or delete alerts: 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. - ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![Filter alerts by rule](/assets/images/enterprise/3.1/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. - ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) + ![Open an alert from the summary list](/assets/images/enterprise/3.1/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) diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md index 8ec22325f4..fdca8b11dd 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -25,7 +25,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -65,7 +65,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endnote %} @@ -91,7 +91,7 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. 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 index cb310269c0..76f9035a65 100644 --- 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 @@ -1,16 +1,20 @@ --- title: GitHub Advanced Securityについて -intro: '{% data variables.product.prodname_dotcom %}では、{% data variables.product.prodname_advanced_security %}ライセンスのもとでセキュリティ機能がさらに強化されます。 これらの機能は、{% data variables.product.prodname_dotcom_the_website %}のパブリックリポジトリに対しても有効になります。' +intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license.{% if currentVersion == "free-pro-team@latest" %} These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' +product: '{% data reusables.gated-features.ghas %}' versions: free-pro-team: '*' enterprise-server: '>=3.0' + github-ae: '*' +topics: + - セキュリティ --- ### {% data variables.product.prodname_GH_advanced_security %} について -{% data variables.product.prodname_dotcom %}には、コードの質を改善し維持できる多くの機能があります。 依存関係グラフや{% data variables.product.prodname_dependabot_alerts %}など、一部の機能はすべてのプランに含まれます。 それ以外のセキュリティ機能には、{% data variables.product.prodname_dotcom_the_website %}のパブリックリポジトリとは別のリポジトリで{% data variables.product.prodname_GH_advanced_security %}のライセンスを実行する必要があります。 (つまり、{% data variables.product.prodname_dotcom_the_website %}のプライベートおよび内部リポジトリと、{% data variables.product.prodname_ghe_server %}のすべてのリポジトリです。) +{% data variables.product.prodname_dotcom %}には、コードの質を改善し維持できる多くの機能があります。 これらの一部は、依存関係グラフや {% data variables.product.prodname_dependabot_alerts %}{% endif %} など、すべてのプランに含まれています{% if currentVersion != "github-ae@latest" %}。 それ以外のセキュリティ機能には、{% data variables.product.prodname_dotcom_the_website %}のパブリックリポジトリとは別のリポジトリで{% data variables.product.prodname_GH_advanced_security %}のライセンスを実行する必要があります。 -セキュリティ機能すべての概要については、「[リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)」を参照してください。 セキュリティ機能に関連するアクションの権限要件に関する詳しい情報については、「[Organization のリポジトリの権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" %}詳細については、「[{% data variables.product.prodname_GH_advanced_security %} のライセンスについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)」を参照してください。{% elsif currentVersion ver_gt "enterprise-server@2.22" %}{% data variables.product.prodname_GH_advanced_security %} のライセンスの購入については、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。{% elsif currentVersion == "github-ae@latest" %}ベータリリース中の {% data variables.product.prodname_ghe_managed %} の {% data variables.product.prodname_GH_advanced_security %} は無料です。{% endif %} ### {% data variables.product.prodname_advanced_security %}機能について @@ -21,28 +25,47 @@ versions: - **{% data variables.product.prodname_secret_scanning_caps %}** - シークレット、たとえばリポジトリにチェックインされているキーやトークンなどを検出します。 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} について](/github/administering-a-repository/about-secret-scanning)」を参照してください。 {% 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)." +- **依存関係のレビュー** - プルリクエストをマージする前に、依存関係に対する変更の影響を詳細に示し、脆弱性なバージョンがあればその詳細を確認できます。 For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -開発中の{% data variables.product.prodname_advanced_security %}機能については、「[{% data variables.product.prodname_dotcom %} パブリックロードマップ](https://github.com/github/roadmap).」を参照してください。 +開発中の{% data variables.product.prodname_advanced_security %}機能については、「[{% data variables.product.prodname_dotcom %} パブリックロードマップ](https://github.com/github/roadmap).」を参照してください。 セキュリティ機能すべての概要については、「[リポジトリのセキュリティ保護について](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)」を参照してください。 + +{% if currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +### {% data variables.product.product_name %} で {% data variables.product.prodname_advanced_security %} 機能を有効にする {% if currentVersion ver_gt "enterprise-server@2.22" %} -### {% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_advanced_security %}機能を有効にする - -この機能を使用するには、サイト管理者が{% data variables.product.product_location %}の{% data variables.product.prodname_advanced_security %}を有効にする必要があります。 詳しい情報については、「[高度なセキュリティ機能を設定する](/admin/configuration/configuring-advanced-security-features)」を参照してください。 - -システムを設定すると、Organizationまたはリポジトリのレベルでこの機能を有効化または無効化することができます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」と「[リポジトリのセキュリティと分析設定を管理する](/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 %}. +サイト管理者は +これらの機能を使用する前に、{% data variables.product.product_location %} に対して {% data variables.product.prodname_advanced_security %} を有効化する必要があります。 詳しい情報については、「[高度なセキュリティ機能を設定する](/admin/configuration/configuring-advanced-security-features)」を参照してください。 {% endif %} +システムを設定すると、Organizationまたはリポジトリのレベルでこの機能を有効化または無効化することができます。 For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)." + +{% endif %} + +{% if currentVersion != "github-ae@latest" %} ### {% data variables.product.prodname_dotcom_the_website %}で{% data variables.product.prodname_advanced_security %}機能を有効にする -{% data variables.product.prodname_dotcom_the_website %}のパブリックリポジトリの場合、この機能は永続的に有効になっており、無効にできるのはプロジェクトの可視性背を変更して、コードがパブリックでなくなった場合だけです。 +{% data variables.product.prodname_dotcom_the_website %} のパブリックリポジトリでは、これらの機能は永続的に有効になっており、プロジェクトの可視性を変更してコードがパブリックでなくなった場合にのみ無効化できます。 -その他すべてのリポジトリの場合は、ライセンスを有効にするとOrganizationまたはリポジトリのレベルでこの機能を有効化または無効化することができます。 {% if currentVersion == "free-pro-team@latest" %}詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」と「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 -For information about purchasing a license for +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)."{% endif %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Enterprise アカウントをお持ちの場合は、Enterprise ライセンスページに Enterprise 全体のライセンス使用状況が表示されます。 詳細については、「[{% data variables.product.prodname_GH_advanced_security %} の使用状況を表示する](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage)」を参照してください。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### 参考リンク + +- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)" + +{% elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} + +### 参考リンク + +- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)" -{% 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/githubs-products.md b/translations/ja-JP/content/github/getting-started-with-github/githubs-products.md index 0f8b56ee3a..f6d7806806 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 @@ -92,7 +92,7 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる - {% data variables.contact.enterprise_support %}。 詳細は「{% data variables.product.prodname_ghe_cloud %} サポート」および「{% data variables.product.prodname_ghe_cloud %} 補遺」を参照してください。 - 50,000 {% data variables.product.prodname_actions %} 分 - 50GBの{% data variables.product.prodname_registry %}ストレージ -- {% data variables.product.prodname_pages %} サイトのアクセス制御。 詳しい情報については、「{% data variables.product.prodname_pages %} サイトの可視性を変更する」を参照してください。 +- {% data variables.product.prodname_pages %} サイトのアクセス制御。 詳しい情報については、「{% data variables.product.prodname_pages %} サイトの可視性を変更する」を参照してください。 - 99.9% の月次稼働時間を保証するサービスレベルアグリーメント - エンタープライズアカウントで複数の {% data variables.product.prodname_dotcom_the_website %} Organization に対してポリシーと請求を一元管理するためのオプション。 詳細は「Enterprise アカウントについて」を参照してください。 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 1aa3810a40..d5da0e589f 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 @@ -52,6 +52,7 @@ versions: | control z または command z | 元に戻します | | control y または command y | やり直します | | cmd + shift + p | [**Edit file**] タブと [**Preview changes**] タブを切り替えます | +| control s or command s | Write a commit message | その他のキーボードショートカットについては、[CodeMirror ドキュメント](https://codemirror.net/doc/manual.html#commands)を参照してください。 diff --git a/translations/ja-JP/content/github/index.md b/translations/ja-JP/content/github/index.md index 44df7d3b9f..3da4ee87bb 100644 --- a/translations/ja-JP/content/github/index.md +++ b/translations/ja-JP/content/github/index.md @@ -23,7 +23,7 @@ versions: {% link_in_list /managing-subscriptions-and-notifications-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 %} @@ -57,7 +57,6 @@ versions: {% 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 %} 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 index a5d7bb10b9..d680ca7e78 100644 --- 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 @@ -1,6 +1,6 @@ --- -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 %}.' +title: リポジトリのファイルを削除する +intro: '{% data variables.product.product_name %} のリポジトリ内にある各ファイル{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}またはディレクトリ全体{% endif %}を削除できます。' redirect_from: - /articles/deleting-files - /github/managing-files-in-a-repository/deleting-files @@ -9,18 +9,20 @@ 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. +permissions: '書き込み権限を持つユーザは、リポジトリ内のファイル{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}またはディレクトリ{% endif %}を削除できます。' +topics: + - repositories --- -### About file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} and directory{% endif %} deletion +### ファイル{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}とディレクトリ{% endif %}の削除について -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 currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、またはディレクトリにあるすべてのファイルを含むディレクトリ全体を削除できます{% 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)を参照してください。 +書き込み権限を持たないリポジトリ内のファイルまたはディレクトリ{% endif %}を削除しようとすると、プロジェクトがユーザアカウントにフォークされ、変更をコミットした後に元のリポジトリにプルリクエストを送信できるようになります。 詳しい情報については[プルリクエストについて](/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)」を参照してください。 +削除したファイル{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}またはディレクトリ{% endif %}に機密データが含まれている場合、そのデータは引き続きリポジトリの Git 履歴で利用できます。 {% data variables.product.product_name %} からファイルを完全に削除するには、リポジトリの履歴からファイルを削除する必要があります。 詳細は「[機密データをリポジトリから削除する](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)」を参照してください。 -### Deleting a file +### ファイルを削除する 1. リポジトリ内で削除対象のファイルを見つけます。 2. ページの上部で、次をクリックします。 @@ -31,13 +33,13 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_ {% 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. +1. リポジトリ内で削除対象のディレクトリを見つけます。 +1. 右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックしてから、[**Delete directory**] をクリックします。 ![ディレクトリを削除するボタン](/assets/images/help/repository/delete-directory-button.png) +1. 削除するファイルを確認します。 {% 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 +{% endif %} diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 67f9613edb..67ff22ea9a 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -1,90 +1,99 @@ --- -title: About alerts for vulnerable dependencies -intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.' -redirect_from: - - /articles/about-security-alerts-for-vulnerable-dependencies - - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies +title: 脆弱性のある依存関係に関するアラートについて +intro: '{% data variables.product.product_name %} は、リポジトリに影響を与える脆弱性を検出すると、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}セキュリティアラート{% endif %}を送信します。' versions: - free-pro-team: '*' - enterprise-server: '*' + enterprise-server: '<=2.22' +topics: + - セキュリティ --- -### About vulnerable dependencies +### 脆弱性のある依存関係について {% data reusables.repositories.a-vulnerability-is %} -When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it. +セキュリティ上の脆弱性があるパッケージにコードが依存している場合、この脆弱性のある依存関係により、プロジェクトまたはそれを使用するユーザにさまざまな問題が発生する可能性があります。 -### Detection of vulnerable dependencies +### 脆弱性のある依存関係の検出 - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} は脆弱性のある依存関係を検出し、{% data variables.product.prodname_dependabot_alerts %}を送信します{% else %}{% data variables.product.product_name %} は脆弱性のある依存関係を検出し、次の場合にセキュリティアラート{% endif %}を送信します。 {% if currentVersion == "free-pro-team@latest" %} -- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)." -- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %} -- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}."{% endif %} -- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +- {% data variables.product.prodname_advisory_database %} に新しい脆弱性が追加されたとき。 詳しい情報については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ脆弱性を参照する](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)」を参照してください。{% else %} +- 新しいアドバイザリデータが {% data variables.product.prodname_dotcom_the_website %} から 1 時間ごとに {% data variables.product.prodname_ghe_server %} に同期されたとき。 アドバイザリデータに関する詳しい情報については、「{% data variables.product.prodname_advisory_database %} のセキュリティ脆弱性を参照する」を参照してください。{% endif %} +- リポジトリの依存関係グラフが変更されたとき。 たとえば、コントリビューターがコミットをプッシュして、依存しているパッケージまたはバージョンを変更したとき{{% if currentVersion == "free-pro-team@latest" %}、またはいずれかの依存関係のコードが変更されたときなどです{% endif %}。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 {% data reusables.repositories.dependency-review %} -For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +{% data variables.product.product_name %} が脆弱性と依存関係を検出できるエコシステムのリストについては、「[サポートされているパッケージエコシステム](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)」を参照してください。 {% note %} -**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use. +**注釈:** マニフェストとロックファイルを最新の状態に保つことが重要です。 依存関係グラフが現在の依存関係とバージョンを正確に反映していない場合、使用する脆弱性のある依存関係のアラートを見逃す可能性があります。 また、使用しなくなった依存関係のアラートを受け取る場合もあります。 {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %} -### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies +### 脆弱性のある依存関係の {% data variables.product.prodname_dependabot %} アラート {% else %} -### Security alerts for vulnerable dependencies +### 脆弱性のある依存対象に関するセキュリティアラート {% endif %} {% data reusables.repositories.enable-security-alerts %} -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} は、_パブリック_リポジトリ内の脆弱性のある依存関係を検出し、デフォルト設定で {% data variables.product.prodname_dependabot_alerts %} を生成します。 プライベートリポジトリの所有者、または管理アクセス権を持つユーザは、リポジトリの依存関係グラフと {% data variables.product.prodname_dependabot_alerts %} を有効にすることで、{% data variables.product.prodname_dependabot_alerts %} を有効化できます。 -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +ユーザアカウントまたは Organization が所有するすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にすることもできます。 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](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." -{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." + +{% data variables.product.product_name %} は依存関係グラフの生成をすぐに開始し、脆弱性のある依存関係が特定されるとすぐにアラートを生成します。 グラフは通常数分以内に入力されますが、多くの依存関係を持つリポジトリの場合は時間がかかる場合があります。 詳しい情報については、「[プライベートリポジトリのデータ使用を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)」を参照してください。 {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +ー +{% data variables.product.product_name %} が脆弱性のある依存関係を特定すると、{% data variables.product.prodname_dependabot %} アラートを生成し、リポジトリの [Security] タブに表示します。 アラートには、プロジェクト内で影響を受けるファイルへのリンクと、修正バージョンに関する情報が含まれています。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。 詳しい情報については、「[脆弱性のある依存関係に対する通知を設定する](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)」を参照してください。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +ー +{% data variables.product.prodname_dependabot_security_updates %} が有効になっているリポジトリの場合、アラートには、マニフェストまたはロックファイルを脆弱性を解決する最小バージョンに更新するためのプルリクエストへのリンクも含まれる場合があります。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。 {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. +ー +{% data variables.product.product_name %} が脆弱性のある依存関係を特定すると、影響を受けるリポジトリのメンテナに、脆弱性の詳細、プロジェクト内の影響を受けるファイルへのリンク、および修正バージョンに関する情報を含むセキュリティアラートを送信します。 {% endif %} {% warning %} -**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary. +**注釈**: {% data variables.product.product_name %} のセキュリティの機能は、すべての脆弱性を捕捉するものではありません。 当社は常に脆弱性データベースを更新し、最新の情報でアラートを生成するよう努力していますが、一定の期間内にすべてをの問題を把握したり、既知の脆弱性について通知したりすることはできません。 これらの機能は、それぞれの依存関係の潜在的な脆弱性やその他の問題に関する人によるレビューを置き換えるものではなく、必要な場合にはセキュリティサービスによるコンサルティングや、総合的な脆弱性レビューを行うことをおすすめします。 {% endwarning %} -### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts +### {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}セキュリティ{% endif %}アラートへのアクセス -You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +特定のプロジェクト{% if currentVersion == "free-pro-team@latest" %}に影響を与えるすべてのアラートは、リポジトリの [Security] タブ{% endif %}またはリポジトリの依存関係グラフで確認できます。{% if currentVersion == "free-pro-team@latest" %}詳細については、「[リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」を参照してください。{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +デフォルト設定では、影響を受けるリポジトリの管理者権限を持つユーザに +新しい {% data variables.product.prodname_dependabot_alerts %} について通知します。{% endif %}{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} は、リポジトリで特定された脆弱性を公開することはありません。 {% data variables.product.prodname_dependabot_alerts %} を、自分が所有または管理者権限を持っているリポジトリで作業している追加のユーザや Team に表示することもできます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. +デフォルトでは、影響を受けるリポジトリで管理者権限を持つ人々にセキュリティアラートが送られます。 +{% data variables.product.product_name %} は、特定のリポジトリに対して特定された脆弱性を公表することはありません。 {% endif %} -{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} 詳細については、「[通知の配信方法を選択する](/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" %}詳細については、「[脆弱性のある依存関係に対する通知を設定する](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)」を参照してください。{% endif %} {% if currentVersion == "free-pro-team@latest" %} -### Further reading +また、 +{% data variables.product.prodname_advisory_database %} の特定の脆弱性に対応するすべての {% data variables.product.prodname_dependabot_alerts %} を確認できます。 詳しい情報については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ脆弱性を参照する](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)」を参照してください。 +{% endif %} -- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +### 参考リンク + +- 「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」 +- [リポジトリ内の脆弱な依存関係を表示・更新する](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository) +- [{% data variables.product.product_name %} によるデータの利用方法と保護方法を理解する](/categories/understanding-how-github-uses-and-protects-your-data){% endif %} 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 697b07c5d9..9df575d81c 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 @@ -13,7 +13,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} がリポジトリ内にある脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} アラートを生成し、リポジトリの [Security] タブに表示します。 {% data variables.product.product_name %} は、影響を受けるリポジトリのメンテナに、通知設定に従って新しいアラートについて通知します。{% else %}{% data variables.product.product_name %} がリポジトリ内の脆弱性のある依存関係を検出すると、セキュリティアラートを送信します。{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} は、すべてのパブリックリポジトリでデフォルト設定で有効になっています。 {% data variables.product.prodname_dependabot_alerts %} の場合、デフォルト設定では、特定の脆弱性ごとにグループ化された {% data variables.product.prodname_dependabot_alerts %} をメールで受信します。 {% endif %} -{% if currentVersion == "free-pro-team@latest" %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/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)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/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" %} 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 64f25bd77b..03ab7a3efe 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 @@ -1,6 +1,6 @@ --- -title: Configuring notifications -intro: 'Choose the type of activity on {% data variables.product.product_name %} that you want to receive notifications for and how you want these updates delivered.' +title: 通知を設定する +intro: '通知を受信する {% data variables.product.product_name %} のアクティビティのタイプと、これらの更新の配信方法を選択します。' redirect_from: - /articles/about-web-notifications - /format-of-notification-emails/ @@ -17,81 +17,85 @@ versions: free-pro-team: '*' enterprise-server: '>=2.21' github-ae: '*' +topics: + - notifications --- {% 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. +次の場所で、{% data variables.product.product_name %} のアクティビティに関する通知を受け取ることができます。 - - 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" or currentVersion ver_gt "2.22" %} and {% data variables.product.prodname_mobile %}{% endif %} + - {% data variables.product.product_name %} Web インターフェースの通知インボックス{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} + - {% data variables.product.product_name %}{% endif %} のインボックスと同期する {% data variables.product.prodname_mobile %} の通知インボックス + - {% 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" 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)." +{% data reusables.notifications-v2.notifications-inbox-required-setting %} 詳しい情報については、「[通知設定を選択する](#choosing-your-notification-settings)」を参照してください。 {% endif %} {% data reusables.notifications.shared_state %} -#### Benefits of the notifications inbox +#### 通知インボックスの利点 -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. - - Unsubscribe and remove a notification from your inbox. - - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.product.product_name %} from within the notifications inbox. - - See one of the latest reasons you're receiving a notification from your inbox with a `reasons` label. - - 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 +{% 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` クエリを使用します。 + - サブスクライブ解除して、インボックスから通知を削除する。 + - 通知が、通知インボックスから {% data variables.product.product_name %} で発生する Issue、プルリクエスト、または Team ディスカッションをプレビューする。 + - インボックスから `reasons` ラベルが付いた通知を受信する最新の理由の1つを確認する。 + - カスタムフィルタを作成して、必要なときにさまざまな通知にフォーカスする。 + - インボックスの通知をリポジトリまたは日付別にグループ化して、コンテキストの切り替えを減らし、概要をすばやく確認する。 {% 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)." +さらに、次を使用して、モバイルデバイスで通知を受信してトリアージすることができます。 +{% data variables.product.prodname_mobile %}. 詳しい情報については、「[GitHub for mobile を使用して通知設定を管理する](#managing-your-notification-settings-with-github-for-mobile)」または「[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)」を参照してください。 {% endif %} -#### Benefits of using an email client for notifications +#### 通知にメールクライアントを使用する利点 -One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)." +メールクライアントを使用する利点の 1 つは、メールクライアントのストレージ容量に応じて、すべての通知を無期限に保持できることです。 インボックスの通知は、**保存済**としてマークしていない限り、5 か月間だけ保持されます。 **保存済**の通知は、無期限に保持されます。 インボックスの保持ポリシーの詳細については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)」を参照してください。 -Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels. +メールクライアントに通知を送信すると、メールクライアントの設定に従ってインボックスをカスタマイズすることもできます。これには、カスタムラベルまたは色分けされたラベルを含めることができます。 -Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a verified personal email address. For more information, about your email customization options, see "[Customizing your email notifications](#customizing-your-email-notifications)." +メール通知では、受信する各種通知に柔軟に対応し、更新用にさまざまなメールアドレスを選択できます。 たとえば、リポジトリの特定の通知を検証済みの個人のメールアドレスに送信できます。 メールのカスタマイズオプションの詳細については、「[メール通知をカスタマイズする](#customizing-your-email-notifications)」を参照してください。 -### About participating and watching notifications +### 参加と Watch 対象の通知について -When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/github/building-a-strong-community/about-team-discussions)." +リポジトリの Watch 時は、そのリポジトリでのアクティビティの更新をサブスクライブしています。 同様に、特定の Team のディスカッションの Watch 時は、その Team のページですべての会話の更新をサブスクライブしていることになります。 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)を参照してください。 -To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)." +監視しているリポジトリを表示するには、[Watch ページ](https://github.com/watching)にアクセスします。 詳しい情報については「[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" %} -#### Configuring notifications +#### 通知を設定する {% endif %} -You can configure notifications for a repository on the repository page, or on your watching page.{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +リポジトリの通知は、リポジトリページまたは Watch ページで設定できます。 +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} リポジトリ内のリリースの通知のみを受信するか、リポジトリのすべての通知を無視するかを選択できます。{% endif %}{% if currentVersion == "free-pro-team@latest" %} -#### About custom notifications +#### カスタム通知について {% data reusables.notifications-v2.custom-notifications-beta %} -You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository. -{% endif %} For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)." +リポジトリの通知をカスタマイズできます。たとえば、リポジトリ内で複数のタイプのイベント (Issue、プルリクエスト、リリース、ディスカッション) の更新が発生した場合にのみ通知を受け取るか、リポジトリのすべての通知を無視するかを選択できます。 +{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. -#### 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. +#### 会話への参加 +会話にコメントしたり、あなたのユーザ名が @メンションされたりすると、会話に_参加_することになります。 デフォルトでは、会話に参加すると、会話に自動的にサブスクライブされます。 手動で参加した会話をサブスクライブ解除するには、Issue またはプルリクエストで [**Unsubscribe**] をクリックするか、通知インボックスの [**Unsubscribe**] オプションを使用します。 -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 %}. +Watch 中または参加中の会話について、メールまたは {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} と {% data variables.product.prodname_mobile %}{% endif %} の通知インボックスで通知を受け取るかどうかを選択できます。 -![Participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png) +![参加および Watch 対象の通知オプション](/assets/images/help/notifications-v2/participating-and-watching-options.png) -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". +例: + - 通知をメールに送信しない場合は、[**Email**] をオフにして、参加と Watch 対象の通知を行います。 + - 会話に参加したときにメールで通知を受信する場合は、[Participating] の下の [**Email**] を選択します。 -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. +Web{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} およびモバイル{% endif %} の Watch 通知または参加通知を有効にしない場合、通知インボックスは更新されません。 -### Customizing your email notifications +### メール通知をカスタマイズする -After enabling email notifications, {% data variables.product.product_name %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.product.product_name %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. +メール通知を有効化すると、{% data variables.product.product_name %} はコンテンツを HTML とプレーンテキストの両方で含むマルチパートのメールとして通知を送信します。 メール通知のコンテンツには、{% data variables.product.product_name %} のオリジナルのコンテンツに含まれる Markdown、@メンション、絵文字、ハッシュリンクなどがすべて含まれます。 メールでテキストだけを見たいなら、プレーンテキストのコピーだけを表示するようにメールクライアントを設定できます。 {% data reusables.notifications.outbound_email_tip %} @@ -99,129 +103,160 @@ After enabling email notifications, {% data variables.product.product_name %} wi {% if currentVersion == "free-pro-team@latest" %} -If you're using Gmail, you can click a button beside the notification email to visit the original issue or pull request that generated the notification. +Gmailを使っているなら、通知メールの横にあるボタンをクリックして、通知を生成したオリジナルのIssueあるいはプルリクエストにアクセスできます。 -![Buttons in Gmail](/assets/images/help/notifications/gmail-buttons.png) +![Gmailのボタン](/assets/images/help/notifications/gmail-buttons.png) {% endif %} -Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.product.product_name %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from: - - Comments on issues and pull requests. - - Pull request reviews. - - Pull request pushes. - - Your own updates, such as when you open, comment on, or close an issue or pull request. +参加中または Watch 中の会話の更新を送信するデフォルトのメールアドレスを選択します。 また、デフォルトのメールアドレスを使用するための更新を受信する {% data variables.product.product_name %} のアクティビティを指定することもできます。 たとえば、デフォルトのメールを次の場所から更新するかどうかを選択します。 + - Issue やプルリクエストへのコメント。 + - プルリクエストのレビュー. + - プルリクエストのプッシュ。 + - Issue やプルリクエストのオープン、コメント、クローズなどの、自分自身の操作による更新。 -Depending on the organization that owns the repository, you can also send notifications to different email addresses. Your organization may require the email address to be verified for a specific domain. For more information, see "[Choosing where your organization’s email notifications are sent](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)." +リポジトリを所有する Organization に応じて、さまざまなメールアドレスに通知を送信することもできます。 Organization では、特定のドメインのメールアドレスを検証する必要がある場合があります。 詳しい情報については、「[Organization のメール通知の送信先を選択する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)」を参照してください。 -You can also send notifications for a specific repository to an email address. For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)." +特定のリポジトリの通知をメールアドレスに送信することもできます。 詳しい情報については、「[リポジトリへのプッシュに対するメール通知について](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)」を参照してください。 {% data reusables.notifications-v2.email-notification-caveats %} -### Filtering email notifications +### メール通知のフィルタリング -Each email notification that {% data variables.product.product_name %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.product_name %} notifications, or certain types of {% data variables.product.product_name %} notifications. +{% data variables.product.product_name %} が送信する各メール通知には、ヘッダ情報が含まれています。 各メールのヘッダ情報には一貫性があるので、それを使ってメールクライアントですべての {% data variables.product.product_name %} 通知あるいは特定の種類の {% data variables.product.product_name %} 通知をフィルタリングしたりフォワードしたりできます。 -If you believe you're receiving notifications that don't belong to you, examine the `X-GitHub-Recipient` and `X-GitHub-Recipient-Address` headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user. +自分向けではない通知を受信していると思われる場合は、`X-GitHub-Recipient` および `X-GitHub-Recipient-Address` ヘッダを調べてください。 これらのヘッダは、対象の受信者を示しています。 メールの設定によっては、別のユーザ向けの通知を受け取る場合があります。 -Email notifications from {% data variables.product.product_name %} contain the following header information: +{% data variables.product.product_name %} からのメール通知には、以下のヘッダ情報が含まれています: -| Header | Information | -| --- | --- | -| `From` address | This address will always be {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | -| `To` field | This field connects directly to the thread.{% if currentVersion != "github-ae@latest" %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% if currentVersion != "github-ae@latest" %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} +| ヘッダ | 情報 | +| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `From` アドレス | このアドレスは常に{% if currentVersion == "free-pro-team@latest" %}「` notifications@github.com`」{% else %}「サイト管理者が設定した no-reply メールアドレス」{% endif %}になります。 | +| `To` フィールド | このフィールドはスレッドに直接接続します。 {% if currentVersion != "github-ae@latest" %}メールに返信すると、会話に新しいコメントが追加されます。{% endif %} +| `Cc` アドレス | あなたが会話をサブスクライブしていれば、{% data variables.product.product_name %}はあなたに `Cc` します。 2番目の`Cc`メールアドレスは、通知の理由にマッチします。 これらの通知理由に対するサフィックスは{% data variables.notifications.cc_address %}です。 通知の理由には以下のようなものがあります。
  • `assign`: 受信者はIssueあるいはプルリクエストに割り当てられました。
  • `author`: 受信者はIssueあるいはプルリクエストの作者です。
    • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
    • {% endif %}
  • `comment`: 受信者はIssueあるいはプルリクエストにコメントしました。
  • `manual`: 手作業でサブスクライブした Issue あるいはプルリクエストが更新されました。
  • `mention`: 受信者は Issue あるいはプルリクエストにメンションされました。
  • `push`: 受信者がサブスクライブしているプルリクエストに誰かがコミットしました。
  • `review_requested`: 受信者あるいは受信者がメンバーになっている Team にプルリクエストのレビューがリクエストされました。
    • {% if currentVersion != "github-ae@latest" %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} は、受信者がセキュリティのアラートを受け取るリポジトリに脆弱性を検出しました。
    • {% endif %}
  • `state_change`: 受信者がサブスクライブしている Issue あるいはプルリクエストがクローズもしくはオープンされました。
  • `subscribed`: 受信者が Watch しているリポジトリに更新がありました。
  • `team_mention`: 受信者が属している Team が Issue あるいはプルリクエストでメンションされました。
  • `your_activity`: 受信者が Issue あるいはプルリクエストをオープン、コメントあるいはクローズしました。
| +| `mailing list` フィールド | このフィールドはリポジトリの名前とそのオーナーを特定します。 このアドレスのフォーマットは常に`..{% data variables.command_line.backticks %}`となります。 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} +| `X-GitHub-Severity`フィールド | {% data reusables.repositories.security-alerts-x-github-severity %} 考えられる重大度レベルは次のとおりです。
  • `low`
  • `moderate`
  • `high`
  • `critical`
詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 +{% endif %} -### Choosing your notification settings +### 通知設定を選択する {% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %} -3. On the notifications settings page, choose how you receive notifications when: - - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %}{% if currentVersion == "enterprise-server@2.21" %} - - There are new security alerts in your repository. For more information, see "[Security alert notification options](#security-alert-notification-options)." {% endif %} {% if currentVersion == "free-pro-team@latest" %} - - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %} +3. 通知設定ページで、次の場合の通知の受信方法を選択します。 + - Watch しているリポジトリや Team ディスカッション、または参加している会話に更新がある場合。 詳しい情報については、「[参加と Watch 対象の通知について](#about-participating-and-watching-notifications)」を参照してください。 + - 新しいリポジトリにアクセスするか、新しい Team に参加した場合。 詳しい情報については、「[自動 Watch](#automatic-watching)」を参照してください。"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} + - リポジトリに新しい{% if page.version == 'dotcom' %} {% data variables.product.prodname_dependabot_alerts %} {% else %}セキュリティアラート{% endif %}があります。 詳しい情報については、「[{% data variables.product.prodname_dependabot_alerts %} 通知オプション](#dependabot-alerts-notification-options)」を参照してください。 {% endif %}{% if currentVersion == "enterprise-server@2.21" %} + - リポジトリに新しいセキュリティアラートがある場合。 There are new security alerts in your repository. {% endif %} {% if currentVersion == "free-pro-team@latest" %} + - {% data variables.product.prodname_actions %} で設定されたリポジトリにワークフロー実行の更新がある場合。 詳しい情報については、「[{% data variables.product.prodname_actions %} 通知オプション](#github-actions-notification-options)」を参照してください。{% endif %} -### Automatic watching +### 自動 Watch -By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options. +デフォルトでは、新しいリポジトリにアクセスすると、そのリポジトリの Watch が自動的に開始されます。 新しいチームに参加するたびに、更新が自動的にサブスクライブされ、その Team が@メンションされたときに通知を受け取ります。 自動でサブスクライブしない場合は、自動 Watch オプションの選択を解除できます。 - ![Automatic watching options](/assets/images/help/notifications-v2/automatic-watching-options.png) + ![自動 Watch オプション](/assets/images/help/notifications-v2/automatic-watching-options.png) -If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option. +「リポジトリを自動的に Watch する」が無効になっている場合、自分のリポジトリを自動的に Watch することはありません。 リポジトリページに移動して、Watch オプションを選択する必要があります。 -### Choosing where your organization’s email notifications are sent +### 個々のリポジトリの Watch 設定を行う -If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address. +リポジトリごとに Watch するどうかを選択できます。 また、Issue、プルリクエスト、ディスカッション (リポジトリで有効になっている場合)、{% endif %}新しいリリースなどの {% if currentVersion == "free-pro-team@latest" %} 特定のイベントタイプのみを通知するか、個々のリポジトリを完全に無視するかを選択できます。 + +{% data reusables.repositories.navigate-to-repo %} +2. 右上隅の [Watch] ドロップダウンメニューをクリックして、Watch オプションを選択します。 +{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} + ![リポジトリのドロップダウンメニューの Watch オプション](/assets/images/help/notifications-v2/watch-repository-options.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} + ![リポジトリのドロップダウンメニューの Watch オプション](/assets/images/help/notifications-v2/watch-repository-options-custom.png) +{% data reusables.notifications-v2.custom-notifications-beta %} +[**Custom**] オプションを使用すると、通知をさらにカスタマイズして、参加や @メンション に加えて、リポトリで特定のイベントが発生したときにのみ通知されるようにすることができます。 + + ![リポジトリのドロップダウンメニューのカスタム Watch オプション](/assets/images/help/notifications-v2/watch-repository-options-custom2.png) + +[Issue] を選択すると、リポジトリ内のすべての Issue (このオプションを選択する前からあった Issue を含む) の更新について通知され、サブスクライブされます。 このリポジトリのプルリクエストで @メンションされている場合は、その通知も受信し、Issue についての通知に加えて、その特定のプルリクエストの更新をサブスクライブします。 + +{% endif %} + +### Organization のメール通知の送信先を選択する + +Organization に所属している場合、Organization のアクティビティに関する通知の送信先にするメールアカウントを指定できます。 たとえば、職場の Organization に所属している場合、通知を個人のアドレスではなく、職場のアドレスに送信する方が良いでしょう。 {% data reusables.notifications-v2.email-notification-caveats %} {% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %} -3. Under "Default notification email", select the email address you'd like notifications sent to. -![Default notification email address drop-down](/assets/images/help/notifications/notifications_primary_email_for_orgs.png) -4. Click **Save**. +3. [Default notification email] で、通知の送信先にするメールアドレスを選択します。 + ![デフォルトの通知メールアドレスのドロップダウン](/assets/images/help/notifications/notifications_primary_email_for_orgs.png) +4. [**Save**] をクリックします。 -#### Customizing email routes per organization +#### Organization ごとにメールの送信先を設定する -If you are a member of more than one organization, you can configure each one to send notifications to any of{% if currentVersion == "free-pro-team@latest" %} your verified email addresses{% else %} the email addressed you've added to your {% data variables.product.product_name %} account{% endif %}. {% if currentVersion == "free-pro-team@latest" %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} +複数の Organization のメンバーである場合は、検証済みのメールアドレス {% else %} {% data variables.product.product_name %}アカウント{% endif %}に追加したメールアドレスのいずれかに通知を送信するように各 Organization を設定できます。 {% if currentVersion == "free-pro-team@latest" %} 詳しい情報については、「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。{% endif %} {% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %} -3. Under "Custom routing," find your organization's name in the list. -![List of organizations and email addresses](/assets/images/help/notifications/notifications_org_emails.png) -4. Click **Edit** next to the email address you want to change. -![Editing an organization's email addresses](/assets/images/help/notifications/notifications_edit_org_emails.png) -5. Select one of your verified email addresses, then click **Save**. -![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) +3. [Custom routing] で、一覧から Organization の名前を見つけます。 + ![Organization とメールアドレスの一覧](/assets/images/help/notifications/notifications_org_emails.png) +4. 変更したいアドレスの隣にある [**Edit**] をクリックします。 ![Organization のメールアドレスの編集](/assets/images/help/notifications/notifications_edit_org_emails.png) +5. 検証済みメールアドレスのうち 1 つを選択し、[**Save**] をクリックします。 + ![Organization ごとのメールアドレス切り替え](/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 %} notification options +### {% data variables.product.prodname_dependabot_alerts %} の通知オプション {% else %} -### Security alert notification options +### Security alert options {% endif %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %} {% data reusables.notifications.vulnerable-dependency-notification-options %} +利用可能な通知の配信方法の詳細、および次の通知を最適化するためのアドバイスについては -For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %} セキュリティアラート{% endif %}からの通知を減らす方法については、「[脆弱性のある依存関係の通知を設定する](/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 %} notification options +### {% data variables.product.prodname_actions %} の通知オプション -Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs. +{% data variables.product.prodname_actions %} で設定されている、Watch しているリポジトリのワークフロー実行更新を受信する方法を選択します。 失敗したワークフローの実行に関する通知のみを受信するように選択することもできます。 - ![Notification options for {% data variables.product.prodname_actions %}](/assets/images/help/notifications-v2/github-actions-notification-options.png) + ![{% 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" %} -### Enabling push notifications with {% data variables.product.prodname_mobile %} +### {% 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. +{% data variables.product.prodname_mobile %} をインストールすると、自動的に Web 通知が有効になります。 アプリケーション内で、次のイベントのプッシュ通知を有効にできます。 +- ダイレクトメンション +- Issue またはプルリクエストへの割り当て +- プルリクエストのレビューをリクエスト +- デプロイメントの承認をリクエスト -You can only receive notifications for pushes to repositories on {% data variables.product.prodname_mobile %} at this time. +{% data variables.product.prodname_mobile %} がモバイルデバイスにプッシュ通知を送信するタイミングをスケジュール設定することもできます。 {% data reusables.mobile.push-notifications-on-ghes %} -#### Enabling push notifications with {% data variables.product.prodname_ios %} +#### {% data variables.product.prodname_ios %} で通知設定を管理する -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 iOS](/assets/images/help/mobile/ios-settings-icon.png) -3. To update your notification settings, tap **Push notifications**. -4. To turn on push notifications for direct mentions, use the **Direct Mentions** toggle. +1. 下部のメニューで、[**Profile**] をタップします。 +2. 設定を表示するには、{% octicon "gear" aria-label="The Gear icon" %} をタップします。 +3. 通知設定を更新するには、[**Notifications**] をタップしてから、トグルを使用して、好みの種類のプッシュ通知を有効または無効にします。 +4. オプションで、{% data variables.product.prodname_mobile %} がモバイルデバイスにプッシュ通知を送信するタイミングをスケジュールするには、[**Working Hours**] をタップし、[**Custom working hours**] トグルを使用して、プッシュ通知を受信するタイミングを選択します。 -{% if currentVersion == "free-pro-team@latest" %} -#### Enabling push notifications with {% data variables.product.prodname_android %} +#### {% data variables.product.prodname_android %} で通知設定を管理する + +1. 下部のメニューで、[**Profile**] をタップします。 +2. 設定を表示するには、{% octicon "gear" aria-label="The Gear icon" %} をタップします。 +3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications. +4. オプションで、{% data variables.product.prodname_mobile %} がモバイルデバイスにプッシュ通知を送信するタイミングをスケジュールするには、[**Working Hours**] をタップし、[**Custom working hours**] トグルを使用して、プッシュ通知を受信するタイミングを選択します。 + +### {% data variables.product.prodname_mobile %} を使用して個々のリポジトリの Watch 設定をする + +リポジトリごとに Watch するどうかを選択できます。 また、Issue、プルリクエスト、ディスカッション (リポジトリで有効になっている場合)、{% endif %}新しいリリースなどの {% if currentVersion == "free-pro-team@latest" %} 特定のイベントタイプのみを通知するか、個々のリポジトリを完全に無視するかを選択できます。 + +1. {% data variables.product.prodname_mobile %}で、リポジトリのメインページにアクセスしてください。 +2. [**Watch**] をタップします。 ![{% data variables.product.prodname_mobile %} の Watch ボタン](/assets/images/help/notifications-v2/mobile-watch-button.png) +3. 通知を受け取るアクティビティを選択するには、目的の Watch 設定をタップします。 ![{% data variables.product.prodname_mobile %} の Watch 設定ドロップダウンメニュー](/assets/images/help/notifications-v2/mobile-watch-settings.png) -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/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index fa4321a743..0f5ab7acd2 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -1,6 +1,6 @@ --- -title: Viewing your subscriptions -intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.' +title: サブスクリプションを表示する +intro: '通知の送信元と通知のボリュームを把握するため、定期的にサブスクリプションを確認し、リポジトリを Watch することをお勧めします。' redirect_from: - /articles/subscribing-to-conversations/ - /articles/unsubscribing-from-conversations/ @@ -18,86 +18,66 @@ versions: free-pro-team: '*' enterprise-server: '>=2.21' github-ae: '*' +topics: + - notifications --- -You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)." +{% data variables.product.product_name %} で進行中のアクティビティのサブスクリプションの通知を受け取ります。 会話をサブスクライブする理由はたくさんあります。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)」を参照してください。 -We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." +健全な通知ワークフローの一環として、サブスクリプションの監査とサブスクライブ解除をお勧めします。 サブスクライブ解除に関する詳しい情報については、「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。 -### Diagnosing why you receive too many notifications +### 通知過多の理由を診断する -When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository. +インボックスの通知が多すぎて管理できない場合は、サブスクリプションが多すぎないか確認したり、通知設定を変更して、サブスクリプションと受信する通知の種類を減らしたりすることを検討してください。 たとえば、設定を無効にして、チームまたはリポジトリに参加するたびにすべてのリポジトリとすべての Team ディスカッションを自動的に監視することを検討できます。 -![Automatic watching](/assets/images/help/notifications-v2/automatic-watching-example.png) +![自動 Watch](/assets/images/help/notifications-v2/automatic-watching-example.png) -For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)." +詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)」を参照してください。 -To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)." +リポジトリのサブスクリプションの概要を確認するには、「[Watch しているリポジトリを確認する](#reviewing-repositories-that-youre-watching)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. +**参考:** [Watch ページ](https://github.com/watching)または {% data variables.product.prodname_dotcom_the_website %} の任意のリポジトリページにある [**Watch/Unwatch**] ドロップダウンリストの [**Custom**] オプションを使用して、通知するイベントの種類を選択できます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)」を参照してください。 {% endtip %} {% endif %} -Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." +過去に Watch することを選択したリポジトリが忘れらていることが多くあります。 「Watched repositories」ページから、リポジトリから素早く Watch 解除することができます。 サブスクライブ解除する方法について詳しくは、{% data variables.product.prodname_blog %} の「[Watch 解除の推奨](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)」および「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。 トリアージワークフローを作成して、受信する通知を支援することもできます。 トリアージワークフローのガイダンスについては、「[通知をトリアージするためのにワークフローをカスタマイズする](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。 -### Reviewing all of your subscriptions +### サブスクリプションのリストを確認する {% data reusables.notifications.access_notifications %} -1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**. - ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png) +1. 左側のサイドバーの、通知元のリポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[**Subscriptions**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png) -2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for. +2. フィルタとソートを使用して、サブスクリプションのリストを絞り込み、通知の受信を希望しない会話のサブスクリプションを解除します。 - ![Subscriptions page](/assets/images/help/notifications-v2/all-subscriptions.png) + ![サブスクリプションページ](/assets/images/help/notifications-v2/all-subscriptions.png) {% tip %} -**Tips:** -- To review subscriptions you may have forgotten about, sort by "least recently subscribed." +**参考:** +- 忘れている可能性のあるサブスクリプションを確認するには、[least recently subscribed] でソートします。 -- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu. +- 引き続き通知が受信可能なリポジトリのリストを確認するには、[filter by repository] ドロップダウンメニューのリポジトリリストを参照します。 {% endtip %} -### Reviewing repositories that you're watching +### Watch しているリポジトリを確認する -1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**. - ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png) -2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository. +1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンメニューを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png) +2. Watch しているリポジトリを評価し、それらの更新がまだ関連していて有用であるかどうかを判断します。 リポジトリを Watch すると、そのリポジトリのすべての会話が通知されます。 {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png) + ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% if currentVersion == "free-pro-team@latest" %} - ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png) + ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications-custom.png) {% endif %} {% tip %} - **Tip:** Instead of watching a repository, consider only receiving notifications {% if currentVersion == "free-pro-team@latest" %}when there are updates to issues, pull requests, releases or discussions (if enabled for the repository), or any combination of these options,{% else %}for releases in a repository,{% endif %} or completely unwatching a repository. - - When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned. + **参考:** リポジトリを Watch する代わりに、リポジトリ内のリリースについて、Issue、プルリクエスト、リリースまたはディスカッション (リポジトリで有効になっている場合){% if currentVersion == "free-pro-team@latest" %}、または{% else %}リポジトリ内のリリースの場合{% endif %}、これらのオプションの任意の組み合わせが更新された場合にのみ通知を受信するか、リポジトリを完全に Watch 解除するかを検討してください。 + + リポジトリを Watch 解除しても、@メンションされたときやスレッドに参加しているときには通知を受信することができます。 特定のイベントタイプの通知を受信するように設定すると、リポジトリにこれらのイベントタイプが更新された場合、スレッドに参加している場合、または参加している自分または Team が @メンションされた場合にのみ通知されます。 {% endtip %} - -### Configuring your watch settings for an individual repository - -You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository. - -{% data reusables.repositories.navigate-to-repo %} -2. In the upper-right corner, click the "Watch" drop-down menu to select a watch option. -{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} - ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png) -{% data reusables.notifications-v2.custom-notifications-beta %} -The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. - - ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2.png) - -If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. - -{% endif %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 7671e3d515..7b068d8ece 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,9 +12,9 @@ topics: {% 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)」を参照してください。 -If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_actions %} の使用を有効にして支払うことができます。 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。 利用時間 (分) は毎月リセットされますが、ストレージはリセットされません。 @@ -57,7 +57,7 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr 月末に、{% data variables.product.prodname_dotcom %}はアカウントに含まれている量に対して使用された分とストレージのコストを計算します。 たとえば、Organizationが{% 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. + - 単価 $0.008 で 3,000 Linux 分 = $24。 - 単価$0.016で2,000 Windows分 = $32。 月末に、{% data variables.product.prodname_dotcom %}はデータ転送を最も近いGBに丸めます。 @@ -77,6 +77,6 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr {% 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/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index dcbd4b2cb6..9c15e552bf 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -16,7 +16,7 @@ topics: {% data reusables.package_registry.container-registry-beta-billing-note %} -Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_registry %} の使用を有効にして支払うことができます。 For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_registry %} の使用を有効にして支払うことができます。 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。 データ転送は毎月リセットされますが、ストレージはリセットされません。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md index 9a2a6c8f81..86540a4445 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security.md @@ -31,21 +31,21 @@ Enterprise アカウントの {% data variables.product.prodname_GH_advanced_sec ### {% data variables.product.prodname_GH_advanced_security %} のライセンス利用を管理する -単一のリポジトリまたは Organization 内のすべてのリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にすると、{% data variables.product.company_short %} は、使用する追加のシートの数を示し、確認を求めるプロンプトを表示します。 If you disable access to {% data variables.product.prodname_GH_advanced_security %}, any seats used by "unique" committers are freed up. This makes it easy to understand the impact of your changes on the use of your license. +単一のリポジトリまたは Organization 内のすべてのリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にすると、{% data variables.product.company_short %} は、使用する追加のシートの数を示し、確認を求めるプロンプトを表示します。 {% data variables.product.prodname_GH_advanced_security %} へのアクセスを無効にすると、「一意」のコミッターが使用するシートが解放されます。 これによって、ライセンスの使用に関する変更のインパクトを簡単に理解できます。 -If you are over your license limit, {% data variables.product.prodname_GH_advanced_security %} continues to work on all repositories where it is already enabled. However, in organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled for new repositories, repositories will be created with the feature disabled. In addition, the option to enable {% data variables.product.prodname_GH_advanced_security %} for existing repositories will not be available. If you change the visibility of a public repository to private then {% data variables.product.prodname_GH_advanced_security %} will be disabled for that repository. +ライセンス制限を超えている場合、{% data variables.product.prodname_GH_advanced_security %} はすでに有効になっているすべてのリポジトリで引き続き動作します。 ただし、{% data variables.product.prodname_GH_advanced_security %} が新しいリポジトリに対して有効になっている Organization では、リポジトは機能が無効の状態で作成されます。 さらに、既存のリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にするオプションは使用できなくなります。 パブリックリポジトリの可視性をプライベートに変更すると、そのリポジトリの {% data variables.product.prodname_GH_advanced_security %} は無効になります。 -As soon as you free up some seats, by disabling {% data variables.product.prodname_GH_advanced_security %} for some repositories or by increasing your license size, the options for enabling {% data variables.product.prodname_GH_advanced_security %} will work again as normal. +一部のリポジトリで {% data variables.product.prodname_GH_advanced_security %} を無効にするか、ライセンスサイズを増やすと、一部のシートを解放した直後に {% data variables.product.prodname_GH_advanced_security %} を有効にするオプションが通常どおり動作します。 -You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +Enterprise アカウントが所有する Organization による {% data variables.product.prodname_advanced_security %} の使用を許可または禁止するポリシーを適用できます。 詳しい情報については、「[Enterprise アカウントに {% data variables.product.prodname_advanced_security %} のポリシーを適用する](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account)」を参照してください。 -For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage)." +ライセンスの使用状況の表示について詳しくは、「[{% data variables.product.prodname_GH_advanced_security %} の使用状況を表示する](/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage)」を参照してください。 -### Getting the most out of your {% data variables.product.prodname_GH_advanced_security %} license +### {% data variables.product.prodname_GH_advanced_security %} ライセンスを最大限に活用する -When you decide which repositories and organizations to prioritize for {% data variables.product.prodname_GH_advanced_security %}, you should review them and identify: +{% data variables.product.prodname_GH_advanced_security %} の優先順位を付けるリポジトリと Organization を決定するときは、それらを確認して次のことを特定する必要があります。 -- Codebases that are the most critical to your company's success. These are the projects for which the introduction of vulnerable code, hard-coded secrets, or vulnerable dependencies would have the greatest impact on your company. -- Codebases with the highest commit frequency. These are the most actively developed projects, consequently there is a higher risk that security problems could be introduced. +- 会社の成功にとって最も重要なコードベース。 これらは、脆弱なコード、ハードコードされたシークレット、または脆弱な依存関係の導入が会社に最大の影響を与えるプロジェクトです。 +- コミット頻度が最も高いコードベース。 これらは最も積極的に開発されたプロジェクトであるため、セキュリティの問題が発生するリスクが高くなります。 -When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, you should assess which other codebases you could add without adding any extra unique committers and using up more seats on your license. After this, review the next most important and busy codebases. If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}. +これらの Organization またはリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} を有効にした場合、一意のコミッターを追加したり、ライセンスのシートを使い切ったりせずに、追加できる他のコードベースを評価する必要があります。 この後、次に重要でビジーなコードベースを確認します。 ライセンスのシート数を増やす場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 62c4819143..865c8bb426 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -20,11 +20,11 @@ topics: ### 個人アカウントへの割引 -{% 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/explore-the-benefits-of-teaching-and-learning-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/explore-the-benefits-of-teaching-and-learning-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/explore-the-benefits-of-teaching-and-learning-with-github-education/use-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/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」を参照してください。 また、学生のために教材をお求めいただくこともできます。 詳しい情報については [{% data variables.product.prodname_education %}](https://education.github.com/) にアクセスして下さい。 ### 非営利目的や図書館への割引 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md index b739e42f82..71ca079baf 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md @@ -11,22 +11,22 @@ topics: {% 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 %} ### スポンサーシップをダウングレードする {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### スポンサーシップをキャンセルする {% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} +{% data reusables.user_settings.billing_plans %} {% data reusables.sponsors.billing-switcher %} -{% data reusables.user_settings.subscriptions-tab %} 3. [{% data variables.product.prodname_sponsors %}] の、スポンサードオープンソースコントリビューターの右で、あなたがスポンサーした額の隣にある{% octicon "triangle-down" aria-label="The down triangle octicon" %}をクリックし、[**Cancel sponsorship**] をクリックします。 ![[Cancel sponsorship] ボタン](/assets/images/help/billing/edit-sponsor-billing.png) 4. スポンサーシップのキャンセルに関する情報を確認してから、[**OK**] をクリックします。 ![キャンセルの確認ボックス](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md index dc891c2e40..19aefd0406 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security.md @@ -1,6 +1,6 @@ --- -title: Managing licensing for GitHub Advanced Security -intro: 'You can view and manage your use of seats on a license for {% data variables.product.prodname_advanced_security %}.' +title: GitHub Advanced Security のライセンスを管理する +intro: '{% data variables.product.prodname_advanced_security %} のライセンスのシートの使用を表示および管理できます。' mapTopic: true product: '{% data reusables.gated-features.ghas %}' versions: diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 7f6c5b2838..1894da14dd 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,13 +14,13 @@ topics: {% 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)」を参照してください。 -If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_actions %} の使用を有効にして支払うことができます。 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。 -As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. たとえば、Organizationで {% data variables.product.prodname_team %} を使用していて超過を許可しておらず、月あたりのストレージ使用量が1.9GBから2.1GBに増えるワークフローアーティファクトを作成した場合、ストレージは製品に含まれる2GBをわずかに超えることになります。 +$0 以外の利用上限を設定すると、直ちに現在の支払い期間中の超過分について責任が生じます。 たとえば、Organizationで {% 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 %} に対する利用上限を管理する diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 292cf1b510..d89618ab96 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,13 +14,13 @@ topics: {% 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)」を参照してください。 -Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_registry %} の使用を有効にして支払うことができます。 For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプション ID を Enterprise アカウントに接続して、アカウントを含む金額を超える {% data variables.product.prodname_registry %} の使用を有効にして支払うことができます。 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。 -As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. たとえば、Organizationで {% data variables.product.prodname_team %} を使用していて超過を許可しておらず、月あたりのストレージ使用量が1.9GBから2.1GBに増えるプライベートパッケージの新しいバージョンを発行した場合、ストレージは製品に含まれる2GBをわずかに超えることになります。 +$0 以外の利用上限を設定すると、直ちに現在の支払い期間中の超過分について責任が生じます。 たとえば、Organizationで {% 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 %} に対する利用上限を管理する diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md index 5e47863978..4111b1061a 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md @@ -14,6 +14,8 @@ topics: {% data variables.product.product_name %}では、クーポンを適用する前にアカウントの支払いをした場合の返金はできません。 また、適用先のアカウントを間違えた場合にも、利用したクーポンの移譲や新たなクーポンの発行はできません。 クーポンを利用する前に、クーポンを正しいアカウントに適用していることを確認してください。 +{% data reusables.dotcom_billing.coupon-expires %} + クーポンは {% data variables.product.prodname_marketplace %}アプリケーションの有料プランには適用できません。 ### 個人アカウントでクーポンを利用する diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md index 00eac8f4e7..5d584bb002 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md @@ -15,6 +15,8 @@ topics: {% data variables.product.product_name %} のクーポン付きプランの支払いをしていて、{% data variables.product.product_name %} の[他の有料機能や製品](/articles/about-billing-on-github)の支払い方法を使用していない場合、クレジットカードや PayPal の情報を削除できます。 +{% data reusables.dotcom_billing.coupon-expires %} + {% tip %} **ヒント:** 他の有料機能や製品のプランがなくて[アカウントを無料製品にダウングレード](/articles/downgrading-your-github-subscription)した場合、支払い情報は自動的に削除されます。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md index 10a50bdaa8..fadc4a6b0a 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md @@ -11,7 +11,7 @@ topics: {% data reusables.sponsors.org-sponsors-release-phase %} -### About sponsorship upgrades +### スポンサーシップのアップグレードについて スポンサーシップ層をアップグレードした場合、その変更は直ちに有効になります。 {% data reusables.sponsors.prorated-sponsorship %} @@ -19,5 +19,6 @@ topics: {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md index 9f9b180612..3e0b4c1014 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -59,7 +59,7 @@ Organization を {% data variables.product.prodname_free_team %} から {% data #### {% data variables.product.prodname_ghe_cloud %} を使用する Organization の次のステップ -Organization を {% data variables.product.prodname_ghe_cloud %} にアップグレードした場合は、ここで Organization の ID とアクセス管理を設定できます。 詳細は「[Organization で SAML シングルサインオンを管理する](/articles/managing-saml-single-sign-on-for-your-organization)」を参照してください。 +Organization を {% data variables.product.prodname_ghe_cloud %} にアップグレードした場合は、ここで Organization の ID とアクセス管理を設定できます。 詳細は「[Organization で SAML シングルサインオンを管理する](/organizations/managing-saml-single-sign-on-for-your-organization)」を参照してください。 {% data variables.product.prodname_ghe_cloud %} で Enterprise アカウントを使いたい場合は、{% data variables.contact.contact_enterprise_sales %} に連絡してください。 詳細は「[Enterprise アカウントについて](/articles/about-enterprise-accounts)」を参照してください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md index 5408603476..791e1480eb 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md @@ -1,24 +1,24 @@ --- -title: Viewing your GitHub Advanced Security usage -intro: 'You can view and manage usage of your {% data variables.product.prodname_GH_advanced_security %} license.' -permissions: Organization and enterprise owners can manage access to {% data variables.product.prodname_GH_advanced_security %} for their organization or enterprise organizations. +title: GitHub Advanced Security の使用状況を表示する +intro: '{% data variables.product.prodname_GH_advanced_security %} ライセンスの使用状況を表示および管理できます。' +permissions: Organization および Enterprise の所有者は、Organization または Enterprise の Organization の {% data variables.product.prodname_GH_advanced_security %} へのアクセスを管理できます。 product: '{% data reusables.gated-features.ghas %}' redirect_from: /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account versions: free-pro-team: '*' --- -{% data variables.product.prodname_GH_advanced_security %}の各ライセンスは、それらの機能を使用できるアカウントもしくはシートの最大数を指定します。 Periodically you should check that your use is within your license capacity. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)." +{% data variables.product.prodname_GH_advanced_security %}の各ライセンスは、それらの機能を使用できるアカウントもしくはシートの最大数を指定します。 定期的に、使用がライセンス容量の容量内であることを確認する必要があります。 詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} Enterprise ライセンスのライセンスについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)」を参照してください。 -### Viewing and managing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account +### Enterprise アカウントの {% data variables.product.prodname_GH_advanced_security %} ライセンス使用状況の表示と管理 -You can check how many seats your license includes and how many of them are currently used on the "Enterprise licensing" page. +ライセンスに含まれるシート数と、現在使用されているシート数は、[Enterprise ライセンス] ページで確認できます。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} - The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) -4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png) -5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 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)." + 「{% data variables.product.prodname_GH_advanced_security %}」セクションには、現在の使用状況の詳細が表示されます。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) シートが不足すると、セクションが赤色になります。 {% data variables.product.prodname_GH_advanced_security %} の使用を減らすか、シートを追加購入する必要があります。 詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} Enterprise ライセンスのライセンスについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)」を参照してください。 ![Enterprise ライセンス設定内の {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) +4. 必要に応じて、Organization ごとの使用状況の詳細な内訳を表示するには、左サイドバーで [**Billing**] をクリックします。 ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) [{% data variables.product.prodname_GH_advanced_security %}] セクションで、各 Organization のコミッターと一意のコミッター数を確認できます。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png) +5. 必要に応じて、所有者である Organization の名前をクリックして、Organization のセキュリティと分析の設定を表示します。 ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) +6. [Security & analysis] 設定ページで、[{{% data variables.product.prodname_GH_advanced_security %} repositories] セクションまでスクロールして、この Organization のリポジトリごとの使用状況の詳細を確認します。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 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 index 74618bb76e..969c6a2bed 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### 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.dotcom-saml-explanation %} 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。 {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md index c54788b388..34395d8f95 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -36,7 +36,7 @@ Enterprise のワークフローをすべて無効にすることも、Organizat {% 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. ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) +1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) ### プライベートリポジトリのフォークのワークフローを有効にする 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 19e26f8bdf..b93707073e 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 @@ -49,7 +49,7 @@ Enterprise のオーナーは、特定の IP アドレスに対する許可リ {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -許可 IP アドレスを、Organization ごとに設定することもできます。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)」を参照してください。 +許可 IP アドレスを、Organization ごとに設定することもできます。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)」を参照してください。 #### 許可 IP アドレスを追加する diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md index e6884e596f..0f3be3ba51 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md @@ -15,7 +15,7 @@ topics: ### Team ディスカッションでポリシーを施行する -自分の Enterprise アカウントによって所有されているすべての Organization 全体で、Team ディスカッションを有効または無効にしたり、オーナーに Organization レベルで設定を管理させたりできます。 詳しい情報については[Team ディスカッションについて](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)を参照してください。 +自分の Enterprise アカウントによって所有されているすべての Organization 全体で、Team ディスカッションを有効または無効にしたり、オーナーに Organization レベルで設定を管理させたりできます。 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions/)を参照してください。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 44d33a6f8b..5291beb4ae 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 @@ -27,9 +27,9 @@ The total quantity of your licenses for your enterprise on {% data variables.pro 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 %} で Enterprise アカウントを作成します。 すでに {% data variables.product.prodname_dotcom_the_website %} に Enterprise アカウントをお持ちの場合、または不明な場合は、営業チームにお問い合わせください。 -2. {% data variables.product.prodname_vss_admin_portal_with_url %} のサブスクライバーに {% data variables.product.prodname_vss_ghe %} のライセンスを割り当てます。 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. +2. {% data variables.product.prodname_vss_admin_portal_with_url %} のサブスクライバーに {% data variables.product.prodname_vss_ghe %} のライセンスを割り当てます。 ライセンス割り当ての詳細については、Microsoft Docs の「[{% data variables.product.prodname_enterprise %} を使用した {% data variables.product.prodname_vs %} プランの管理](https://docs.microsoft.com/visualstudio/subscriptions/assign-github)」を参照してください。 -3. {% data variables.product.prodname_dotcom_the_website %} で、Enterprise アカウントが所有する Organization を少なくとも 1 つ作成します。 For more information, see "[Adding organizations to your enterprise account](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)." +3. {% data variables.product.prodname_dotcom_the_website %} で、Enterprise アカウントが所有する Organization を少なくとも 1 つ作成します。 詳しい情報については、「[Enterprise アカウントに Organization を追加する](/github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account)」参照してください。 ### サブスクライバーを招待して {% data variables.product.prodname_enterprise %} を使用する @@ -39,7 +39,7 @@ Organization owners can invite new members to an organization by email address. While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. -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)." +For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/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)." ### {% data variables.product.prodname_enterprise %} ライセンスを表示する @@ -49,4 +49,4 @@ For more information, see "[Inviting users to join your organization](/github/se ### 参考リンク -- [Introducing Visual Studio subscriptions with GitHub Enterprise](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in the Microsoft Docs +- Microsoft Docs の [GitHub Enterprise による Visual Studio サブスクリプションの紹介](https://docs.microsoft.com/visualstudio/subscriptions/access-github) 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 index b8d261eb3c..9ffc28d658 100644 --- 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 @@ -19,7 +19,7 @@ If you use Azure AD as your IdP, you can enable team synchronization for your en {% 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)」を参照してください。 +Organization ごとの Team 同期の設定と管理も可能です。 詳細は「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照してください。 ### 必要な環境 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md index aba090b0c5..49feb770aa 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -11,13 +11,13 @@ topics: ### About email restrictions for your enterprise account -When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization. ### Restricting email notifications for your enterprise account -Before you can restrict email notifications for your enterprise account, you must verify at least one domain for the enterprise account. For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)." +Before you can restrict email notifications for your enterprise account, you must verify at least one domain for the enterprise account. 詳しい情報については、「[Enterprise アカウントのドメインを検証する](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)」を参照してください。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md index 2e03242dc5..ecf76c421e 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -12,9 +12,9 @@ topics: - enterprise --- -### 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. 詳しい情報については [Organization のドメインの検証](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)を参照してください。 +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. 詳しい情報については [Organization のドメインの検証](/organizations/managing-organization-settings/verifying-your-organizations-domain)を参照してください。 After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %} @@ -22,7 +22,7 @@ Organization owners will be able to verify the identity of organization members After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account to approved domains](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)." -Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." ### Verifying your enterprise account's domain @@ -34,7 +34,7 @@ To verify your enterprise account's domain, you must have access to modify domai 1. [**Add a domain**] をクリックします。 ![[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/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 d7a6e53399..8a51d468b0 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 @@ -53,4 +53,4 @@ Enterprise アカウントに対する SAML シングルサインオンを有効 ### 参考リンク -- [組織へのメンバーの SAML アクセスの表示と管理](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) +- [組織へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md index 8b43051bf4..cb52432203 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -14,7 +14,7 @@ topics: Organization の説明、場所、Web サイト、メールアドレスをオプションで追加することや、重要なリポジトリをページの上部にピン止めすることもできます。 -{% if currentVersion == "free-pro-team@latest" %}Organization の ID を確認し、Organization のプロファイルページに「Verified」のバッジを表示するには、{% data variables.product.product_name %} を使用して Organization のドメインを検証する必要があります。 詳しい情報については [Organization のドメインの検証](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)を参照してください。 +{% if currentVersion == "free-pro-team@latest" %}Organization の ID を確認し、Organization のプロファイルページに「Verified」のバッジを表示するには、{% data variables.product.product_name %} を使用して Organization のドメインを検証する必要があります。 詳しい情報については [Organization のドメインの検証](/organizations/managing-organization-settings/verifying-your-organizations-domain)を参照してください。 ![検証済み Organization プロフィールページのサンプル](/assets/images/help/profile/org_profile_verified.png) {% else %} @@ -23,4 +23,4 @@ Organization の説明、場所、Web サイト、メールアドレスをオプ ### 参考リンク -- [Organization について](/github/setting-up-and-managing-organizations-and-teams/about-organizations) +- [Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index eabd9dc7d6..f59572b686 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -1,12 +1,14 @@ --- title: プライベートコントリビューションをプロフィールで公開または非公開にする -intro: '{% data variables.product.product_name %} プロフィールには、過去 1 年間のリポジトリコントリビューションのグラフが表示されます。 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 %} プロフィールには、過去 1 年間のリポジトリコントリビューションのグラフが表示されます。 パブリックリポジトリ{% endif %}からのアクティビティに加えて、{% 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 %}からの匿名化されたアクティビティを表示するように選択できます。' redirect_from: - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - プロフィール --- プライベートコントリビューションを公開しても、あなたが作業しているプライベートリポジトリへのアクセス権がないユーザーがあなたのプライベートコントリビューションを見ることはできません。 かわりに、特定の日におけるプライベートコントリビューションの数だけを見ることができます。 パブリックコントリビューションには、詳細な情報が含まれます。 詳細は、「[プロフィールページ上にコントリビューションを表示する](/articles/viewing-contributions-on-your-profile-page)」を参照してください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 2732b6688d..b6957290d5 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/ja-JP/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 %} プロフィールには、ピン止めされたリポジトリと、{% endif %}過去 1 年間のリポジトリのコントリビューションのグラフが表示されます。' redirect_from: - /articles/viewing-contributions/ - /articles/viewing-contributions-on-your-profile-page/ @@ -9,13 +9,15 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - プロフィール --- -{% 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 %} @@ -25,15 +27,17 @@ versions: - リポジトリのデフォルトブランチまたは `gh-pages` ブランチにコミットすること - Issue を開くこと +- ディスカッションをオープンすること +- ディスカッションに回答すること - プルリクエストを提案すること -- 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) @@ -54,11 +58,11 @@ versions: #### 特定の時期からのコントリビューションを表示する - ある日の正方形をクリックすると、その 24 時間の間になされたコントリビューションが表示されます。 -- *Shift* を押しながら、別の日の正方形をクリックすると、その期間中になされたコントリビューションが表示されます。 +- *Shift* を押しながら、別の日の四角をクリックすると、その期間中に行われたコントリビューションが表示されます。 {% note %} -**メモ:** コントリビューションカレンダーでは 1 か月の範囲まで選ぶことができます。 もっと長い期間を選択した場合、1 か月分のコントリビューションのみが表示されます。 +**メモ:** コントリビューションカレンダーでは 1 か月の範囲まで選ぶことができます。 より長期間を選択した場合、1 か月分のコントリビューションのみが表示されます。 {% endnote %} @@ -86,9 +90,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/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 ab5d12ac01..fe0fcde06a 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 @@ -13,9 +13,9 @@ topics: ### カウントされるコントリビューション -#### 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. +Issue、プルリクエスト、およびディスカッションは、フォークではなくスタンドアロンリポジトリで開かれた場合、コントリビューショングラフに表示されます。 #### コミット 次の条件の**すべて**を満たしている場合、コミットはコントリビューショングラフに表示されます。 @@ -25,7 +25,7 @@ Issues, pull requests and discussions will appear on your contribution graph if - リポジトリのデフォルトブランチ内 - `gh-pages` ブランチ (プロジェクトサイトのリポジトリの場合) 内 -プロジェクトサイトに関する詳しい情報については「[{% data variables.product.prodname_pages %}について](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)」を参照してください。 +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." また、次のうち**少なくとも 1 つ**が該当する必要があります: - リポジトリのコラボレーターであるか、またはリポジトリを所有する Organization のメンバーであること。 @@ -41,9 +41,9 @@ Issues, pull requests and discussions will appear on your contribution graph if コントリビューションとしてカウントするための要件を満たすコミットを行った後、コントリビューションがコントリビューショングラフに表示されるまで、最大 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 %} +コミットをコントリビューショングラフに表示するには、{% endif %}{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} のアカウントに接続されているメールアドレス、またはメール設定にある {% data variables.product.product_name %} 提供の `noreply` のメールアドレスを使用して行う必要があります。{% 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 %} コミット URL の最後に `.patch` を追加すると、コミットに使用されたメールアドレスを確認できます。例: https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: @@ -56,7 +56,7 @@ Subject: [PATCH] より良いウェルカムメッセージのためのインデ [`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 %} のアカウントに接続されていない場合は、Git で作者コミットに使用されるメールアドレスを変更します。 詳しい情報については、「[コミットメールアドレスを設定する](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)」を参照してください。{% else %}{% data variables.product.product_name %} アカウントに[メールアドレスを追加](/articles/adding-an-email-address-to-your-github-account)する必要があります。 新しいアドレスを追加すると、 コントリビューショングラフが自動的に再構築されます。{% endif %} {% warning %} @@ -66,7 +66,7 @@ If the email address used for the commit is not connected to your account on {% #### デフォルトまたは `gh-pages` ブランチでコミットされていません -コミットがデフォルトのブランチまたは `gh-pages` ブランチ (プロジェクトサイトを持つリポジトリの場合) で行われた場合にのみカウントされます。 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)」を参照してください。 +コミットがデフォルトのブランチまたは `gh-pages` ブランチ (プロジェクトサイトを持つリポジトリの場合) で行われた場合にのみカウントされます。 For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." コミットがデフォルト以外または `gh-pages` 以外のブランチにあり、コントリビューションにカウントする場合は、以下のうち 1 つを行う必要があります: - 変更をデフォルトのブランチまたは `gh-pages` ブランチにマージするには、[プルリクエストを開きます](/articles/creating-a-pull-request)。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md index 40cdeff0a0..f534da1b00 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md @@ -42,7 +42,7 @@ topics: ニュースフィードでは、あなたがフォローしているユーザが以下のことをした場合に更新情報が示されます: - リポジトリに Star を付ける。 - 別のユーザをフォローする。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- Creates a public repository.{% endif %} +- パブリックリポジトリを作成する{% endif %} - あなたが Watch しているリポジトリ上で "help wanted" あるいは "good first issue" のラベルを付けた Issue あるいはプルリクエストをオープンする。 - Watch しているリポジトリにコミットをプッシュする。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} - パブリックリポジトリをフォークする。{% endif %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md index d6aada49b0..48e91838b9 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/changing-your-github-username.md @@ -10,11 +10,13 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '*' +topics: + - アカウント --- ### ユーザ名の変更について -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 %} @@ -30,15 +32,15 @@ You can change your username to another username that is not currently in use.{% - 既存のリポジトリへの Web リンクは引き続き機能します。 変更を加えてから完了するまでに数分かかることがあります。 - ローカルリポジトリのクローンから古いリモートトラッキング URL へのコマンドラインプッシュは引き続き機能します。 -古いユーザ名の新しい所有者が、あなたのリポジトリと同じ名前のリポジトリを作成すると、リダイレクトエントリが上書きされ、リダイレクトは機能しなくなります。 こうしたことが起こることを防ぐため、ユーザ名を変更したら、既存のすべてのリモートリポジトリ URL を更新することをお勧めします。 詳しい情報については、「[リモートの URL を変更する](/articles/changing-a-remote-s-url)」を参照してください。 +古いユーザ名の新しい所有者が、あなたのリポジトリと同じ名前のリポジトリを作成すると、リダイレクトエントリが上書きされ、リダイレクトは機能しなくなります。 こうしたことが起こることを防ぐため、ユーザ名を変更したら、既存のすべてのリモートリポジトリ URL を更新することをお勧めします。 For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." ### 前のプロフィールページにリンクする -ユーザ名を変更した後、`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)別のメールアドレスに関連付けられている場合（ID ベースの {% data variables.product.product_name %} 提供の `noreply` メールアドレスを含む）、{% endif %}ユーザ名を変更した後も、引き続き自分に帰属し、コントリビューショングラフに表示されます。 メールアドレスの設定に関する詳細は「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。 ### ユーザ名を変更する @@ -52,6 +54,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/ja-JP/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md index f798b33799..9cee49a0c8 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -52,7 +52,7 @@ Organization の名前を、あなたの個人アカウントが使用してい {% tip %} -**ヒント**: ユーザアカウントを Organization に変換した場合、アカウントに属していたリポジトリのコラボレーターは、新しい Organization に*外部コラボレーター*として追加されます。 希望する場合は、*外部コラボレーター*を新しい Organization のメンバーに招待できます。 詳しい情報については「[Organization の権限レベル](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)」を参照してください。 +**ヒント**: ユーザアカウントを Organization に変換した場合、アカウントに属していたリポジトリのコラボレーターは、新しい Organization に*外部コラボレーター*として追加されます。 希望する場合は、*外部コラボレーター*を新しい Organization のメンバーに招待できます。 詳しい情報については「[Organization の権限レベル](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)」を参照してください。 {% endtip %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index c81430fcb9..e58e6e2977 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -56,4 +56,4 @@ Organization が所有するリポジトリは、細やかなアクセスを許 - "[ユーザ アカウントリポジトリの権限レベル](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)" - [個人リポジトリからコラボレーターを削除する](/articles/removing-a-collaborator-from-a-personal-repository) - [コラボレーターのリポジトリから自分を削除する](/articles/removing-yourself-from-a-collaborator-s-repository) -- [メンバーを Team に編成する](/articles/organizing-members-into-teams) +- [メンバーを Team に編成する](/organizations/organizing-members-into-teams) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md index b510d7154f..1b4f129d0c 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -25,4 +25,4 @@ topics: ### 参考リンク -- 「[Organization のリポジトリのデフォルブランチ名を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)」 +- 「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」 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 340eefeeb9..bee7f166e8 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 @@ -13,7 +13,7 @@ topics: 特定のイベントに対しては、スケジュールされたリマインダーにリアルタイムのアラートを有効にすることもできます。 リアルタイムアラートは、自分がレビューを割り当てられたなど、重要なイベントが発生したときすぐに Slack チャネルで送信されます。 -メンバーになっている Organization のプルリクエストについて、個人または Team レベルのレビューリクエストのスケジュールされたリマインダーを設定できます。 自分自身のスケジュールされたリマインダーを作成するには、Organization のオーナーが Slack ワークスペースを承認する必要があります。 詳しい情報については、「[Organization にスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)」を参照してください。 +メンバーになっている Organization のプルリクエストについて、個人または Team レベルのレビューリクエストのスケジュールされたリマインダーを設定できます。 自分自身のスケジュールされたリマインダーを作成するには、Organization のオーナーが Slack ワークスペースを承認する必要があります。 詳しい情報については、「[Organization にスケジュールされたリマインダーを管理する](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)」を参照してください。 {% data reusables.reminders.scheduled-reminders-limitations %} @@ -50,5 +50,5 @@ topics: ### 参考リンク -- [Organization にスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization) -- [Team のスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team) +- [Organization にスケジュールされたリマインダーを管理する](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization) +- [Team のスケジュールされたリマインダーを管理する](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team) diff --git a/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md index 8dfa41142b..94d5817c36 100644 --- a/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/ja-JP/content/github/site-policy/github-corporate-terms-of-service.md @@ -125,7 +125,7 @@ GitHub’s quarterly uptime commitment for GitHub Enterprise Cloud is provided i お客様が「製品」を利用する際には、[「GitHub利用規程」](/articles/github-acceptable-use-policies)および[「GitHubコミュニティガイドライン」](/articles/github-community-guidelines)に従う必要があります。 お客様は、いかなる管轄区域内でも、違法、わいせつ、不快、または詐欺的なコンテンツまたは活動 (損害を与えたりそう標榜したりする、ネットワークまたはシステムの完全性またはセキュリティを妨害または侵害する、フィルタを回避する、迷惑・虐待的・虚偽的なメッセージ、ウイルスまたは有害なコードを送信する、あるいは第三者の権利を侵害するなど) の目的で「サービス」を使用してはなりません。 #### 3. プライバシー -The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Addendum](/github/site-policy/github-data-protection-addendum) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. 「サービス」からデータを収集する個人、団体、またはサービスは、特にユーザの個人情報 (「GitHub のプライバシーについての声明」に規定) の収集に関して、GitHubの プライバシーについての声明に従う必要があります。 お客様がGitHubから「ユーザ個人情報」を収集した場合、お客様は「外部ユーザ」が承認した目的にのみその個人情報を使用するものとします。 お客様は、かかる個人情報を合理的に保護するものとし、GitHubはGitHubまたは「外部ユーザ」からの苦情、削除要請、および連絡拒否の要請に速やかに対応するものとします。 +The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Agreement](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. 「サービス」からデータを収集する個人、団体、またはサービスは、特にユーザの個人情報 (「GitHub のプライバシーについての声明」に規定) の収集に関して、GitHubの プライバシーについての声明に従う必要があります。 お客様がGitHubから「ユーザ個人情報」を収集した場合、お客様は「外部ユーザ」が承認した目的にのみその個人情報を使用するものとします。 お客様は、かかる個人情報を合理的に保護するものとし、GitHubはGitHubまたは「外部ユーザ」からの苦情、削除要請、および連絡拒否の要請に速やかに対応するものとします。 ### D. コンテンツの責任、所有権、ライセンス権 diff --git a/translations/ja-JP/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/ja-JP/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md new file mode 100644 index 0000000000..44d402517a --- /dev/null +++ b/translations/ja-JP/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md @@ -0,0 +1,348 @@ +--- +title: GitHub Data Protection Agreement (Non-Enterprise Customers) +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum +versions: + free-pro-team: '*' +--- + +_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._ + +## はじめに + +The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products. + +本DPAと、GitHubとお客様との契約の別の条項との間で矛盾または不一致が生じた場合、本DPAが優先されるものとします。 本特約で定義されているお客様の個人データの処理に適用される可能性のある、GitHubのプライバシーについての声明の規定とDPAの規定が矛盾する場合、DPAの規定が優先されます。 明確にするために記すと、添付1の標準契約条項10条に従い、標準契約条項がDPAのあらゆる規定より優先されます。 + + +## GitHubデータ保護 + +### 1. 定義 + +1.1 「**適用されるデータ保護法**」とは、お客様によるGitHubおよびGitHubサービスの利用に適用される、お客様の個人データの処理および利用に関する特定の法律、規制、規制の枠組み、またはその他の法令を言い、以下のものが該当します。 + + a. EU 一般データ保護規則 2016/679 (「**GDPR**」)、および施行されているまたはそれに準ずる、効力を有し適用される国家の法令 + + b. 2018年カリフォルニア州消費者プライバシー法 (Cal. Civ. Code §§1798.100 et seq.) (**「CCPA」**) + + c. 2018年英国データ保護法およびそれに含まれるGDPRの実施 + +1.2 「**コントローラー (管理者)**」、「**データ主体**」、「**加盟国**」、「**個人データ**」、「**個人データの侵害**」、「**処理**」、「**プロセッサー (処理者)**」、および「**監督官庁**」の語はそれぞれ、「適用されるデータ保護法」で指定された意味を持ちます。 不一致がある場合は、GDPR で規定された意味が優先されます。 + +1.3 「**お客様の個人データ**」とは、GitHubによる処理のためにお客様から提供されるか、または本契約に基づく義務を履行する過程でGitHubによって生成されるものかを問わず、お客様がコントローラー (管理者) である個人データのことを言います。 これには、支払い情報、IPアドレス、法人のメールアドレスなど、お客様がコントローラー (管理者) であるあらゆる個人データが該当します。 + +1.4 「**お客様のリポジトリデータ**」とは、お客様がプライベートリポジトリにアップロードまたは作成した任意のデータまたは情報のことを言います。 + +1.5 「**データ侵害**」とは、個人データの侵害など、保護されているお客様のデータの侵害が確認された、または合理的に疑われる場合を差します。 + +1.6 「**エンドユーザー**」とは、GitHubアカウントを管理し、GitHub利用規約に同意していて、その個人データがGitHubによって転送、保存、処理されるデータ主体です。 たとえば、GitHubアカウントを持っている、お客様の各従業員や契約者も、GitHubのエンドユーザーです。 + +1.7 データ処理の「**許可された目的**」とは、本契約、GitHubのプライバシーについての声明、およびこの付属文書Aに規定されている「サービス」を提供する限定的で特定の目的、あるいはデータ主体がお客様の個人データの使用を承認した目的のことです。 + +1.8 「**保護されたデータ**」には、本契約に基づいてGitHubが顧客に代わって処理するお客様の個人データとお客様のリポジトリデータが含まれます。 + +1.9 「**機密データ**」とは、人種または民族的出自、政治上の意見、宗教的または哲学的な信念、あるいは労働組合への加入、自然人を一意に識別する遺伝子データまたはバイオメトリックデータの処理、健康状態や性生活、性的指向に関するデータ、および犯罪、前科、または保安に関するデータなどを明らかにするお客様の個人データを指します。 + +### 2. ステータスとコンプライアンス + +#### 2.1 データ処理。 +GitHubは、本契約に関連して受領したお客様の個人データに関するプロセッサー (処理者) として機能し、本契約およびその他の書面による通知で示されるお客様の指示に従って、許可された目的でのみお客様の個人データを処理します。 適用されるデータ保護法との不一致などが理由で、GitHubがお客様の指示を遵守できない場合、または適用されるデータ保護法その他の法的要件によって処理が必要とされる場合、GitHubは許可される範囲でお客様に通知します。 GitHubは、お客様の個人データをすべて米国ならびに欧州連合で処理しますが、GitHubのサブプロセッサー (副処理者) はデータを米国または欧州連合以外で処理する可能性があります。 また、GitHubはお客様のリポジトリデータについて処理者として機能します。 + +#### 2.2 データコントローラー (管理者)。 +GitHubは、お客様の個人データをお客様から受け取ることも、またエンドユーザーアカウントを作成するデータ主体から直接受け取ることもあります。 お客様は、直接GitHubに移転する場合にお客様の個人データのコントローラー (管理者) となります。 + +#### 2.3 GitHubによる順守、データ移転 +GitHubは、お客様の個人データの処理に関して、適用されるデータ保護法に従います。 + +本サービスを提供するための、欧州連合、欧州経済領域、英国、およびスイス外でのお客様の個人データの移転はすべて、添付1の標準契約条項 (「標準契約条項」) に準拠するものとします。 GitHubは、欧州経済領域、英国、およびスイスからのお客様の個人情報の収集、使用、移転、保持、およびその他の処理に関する、欧州経済領域およびスイスデータ保護法の要件を順守します。 第三国または国際機関へのお客様の個人データの移転はすべて、GDPR第46条に記載されている適切な保護措置の対象となり、かかる転送および保護措置については、GDPR第30条 (2) に従って文書化されるものとします。 + +さらにGitHubは、EU-米国プライバシーシールドフレームワーク およびスイス-米国 プライバシーシールドフレームワークおよびそれに伴う義務について認証を受けています。ただしGitHubは、個人情報の移転についての法的根拠として、それらに依拠するものではありません。 GitHubは、プライバシーシールド原則で要求されているものと同水準の保護を提供する義務が果たせなくなったと判断した場合、お客様に通知することに同意します。 + + +### 3. データ保護 + +#### 3.1 目的限定。 +GitHubは、当事者が目的の拡大に書面で合意する場合を除き、許可された目的でのみ、保護データを処理し通信します。 + +#### 3.2 データの品質と均衡性。 +GitHubはお客様の個人データを正確に、かつ最新の状態に保つか、お客様がそれを自ら実施できるようにします。 GitHubは商業的に妥当な手順で、お客様に代わって収集した保護データが適切、妥当であり、それが移転および処理される目的に関連して過剰でないことを保証します。 いかなる場合も、GitHubがお客様に代わって故意に機密データを集めることはありません。 お客様は、GitHubサービスが機密データの保存を目的にしないことに同意するものとします。お客様が選択して機密データをサービスにアップロードする場合、お客様はGDPRの第9条、または適用されるデータ保護法で該当する条項に従う必要があります。 + +#### 3.3 データの保持と削除。 +許可された目的に必要でなくなってから、お客様から合理的な請求があった場合、法律で禁じられている場合を除き、請求から30日以内に、GitHubはお客様の個人データすべてと関連データを、保存されているすべての場所で返却、破棄、または匿名化します。 適用されるデータ保護法が必要とする限りにおいて、また適用されるデータ保護法の定める範囲とその期間に限って、GitHubはお客様の個人データと関連データを保持する場合があります。ただし、お客様の個人データは適用されるデータ保護法に定められた目的上必要な場合に限って処理し、その他の目的では処理しないこと、またお客様の個人データは適用されるデータ保護法で引き続き保護されることをGitHubは保証するものとします。 + +#### 3.4 データ処理。 +GitHubは、お客様の個人データの処理に関するGDPRの第28条第3項に従って、以下の情報を提供します。 + +a. お客様の個人データの*主題と処理期間*は、本契約および本付属文書で定められています。 + +b. お客様の個人データの*処理の性質と目的*は、本付属文書のセクション3.1に記載されています。 + +c. *処理されるお客様の個人データのタイプ*は、GitHubのプライバシーについての声明に記載されており、ユーザ名、パスワード、メールアドレス、IPアドレスなどの個人データが含まれます。 GitHubは、お客様のアカウントに対する請求に必要な情報を処理しますが、クレジットカード情報は処理も保存もしません。 お客様は、お客様のプロフィール設定で、あるいはお客様の個人データをGitHubリポジトリにアップロードすることによって、追加の個人データをGitHubに提供することもできます。 + +d. *お客様の個人データが関係するデータ主体のカテゴリ*は、お客様自体と、そのエンドユーザです。 + +e. *お客様の義務の権利*は、本契約および本付属文書で定められています。 + +### 4. セキュリティと監査の義務 + +#### 4.1 技術的および組織的セキュリティ対策。 +最新技術、実装のコスト、処理の性質や範囲、目的と、考えられる可能性ごとのリスク、自然人の権利と自由の重大度を考慮して、GitHubは個人データの処理によって生じる偶発的または違法な破壊、紛失、改変、不正な開示といったリスクに応じ適切なレベルのセキュリティを確保するために、適切な技術的および組織的対策を講じるものとします。 GitHubは、こうした対策の準拠状況を常に監視し、本契約の期間を通じて適切な安全対策をとり続けます。 + +#### 4.2 インシデント対応と侵害通知。 +GitHub will comply with Applicable Data Protection Laws. + +#### 4.3 GitHubのスタッフ。 +GitHubは、保護データの処理に当たるGitHubスタッフ全員が保護データを機密として扱うことに合意し、本付属文書と適用されるデータ保護法の遵守について適切な訓練を受けていることを保証する合理的な手順を踏むことを、表明および保証します。 + +#### 4.4 記録。 +GitHubは、適用されるデータ保護法のもとで必要な情報を含め、お客様に代わって実行される全カテゴリの処理活動について完全、正確、最新の書面による記録を維持します。 支援がGitHubのセキュリティに、または個々のデータ主体のプライバシー権にリスクをもたらさない限り、GitHubはこれらの記録を、お客様が適用されるデータ保護法に準拠していることを証明するためなど合理的に必要とされる場合に、請求があればお客様に公開します。 + +#### 4.5 支援。 +GitHubは、データプライバシーの影響評価、データ主体の権利請求、監督機関との協議などに関して、いずれの場合も、お客様の個人データの処理についてのみ、また処理の性質を考慮して、合理的な支援をお客様に提供します。 + +### 5. 保護データの使用と開示 + +#### 5.1 マーケティングでの不使用。 +GitHubは、第三者のコンテンツの広告を目的として保護データを使用せず、また合併・吸収の一環の場合を除いて保護データを第三者に売却しません。 + +#### 5.2 GitHubのプライバシーについての声明。 +GitHubのプライバシーについての声明は [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement)で公開されており、Cookieの使用、紛争解決のプロセス、GitHubのGDPR順守に関する詳細など、GitHubのプライバシーおよびデータ使用の慣例について詳細を定めています。 + +### 6. 副処理とデータの委譲 + +#### 6.1 データの保護。 +GitHubは、第三者の決済プロセッサー (処理者) など、保護データをサブプロセッサー (副処理者) に委譲する際の責任を負います。 GitHubが実際に第三者のサブプロセッサーに保護データを移譲する場合、またはGitHubが第三者のサービスをインストール、使用、または有効化してGitHubに代わって保護データを処理させる場合、GitHubは本DPAおよび適用されるデータ保護法によって要求されている通り、その第三者サブプロセッサーが守秘義務、セキュリティ、ポリシー保護を遵守する、または少なくとも同レベルで提供するよう書面での契約により拘束されることを保証するものとします。 + +#### 6.2 GitHubサブプロセッサーの承認。 +お客様は、本契約のセクション6および他の規制に従って、GitHubがサブプロセッサー (副処理者) を任命することを承認 (また、セクション6に従って各サブプロセッサーが任命されることを許可) します。 GitHubは、本契約の発効日時点で契約している現行のサブプロセッサーをそのまま採用し続けることもできます。 + +#### 6.3 後続の副処理に関する一般的な合意。 +お客様は、GitHubが以下の要件を満たしているという条件で、GitHubが後続のサブプロセッサー (副処理者) と契約することを一般的に合意します。 + +a. 後続のサブプロセッサーは、欧州委員会が「適切」なレベルの保護があると宣言した国のデータのみを処理することに書面で合意するか、あるいは標準契約条項に相当する条件で、または管轄の欧州データ保護当局によって付与される、拘束力のある企業規則の承認に従う、または適切なEU-米国プライバシーシールドおよび スイス-米国プライバシーシールドの認証に従うデータのみを処理することに書面で合意する必要があります。 + +b. GitHubは、後続のサブプロセッサーによるお客様の個人データへのアクセスを、そのサービスの実施に厳密に必要な内容のみに制限し、サブプロセッサーがそれ以外の目的でお客様の個人データを処理することを禁じます。 + +#### 6.4 サブプロセッサーの契約の開示。 +GitHubは、お客様の個人データを処理するために契約した後続のサブプロセッサーのリストを[https://docs.github.com/articles/github-subprocessors-and-cookies](/articles/github-subprocessors-and-cookies)に保管しています。これには、処理されるお客様の個人データのカテゴリ、サブプロセッサーが実行する処理の種類の説明、処理の場所なども含まれています。 お客様から書面による請求があれば、GitHubはこのサブプロセッサーリストと、お客様の個人データが処理されるときの条項を提供します。 サブプロセッサーの守秘制限に従って、GitHubはリストと条項をお客様に提供する前に、機密情報や商売上重要な情報を削除する場合があります。 GitHubが機密または重要な情報お客様に開示できない場合、当事者はGitHubが副処理の契約に従って合理的に可能な情報を提供することに合意します。 + +#### 6.5 サブプロセッサーに対する異議。 +GitHubは、サブプロセッサーの追加と削除について、のサイトで、セクション6.4に挙げたカテゴリを含めて、30日前に書面で通知します。 GitHubと新しいサブプロセッサーとの契約に合理的な異議がある場合、お客様はただちに書面でGitHubに通知する必要があります。 可能な場合GitHubは、異議を受けたサブプロセッサーによるデータの処理を避けるために、商業的に相応の努力で、該当する「サービス」に代替策を講じるものとします。 90日以内にGitHubが代替策を講じられず、当事者も解決できない場合、お客様は本契約を解約することができます。 + +### 7. 解約 + +#### 7.1 一時停止 +GitHubが、適切なレベルのセキュリティまたはプライバシー保護を維持する義務に違反した場合、お客様はあらゆる個人データの委譲を一時的に停止し、違反が是正されるか本契約を解約するまで、お客様に代わってお客様の個人データを収集・処理することを禁じることができます。 + +#### 7.2 理由のある解約。 +お客様は、本契約のもとで有する解約の権利に加えて、以下の場合には、法律上または衡平法上の他の請求権を損なうことなく本契約を解約できるものとします。 + +a. GitHubがプライバシー義務を満たせなくなったとお客様に通達する。 + +b. お客様の個人データすべての委譲、収集、処理が、セクション7.1に従って1か月以上一時停止されている。 + +c. GitHubが、本付属文書での保証または代理を実質的に、または永続的に侵害している。 + +d. GitHubが、事業を継続しなくなった、解散した、財産管理に入った、あるいはGitHubに代わって清算命令が発令された。 + +e. セクション6.5に従ってお客様がサブフォルダに異議を申し立て、GitHubが90日以内に代替策を講じられなかった。 + +#### 7.3 侵害。 +本付属文書の重大な条項を遵守できなかった場合は、本契約のもとでの重大な違反と見なされます。 + +#### 7.4 不履行。 +法律または規制の変更によって、本付属文書の遂行が不可能になった、または商業的に妥当でなくなった場合、当事者は誠意をもって本付属文書を再交渉することができます。 再交渉しても解決に至らない、または当事者が合意に達しない場合、当事者は30日後に本契約を解約できます。 + +#### 7.5 通知。 +GitHubが本付属文書に定めるプライバシー義務を満たせなくなったと判断した場合、GitHubはただちに書面でお客様に通知します。 + +#### 7.6 変更。 +GitHubは、適用されるデータ保護法より必要な場合には随時、お客様に30日前に通知したうえで、本付属文書を変更できます。 + +#### 7.7. 解約要件。 +解約の際、GitHubは以下を行う必要があります。 + +a. 妥当かつ適切な手段を講じて、お客様の個人データの処理を停止する。 + +b. セクション3.3に従ってGitHubがお客様に代わって保存していたお客様の個人データを、解約後90日以内に削除または匿名化する。 + +c. gitHubがセクション7.7の義務に従っているという合理的な保証をお客様に提示する。 + +### 8. データ処理の責任 + +#### 8.1 制限。 +適用されるデータ保護法による制限を除き、本付属文書のもとで行われる請求は、責任の制限に関する本契約の条項に従うものとします。 + +## 添付1 – 標準契約条項 (プロセッサー) +お客様による該当する契約の履行には、GitHub, Inc.により連署された、GitHubデータ保護特約の本添付1の履行が含まれます。 + +本標準契約条項の使用に規制当局の承認が必要な国においては、お客様が規制当局から必要な証人を得ていない限り、欧州委員会2010/87/EU (2010年2月) に基づき、当該国からのデータ輸出を合法とするにあたり、本標準契約条項に依拠することはできません。 + +適切な水準のデータ保護を保証しない第三国に拠点を置く処理者に個人データを移転することについて定めた一般データ保護規則 (EU 2016/679) 第46条第2項において、お客様 (データ移転元) と、GitHub (データ移転先、本書下部に署名) との各「当事者」、総称して「両当事者」は、添付1に定めるデータ移転元からデータ移転先への個人データの移転のため、個人のプライバシー、基本的権利、および自由の保護に関する適切な保護措置に関する引証として、以下の契約条項 (「条項」または「標準契約条項」) に合意したものとします。 + +#### 第1条: 定義 +(a) 「個人データ」、「データの特別カテゴリ」、「処理」、「管理者」、「処理者」、「データ主体」、および「監督当局」という用語は、個人データの処理に関する保護およびかかるデータの自由な移動に関する一般データ保護規則 (EU 2016/679) と同じ意味を持つものとします。 + +(b) 「データ移転元」とは、個人情報を移転する管理者を意味します。 + +(c) 「データ移転先」とは、移転後に、データ移転元の指示および本条項の規定に従って処理するためにデータ移転元から個人データを受信することに合意し、かつ一般データ保護規則 (EU 2016/679) 第45条第2項の意味する範囲において適切な保護を保証しない第三国の機構の支配下にない処理者のことを意味します。 + +(d) 「サブプロセッサー」とは、データ移転元の指示、本条項の規定、および書面による請負契約の規定に従い、移転後にデータ移転元の代理として処理活動を実施することのみを目的として、データ移転先から、または データ移転先の別のサブプロセッサーから個人データを受信することに合意している、データ移転先またはデータ移転先の別のサブプロセッサーから業務を請け負う任意の処理者のことを意味します。 + +(e)「適用されるデータ保護法」とは、個人の基本的人権と自由、特に、データ移転元が存在する加盟国内におけるデータコントローラーに適用される、個人情報処理に関するプライバシーの権利を保護する法律のことを意味します。 + +(f) 特に処理がネットワークを介したデータの送信を伴う偶発的または違法な破壊、偶発的な紛失、改変、不正な開示またはアクセス、およびその他あらゆる違法な処理の形態に対して個人データを保護する対策のことを意味します。 + +#### Clause 2: Details of the transfer +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +#### Clause 3: Third-party beneficiary clause +1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary. + +2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. + +3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law. + +#### Clause 4: Obligations of the data exporter +The data exporter agrees and warrants: + +(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State; + +(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses; + +(c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below; + +(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation; + +(e) that it will ensure compliance with the security measures; + +(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of the General Data Protection Regulation (EU 2016/679); + +(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension; + +(h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information; + +(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and + +(j) that it will ensure compliance with Clause 4(a) to (i). + +#### Clause 5: Obligations of the data importer +The data importer agrees and warrants: + +(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(c) that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred; + +(d) that it will promptly notify the data exporter about: + +(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation, + +(ii) any accidental or unauthorised access, and + +(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so; + +(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + +(f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; + +(g) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter; + +(h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent; + +(i) that the processing services by the subprocessor will be carried out in accordance with Clause 11; and + +(j) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter. + +#### Clause 6: Liability +1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered. + +2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity. The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities. + +3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +#### Clause 7: Mediation and jurisdiction +1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: + +(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; + +(b) to refer the dispute to the courts in the Member State in which the data exporter is established. + +2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. + +#### Clause 8: Cooperation with supervisory authorities +1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law. + +2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law. + +3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5(b). + +#### 第9条: 準拠法。 +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +#### Clause 10: Variation of the contract +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +#### Clause 11: Subprocessing +1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement. + +2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established. + +4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority. + +#### Clause 12: Obligation after the termination of personal data processing services +1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore. + +2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1. + +### Appendix 1 to the Standard Contractual Clauses +Data exporter: Customer is the data exporter. + +**Data importer:** The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects:** Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal information to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following types of data subjects in the Customer Personal Data: + +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Dependents of the above; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users (e.g., customers, clients, patients, visitors, etc.) and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter; +- Stakeholders or individuals who passively interact with data exporter (e.g., because they are the subject of an investigation, research or mentioned in documents or correspondence from or to the data exporter); or +- Professionals with professional privilege (e.g., doctors, lawyers, notaries, religious workers, etc.). + +**Categories of data:** The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Service. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following categories in the Customer Personal Data: +- Authentication data (for example, username, email, password); +- Contact information (for example, email); +- Unique identification numbers and signatures (IP addresses, unique identifier in tracking cookies or similar technology). +- Other unique identifying information. Data subjects may include more data such as real names, avatar images, and other personal information; + +**Special categories of data (if appropriate):** The data importer does not intentionally collect or process any special categories of data in carrying out its services to the data exporter. + +However, because the data importer provides storage services and does not control the categories of data it stores, the data exporter may choose to transfer special categories of data. Consequently, the data exporter is solely responsible for ensuring that it complies with all obligations imposed by applicable laws and regulations relating to the collection and processing of any special categories of data, including obtaining the explicit consent of the data subject prior to processing sensitive personal data. + +**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontractors: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain Customer Personal Data only to deliver the services the data importer has retained them to provide, and they are prohibited from using Customer Personal Data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +**1. Personnel.** Data importer’s personnel will not process Customer Personal Data without authorization. Personnel are obligated to maintain the confidentiality of any Customer Personal Data and this obligation continues even after their engagement ends. + +**2. Data Privacy Contact.** The data privacy officer of the data importer can be reached at the following address: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA + +**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction. + +Signature of GitHub, Inc. appears below. + +Signing the Standard Contractual Clauses, Appendix 1 and Appendix 2 on behalf of the data importer + +![2020年7月20日、午後2:20:29のスクリーンショット](/assets/images/help/site-policy/docusign-signature.png) + +Lynn Hashimoto, Head of Product & Regulatory Legal + +GitHub, Inc. diff --git a/translations/ja-JP/content/github/site-policy/github-privacy-statement.md b/translations/ja-JP/content/github/site-policy/github-privacy-statement.md index 345e4be99b..c42b2dc6b6 100644 --- a/translations/ja-JP/content/github/site-policy/github-privacy-statement.md +++ b/translations/ja-JP/content/github/site-policy/github-privacy-statement.md @@ -192,7 +192,7 @@ If you would like to compile GitHub data, you must comply with our Terms of Serv #### Organization -さらに、お客様は、GitHub上でのアクションを通じて、ユーザ個人情報を共有するために指示することができます。 Organizationでコラボレートしている場合またはそのOrganizationのメンバーとなったの場合、そのアカウントオーナーはお客様のユーザ個人情報を受け取ることができます。 Organizationへの招待を承認した場合、オーナーが閲覧できる情報の種類についてお客様に通知されます。（詳細は、[Organizationメンバーシップについて](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)を参照してください） [認証ドメイン](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)付きOrganizationへの招待を承認した場合、Organizationのオーナーは、Organizationの認証ドメイン内でお客様の完全なメールアドレスを閲覧できます。 +さらに、お客様は、GitHub上でのアクションを通じて、ユーザ個人情報を共有するために指示することができます。 Organizationでコラボレートしている場合またはそのOrganizationのメンバーとなったの場合、そのアカウントオーナーはお客様のユーザ個人情報を受け取ることができます。 Organizationへの招待を承認した場合、オーナーが閲覧できる情報の種類についてお客様に通知されます。（詳細は、[Organizationメンバーシップについて](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)を参照してください） [認証ドメイン](/organizations/managing-organization-settings/verifying-your-organizations-domain)付きOrganizationへの招待を承認した場合、Organizationのオーナーは、Organizationの認証ドメイン内でお客様の完全なメールアドレスを閲覧できます。 Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization. @@ -321,7 +321,7 @@ GitHub processes personal information both inside and outside of the United Stat ### プライバシーステートメントの変更 -ほとんどの変更は軽微ですが、GitHubは、随時、プライバシーステートメントを変更することがあります。 当社は、ホームページに通知を掲載すること、または、GitHubアカウントで指定するプライマリメールアドレスにemailを送信することで、変更が発効する遅くとも30日前にウェブサイト上で、このプライバシーステートメントの重要な変更についてユーザへの通知を提供します。 また、当社は、このポリシーの変更を追跡している[サイトポリシーリポジトリ](https://github.com/github/site-policy/)をアップデートします。 For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. +ほとんどの変更は軽微ですが、GitHubは、随時、プライバシーステートメントを変更することがあります。 当社は、ホームページに通知を掲載すること、または、GitHubアカウントで指定するプライマリメールアドレスにemailを送信することで、変更が発効する遅くとも30日前にウェブサイト上で、このプライバシーステートメントの重要な変更についてユーザへの通知を提供します。 また、当社は、このポリシーの変更を追跡している[サイトポリシーリポジトリ](https://github.com/github/site-policy/)をアップデートします。 For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### ライセンス diff --git a/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md index 7052c0bf40..871f8b6fd0 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 @@ -13,7 +13,7 @@ topics: - legal --- -Effective date: **January 29, 2021** +Effective date: **April 2, 2021** GitHubは、お客様のデータを当社が利用する方法、お客様のデータを当社が収集する方法、およびお客様のデータを共有する対象について、高い透明性を提供します。 To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). @@ -33,7 +33,6 @@ GitHubは、お客様のデータを当社が利用する方法、お客様の | MailChimp | 顧客チケットメールサービスプロバイダ | 米国 | 米国 | | Mailgun | トランザクションメールサービスプロバイダ | 米国 | 米国 | | Microsoft | Microsoft Services | 米国 | 米国 | -| Monday.com | チームコラボレーションおよびプロジェクト管理プラットフォーム | 米国 | イスラエル | | Nexmo | SMS通知プロバイダ | 米国 | 米国 | | Salesforce.com | 顧客関係管理 | 米国 | 米国 | | Sentry.io | Application monitoring provider | 米国 | 米国 | diff --git a/translations/ja-JP/content/github/site-policy/index.md b/translations/ja-JP/content/github/site-policy/index.md index fdbea86787..fb1344ac3d 100644 --- a/translations/ja-JP/content/github/site-policy/index.md +++ b/translations/ja-JP/content/github/site-policy/index.md @@ -16,6 +16,7 @@ topics: {% 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-agreement-non-enterprise-customers %} {% link_in_list /global-privacy-practices %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} {% link_in_list /github-sponsors-additional-terms %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 6c11804151..c3f389ff73 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -24,7 +24,9 @@ topics: ### スポンサーシップ層 -{% data reusables.sponsors.tier-details %} 詳細は、「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」、「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)」、および「[スポンサーシップのレベルを変更する](/articles/changing-your-sponsorship-tiers)」を参照してください。 +{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)." + +It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. ### スポンサーシップの支払い @@ -34,5 +36,9 @@ topics: 詳しい情報については、「[{% data variables.product.prodname_sponsors %}からの支払いを管理する](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)」を参照してください。 +### {% data variables.product.prodname_sponsors %} についてのフィードバックを共有する + +{% data reusables.sponsors.feedback %} + ### 参考リンク - {% data variables.product.prodname_blog %} の「[{% data variables.product.prodname_sponsors %} Team に関するよくある質問](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)」 diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md index d4f15a247c..bd1515c23f 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -37,7 +37,7 @@ topics: ### {% data variables.product.prodname_sponsors %} についてのフィードバックを共有する -これは単なる始めに過ぎません。{% data variables.product.prodname_sponsors %} が将来皆さんのお役に立てるよう、ぜひともご意見をお寄せください。 フィードバックやご提案は、[{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors) からお送りください。 +{% data reusables.sponsors.feedback %} ### 参考リンク - [オープンソースコントリビューターをスポンサーする](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors) diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md index 23a9c7eaff..337e8ec8cb 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -15,6 +15,8 @@ topics: スポンサード開発者アカウントの場合、アップデートはユーザーアカウントのプライマリメールアドレスから送信されます。 ユーザアカウントでメールアドレスのプライバシーを有効化している場合は、`noreply@github.com` から送信されます。 スポンサードOrganizationの場合、アップデートはOrganizationの`noreply@github.com` メールアドレスから送信されます。 詳細は「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。 +You can also contact any one-time sponsors who contributed within the last 30 days and enabled updates. + ### スポンサーに連絡する {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/index.md index 4125c0e3bd..abafa82974 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/index.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/index.md @@ -25,7 +25,7 @@ topics: {% 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 /managing-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 %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md index f00e461b1f..78b0db2ee1 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -13,6 +13,12 @@ topics: 目標には、確保したいスポンサーの数、または毎月集めたい金額を設定できます。 一度に設定できる目標は 1 つだけです。 目標に達したら、次の目標を設定できます。 +{% note %} + +**Note:** Goals are intended to help people track momentum so only monthly sponsors contribute toward your goal. + +{% endnote %} + ### 目標の設定 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md new file mode 100644 index 0000000000..5d7878a93e --- /dev/null +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md @@ -0,0 +1,45 @@ +--- +title: Managing your sponsorship tiers +intro: '新しいスポンサーシップ層の追加や、既存スポンサーシップ層の編集、破棄が可能です。' +redirect_from: + - /articles/changing-your-sponsorship-tiers + - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +topics: + - sponsors +--- + +### スポンサーシップ層について + +{% 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.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 %} + +### Enabling tiers with custom amounts + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.enable-custom-amounts %} + +### Disabling tiers with custom amounts + +You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired. diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 8d8b70597d..75b8e4cf74 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -48,6 +48,7 @@ Organization 外の個人コントリビューターとして {% data variables. {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### 銀行口座情報をサブミットする diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index cacfefcf2c..c11eccf7f8 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -48,6 +48,7 @@ Organization として {% data variables.product.prodname_sponsors %} に参加 {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### 銀行口座情報をサブミットする diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index cd6f3ac842..d472b401c7 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -1,6 +1,6 @@ --- title: オープンソースコントリビューターに対するスポンサー -intro: 'あなたが頼りにしているオープンソースプロジェクトを設計、作成、維持する開発者または Organization に対して、毎月定期的に支払いをすることができます。' +intro: 'You can make a one-time or monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' redirect_from: - /articles/sponsoring-a-developer - /articles/sponsoring-an-open-source-contributor @@ -24,11 +24,11 @@ topics: - オープンソースを大切にする Organization としてブランド認知度を確立する - Organization が提供する製品を補完するライブラリを構築しているオープンソース開発者に感謝する -{% data variables.product.product_name %} でアカウントをスポンサーするときは、クレジットカードを使用できます。 Organization が請求書で支払いしたい場合は、[お問い合わせ](https://support.github.com/contact/org-sponsors-waitlist)ください。 +You use your normal payment method to sponsor an account on {% data variables.product.product_name %}. Organization が請求書で支払いしたい場合は、[お問い合わせ](https://support.github.com/contact/org-sponsors-waitlist)ください。 {% data reusables.sponsors.no-fees %}詳細は「[{% data variables.product.prodname_sponsors %} の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。 -クレジットカードを使用してアカウントをスポンサーすると、その変更は直ちに有効になります。 {% data reusables.sponsors.prorated-sponsorship %} +When you sponsor an account the change is effective immediately, unless you are sponsoring on behalf of an organization that pays by invoice. {% data reusables.sponsors.prorated-sponsorship %} Your sponsorship is included in the next scheduled payment to the sponsored account. {% data reusables.sponsors.manage-updates-for-orgs %} @@ -53,6 +53,7 @@ topics: - 開発者をスポンサーする場合は、開発者の名前の下で [**Sponsor**] をクリックします。 ![[Sponsor] ボタン](/assets/images/help/profile/sponsor-button.png) - Organization をスポンサーする場合は、開発者の名前の下で [**Sponsor**] をクリックします。 ![[Sponsor] ボタン](/assets/images/help/sponsors/sponsor-org-button.png) 1. オプションとして、ページの右側で、Organization に代わってアカウントをスポンサーする場合は、[**Sponsor as**] ドロップダウンメニューを使用して Organization をクリックします。 ![スポンサーとしてのアカウントを選択するドロップダウンメニュー](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index 1a66878f1a..1f6624125d 100644 --- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -1,89 +1,94 @@ --- -title: About the dependency graph -intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' +title: 依存関係グラフについて +intro: '依存関係グラフ、それがサポートするエコシステム、およびリポジトリが依存するパッケージの決定方法についての詳細。' versions: - free-pro-team: '*' - enterprise-server: '*' + enterprise-server: '<=2.22' +topics: + - repositories --- -### Dependency graph availability +### 依存関係グラフの利用 The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### 依存関係グラフについて The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: -- Dependencies, the ecosystems and packages it depends on +- 依存関係、エコシステム、それが依存しているパッケージ - Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. {% if currentVersion == "free-pro-team@latest" %} -When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. 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)." +When you create a pull request containing changes to dependencies that targets the default branch, +{% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. 詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。 {% endif %} -### Dependencies included +### 含まれる依存関係 -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +依存関係グラフには、サポートされているエコシステムについてマニフェストおよびロックファイル、または同等のもので詳細に定義されているリポジトリの依存関係がすべて含まれています。 これは以下のものが含まれます。 -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- マニフェストまたはロックファイルで明示的に定義されている、直接依存関係 +- 直接依存関係の間接依存関係。推移的な依存関係、または下位の依存関係とも言う。 -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. 最も信頼性の高いグラフを得るには、ロックファイル (または同等のもの) を使用してください。直接および間接の依存関係のうち現在どのバージョンを使用しているかが正確に定義されているからです。 If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. {% if currentVersion == "free-pro-team@latest" %} ### Dependents included For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} -### Using the dependency graph +### 依存関係グラフの使用 -You can use the dependency graph to: +依存関係グラフを使用する目的は、次のとおりです。 -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} +- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. 詳しい情報については、「[リポジトリの依存関係を調べる](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} +- Organization のリポジトリで使用されている依存関係のサマリーを 1 つのダッシュボードで確認すること。 詳細は「[Organization のインサイトを表示する](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)」を参照してください。{% endif %} +- リポジトリの脆弱な依存関係を表示・更新すること。 For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} - See information about vulnerable dependencies in pull requests. 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 %} -### Enabling the dependency graph +### 依存関係グラフの有効化 -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. 依存関係グラフは、パブリックリポジトリに対しては常に自動的に生成され、プライベートリポジトリに対しては有効化を選択することができます。 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" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. 詳しい情報については、「[{% data variables.product.prodname_ghe_server %}の脆弱性のある依存関係に関するセキュリティアラートの有効化](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。 {% endif %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +依存関係グラフを初めて有効化すると、サポートされているエコシステムのマニフェストおよびロックファイルがすぐに解析されます。 グラフは通常数分以内に入力されますが、多くの依存関係を持つリポジトリの場合は時間がかかる場合があります。 Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. -### Supported package ecosystems +### サポートされているパッケージエコシステム -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +推奨されるフォーマットでは、直接および間接の依存関係すべてに使用されるバージョンを明示的に定義しています。 これらのフォーマットを使用したほうが、依存関係グラフは正確になります。 It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +{% if currentVersion == "free-pro-team@latest" %}The ecosystems listed below are supported for the dependency graph, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_dependabot_security_updates %}.{% endif %} +| +{% if currentVersion ver_gt "enterprise-server@2.21" %}The ecosystems listed below are supported for the dependency graph and {% data variables.product.prodname_dependabot_alerts %}.{% endif %} +| パッケージマネージャー | 言語 | 推奨されるフォーマット | サポートされているすべてのフォーマット | +| ------------ | ---------------------- | -------------------------------------------------- | -------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET 言語 (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`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`、`Gemfile`、`*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`、`yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**メモ:** `setup.py` ファイルで Python の依存関係をリストする場合、プロジェクトの依存関係すべてを解析してリストすることはできない場合があります。 {% endnote %} -### Further reading +### 参考リンク -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia +- Wikipedia の「[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)」 - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- [Organization のインサイトを表示する](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization) +- [リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index 4e7f674458..dc4942276e 100644 --- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -68,7 +68,7 @@ Any direct and indirect dependencies that are specified in the repository's mani リポジトリ管理者は、プライベートリポジトリに対して依存関係グラフを有効または無効にすることができます。 -You can also enable or disable the dependency graph for all repositories owned by your user account or organization. 詳しい情報については、「[ユーザーアカウントのセキュリティおよび分析設定を管理する](/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)」を参照してください。 +You can also enable or disable the dependency graph for all repositories owned by your user account or organization. 詳しい情報については、「[ユーザーアカウントのセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)」または「[Organization のセキュリティおよび分析設定を管理する](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -109,7 +109,7 @@ The "Used by" section represents a single package from the repository. If you ha ### 参考リンク - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- [Organization のインサイトを表示する](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization) +- [Organization のインサイトを表示する](/organizations/collaborating-with-groups-in-organizations/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) {% endif %} diff --git a/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md b/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md index 1d92c3aa94..b7dae5cb37 100644 --- a/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md +++ b/translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md @@ -11,7 +11,7 @@ topics: 自分のアカウントで有料の {% data variables.product.prodname_dotcom %} 製品を使用している場合は、{% data variables.contact.github_support %} に直接問い合わせることができます。 ユーザアカウントまたは Organization の {% data variables.product.prodname_free_user %} を使用している場合は、{% data variables.contact.contact_support %} に連絡してアカウント、セキュリティ、悪用の問題を報告できます。 詳しい情報については、「[GitHub Supportについて](/github/working-with-github-support/about-github-support)」を参照してください。 -{% data variables.product.prodname_ghe_server %}、{% data variables.product.prodname_ghe_cloud %}、または {% data variables.product.premium_support_plan %} を使っている場合、{% data variables.contact.enterprise_portal %} でチケットをサブミットする必要があります。 +If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)." ### {% data variables.contact.support_portal %} を使ってチケットをサブミットする 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 080eaf495e..3a82f63fba 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 @@ -33,7 +33,7 @@ Secret gists don't show up in {% data variables.gists.discover_url %} and are no 通知は以下の場合に送られます: - あなたが Gist の作者である場合。 - 誰かがあなたを Gist 中でメンションした場合。 -- いずれかの Gist の上部で [** Subscribe**] をクリックして、Gist をサブスクライブした場合。 +- You subscribe to a gist, by clicking **Subscribe** at the top of any gist. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} @@ -55,13 +55,15 @@ Gist は GeoJSON ファイルのマッピングをサポートしています。 ### Gist の作成 -テキストファイルをデスクトップから直接 Gist エディターにドラッグアンドドロップすることもできます。 +Follow the steps below to create a gist. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% note %} 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. +Alternatively, you can drag and drop a text file from your desktop directly into the editor. + {% endnote %} {% endif %} @@ -69,7 +71,7 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. 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) +4. Type the text of your gist into the gist text box. ![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 %} diff --git a/translations/ja-JP/content/index.md b/translations/ja-JP/content/index.md index 8a144eecbf..74cd2cadb8 100644 --- a/translations/ja-JP/content/index.md +++ b/translations/ja-JP/content/index.md @@ -13,5 +13,43 @@ featuredLinks: - /github/getting-started-with-github/managing-remote-repositories - /github/working-with-github-pages versions: '*' +children: + - github + - 管理 + - organizations + - code-security + - actions + - パッケージ + - developers + - rest + - graphql + - insights + - ディスカッション + - コミュニティ + - pages + - education + - desktop + - early-access +externalProducts: + cli: + id: cli + name: GitHub CLI + href: 'https://cli.github.com/manual' + external: true + atom: + id: atom + name: Atom + href: 'https://atom.io/docs' + external: true + electron: + id: electron + name: Electron + href: 'https://electronjs.org/docs' + external: true + codeql: + id: codeql + name: 'CodeQL' + href: 'https://codeql.github.com/docs' + external: true --- diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md index 63ef9134f5..d241c01943 100644 --- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md +++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md @@ -1,18 +1,16 @@ --- -title: Managing available metrics and reports -intro: 'You can enable and disable specific metrics across {% data variables.product.prodname_insights %}.' +title: 利用可能なメトリクスとレポートの管理 +intro: '{% 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: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.' +permissions: '{% data variables.product.prodname_insights %}の管理権限を持っている人は、利用可能なメトリクスやレポートを管理できます。' versions: enterprise-server: '*' --- -When you disable a metric, the metric will not be visible for any user, anywhere on {% data variables.product.prodname_insights %}. +メトリクスを無効化すると、そのメトリクスはどのユーザからも、{% data variables.product.prodname_insights %}のどこからも見えなくなります。 {% data reusables.github-insights.settings-tab %} -2. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Toggle reports**. - ![Toggle reports tab](/assets/images/help/insights/toggle-reports-tab.png) -3. To the right of the metric you want to manage, use the **Enabled** or **Disabled** drop-down menu. - ![Drop-down menu to toggle metric](/assets/images/help/insights/toggle-report-drop-down.png) +2. **{% octicon "gear" aria-label="The gear icon" %} Settings（{{ octicon-gear The gear icon }}設定）**の下で、**Toggle reports（レポートの切り替え）**をクリックしてください。 ![レポートの切り替えタブ](/assets/images/help/insights/toggle-reports-tab.png) +3. 管理したいメトリクスの右で、** Enabled（有効）**あるいは**Disabled（無効）**ドロップダウンメニューを使ってください。 ![メトリクスの切り替えのドロップダウンメニュー](/assets/images/help/insights/toggle-report-drop-down.png) diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md new file mode 100644 index 0000000000..c8155dced2 --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -0,0 +1,33 @@ +--- +title: Organizationについて +intro: Organizationは、企業やオープンソースプロジェクトが多くのプロジェクトにわたって一度にコラボレーションできる共有アカウントです。 オーナーと管理者は、Organizationのデータとプロジェクトへのメンバーのアクセスを、洗練されたセキュリティ及び管理機能で管理できます。 +redirect_from: + - /articles/about-organizations + - /github/setting-up-and-managing-organizations-and-teams/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} +### Organization と Enterprise アカウント + +Enterprise アカウントは、複数の {% data variables.product.prodname_dotcom_the_website %} Organization のポリシーと支払いを集中管理するために利用できます。 + +enterprise アカウントに属する Organization では、支払いは enterprise アカウントのレベルで管理され、Organization のレベルでは支払い設定は利用できません。 Enterprise のオーナーは、Enterprise アカウントですべての Organization に対するポリシーを設定することも、Organization のオーナーに Organization のレベルでポリシーを設定することを許可することもできます。 Organization のオーナーは、Enterprise アカウントのレベルで Organization に強制された設定を変更することはできません。 Organization のポリシーや設定について質問がある場合は Enterprise アカウントのオーナーに問い合わせてください。 + +{% data reusables.gated-features.enterprise-accounts %} + +{% data reusables.organizations.org-ownership-recommendation %}詳細は、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」を参照してください。 + +### Organization の利用規約とデータ保護 + +会社、非営利団体、グループなどは、Organization として標準の利用規約あるいは企業向け利用規約に合意できます。 詳細は「[企業向け利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。 + +{% endif %} diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md new file mode 100644 index 0000000000..158307d074 --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -0,0 +1,49 @@ +--- +title: Organization ダッシュボードについて +intro: 'Organization のメンバーは、直近のアクティビティの更新情報を常時受け取り、作業中の Issue やプルリクエストを追跡したり、Organization をフォローしたりするために、Organization のダッシュボードにアクセスできます。' +redirect_from: + - /articles/about-your-organization-dashboard + - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Organization ダッシュボードへのアクセス + +{% data reusables.dashboard.access-org-dashboard %} + +### 最近のアクティビティを見つける + +ニュースフィードの [Recent activity] セクションでは、Organization で最近更新された Issue やプルリクエストを素早く見つけてフォローアップできます。 + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### Organization 内のリポジトリを見つける + +ダッシュボードの左サイドバーでは、自分がアクティブになっている Organization 内のリポジトリにアクセスできます。 + +![Organization 内で自分が最もアクティブなリポジトリのリスト](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) + +### Organization からのアクティビティの更新を受ける + +ニュースフィードの [All activity] セクションでは、Organization 内の他の Team やリポジトリからの更新情報を見ることができます。 + +[All activity] セクションは、Organization 内のすべての最近のアクティビティを表示します。これにはあなたがサブスクライブしていないリポジトリでのアクティビティや、フォローしていない人々のアクティビティも含まれます。 詳しい情報については、{% 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 %}」[リポジトリの Watch と Watch 解除](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}」および「[人をフォローする](/articles/following-people)」を参照してください。 + +たとえば Organization のニュースフィードは Organization 内の誰かが以下のようなことをしたときに 更新情報を知らせます: + - 新しいブランチを作成する + - Issue またはプルリクエストへのコメント + - プルリクエストのレビューコメントをサブミットする + - リポジトリをフォーク + - ウィキページを作成 + - コミットをプッシュする{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - パブリックリポジトリを作成する{% endif %} + +### さらなる情報 + +- [パーソナルダッシュボードについて](/articles/about-your-personal-dashboard) diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md new file mode 100644 index 0000000000..0df12f6523 --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -0,0 +1,26 @@ +--- +title: Organization のニュースフィードについて +intro: Organization のニュースフィードを使って、その Organization が所有しているリポジトリ上での最近のアクティビティを知ることができます。 +redirect_from: + - /articles/news-feed/ + - /articles/about-your-organization-s-news-feed + - /articles/about-your-organizations-news-feed + - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization のニュースフィードは、その Organization が所有しているリポジトリ上での他の人々のアクティビティを知らせます。 Organization のニュースフィードを使って、誰かによる Issue あるいはプルリクエストのオープン、クローズ、マージや、ブランチの作成や削除、タグあるいはリリースの作成、Issue、プルリクエスト、コミットへのコメント、あるいは新しいコミットの {% data variables.product.product_name %}へのプッシュを知ることができます。 + +### Organization のニュースフィードへのアクセス + +1. 自分の {% data variables.product.product_name %}アカウントに {% data variables.product.signin_link %}します。 +2. 自分の {% data reusables.user_settings.personal_dashboard %}を開きます。 +3. ページの左上隅にあるアカウントコンテキストスイッチャーをクリックします。 ![Enterprise のコンテキストスイッチャーボタン](/assets/images/help/organizations/account_context_switcher.png) +4. ドロップダウンメニューから Organization を選択します。{% 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/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md new file mode 100644 index 0000000000..91a1615a41 --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -0,0 +1,34 @@ +--- +title: Organization の設定へのアクセス +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 + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings +intro: 'Organization アカウントの設定ページには、支払い、Team のメンバーシップ、リポジトリ設定など、アカウントを管理するいくつかの方法があります。' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**ヒント:** Organization の支払い情報とアカウント設定を見て変更できるのは、Organization のオーナーと支払いマネージャーのみです。 {% 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/ja-JP/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000..35cb2a0fe7 --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md @@ -0,0 +1,28 @@ +--- +title: 新しい Organization をゼロから作成 +intro: Organization を作成して、リポジトリへの細かなアクセス許可を適用します。 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /articles/creating-a-new-organization-from-scratch + - /admin/user-management/creating-organizations + - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch +topics: + - organizations + - teams +--- + +ゼロから作成されたばかりの新しい Organization には、何のリポジトリも関連付けられていません。 自分の Organization へのリポジトリ追加に関する詳しい情報については、「[新しいリポジトリを作成する](/articles/creating-a-new-repository)」と「[リポジトリを移譲する](/articles/transferring-a-repository)」を参照してください。 + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. プロンプトに従って Organization を作成します。 {% if currentVersion == "free-pro-team@latest" %}Team で利用できるプランに関する詳しい情報については、「[{% data variables.product.prodname_dotcom %} の製品](/articles/githubs-products)」を参照してください。{% endif %} + +### 参考リンク + +{% if currentVersion == "free-pro-team@latest" %} +- [支払い請求先メールアドレスを設定する](/articles/setting-your-billing-email){% endif %} +- [Organization について](/articles/about-organizations) diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md new file mode 100644 index 0000000000..48f8a30abf --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md @@ -0,0 +1,22 @@ +--- +title: Organization のグループでコラボレーションする +intro: グループの人々は、Organization のアカウントで、多くのプロジェクトをまたいで同時にコラボレーションできます。 +redirect_from: + - /articles/creating-a-new-organization-account/ + - /articles/collaborating-with-groups-in-organizations + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000..f069a5b72b --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -0,0 +1,50 @@ +--- +title: Organization のインサイトを表示する +intro: 'Organization のインサイトは、Organization のアクティビティ、コントリビューション、および依存関係についてのデータを提供します。' +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/viewing-insights-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization のメンバー全員が Organization のインサイトを表示できます。 詳細は「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」を参照してください。 + +Organization のメンバーが、コードについてコラボレートや作業をするため {% data variables.product.product_name %} をどう使っているかについて、より深く理解するために、Organization activity insights を使用できます。 dependency insights は、Organization のオープンソース利用について追跡、レポート、および行動するため役立ちます。 + +### Organization activity insights を表示する + +{% note %} + +**注釈:** Organization activity insights は現在パブリックベータであり、変更されることがあります。 + +{% endnote %} + +Organization activity insights を使えば、Issue やプルリクエストアクティビティ、使用されている言語の上位、Organization のメンバーが時間を費やした場所についての累積的情報などを含む、Organization 全体や特定のリポジトリに関するデータの視覚的表現を月ごと、週ごと、年ごとに表示できます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Organization 名の下にある {% octicon "graph" aria-label="The bar graph icon" %} [**Insights**] をクリックします。 ![[organization insights] タブをクリックする](/assets/images/help/organizations/org-nav-insights-tab.png) +4. オプションで、ページ右上において、表示するデータを直近**1 週間**、**1 か月**、 **1 年**から選びます。 ![org insights を表示する期間を選択する](/assets/images/help/organizations/org-insights-time-period.png) +5. オプションで、ページ右上において、データを表示するリポジトリを最大 3 つまで選んで、[**Apply**] をクリックします。 ![org insights を表示するリポジトリを選択する](/assets/images/help/organizations/org-insights-repos.png) + +### Organization dependency insights を表示する +dependency insights を使えば、あなたの Organization が頼るオープンソースプロジェクトの脆弱性、ライセンスその他の重要情報を表示できます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Organization 名の下にある {% octicon "graph" aria-label="The bar graph icon" %} [**Insights**] をクリックします。 ![メイン Organization ナビゲーションバーの [Insights] タブ](/assets/images/help/organizations/org-nav-insights-tab.png) +4. この Organization への依存関係を表示するには、[**Dependencies**] をクリックします。 ![メイン Organization ナビゲーションバーの下にある [Dependencies] タブ](/assets/images/help/organizations/org-insights-dependencies-tab.png) +5. あなたの {% data variables.product.prodname_ghe_cloud %} Organization の dependency insights をすべて表示するには、[**My organizations**] をクリックします。 ![[Dependencies] タブの下にある [My organizations] ボタン](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) +6. [**Open security advisories**] および [**Licenses**] グラフの結果をクリックすることで、脆弱性ステータス、ライセンスまたはその 2 つを組み合わせてフィルタリングできます。 ![Organization の脆弱性およびライセンスのグラフ](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +7. 各脆弱性の隣にある [{% octicon "package" aria-label="The package icon" %} **dependents**] をクリックして、Organization でどの依存関係が各ライブラリを使っているかを表示できます。 ![Organization の脆弱性のある依存関係](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) + +### 参考リンク + - [Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations) + - [リポジトリの依存関係を見る](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository) + - [Organization dependency insights の可視性を変更する](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights) + - [Enterprise アカウントに dependency insights に関するポリシーを施行する](/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account) diff --git a/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md new file mode 100644 index 0000000000..2dd0944f9a --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -0,0 +1,49 @@ +--- +title: Team ディスカッションについて +intro: 'Team は、Organization 内の Team のページ内のディスカッションポストにおける好きな話題について、計画をしたり、更新をしたり、議論をしたりできます。' +redirect_from: + - /articles/about-team-discussions + - /github/building-a-strong-community/about-team-discussions + - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - コミュニティ +--- + +{% data reusables.organizations.team-discussions-purpose %} + +Organization のメンバーは、誰でも Team のページにポストしたり、パブリックなディスカッションに参加したりできます。 {% data reusables.organizations.team-discussions-permissions %} + +![パブリックおよびプライベートのディスカッションを持つ Team ページのディスカッションタブ](/assets/images/help/organizations/team-page-discussions-tab.png) + +Team のディスカッションにリンクを張って、別のところから参照できます。 重要なポストは Team のページにピン止めして、後で簡単に参照できます。 詳しい情報については[Team のディスカッションのピン止め](/organizations/collaborating-with-your-team/pinning-a-team-discussion)を参照してください。 + +![ピン止めされたディスカッションを持つ、Team ページの [Pinned] ディスカッションタブ](/assets/images/help/organizations/team-discussions-pinned.png) + +{% data reusables.organizations.team-discussions-default %}オーナーは Organization 全体にわたって Team ディスカッションを無効化できます。 詳しい情報については [Organization の Team ディスカッションの無効化](/articles/disabling-team-discussions-for-your-organization)を参照してください。 + +### Team ディスカッションの通知 + +Team のページのパブリックなディスカッションに誰かがポストしたり返信したりしたとき、その Team のメンバーや子チームのメンバーは、メールあるいは Web 通知を受け取ります。 誰かが Team のページ上のプライベートなディスカッションにポストあるいは返信した場合は、その Team のメンバーだけが通知を受け取ります。 + +{% tip %} + +**ヒント:** 通知の設定によって、更新はメール、{% data variables.product.product_name %}上の Web 通知、あるいはその両方で受け取ることになります。 詳しい情報については、% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)」{% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications)」および「[Web 通知について](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}」を参照してください。 + +{% endtip %} + +デフォルトでは、ユーザ名が Team のディスカッション内でメンションされると、ユーザ名をメンションしたポストと、そのポストに対する返信についての通知を受けることになります。 また、デフォルトでは、ポストに返信した場合、そのポストに対する他の返信についても通知を受け取ることになります。 + +Team のディスカッションに対する通知をオフにするには、特定のディスカッションのポストのサブスクライブを解除するか、Watch の解除あるいは特定の Team のディスカッションを完全に無視するよう通知設定を変更できます。 Team のディスカッションの Watch を解除している場合でも、特定のディスカッションのポストについての通知をサブスクライブすることはできます。 + +詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)」{% else %}「[通知のサブスクライブとサブスクライブ解除](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}」および「[入れ子チーム](/articles/about-teams/#nested-teams)」を参照してください。 + +### 参考リンク + +- [{% data variables.product.prodname_dotcom %}での会話について](/articles/about-conversations-on-github) +- [Team について](/articles/about-teams) +- [Team ディスカッションの作成](/organizations/collaborating-with-your-team/creating-a-team-discussion) +- [Team ディスカッションの編集または削除](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion) diff --git a/translations/ja-JP/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/ja-JP/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md new file mode 100644 index 0000000000..34a2e05bb6 --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md @@ -0,0 +1,30 @@ +--- +title: Team ディスカッションの作成 +intro: 'Organization のメンバーであれば誰でも _public_ Team ディスカッションのポストを作成できます。 _private_ Team ディスカッションのポストを作成するには、Team のメンバーか Organization のオーナーでなければなりません。' +redirect_from: + - /articles/creating-a-team-discussion + - /github/building-a-strong-community/creating-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - コミュニティ +--- + +{% data reusables.organizations.team-discussions-permissions %} 詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/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. Team ディスカッションのタイトルとコメントを入力して会話を開始します。 ![新しい Team ディスカッション コメント](/assets/images/help/projects/team-discussions-comment.png) +7. 任意で、自分のポストをプライベートにするかパブリックにするかをドロップダウンメニューから選択します。 ![Team ディスカッションのプライバシー設定メニュー](/assets/images/help/projects/team-discussions-privacy-menu.png) +8. [**Comment**] をクリックします。 ![新しい Team ディスカッションの [Comment] ボタン](/assets/images/help/projects/team-discussions-comment-button.png) + +### 参考リンク + + - "[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)" + - [Team ディスカッションの編集または削除](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion) + - "[Team ディスカッションをピン止めする](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/ja-JP/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/ja-JP/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000..b68a2b7c7f --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,28 @@ +--- +title: Team ディスカッションの編集または削除 +intro: 'Organization のメンバーは、Team のページでディスカッションを編集または削除できます。 Organization のメンバーであれば、ディスカッションを編集または削除できます。' +redirect_from: + - /articles/editing-or-deleting-a-team-discussion + - /github/building-a-strong-community/editing-or-deleting-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - コミュニティ +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. 編集または削除する Team ディスカッションの横にある {% octicon "kebab-horizontal" aria-label="The edit icon" %} をクリックします。 +7. [**Edit**] をクリックします。 オプションで、[**Delete**] をクリックします。 ![Team ディスカッションの編集ボタン](/assets/images/help/projects/edit-team-discussions-button.png) +8. Team ディスカッションのタイトルとコメントを必要に応じて変更し、[**Update comment**] をクリックします。 ![[Update comment] ボタン](/assets/images/help/projects/update-comment-button.png) + +### 参考リンク + + - "[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)" + - [Team ディスカッションの作成](/organizations/collaborating-with-your-team/creating-a-team-discussion) + - "[Team ディスカッションをピン止めする](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/ja-JP/content/organizations/collaborating-with-your-team/index.md b/translations/ja-JP/content/organizations/collaborating-with-your-team/index.md new file mode 100644 index 0000000000..04a615f9b3 --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-your-team/index.md @@ -0,0 +1,19 @@ +--- +title: Team とコラボレーションする +intro: 'Organization 内で、Team は Team ディスカッションを使い、プロジェクトをまたいで協力して作業できます。' +redirect_from: + - /articles/collaborating-with-your-team + - /github/building-a-strong-community/collaborating-with-your-team + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - コミュニティ +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/ja-JP/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md new file mode 100644 index 0000000000..97cea36a2d --- /dev/null +++ b/translations/ja-JP/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +title: Team ディスカッションをピン止めする +intro: '重要なディスカッションは、参照しやすいように Organization の Team ページにピン止めすることができ、必要がなくなったらピン止めを解除できます。' +redirect_from: + - /articles/pinning-a-team-discussion + - /github/building-a-strong-community/pinning-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - コミュニティ +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +5. ピン止めする Team ディスカッションの横にある {% octicon "pin" aria-label="The pin icon" %} をクリックします。 アイコンをクリックしてディスカッションのピン止めを解除することもできます。 ![ディスカッションをピン止めする](/assets/images/help/projects/pin-discussion-button.png) + +### 参考リンク + + - "[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)" + - [Team ディスカッションの作成](/organizations/collaborating-with-your-team/creating-a-team-discussion) + - [Team ディスカッションの編集または削除](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion) diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000..f8ebd9038c --- /dev/null +++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,26 @@ +--- +title: 2 要素認証と SAML シングルサインオンについて +intro: Organization の管理者は、SAML シングルサインオンと 2 要素認証を共に有効化し、Organization のメンバーの認証方法を追加できます。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-two-factor-authentication-and-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +2 要素認証 (2FA) は、Organization のメンバーに基本的な認証を提供します。 2FA を有効化することで、Organization の管理者はメンバーの {% data variables.product.product_name %} アカウントが悪用される可能性を抑制できます。 2FA に関する詳細は「[2 要素認証について](/articles/about-two-factor-authentication)」を参照してください。 + +認証方法を追加するために、Organization の管理者は [SAML シングルサインオン (SSO) を有効化](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)し、Organization のメンバーが Organization へのアクセスにシングルサインオンを使わなければならないようにすることができます。 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。 + +2 要素認証と SAML SSO をどちらも有効化した場合、Organization のメンバーは以下のようにしなければなりません: +- {% data variables.product.product_name %} アカウントへのログインには 2 要素認証を利用 +- Organization へのアクセスにはシングルサインオンを利用 +- API あるいは Git のアクセスには認可されたトークンを使い、トークンの認可にはシングルサインオンを利用 + +### 参考リンク + +- [Organization 用の SAML シングルサインオンの強制](/articles/enforcing-saml-single-sign-on-for-your-organization) diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md new file mode 100644 index 0000000000..f8cc674689 --- /dev/null +++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -0,0 +1,16 @@ +--- +title: SAML シングルサインオンでの Organization へのアクセスを許可する +intro: 'Organization の管理者は、SAML シングルサインオンでの Organization へのアクセスを許可できます。 このアクセス権は、Organization メンバー、ボット、およびサービスアカウントに付与することができます。' +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000..a0296ee648 --- /dev/null +++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,25 @@ +--- +title: SAML シングルサインオンでボットおよびサービスアカウントを管理する +intro: SAML シングルサインオンを有効にしている Organization は、ボットおよびサービスアカウントへのアクセスを維持できます。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +ボットおよびサービスアカウントへのアクセスを維持するために、Organization の管理者はその Organization に対して SAML シングルサインオンを[有効化](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)することはできますが、[強制](/articles/enforcing-saml-single-sign-on-for-your-organization)することは**できません**。 Organization に対して SAML シングルサインオンを強制する必要がある場合は、アイデンティティプロバイダ (IdP) を利用してボットまたはサービスアカウントに外部アイデンティティを作成する方法があります。 + +{% warning %} + +**注釈:** Organization に対して SAML シングルサインオンを強制しておらず、ボットおよびサービスアカウントに対して IdP で外部 ID を設定して**いない**場合、それらは Organization から削除されます。 + +{% endwarning %} + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000..cdb837464e --- /dev/null +++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,64 @@ +--- +title: 組織へのメンバーの SAML アクセスの表示と管理 +intro: 'Organization のメンバーのリンクされたアイデンティティ、アクティブなセッション、認可されたクレデンシャルの表示と取り消しが可能です。' +permissions: Organization のオーナーは、組織へのメンバーの SAML アクセスを表示したり管理したりすることもできます。 +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Organization への SAML アクセスについて + +Organization に対する SAML シングルサインオンを有効にすると、各 Organization メンバーは ID プロバイダ (IdP) での外部アイデンティティを、既存の {% data variables.product.product_name %} アカウントにリンクできます。 {% data variables.product.product_name %}上の Organizationのリソースにアクセスするには、メンバーはアクティブなSAMLセッションをブラウザーに持っていなければなりません。 OrganizationのリソースにAPIまたはGitを使ってアクセスするには、メンバーは、メンバーがOrganizationでの利用のために認可した個人アクセストークンもしくはSSHキーを使わなければなりません。 + +各メンバーのリンクされたアイデンティティ、アクティブなセッション、同じページで認可されたクレデンシャルの表示と取り消しが可能です。 + +### リンクされているアイデンティティの表示と取り消し + +{% 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 %} + +### アクティブな 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 %} + +### 認可されたクレデンシャルの表示と取り消し + +{% 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 %} + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) +- [Enterprise アカウントへのユーザの SAML アクセスの表示および管理](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account) diff --git a/translations/ja-JP/content/organizations/index.md b/translations/ja-JP/content/organizations/index.md new file mode 100644 index 0000000000..e0ef400500 --- /dev/null +++ b/translations/ja-JP/content/organizations/index.md @@ -0,0 +1,32 @@ +--- +title: Organization および Team +shortTitle: Organization +intro: プロジェクトおよびデータへのアクセスを管理し、Organization の設定をカスタマイズしながら、多くのプロジェクトにわたってコラボレーションします。 +redirect_from: + - /articles/about-improved-organization-permissions/ + - /categories/setting-up-and-managing-organizations-and-teams + - /github/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_with_intro /collaborating-with-groups-in-organizations %} +{% link_with_intro /managing-membership-in-your-organization %} +{% link_with_intro /managing-peoples-access-to-your-organization-with-roles %} +{% link_with_intro /organizing-members-into-teams %} +{% link_with_intro /collaborating-with-your-team %} +{% link_with_intro /managing-access-to-your-organizations-repositories %} +{% link_with_intro /managing-access-to-your-organizations-project-boards %} +{% link_with_intro /managing-access-to-your-organizations-apps %} +{% link_with_intro /managing-organization-settings %} +{% link_with_intro /restricting-access-to-your-organizations-data %} +{% link_with_intro /keeping-your-organization-secure %} +{% link_with_intro /managing-saml-single-sign-on-for-your-organization %} +{% link_with_intro /granting-access-to-your-organization-with-saml-single-sign-on %} +{% link_with_intro /managing-git-access-to-your-organizations-repositories %} +{% link_with_intro /migrating-to-improved-organization-permissions %} diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md new file mode 100644 index 0000000000..4f14500bd8 --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md @@ -0,0 +1,24 @@ +--- +title: Organization を安全に保つ +intro: 'Organization のオーナーがプロジェクトとデータを安全に保つ方法はいくつかあります。 Organization のオーナーは、不正な、または悪意のあるアクティビティが発生していないことを確認するために、Organization の監査ログ{% if currentVersion != "github-ae@latest" %}、メンバーの 2 要素認証ステータス、{% endif %} そしてアプリケーション設定を定期的にレビューする必要があります。' +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure + - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000..ad09c18675 --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Organization に対する許可 IP アドレスを管理する +intro: 接続を許可される IP アドレスのリストを設定することで、Organization のアセットに対するアクセスを制限することができます。 +product: '{% data reusables.gated-features.allowed-ip-addresses %}' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization のオーナーは、Organization に対する許可 IP アドレスを管理できます。 + +### 許可 IP アドレスについて + +特定の IP アドレスに対する許可リストを設定することで、Organization アセットへのアクセスを制限できます。 {% 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 %} + +Enterprise アカウントで Organization に対して許可される IP アドレスを設定することもできます。 詳しい情報については、{% if currentVersion == "github-ae@latest" %}「[Enterprise へのネットワークトラフィックを制限する](/admin/configuration/restricting-network-traffic-to-your-enterprise)」を参照してください。 {% else %}「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)」を参照してください。{% endif %} + +### 許可 IP アドレスを追加する + +{% 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 %} + +### 許可 IP アドレスを有効化する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +3. [IP allow list] で、「**Enable IP allow list**」を選択します。 ![IP アドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) +4. [**Save**] をクリックします。 + +### 許可 IP アドレスを編集する + +{% 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. [**Update**] をクリックします。 + +### 許可 IP アドレスを削除する + +{% 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 %} + +### IP許可リストで {% data variables.product.prodname_actions %} を使用する + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-actions.ip-allow-list-hosted-runners %} + +{% else %} + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +{% endif %} diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000..0ca55b8303 --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,143 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +topics: + - organizations + - teams +--- + +### セキュリティおよび分析設定の管理について + +{% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 {% 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 %} + +### セキュリティと分析の設定を表示する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security-and-analysis %} + +表示されるページでは、Organization 内のリポジトリのすべてのセキュリティおよび分析機能を有効化または無効化にできます。 + +{% if currentVersion == "free-pro-team@latest" %}Organization が {% data variables.product.prodname_GH_advanced_security %} のライセンスを持つ Enterprise に属している場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_GH_advanced_security %} のライセンスをお持ちの場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれています。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %} + +{% if currentVersion == "github-ae@latest" %}このページには、{% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。{% endif %} + +### すべての既存のリポジトリに対して機能を有効化または無効化する + +すべてのリポジトリの機能を有効化または無効化できます。 {% if currentVersion == "free-pro-team@latest" %}変更が Organization 内のリポジトリに与える影響は、リポジトリの可視性によって決まります。 + +- **依存関係グラフ** - この機能はパブリックリポジトリに対して常に有効になっているため、変更はプライベートリポジトリにのみ影響します。 +- **{% 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 %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + +1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 +2. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_GH_advanced_security %} のライセンスにシートがない場合、「{% data variables.product.prodname_GH_advanced_security %}」の制御は無効になります。{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![[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 %} + {% if currentVersion == "github-ae@latest" %} + ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +3. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![新規のリポジトリの [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 %} +4. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![機能 を無効または有効にするボタン](/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 %} + {% endif %} + {% if currentVersion == "github-ae@latest" %} +3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Organization 内の適格なすべてのリポジトリの機能を有効化するボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} + + {% data reusables.security.displayed-information %} + +### 新しいリポジトリが追加されたときに機能を自動的に有効化または無効化する + +1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/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 %} + {% if currentVersion == "github-ae@latest" %} + ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### {% data variables.product.prodname_dependabot %} のプライベート依存関係へのアクセスを許可する + +{% data variables.product.prodname_dependabot %} は、プロジェクト内の古い依存関係参照をチェックし、それらを更新するためのプルリクエストを自動的に生成できます。 これを行うには、{% data variables.product.prodname_dependabot %} がすべてのターゲット依存関係ファイルにアクセスできる必要があります。 通常、1 つ以上の依存関係にアクセスできない場合、バージョン更新は失敗します。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} バージョン更新について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 + +デフォルトでは、{% data variables.product.prodname_dependabot %} はプライベートリポジトリまたはプライベートパッケージレジストリにある依存関係を更新できません。 ただし、依存関係が、その依存関係を使用するプロジェクトと同じ Organization 内のプライベート {% data variables.product.prodname_dotcom %} リポジトリにある場合は、ホストリポジトリへのアクセスを許可することで、{% data variables.product.prodname_dependabot %} がバージョンを正常に更新できるようにすることができます。 + +コードがプライベートレジストリ内のパッケージに依存している場合は、リポジトリレベルでこれを設定することにより、{% data variables.product.prodname_dependabot %} がこれらの依存関係のバージョンを更新できるようにすることができます。 これを行うには、リポジトリの _dependabot.yml_ ファイルに認証の詳細を追加します。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries) 」を参照してください。 + +{% data variables.product.prodname_dependabot %} がプライベート {% data variables.product.prodname_dotcom %} リポジトリにアクセスできるようにするには： + +1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 +1. [{% data variables.product.prodname_dependabot %} private repository access] の下で、[**Add private repositories**] または [**Add internal and private repositories**] をクリックします。 ![[Add repositories] ボタン](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. 許可するリポジトリの名前を入力します。 ![[Add repositories] ボタン](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. 許可するリポジトリをクリックします。 + +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. ![リポジトリを削除する [X] ボタン](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### Organization 内の個々のリポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する + +[Settings] タブから、リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能へのアクセスを管理できます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 ただし、Organization の [Settings] タブから、リポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を無効にすることもできます。 + +1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。 +1. {% data variables.product.prodname_GH_advanced_security %} が有効になっている Organization 内のすべてのリポジトリのリストを表示するには、「{% data variables.product.prodname_GH_advanced_security %} リポジトリ」セクションまでスクロールします。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) この表は、各リポジトリの一意のコミッターの数を示しています。 これは、{% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除することによりライセンスで解放できるシートの数です。 ライセンスのサイズは、Organization レベルのライセンスに対して表示されます。 詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}のライセンスについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)」を参照してください。 +1. リポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除し、リポジトリ固有のコミッターが使用するシートを解放するには、隣接する {% octicon "x" aria-label="X symbol" %} をクリックします。 +1. 確認ダイアログで、[**Remove repository**] をクリックして、{% data variables.product.prodname_GH_advanced_security %} の機能へのアクセスを削除します。 + +{% note %} + +**注釈:** リポジトリの {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する場合は、影響を受ける開発チームと連絡を取り、変更が意図されたものかを確認する必要があります。 これにより、失敗したコードスキャンの実行をデバッグすることに時間を費すことがなくなります。 + +{% endnote %} + +{% 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 %}{% if currentVersion != "github-ae@latest" %} +- [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) +- 「[プロジェクトの依存関係にある脆弱性を管理する](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)」{% endif %} diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..5a231b6151 --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Organization で 2 要素認証の義務化を準備する +intro: '2 要素認証を義務化する前に、予定されている変更についてユーザに通知し、どのユーザーが 2 要素認証をすでに使用しているかを確認することができます。' +redirect_from: + - /articles/preparing-to-require-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +Organization で 2 要素認証を義務付ける 1 週間以上前に、{% if currentVersion == "free-pro-team@latest" %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバーと外部コラボレーター{% endif %}に通知することをおすすめします。 + +Organization で 2 要素認証を必須にすると、2 要素認証を使わないメンバー、外部コラボレーター、および支払いマネージャー (ボットアカウントを含む) は Organization から削除され、そのリポジトリにアクセスできなくなります。 Organization のプライベートリポジトリのフォークへのアクセスも失います。 + +組織で 2 要素認証を必須にする前に、次の準備をすることをおすすめします: + - 個人アカウントで [2 要素認証を有効化する](/articles/securing-your-account-with-two-factor-authentication-2fa/) + - Organization のユーザに、自分のアカウントで 2 要素認証をセットアップするよう指示する + - [Organization でどのユーザが 2 要素認証を有効にしているか](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/)を確認する + - 2 要素認証が有効になると、2 要素認証を使っていないユーザは自動的に Organization から削除されることを告知する diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..a9d4454882 --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,80 @@ +--- +title: Organization で 2 要素認証を要求する +intro: 'Organization のオーナーは、{% if currentVersion == "free-pro-team@latest" %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバーおよび外部のコラボレーター{% endif %}に、それぞれの個人アカウントに対する 2 要素認証を有効にするように義務付けることで、悪意のある行為者が Organization のリポジトリや設定にアクセスしにくくすることができます。' +redirect_from: + - /articles/requiring-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +### Organization の2 要素認証について + +{% data reusables.two_fa.about-2fa %} Organization のすべての{% if currentVersion == "free-pro-team@latest" %}メンバー、外部コラボレーター、支払いマネージャー{% else %}メンバーおよび外部コラボレーター{% endif %}に、{% data variables.product.product_name %} で 2 要素認証を有効にすることを義務付けることができます。 2 要素認証の詳細は「[2 要素認証 (2FA) でアカウントを保護する](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" %} + +Enterprise で Organization の 2 要素認証を必須にすることもできます。 詳細は、「[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)」を参照してください。 + +{% endif %} + +{% warning %} + +**警告:** + +- Organization に対して 2 要素認証の使用を義務付ける場合、2FA を使用しない{% if currentVersion == "free-pro-team@latest" %}メンバー、外部コラボレーター、支払いマネージャー {% else %}メンバーおよび外部コラボレーター{% endif %} (ボット アカウントを含む) は Organization から削除され、そのリポジトリへのアクセス権が失われます。 Organization のプライベートリポジトリのフォークへのアクセスも失います。 Organization から削除されてから 3 か月以内に、個人アカウントに対して 2 要素認証を有効にすれば、[それらのアカウントが持っていたアクセス特権と設定を復元](/articles/reinstating-a-former-member-of-your-organization)できます。 +- 義務付けられた 2 要素認証を有効にした後に、Organization のオーナー、メンバー、{% if currentVersion == "free-pro-team@latest" %}支払いマネージャー、{% endif %} または外部コラボレーターがそれぞれの個人アカウントで 2 要素認証を無効にすると、それらは Organization から自動的に削除されます。 +- あなたが、2 要素認証を義務付けている Organization の唯一のオーナーである場合、その Organization での 2 要素認証義務を無効にしなければ、あなたの個人アカウントの 2 要素認証を無効にすることはできません。 + +{% endwarning %} + +{% data reusables.two_fa.auth_methods_2fa %} + +### 必要な環境 + +{% if currentVersion == "free-pro-team@latest" %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバーおよび外部コラボレーター{% endif %}に、 2 要素認証を使用することを義務付けるには、まず{% data variables.product.product_name %} の自分自身の個人アカウントで 2 要素認証を有効にする必要があります。 詳細は「[2 要素認証 (2FA) でアカウントを保護する](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)」を参照してください。 + +2 要素認証の使用を義務付ける前に、{% if currentVersion == "free-pro-team@latest" %}Organization のメンバー、外部コラボレーター、支払いマネージャー {% else %}Organization のメンバーおよび外部コラボレータ{% endif %}に通知して、それぞれのアカウントで 2 要素認証をセットアップするように依頼することをおすすめします。 メンバーと外部のコラボレーターがすでに 2 要素認証を使用しているかどうかを確認できます。 詳細は「[Organization 内のユーザが 2 要素認証を有効にしているか確認する](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)」を参照してください。 + +### Organization で 2 要素認証を要求する + +{% 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. Organization から削除されるメンバーまたは外部コラボレーターが存在する場合、彼らに招待状を送信して、元の権限と Organization へのアクセス権を復元できるようにすることをおすすめします。 招待を受諾できるためには、まず 2 要素認証が有効でなければなりません。 +{% endif %} + +### Organization から削除された人々を表示する + +2 要素認証義務に従っていないために Organization から自動的に削除された人々を表示するには、Organization から削除された人々を対象に、[Organization の Audit log を検索する](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log)ことができます。 Audit log イベントでは、削除された理由が 2 要素認証義務に従わなかったことなのかどうかが示されます。 + +![2 要素認証の違反により削除されたユーザーを示す Audit log イベント](/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. 検索クエリを入力します。 以下のように検索します: + - 削除された Organization のメンバーを検索するには、検索クエリで `action:org.remove_member` を使用します + - 削除された外部コラボレーターを検索するには、検索クエリで `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)を使用すれば、Organization から削除された人々を表示できます。 + +### 削除されたメンバーと外部コラボレーターを Organization に復帰できるようにする + +2要素認証の利用の要求を有効化したときにOrganizationから削除されたメンバーあるいは外部のコラボレータがいれば、その人たちには削除されたことを知らせるメールが届きます。 そうなった場合には、彼らは個人アカウントで2FAを有効化し、OrganizationのオーナーにOrganizationへのアクセスを求めなければなりません。 + +### 参考リンク + +- 「[Organization 内のユーザーが 2 要素認証を有効にしているかどうかを表示する](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)」 +- 「[2 要素認証でアカウントを保護する](/articles/securing-your-account-with-two-factor-authentication-2fa)」 +- "[Organization の以前のメンバーを回復する](/articles/reinstating-a-former-member-of-your-organization)" +- "[以前の外部コラボレーターの Organization へのアクセス権を回復する](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000..1af16e0c5c --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,31 @@ +--- +title: メール通知を承認済みドメインに制限する +intro: 'Organization の情報が個人アカウントに漏れるのを防ぐために、Organization のオーナーは Organization アクティビティに関するメール通知を検証済みドメインに制限できます。' +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### メールの制限について + +Organization で制限付きのメール通知が有効になっている場合、メンバーは Organization の検証済みドメインに関連付けられたメールアドレスのみを使用して、Organization のアクティビティに関するメール通知を受信できます。 詳しい情報については [Organization のドメインの検証](/articles/verifying-your-organization-s-domain)を参照してください。 + +外部のコラボレーターは、検証済みドメインへのメール通知の制限の対象になりません。 外部コラボレーターに関する詳しい情報については「[Organization の権限レベル](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)」を参照してください。 + +Enterprise アカウントがオーナーの Organization の場合、Organization のメンバーは、Organization の検証済みドメインに加えて、Enterprise アカウントの検証済みドメインから通知を受け取ることができます。 詳しい情報については、「[Enterprise アカウントのドメインを検証する](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)」を参照してください。 + +### メール通知を承認済みドメインに制限する + +{% 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. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000..90c0527b29 --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,643 @@ +--- +title: Organization の Audit log をレビューする +intro: 'Audit log により、Organization の管理者は Organization のメンバーによって行われたアクションをすばやくレビューできます。 これには、誰がいつ何のアクションを実行したかなどの詳細が残されます。' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-the-audit-log-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Audit log にアクセスする + +Audit log には、過去 90 日以内に Organization に影響を与えたアクティビティによってトリガーされたイベントが一覧表示されます。 Organization の Audit log にアクセスできるのはオーナーのみです。 + +{% 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 %} + +### Audit log を検索する + +{% data reusables.audit_log.audit-log-search %} + +#### 実行されたアクションに基づく検索 + +特定のイベントを検索するには、クエリで `action` 修飾子を使用します。 Audit log に一覧表示されるアクションは以下のカテゴリに分類されます。 + +| カテゴリ名 | 説明 | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`アカウント`](#account-category-actions) | Organization アカウントに関連するすべてのアクティビティが対象です。 | +| [`advisory_credit`](#advisory_credit-category-actions) | {% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリのコントリビューターのクレジットに関連するすべてのアクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | +| [`支払い`](#billing-category-actions) | Organization の支払いに関連するすべてのアクティビティが対象です。 | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | 既存のリポジトリ内の {% data variables.product.prodname_dependabot %} アラートの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 | +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Organization 内に作成された新しいリポジトリ内の {% data variables.product.prodname_dependabot %} アラートの Organization レベルの設定アクティビティが対象です。 | +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | 既存のリポジトリ内の {% data variables.product.prodname_dependabot_security_updates %} の Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[{% 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) | Organization で作成された新しいリポジトリ内の {% data variables.product.prodname_dependabot_security_updates %} の Organization レベルの設定アクティビティが対象です。 | +| [`dependency_graph`](#dependency_graph-category-actions) | リポジトリの依存関係グラフの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Organization 内に作成された新しいリポジトリの Organization レベルの設定アクティビティが対象です。{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Team ページに投稿されたディスカッションに関連するすべてのアクティビティが対象です。 | +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Team ページに投稿されたディスカッションへの返答に関連するすべてのアクティビティが対象です。 | +| [`フック`](#hook-category-actions) | webhookに関連するすべてのアクティビティを含みます。 | +| [`integration_installation_request`](#integration_installation_request-category-actions) | Organization 内で使用するインテグレーションをオーナーが承認するよう求める、 Organization メンバーからのリクエストに関連するすべてのアクティビティが対象です。 | +| [`Issue`](#issue-category-actions) | Issue の削除に関連するアクティビティが対象です。 |{% if currentVersion == "free-pro-team@latest" %} +| [`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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} でのアプリのリストに関連するすべてのアクティビティが対象です。 | +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Organization 内のリポジトリの {% data variables.product.prodname_pages %} サイトの公開の管理に関連するすべてのアクティビティが対象です。 For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |{% endif %} +| [`org`](#org-category-actions) | Organization メンバーシップに関連するアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | 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) | Organization のリポジトリのデフォルトラベルに関連するすべてのアクティビティが対象です。{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | OAuth アプリに関連するすべてのアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`パッケージ`](#packages-category-actions) | {% data variables.product.prodname_registry %} に関連するすべてのアクティビティが対象です。{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Organization の GitHub への支払い方法に関連するすべてのアクティビティが対象です。{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Organization のプロフィール画像に関連するすべてのアクティビティが対象です。 | +| [`project`](#project-category-actions) | プロジェクト ボードに関連するすべての活動が対象です。 | +| [`protected_branch`](#protected_branch-category-actions) | 保護されたブランチ関連するすべてのアクティビティが対象です。 | +| [`repo`](#repo-category-actions) | Organization が所有するリポジトリに関連するアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | {% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリに関連するリポジトリレベルのアクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | [プライベート リポジトリに対するデータの使用を有効または無効にする](/articles/about-github-s-use-of-your-data)に関連するすべての活動が対象です。{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | プライベートリポジトリの依存関係グラフの有効化または無効化に関連する | +| {% if currentVersion == "free-pro-team@latest" %}リポジトリ{% endif %}レベルのアクティビティが含まれます。 詳しい情報については、「[依存関係グラフについて](/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" or currentVersion == "github-ae@latest" %} | | +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | シークレットスキャンに関連するリポジトリレベルのアクティビティが対象です。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | [脆弱性のある依存関係](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)の {% data variables.product.prodname_dependabot_alerts %} に関連するすべてのアクティビティが対象です。{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | {% data variables.product.prodname_dependabot %} アラートの リポジトリレベルの設定アクティビティが対象です。 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| [`secret_scanning`](#secret_scanning-category-actions) | 既存のリポジトリ内のシークレットスキャンの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | +| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Organization で作成された新しいリポジトリ内のシークレットスキャンの Organization レベルの設定アクティビティが対象です。 |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`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 ディスカッションに関連するすべてのアクティビティが対象です。 | + +次の用語を使用すれば、特定の一連の行動を検索できます。 例: + + * `action:team`はteamカテゴリ内でグループ化されたすべてのイベントを検索します。 + * `-action:hook` は webhook カテゴリ内のすべてのイベントを除外します。 + +各カテゴリには、フィルタできる一連の関連アクションがあります。 例: + + * `action:team.create`はTeamが作成されたすべてのイベントを検索します。 + * `-action:hook.events_changed` は webhook の変更されたすべてのイベントを除外します。 + +#### アクション時間に基づく検索 + +`created` 修飾子を使用して、行われた日時に基づいて Audit log 内のイベントをフィルタします。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +例: + + * `created:2014-07-08` は、2014 年 7 月 8 日に発生したイベントをすべて検索します。 + * `created:>=2014-07-08` は、2014 年 7 月 8 日かそれ以降に生じたすべてのイベントを検索します。 + * `created:<=2014-07-08`は、2014 年 7 月 8 日かそれ以前に生じたすべてのイベントを検索します。 + * `created:2014-07-01..2014-07-31`は、2014 年 7 月に起きたすべてのイベントを検索します。 + +Audit log には過去 90 日間のデータが存在しますが、`created` 修飾子を使用すればそれより前のイベントを検索できます。 + +#### 場所に基づく検索 + +修飾子 `country` を使用すれば、発信元の国に基づいて Audit log 内のイベントをフィルタリングできます。 国の 2 文字のショートコードまたはフル ネームを使用できます。 名前に空白がある国は引用符で囲む必要があることに注意してください。 例: + + * `country:de` は、ドイツで発生したイベントをすべて検索します。 + * `country:Mexico` はメキシコで発生したすべてのイベントを検索します。 + * `country:"United States"` はアメリカ合衆国で発生したすべてのイベントを検索します。 + +{% if currentVersion == "free-pro-team@latest" %} +### Audit log をエクスポートする + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### Audit log API を使用する + +GraphQL API{% if currentVersion == "free-pro-team@latest" %} または REST API を使用して Audit log を操作できます{% endif %}。 + +{% if currentVersion == "free-pro-team@latest" %} + +#### GraphQL API を使用する + +{% endif %} + +{% note %} + +**注釈**: {% data variables.product.prodname_enterprise %} を使用している Organization が Audit log GraphQL API を利用できます。 {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +IP の安全性を保ち、Organization のコンプライアンスを守るため、Audit log GraphQL API を使って、Audit log データのコピーを保存し、モニタリングできます。 +{% data reusables.audit_log.audit-log-api-info %} + +{% if currentVersion == "free-pro-team@latest" %} +GraphQL API を使用して Git イベントを取得することはできませんので、ご注意ください。 Git イベントを取得するには、代わりに REST API を使用してください。 詳しい情報については、「[`git` category actions](#git-category-actions)」を参照してください。 +{% endif %} + +GraphQL のレスポンスには、90 日から 120 日までのデータを含めることができます。 + +たとえば、GraphQL にリクエストして、Organization に新しく追加された Organization メンバー全員を表示できます。 詳細は「[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" %} + +#### REST API を使用する + +{% note %} + +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. + +{% endnote %} + +IP の安全性を保ち、Organization のコンプライアンスを守るため、Audit log REST API を使って、Audit log データのコピーを保存し、モニタリングできます。 +{% data reusables.audit_log.audit-log-api-info %} +* クローン、フェッチ、プッシュなどの Git イベント + +{% data reusables.audit_log.audit-log-git-events-retention %} + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endif %} + +### Audit log のアクション + +Audit log にイベントとして記録される最も一般的なアクションの概要です。 + +{% if currentVersion == "free-pro-team@latest" %} + +#### `account` カテゴリアクション + +| アクション | 説明 | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `billing_plan_change` | Organization の[支払いサイクル](/articles/changing-the-duration-of-your-billing-cycle)が変わるときにトリガーされます。 | +| `plan_change` | Organization の[プラン](/articles/about-billing-for-github-accounts)が変わるときにトリガーされます。 | +| `pending_plan_change` | Organization のオーナーまたは支払いマネージャーが[支払い済みサブスクリプションをキャンセルまたはダウングレードする](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/)ときにトリガーされます。 | +| `pending_subscription_change` | [{% data variables.product.prodname_marketplace %} の無料トライアルが始まるか期限切れになる](/articles/about-billing-for-github-marketplace/)ときにトリガーされます。 | + +#### `advisory_credit` カテゴリアクション + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `accept` | ユーザがセキュリティアドバイザリのクレジットを受け入れるとトリガーされます。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory)」を参照してください。 | +| `create` | セキュリティアドバイザリの管理者がクレジットセクションにユーザを追加するとトリガーされます。 | +| `decline` | ユーザがセキュリティアドバイザリのクレジットを拒否するとトリガーされます。 | +| `destroy` | セキュリティアドバイザリの管理者がクレジットセクションからユーザを削除するとトリガーされます。 | + +#### `billing` カテゴリアクション + +| アクション | 説明 | +| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| `change_billing_type` | Organization が[{% data variables.product.prodname_dotcom %} の支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 | +| `change_email` | Organization の[支払い請求先メール アドレス](/articles/setting-your-billing-email)が変わるときにトリガーされます。 | + +#### `dependabot_alerts` カテゴリアクション + +| アクション | 説明 | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Organization のオーナーが既存のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリの {% data variables.product.prodname_dependabot_alerts %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `enable` | Organization のオーナーが既存のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効にするとトリガーされます。 | + +#### `dependabot_alerts_new_repos` カテゴリアクション + +| アクション | 説明 | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Organization のオーナーが新規のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリの {% data variables.product.prodname_dependabot_alerts %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `enable` | Organization のオーナーが新規のすべての{% if currentVersion == "free-pro-team@latest" %}プライベート{% endif %}リポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効にするとトリガーされます。 | + +#### `dependabot_security_updates` カテゴリアクション + +| アクション | 説明 | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Organization のオーナーが既存のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `enable` | Organization のオーナーが既存のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効にするとトリガーされます。 | + +#### `dependabot_security_updates_new_repos` カテゴリアクション + +| アクション | 説明 | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Organization のオーナーが新規のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `enable` | Organization のオーナーが新規のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効にするとトリガーされます。 | + +#### `dependency_graph` カテゴリアクション + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Organization のオーナーが既存のすべてのリポジトリに対して依存関係グラフを無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `enable` | Organization のオーナーが既存のすべてのリポジトリに対して依存関係グラフを有効にするとトリガーされます。 | + +#### `dependency_graph_new_repos` カテゴリアクション + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Organization のオーナーが新規のすべてのリポジトリに対して依存関係グラフを無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `enable` | Organization のオーナーが新規のすべてのリポジトリに対して依存関係グラフを有効にするとトリガーされます。 | + +{% endif %} + +#### `discussion_post` カテゴリアクション + +| アクション | 説明 | +| --------- | ------------------------------------------------------------------------------------------------ | +| `update` | [Team ディスカッションの投稿が編集される](/articles/managing-disruptive-comments/#editing-a-comment)ときにトリガーされます。 | +| `destroy` | [Team ディスカッションの投稿が削除される](/articles/managing-disruptive-comments/#deleting-a-comment)ときにトリガーされます。 | + +#### `discussion_post_reply` カテゴリアクション + +| アクション | 説明 | +| --------- | ---------------------------------------------------------------------------------------------------- | +| `update` | [Team ディスカッションの投稿への返答が編集される](/articles/managing-disruptive-comments/#editing-a-comment)ときにトリガーされます。 | +| `destroy` | [Team ディスカッションの投稿への返答が削除される](/articles/managing-disruptive-comments/#deleting-a-comment)ときにトリガーされます。 | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### `enterprise` カテゴリアクション + +{% data reusables.actions.actions-audit-events-for-enterprise %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `environment` カテゴリアクション + +| アクション | 説明 | +| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `git` カテゴリアクション + +{% note %} + +**注釈:** Audit log の Git イベントにアクセスするには、Audit log REST API を使用する必要があります。 The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| アクション | 説明 | +| ------ | --------------------------- | +| `クローン` | リポジトリがクローンされるとトリガーされます。 | +| `フェッチ` | リポジトリから変更がフェッチされるとトリガーされます。 | +| `プッシュ` | リポジトリに変更がプッシュされるとトリガーされます。 | + +{% endif %} + +#### `hook` カテゴリアクション + +| アクション | 説明 | +| ---------------- | ------------------------------------------------------------------------------- | +| `create` | Organization が所有するリポジトリに[新たなフックが追加された](/articles/creating-webhooks)ときにトリガーされます。 | +| `config_changed` | 既存のフックに変更された設定がある場合にトリガーされます。 | +| `destroy` | 既存のフックがリポジトリから削除されたときにトリガーされます。 | +| `events_changed` | フックでのイベントが変更された場合にトリガーされます。 | + +#### `integration_installation_request` カテゴリアクション + +| アクション | 説明 | +| -------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Organization のメンバーが、Organization 内で使用するために、Organization のオーナーにインテグレーションをインストールすることを要求するときにトリガーされます。 | +| `close` | Organization 内で使用するためにインテグレーションをインストールする要求が、Organization のオーナーにより承認または拒否されるか、あるいは要求を公開した Organization のメンバーによりキャンセルされるときにトリガーされます。 | + +#### `issue` カテゴリアクション + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------- | +| `destroy` | リポジトリで管理者権限を所有する Organization のオーナーまたは誰かが、Organization が所有するリポジトリから問題を削除するときにトリガーされます。 | + +{% if currentVersion == "free-pro-team@latest" %} + +#### `marketplace_agreement_signature` カテゴリアクション + +| アクション | 説明 | +| -------- | --------------------------------------------------------------------------------------- | +| `create` | {% data variables.product.prodname_marketplace %} Developer Agreement に署名するときにトリガーされます。 | + +#### `marketplace_listing` カテゴリアクション + +| アクション | 説明 | +| --------- | ----------------------------------------------------------------------------------- | +| `承認` | 一覧表を {% data variables.product.prodname_marketplace %}に掲載することが承認されるときにトリガーされます。 | +| `create` | {% data variables.product.prodname_marketplace %} で自分のアプリケーションの一覧表を作成するときにトリガーされます。 | +| `delist` | 一覧表が {% data variables.product.prodname_marketplace %} から削除されるときにトリガーされます。 | +| `redraft` | 一覧表がドラフト状態に戻されるときにトリガーされます。 | +| `reject` | 一覧表が {% data variables.product.prodname_marketplace %} に掲載することを認められないときにトリガーされます。 | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +#### `members_can_create_pages` カテゴリアクション + +For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." + +| アクション | 説明 | +|:--------- |:-------------------------------------------------------------------------------------------------------------- | +| `enable` | Organizationのオーナーが Organization のリポジトリについて {% data variables.product.prodname_pages %} サイトの公開を有効化するときトリガーされます。 | +| `disable` | Organizationのオーナーが Organization のリポジトリについて {% data variables.product.prodname_pages %} サイトの公開を無効化するときトリガーされます。 | + +{% endif %} + +#### `org` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_policy_selected_member_disabled` | Enterprise のオーナーが、Organization が所有するリポジトリで {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できないようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Enterprise のオーナーが、Organization が所有するリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できるようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `audit_log_export` | Organization の管理者が [Organization の Audit log のエクスポートを作成する](#exporting-the-audit-log)ときにトリガーされます。 エクスポートにクエリが含まれていた場合、ログには使用されたクエリとそのクエリに一致する Audit log エントリの数が一覧表示されます。 | +| `block_user` | Organization のオーナーが[Organization のリポジトリにユーザーがアクセスするのをブロックする](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)ときにトリガーされます。 | +| `cancel_invitation` | Organization の招待が取り消されている場合にトリガーされます。 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | Organization に対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。{% endif %} |{% if currentVersion == "free-pro-team@latest"%} +| `disable_oauth_app_restrictions` | オーナーが Organization に対して[{% data variables.product.prodname_oauth_app %} のアクセス制限を無効にする](/articles/disabling-oauth-app-access-restrictions-for-your-organization)ときにトリガーされます。 | +| `disable_saml` | Organization の管理者が Organization に対して SML シングルサインオンを無効にするときにトリガーされます。{% endif %} +| `disable_member_team_creation_permission` | Organization のオーナーがオーナーに Team 作成を制限するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 |{% if currentVersion != "github-ae@latest" %} +| `disable_two_factor_requirement` | Organization のすべてのメンバー{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャー、{% endif %}および外部のコラボレータに対してオーナーが 2 要素認証を無効化するときにトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable_oauth_app_restrictions` | オーナーが Organization に対して[{% data variables.product.prodname_oauth_app %} のアクセス制限を有効にする](/articles/enabling-oauth-app-access-restrictions-for-your-organization)ときにトリガーされます。 | +| `enable_saml` | Organization の管理者が Organization に対して [SAML シングルサインオン を有効にする](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)ときにトリガーされます。{% endif %} +| `enable_member_team_creation_permission` | メンバーが Team を作成するのを Organizationのオーナーが許可するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 |{% if currentVersion != "github-ae@latest" %} +| `enable_two_factor_requirement` | Organization のすべてのメンバー{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャー、{% endif %}および外部のコラボレータに対してオーナーが 2 要素認証を有効化するときにトリガーされます。{% endif %} +| `invite_member` | [新しいユーザーがOrganization に参加するよう招待](/articles/adding-organization-members-to-a-team)されたにトリガーされます。{% if currentVersion == "free-pro-team@latest" %} +| `oauth_app_access_approved` | オーナーが [{% data variables.product.prodname_oauth_app %} へのアクセスを許可する](/articles/approving-oauth-apps-for-your-organization/)ときにトリガーされます。 | +| `oauth_app_access_denied` | オーナーが Organization への[以前に承認した {% data variables.product.prodname_oauth_app %} のアクセス権を無効にする](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)ときにトリガーされます。 | +| `oauth_app_access_requested` | オーナーが Organization への {% data variables.product.prodname_oauth_app %} アクセスを許可することを Organization のメンバーが要求するときにトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。 | +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `remove_billing_manager` | [オーナーが Organization から支払いマネージャーを削除する](/articles/removing-a-billing-manager-from-your-organization/)とき、または [Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、支払いマネージャーが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます。 +{% endif %} +| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Organization から [Organization のメンバーが自身を削除](/articles/removing-yourself-from-an-organization/)するときにもトリガーされます。 | +| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_self_hosted_runner` | セルフホストランナーが削除されたときにトリガーされます。 For more information, see "[Removing a runner from an organization](/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` | Organization のオーナーがメンバーのリンクされたアイデンティティを取り消すときにトリガーされます。 詳細は、「[組織へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 | +| `revoke_sso_session` | Organization のオーナーがメンバーの SAML セッションを取り消すときにトリガーされます。 詳細は、「[組織へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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` | セルフホストランナーグループが作成されたときにトリガーされます。 For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." | +| `runner_group_created` | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。 | +| `runner_group_updated` | セルフホストランナーグループの設定が変更されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 | +| `runner_group_runners_added` | セルフホストランナーがグループに追加されたときにトリガーされます。 For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | +| `runner_group_runner_removed` | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | +| `runner_group_runners_updated` | ランナーグループのメンバーリストが更新されたときにトリガーされます。 For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `unblock_user` | Organizationのオーナーが[ Organization からユーザりブロックを解除](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)するときにトリガーされます。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% 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` | オーナーが Organization の新しいリポジトリのデフォルトブランチの名前を変更するときにトリガーされます。 詳しい情報については、「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照してください。{% endif %} +| `update_default_repository_permission` | オーナーが Organization のメンバーのデフォルトリポジトリの権限レベルを変更するときにトリガーされます。 | +| `update_member` | オーナーがユーザーのロールをオーナーからメンバーに、またはメンバーからオーナーに変更するときにトリガーされます。 | +| `update_member_repository_creation_permission` | オーナーが Organization のメンバーのリポジトリ作成権限を変更するときにトリガーされます。{% if currentVersion == "free-pro-team@latest" %} +| `update_saml_provider_settings` | Organization の SAML プロバイダ設定が更新されるときにトリガーされます。 | +| `update_terms_of_service` | Organization が標準利用規約と企業向け利用規約を切り替えるときにトリガーされます。 詳細は「[企業利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `org_credential_authorization` category actions + +| アクション | 説明 | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `grant` | [SAML シングルサインオンに使用するクレデンシャルをメンバーが認可する](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。 | +| `deauthorized` | [SAML シングルサインオンに使用するクレデンシャルの認可をメンバーが取り消す](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。 | +| `revoke` | オーナーが[認可されたクレデンシャルを取り消す](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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" %} +#### `organization_label` category actions + +| アクション | 説明 | +| --------- | -------------------------- | +| `create` | デフォルトラベルが作成されるときにトリガーされます。 | +| `update` | デフォルトラベルが編集されるときにトリガーされます。 | +| `destroy` | デフォルトラベルが削除されるときにトリガーされます。 | + +{% endif %} + +#### `oauth_application` category actions + +| アクション | 説明 | +| --------------- | ------------------------------------------------------------------------------------------ | +| `create` | 新たな {% data variables.product.prodname_oauth_app %} が作成されるときにトリガーされます。 | +| `destroy` | 既存の {% data variables.product.prodname_oauth_app %} が削除されるときにトリガーされます。 | +| `reset_secret` | {% data variables.product.prodname_oauth_app %} のクライアント シークレットがリセットされるときにトリガーされます。 | +| `revoke_tokens` | {% data variables.product.prodname_oauth_app %} のユーザートークンが取り消されるときにトリガーされます。 | +| `移譲` | 既存の {% data variables.product.prodname_oauth_app %} が新しい Organization に移譲されるときにトリガーされます。 | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +#### `packages` category actions + +| アクション | 説明 | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `package_version_published` | Triggered when a package version is published. | +| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `payment_method` カテゴリアクション + +| アクション | 説明 | +| -------- | -------------------------------------------------------------------- | +| `clear` | ファイル上の支払い方法が[削除される](/articles/removing-a-payment-method)ときにトリガーされます。 | +| `create` | 新しいクレジット カードや PayPal アカウントなど、新たな支払い方法が追加されるときにトリガーされます。 | +| `update` | 既存の支払い方法が更新されるときにトリガーされます。 | + +{% endif %} + +#### `profile_picture` カテゴリアクション +| アクション | 説明 | +| ------ | -------------------------------------------- | +| update | Organization のプロファイル写真を設定または更新するときにトリガーされます。 | + +#### `project` カテゴリアクション + +| アクション | 説明 | +| ------------------------ | -------------------------------------------------------------------------------------- | +| `create` | プロジェクト ボードが作成されるときにトリガーされます。 | +| `link` | リポジトリがプロジェクト ボードにリンクされるときにトリガーされます。 | +| `rename` | プロジェクトボードの名前が変更されるときにトリガーされます。 | +| `update` | プロジェクト ボードが更新されるときにトリガーされます。 | +| `delete` | プロジェクトボードが削除されるときにトリガーされます。 | +| `unlink` | リポジトリがプロジェクトボードからリンク解除されるときにトリガーされます。 | +| `update_org_permission` | Organization のすべてのメンバーに対して、基本レベルの権限が変更または削除されるときにトリガーされます。 | +| `update_team_permission` | Team のプロジェクト ボードの権限レベルが変更されるとき、または Team がプロジェクト ボードに追加または削除されるときにトリガーされます。 | +| `update_user_permission` | Organization のメンバーまたは外部コラボレーターがプロジェクト ボードに追加または削除されるとき、または彼らの権限レベルが変更されている場合にトリガーされます。 | + +#### `protected_branch` category actions + +| アクション | 説明 | +| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | ブランチでブランチの保護が有効になるときにトリガーされます。 | +| `destroy` | ブランチでブランチの保護が無効になるときにトリガーされます。 | +| `update_admin_enforced` | リポジトリの管理者に対してブランチの保護が実施されるときにトリガーされます。 | +| `update_require_code_owner_review` | 必須コードオーナーレビューの実施がブランチで更新されるときにトリガーされます。 | +| `dismiss_stale_reviews` | 古い Pull Request の却下の実施がブランチで更新されるときにトリガーされます。 | +| `update_signature_requirement_enforcement_level` | 必須コミット署名の実施がブランチで更新されるときにトリガーされます。 | +| `update_pull_request_reviews_enforcement_level` | 必須 Pull Request レビューの実施がブランチで更新されるときにトリガーされます。 | +| `update_required_status_checks_enforcement_level` | 必須ステータスチェックの実施がブランチで更新されるときにトリガーされます。 | +| `update_strict_required_status_checks_policy` | マージする前に最新にする必要があるブランチの要件が変更されるときにトリガーされます。 | +| `rejected_ref_update` | ブランチ更新の試行が拒否されるときにトリガーされます。 | +| `policy_override` | Triggered when a branch protection requirement is overridden by a repository administrator.{% 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` | 保護されたブランチについて、フォースプッシュが有効化または無効化されるときにトリガーされます。 | +| `update_allow_deletions_enforcement_level` | 保護されたブランチについて、ブランチ削除が有効化または無効化されるときにトリガーされます。 | +| `update_linear_history_requirement_enforcement_level` | 保護されたブランチについて、必須の直線状のコミット履歴が有効化または無効化されるときにトリガーされます。 | +{% endif %} + +#### `repo` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | +| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +| `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" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 | +| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for 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).".{% 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.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` | リポジトリに対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} +| `destroy` | [リポジトリが削除される](/articles/deleting-a-repository)ときにトリガーされます。{% if currentVersion == "free-pro-team@latest" %} +| `disable` | リポジトリが無効になるときにトリガーされます ([残高不足](/articles/unlocking-a-locked-account)などの場合)。{% endif %} +| `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 {% data variables.product.prodname_actions %} secret is removed.{% 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` | 新しいセルフホストランナーが登録されたときにトリガーされます。 For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `remove_self_hosted_runner` | セルフホストランナーが削除されたときにトリガーされます。 For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." |{% endif %} +| `remove_topic` | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。 | +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `移譲` | [リポジトリが移譲される](/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 {% data variables.product.prodname_actions %} secret is updated.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `repository_advisory` category actions + +| アクション | 説明 | +| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `close` | Triggered when someone closes a security advisory. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | +| `オープン` | Triggered when someone opens a draft security advisory. | +| `publish` | Triggered when someone publishes a security advisory. | +| `さいお` | Triggered when someone reopens as draft security advisory. | +| `update` | Triggered when someone edits a draft or published security advisory. | + +#### `repository_content_analysis` category actions + +| アクション | 説明 | +| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enable` | Organization のオーナーまたはリポジトリへの管理者アクセス権を所有する人が[プライベート リポジトリに対してデータ使用設定を有効にする](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)ときにトリガーされます。 | +| `disable` | Organization のオーナーまたはリポジトリへの管理者アクセス権を所有する人が[プライベート リポジトリに対してデータ使用設定を無効にする](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)ときにトリガーされます。 | + +{% endif %}{% if currentVersion != "github-ae@latest" %} + +#### `repository_dependency_graph` category actions + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | +| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### `repository_secret_scanning` category actions + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | +| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### `repository_vulnerability_alert` category actions + +| アクション | 説明 | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when {% data variables.product.product_name %} creates a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 | +| `却下` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. | +| `解決` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### `repository_vulnerability_alerts` category actions + +| アクション | 説明 | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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. 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 | +| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. | +| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### `secret_scanning` category actions + +| アクション | 説明 | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Triggered when an organization owner disables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | +| `enable` | Triggered when an organization owner enables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. | + +#### `secret_scanning_new_repos` category actions + +| アクション | 説明 | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Triggered when an organization owner disables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | +| `enable` | Triggered when an organization owner enables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `sponsors` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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` | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)」を参照) | +| `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 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 "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| sponsored_developer_update_newsletter_send | スポンサーにメールで最新情報を送信したときにトリガーされます (「[スポンサーに連絡する](/articles/contacting-your-sponsors)」を参照) | +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `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 %} + +#### `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` | 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](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/managing-peoples-access-to-your-organization-with-roles/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 + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `disable` | Organization のオーナーが Organization の Team ディスカッションを無効にするときにトリガーされます。 詳しい情報については [Organization の Team ディスカッションの無効化](/articles/disabling-team-discussions-for-your-organization)を参照してください。 | +| `enable` | Organization のオーナーが Organization の Team ディスカッションを有効にするときにトリガーされます。 | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +#### `workflows` category actions + +{% data reusables.actions.actions-audit-events-workflow %} + +{% endif %} + +### 参考リンク + +- "[Organization を安全に保つ](/articles/keeping-your-organization-secure)" diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000..f178bb6fd8 --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,25 @@ +--- +title: Organization のインストール済みインテグレーションをレビューする +intro: Organization のインストール済みインテグレーションの権限レベルをレビューして、各インテグレーションの Organization リポジトリへのアクセス権を設定できます。 +redirect_from: + - /articles/reviewing-your-organization-s-installed-integrations + - /articles/reviewing-your-organizations-installed-integrations + - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. 左サイドバーで [**Installed {% data variables.product.prodname_github_app %}s**] をクリックします。 ![Organization の Settings サイドバーでの [Installed {% data variables.product.prodname_github_app %}s] タブ](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. レビューする {% data variables.product.prodname_github_app %}の横にある [**Configure**] をクリックします。 ![[Configure] ボタン](/assets/images/help/organizations/configure-installed-integration-button.png) +6. {% data variables.product.prodname_github_app %} の権限とリポジトリのアクセス権をレビューします。 ![{% data variables.product.prodname_github_app %} にすべてのリポジトリまたは特定のリポジトリへのアクセス権を付与するためのオプション](/assets/images/help/organizations/toggle-integration-repo-access.png) + - {% data variables.product.prodname_github_app %} に Organization のすべてのリポジトリへのアクセス権を付与するには、[**All repositories**] をクリックします。 + - アプリケーションにアクセス権を付与する特定のリポジトリを選択するには、[**Only select repositories**] を選択し、続いてリポジトリ名を入力します。 +7. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000..d5392f734b --- /dev/null +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,30 @@ +--- +title: Organization 内のユーザが 2 要素認証を有効にしているかどうかを表示する +intro: 'どの Organization のオーナー、メンバー、および 外部コラボレーターが 2 要素認証を有効にしているかを確認できます。' +redirect_from: + - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled + - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% note %} + +**注釈:** {% if currentVersion == "free-pro-team@latest" %}オーナー、支払いマネージャーおよび{% else %}{% endif %}外部コラボレーターを含むすべてのメンバーに、2 要素認証を有効にするよう要求できます。 詳しい情報については [Organization で 2 要素認証を要求する](/articles/requiring-two-factor-authentication-in-your-organization)を参照してください。 + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Organization のオーナー含め、2 要素認証を有効または無効にした Organization メンバーを表示するには、[**2FA**] をクリックして、[**Enabled**] または [**Disabled**] を選択します。 ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png) +5. Organization の外部コラボレーターを表示するには、[People] タブの下の [**Outside collaborators**] をクリックします。 ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) +6. どの外部コラボレーターが 2 要素認証を有効または無効にしているかを確認するには、右側の [**2FA**] をクリックして、[**Enabled**] または [**Disabled**] を選択します。 ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) + +### 参考リンク + +- 「[Organization における人のロールを表示する](/articles/viewing-people-s-roles-in-an-organization)」 diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000..4c755e4855 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,40 @@ +--- +title: GitHub App マネージャーを Organization に追加する +intro: 'Organization のオーナーは、その Organization が所有している一部または全部の {% data variables.product.prodname_github_app %} を管理する機能をユーザに付与できます。' +redirect_from: + - /articles/adding-github-app-managers-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data variables.product.prodname_github_app %} マネージャー権限に関する詳しい情報については「[Organization の権限レベル](/articles/permission-levels-for-an-organization#github-app-managers)」を参照してください。 + +### Organization が所有するすべての {% 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. [Management] の下で、Organization の {% data variables.product.prodname_github_app %} マネージャーに指名したい人物のユーザ名を入力し、[**Grant**] をクリックします。 ![{% data variables.product.prodname_github_app %} マネージャーを追加](/assets/images/help/organizations/add-github-app-manager.png) + +### 個々の {% 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. [{% data variables.product.prodname_github_app %}s] の下で、{% 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) + +{% if currentVersion == "free-pro-team@latest" %} +### 参考リンク + +- 「[{% data variables.product.prodname_dotcom %} Marketplaceについて](/articles/about-github-marketplace/)」 +{% endif %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/index.md new file mode 100644 index 0000000000..8e2d9ee6c4 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -0,0 +1,18 @@ +--- +title: Organization のアプリケーションに対するアクセスを管理する +intro: 'Organization のオーナーは、Organization の個々のメンバーが Organization で {% data variables.product.prodname_github_app %} を管理することを許可できます。' +redirect_from: + - /articles/managing-access-to-your-organization-s-apps + - /articles/managing-access-to-your-organizations-apps + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /adding-github-app-managers-in-your-organization %} +{% link_in_list /removing-github-app-managers-from-your-organization %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000..de65d3de3d --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,40 @@ +--- +title: GitHub App マネージャーを Organization から削除する +intro: 'Organization のオーナーは、Organization のメンバーに付与されていた {% data variables.product.prodname_github_app %} マネージャー権限を削除することができます。' +redirect_from: + - /articles/removing-github-app-managers-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data variables.product.prodname_github_app %} マネージャー権限に関する詳しい情報については「[Organization の権限レベル](/articles/permission-levels-for-an-organization#github-app-managers)」を参照してください。 + +### Organization 全体で {% 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. [Management] の下で、{% data variables.product.prodname_github_app %}マネージャー権限を削除する個人のユーザ名を探し、 [**Revoke**] をクリックします。 ![{% data variables.product.prodname_github_app %} マネージャー権限の削除](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) + +### 個別の {% data variables.product.prodname_github_app %} で {% 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. [{% 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) + +{% if currentVersion == "free-pro-team@latest" %} +### 参考リンク + +- 「[{% data variables.product.prodname_dotcom %} Marketplaceについて](/articles/about-github-marketplace/)」 +{% endif %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000..fb13f18878 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Organization のプロジェクトボードに外部のコラボレータを追加する +intro: 'Organization のオーナーあるいはプロジェクトボードの管理者は、外部のコラボレータを追加し、追加したコラボレータのプロジェクトボードへの権限をカスタマイズできます。' +redirect_from: + - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +外部のコラボレータは Organization の明示的なメンバーではありませんが、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 %} +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/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md new file mode 100644 index 0000000000..5cac253af5 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -0,0 +1,22 @@ +--- +title: Organization のプロジェクトボードへのアクセスを管理する +intro: 'Organization のオーナーまたはプロジェクトボードの管理者は、Organization が所有するプロジェクトボードについて、Organization のメンバー、チーム、外部のコラボレーターごとに異なるレベルのアクセス権を付与できます。' +redirect_from: + - /articles/managing-access-to-your-organization-s-project-boards + - /articles/managing-access-to-your-organizations-project-boards + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000..f82f063489 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,39 @@ +--- +title: Organization メンバーのプロジェクトボードへのアクセスを管理する +intro: 'Organization のオーナーまたはプロジェクトボード管理者は、Organization のすべてのメンバーについて、プロジェクトボードのデフォルトの権限レベルを設定できます。' +redirect_from: + - /articles/managing-access-to-a-project-board-for-organization-members + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +デフォルトでは、Organization のメンバーはその Organization のプロジェクトボードに対する書き込みアクセスを持ちます。ただし、Organization のオーナーまたはプロジェクトボード管理者が、特定のプロジェクトボードに異なる権限を設定している場合は例外です。 + +### Organization のすべてのメンバーに対して標準の権限レベルを設定する + +{% tip %} + +**ヒント:** Organization メンバーの、プロジェクトボードに対する権限を高くすることができます。 詳しい情報については、「[Organization のプロジェクトボードの権限](/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. [Organization member permission] で、Organization のすべてのメンバーに対する標準の権限レベルを、[**Read**]、[**Write**]、[**Admin**]、[**None**] の中から選択します。 ![Organization のすべてのメンバーのプロジェクトボードに対する標準の権限](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. [**Save**] をクリックします。 + +### 参考リンク + +- 「[Organization のプロジェクトボードに対する個々のアクセスを管理する](/articles/managing-an-individual-s-access-to-an-organization-project-board)」 +- 「[Organization のプロジェクトボードに対するチームのアクセスを管理する](/articles/managing-team-access-to-an-organization-project-board)」 +- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..c4f0839ad9 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,62 @@ +--- +title: Organization のプロジェクトボードに対する個々のアクセスを管理する +intro: 'Organization のオーナーまたはプロジェクトボードの管理者は、Organization で所有しているプロジェクトボードに対する個々のメンバーのアクセスを管理できます。' +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-project-board + - /articles/managing-an-individuals-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% note %} + +**メモ:** {% data reusables.project-management.cascading-permissions %} 詳細は「[Orgazniation のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 + +{% endnote %} + +### 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 %} +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 %} + +### 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.collaborator-permissions %} + +### Organization メンバーのプロジェクトボードへのアクセスを削除する + +プロジェクトボードからコラボレーターを削除しても、コラボレーターは引き続き他のロールの権限でボードにアクセスできる場合があります。 プロジェクトボードへのアクセスを完全に削除するには、個人の各ロールごとにアクセスを削除する必要があります。 たとえば、ユーザは Organization のメンバーとして、またはチーム メンバーとしてプロジェクトボードにアクセスできます。 詳しい情報については、「[Organization のプロジェクトボードの権限](/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 %} + +### 参考リンク + +- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..89b4acd4b9 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,52 @@ +--- +title: Organization のプロジェクトボードに対するチームのアクセスを管理する +intro: 'Organization のオーナーまたはプロジェクトボードの管理者は、Organization が所有しているプロジェクトボードへのアクセスをチームに付与できます。' +redirect_from: + - /articles/managing-team-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% warning %} + +**警告:** +- チームがプロジェクトボードに直接アクセスできる場合は、チームの権限レベルを変更できます。 プロジェクトボードへのチームのアクセスが親チームから継承される場合は、プロジェクトボードへの親チームのアクセスを変更する必要があります。 +- 親チームのプロジェクトボードへのアクセスを追加または削除すると、その親の子チームそれぞれでも、同じプロジェクトボードへのアクセスが追加または削除されます。 詳しい情報については[Team について](/articles/about-teams)を参照してください。 + +{% endwarning %} + +### プロジェクトボードへのアクセスをチームに付与する + +あるプロジェクトボードに対する同じ権限レベルをチーム全体に付与することができます。 + +{% note %} + +**メモ:** {% data reusables.project-management.cascading-permissions %} たとえば、Organization のオーナーが、あるプロジェクトボードに対する読み取り権限をチームに付与しており、プロジェクトボードの管理者がチームのメンバーいずれかに、個別のコラボレーターとしてそのボードに対する管理者権限を付与している場合、そのユーザはプロジェクトボードに対する管理者権限を持つことになります。 詳細は「[Organization のプロジェクトボード権限](/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. 左サイトバーで [**Teams**] をクリックします。 +9. チームを追加する場合は、[**Add a team: Select team**] をクリックします。 次に、ドロップダウン メニューからチームを選択するか、追加したいチームを検索します。 ![Organization のチームのリストが表示される [Add a team] ドロップダウン メニュー](/assets/images/help/projects/add-a-team.png) +10. チーム名の隣にあるドロップダウン メニューを使って、目的の権限レベルを [**Read**]、[**Write**]、[**Admin**] から選択します。 ![[Read]、[Write]、[Admin] のオプションがあるチームの権限](/assets/images/help/projects/org-project-team-choose-permissions.png) + +### プロジェクトボードへのチームのアクセスを設定する + +チームのプロジェクトボードへのアクセスが親チームから継承されている場合は、その子チームへのアクセスを更新するために、親チームのプロジェクトボードへのアクセスを変更する必要があります。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. チームの会話の上にある {% octicon "project" aria-label="The Projects icon" %}[**Projects**] をクリックします。 ![チームの [Repositories] タブ](/assets/images/help/organizations/team-project-board-button.png) +5. 権限レベルを変更するには、更新するプロジェクトボードの右にあるドロップダウンを使用します。 プロジェクトボードを削除するには、[**{% octicon "trashcan" aria-label="The trashcan icon" %}**] をクリックします。 ![チームからプロジェクトボードを削除する [Trash] ボタン](/assets/images/help/organizations/trash-button.png) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000..e71c79c540 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -0,0 +1,44 @@ +--- +title: Organization のプロジェクトボード権限 +intro: 'Organization のオーナーと、プロジェクトボード管理者権限を持つユーザーは、Organization のプロジェクトボードに対する読み取り、書き込み、管理の各権限を誰が持つかをカスタマイズすることができます。' +redirect_from: + - /articles/project-board-permissions-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### 権限の概要 + +ユーザーと Team のプロジェクトボードに対する権限には、次の 3 つのレベルがあります: + +{% data reusables.project-management.project-board-permissions %} + +Organization のオーナーと、管理者権限を持つユーザーは、外部コラボレーターまたは Organization メンバーとして、または Team や Organization のメンバーシップを通じて、Organization のプロジェクトボードに対するユーザーのアクセス権を個々に付与することができます。 外部コラボレーターとは、Organization のメンバーではないが、Organization でコラボレーションの権限を付与されたユーザーのことです。 + +Organization のオーナーと、プロジェクトボードに対する管理者権限を持つユーザーは、次の操作を実行できます: +- すべての Organization メンバーに対して、デフォルトのプロジェクトボード権限を設定する。 +- Organization メンバー、Team、外部コラボレーターについてプロジェクトボードへのアクセスを管理する。 詳細は「[Organization のプロジェクトボードに対するチームのアクセスを管理する](/articles/managing-team-access-to-an-organization-project-board)」、「[Organization のプロジェクトボードに対する個々のアクセスを管理する](/articles/managing-an-individual-s-access-to-an-organization-project-board)」、「[Organization メンバーのプロジェクトボードへのアクセスを管理する](/articles/managing-access-to-a-project-board-for-organization-members)」を参照してください。 +- プロジェクトボードの可視性を管理する。 詳細は「[Organization メンバーのプロジェクトボードへのアクセスを管理する](/articles/managing-access-to-a-project-board-for-organization-members)」を参照してください。 + +### プロジェクトボードに対するカスケード権限 + +{% data reusables.project-management.cascading-permissions %} + +たとえば、Organization のオーナーが、あるプロジェクトボードに対する読み取り権限を Organization のすべてのメンバーに付与しており、プロジェクトボードの管理者が個別のコラボレーターとして、同じボードに対する書き込み権限を Organization のメンバーに付与している場合、そのユーザーはそのプロジェクトボードに対する書き込み権限を持つことになります。 + +### プロジェクトボードの可視性 + +{% data reusables.project-management.project-board-visibility %}プロジェクトボードの表示をプライベートから{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %}に変更したり、元に戻したりすることができます。 詳細は「[プロジェクトボードの可視性を変更する](/articles/changing-project-board-visibility)」を参照してください。 + +### 参考リンク + +- 「[プロジェクトボードの可視性を変更する](/articles/changing-project-board-visibility)」 +- 「[Organization のプロジェクトボードに対する個々のアクセスを管理する](/articles/managing-an-individual-s-access-to-an-organization-project-board)」 +- 「[Organization のプロジェクトボードに対するチームのアクセスを管理する](/articles/managing-team-access-to-an-organization-project-board)」 +- [Organization メンバーのプロジェクトボードへのアクセスを管理する](/articles/managing-access-to-a-project-board-for-organization-members) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000..973334ad74 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,23 @@ +--- +title: 外部コラボレーターを Organization プロジェクトボードから削除する +intro: 'Organization のオーナーあるいはプロジェクトボードの管理者は、外部コラボレーターのプロジェクトボードへのアクセスを削除できます。' +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000..eef89c78e7 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,42 @@ +--- +title: 外部のコラボレータを Organization のリポジトリに追加する +intro: '*外部のコラボレータ*は、Organization の明示的なメンバーではありませんが、Organization の 1 つ以上のリポジトリに読み取り、書き込み、あるいは管理権限を持っている人です。' +redirect_from: + - /articles/adding-outside-collaborators-to-repositories-in-your-organization + - github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} 外部コラボレーターをリポジトリに追加できます。ただし、Organization のオーナーがコラボレーターの招待を禁じていない場合に限ります。 詳しい情報については、「[外部のコラボレーターを追加するための権限を設定する](/articles/setting-permissions-for-adding-outside-collaborators)」を参照してください。 + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% if currentVersion != "github-ae@latest" %} +Organization が[メンバーおよび外部コラボレーターに 2 要素認証を使うことを求める](/articles/requiring-two-factor-authentication-in-your-organization)なら、メンバーおよび外部コラボレーターはあなたからの Organization のリポジトリでのコラボレーションの招待を受諾する前に、2 要素認証を有効化しなければなりません。 +{% 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. 検索フィールドで、招待する人の名前を入力し、一致するリストの名前をクリックします。 ![リポジトリに招待する人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field.png) +6. [Choose a role] で、人に付与する権限を選択し、[**Add NAME to REPOSITORY**] をクリックします。 ![人の権限を選択する](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +{% else %} +5. 左のサイドバーで、[**Collaborators & teams**] をクリックします。 ![コラボレーターと Team がハイライトされたリポジトリ設定サイドバー](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. "Collaborators" の下で、リポジトリへのアクセスを許可したい人の名前を入力し、[**Add collaborator**] をクリックします。 ![Octocat のユーザ名が検索フィールドに入力されているコラボレーターセクション](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. 新しいコラボレータの名前の隣で、*Write (書き込み)*、*Read (読み取り)*、*Admin (管理)* の中から適切な権限レベルを選択してください。 ![リポジトリの権限の選択](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +{% endif %} + +### 参考リンク + +- [Organizatin のメンバーを外部のコラボレータに変換する](/articles/converting-an-organization-member-to-an-outside-collaborator) +- [外部のコラボレータを Organization のリポジトリから削除する](/articles/removing-an-outside-collaborator-from-an-organization-repository) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000..80f61c7980 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,24 @@ +--- +title: Organization で外部のコラボレーターになる招待をキャンセルする +intro: 人に対して、Organization が所有しているリポジトリで外部のコラボレーターになる招待をすべてキャンセルすることができます。 +permissions: Organization のオーナーは、そのOrganization で外部のコラボレーターになる招待をキャンセルすることができます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization が所有しているリポジトリで外部のコラボレーターになる招待を保留にしている人すべてのリストを表示できます。 + +保留中のコラボレーターごとに、Organization のリポジトリに参加する招待をすべて同時にキャンセルできます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% 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) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000..64d81ad11e --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,44 @@ +--- +title: Organization メンバーを外部コラボレーターに変換する +intro: 'Organization の現在のメンバーが、コンサルタントや一時的な雇用者などで、特定のリポジトリへのアクセスのみが必要な場合は、そのメンバーを「外部コラボレーター」に変換できます。' +redirect_from: + - /articles/converting-an-organization-member-to-an-outside-collaborator + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %}Organization メンバーを外部コラボレーターに変換できます。 + +{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} + +Organization のメンバーが外部コラボレーターに変換された後は、現在の Team メンバーシップによって許可されるリポジトリにしかアクセスできません。 Organization の明示的なメンバーではなくなり、以下のことができなくなります: + +- Team の作成 +- Organization の全メンバーおよび Team の表示 +- 参照可能なチームへの @メンション +- チームメンテナになる + +詳しい情報については、「[Organization の権限レベル](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)」を参照してください。 + +アクセスが期待通りであることを確実にするために、Organization メンバーの、リポジトリへのアクセスを確認することをおすすめします。 詳細は、「[Organization のリポジトリへの個人のアクセスを管理する](/articles/managing-an-individual-s-access-to-an-organization-repository)」を参照してください。 + +Organization のメンバーを外部コラボレーターに変換する際、Organization メンバーとしての権限は 3 か月保存されるので、この期間内に、そのユーザを Organization に{% if currentVersion == "free-pro-team@latest" %}再参加するよう招待{% else %}再追加{% endif %}すれば、メンバーとしての権限を回復できます。 詳しい情報については、「[Organization の以前のメンバーを回復する](/articles/reinstating-a-former-member-of-your-organization)」を参照してください。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. 外部コラボレーターに変換したい人を選択します。 ![2 人のメンバーを選択した状態のメンバーリスト](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. メンバーのリストの上のドロップダウンメニューで、[**Convert to outside collaborator**] をクリックします。 ![メンバーを外部コラボレーターに変換するオプションのあるドロップダウンメニュー](/assets/images/help/teams/user-bulk-management-options.png) +6. メンバーの外部コラボレーターへの変換に関する情報を読み、[**Convert to outside collaborator**] をクリックします。 ![外部コラボレーターの権限に関する情報および [Convert to outside collaborator] ボタン](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) + +### 参考リンク + +- [外部コラボレーターを Organization のリポジトリに追加する](/articles/adding-outside-collaborators-to-repositories-in-your-organization) +- [外部のコラボレータを Organization のリポジトリから削除する](/articles/removing-an-outside-collaborator-from-an-organization-repository) +- [外部コラボレーターを Organization のメンバーに変換する](/articles/converting-an-outside-collaborator-to-an-organization-member) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000..0dcaa814c3 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,41 @@ +--- +title: 外部コラボレーターを Organization メンバーに変換する +intro: 'Organization のリポジトリ上の外部コラボレーターに、Organization 内において、より幅広い権限を与えたい場合、Organization のメンバーとして{% if currentVersion == "free-pro-team@latest" %}ユーザーを招待{% else %}ユーザーを追加{% endif %}することができます。' +redirect_from: + - /articles/converting-an-outside-collaborator-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization のオーナーは、Organization に{% if currentVersion == "free-pro-team@latest" %ユーザーを招待{% else %}ユーザを追加{% endif %}できます。' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +Organization がユーザ単位の有料プランである場合、新しいメンバーを招待して参加させる、または Organization の以前のメンバーを復帰させる前に、そのためのライセンスが用意されている必要があります。 詳細は「[ユーザごとの価格付けについて](/articles/about-per-user-pricing)」を参照してください。 {% data reusables.organizations.org-invite-expiration %}{% endif %} + +{% if currentVersion != "github-ae@latest" %} +Organization が[メンバーに 2 要素認証を使うことを要求](/articles/requiring-two-factor-authentication-in-your-organization)している場合、 {% if currentVersion == "free-pro-team@latest" %}招待されるユーザは招待を受諾する前に手元で [2 要素認証を有効化](/articles/securing-your-account-with-two-factor-authentication-2fa)しておく必要があります。{% else %}ユーザを Organization に追加する前にそのユーザは手元で [2 要素認証を有効化](/articles/securing-your-account-with-two-factor-authentication-2fa)しておく必要があります。{% 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. 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**.![外部のコラボレーターを Organization に招待](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) +{% else %} +5. メンバーにしたい外部のコラボレーターの名前の右側で、[**Invite to organization**] をクリックします。![外部のコラボレーターを 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 %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### 参考リンク + +- [Organizatin のメンバーを外部のコラボレータに変換する](/articles/converting-an-organization-member-to-an-outside-collaborator) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..29b457743b --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md @@ -0,0 +1,28 @@ +--- +title: Organization のリポジトリに対するアクセスを管理する +intro: Organization のオーナーは、Organization のリポジトリに対する個人およびチームのアクセスを管理できます。 チームメンテナは、チームのリポジトリアクセスを管理することも可能です。 +redirect_from: + - /articles/permission-levels-for-an-organization-repository/ + - /articles/managing-access-to-your-organization-s-repositories + - /articles/managing-access-to-your-organizations-repositories + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000..23ee3e8ee3 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,39 @@ +--- +title: Organization のリポジトリへの個人のアクセスを管理する +intro: Organization が所有するリポジトリへの個人のアクセスを管理できます。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +管理権限を持つ人は、Organization のメンバーや外部のコラボレータの、Organization のリポジトリに対するアクセスを管理できます。 + +### リポジトリへのアクセスを削除する + +Organization のリポジトリからコラボレーターを削除すると、そのコラボレータはリポジトリに対する読み取りおよび書き込みアクセスを失います。 リポジトリがプライベートで、コラボレータがリポジトリをフォークしている場合、そのそのフォークも削除されますが、リポジトリのローカルクローンは保持したままになります。 + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +### Organization のリポジトリへの個人のアクセスを管理する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. アクセスのタイプが異なるユーザを管理するには、[**Members**] または [**Outside collaborators**] をクリックします。 ![メンバーまたは外部コラボレーターを Organization に招待するボタン](/assets/images/help/organizations/select-outside-collaborators.png) +5. 管理する個人の名前の右側にある {% octicon "gear" aria-label="The Settings gear" %}ドロップダウン メニューで、[**Manage**] をクリックします。 ![[Manage] アクセスリンク](/assets/images/help/organizations/member-manage-access.png) +6. [Manage access] ページで、リポジトリの隣にある [**Manage access**] をクリックします。 ![リポジトリの [Manage access] ボタン](/assets/images/help/organizations/repository-manage-access.png) +7. この個人がコラボレーターなのか、チーム メンバーとしてリポジトリにアクセスできるのかなど、特定のリポジトリに対するアクセスを確認します。 ![ユーザのリポジトリへのアクセスのマトリクス](/assets/images/help/organizations/repository-access-matrix-for-user.png) + +### 参考リンク + +{% if currentVersion == "free-pro-team@latest" %}- [リポジトリ内での操作を制限する](/articles/limiting-interactions-with-your-repository){% endif %} +- [Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000..d50a6a5bfc --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +title: Organization リポジトリへの Team のアクセスを管理する +intro: 'リポジトリへのチームアクセスを付与、リポジトリへのチームアクセスを削除、またはリポジトリへのチームの権限レベルを変更することができます。' +redirect_from: + - /articles/managing-team-access-to-an-organization-repository-early-access-program/ + - /articles/managing-team-access-to-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +リポジトリに対して管理者権限がある人は、リポジトリへのチームアクセスを管理できます。 チームメンテナは、リポジトリへのチームアクセスを削除できます。 + +{% warning %} + +**警告:** +- チームがリポジトリに直接アクセスできる場合は、チームの権限レベルを変更できます。 リポジトリへのチームのアクセスが親チームから継承される場合は、リポジトリへの親チームのアクセスを変更する必要があります。 +- 親チームのリポジトリへのアクセスを追加または削除すると、その親の子チームそれぞれでも、同じリポジトリへのアクセスが追加または削除されます。 詳しい情報については[Team について](/articles/about-teams)を参照してください。 + +{% endwarning %} + +### リポジトリへのアクセスをチームに付与する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. リポジトリ リストの上にある [**Add repository**] をクリックします。 ![[Add repository] ボタン](/assets/images/help/organizations/add-repositories-button.png) +6. リポジトリの名前を入力して、[**Add repository to team**] をクリックします。 ![リポジトリ検索フィールド](/assets/images/help/organizations/team-repositories-add.png) +7. オプションで、リポジトリ名の右にあるドロップダウンメニューを使って、チームの権限レベルを変更することもできます ![リポジトリのアクセス レベルのドロップダウン](/assets/images/help/organizations/team-repositories-change-permission-level.png) + +### リポジトリへのチームのアクセスを削除する + +チームがリポジトリに直接アクセスできる場合は、リポジトリへのチームのアクセスを削除できます。 リポジトリへのチームのアクセスが親チームから継承される場合、子チームからリポジトリを削除するには親チームからリポジトリを削除する必要があります。 + +{% 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. チームから削除するリポジトリ (複数選択も可) を選択します。 ![いくつかのリポジトリがチェックボックスで選択されたチーム リポジトリのリスト](/assets/images/help/teams/select-team-repositories-bulk.png) +6. リポジトリ リストの上にあるドロップダウン メニューで、[**Remove from team**] をクリックします。 ![チームからリポジトリを削除するオプションのあるドロップダウン メニュー](/assets/images/help/teams/remove-team-repo-dropdown.png) +7. チームから削除されるリポジトリをレビューし、[**Remove repositories**] をクリックします。 ![チームがアクセスできなくなったリポジトリのリストがあるモーダル ボックス](/assets/images/help/teams/confirm-remove-team-repos.png) + +### 参考リンク + +- [Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000..52d2f44382 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,76 @@ +--- +title: 以前の外部のコラボレータの Organization へのアクセスを復帰させる +intro: 'Organization のリポジトリ、フォーク、設定に対する元外部のコラボレータのアクセス許可を元に戻すことができます。' +redirect_from: + - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization + - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization のプライベートリポジトリへの外部のコラボレータのアクセスが削除されると、ユーザのアクセス権限と設定は 3 か月間保存されます。 そのタイムフレーム内にユーザを Organization へ再度{% if currentVersion == "free-pro-team@latest" %}招待{% else %}追加{% endif %}した場合、そのユーザの権限をリストアできます。 + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +以前の外部コラボレーターを復帰させると、次のことがリストアできます: + - ユーザの Organization リポジトリへの以前のアクセス + - Organization が所有しているリポジトリのあらゆるプライベートフォーク + - Organization のチームでのメンバーシップ + - Organization のリポジトリへの以前のアクセスと権限 + - Organization リポジトリでの Star + - Organization での Issue 割り当て + - リポジトリプラン (リポジトリのアクティビティを Watch するか Watch しないか無視するかについての通知設定) + +{% tip %} + +**ヒント**: + - 外部コラボレーターの Organization へのアクセスを復帰させることができるのは、Organization のオーナーだけです。 詳細は「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」を参照してください。 + - {% data variables.product.product_location %} のメンバー復帰フローでは、外部コラボレーターの復帰を説明するために「メンバー」という用語を使用することがありますが、この個人を復帰させて以前の権限を保持しても、付与されるのはその[外部コラボレーターの以前の権限](/articles/permission-levels-for-an-organization/#outside-collaborators)のみです。{% if currentVersion == "free-pro-team@latest" %} + - Organization がユーザ単位の有料プランである場合、新しいメンバーを招待して参加させる、または Organization の以前のメンバーを復帰させる前に、そのためのライセンスが用意されている必要があります。 詳しい情報については、「[ユーザごとの価格付けについて](/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. [**Invite and reinstate**] をクリックして外部コラボレーターの Organization での以前の権限をリストアすることを選択するか、[**Invite and start fresh**] をクリックして以前の権限をクリアして新たにアクセス権を設定することを選択します。 + + {% warning %} + + **警告:** 外部コラボレーターを Organization のメンバーにアップグレードする場合は、[**Invite and start fresh**] を選択して、その個人の新しいロールを選択します。 ただし、[start fresh] を選択する場合、その個人のプライベートフォークは Organization のリポジトリから失われますので、注意が必要です。 以前の外部コラボレーターを Organization のメンバーにし、*かつ*そのコラボレーターのプライベートフォークを保持するには、代わりに [**Invite and reinstate**] を選択します。 その個人が招待を承認したら、[Organization にメンバーとして参加するよう招待する](/articles/converting-an-outside-collaborator-to-an-organization-member)ことにより、その個人を Organization メンバーに変換できます。 + + {% endwarning %} + + ![設定をリストアするか否かの選択](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. [**Add and reinstate**] をクリックして外部のコラボレータの Organization での以前の権限をリストアすることを選択するか、[**Add and start fresh**] をクリックして以前の権限をクリアして新たにアクセス権を設定することを選択します。 + + {% warning %} + + **警告:** 外部コラボレーターを Organization メンバーにアップグレードする場合は、[**Add and start fresh**] を選択して、その個人に新しいロールを選択してください。 ただし、[start fresh] を選択する場合、その個人のプライベートフォークは Organization のリポジトリから失われますので、注意が必要です。 以前の外部コラボレーターを Organization のメンバーにして、*かつ*そのプライベートフォークを保持するには、代わりに [**Add and reinstate**] を選択します。 それから、[Organization にメンバーとして追加する](/articles/converting-an-outside-collaborator-to-an-organization-member)ことにより、その個人を Organization メンバーに変換できます。 + + {% endwarning %} + + ![設定をリストアするか否かの選択](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. 以前の外部コラボレーターの以前の権限をクリアした場合は、そのユーザのロールを選択し、オプションでいくつかのチームに追加してから、[**Send invitation**] をクリックします。 ![ロールとTeamオプションと招待の送信ボタン](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. 以前の外部コラボレーターの以前の権限をクリアした場合は、そのユーザのロールを選択し、オプションでいくつかのチームに追加してから、[**Add member**] をクリックします。 ![ロールと Team のオプションと [add member] ボタン](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +8. 招待された人物は、Organizationへの招待メールを受け取ります。 Organization で 外部コラボレーターになるには、招待を受諾する必要があります。 {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### 参考リンク + +- [Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000..7e2107757a --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,57 @@ +--- +title: 外部コラボレーターを Organization リポジトリから削除する +intro: オーナーあるいはリポジトリ管理者は、外部コラボレーターのリポジトリへのアクセスを削除できます。 +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**警告:** +- 外部コラボレーターをプライベートリポジトリから削除しても、有料ライセンスのカウントは自動ではダウングレードしません。 Organization からユーザを削除したあとに有料シートの数を減らすには、「[Organization の有料ライセンスをダウングレードする](/articles/downgrading-your-organization-s-paid-seats)」の手順に従ってください。 + +- リポジトリへのアクセスを失った個人に、機密情報や知的財産を確実に削除してもらうのは、あなたの責任です。 + +{% endwarning %} + +{% endif %} + +コラボレーターが削除される一方でプライベートリポジトリのフォークが削除されると、その個人はリポジトリのローカルクローンをそのまま保持します。 + +### 外部コラボレーターを Organization のすべてのリポジトリから削除する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Organization から削除する外部コラボレーターを 1 人以上選択します。 ![外部コラボレーターのリストで外部コラボレーターを 2 名選択](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) +6. 外部コラボレーターのリストの上のドロップダウンメニューで [**Remove from all repositories**] をクリックします。 ![外部コラボレーターを削除するオプションのあるドロップダウンメニュー ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) +7. Organization から削除される外部コラボレーターをレビューしてから、[**Remove outside collaborators**] をクリックします。 ![削除される外部コラボレーターのリストおよび [Remove outside collaborators] ボタン](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) + +### 外部コラボレーターを Organization の特定のリポジトリから削除する + +外部コラボレーターを Organization の特定のリポジトリからのみ削除する場合、特定のリポジトリごとにアクセスを削除していきます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. 削除する個人のユーザ名の右側にある {% octicon "gear" aria-label="The Settings gear" %}ドロップダウンメニューで、[**Manage**] をクリックします。 ![[Manage access] ボタン](/assets/images/help/organizations/member-manage-access.png) +6. 外部コラボレーターを削除するリポジトリの右側で [**Manage access**] をクリックします。 ![外部コラボレーターがアクセスできるリポジトリの横にある [Manage access] ボタンを選択](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) +7. 外部コラボレーターのリポジトリへのアクセスを完全に削除するため、右上隅の [**Remove access to this repository**] をクリックします。 ![[Remove access to this repository] ボタン](/assets/images/help/organizations/remove-access-to-this-repository.png) +8. 確定するため、[**Remove access**] をクリックします。 ![リポジトリから削除する外部コラボレータの確定](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) + +### 参考リンク + +- [外部コラボレーターを Organization のリポジトリに追加する](/articles/adding-outside-collaborators-to-repositories-in-your-organization) +- [Organizatin のメンバーを外部のコラボレータに変換する](/articles/converting-an-organization-member-to-an-outside-collaborator) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000..982d5a6383 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -0,0 +1,181 @@ +--- +title: Organization のリポジトリ権限レベル +intro: 'Organization の各リポジトリに対するアクセスを、権限レベルを細かく設定することによりカスタマイズできます。これにより、ユーザが必要な機能やタスクにアクセスできるようになります。' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +管理権限を持つ人は、Organization が所有するリポジトリに対する人およびチームのアクセスを管理できます。 + +### Organization が所有するリポジトリの権限レベル + +Organization のメンバー、外部のコラボレータ、および Team に対して、Organization が所有するリポジトリに異なるレベルのアクセスを付与できます。 権限レベルごとに、リポジトリのコンテンツと設定へのアクセスが段階的に増加します。 プロジェクトにおける各人または各 Team のロールに相応しいレベルを選択し、プロジェクトに対して必要以上のアクセスを与えないようにしましょう。 + +以下のリストでは、Organization のリポジトリに対する権限レベルを、低いものから高いものに並べています: +- **Read**: プロジェクトを表示またはプロジェクトについてディスカッションしたい、コードを書かないコントリビューターにおすすめします +- **Triage**: 書き込みアクセスなしに、Issue やプルリクエストを積極的に 管理したいコントリビューターにおすすめします +- **Write**: プロジェクトに積極的にプッシュしたいコントリビューターにおすすめします +- **Maintain**: センシティブ、または破壊的なアクションにアクセスせずにリポジトリを管理する必要がある、プロジェクト管理者におすすめします +- **Admin**: セキュリティの管理やリポジトリの削除など、センシティブおよび破壊的なアクションを含めて、プロジェクトへの完全なアクセスが必要な人におすすめします + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +ユーザおよび Team にリポジトリへのアクセスを付与することに関する詳細は、「[Organization のリポジトリに対するアクセスを管理する](/articles/managing-access-to-your-organizations-repositories)」を参照してください。 + +Organizationのオーナーは、その Organization のリポジトリにアクセスするとき、Organization の全メンバーに適用される基本レベルの権限を設定できます。 詳しい情報については、「[Organization の基本レベル権限の設定](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)」を参照してください。 + +また、Organization のオーナーは、Organization 全体にわたって、特定の設定およびアクセスをさらに制限することも選択できます。 特定の設定についてのオプションに関する詳細は、[Organization の設定を管理する](/articles/managing-organization-settings)」を参照してください。 + +Organization レベルの設定を管理することに加え、Organization のオーナは Organization が所有するすべてのリポジトリの管理者権限を持っています。 詳細は「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」を参照してください。 + +{% warning %} + +**警告:** 誰かがリポジトリにデプロイキーを追加すると、そのリポジトリに対しては、秘密鍵を持つユーザであれば (鍵の設定によっては) 誰でも読み取りや書き込みができます。そのユーザが後に Organization から削除されても同じです。 + +{% endwarning %} + +### 各権限レベルが可能なリポジトリへのアクセス +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**注釈:** セキュリティ機能を使用するために必要なリポジトリのアクセス許可は、以下の「[セキュリティ機能のアクセス許可要件](#permission-requirements-for-security-features)」にリストされています。 + +{% endnote %} + +{% 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" %} +| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| ラベルの適用/却下 | | **X** | **X** | **X** | **X** | +| ラベルの作成、編集、削除 | | | **X** | **X** | **X** | +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [プルリクエストの自動マージの有効化または無効化](/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** | +| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [会話のロック](/communities/moderating-comments-and-conversations/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" or currentVersion == "github-ae@latest" %} +| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **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" %} +| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** +{% endif %} +| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | +| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** | +| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | +| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/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" or currentVersion ver_gt "enterprise-server@3.0" %} +| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | | | **X** | +| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | **X** | **X** | **X** +{% endif %} +| Webhookおよびデプロイキーの管理 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [プライベートリポジトリ用のデータ利用設定を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **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" %} +| リポジトリの [{% 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** | +| [Issue をまとめてディスカッションに変換する](/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** | +| [Issue を個別にディスカッションに変換する](/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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +#### セキュリティ機能のアクセス許可要件 + +このセクションでは、{% data variables.product.prodname_advanced_security %} 機能などのセキュリティ機能に必要なリポジトリのアクセス許可レベルを確認できます。 + +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:| +| {% if currentVersion == "free-pro-team@latest" %} | | | | | | +| リポジトリでの[脆弱性のある依存関係に対する{% 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/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** | +| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| [プルリクエストの {% 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@3.0" or currentVersion == 'github-ae@next' %} +| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | +| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% if currentVersion == "enterprise-server@3.0" %} +| [リポジトリの {% 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-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +[1] リポジトリの作者とメンテナは、自分のコミットのアラート情報のみを表示できます。 +{% endif %} +{% endif %} + +### 参考リンク + +- "[Organization のリポジトリへのアクセスを管理する](/articles/managing-access-to-your-organization-s-repositories)" +- [外部コラボレーターを Organization のリポジトリに追加する](/articles/adding-outside-collaborators-to-repositories-in-your-organization) +- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000..3db089879e --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -0,0 +1,36 @@ +--- +title: Organization の基本レベルの権限の設定 +intro: Organization が所有しているリポジトリに対して、基本レベルの権限を設定できます。 +permissions: Organization のオーナーは、Organization に対して基本レベルの権限を設定できます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Organization の基本レベルの権限について + +Organization のリポジトリにアクセスするとき Organization の全メンバーに適用される基本レベルの権限を設定できます。 基本レベルの権限は、外部のコラボレーターには適用されません。 + +{% if currentVersion == "free-pro-team@latest" %}デフォルトでは、Organization のメンバーは Organization のリポジトリに対する**読み取り**権限を付与されます。{% endif %} + +Organization のリポジトリに対する管理者権限があるユーザが、リポジトリに対してそれより高いレベルの権限を付与すると、基本レベルの権限は、付与された高い権限によってオーバーライドされます。 + +### 基本レベルの権限の設定 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. [Base permissions] で、ドロップダウンを使用して新しい基本レベルの権限を選択します。 ![[base permissions] ドロップダウンから新しい権限レベルを選択する](/assets/images/help/organizations/base-permissions-drop-down.png) +6. 変更を確認します。 確定するために、[**Change default permission to PERMISSION**] をクリックします。 ![基本レベルの権限の変更を確認して確定する](/assets/images/help/organizations/base-permissions-confirm.png) + +### 参考リンク + +- [Organization のリポジトリの権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization) +- [外部コラボレーターを Organization のリポジトリに追加する](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000..f7c15e2942 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,41 @@ +--- +title: 自分のリポジトリにアクセスできる人を表示する +intro: 'Organization のオーナーは、Organization 内のリポジトリへの人のアクセスを表示できます。 {% data variables.product.prodname_ghe_cloud %} または {% data variables.product.prodname_ghe_server %} を使用して、Organization のオーナーは、リポジトリにアクセスできる人の CSV リストをエクスポートすることもできます。' +redirect_from: + - /articles/viewing-people-with-access-to-your-repository + - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +管理者はこの情報を使用して、社外の人の支援、コンプライアンスのためのデータ収集、およびその他の一般的なセキュリティチェックを行うことができます。 + +![リポジトリユーザの権限リスト](/assets/images/help/repository/repository-permissions-list.png) + +### 自分のリポジトリにアクセスできる人を表示する + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**注釈**: リポジトリにアクセスできる Team と人について、組み合わせた概要を確認することもできます。 詳細は、「[リポジトリへのアクセス権を持つ Team と人を管理する](/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 %} + +### リポジトリへのアクセス権を持つ人のリストをエクスポートする + +{% data variables.product.prodname_ghe_cloud %} または {% data variables.product.prodname_ghe_server %} の Organization のオーナーは、リポジトリにアクセスできる人の CSV リストをエクスポートできます。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} +4. [**Export CSV**] をクリックします。 ![リポジトリサイドバーの人タブ](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000..2a46459ccf --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -0,0 +1,47 @@ +--- +title: SSH 認証局について +intro: 'SSH認証局を利用すると、メンバーがGitでリソースにアクセスするときに使用するSSH証明書を、OrganizationまたはEnterpriseアカウントが発行できます。' +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/about-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +SSH証明書とは、1つのSSHキーでもうひとつのSSHキーに署名する仕組みです。 SSH認証局 (CA) を利用して、Organizationのメンバーに署名済みのSSH証明書を提供すると、EnterpriseアカウントまたはOrganizationにCAを追加できるため、Organizationのメンバーはそれぞれの証明書を使用してOrganizationのリソースにアクセスできるようになります。 詳細については、「[OrganizationのSSH認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照してください。 + +SSH CAをOrganizationまたはEnterpriseアカウントに追加すると、そのCAを利用して、OrganizationメンバーのクライアントSSH証明書に署名できるようになります。 Organizationのメンバーは、署名済みの証明書を使用して、GitでOrganizationのリポジトリにアクセスできます (ただし、自分のOrganizationのリポジトリに限る)。 メンバーがOrganizationのリソースにアクセスするときに、SSH証明書の使用を必須にすることができます。.{% if currentVersion == "free-pro-team@latest" %}詳細については、「[Enterprise アカウントでセキュリティ設定を強制する](/articles/enforcing-security-settings-in-your-enterprise-account#managing-your-enterprise-accounts-ssh-certificate-authorities)」を参照してください。{% endif %} + +たとえば、毎朝新しい証明書を開発者に発行する内部システムなども構築できます。 各開発者は、その日の証明書を使用して、{% data variables.product.product_name %}でOrganizationのリポジトリを扱うことができます。 1日の最後になると証明書は自動的に失効するので、証明書が侵害されることがあっても、リポジトリは保護されます。 + +各証明書を発行する際には、その証明書がどの{% data variables.product.product_name %}ユーザー用かを示すエクステンションを指定する必要があります。 たとえば、OpenSSH の`ssh-keygen` コマンドを以下のように使用することができます。_KEY-IDENTITY_ は特定のキー IDに、_USERNAME_ は {% data variables.product.product_name %} ユーザ名に置き換えます。 + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +SSH を使用して複数の {% data variables.product.company_short %} 製品にアクセスするユーザに証明書を発行するには、2 つのログイン機能拡張を含めて、各製品のユーザ名を指定できます。 たとえば、次のコマンドは、{% data variables.product.prodname_ghe_cloud %} のユーザアカウントに対して _USERNAME-1_ の証明書を発行し、_HOSTNAME_ の {% data variables.product.prodname_ghe_managed %} または {% data variables.product.prodname_ghe_server %} のユーザアカウントに対して _USERNAME-2_ の証明書を発行します。 + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +``` + +`source-address` エクステンションを使用して、Organization のリソースに Organization のメンバーがアクセスできる IP アドレスを制限できます。 エクステンションには、CIDR 表記を用いて特定の IP アドレスまたは一定範囲の IPアドレスを指定できます。 コンマで値を区切ることで、複数のアドレスや範囲を指定できます。 詳しい情報については、Wikipedia の「[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)」を参照してください。 + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +{% if currentVersion == "free-pro-team@latest" %} + +SAMLシングルサインオンが強制されている場合でも、Organizationのメンバーはそれぞれの署名済み証明書を認証に使用できます。 SSH証明書を必須にしている場合を除き、Organizationのメンバーは他の認証方法、たとえばユーザー名とパスワード、個人アクセストークン、独自のSSHキーなどを使用して、GitのOrganizationリソースにアクセスし続けることができます。 + +{% endif %} + +認証エラーを防ぐために、Organization のメンバーは Organization ID を含む特殊な URL を使用し、署名された証明書を使ってリポジトリを複製する必要があります。 リポジトリに対する読み取りアクセス権限がある人は誰でも、リポジトリページでこの URL を確認できます。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。 diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..794603524f --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -0,0 +1,19 @@ +--- +title: Organization のリポジトリに対する Git アクセスを管理する +intro: SSH 認証局 (CA) を Organization に追加し、SSH CA に署名された鍵を使って、メンバーが Git 経由で Organization のリポジトリにアクセスできるようにすることができます。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /about-ssh-certificate-authorities %} +{% link_in_list /managing-your-organizations-ssh-certificate-authorities %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000..304b042e70 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,38 @@ +--- +title: OrganizationのSSH認証局を管理する +intro: Organizationから、SSH認証局を追加または削除することができます。 +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-your-organizations-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organizationのオーナーは、OrganizationのSSH認証局 (CAN) を管理できます。 + +SSH CAをOrganizationに追加すると、メンバーはあなたが提供したSSH証明書を使用してOrganizationにアクセスできるようになります。 {% data reusables.organizations.can-require-ssh-cert %}詳細については、「[SSH認証局について](/articles/about-ssh-certificate-authorities)」を参照してください。 + +### 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 %} + +### 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/ja-JP/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md new file mode 100644 index 0000000000..129389cd4a --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -0,0 +1,29 @@ +--- +title: Organization への人の追加 +intro: '{% data variables.product.product_name %}のユーザ名あるいはメールアドレスを使えば、誰でも Organization のメンバーにすることができます。' +redirect_from: + - /articles/adding-people-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization +versions: + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization のオーナーは、Organization にユーザを追加できます。' +--- + +{% if currentVersion != "github-ae@latest" %} +Organization が[メンバーに 2 要素認証を使うことを要求](/articles/requiring-two-factor-authentication-in-your-organization)しているなら、ユーザを Organization に追加する前にそのユーザは [2 要素認証を有効化](/articles/securing-your-account-with-two-factor-authentication-2fa)していなければなりません。 +{% 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 %} + +### 参考リンク +- [Team へのOrganization メンバーの追加](/articles/adding-organization-members-to-a-team) diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000..aec611b706 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,21 @@ +--- +title: 私の Organization に所属する人のためにアカウントを作成できますか? +intro: '作成した Organization にユーザを追加することはできますが、個人のアカウントを代理で作成することはできません。' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization + - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization にアクセスするには個人アカウントでログインする必要があるため、各 Team メンバーは個人アカウントが必要です。 Organization に追加したい人のユーザ名があれば、その人を Team に追加できます。 + +### Organization へのユーザの追加 + +1. [個人アカウントを作成する](/articles/signing-up-for-a-new-github-account)よう各自に指示してください。 +2. Organization のメンバーシップを与えたい人に、ユーザー名を尋ねます。 +3. Organization に、作成された[新しい個人アカウントを招待](/articles/inviting-users-to-join-your-organization)してください。 各アカウントのアクセスを制限するには、[Organization ロール](/articles/permission-levels-for-an-organization)および[リポジトリの権限](/articles/repository-permission-levels-for-an-organization)を使用します。 diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000..496752743b --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Organization への招待のキャンセルまたは編集 +intro: Organization のオーナーは、Organization のメンバーへの招待を、ユーザが承認する前ならいつでもキャンセルまたは編集できます。 +redirect_from: + - /articles/canceling-or-editing-an-invitation-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. [People] タブで、[**Pending invitation**] をクリックします。 ![招待の保留リンク](/assets/images/help/organizations/pending-invitation-link.png) +5. 編集またはキャンセルしたい人の、ユーザ名またはメールアドレスの隣にある [**Edit invitation**] をクリックします。 ![招待の編集ボタン](/assets/images/help/organizations/edit-invitation-button.png) + + 探している人が見つからない場合、ウインドウの下部にある [**View all invitations**] をクリックしてください。 +6. ユーザの Organization への招待を編集するかキャンセルするかを決めます。 ![[Update invitation] ボタンと [Cancel invitation] ボタン](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) + - ユーザの招待を編集するには、別のロールまたは Team を選択して、[**Update invitation**] をクリックします。 + - ユーザの Organization への招待をキャンセルするには、[**Cancel invitation**] をクリックします。 + +### 参考リンク + +{% if currentVersion == "free-pro-team@latest" %} +- [Organization に参加するようユーザを招待する](/articles/inviting-users-to-join-your-organization)" +{% endif %} +- [Team へのOrganization メンバーの追加](/articles/adding-organization-members-to-a-team) diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md new file mode 100644 index 0000000000..4f7b72fe36 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md @@ -0,0 +1,23 @@ +--- +title: Organization でメンバーシップを管理する +intro: 'Organization を作成すると、Organization のメンバーとして{% if currentVersion == "free-pro-team@latest" %}ユーザを招待{% else %}ユーザを追加{% endif %}することができます。 メンバーの削除や、元のメンバーの復帰も可能です。' +redirect_from: + - /articles/removing-a-user-from-your-organization/ + - /articles/managing-membership-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000..45d0a9b925 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Organization に参加するようユーザを招待する +intro: 'Organization のメンバーとして追加したい人がいれば、その人の {% data variables.product.product_name %} ユーザ名またはメール アドレスを使用して招待することができます。' +permissions: Organization オーナーは Organization に参加するようユーザを招待できます。 +redirect_from: + - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ + - /articles/inviting-users-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**ヒント**: +- Organization がユーザ単位の有料プランである場合、新しいメンバーを招待して参加させる、または Organization の以前のメンバーを復帰させる前に、そのためのライセンスが用意されている必要があります。 詳細は「[ユーザごとの価格付けについて](/articles/about-per-user-pricing)」を参照してください。 {% data reusables.organizations.org-invite-expiration %} +- Organization がメンバーに 2 要素認証を使うことを要求している場合、招待するユーザは招待を受ける前に 2 要素認証を有効化する必要があります。 詳細については、「[Organization で 2 要素認証を要求する](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)」と「[2要素認証 (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 %} + +### 参考リンク +- [Team へのOrganization メンバーの追加](/articles/adding-organization-members-to-a-team) diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000..a9694e64db --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,63 @@ +--- +title: Oraganization の以前のメンバーを復帰させる +intro: 'Organizationのオーナーは {% if currentVersion == "free-pro-team@latest" %}Oraganization の以前のメンバーを招待して Oraganization に復帰させて{% else %}以前のメンバーを Oraganization に追加して{% endif%}、その個人の以前のロール、アクセス権、フォーク、設定をリストアするかどうかを選択することができます。' +redirect_from: + - /articles/reinstating-a-former-member-of-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: Organization のオーナーは、Organization の元メンバーを元に戻すことができます。 +topics: + - organizations + - teams +--- + +### メンバーの復帰について + +[ユーザを Organization から削除する](/articles/removing-a-member-from-your-organization)場合{% if currentVersion == "github-ae@latest" %}または{% else %}、{% endif %}[Organization のメンバーを外部のコラボレータに変換する](/articles/converting-an-organization-member-to-an-outside-collaborator){% if currentVersion != "github-ae@latest" %}場合、または[メンバーと外部のコラボレータに 2要素認証（2FA）を有効化するよう要求](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}したためにユーザが Organization から削除される場合、そのユーザのアクセス権限と設定は 3 か月間保存されます。 そのタイムフレーム内にユーザを Organization へ再度{% if currentVersion =="free-pro-team@latest" %}招待{% else %}追加{% endif %}した場合、そのユーザの権限をリストアできます。 + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +Oraganization の以前のメンバーを復帰させると、次のことがリストアできます: + - Organization でのユーザのロール + - Organization が所有しているリポジトリのあらゆるプライベートフォーク + - Organization のチームでのメンバーシップ + - Organization のリポジトリへの以前のアクセスと権限 + - Organization リポジトリでの Star + - Organization での Issue 割り当て + - リポジトリプラン (リポジトリのアクティビティを Watch するか Watch しないか無視するかについての通知設定) + +{% if enterpriseServerVersions contains currentVersion %} +Organization のメンバーが 2 要素認証を使用していなかったために Organization から削除された場合、Organization で 2 要素認証を使用するようメンバーに要求することに変わりないのであれば、以前のメンバーは 2 要素認証を有効化しないとメンバーとして復帰できません。 +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Organization にユーザ単位の有料プランがある場合、Organization の以前のメンバーを復帰させる前に、使用されていないライセンスを使用可能にしておく必要があります。 詳細は「[ユーザごとの価格付けについて](/articles/about-per-user-pricing)」を参照してください。 {% data reusables.organizations.org-invite-expiration %} +{% endif %} + +### Oraganization の以前のメンバーを復帰させる + +{% 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. その個人の Organization での以前の権限をリストアするか、以前の権限をクリアして新たにアクセス権を設定するか、選択してから [**Invite and reinstate**] または [**Invite and start fresh**] をクリックします。 ![情報をリストアするか否かを選択](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. その個人の Organization での以前の権限をリストアするか、以前の権限をクリアして新たにアクセス権を設定するか、選択してから [**Add and reinstate**] または [**Add and start fresh**] をクリックします。 ![権限をリストアするかを選択](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. Oraganization の以前のメンバーの以前の権限をクリアした場合は、そのユーザのロールを選択し、オプションでいくつかのチームに追加してから、[**Send invitation**] をクリックします。 ![ロールとTeamオプションと招待の送信ボタン](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. Oraganization の以前のメンバーの以前の権限をクリアした場合は、そのユーザのロールを選択し、オプションでいくつかのチームに追加してから、[**Add member**] をクリックします。 ![ロールと Team のオプションと [add member] ボタン](/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 %} + +### 参考リンク + +- [Organizatin のメンバーを外部のコラボレータに変換する](/articles/converting-an-organization-member-to-an-outside-collaborator) diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000..ea82429840 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -0,0 +1,60 @@ +--- +title: Organization からメンバーを削除する +intro: 'Organization のメンバーが、Organization が所有するリポジトリへのアクセスを必要としなくなった場合、そのメンバーを Organization から削除することができます。' +redirect_from: + - /articles/removing-a-member-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization からメンバーを削除できるのは、Organization のオーナーだけです。 + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**警告:** Organization からメンバーを削除する際は次の点にご注意ください: +- 有料ライセンスのカウントは自動的にはダウングレードされません。 Organization からユーザを削除したあとに有料シートの数を減らすには、「[Organization の有料ライセンスをダウングレードする](/articles/downgrading-your-organization-s-paid-seats)」の手順に従ってください。 +- 削除されたメンバーは Organization のプライベートリポジトリのプライベートフォークへのアクセスは失いますが、ローカルコピーを自分で持っておくことは可能です。 ただし、ローカルコピーを Organization のリポジトリと同期させることはできません。 そのプライベートフォークは、そのユーザが Organization から削除されてから 3 か月以内に [Organization メンバーとして復帰した](/articles/reinstating-a-former-member-of-your-organization)場合、リストアできます。 最終的に、リポジトリへのアクセスを失った個人に、機密情報や知的財産を確実に削除してもらうのは、あなたの責任です。 +- 削除されたメンバーによって送信され、まだ受け取られていない Organization への招待がある場合はキャンセルされ、アクセスできなくなりすま。 + +{% endwarning %} + +{% else %} + +{% warning %} + +**警告:** Organization からメンバーを削除する際は次の点にご注意ください: + - 削除されたメンバーは Organization のプライベートリポジトリのプライベートフォークへのアクセスは失いますが、ローカルコピーを自分で持っておくことは可能です。 ただし、ローカルコピーを Organization のリポジトリと同期させることはできません。 そのプライベートフォークは、そのユーザが Organization から削除されてから 3 か月以内に [Organization メンバーとして復帰した](/articles/reinstating-a-former-member-of-your-organization)場合、リストアできます。 最終的に、リポジトリへのアクセスを失った個人に、機密情報や知的財産を確実に削除してもらうのは、あなたの責任です。 + - 削除されたユーザーによって送信され、まだ受け取られていない Organization への招待がある場合はキャンセルされ、アクセスできなくなりすま。 + +{% endwarning %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +Organization から削除する個人の移行と、その個人による機密情報や知的財産の削除ができるようにするため、Organization から離脱する際のベストプラクティスのチェックリストを共有するよう推奨します。 例については、「[退職のためのベストプラクティス](/articles/best-practices-for-leaving-your-company/)」を参照してください。 + +{% endif %} + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} + +### ユーザのメンバーシップを削除する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Organization から削除するメンバーを選択します。 ![2 人のメンバーを選択した状態のメンバーリスト](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. メンバーのリストの上のドロップダウンメニューで、[**Remove from organization**] をクリックします。 ![メンバーを削除するオプションのあるドロップダウンメニュー](/assets/images/help/teams/user-bulk-management-options.png) +6. Organization から削除されるメンバーをレビューしてから、[**Remove members**] をクリックします。 ![削除されるメンバーのリストおよび [Remove members] ボタン](/assets/images/help/teams/confirm-remove-members-bulk.png) + +### 参考リンク + +- 「[チームから Organization メンバーを削除する](/articles/removing-organization-members-from-a-team)」 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000..980d39aa4f --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Organization 内の Issue の削除を許可する +intro: Organization のオーナーは、Organization が所有するリポジトリ内の Issue の削除を許可できます。 +redirect_from: + - /articles/allowing-people-to-delete-issues-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +デフォルトでは、Organization 内の Issue は削除できません。 Organization のオーナーは、まず Organization の全リポジトリでこの機能を有効化しなければなりません。 + +有効化されると、Organization のオーナー、そして Organization が所有するリポジトリに管理権限を持つ人は、Issue を削除できるようになります。 リポジトリの管理権限を持つ人には、管理権限を持つ Organization メンバーや外部コラボレーターが含まれます。 詳細は「[Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization/)」および「[Issue を削除する](/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. [Issue deletion] の下で、[**Allow members to delete issues for this organization**] (この Organization の Issue の削除をメンバーに許可する) を選択します。 ![Issue の削除を許可するチェックボックス](/assets/images/help/settings/issue-deletion.png) +6. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/ja-JP/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000..59da9dabd2 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,24 @@ +--- +title: Organization dependency insights の可視性を変更する +intro: Organization のメンバーが、Organization dependency insights を表示できるように設定できます。また、Organization のオーナーにのみ表示できるようにも設定できます。 +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/changing-the-visibility-of-your-organizations-dependency-insights + - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization のオーナーは、organization dependency insights の表示制限を設定できます。 デフォルトでは、Organization のメンバー全員が Organization dependency insight を表示できます。 + +Enterprise のオーナーは、Enterprise アカウントにあるすべての Organization dependency insights について、表示制限を設定できます。 詳しい情報については、「[Enterprise アカウントに dependency insights に関するポリシーを施行する](/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. [Member organization permissions] で、[**Allow members to view dependency insights**] を選択または選択解除します。 ![insights の表示をメンバーに許可するチェックボックス](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000..9aaffbeef3 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,22 @@ +--- +title: Organization 内の GitHub Actions アーティファクトとログの保持期間を設定する +intro: 'Organization 内の {% data variables.product.prodname_actions %} アーティファクトとログの保持期間を設定することができます。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.actions.about-artifact-log-retention %} + +## Organization の保持期間を設定する + +{% 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/ja-JP/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/ja-JP/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000..12880340df --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -0,0 +1,33 @@ +--- +title: Organization をユーザに変換する +intro: 'Organization は個人ユーザアカウントに変換できませんが、新しいユーザアカウントを作成して、そこへ Organization のリポジトリを移譲することは可能です。' +redirect_from: + - /articles/converting-an-organization-into-a-user + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +1. 新しい GitHub ユーザアカウントに[サインアップ](/articles/signing-up-for-a-new-github-account)します。 +2. [ユーザのロールをオーナーに変更](/articles/changing-a-person-s-role-to-owner)します。 +3. 新しいユーザアカウントに{% data variables.product.signin_link %}します。 +4. 新しいユーザアカウントに[各 Organization リポジトリを移譲](/articles/how-to-transfer-a-repository)します。 +5. [Organization を削除](/articles/deleting-an-organization-account)します。 +6. Organization の名前に[ユーザ名を変更](/articles/changing-your-github-username)します。 + +{% else %} + +1. 新しい GitHub Enterprise ユーザアカウントにサインアップします。 +2. [ユーザのロールをオーナーに変更](/articles/changing-a-person-s-role-to-owner)します。 +3. 新しいユーザアカウントに{% data variables.product.signin_link %}します。 +4. 新しいユーザアカウントに[各 Organization リポジトリを移譲](/articles/how-to-transfer-a-repository)します。 +5. [Organization を削除](/articles/deleting-an-organization-account)します。 +6. Organization の名前に[ユーザ名を変更](/articles/changing-your-github-username)します。 + +{% endif %} diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md new file mode 100644 index 0000000000..b445d8b6ea --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -0,0 +1,34 @@ +--- +title: Organization アカウントの削除 +intro: 'Organization を削除すると、リポジトリ、プライベートリポジトリのフォーク、ウィキ、Issue、プルリクエスト、プロジェクトページや Organization ページもすべて削除されます。 {% if currentVersion == "free-pro-team@latest" %}Organization 名は新しいユーザや Organization のアカウントで使用できるようになり、支払いは終了します。{% endif %}' +redirect_from: + - /articles/deleting-an-organization-account + - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**参考**: 有料プランを解約したい場合、Organization とそのコンテンツを削除する代わりに、[Organization を {% data variables.product.prodname_free_team %} にダウングレードする](/articles/downgrading-your-github-subscription)ことができます。 + +{% endtip %} + +{% endif %} + +### 1. Organization コンテンツのバックアップ + +Organization を削除すると、GitHub では**コンテンツを復元できません**。 したがって、Organization を削除する前に、アカウントからすべてのリポジトリ、ウィキ、Issue、プロジェクトボードのコピーがあることを確認してください。 + +### 2. Organization の削除 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Organization の設定ページの下の方にある [**Delete this Organization**] をクリックします。 ![[Delete this organization] ボタン](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000..6be9e7c03e --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,85 @@ +--- +title: Organization について GitHub Actions を無効化または制限する +intro: 'Organization のオーナーは Organization の GitHub Actions を無効化、有効化、制限することができます。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Organization の {% data variables.product.prodname_actions %} 権限について + +{% data reusables.github-actions.disabling-github-actions %} {% data variables.product.prodname_actions %} の詳細は、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。 + +Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化することができます。 {% data reusables.github-actions.enabled-actions-description %} Organization のすべてのリポジトリについて 、{% data variables.product.prodname_actions %} を無効化できます。 {% data reusables.github-actions.disabled-actions-description %} + +あるいは、Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化したうえで、ワークフローで実行できるアクションを制限することができます。 {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### Organization の {% data variables.product.prodname_actions %} 権限の管理 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. [**Local and third-party Actions**] で、オプションを選択します。 ![この Organization でアクションを有効化、無効化、制限](/assets/images/help/repository/enable-org-actions.png) +1. [**Save**] をクリックします。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### Organization の {% data variables.product.prodname_actions %} 権限の管理 + +Organization のワークフローをすべて無効にすることも、Organization でどのアクションを使用できるかを設定するポリシーを設定することもできます。 + +{% data reusables.actions.actions-use-policy-settings %} + +{% note %} + +**注釈:** Organizationが、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 詳しい情報については、 {% if currentVersion == "free-pro-team@latest" %}「[Enterprise アカウントで {% data variables.product.prodname_actions %} のポリシーを施行する](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)」{% else %}"[Enterprise で{% data variables.product.prodname_actions %} のポリシーを施行する](/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. [**Policies**] でオプションを選択します。 ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png) +1. [**Save**] をクリックします。 + +### Allowing specific actions to run + +{% 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. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) +1. [**Save**] をクリックします。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### プライベートリポジトリのフォークのワークフローを有効にする + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Organization のプライベートフォークポリシーを設定する + +{% 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/ja-JP/content/organizations/managing-organization-settings/index.md b/translations/ja-JP/content/organizations/managing-organization-settings/index.md new file mode 100644 index 0000000000..b6bd87c876 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/index.md @@ -0,0 +1,39 @@ +--- +title: Organization の設定を管理する +intro: 'Organization の管理者は、Organization に属するリポジトリの名前や、オーナー チームのメンバーシップなど、いつくかの設定を変更できます。 また、Organization とそのリポジトリすべてを削除することもできます。' +redirect_from: + - /articles/managing-organization-settings + - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 /managing-the-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 %} diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000..2e73146698 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,26 @@ +--- +title: Organization のプロジェクトボードに JIRA を統合する +intro: 'Jira Cloud を Organization のアカウントに統合すると、コミットとプルリクエストをスキャンし、メンションされている JIRA の Issue で、関連するメタデータとハイパーリンクを作成できます。' +redirect_from: + - /articles/integrating-jira-with-your-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. 左サイドバーの [**Organization settings**] で、Organization の名前をクリックします。 ![サイドバーの Organization 名](/assets/images/help/settings/organization-settings-from-sidebar.png) +3. 左サイドバーの **[Developer settings]** で、[**OAuth applications**] をクリックします。 ![左サイドバーの [OAuth applications] タブ](/assets/images/help/organizations/org-oauth-applications-ghe.png) +4. [**Register a new application**] をクリックします。 +5. [**Application name**] に "Jira" と入力します。 +6. [**Homepage URL**] に、JIRA インスタンスの完全な URL を入力します。 +7. [**Authorization callback URL**] に、JIRA インスタンスの完全な URL を入力します。 +8. **Register application** をクリックする。 ![[Register application] ボタン](/assets/images/help/oauth/register-application-button.png) +9. [**Organization owned applications**] で、[Client ID] と [Client Secret] の値を確認します。 ![クライアント ID とクライアントシークレット](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### 参考リンク + +- [「JIRA を個人プロジェクトに統合する」](/articles/integrating-jira-with-your-personal-projects) +- Jira Cloud を GitHub に接続する (Atlassian ドキュメント) diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..25ffe5908e --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,67 @@ +--- +title: Organization 内のリポジトリのためのデフォルトラベルを管理する +intro: Organization の新しいリポジトリすべてに含まれるラベルをカスタマイズできます。 +redirect_from: + - /articles/managing-default-labels-for-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organizationのオーナーは、Organization のリポジトリのデフォルトラベルを管理できます。 + +デフォルトラベルは、Organization の新しいリポジトリすべてに含まれますが、そのリポジトリへの書き込みアクセスがある人は誰でも、そのリポジトリのラベルを後で編集または削除できます。 デフォルトラベルを追加、編集、削除しても、既存リポジトリのラベルは追加、編集、削除されません。 + +### デフォルトラベルの作成 + +{% 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. [Repository labels] で、[**New label**] をクリックします。 ![[New label] ボタン](/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 %} + +### デフォルトラベルの編集 + +{% 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 %} + +### デフォルトラベルの削除 + +{% 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 %} + +### 参考リンク + +- [ラベルについて](/articles/about-labels) diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..701128a5c5 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Organization 内のリポジトリのディスカッション作成を管理する +intro: Organization が所有するリポジトリで、メンバーがディスカッションを作成するために必要な権限レベルを選択できます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization +permissions: Organization のオーナーは、Organization が所有するリポジトリのディスカッションの作成を管理できます。 +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.discussions.beta %} + +### 読み取りアクセス権を持つユーザがディスカッションを作成することを許可または禁止する + +デフォルト設定では、リポジトリ管理者または Organization のオーナーが Organization が所有するリポジトリのディスカッションを有効にすると、読み取りアクセス権を持つ Organization のメンバーがディスカッションを作成できます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +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**] をクリックします。 ![ディスカッション設定の [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)" diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000..b955da6433 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,66 @@ +--- +title: Organization にスケジュールされたリマインダーを管理する +intro: Organization の Team がレビューをリクエストされたすべてのプルリクエストについて、Slack でリマインダーを受け取ることができます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### プルリクエストのスケジュールされたリマインダーについて + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Organization のオーナーは、Team がレビューをリクエストされたすべてのプルリクエストについて、その Organization の 1 つ以上の Team にリマインダーをスケジュールできます。 + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Organization のスケジュールされたリマインダーを作成する +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![[Scheduled reminders] ボタン](/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. [Filter by team assigned to review code] で、[**Add a team**] ドロップダウンをクリックし、1 つ以上の Team を選択します。 最大 100 チームまで追加できます。 選択した Team が、上で選択する [Tracked repositories] にアクセスできない場合は、スケジュールされたリマインダーは作成できません。 ![[Add a team] ドロップダウン](/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 %} + +### Organization のスケジュールされたリマインダーを管理する +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Organization のスケジュールされたリマインダーを削除する +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![[Scheduled reminders] ボタン](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.delete %} + +### 参考リンク + +- [スケジュールされたリマインダーの管理](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders) +- [Team のスケジュールされたリマインダーを管理する](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team) diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..5cb01fa620 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Organization のリポジトリのデフォルブランチ名を管理する +intro: 'Organization でメンバーが作成するリポジトリについて、デフォルトブランチ名を設定できます。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +permissions: リポジトリのデフォルトブランチ名を管理する +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +### デフォルトブランチ名について + +Organization のメンバーが Organization で新しいリポジトリを作成するとき、リポジトリにはブランチが 1 つ含まれます。これがデフォルトブランチです。 Organization のメンバーが新しいリポジトリを作成するとき、{% data variables.product.prodname_dotcom %} はブランチを 1 つ作成し、それをリポジトリのデフォルトブランチに設定します。 デフォルトブランチの詳細については、「[ブランチについて](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)」を参照してください。 + +{% data reusables.branches.set-default-branch %} + +Enterprise のオーナーが Enterprise のデフォルトブランチ名にポリシーを適用している場合、Organization のデフォルトブランチ名を設定することはできません。 代わりに、個々のリポジトリのデフォルトブランチを変更できます。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" %}「[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 %}「[Enterprise でリポジトリ管理ポリシーを適用する](/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)」を参照してください。 + +### デフォルトブランチ 名を設定する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. [Repository default branch] で、[**Change default branch name now**] をクリックします。 ![[Override] ボタン](/assets/images/help/organizations/repo-default-name-button.png) +4. 新しいブランチに使用したいデフォルト名を入力します。 ![デフォルト名を入力するテキストフィールド](/assets/images/help/organizations/repo-default-name-text.png) +5. [**Update**] をクリックします。 ![[Update] ボタン](/assets/images/help/organizations/repo-default-name-update.png) + +### 参考リンク + +- /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000..78565f202c --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,28 @@ +--- +title: Organization のメンバー名表示を管理する +intro: Organization のプライベートリポジトリ内において、Organization のメンバーが、コメント作者のプロフィール名を表示できるよう許可することができます。 +product: '{% data reusables.gated-features.display-names %}' +redirect_from: + - /articles/managing-the-display-of-member-names-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization のオーナーは、Organization 内のメンバー名表示を管理できます。 + +![コメントに表示されたコメント作者の名前](/assets/images/help/issues/commenter-full-name.png) + +Organization の各メンバーは、自分のプロフィール名を設定で選択します。 詳細は「[プロフィールをパーソナライズする](/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. [Admin repository permissions] の下で、[**Allow members to see comment author's profile name in private repositories**] を選択または選択解除します。 ![プライベートリポジトリ内で、コメント作者のフルネームを表示することをメンバーに許可するためのチェックボックス](/assets/images/help/organizations/allow-members-to-view-full-names.png) +6. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000..f894754465 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Organization のフォークポリシーを管理する +intro: 'Organization が所有するプライベート{% 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 + - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization +permissions: Organization のオーナーは、Organization のフォークポリシーを管理できます。 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +デフォルトでは、新しい Organization はプライベート{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} および内部{% endif %} リポジトリのフォークを禁止するように設定されます。 + +Organization レベルでプライベート{% 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 %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. [Repository forking] で、[**Allow forking of private repositories**] または [**Allow forking of private and internal repositories**] を選択します。 ![Organization でフォークを許可または禁止するチェックボックス](/assets/images/help/repository/allow-disable-forking-organization.png) +6. [**Save**] をクリックします。 + +### 参考リンク + +- [フォークについて](/articles/about-forks) +- [Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..61f713baed --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Organization の GitHub Pages サイトの公開を管理する +intro: 'Organization のメンバーが Organization 内のリポジトリから {% data variables.product.prodname_pages %} サイトを公開できるかどうかを制御し{% if currentVersion == "free-pro-team@latest" %}、メンバーがサイトに対して選択できる可視性を制限できます{% endif %}。' +permissions: 'Organization のオーナーは、Organization のリポジトリからの {% data variables.product.prodname_pages %} サイトの公開を管理できます。' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. それ以外の場合は、公開を許可するか禁止するかを選択できます。 {% data variables.product.prodname_pages %} サイトのアクセス制御の詳細については、「[{% data variables.product.prodname_pages %} サイトの可視性を変更する](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)」を参照してください。 +{% endif %} + +{% data variables.product.prodname_pages %} サイトの公開を許可しない場合、すでに公開されているサイトはすべて公開されたままになります。 そのサイトは手動で取り下げることができます。 詳細は「[{% data variables.product.prodname_pages %}サイトの取り下げ](/pages/getting-started-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 %}{% if currentVersion == "free-pro-team@latest" %} +1. [Pages creation] で、許可する可視性を選択し、禁止する可視性を選択解除します。 ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. [Pages creation] で、[**Allow members to publish sites**] を選択または選択解除します。 ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. [**Save**] をクリックします。 + +### 参考リンク + +- 「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..2a8425103c --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,28 @@ +--- +title: Organization のスポンサーアカウントからの更新を管理する +intro: Organization がスポンサーしているアカウントから更新を受信するメールアドレスを管理できます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors +versions: + free-pro-team: '*' +permissions: Organization のオーナーは、Organization のスポンサーアカウントから更新を管理できます。 +topics: + - organizations + - teams +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +Organization がスポンサーする開発者や Organization は、作業に関する最新情報を送信できます。 これらの更新を受信するメールアドレスを管理できます。 + +Organization のスポンサーアカウントからの更新を無効化することもできます。 詳細は「[スポンサーシップを管理する](/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. [Sponsors update email (Private)] の下に、Organization のスポンサーアカウントから更新を受信するメールアドレスを入力します。 ![スポンサーアカウントから更新を受信するためのメールアドレスを入力するためのテキストボックス](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. [**Update profile**] をクリックします。 ![[Update profile] ボタン](/assets/images/help/organizations/update-profile-button.png) + +### 参考リンク + +- 「[{% data variables.product.prodname_sponsors %} でオープンソースコミュニティをサポートする](/github/supporting-the-open-source-community-with-github-sponsors)」 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md new file mode 100644 index 0000000000..84a5ff2bf7 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -0,0 +1,50 @@ +--- +title: Organization の名前を変更する +intro: 'プロジェクトや企業の名前が変更になった場合、Organization の名前を更新して一致させることができます。' +redirect_from: + - /articles/what-happens-when-i-change-my-organization-s-name/ + - /articles/renaming-an-organization + - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**ヒント:** Organization の名前を変更できるのは Organization オーナーだけです。 {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +### Organization の名前を変更するとどうなりますか？ + +Organization の名前を変更したら、古い Organization 名は他の個人が使用できるようになります。 Organization の名前を変更すると、古い Organization 名の下にあるリポジトリへの参照のほとんどが、自動で新しい名前に変わります。 ただし、プロフィールへのリンクによっては、自動的にリダイレクトされません。 + +#### 自動で行われる変更 + +- {% data variables.product.prodname_dotcom %} ではリポジトリへの参照を自動でリダイレクトします。 Organization に既存の**リポジトリ**への Web リンクは引き続き機能します。 変更を開始してから完了するまでに数分かかることがあります。 +- ローカルリポジトリのプッシュは、古いリモートトラッキング URL へは更新なしでそのまま行えます。 ただし、Organization の名前を変更したら、既存のすべてのリモートリポジトリ URL を更新するよう推奨します。 変更後の古い Organization 名は他のいずれの個人も使用できるようになるため、新しい Organization オーナーがリポジトリへのリダイレクトエントリをオーバーライドすることがありえます。 For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +- 以前の Git コミットも、Organization 内のユーザへ正しく関連付けられます。 + +#### 自動ではない変更 + +Organization の名前を変更したら、次のようになります: +- 以前の Organization プロフィールページ (`https://{% data variables.command_line.backticks %}/previousorgname` など) にリンクすると、404 エラーが返されます。 他のサイト{% if currentVersion == "free-pro-team@latest" %} (LinkedIn や Twitter のプロフィールなど) {% endif %}からの Organization へのリンクを更新するよう推奨します。 +- 古い Organization 名を使用する API リクエストでは、404 エラーが返されます。 API リクエストにある古い Organization 名を更新するようおすすめします。 +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} + +### Organization の名前を変更する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. 設定ページの末尾近くにある [Rename organization] の下の [**Rename Organization**] をクリックします。 ![[Rename organization] ボタン](/assets/images/help/settings/settings-rename-organization.png) + +### 参考リンク + +* 「[コミットが間違ったユーザにリンクされているのはなぜですか？](/articles/why-are-my-commits-linked-to-the-wrong-user)」 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000..f232b0a83b --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,35 @@ +--- +title: Organization 内でリポジトリの作成を制限する +intro: 'Organization のデータを保護するために、Organization 内でリポジトリを作成するための権限を設定できます。' +redirect_from: + - /articles/restricting-repository-creation-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +メンバーが Organization でリポジトリを作成できるかどうかを選択できます。 メンバーにリポジトリの作成を許可する場合、メンバーが作成できるリポジトリの種類を選択できます。{% if currentVersion == "free-pro-team@latest" %}メンバーがプライベートリポジトリのみを作成することを許可する場合、Organization は {% data variables.product.prodname_ghe_cloud %} を使用する必要があります。{% endif %} 詳細は「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」を参照してください。 + +Organization のオーナーは、いつでもどんなタイプの Team でも作成できます。 + +{% if currentVersion == "free-pro-team@latest" %}Enterprise オーナー{% else %}サイト管理者{% endif %}は、Organization のリポジトリ作成ポリシーで使用できるオプションを制限できます。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" %}"「[Enterprise アカウントでリポジトリ管理ポリシーを施行する](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account)」{% else %}「[Enterprise でのリポジトリの作成を制限する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」{% endif %} を参照してください。 + +{% warning %} + +**警告**: この設定で制限されるのは、リポジトリを作成するときの可視性オプションだけです。後からリポジトリの可視性を変更する機能は制限されません。 詳しい情報については「[Organization 内でリポジトリの可視性の変更を制限する](/organizations/managing-organization-settings/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. [Repository creation] で、1 つ以上のオプションを選択します。 ![リポジトリ作成のオプション](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +6. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..3af1552872 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Organization 内でリポジトリの可視性の変更を制限する +intro: 'Organization のデータを保護するために、Organization 内でリポジトリの可視性を変更するための権限を設定できます。' +redirect_from: + - /articles/restricting-repository-visibility-changes-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +リポジトリの可視性を変更する資格を Organization のオーナーのみに制限すること、または可視性を変更することをリポジトリの管理者権限を所有するメンバーに許可することができます。 + +{% warning %} + +**警告**: この設定を有効にすると、管理者権限をもつユーザは、作成できるリポジトリのタイプにかかわらず、既存のリポジトリを任意の可視性に変更できるようになります。 詳しい情報については「[Organization でのリポジトリ作成の制限](/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. [Repository visibility change] の下で、[**Allow members to change repository visibilities for this organization**] の選択を解除します。 ![リポジトリ可視性変更をメンバーに許可するチェックボックス](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) +6. [**Save**] をクリックします。 + +### 参考リンク + +- 「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000..9e9df80c1c --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,28 @@ +--- +title: 外部のコラボレーターを追加するための権限を設定する +intro: 'Organization のデータを保護し、Organization 内で使用されている有料ライセンスの数が無駄遣いされないようにするために、外部コラボレーターを Organization のリポジトリに招待することをオーナーのみに許可できます。' +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +リポジトリに対する管理者権限を持つ Organization のオーナーとメンバーは、リポジトリで作業するように外部のコラボレーターを招待できます。 外部のコラボレーターの招待権限を、Organization のオーナーに制限することもできます。 + +{% 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. [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/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000..1a00ac0b42 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,24 @@ +--- +title: リポジトリを削除または移譲する権限を設定する +intro: 'リポジトリの削除や移譲を、リポジトリの管理者権限を持つ Organization メンバーに許可したり、Organization のオーナーのみがリポジトリを削除や移譲できるよう制限したりできます。' +redirect_from: + - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ + - /articles/setting-permissions-for-deleting-or-transferring-repositories + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +コードオーナーは、Organization 内のリポジトリについて、削除や移譲の権限を設定できます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. [Repository deletion and transfer] の下で、[**Allow members to delete or transfer repositories for this organization**] を選択または選択解除します。 ![リポジトリの削除をメンバーに許可するためのチェックボックス](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) +6. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000..1d47459fe5 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Organization のチーム作成権限を設定する +intro: Organization のメンバーが Team を作成できるように許可する、もしくは Organization のオーナーのみ Team を作成できるように制限することができます。 +redirect_from: + - /articles/setting-team-creation-permissions-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization のオーナーは Team の作成権限を設定できます。 + +Team の作成権限を設定しなかった場合、デフォルトでは、すべての Organization メンバーが Team を作成できるようになります。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. [Team creation rules] で、[**Allow members to create teams**] を選択または選択解除します。 ![Team の作成をメンバーに許可するためのチェックボックス](/assets/images/help/organizations/allow-members-to-create-teams.png) +6. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md new file mode 100644 index 0000000000..76b582f9e7 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -0,0 +1,29 @@ +--- +title: Organization の所有権を移譲する +intro: '他の誰かを Organization アカウントのオーナーにするには、新しいオーナーを追加し、{% if currentVersion == "free-pro-team@latest" %}請求情報が更新されることを確認し、{% endif %}アカウントから自分を削除します。' +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership + - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +1. もしあなたが *owner* の権限を持つ唯一のメンバーである場合、他の Organization メンバーにオーナーロールを付与します。 詳細は「[Organizationのオーナーの指名](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)」を参照してください。 +2. 新しいオーナーに連絡し、そのオーナーが [Organization の設定にアクセス](/articles/accessing-your-organization-s-settings)できることを確認します。 +{% if currentVersion == "free-pro-team@latest" %} +3. Organization で GitHub への支払いを現在担当している場合、新しいオーナーまたは[支払いマネージャー](/articles/adding-a-billing-manager-to-your-organization/)に Organization の支払い情報を更新してもらう必要があります。 詳細は「[支払い方法を追加または編集する](/articles/adding-or-editing-a-payment-method)」を参照してください。 + + {% warning %} + + **警告**: Organization から自身を削除しても、Organization アカウントのファイル上の支払い情報は**更新されません**。 新しいコードオーナーまたは支払いマネージャーは、あなたのクレジットカードまたは Paypal の情報を削除するためにファイル上の支払い情報を更新しなければなりません。 + + {% endwarning %} + +{% endif %} +4. Organization から[自分を削除する](/articles/removing-yourself-from-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/ja-JP/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000..487268a248 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,24 @@ +--- +title: 企業利用規約にアップグレードする +intro: Organization は、標準の利用規約から企業の利用規約にアップグレードできます。 +redirect_from: + - /articles/upgrading-to-the-corporate-terms-of-service + - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +標準の利用規約は、{% data variables.product.prodname_dotcom %} と個人としてのあなたとの間の合意です。 会社、非営利団体、グループなどのエンティティに代わって {% data variables.product.prodname_dotcom %} との契約を締結するには、Organization のオーナーが企業利用規約にアップグレードします。 + +1. 企業利用規約へのアップグレードをリクエストするには、{% data variables.contact.contact_support %} にお問い合わせください。 彼らは、Organization のダッシュボード上のバナーを有効にします。それにより、企業利用規約を受け入れることができます。 +{% data reusables.dashboard.access-org-dashboard %} +3. ページ上部の利用規約バナーの右側にある [**Sign now**] をクリックします。 ![[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) +5. Organization アカウントを所有する会社、非営利団体、またはグループの名前を入力します。 これは、{% data variables.product.prodname_dotcom %} と契約を締結するエンティティです。 ![ビジネス名フィールド](/assets/images/help/organizations/business-name-field.png) +6. エンティティを代表して企業利用規約に同意するには、[**Accept terms**] をクリックします。 ![[Accept terms] ボタン](/assets/images/help/organizations/accept-terms-button.png) + +### 参考リンク +- 「[GitHub の企業利用規約](/articles/github-corporate-terms-of-service/)」 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md b/translations/ja-JP/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md new file mode 100644 index 0000000000..818810ac33 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md @@ -0,0 +1,42 @@ +--- +title: Organization のドメインを検証する +intro: 'Organization が管理しているドメインを検証して、{% data variables.product.product_name %} で Organization のアイデンティティを確認できます。' +redirect_from: + - /articles/verifying-your-organization-s-domain + - /articles/verifying-your-organizations-domain + - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### ドメイン検証について + +{% data variables.product.product_name %} 上のドメインを確認するには、Organization のコードオーナー権限が必要です。 詳細は「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」を参照してください。 ドメインホスティングサービスでドメインレコードを変更するためのアクセスも必要になります。 + +Organization のドメインの所有権を検証したあと、「検証済み」バッジが Organization のプロフィールに表示されます。 Organization が {% data variables.product.prodname_ghe_cloud %} 上にあり、企業向け利用規約に同意した場合、Organization のオーナーは、検証済みドメインにある各メンバーのメールアドレスを見て、Organization メンバーの身元を検証できるようになります。 詳細は「[Organization のプロフィールページについて](/articles/about-your-organization-s-profile/)」および「[企業利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。 + +Enterprise アカウントがオーナーの Organization の場合、Organization による検証済みのドメインに加えて、Enterprise アカウントで検証されたドメインの「検証済み」バッジが Organization のプロフィールに表示されます。 詳しい情報については、「[Enterprise アカウントのドメインを検証する](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)」を参照してください。 + +{% data reusables.organizations.verified-domains-details %} + +{% data variables.product.prodname_ghe_cloud %} では、Organization のドメインの所有権を検証したあと、その Organization へのメール通知を制限することができます。 詳しい情報については「[メール通知を承認済みドメインに制限する](/articles/restricting-email-notifications-to-an-approved-domain)」を参照してください。 + +### Organization のドメインを検証する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +5. [**Add a domain**] をクリックします。 ![[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. DNS 設定が変更されるまで待ちます。これには、最大 72 時間かかる場合があります。 コマンドラインで `dig` コマンドを実行し、`ORGANIZATION` を Organization の名前に、`example.com` を検証するドメインに置き換えることで、DNS 設定が変更されたことを確認できます。 新しい TXT レコードがコマンド出力に表示されているはずです。 + ```shell + $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT + ``` +8. TXT レコードが DNS に追加されたことを確認したら、組織の設定の [Verified domains] タブに移動します。 [Verified domains] タブを探すには、上記のステップ 1 〜 4 を実行します。 ![保留ドメインを含む確認済みドメイン設定ページ](/assets/images/help/organizations/pending-domain-verification.png) +{% data reusables.organizations.continue-verifying-domain %} +11. 必要に応じて、Organization のプロフィールページに「検証済み」バッジが表示されたら、ドメインホスティングサービスの DNS レコードから TXT エントリを削除できます。 ![検証済みバッジ](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000..e812f12969 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,57 @@ +--- +title: Organization への支払いマネージャーの追加 +intro: '*支払いマネージャー*は、支払い情報の更新など、Organization の支払い設定を管理するユーザです。 Organization の通常のメンバーが支払いのリソースにアクセスできないことが普通なら、これは良い選択肢になります。' +redirect_from: + - /articles/adding-a-billing-manager-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - 支払い +--- + +Organization のオーナーの Team のメンバーは、人に*支払いマネージャー*権限を与えることができます。 Organization の支払いマネージャーになる招待を受け入れた人は、追加で他の人に、支払いマネージャーになるよう招待できます。 + +{% note %} + +**注釈:** 支払いマネージャーは、Organization のプラン中の有料ライセンスを消費しません。 + +{% endnote %} + +### 支払いマネージャーの権限 + +支払いマネージャーは以下のことができます: + +- アカウントのアップグレードまたはダウングレード +- 支払い方法の追加、更新、削除 +- 支払い履歴の閲覧 +- 領収書のダウンロード +- 支払いマネージャーの表示、招待、削除 + +加えて、すべての支払いマネージャーは Organization の支払日にメールで領収書を受け取ります。 + +支払いマネージャーは以下のことは**できません**: + +- Organization のリポジトリの作成あるいはアクセス +- Organization のプライベートメンバーの閲覧 +- Organization メンバーのリスト内に表示されること +- {% data variables.product.prodname_marketplace %}アプリケーションのサブスクリプションの購入、編集、キャンセル + +{% tip %} + +**ヒント:** Organization が[ メンバー、支払いマネージャー、外部のコラボレータに 2 要素認証を使うことを求める](/articles/requiring-two-factor-authentication-in-your-organization)場合、ユーザは Organization の支払いマネージャーになるための招待を受け付ける前に 2 要素認証を有効化しなければなりません。 + +{% endtip %} + +### 支払いマネージャーの招待 + +招待された人は、Organization の支払いマネージャーになることを依頼する招待メールを受信します。 招待された人が招待メール中の受諾のリンクをクリックすると、その人は自動的に支払いマネージャーとして Organization に追加されます。 その人がまだ GitHub のアカウントを持っていない場合は、アカウント作成のためのサインアップにリダイレクトされ、アカウント作成後に自動的に支払いマネージャーとして Organization に追加されます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Billing managers（支払いマネージャー）の隣にある [**Add a billing manager**] をクリックします。 ![支払いマネージャーの招待](/assets/images/help/billing/settings_billing_managers_list.png) +6. 追加したい人のユーザ名あるいはメールアドレスを入力し、[**Send Invitation**] をクリックします。 ![支払いマネージャーの招待ページ](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000..dd7e127038 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,29 @@ +--- +title: Organization メンバーに「チームメンテナー」権限を付与する +intro: 'Organization のオーナーは、Organization の任意のメンバーを Team の *チームメンテナー* に昇格させて、Organization のオーナーが持ついくつかの権限を付与することができます。' +redirect_from: + - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ + - /articles/giving-team-maintainer-permissions-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team_maintainers_can %} + +### Organization メンバーをチームメンテナに昇格させる + +Organization メンバーをチームメンテナに昇格させる前に、昇格対象の人物がすでに Team のメンバーである必要があります。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +4. チームメンテナに昇格させる人 (一人または複数人) を選択します。 ![Organization メンバーの横のチェックボックス](/assets/images/help/teams/team-member-check-box.png) +5. Team のメンバー一覧の上にあるドロップダウンメニューを使用して、[**Change role...**] をクリックします。 ![ロールを変更するオプションのあるドロップダウンメニュー](/assets/images/help/teams/bulk-edit-drop-down.png) +6. 新しいロールを選択して、[**Change role**] をクリックします。 ![メンテナーまたはメンバーのロールのラジオボタン](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md new file mode 100644 index 0000000000..071d5fb284 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -0,0 +1,21 @@ +--- +title: Organization へのアクセスをロールで管理する +intro: 'Organization における個人のロールは、Organization、その設定、およびデータにアクセスできるレベルを決めるものです。 個人を Organization のオーナー、メンバー、支払いマネージャーに指定したり、チームメンテナの権限を付与したりできます。' +redirect_from: + - /articles/managing-people-s-access-to-your-organization-with-roles + - /articles/managing-peoples-access-to-your-organization-with-roles + - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000..f9874b0398 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Organization の所有権の継続性を管理する +intro: Organization には、所有権で問題が起きないように複数の Organizationのオーナーを設定できます。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization +permissions: Organizationのオーナーは、Organization のメンバーを Organizationのオーナーに昇格させることができます。 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Organization の所有権の継続性の管理について + +{% data reusables.organizations.org-ownership-recommendation %} + +Organizationのオーナーには、Organization に対する管理アクセス権限があります。 {% data reusables.organizations.new-org-permissions-more-info %} + +### Organizationのオーナーの指名 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. オーナーに昇格させる人 (一人または複数人) を選択します。 ![2 人のメンバーを選択した状態のメンバーリスト](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Team のメンバー一覧の上にあるドロップダウンメニューで [**Change role**] をクリックします。 ![メンバーを削除するオプションのあるドロップダウンメニュー](/assets/images/help/teams/user-bulk-management-options.png) +6. 新しいロールを選択して、[**Change role**] をクリックします。 ![[Owner] ラジオボタン、[Member] ラジオボタン、[Change role] ボタン](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md new file mode 100644 index 0000000000..fddae34ac9 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -0,0 +1,147 @@ +--- +title: Organization の権限レベル +intro: '[Organizationを作成](/articles/creating-a-new-organization-account)したら、Organization アカウントを管理する少人数グループにオーナー権限を付与する必要があります。' +redirect_from: + - /articles/permission-levels-for-an-organization-early-access-program/ + - /articles/permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Organization の権限レベル + +Organization のメンバーは、*owner (オーナー)*{% if currentVersion == "free-pro-team@latest" %}、*billing manager (支払いマネージャー)*、{% endif %}あるいは *member (メンバー)* ロールを持つことができます。 + +- **オーナー**は、Organization について完全な管理アクセスを持ちます。 このロールは制限する必要がありますが、Organization で少なくとも 2 人は指定する必要があります。 詳細は、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" %} +- **支払いマネージャー**は、個人に支払い設定の管理を許可できます。 詳細は「[Organization に支払いマネージャーを追加する](/articles/adding-a-billing-manager-to-your-organization)」を参照してください。 +{% endif %} +- **メンバー**は、それ以外のユーザのデフォルトのロールです。 + +{% if currentVersion == "free-pro-team@latest" %} + + +| Organization のアクション | オーナー | メンバー | 支払いマネージャー | +|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:---------:| +| リポジトリの作成 (詳細については「[Organization 内でリポジトリの作成を制限する](/articles/restricting-repository-creation-in-your-organization)」を参照) | **X** | **X** | | +| 支払い情報を表示および編集する | **X** | | **X** | +| Organization に参加するようユーザを招待する | **X** | | | +| Organization に参加する招待を編集およびキャンセルする | **X** | | | +| Organization からメンバーを削除する | **X** | | | +| 以前のメンバーを Oraganization に復帰させる | **X** | | | +| **すべての Team** に対してユーザーを追加および削除する | **X** | | | +| Organization メンバーを*チームメンテナ*に昇格させる | **X** | | | +| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)を参照) | **X** | | | +| スケジュールされたリマインダーを設定する (「[プルリクエストのスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)」を参照) | **X** | | | +| **すべてのリポジトリに**コラボレーターを追加する | **X** | | | +| Organization 参加ログにアクセスする | **X** | | | +| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/articles/about-your-organization-s-profile)」を参照) | **X** | | | +| Organization のドメインを検証する (詳細は「[Organization のドメインを検証する](/articles/verifying-your-organization-s-domain)」を参照) | **X** | | | +| メール通知を検証済みドメインに制限する（詳細は、「[メール通知を承認済みドメインに制限する](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)」を参照してください） | **X** | | | +| **すべての Team** を削除する | **X** | | | +| すべてのリポジトリを含めて Organization のアカウントを削除する | **X** | | | +| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照) | **X** | **X** | | +| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照) | **X** | **X** | | +| Organization の全メンバーおよび Team の表示 | **X** | **X** | | +| 参照可能なチームへの @メンション | **X** | **X** | | +| *チームメンテナ*に指定できる | **X** | **X** | | +| Organization のインサイトを表示する (詳細は「[Organization のインサイトを表示する](/articles/viewing-insights-for-your-organization)」を参照) | **X** | **X** | | +| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照) | **X** | **X** | | +| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照) | **X** | | | +| **すべての Team** で Team ディスカッションを編集および削除する (詳細は「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments)」を参照) | **X** | | | +| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)」を参照) | **X** | **X** | | +| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照) | **X** | | | +| Organization dependency insights の可視性を管理する (詳細は「[Organization dependency insights の可視性を変更する](/articles/changing-the-visibility-of-your-organizations-dependency-insights)」を参照) | **X** | | | +| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照) | **X** | | | +| アカウントをスポンサーし、Organization のスポンサーシップを管理する（詳細は、「[オープンソースコントリビューターをスポンサーする](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)」を参照） | **X** | **X** | | +| スポンサーアカウントからのメール更新の管理（詳細は、「[Organization のスポンサーアカウントからの更新を管理する](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)」を参照） | **X** | | | +| スポンサーシップを別の Organization に関連付ける（詳細は、「[Organization へのスポンサーシップの関連付け](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)」を参照してください）。 | **X** | | | +| Organization 内のリポジトリからの {% data variables.product.prodname_pages %} サイトの公開を管理する（詳細は、「[Organization の {% data variables.product.prodname_pages %} サイトの公開を管理する](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照） | **X** | | | +| Organization のセキュリティおよび分析設定を管理する (詳細は「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照) | **X** | | | +| [SAML シングルサインオン](/articles/about-identity-and-access-management-with-saml-single-sign-on)を有効にして強制する | **X** | | | +| [組織へのユーザーの SAML アクセスを管理する](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** | | | +| リポジトリを移譲する | **X** | | | +| {% data variables.product.prodname_marketplace %} アプリケーションを購入、インストール、支払い管理、キャンセルする | **X** | | | +| {% data variables.product.prodname_marketplace %} のアプリケーションをリストする | **X** | | | +| Organization のリポジトリすべてについて、脆弱な依存関係についての [{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) アラートを受け取る | **X** | | | +| {% data variables.product.prodname_dependabot_security_updates %} の管理 (「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照) | **X** | | | +| [フォークポリシーの管理](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Organization のパブリックリポジトリでのアクティビティを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | +| Organization にある*すべてのリポジトリ*のプル (読み取り)、プッシュ (書き込み)、クローン作成 (コピー) | **X** | | | +| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換 | **X** | | | +| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| デフォルブランチ名を管理する (「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照) | **X** | | | +| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照) | **X** | | | +| Team の同期を有効化する (「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照) | **X** | | | + +{% else %} + + +| Organization のアクション | オーナー | メンバー | +|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------------------------------------------------------------------------:| +| Organization に参加するようユーザを招待する | **X** | | +| Organization に参加する招待を編集およびキャンセルする | **X** | | +| Organization からメンバーを削除する | **X** | | | +| 以前のメンバーを Oraganization に復帰させる | **X** | | | +| **すべての Team** に対してユーザーを追加および削除する | **X** | | +| Organization メンバーを*チームメンテナ*に昇格させる | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)を参照) | **X** | +{% endif %} +| **すべてのリポジトリに**コラボレーターを追加する | **X** | | +| Organization 参加ログにアクセスする | **X** | | +| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/articles/about-your-organization-s-profile)」を参照) | **X** | | | +| **すべての Team** を削除する | **X** | | +| すべてのリポジトリを含めて Organization のアカウントを削除する | **X** | | +| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照) | **X** | **X** | +| Organization の全メンバーおよび Team の表示 | **X** | **X** | +| 参照可能なチームへの @メンション | **X** | **X** | +| *チームメンテナ*に指定できる | **X** | **X** | +| リポジトリを移譲する | **X** | | +| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** | | +| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照) | **X** | **X** | | +| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照) | **X** | **X** | | +| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照) | **X** | | | +| **すべての Team** で Team ディスカッションを編集および削除する (「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments)」を参照) | **X** | | | +| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)」を参照) | **X** | **X** | **X** | +| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照) | **X** | | | +| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照) | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| Organization 内のリポジトリからの {% data variables.product.prodname_pages %} サイトの公開を管理する（詳細は、「[Organization の {% data variables.product.prodname_pages %} サイトの公開を管理する](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照） | **X** | +{% endif %} +| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Organization にある*すべてのリポジトリ*のプル (読み取り)、プッシュ (書き込み)、クローン作成 (コピー) | **X** | | +| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換 | **X** | | +| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/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" %} +| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照) | **X** | +{% endif %} +{% if currentVersion == "github-ae@latest" %}| IP 許可リストを管理する (詳細は「[Enterprise へのネットワークトラフィックを制限する](/admin/configuration/restricting-network-traffic-to-your-enterprise)」を参照) | **X** | |{% endif %} + +{% endif %} + +### {% data variables.product.prodname_github_app %} マネージャー + +デフォルトでは、Organization によって所有されている {% data variables.product.prodname_github_app %} の設定を管理できるのは Organization のオーナーだけです。 Organization によって所有されている {% data variables.product.prodname_github_app %} の管理を追加のユーザーに許可するために、オーナーは {% data variables.product.prodname_github_app %} マネージャーに権限を付与する必要があります。 + +ユーザーを Organization の {% data variables.product.prodname_github_app %} マネージャーとして指定すると、Organization によって所有されている一部またはすべての {% data variables.product.prodname_github_app %} の設定を管理するアクセス権を付与できます。 詳しい情報については、以下を参照してください。 + +- [GitHub App マネージャーを Organization に追加する](/articles/adding-github-app-managers-in-your-organization) +- [GitHub App マネージャーを Organization から削除する](/articles/removing-github-app-managers-from-your-organization) + +### 外部コラボレーター + +リポジトリへのアクセスを許可するとともに Organization のデータを安全に保つために、*外部のコラボレータ*を追加できます。 {% data reusables.organizations.outside_collaborators_description %} + +### 参考リンク + +- [Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization) +- [Team について](/articles/about-teams) +- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization) diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000..abd660b835 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Organization から支払いマネージャーを削除する +intro: '*支払いマネージャー* ロールが付与された個人が Organization の支払い情報の参照や変更を必要としなくなった場合、その個人のアクセスを Organization から削除することができます。' +redirect_from: + - /articles/removing-a-billing-manager-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - 支払い +--- + +{% warning %} + +**メモ:** {% 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. [支払いマネージャー] リストで、削除する個人の名前の横にある {% octicon "x" aria-label="X symbol" %} をクリックします。 ![支払いマネージャーの削除](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000..94c99cad3a --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,62 @@ +--- +title: SAML シングルサインオンを使うアイデンティティおよびアクセス管理について +intro: 'ユーザのアイデンティティとアプリケーションをアイデンティティプロバイダ (IdP) で集中管理する場合、Security Assertion Markup Language (SAML) シングルサインオン (SSO) を設定して {% data variables.product.prodname_dotcom %} での Organization のリソースを保護することができます。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/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 +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### SAML SSO について + +{% data reusables.saml.dotcom-saml-explanation %} + +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 のリソースにアクセスできます。 + +Organization のオーナーは、個々の Organization に SAML SSO を適用できます。または、Enterprise のオーナーは、Enterprise アカウント内のすべての Organization に SAML SSO を適用できます。 詳しい情報については、「[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 %} + +Organization で SAML SSO を有効化する前に、IdP を Organization に接続する必要があります。 詳細は「[アイデンティティプロバイダを Organization に接続する](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)」を参照してください。 + +1 つの Organization に対して、SAML SSO は無効化、強制なしの有効化、強制ありの有効化ができます。 Organization に対して SAML SSO を有効にし、Organization のメンバーが IdP での認証に成功した後、SAML SSO 設定を強制できます。 {% data variables.product.prodname_dotcom %} Organization に対して SAML SSO を強制する方法については、「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。 + +認証を受けて Organization のリソースにアクセスするために、メンバーは定期的に IdP の認証を受ける必要があります。 このログイン間隔は利用しているアイデンティティプロバイダ (IdP) によって指定されますが、一般的には 24 時間です。 このように定期的にログインしなければならないことから、アクセスの長さには制限があり、ユーザがアクセスを続行するには再認証が必要になります。 + +コマンドラインで API と Git を使用して、Organization の保護されているリソースにアクセスするには、メンバーが個人アクセストークンまたは SSH キーで認可および認証を受ける必要があります。 詳しい情報については、「[SAMLシングルサインオンで利用するために個人アクセストークンを認可する](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」と、「[SAML シングルサインオンで使用するために SSH キーを認可する](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。 + +メンバーが初めて SAML SSO を使用して Organization にアクセスする場合は、Organization にリンクするレコード、メンバーの {% data variables.product.prodname_dotcom %} アカウント、およびメンバーの IdP 上のアカウントを {% data variables.product.prodname_dotcom %} が自動的に作成します。 Organization または Enterprise アカウントのメンバーについて、リンクされた SAML アイデンティティ、アクティブセッション、認可されたクレデンシャルの表示と取り消しが可能です。 詳細は、「[Organization へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)」と「[Enterprise アカウントへのユーザの SAML アクセスの表示および管理](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)」を参照してください。 + +新しいリポジトリを作成するときにメンバーが SAML SSO セッションでサインインする場合、そのリポジトリのデフォルトの可視性はプライベートになります。 それ以外の場合、デフォルトの可視性はパブリックです。 リポジトリの可視性に関する詳しい情報については、「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」を参照してください。 + +{% 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 %} + +一部の IdPs は、SCIM を介した {% data variables.product.prodname_dotcom %} Organization へのプロビジョニングアクセスをサポートしています。 詳しい情報については「[SCIMについて](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 + +### SAML SSO で 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)」を参照してください。 + +新しいユーザを、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について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### 参考リンク + +- [2要素認証とSAMLシングルサインオンについて](/articles/about-two-factor-authentication-and-saml-single-sign-on) +- [SAML シングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md new file mode 100644 index 0000000000..493271854e --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -0,0 +1,31 @@ +--- +title: SCIM について +intro: 'System for Cross-domain Identity Management (SCIM) を使うと、管理者はユーザの識別情報のシステム間での交換を自動化できます。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-scim + - /github/setting-up-and-managing-organizations-and-teams/about-scim +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +[SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) を Organization 内で使うと、Organization のメンバーの {% data variables.product.product_name %}へのアクセスの追加、管理、削除のための SCIM を実装できます。 たとえば、管理者は Organization のメンバーのデプロビジョニングに SCIM を使い、自動的にメンバーを Organization から削除できます。 + +SCIM を実装せずに SAML SSO を使った場合、自動のプロビジョニング解除は行われません。 Organization のメンバーのアクセスが ldP から削除された後、セッションの有効期限が切れても、そのメンバーは Organization から自動的には削除されません。 認証済みのトークンにより、セッションが期限切れになった後も Organization へのアクセスが許可されます。 アクセスを削除するには、Organization の管理者は手動で認証済みのトークンを Organization から削除するか、その削除を SCIM で自動化します。 + +Organization の {% data variables.product.product_name %} の SCIM API と連携できるアイデンティティプロバイダとして、以下のものがあります。 詳しい情報については{% data variables.product.product_name %}API ドキュメンテーション中の[SCIM](/rest/reference/scim) を参照してください。 +- Azure AD +- Okta +- OneLogin + +{% data reusables.scim.enterprise-account-scim %} 詳細については、「[Enterprise アカウント内の Organization のユーザプロビジョニングについて](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)」を参照してください。 + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) +- [アイデンティティプロバイダの Organization への接続](/articles/connecting-your-identity-provider-to-your-organization) +- [Organization での SAML シングルサインオンの有効化とテスト](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) +- [Organization へのメンバーの SAML アクセスの表示と管理](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000..7b9c63b4eb --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,31 @@ +--- +title: アイデンティティプロバイダが利用できない場合の Organization へのアクセス +intro: 'アイデンティティプロバイダが利用できない場合でも、Organization の管理者はシングルサインオンをバイパスし、リカバリコードを利用して {% data variables.product.product_name %}にサインインできます。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization の管理者は、シングルサインオンをバイパスするために、[ダウンロード済み、あるいは保存済みのリカバリコードのいずれか](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)を利用できます。 そうしたリカバリコードを、すでに [ LastPass](https://lastpass.com/)、[1Password](https://1password.com/)、[ Keeper](https://keepersecurity.com/) などのパスワードマネージャーに保存しているかもしれません。 + +{% note %} + +**メモ:** リカバリコードは一度しか使えず、順番に使わなければなりません。 リカバリコードにより、アクセスが 24 時間許可されます。 + +{% endnote %} + +1. シングルサインオンをバイパスするには、シングルサインオンダイアログの下部で、[**Use a recovery code**] をクリックします。 ![リカバリコードを入力するためのリンク](/assets/images/help/saml/saml_use_recovery_code.png) +2. [Recovery Code] フィールドにリカバリコードを入力します。 ![リカバリコードを入力するフィールド](/assets/images/help/saml/saml_recovery_code_entry.png) +3. [**Verify**] をクリックします。 ![リカバリコードを検証するボタン](/assets/images/help/saml/saml_verify_recovery_codes.png) + +一度使用したリカバリコードは二度と使用できないということを覚えておいてください。 リカバリコードは再利用できません。 + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000..681673e8cf --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,81 @@ +--- +title: Okta を使う SAML シングルサインオンおよび SCIM を設定する +intro: 'Okta を使う Security Assertion Markup Language (SAML) シングルサインオン (SSO) および System for Cross-domain Identity Management (SCIM) を使用すると、 {% data variables.product.prodname_dotcom %} で Organization へのアクセスを自動的に管理することができます。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta +product: '{% data reusables.gated-features.saml-sso %}' +permissions: Organization のオーナーは、Okta を使う Organization に SAML SSO および SCIM を設定できます。 +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Okta での SAML と SCIM について + +Organization がアイデンティティプロバイダ (IdP) である Okta を使う SAML SSO と SCIM を使用するように設定すれば、{% data variables.product.prodname_dotcom %} Organization や他の Web アプリケーションへのアクセスを、1 つの集中インターフェースから制御することができます。 + +SAML SSO は、リポジトリや Issue、プルリクエストといった Organization のリソースに対するアクセスを制御し、保護します。 SCIM は、Okta で変更を行ったとき、{% data variables.product.prodname_dotcom %} の Organization に対するメンバーのアクセスを自動的に追加、管理、削除します。 詳しい情報については、「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」と「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 + +SCIM を有効にすると、Okta で {% data variables.product.prodname_ghe_cloud %} アプリケーションを割り当てる任意のユーザが次のプロビジョニング機能を使えるようになります。 + +| 機能 | 説明 | +| ------------- | -------------------------------------------------------------------------------------------------------------------- | +| 新しいユーザのプッシュ | Okta でユーザを作成すると、{% data variables.product.prodname_dotcom %} Organization に参加するためのメールがユーザに届きます。 | +| ユーザ無効化のプッシュ | Okta でユーザを無効化すると、そのユーザは {% data variables.product.prodname_dotcom %} Organization から削除されます。 | +| プロフィール更新のプッシュ | Okta でユーザのプロフィールを更新すると、そのユーザの {% data variables.product.prodname_dotcom %} の Organization でのメンバーシップに関するメタデータが更新されます。 | +| ユーザの再アクティブ化 | Okta でユーザを再アクティブ化すると、{% data variables.product.prodname_dotcom %} の Organization に復帰するための招待メールがそのユーザに届きます。 | + +### 必要な環境 + +{% data reusables.saml.use-classic-ui %} + +### Okta で {% data variables.product.prodname_ghe_cloud %} アプリケーションを追加する + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +4. [Github Enterprise Cloud - Organization] の右で [**Add**] をクリックします。 ![{% data variables.product.prodname_ghe_cloud %} アプリケーションの [Add] をクリック](/assets/images/help/saml/okta-add-ghec-application.png) + +5. [**GitHub Organization**] フィールドに、{% data variables.product.prodname_dotcom %} の Organization 名を入力します。 たとえば、Organization の URL が https://github.com/octo-org の場合、Organization 名は `octo-org` となります。 ![GitHub の Organization 名を入力](/assets/images/help/saml/okta-github-organization-name.png) + +6. [**Done**] をクリックします。 + +### SAML SSO の有効化とテスト + +{% 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. SAML 2.0 の設定方法に関するガイドから、サインオン URL、発行者 URL、公開の証明書を使用して、{% data variables.product.prodname_dotcom %} での SAML SSO を有効化してテストします。 詳細は「[Organization での SAML シングルサインオンの有効化とテスト](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)」を参照してください。 + +### Okta で SCIM を使ってアクセスのプロビジョニングを設定する + +{% 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. [**Authenticate with Github Enterprise Cloud - Organization**] をクリックします。 ![Okta アプリケーションの [Authenticate with Github Enterprise Cloud - Organization] ボタン](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) + +7. Organization 名の右にある [**Grant**] をクリックします。 ![Organization にアクセスできるよう Okta SCIM インテグレーションを認証する [Grant] ボタン](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) + + {% note %} + + **注釈**: リストに自分の Organization が表示されていない場合は、ブラウザで `https://github.com/orgs/ORGANIZATION-NAME/sso` を開き、IdP での管理者アカウントを使用して SAML SSO 経由で Organization に認証してもらいます。 たとえば、Organization 名が `octo-org` の場合、URL は `https://github.com/orgs/octo-org/sso` となります。 詳しい情報については「[SAML シングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」を参照してください。 + + {% endnote %} +1. [**Authorize OktaOAN**] をクリックします。 ![Organization にアクセスできるよう Okta SCIM インテグレーションを認証する [Authorize OktaOAN] ボタン](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} + +### 参考リンク + +- [Okta を使用して Enterprise アカウントの SAML シングルサインオンおよび SCIM を設定する](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta) +- [Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta) +- Okta ドキュメントの「[Understanding SAML](https://developer.okta.com/docs/concepts/saml/)」 +- Okta ドキュメントの「[Understanding SCIM](https://developer.okta.com/docs/concepts/scim/)」 diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000..3ae1ddf703 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,34 @@ +--- +title: アイデンティティプロバイダを Organization に接続する +intro: 'SAML シングルサインオンおよび SCIM を使うには、あなたのアイデンティティプロバイダを、あなたの {% data variables.product.product_name %} Organization に接続する必要があります。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/connecting-your-identity-provider-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data variables.product.product_name %} Organization で [SAML SSO を有効化する](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)前に、アイデンティティプロバイダ (IdP) を Organization に接続する必要があります。 + +アイデンティティプロバイダに関する SAML および SCIM の詳細については、以下のドキュメンテーションで確認できます: +- Active Directory フェデレーションサービス (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) および [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) および [SCIM](http://developer.okta.com/standards/SCIM/) +- OneLogin: [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) および [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 %} + +**メモ:** {% data variables.product.product_name %} がサポートする SCIM アイデンティティプロバイダは Azure AD、Okta、OneLogin です。 SCIM に関する詳細は「[SCIM について](/articles/about-scim)」を参照してください。 + +{% endnote %} + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) +- [Organization 用の SAML シングルサインオンの強制](/articles/enforcing-saml-single-sign-on-for-your-organization) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000..316e92d632 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,36 @@ +--- +title: Organization の SAML シングルサインオンのリカバリコードをダウンロードする +intro: 'Organization のアイデンティティプロバイダを利用できない場合でも変わりなく {% data variables.product.product_name %} にアクセスできるよう、Organization の管理者は Organization 用に SAML シングルサインオンのリカバリコードをダウンロードする必要があります。' +redirect_from: + - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes + - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes + - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +リカバリコードは共有や配布しないでください。 [LastPass](https://lastpass.com/)、[1Password](https://1password.com/)、[Keeper](https://keepersecurity.com/) などのパスワードマネージャで保存することをおすすめします。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. [SAML single sign-on] の下にあるリカバリコードに関する注意書きの [**Save your recovery codes**] をクリックします。 ![リカバリコードを表示し保存するリンク](/assets/images/help/saml/saml_recovery_codes.png) +6. [**Download**]、[**Print**]、または [**Copy**] をクリックしてリカバリコードを保存します。 ![リカバリコードをダウンロード、印刷、コピーするボタン](/assets/images/help/saml/saml_recovery_code_options.png) + + {% note %} + + **メモ:** リカバリコードがあれば IdP を使用できないときに {% data variables.product.product_name %}に戻れます。 新しいリカバリコードを生成すると、「シングルサインオンのリカバリコード」ページに表示されているリカバリコードは自動的に更新されます。 + + {% endnote %} + +7. リカバリコードを {% data variables.product.product_name %}へのアクセス回復のために一度使用すると、再利用はできません。 {% data variables.product.product_name %} へのアクセスは、シングルサインオンを使用してサインインするか聞かれるまでの 24 時間だけ有効です。 + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) +- 「[アイデンティティプロバイダが利用できない場合の Organization へのアクセス](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)」 diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..ab7e17acf1 --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,51 @@ +--- +title: Organization 向けの SAML シングルサインオンを有効化してテストする +intro: Organization のオーナーと管理者は、SAML シングルサインオンを有効にして、Organization のセキュリティを強化できます。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +すべてのメンバーに使用するように強制する必要なく、Organization 内で SAML SSO を有効化できます。 SAML SSO を Organization 内で強制せずに有効化することで、Organization での SAML SSO の導入がスムーズになります。 Organization 内の大半のメンバーが SAML SSO を使用するようになったら、Organization 内で強制化できます。 + +SAML SSO を有効化しても強制はしない場合、SAML SSO を使用しないメンバーは、引き続き Organization のメンバーであり続けます。 SAML SSO の強制化の詳細については、「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。 + +{% data reusables.saml.outside-collaborators-exemption %} + +Organization で SAML SSO を強制する前に、アイデンティティプロバイダ (IdP) を設定しておいてください。 詳細は「[Organization での SAML シングルサインオンの施行を準備する](/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. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択します。 ![SAML SSO を有効化するためのチェックボックス](/assets/images/help/saml/saml_enable.png) + + {% note %} + + **メモ:** SAML SSO の有効化後、シングルサインオンのリカバリコードをダウンロードして、IdP が使用できなくなった場合にも Organization にアクセスできるようにできます。 詳細は「[Organization の SAML シングルサインオンのリカバリコードをダウンロード](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)」を参照してください。 + + {% endnote %} + +6. [Sign on URL] フィールドにシングルサインオンのリクエスト用の IdP の HTTPS エンドポイントを入力します。 この値は Idp の設定で使用できます。 ![メンバーがサインインする際にリダイレクトされる URL のフィールド](/assets/images/help/saml/saml_sign_on_url.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. {% octicon "pencil" aria-label="The edit icon" %} をクリックして、[Signature Method] および [Digest Method] ドロップダウンで、SAML 発行者がリクエストの整合性を検証するために使用するハッシュアルゴリズムを選択します。 ![SAML 発行者が使用する署名方式とダイジェスト方式のハッシュアルゴリズム用のドロップダウン](/assets/images/help/saml/saml_hashing_method.png) +10. Organization で SAML SSO を有効化する前に、[ **Test SAML configuration**] をクリックして、入力した情報が正しいことを確認します。 ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_test.png) + + {% tip %} + + **ヒント:** {% data reusables.saml.testing-saml-sso %} + + {% endtip %} +11. SAML SSO を強制して、IdP 経由で認証をされていないすべての Organization メンバーを削除するには、[**Require SAML SSO authentication for all members of the _Organization 名_ organization**] を選択します。 SAML SSO の強制化の詳細については、「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。 ![Organization 向けに SAML SSO を強制するためのチェックボックス ](/assets/images/help/saml/saml_require_saml_sso.png) +12. [**Save**] をクリックします。 ![SAML SSO 設定を保存するためのボタン](/assets/images/help/saml/saml_save.png) + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..b308a58bde --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Organization で SAML シングルサインオンを施行する +intro: Organization のオーナーと管理者は、SAML SSO を施行して Organization のすべてのメンバーがアイデンティティプロバイダを介して認証する必要があるようにできます。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enforcing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization で SAML SSO を施行すると、SAML アイデンティティプロバイダ (IdP) を介して認証していないすべてのメンバーは、管理者も含め、Organization から削除され、削除について知らせるメールが届きます。 Organization の IdP で 外部アイデンティティを設定していないボットとサービスアカウントも削除されます。 ボットとサービスアカウントの詳細については、「[SAML シングルサインオンでボットおよびサービスアカウントを管理する](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)」を参照してください。 Organization のメンバーが正常にシングルサインオンを完了すると、メンバーを復元できます。 + +Organization が、Enterprise アカウントによって所有されている場合、Enterprise アカウントに SAML を有効化すると、Organization レベルの SAML 設定がオーバーライドされます。 詳細は、「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)」を参照してください。 + +{% tip %} + +**ヒント:** {% data reusables.saml.testing-saml-sso %} + +{% endtip %} + +1. Organization で SAML SSO を有効化およびテストします。 この処理の詳細については、「[Organization での SAML シングルサインオンの有効化とテスト](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)」を参照してください。 +2. [**Require SAML SSO authentication for all members of the SAML SSO Org organization**] を選択した後、IdP を介して認証をしていない Organization のメンバーが表示されます。 SAML SSO を施行すると、これらのメンバーは Organization から削除されます。 +3. [**Enforce SAML SSO**] をクリックして SAML SSO を施行して、リストされた Organization のメンバーを削除します。 + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md new file mode 100644 index 0000000000..5d667f997d --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -0,0 +1,24 @@ +--- +title: Organization で SAML シングルサインオンを管理する +intro: Organization の管理者は、メンバーの ID と、SAML シングルサインオン (SSO) による Organization へのアクセスを管理できます。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000..b13b0ceedb --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,79 @@ +--- +title: Organization の Team 同期を管理する +intro: '{% data variables.product.product_name %} 上のアイデンティティプロバイダ (IdP) と Organization の間で Team の同期の有効/無効を切り替えることができます。' +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization +permissions: Organization のオーナーは、Organization の Team 同期を管理できます。 +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Team の同期について + +IdP と {% data variables.product.product_name %} の間で Team の同期を有効化すると、Organization のオーナーとチームメンテナが Organization の Team を 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 %} + +Enterprise アカウントが所有する Organization に対して Team の同期を有効化することもできます。 詳細は、「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)」を参照してください。 + +### Team の同期を有効化する + +Team の同期を有効化する手順は、使用する IdP によって異なります。 各 IdP によって、Team の同期を有効化するうえで必要な環境があります。 個々の IdP ごとに、さらに必要な環境があります。 + +#### 必要な環境 + +{% data reusables.identity-and-permissions.team-sync-required-permissions %} + +Organization と、サポートされている IdP について、SAMLシングルサインオンを有効にする必要があります。 詳細は「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。 + +SAML SSO とサポートされる IdP を使用してOrganization に認証される必要があります。 詳しい情報については「[SAMLシングルサインオンで認証する](/articles/authenticating-with-saml-single-sign-on)」を参照してください。 + +#### Azure AD で Team の同期を有効化する + +{% 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. Organization に接続したいアイデンティティプロバイダのテナント情報を確認してから、[**Approve**] をクリックします。 ![特定の IdP テナントに対して、Team の同期を有効化するペンディングリクエストと、リクエストを承認またはキャンセルするオプション](/assets/images/help/teams/approve-team-synchronization.png) + +#### Okta で Team の同期を有効化する + +{% 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. Organization 名の下で、有効な SSWS トークンと Okta インスタンスの URL を入力します。 ![Okta Organization で Team の同期を有効化するフォーム](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) +6. Organization に接続したいアイデンティティプロバイダのテナント情報を確認してから、[**Create**] をクリックします。 ![Team の同期を有効化する [Create] ボタン](/assets/images/help/teams/confirm-team-synchronization-okta.png) + +### Team の同期を無効化する + +{% 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. [Team synchronization] の下にある [**Disable team synchronization**] をクリックします。 ![Team の同期を無効化する](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000..1d0620ce8b --- /dev/null +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Organization での SAML シングルサインオンの強制を準備する +intro: 'Organization で SAML シングルサインオンを強制する前に、Organization のメンバーシップを検証し、アイデンティティプロバイダへの接続文字列を設定する必要があります。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization で [SAML シングルサインオンを強制](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)すると、アイデンティティプロバイダ (IdP) を介して認証していないメンバーは Organization から削除され、削除について知らせるメールが届きます。 + +Organization で SAML SSO を強制する前に、次の準備が必要です: + +- 必要な場合は、Organization でメンバーを[追加](/articles/inviting-users-to-join-your-organization)または[削除](/articles/removing-a-member-from-your-organization)します。 +- まだ接続していない場合は、IdP を Organization に接続します。 詳細は「[アイデンティティプロバイダを Organization に接続する](/articles/connecting-your-identity-provider-to-your-organization)」を参照してください。 +- Organization のメンバーがサインインし、アカウントを IdP にリンクしていることを確認します。 + +{% data reusables.saml.outside-collaborators-exemption %} + +### 参考リンク + +- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on) diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..9a4e1e8289 --- /dev/null +++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,32 @@ +--- +title: 管理者 Team を改善された Organization の権限に移行する +intro: '2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された権限モデルに移行する必要があるかもしれません。 レガシーの管理者 Team は、改善された Organization 権限モデルに移行するまで、リポジトリの作成資格を自動的に維持します。' +redirect_from: + - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ + - /articles/converting-an-admin-team-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +レガシーの管理者 Team メンバーのために新しい Team を作成することで、レガシーの管理者 Team が持つリポジトリ作成の資格を削除できます。Team が Organization のリポジトリに対して必要なアクセスを持っていることを確認してから、レガシーの管理者 Teamを削除してください。 + +詳しい情報については、「[Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization)」を参照してください。 + +{% warning %} + +**警告:** +- レガシーの管理者 Team のメンバーが、他の Team のメンバーではない場合、そのメンバーは Team を削除すると Organization から削除されます。 Team を削除する前に、メンバーを Organization の直接メンバーにするか、必要なリポジトリに対するコラボレーターアクセスを持たせてください。 +- レガシーの管理者 Team メンバーが作成したプライベートフォークを失わないために、レガシーの管理者 Teamを削除する前に、以下のステップ 1 - 3 に従う必要があります。 +- Organization のメンバーにとって "admin" は、Organization の特定の[リポジトリに対する特定のアクセス](/articles/repository-permission-levels-for-an-organization)を示します。ですから、これを Team 名として使うことは避けるようおすすめします。 + +{% endwarning %} + +1. [新しい Team を作成](/articles/creating-a-team)します。 +2. 新しい Team に、レガシーの管理者 Team の[各メンバーを追加](/articles/adding-organization-members-to-a-team)します。 +3. レガシーの管理者 Team がアクセスしていた各リポジトリについて、 [新しい Team に同等のアクセスを与えます](/articles/managing-team-access-to-an-organization-repository)。 +4. [レガシーの管理者 Team を削除](/articles/deleting-a-team)します。 diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..3ad3dc26e8 --- /dev/null +++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,52 @@ +--- +title: オーナー Team を改善された Organization の権限に移行する +intro: '2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された権限モデルに移行する必要があるかもしれません。 「オーナー」は、Organization の各メンバーに与えられる管理者ロールとなりました。 レガシーのオーナー Team のメンバーには、オーナー権限が自動的に与えられます。' +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +レガシーのオーナー Team を変換する方法はいくつかあります: + +- Team に、メンバーが Organization 内で特別なステータスを持っていることを示す名前を付ける。 +- すべてのメンバーが、Organization のリポジトリにアクセスできる必要な権限を持つ Team に追加されていることを確認してから、元の Team を削除する。 + +### オーナー Team に新しい名前を付ける + +{% tip %} + + **メモ:** Organization のメンバーにとって "admin" は、Organization の特定の[リポジトリに対する特定のアクセス](/articles/repository-permission-levels-for-an-organization) を示します。ですから、これを Team 名として使うことは避けるようおすすめします。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. Team 名のフィールドで、オーナー Team の新しい名前を選びます。 例: + - Organization において、オーナー Team のメンバーがとても少ない場合には、"Core" といったチーム名がいいかもしれません。 + - Organization のすべてのメンバーがオーナー Team のメンバーでもあり、[Team に @mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) できる場合は、"Employees" といったチーム名がいいかもしれません。 ![オーナー Team の名前を "Core" にした、Team 名フィールド](/assets/images/help/teams/owners-team-new-name.png) +6. Team の説明の下にある、[**Save and continue**] をクリックします。 ![[Save and continue] ボタン](/assets/images/help/teams/owners-team-save-and-continue.png) +7. また、代わりに [Team を*パブリック*にする](/articles/changing-team-visibility)こともできます。 + +### レガシーのオーナー Team の削除 + +{% warning %} + +**警告:** オーナー Team のメンバーが、他の Team のメンバーではない場合、そのメンバーは Team を削除すると Organization から削除されます。 Team を削除する前に、メンバーを Organization の直接メンバーにするか、必要なリポジトリに対するコラボレーターアクセスを持たせてください。 + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. ページの下部にある警告を確認し、[**Delete the Owners team**] をクリックします。 ![オーナー Team を削除するリンク](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md new file mode 100644 index 0000000000..022a3d277c --- /dev/null +++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md @@ -0,0 +1,20 @@ +--- +title: 改善された Organization の権限に移行する +intro: '2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された Organization の権限モデルに移行する必要があるかもしれません。' +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000..0095c781d4 --- /dev/null +++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,44 @@ +--- +title: 管理者 Team を改善された Organization の権限に移行する +intro: '2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された権限モデルに移行する必要があるかもしれません。 レガシーの管理者 Team は、改善された Organization 権限モデルに移行するまで、リポジトリの作成資格を自動的に維持します。' +redirect_from: + - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ + - /articles/migrating-admin-teams-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +デフォルトでは、Organization のすべてのメンバーがリポジトリを作成できます。 [リポジトリ作成権限](/articles/restricting-repository-creation-in-your-organization) を Organization のオーナーに制限しており、Organization がレガシーの Organization の権限構造で作成されていた場合、レガシーの管理者 Team のメンバーも引き続きリポジトリを作成できます。 + +レガシーの管理者 Team とは、レガシーの Organization の権限構造で、管理者権限レベルを使用して作成された Team のことです。 この Team のメンバーは、Organization のリポジトリを作成できました。改善された Organization 権限構造でも、その機能は維持されています。 + +レガシーの 管理者 Team を改善された Organization の権限に移行すれば、この機能をなくすことができます。 + +詳細は「[Organization のためのリポジトリの権限レベル](/articles/repository-permission-levels-for-an-organization)」を参照してください。 + +{% warning %} + +**警告:** Organization ですべてのメンバーに対して[リポジトリ作成権限](/articles/restricting-repository-creation-in-your-organization)を無効にされている場合は、レガシーの管理者 Team のメンバーの一部がリポジトリ作成権限を失うことがあります。 Organization でメンバーよるリポジトリ作成を有効にしている場合は、レガシーの管理者 Team を改善された Organization の権限に移行しても、チームメンバーのリポジトリ作成機能は影響されません。 + +{% endwarning %} + +### Organization のレガシーの管理者 Team をすべて移行する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +1. Organization のレガシーの管理者 Team をレビューし、[**Migrate all teams**] をクリックします。 ![[Migrate all teams] ボタン](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) +1. 移行するチームのメンバーについて起きうる変化についての情報を読んだら、[**Migrate all teams**] をクリックします。 ![移行を確定するボタン](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) + +### 1 つの管理者 Team を移行する + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +1. チーム説明のボックスで、[**Migrate team**] をクリックします。 ![[Migrate team] ボタン](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md new file mode 100644 index 0000000000..6bc0e2bbf8 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md @@ -0,0 +1,79 @@ +--- +title: Team について +intro: Team は、Organization のメンバーによって構成されるグループであり、カスケードになったアクセス権限とメンションを伴う会社やグループの構造を反映します。 +redirect_from: + - /articles/about-teams + - /github/setting-up-and-managing-organizations-and-teams/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +![Organization 内の Team のリスト](/assets/images/help/teams/org-list-of-teams.png) + +Organization のオーナーとチームメンテナは、Team に対して、Organization のリポジトリへの管理、読み取り、書き込みアクセスを与えることができます。 Organization のメンバーは、Team 名をメンションすることで、Team 全体に通知を送ることができます。 Organization のメンバーは、Team からのレビューをリクエストすることによっても、Team 全体に通知を送ることができます。 Organization のメンバーは、プルリクエストがオープンされたリポジトリへの読み取りアクセスを持つ特定の Team からのレビューをリクエストできます。 コードの特定の種類や領域に対して Team をオーナーとして CODEOWNERS ファイルで指定できます。 + +詳しい情報については、以下を参照してください。 +- [OrganizationのリポジトリへのTeamのアクセスの管理](/articles/managing-team-access-to-an-organization-repository) +- 「[人や Team のメンション](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)」 +- 「[コードオーナー'について](/articles/about-code-owners/)」 + +![Team のメンションの画像](/assets/images/help/teams/team-mention.png) + +{% if enterpriseServerVersions contains currentVersion %} + +また、LDAP Sync を使って {% data variables.product.product_location %}の Team メンバーと Team ロールを、既成の LDAP グループと同期させることができます。 そうすることで、{% data variables.product.product_location %}内で手動で行う代わりに、LDAP サーバーのユーザのロールベースアクセス制御を確立できます。 詳しい情報については[LDAP Syncの有効化](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)を参照してください。 + +{% endif %} + +{% data reusables.organizations.team-synchronization %} + +### Team の可視性 + +{% data reusables.organizations.types-of-team-visibility %} + +### Team のページ + +各 Team は、Organization 内に独自のページを持ちます。 Team のページでは、Team メンバー、子チーム、Team のリポジトリを見ることができます。 Organization のオーナーとチームメンテナは、Team のページから Team の設定にアクセスし、Team の説明とプロフィール画像を更新できます。 + +Organization のメンバーは、Team 内のディスカッションを作成し、参加できます。 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)を参照してください。 + +![メンバーとディスカッションのリストがある Team ページ](/assets/images/help/organizations/team-page-discussions-tab.png) + +### 入れ子チーム + +{% data variables.product.product_name %}の Organization では、複数レベルの入れ子チームでグループや会社の階層を反映させることができます。 親チームは複数の子チームを持つことができます。それぞれの子チームが持つことができる親チームは 1 つだけです。 シークレットチームを入れ子にすることはできません。 + +子チームは親のアクセス権限を引き継ぐので、大きなグループでの権限管理がシンプルになります。 子チームのメンバーは、親チームが@メンションされた場合にも通知を受けるので、複数グループの人々のコミュニケーションがシンプルになります。 + +たとえば Team の構造が「従業員 > エンジニアリング > アプリケーションエンジニアリング > アイデンティティ」となっているなら、エンジニアリングにリポジトリへの書き込みアクセスを許可すれば、アプリケーションエンジニアとアイデンティティもそのアクセス権を得ることになります。 アイデンティティ Team あるいは Organization の階層の最下位にある Team に @メンションした場合、それらのチームだけが通知を受けることになります。 + +![親チームと子チームがある Team のページ](/assets/images/help/teams/nested-teams-eng-example.png) + +親チームの権限とメンションを誰が共有するのかを簡単に知るには、親チームのページの [Members] タブで親チームの子チームのすべてのメンバーを見ることができます。 子チームのメンバーは、親チームの直接のメンバーではありません。 + +![子チームの全メンバーがある親チームのページ](/assets/images/help/teams/team-and-subteam-members.png) + +Team を作るときには親を選択できます。あるいは、作成済みの Team を Organization の階層の中で移動させることもできます。 詳しい情報については[Organization 階層内での Team の移動](/articles/moving-a-team-in-your-organization-s-hierarchy)を参照してください。 + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +### Organization 内で Team を入れ子にする準備 + +Organization がすでに既存の Team を持っている場合、その Team の上あるいは下に Team を入れ子にする前に、各 Team のリポジトリのアクセス権限を監査しておくべきです。 また、Organization に実装したい新しい構造についても考慮しておくべきです。 + +Team 階層の最上位では、親チームとその子チームのすべてのメンバーにとって安全なアクセス権限を、親チームのリポジトリに与えるべきです。 階層を下っていくにつれて、より注意が必要なリポジトリへの、より細かいアクセスを、子チームに許可していくことができます。 + +1. 既存の Team からすべてのメンバーを削除する +2. 各 Team のリポジトリのアクセス権限を監査して調整し、各 Team に親を与える +3. 必要な新しい Team を作成し、それぞれの新 Team の親を選択し、それらにリポジトリのアクセス権を与える +4. Team に直接人を追加する + +### 参考リンク + +- [Team の作成](/articles/creating-a-team) +- [Team へのOrganization メンバーの追加](/articles/adding-organization-members-to-a-team) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000..732ef8cc25 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,32 @@ +--- +title: Team への Organization メンバーの追加 +intro: 'オーナーあるいはチームメンテナ権限を持っている人は、Organization のメンバーを Team に加えることができます。 オーナー権限を持っている人は、{% if currentVersion == "free-pro-team@latest" %}メンバーではない人を Team および Organization に参加するよう招待{% else %}メンバーではない人を Team および Organization に追加{% endif %}することもできます。' +redirect_from: + - /articles/adding-organization-members-to-a-team-early-access-program/ + - /articles/adding-organization-members-to-a-team + - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. Team メンバーのリストの上部で、[**Add a member**] をクリックします。 ![[Add member] ボタン](/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 %} + +### 参考リンク + +- [Team について](/articles/about-teams) +- [OrganizationのリポジトリへのTeamのアクセスの管理](/articles/managing-team-access-to-an-organization-repository) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/changing-team-visibility.md new file mode 100644 index 0000000000..33d2fcdf0e --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/changing-team-visibility.md @@ -0,0 +1,29 @@ +--- +title: Team の可視性の変更 +intro: チームメンテナーおよび Organization オーナーは、Team を *表示する* か *シークレットにする* かを決定できます。 +redirect_from: + - /articles/changing-team-visibility + - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.types-of-team-visibility %} + +{% tip %} + +**ヒント:** Team に[子または親チーム](/articles/about-teams)がある場合は、シークレットチームにできません。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +3. 可視性を変更したいチームを選択します。 ![2 つの Team を選択した状態の Team リスト](/assets/images/help/teams/list-of-teams-selected.png) +4. Team 一覧の上にあるドロップダウンメニューで [**Change visibility**] をクリックします。 ![Team の可視性を変更するオプションのあるドロップダウンメニュー](/assets/images/help/teams/team-bulk-management-options.png) +5. 選択した Team を可視にするかシークレットにするか選び、[**Change visibility**] をクリックします。 ![チームを表示するまたはシークレットにするラジオボタンと、[Change visibility] ボタン](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md new file mode 100644 index 0000000000..842093d21e --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -0,0 +1,38 @@ +--- +title: Team の作成 +intro: 独立 Team や入れ子 Team を作成してリポジトリの権限およびグループへのメンションを管理できます。 +redirect_from: + - /articles/creating-a-team-early-access-program/ + - /articles/creating-a-team + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization のオーナーと親チームのメンテナだけが親の下に新しく子チームを作成できます。 オーナーは Organization 内の全チームについて作成許可を制限することもできます。 詳細は「[Organization のチーム作成権限を設定する](/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. オプションとして、Organization またはEnterprise アカウントが Team 同期を使用している場合は、Team にアイデンティティプロバイダグループを接続するために、[Identity Provider Groups] ドロップダウンメニューから アイデンティティプロバイダグループを 5 つまで選択します。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 ![アイデンティティプロバイダグループを選択するドロップダウンメニュー](/assets/images/help/teams/choose-an-idp-group.png) +{% endif %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} +9. 任意で、[Team のアクセスを Organization リポジトリに与えます](/articles/managing-team-access-to-an-organization-repository)。 + +### 参考リンク + +- [Team について](/articles/about-teams) +- 「[Team の可視性を変更する](/articles/changing-team-visibility)」 +- "[Organization の階層内での Team の移動](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/deleting-a-team.md new file mode 100644 index 0000000000..f7e3e91d5b --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/deleting-a-team.md @@ -0,0 +1,27 @@ +--- +title: Team の削除 +intro: Organization のオーナーは Team の設定ページからいつでも Team を削除できます。 +redirect_from: + - /articles/deleting-a-team + - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**ヒント:** Organization オーナーだけが親チームを削除できます。 詳しい情報については[Team について](/articles/about-teams)を参照してください。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. 削除対象の Team を 1 つまたは複数選択します。 ![2 つの Team を選択した状態の Team リスト](/assets/images/help/teams/list-of-teams-selected.png) +5. Team のリストの上にあるドロップダウンメニューから [**Delete**] をクリックします。 ![Team の可視性を変更するオプションのあるドロップダウンメニュー](/assets/images/help/teams/team-bulk-management-options.png) +6. 削除対象に選択した 1 つまたは複数の Team を確認し、[**I understand, delete teams**] をクリックします。 ![削除対象の Team のリストと Team 削除ボタン](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000..9f29ccd0a7 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Organization の Team ディスカッションを無効にする +intro: Organization のオーナーは、Organization をまたぐ Team ディスカッションの無効化か有効化を選択できます。 +redirect_from: + - /articles/disabling-team-discussions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team-discussions-default %}Team ディスカッションに関する詳しい情報については「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照してください。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +5. [Team discussions] の下で、[**Enable team discussions for this organization**] の選択を解除します。 ![Organization の Team ディスカッションを有効化または無効化するチェックボックス](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) +6. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/index.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/index.md new file mode 100644 index 0000000000..a5c622b097 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/index.md @@ -0,0 +1,38 @@ +--- +title: メンバーを Team に編成する +intro: Organizationメンバーは、カスケードになったアクセス権限とメンションを伴う会社やグループの構造を反映する Team に編成することができます。 +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 + - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000..5fa7bdd798 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,51 @@ +--- +title: Team のコードレビューの割り当てを管理する +intro: コードレビューの割り当てには、Team のどのメンバーがプルリクエストのレビューをサブミットするかが明確に指定されます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +チームメンテナと Organization のオーナーは、コードレビューの割り当てを設定できます。 + +### コードレビューの割り当てについて + +コードレビューの割り当てを使用すると、Team がプルリクエストのレビューをリクエストされたときいつでも、その Team がレビュー担当者として削除され、指定した Team メンバーサブセットが Team のかわりに割り当てられます。 コードレビューの割り当てでは、Team がレビューをリクエストされたとき、Team の全体に通知するか、Team メンバーのサブセットのみに通知するかを決めることができます。 + +コードオーナーが自動的にレビューをリクエストされる場合、Team は引き続き削除され、個人に置き換えられます。 個別の承認は、保護されたブランチでのコードオーナーの承認要件を満たしません。 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。 + +### ルーティングアルゴリズム + +コードレビューの割り当てでは、2 つの可能なアルゴリズムのいずれかに基づいて、レビュー担当者が自動的に選択されて割り当てられます。 + +ラウンドロビンアルゴリズムは、現在未処理のレビューの数とは関係なく、Team のすべてのメンバー間で交互に、最も新しいレビューリクエストを誰が受け取ったかに基づいてレビュー担当者を選択します。 + +ロードバランスアルゴリズムは、各メンバーの最近のレビューリクエスト合計数に基づいてレビュー担当者を選択し、メンバーごとの未処理レビューの数を考慮します。 ロードバランスアルゴリズムは、各 Teamメンバーが 30 日間に等しい数のプルリクエストをレビューすることを保証しようとします。 + +### コードレビューの割り当ての設定 +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. 左サイドバーで [**Code review assignment**] をクリックします。 ![[Code review assignment] ボタン](/assets/images/help/teams/review-assignment-button.png) +6. [**Enable auto assignment**] を選択します。 ![[Code review assignment] ボタン](/assets/images/help/teams/review-assignment-enable.png) +7. [How many team members should be assigned to review?] でドロップダウンメニューを使用し、各プルリクエストに割り当てるレビュー担当者の数を選択します。 ![[Number of reviewers] ドロップダウン](/assets/images/help/teams/review-assignment-number.png) +8. [Routing algorithm] のドロップダウンメニューで、使用するアルゴリズムを選択します。 詳細は、「[ルーティングアルゴリズム](#routing-algorithms)」を参照してください。 ![[Routing algorithm] ドロップダウン](/assets/images/help/teams/review-assignment-algorithm.png) +9. オプションで、Team の特定メンバーを常にスキップする場合は、[**Never assign certain team members**] を選択します。 次に、スキップする 1 つ以上の Team メンバーを選択します。 ![[Never assign certain team members] チェックボックスとラジオボタン](/assets/images/help/teams/review-assignment-skip-members.png) +10. オプションで、プルレビューリクエストごとのコードレビュー割り当てによって選択された Teamメンバーのみに通知する場合は、[Notifications] で[**If assigning team members, don't notify the entire team.**] を選択します。 ![コードレビューの割当ての通知](/assets/images/help/teams/review-assignment-notifications.png) +11. [**Save changes**] をクリックします。 + +### コードレビューの割り当てを無効化する +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. [**Enable auto assignment**] を選択してチェックマークを外します。 ![[Code review assignment] ボタン](/assets/images/help/teams/review-assignment-enable.png) +6. [**Save changes**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000..6bb09f9cc4 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,69 @@ +--- +title: Team のスケジュールされたリマインダーを管理する +intro: Team に対してレビュー待ちのプルリクエストがあるとき、Slack でリマインダーを受け取ることができます。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Team のスケジュールされたリマインダーについて + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +チームメンテナと Organization のオーナーは、Team がレビューをリクエストされたプルリクエストのスケジュールされたリマインダーを設定できます。 Team のスケジュールされたリマインダーを作成するには、Organization のオーナーが Slack ワークスペースを承認する必要があります。 詳しい情報については、「[Organization にスケジュールされたリマインダーを管理する](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)」を参照してください。 + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Team のスケジュールされたリマインダーを作成する +{% 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 %} +![[Scheduled reminders] ボタン](/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 %} + +### Team のスケジュールされたリマインダーを管理する +{% 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 %} +![[Scheduled reminders] ボタン](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Team のスケジュールされたリマインダーを削除する +{% 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 %} +![[Scheduled reminders] ボタン](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.delete %} + +### 参考リンク + +- [Organization にスケジュールされたリマインダーを管理する](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization) +- [スケジュールされたリマインダーの管理](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000..922c171b99 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,42 @@ +--- +title: Organization 階層内で Team を移動する +intro: 'チームメンテナと Organization のオーナーは、親チームの下に Team を入れ子にしたり、ネストした入れ子チームの親を変更または削除したりすることができます。' +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 + - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization のオーナーは、Team の親を変更できます。 チームメンテナは、子チームと親チーム両方のメンテナであれば、Team の親を変更できます。 子チームでのメンテナ権限を持たないチームメンテナは、親または子チームの追加をリクエストできます。 詳細は「[親チームの追加または変更をリクエストする](/articles/requesting-to-add-or-change-a-parent-team)」および「[子チームの追加をリクエストする](/articles/requesting-to-add-a-child-team)」を参照してください。 + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% tip %} + +**参考:** +- Team の親をシークレットチームに変更することはできません。 詳しい情報については[Team について](/articles/about-teams)を参照してください。 +- 親チームをその子チームの下位に入れ子にすることはできません。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Team のリストで、親を変更する Team の名前をクリックします。 ![Organization の Team のリスト](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. ドロップダウンメニューを使って親チームを選択するか、既存の親を削除して [**Clear selected value**] を選択します。 ![Organization の Team がリストされるドロップダウンメニュー](/assets/images/help/teams/choose-parent-team.png) +7. [**Update**] をクリックします。 +{% data reusables.repositories.changed-repository-access-permissions %} +9. [**Confirm new parent team**] をクリックします。 ![リポジトリアクセス権の変更に関する情報のモーダルボックス](/assets/images/help/teams/confirm-new-parent-team.png) + +### 参考リンク + +- [Team について](/articles/about-teams) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000..640013cc3c --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,23 @@ +--- +title: Team から Organization メンバーを削除する +intro: '*owner* 権限または *team maintainer* 権限が付与されている個人は、Team メンバーを Team から削除することができます。 これは、個人が Team から付与されるリポジトリへのアクセスを必要としなくなった場合や、個人が Team のプロジェクトでフォーカスされなくなった場合に必要となる可能性があります。' +redirect_from: + - /articles/removing-organization-members-from-a-team-early-access-program/ + - /articles/removing-organization-members-from-a-team + - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. 削除する個人を選択します。 ![Organization メンバーの横のチェックボックス](/assets/images/help/teams/team-member-check-box.png) +5. Team メンバーのリストの上のドロップダウンメニューで、[**Remove from team**] をクリックします。 ![ロールを変更するオプションのあるドロップダウンメニュー](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/renaming-a-team.md new file mode 100644 index 0000000000..d10f955669 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/renaming-a-team.md @@ -0,0 +1,21 @@ +--- +title: Team の名前の変更 +intro: チームメンテナおよび Organization オーナーは、Team の名前と説明を編集することができます。 +redirect_from: + - /articles/renaming-a-team + - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Team の新しい名前または説明を入力します。 ![Team の名前と説明のフィールド](/assets/images/help/teams/team-name-description.png) +6. [**Update**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000..fd1f68e83a --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,36 @@ +--- +title: 子チームの追加をリクエストする +intro: 'あなたがある Team でメンテナーの権限を有している場合は、Organization の階層内で既存の Team を自分の Team の下にネストするようリクエストできます。' +redirect_from: + - /articles/requesting-to-add-a-child-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +ある Team を子として追加するようにリクエストすると、その子チームのメンテナーにリクエストが送信されます。 子チームのメンテナーがリクエストを受諾すると、その子チームは Organization の階層内で親チームの下にネストされます。 + +あなたが Organization のオーナーである場合、または子チームと親チームの両方でチームメンテナー権限を所有している場合は、リクエストなしで子チームを追加したり、子チームの設定ページから子チームの親を変更したりできます。 詳細については、「[Organization の階層内で Team を移動する](/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. Team のリストで、子チームを追加する先の Team の名前をクリックします。 ![Organization の Team のリスト](/assets/images/help/teams/click-team-name.png) +5. Team ページの上部で、{% octicon "people" aria-label="The people icon" %} [**Teams**] をクリックします。 ![Team ページでの [Teams] タブ](/assets/images/help/teams/team-teams-tab.png) +6. [**Add a team**] をクリックします。 ![Team ページでの [Add a team] ボタン](/assets/images/help/teams/add-a-team.png) +7. 子チームとして追加する Team の名前を入力し、ドロップダウン リストからそれを選択します。 ![入力するテキストボックスと、子チームの名前を選択するドロップダウンメニュー](/assets/images/help/teams/type-child-team-name.png) +{% data reusables.repositories.changed-repository-access-permissions %} +9. [**Confirm changes**] をクリックして、子チームを追加するリクエストを送信します。 ![リポジトリアクセス権の変更に関する情報のモーダルボックス](/assets/images/help/teams/confirm-new-parent-team.png) + +### 参考リンク + +- [Team について](/articles/about-teams) +- 「[Organization の階層内で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy)」 +- 「[親チームの追加または変更をリクエストする](/articles/requesting-to-add-or-change-a-parent-team)」 diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000..4a8f2198f8 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,36 @@ +--- +title: 親チームの追加または変更をリクエストする +intro: 'ある Team でメンテナーの権限を所有している場合は、Organization の階層内で自分の Team を親チームの下にネストするようにリクエストできます。' +redirect_from: + - /articles/requesting-to-add-or-change-a-parent-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +自分の Team の親を追加または変更するようにリクエストすると、その親チームのメンテナーにリクエストが送信されます。 新しい親チームのメンテナーがリクエストを承認すると、自分の Team は Organization の階層内で親チームの下に子チームとしてネストされます。 + +Organization のオーナーである場合、または子チームと親チームでチームメンテナー権限を所有している場合は、承認をリクエストせずに親チームを追加したり、Team の設定ページから Team の親を変更したりできます。 詳細については、「[Organization の階層内で Team を移動する](/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. Team のリストで、親の下にネストする Team の名前をクリックします。 ![Organization の Team のリスト](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. [Parent team] で、[Select parent team] ドロップダウン メニューを使用して新しい親チームの名前をクリックします。 ![Organization の Team がリストされるドロップダウンメニュー](/assets/images/help/teams/choose-parent-team.png) +7. [**Save changes**] をクリックします。 +{% data reusables.repositories.changed-repository-access-permissions %} +9. [**Confirm changes**] をクリックして、 Team の親を追加または変更するための要求を送信します。 ![リポジトリアクセス権の変更に関する情報のモーダルボックス](/assets/images/help/teams/confirm-new-parent-team.png) + +### 参考リンク + +- [Team について](/articles/about-teams) +- 「[Organization の階層内で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy)」 +- 「[子チームの追加をリクエストする](/articles/requesting-to-add-a-child-team)」 diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000..89c7ffd6a0 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,24 @@ +--- +title: Team のプロフィール画像を設定する +intro: 'チームメンテナおよび Organization のオーナーは、Team で表示される Team のプロフィール画像を設定できます。' +redirect_from: + - /articles/setting-your-team-s-profile-picture + - /articles/setting-your-teams-profile-picture + - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Team のプロフィール画像を設定しない場合、Team プロフィール画像は Organization のプロフィール画像と同じになります。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. [**Upload new picture**] をクリックして、お好みのプロフィール画像を選択してください。 ![Upload new picture](/assets/images/help/teams/org-team-profile-picture-upload.png) +6. 必要に応じてクリック＆ドラッグで画像の縁を刈り込み、[**Set new team avatar**] をクリックします。 ![Set new team avatar](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000..da93e5f557 --- /dev/null +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,99 @@ +--- +title: Team をアイデンティティプロバイダグループと同期する +intro: '{% data variables.product.product_name %} Team をアイデンティティプロバイダ (IdP) グループと同期して、Team メンバーを自動的に追加あるいは削除することができます。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group +product: '{% data reusables.gated-features.team-synchronization %}' +permissions: 'Organization のオーナーとチームメンテナは、{% data variables.product.prodname_dotcom %} Team を IdP グループと同期することができます。' +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Team の同期について + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% if currentVersion == "free-pro-team@latest" %}最大 5 つの IdP グループを {% data variables.product.product_name %} チームに接続できます。{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_name %} の Team を 1 つの IdP グループに接続できます。 グループ内のすべてのユーザは自動的にチームに追加され、メンバーとして親 Organization にも追加されます。 グループを Team から切断すると、Team のメンバーシップを介して Organization のメンバーになったユーザは Organization から削除されます。{% endif %} IdP グループを複数の {% data variables.product.product_name %} Team に割り当てることができます。 + +{% if currentVersion == "free-pro-team@latest" %}Team 同期は、5000 以上のメンバーがいる IdP グループをサポートしていません。{% endif %} + +いったん {% data variables.product.prodname_dotcom %} Team が IdP グループに接続されたら、IdP 管理者はアイデンティティプロバイダを通して Team メンバーシップを変更する必要があります。 {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} または API を使用して Team のメンバーシップを管理することはできません{% endif %}。 + +{% if currentVersion == "free-pro-team@latest" %} +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)」を参照してください。 +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. {% data variables.product.prodname_dotcom %} Team または Organization のメンバーシップを変更するリクエストは、ユーザプロビジョニングの設定に使用されたアカウントによって行われた変更として監査ログに登録されます。 このアカウントに関する詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。 SCIM リクエストのスケジュールについて詳しくは、Microsoft Docs の「[ユーザプロビジョニングのステータスの確認](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)」を参照してください。 +{% endif %} + +親チームは IdP グループと同期できません。 IdP グループに接続したい Team が親チームの場合、新しい Team を作るか、Team と親チームのネスト関係を削除することをお勧めします。 詳細は、「[Team について](/articles/about-teams#nested-teams)」、「[Team の作成](/organizations/organizing-members-into-teams/creating-a-team)」、「[Organization 階層内で Team を移動する](/articles/moving-a-team-in-your-organizations-hierarchy)」を参照してください。 + +IdP グループに接続された Team を含めて {% data variables.product.prodname_dotcom %} Team のリポジトリに対するアクセスを管理するには、{% data variables.product.product_name %} で変更を行う必要があります。 詳細は「[Team について](/articles/about-teams)」および「[Organization リポジトリへの Team のアクセスを管理する](/articles/managing-team-access-to-an-organization-repository)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" %}API を使用して Team の同期を管理することもできます。 詳しい情報については、「[Team 同期](/rest/reference/teams#team-sync)」を参照してください。{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### 同期される Team のメンバーに関する要件 + +チームを IdP グループに接続した後、Team 同期により、次の場合にのみ IdP グループの各メンバーが {% data variables.product.product_name %} 上の対応するチームに追加されます。 +- そのユーザが {% data variables.product.product_name %} の Organization のメンバーの場合。 +- そのユーザがすでに {% data variables.product.product_name %} のユーザアカウントでログインしており、少なくとも 1 回は SAML シングルサインオンを介して Organization または Enterprise アカウントに認証されている場合。 +- そのユーザの SSO ID が IdP グループのメンバーである場合。 + +これらの条件を満たしていない既存の Team またはグループメンバーは、{% data variables.product.product_name %} の Team から自動的に削除され、リポジトリにアクセスできなくなります。 ユーザのリンクされた ID を取り消すと、IdP グループにマップされている Team からユーザが削除されます。 For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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)」と「[Enterprise アカウントで Organization 用に SAML シングルサインオンを有効にする](/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 アカウントで Organization の Team 同期を管理する](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)」参照してください。 + +{% endif %} + +### 必要な環境 + +{% if currentVersion == "free-pro-team@latest" %} +Before you can connect a {% data variables.product.product_name %} 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](/organizations/managing-saml-single-sign-on-for-your-organization/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 管理者にお問い合わせください。 + +SAML SSO を使って認証する必要があります。 詳しい情報については「[SAMLシングルサインオンで認証する](/articles/authenticating-with-saml-single-sign-on)」を参照してください。 + +{% elsif currentVersion == "github-ae@latest" %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). 詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。 + +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. 詳しい情報については、Microsoft Docs の「[GitHub AE への自動ユーザプロビジョニングを設定する](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae)」を参照してください。 +{% endif %} + +### IdP グループをTeam に接続する + +IdP グループを {% data variables.product.product_name %} Team に接続すると、グループ内のすべてのユーザが自動的に Team に追加されます。 {% if currentVersion == "github-ae@latest" %}親 Organization のメンバーになっていないユーザも Organization に追加されます。{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. [Identity Provider Groups] で、ドロップダウンメニューを使用して最大 5 つまでアイデンティティプロバイダグループを選択します。 ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. [Identity Provider Group] で、ドロップダウンメニューを使用してリストからアイデンティティプロバイダグループを選択します。 ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. [**Save changes**] をクリックします。 + +### IdP グループをTeam から切断する + +{% data variables.product.prodname_dotcom %} Team から IdP グループを切断すると、その IdP グループを介して {% data variables.product.prodname_dotcom %} Team に割り当てられている Team メンバーは Team から削除されます。 {% if currentVersion == "github-ae@latest" %} その Team 接続のためだけに親 Organization のメンバーであったユーザも、Organization から削除されます。{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. [Identity Provider Groups] で、切断したい IdP グループの右にある {% octicon "x" aria-label="X symbol" %} をクリックします。 ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. [Identity Provider Groups] で、切断したい IdP グループの右にある {% octicon "x" aria-label="X symbol" %} をクリックします。 ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. [**Save changes**] をクリックします。 diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000..876ff3637d --- /dev/null +++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -0,0 +1,60 @@ +--- +title: OAuthアプリケーションのアクセス制限について +intro: 'Organizationは、{% data variables.product.prodname_oauth_app %}のアクセス制限を有効化することによって、どの{% data variables.product.prodname_oauth_app %}がリポジトリやその他のリソースにアクセスできるかを選択できます。' +redirect_from: + - /articles/about-third-party-application-restrictions/ + - /articles/about-oauth-app-access-restrictions + - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data variables.product.prodname_oauth_app %}のアクセス制限が有効化されると、Organizationのメンバーは{% data variables.product.prodname_oauth_app %}のOrganizationのリソースへのアクセスを認可できなくなります。 Organizationのメンバーは、オーナーに対して使用したい{% data variables.product.prodname_oauth_app %}の認可をリクエストでき、Organizationのオーナーはペンディングになっているリクエストの通知を受信します。 + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% tip %} + +**Tip：**Organizationが{% data variables.product.prodname_oauth_app %}のアクセス制限をセットアップしていない場合、Organizationのメンバーが認可したすべての{% data variables.product.prodname_oauth_app %}は、Organizationのプライベートリソースにアクセスできます。 + +{% endtip %} + +### {% data variables.product.prodname_oauth_app %}のアクセス制限のセットアップ + +Organizationのオーナーが{% data variables.product.prodname_oauth_app %}のアクセス制限を初めてセットアップする場合、以下のようになります。 + +- **Organizationが所有するアプリケーション**には、自動的にOrganizationのリソースへのアクセスが与えられます。 +- **{% data variables.product.prodname_oauth_app %}**は、Organizationのリソースへのアクセスを即座に失います。 +- **2014年の2月以前に作成されたSSHキー**は、Organizationのリソースへのアクセスを即座に失います（これにはユーザ及びデプロイキーが含まれます）。 +- **{% data variables.product.prodname_oauth_app %}によって2014年の2月あるいはそれ以降に作成されたSSHキー**は、Organizationのリソースへのアクセスを即座に失います。 +- **プライベートのOrganizationリポジトリからのフックの配信**は、認可されていない{% data variables.product.prodname_oauth_app %}には送信されなくなります。 +- 認可されていない{% data variables.product.prodname_oauth_app %}からのプライベートなOrganizationのリソースへの**APIアクセス**はできなくなります。 加えて、パブリックなOrganizationリソースの作成、更新、削除のアクションの権限はありません。 +- **ユーザが作成したフック及び2014年の5月以前に作成されたフック**には影響ありません。 +- **Organizationが所有するリポジトリのプライベートフォーク**は、Organizationのアクセス制限に従います。 + +### SSHアクセスの失敗の解決 + +{% data variables.product.prodname_oauth_app %}のアクセス制限が有効化されたOrganizationへのアクセスを2014年2月以前に作成されたSSHキーが失った場合、それ以降のSSHアクセスの試行は失敗します。 ユーザには、キーを認可できる、あるいは信頼されたキーをそこにアップロードできるURLを示すエラーメッセージが返されます。 + +### webhook + +{% data variables.product.prodname_oauth_app %}が制限が有効化された後のOrganizationへのアクセスを許可された場合、その{% data variables.product.prodname_oauth_app %}が作成した既存のwebhookは、ディスパッチを再開します。 + +Organizationが以前に認可された{% data variables.product.prodname_oauth_app %}からアクセスを削除した場合、そのアプリケーションが作成した既存のwebhookはディスパッチされなくなります（それらのフックは無効化されますが、削除はされません）。 + +### アクセス制限の再有効化 + +Organizationが{% data variables.product.prodname_oauth_app %}のアクセスアプリケーション制限を無効化し、後に再び有効化した場合、以前に認可されていた{% data variables.product.prodname_oauth_app %}は自動的にOrganizationのリソースへのアクセスを許可されます。 + +### 参考リンク + +- [Organizationの{% data variables.product.prodname_oauth_app %}アクセス制限の有効化](/articles/enabling-oauth-app-access-restrictions-for-your-organization) +- [Organizationの{% data variables.product.prodname_oauth_app %}の承認](/articles/approving-oauth-apps-for-your-organization) +- [Organizationにインストールされたインテグレーションのレビュー](/articles/reviewing-your-organization-s-installed-integrations) +- [Organizationに以前に承認された{% data variables.product.prodname_oauth_app %}へのアクセスの拒否](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) +- [Organizationの{% data variables.product.prodname_oauth_app %}アクセス制限の無効化](/articles/disabling-oauth-app-access-restrictions-for-your-organization) +- 「[{% data variables.product.prodname_oauth_app %}に対する Organization の承認をリクエストする](/articles/requesting-organization-approval-for-oauth-apps)」 +- 「[{% data variables.product.prodname_oauth_app %} を認可する](/articles/authorizing-oauth-apps)」 diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000..3e399dcc6b --- /dev/null +++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Organization 用の OAuth アプリケーションの承認 +intro: '{% data variables.product.prodname_oauth_app %}による Organization のリソースへのアクセスを Organization のメンバーがリクエストしてきた場合、Organization のオーナーはそのリクエストを承認あるいは否認できます。' +redirect_from: + - /articles/approving-third-party-applications-for-your-organization/ + - /articles/approving-oauth-apps-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data variables.product.prodname_oauth_app %}のアクセス制限が有効化されている場合、Organization のメンバーは Organization のリソースへのアクセスを持つ {% data variables.product.prodname_oauth_app %}を承認する前に、Organization のオーナーからの[承認をリクエスト](/articles/requesting-organization-approval-for-oauth-apps)しなければなりません。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. 承認したいアプリケーションの隣で [**Review**] をクリックします。 ![レビューのリクエストリンク](/assets/images/help/settings/settings-third-party-approve-review.png) +6. リクエストされたアプリケーションに関する情報をレビューしたら、[**Grant access**] をクリックします。 ![アクセスの許可ボタン](/assets/images/help/settings/settings-third-party-approve-grant.png) + +### 参考リンク + +- [{% data variables.product.prodname_oauth_app %}のアクセス制限について](/articles/about-oauth-app-access-restrictions) diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000..5d58282fe0 --- /dev/null +++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,20 @@ +--- +title: 以前承認した OAuth App への Organization のアクセスを拒否する +intro: '以前承認した {% data variables.product.prodname_oauth_app %} を Organization が必要としなくなった場合、オーナーは Organization リソースへのアプリケーションのアクセスを削除できます。' +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 + - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. 無効化したいアプリケーションの隣にある {% octicon "pencil" aria-label="The edit icon" %} をクリックします。 ![編集アイコン](/assets/images/help/settings/settings-third-party-deny-edit.png) +6. [**Deny access**] をクリックします。 ![拒否の確定ボタン](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..34203000c0 --- /dev/null +++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Organization の OAuth App アクセス制限の無効化 +intro: 'Organization のオーナーは、Organization のリソースにアクセス権を持つ {% data variables.product.prodname_oauth_app %} の制限を無効化できます。' +redirect_from: + - /articles/disabling-third-party-application-restrictions-for-your-organization/ + - /articles/disabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% danger %} + +**警告**: Organization で {% data variables.product.prodname_oauth_app %} のアクセス制限を無効化すると、Organization のメンバーであれば誰でも、個人アカウント設定でアプリケーションの使用を承認していれば、自動的に {% data variables.product.prodname_oauth_app %} から Organization のプライベートリソースへのアクセスが認証されます。 + +{% enddanger %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. [**Remove restrictions**] をクリックします。 ![[Remove restrictions] ボタン](/assets/images/help/settings/settings-third-party-remove-restrictions.png) +6. サードパーティアプリケーション制限の無効化に関する情報を確認したら、[**Yes, remove application restrictions**] (はい、アプリケーション制限を削除します) をクリックします。 ![[Remove confirmation] ボタン](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..f3079c86cc --- /dev/null +++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Organization の OAuth App アクセス制限を有効化する +intro: 'Organization のオーナーは、{% data variables.product.prodname_oauth_app %} のアクセス制限を有効化して、信頼されていないアプリが Organization のリソースにアクセスするのを防止できます。その場合も Organization のメンバーは {% data variables.product.prodname_oauth_app %} を個人アカウントで使用できます。' +redirect_from: + - /articles/enabling-third-party-application-restrictions-for-your-organization/ + - /articles/enabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% warning %} + +**警告**: +- {% data variables.product.prodname_oauth_app %} のアクセス制限を有効化すると、Organization のアクセスでの以前に認証されたすべての {% data variables.product.prodname_oauth_app %} と SSH キーが取り消されます。 詳しい情報については、「[{% data variables.product.prodname_oauth_app %}のアクセス制限について](/articles/about-oauth-app-access-restrictions)」を参照してください。 +- {% data variables.product.prodname_oauth_app %} のアクセス制限を設定したら、Organization のプライベートなデータへのアクセスを必要とするすべての {% data variables.product.prodname_oauth_app %} を再認証してください。 Organization のすべてのメンバーは新しい SSH キーを作成する必要があり、Organization は必要に応じて新しいデプロイキーを作成する必要があります。 +- {% data variables.product.prodname_oauth_app %} のアクセス制限が有効化されると、アプリケーションで OAuth トークンを使用して {% 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. [Third-party application access policy] の下で [**Setup application access restrictions**] をクリックします。 ![制限の設定ボタン](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) +6. サードパーティのアクセス制限に関する情報を確認したら、[**Restrict third-party application access**] をクリックします。 ![制限の確認ボタン](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/index.md new file mode 100644 index 0000000000..dc566fb27f --- /dev/null +++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -0,0 +1,19 @@ +--- +title: Organization のデータへのアクセスを制限する +intro: '{% data variables.product.prodname_oauth_app %} のアクセス制限により、Organization のオーナーは、信頼できないアプリが Organization のデータにアクセスすることを制限できます。 これにより、Organization のメンバーは、Organization のデータを安全に保ちながら、個人のユーザー アカウントに対して {% data variables.product.prodname_oauth_app %} を使用できます。' +redirect_from: + - /articles/restricting-access-to-your-organization-s-data + - /articles/restricting-access-to-your-organizations-data + - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file 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 8f9a3f5c6d..edc83dfd2a 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 @@ -1,6 +1,6 @@ --- -title: Using GitHub Packages with GitHub Actions -intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.' +title: GitHub ActionsでのGitHub Packagesの利用 +intro: '{% data variables.product.prodname_actions %}でのワークフローを、自動的にパッケージを{% data variables.product.prodname_registry %}に公開もしくは{% 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 @@ -8,44 +8,87 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} +{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-self-hosted-runners-notice %} -### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} +### {% data variables.product.prodname_actions %}との{% data variables.product.prodname_registry %}について -{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} 詳しい情報については「[{% data variables.product.prodname_actions %}について](/github/automating-your-workflow-with-github-actions/about-github-actions)」を参照してください。 -You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. +ワークフローの一部としてパッケージの公開やインストールを行うことで、リポジトリのCI及びCDの機能を拡張できます。 {% if currentVersion == "free-pro-team@latest" %} -#### Authenticating to {% data variables.product.prodname_github_container_registry %} +#### {% data variables.product.prodname_github_container_registry %} への認証を行う {% data reusables.package_registry.container-registry-beta %} {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} -For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)." +認証の例については、「[{% data variables.product.prodname_container_registry %} で認証する](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)」を参照してください。 {% endif %} -#### Authenticating to package registries on {% data variables.product.prodname_dotcom %} +#### {% data variables.product.prodname_dotcom %} 上のパッケージレジストリを認証する -{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The `GITHUB_TOKEN` has `read:packages` and `write:packages` scopes to the current repository. For forks, the token also has the `read:packages` scope for the parent repository. +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} 上の {% data variables.product.prodname_container_registry %} 以外のパッケージレジストリにアクセスするためワークフローを {% data variables.product.prodname_registry %} に対して認証する場合、{% else %}{% data variables.product.product_name %} 上のパッケージレジストリに対して認証するには、{% endif %}認証のための個人アクセストークンではなく、{% data variables.product.prodname_actions %} を有効化した際に {% data variables.product.product_name %} がリポジトリに対して自動的に作成する `GITHUB_TOKEN` を使用することをお勧めします。 この`GITHUB_TOKEN`は、現在のリポジトリに対する`read:packages`及び`write:packages`スコープを持ちます。 フォークの場合、このトークンは親のリポジトリへの`read:packages`スコープも持ちます。 -You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." +{% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %}コンテキストを使って、ワークフロー中でこの`GITHUB_TOKEN`を参照できます。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。 -### Publishing a package using an action +### About permissions and package access for repository-owned packages -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 %}. +{% note %} + +**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`. + +{% endnote %} + +When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. このトークンの権限は、ワークフローを含むリポジトリに限定されます。 For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)." + +{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow. + +{% if currentVersion == "free-pro-team@latest" %} +### About permissions and package access for {% data variables.product.prodname_container_registry %} + +The {% data variables.product.prodname_container_registry %} (`ghcr.io`) allows users to create and administer containers as free-standing resources at the organization level. Containers can be owned by an organization or personal user account and you can customize access to each of your containers separately from repository permissions. + +All workflows accessing the {% data variables.product.prodname_container_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." + +### Default permissions and access settings for containers modified through workflows + +When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well. + +For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then: +- The container inherits the visibility and permissions model of the repository where the workflow is run. +- Repository admins where the workflow is run become the admins of the container once the container is created. + +These are more examples of how default permissions work for workflows that manage packages. + +| {% data variables.product.prodname_actions %} workflow task | Default permissions and access | +| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Download an existing container | - If the container is public, any workflow running in any repository can download the container.
- If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise
- If the container is private, only workflows running in repositories that are given read permission on that container can download the container.
| +| Upload a new version to an existing container | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container. | +| Delete a container or versions of a container | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container. | + +You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. 詳しい情報については、「[コンテナイメージにアクセス制御と可視性を設定する](/packages/guides/configuring-access-control-and-visibility-for-container-images)」を参照してください。 + +{% endif %} + +### アクションを使ったパッケージの公開 + +継続的インテグレーション (CI) フローの一環として、{% data variables.product.prodname_actions %}を使用してパッケージを自動的に公開できます。 この継続的デプロイメント (CD) に対するアプローチにより、コードが品質基準を満たしている場合に新しいパッケージの作成を自動化できます。 たとえば、開発者が特定のブランチにプッシュするたびに CI テストを実行するワークフローを作成してはいかがでしょう。 テストにパスすると、このワークフローは新しいパッケージバージョンを{% 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 %}: +以下の例では、{% data variables.product.prodname_actions %}を使用してアプリケーションのビルドとテストを行い、それから自動的にDockerイメージを作成して{% 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: +- リポジトリに新しいワークフローファイル (`.github/workflows/deploy-image.yml` など) を作成し、以下のYAMLを追加します。 {% raw %} - ``` + ```yaml{:copy} name: Create and publish a package on: push: @@ -99,16 +142,14 @@ The following example demonstrates how you can use {% data variables.product.pro with: username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - registry: docker.pkg.github.com + registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %} repository: ${{ github.repository }}/octo-image tag_with_sha: true tag_with_ref: true ``` {% endraw %} - The relevant settings are explained in the following table: - - + 上記に関連する設定については、次の表で説明しています。
@@ -145,7 +186,7 @@ on: {% endraw %} @@ -180,7 +221,7 @@ on: {% endraw %} @@ -193,7 +234,7 @@ on: {% endraw %} @@ -206,7 +247,7 @@ uses: docker/build-push-action@v1 {% endraw %} @@ -219,7 +260,7 @@ with: {% endraw %} @@ -232,7 +273,7 @@ username: ${{ github.actor }} {% endraw %} @@ -245,20 +286,18 @@ password: ${{ secrets.GITHUB_TOKEN }} {% endraw %} @@ -271,7 +310,7 @@ repository: ${{ github.repository }}/octo-image {% endraw %} @@ -284,12 +323,12 @@ tag_with_sha: true {% endraw %}
@@ -121,7 +162,7 @@ on: {% endraw %} - Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. + releaseというブランチに変更をプッシュするたびに、Create and publish a packageワークフローを実行するよう設定します。
- This job installs NPM and uses it to build the app. + このジョブではNPMをインストールし、それをアプリケーションのビルドに使用します。
- 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. + このジョブではnpm testを使用してコードをテストします。 needs: run-npm-buildコマンドにより、このジョブをrun-npm-buildジョブに依存するようにします。
- 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. + Build container imageという新しいステップを作成します。 このステップは、build-and-push-imageジョブの一部として実行されます。 needs: run-npm-testコマンドにより、このジョブをrun-npm-testジョブに依存するようにします。
- 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 %}. + Dockerのbuild-push-actionアクションを使用して、リポジトリのDockerfileを元にイメージをビルドします。 ビルドが成功すると、イメージを{% data variables.product.prodname_registry %}にプッシュします。
- Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. + 必要なパラメータをbuild-push-actionアクションに送信します。 これは以降の行で定義されます。
- Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. + パッケージを公開するユーザアカウントを定めます。 いったん公開されると、パッケージはここで定めたアカウントが所有することになります。
- Defines the password that is used to access {% data variables.product.prodname_registry %}. + {% data variables.product.prodname_registry %}にアクセスするために使用するパスワードを定めます。
-{% raw %} ```yaml -registry: docker.pkg.github.com +registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %} ``` -{% endraw %} - Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. + 生成されるパッケージをホストするレジストリを定めます。 This example uses {% data variables.product.prodname_registry %}.{% if currentVersion == "github-ae@latest" %} Replace YOUR-HOSTNAME with the name of your enterprise.{% endif %} {% if currentVersion == "free-pro-team@latest" %} If you're using the {% data variables.product.prodname_container_registry %}, then use ghcr.io as the hostname.{% endif %}
- 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. + 生成されるパッケージをホストするリポジトリを定め、公開されるパッケージの名前を設定します。 octo-imageは、パッケージに付ける名前に置き換えてください。
- Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. + 公開されるパッケージに、コミットのSHAの最初の7文字でタグを付けます。 たとえば、sha-2f2d842となります。
- + {% raw %} ```yaml tag_with_ref: true @@ -297,22 +336,100 @@ 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. + 公開されるパッケージに、Git refでタグを付けます。 これは、パッケージを作成するために使用するブランチの名前などにするとよいでしょう。
-- 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)." +- この新しいワークフローは、リポジトリの`release`という名前のブランチに変更をプッシュするたびに自動的に実行されます。 [**Actions**] タブで、この進捗を表示できます。 +- ワークフローが完成すると、その数分後にリポジトリで新しいパッケージが表示されます。 使用可能なパッケージを見つけるには、「[リポジトリのパッケージを表示する](/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. +### アクションを使ったパッケージのインストール -Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %} +{% data variables.product.prodname_actions %}を使い、CIフローの一部としてパッケージをインストールできます。 たとえば、開発者がコードをプルリクエストにプッシュすると、いつでもワークフローが{% data variables.product.prodname_registry %}によってホストされているパッケージをダウンロードしてインストールすることで、依存関係を解決するようにワークフローを設定できます。 そして、ワークフローはその依存関係を必要とするCIテストを実行できます。 + +Installing packages hosted by the {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. 詳しい情報については、「[{% 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` cannot install packages from any private repository besides the repository where the action runs. You cannot currently use `GITHUB_TOKEN` to authenticate to {% data variables.product.prodname_github_container_registry %}. {% endif %} {% data reusables.package_registry.actions-configuration %} + +{% if currentVersion == "free-pro-team@latest" %} +### Upgrading a workflow that accesses `ghcr.io` + +{% data reusables.package_registry.github-token-security-over-pat %} + +Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." + +1. Navigate to your package landing page. +1. In the left sidebar, click **Actions access**. !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) +2. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add. !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png) + {% note %} + + **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/guides/configuring-access-control-and-visibility-for-container-images#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a container image](/packages/guides/connecting-a-repository-to-a-container-image)." + + {% endnote %} +3. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) +5. Open your workflow file. On the line where you login to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. + +For example, this workflow publishes a Docker container using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate. + +{% raw %} +```yaml{:copy} +name: Demo Push + +on: + push: + # Publish `master` as Docker `latest` image. + branches: + - master + - seed + + # Publish `v1.2.3` tags as releases. + tags: + - v* + + # Run tests for any PRs. + pull_request: + +env: + IMAGE_NAME: ghtoken_product_demo + +jobs: + # Push image to GitHub Packages. + # See also https://docs.docker.com/docker-hub/builds/ + push: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Build image + run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}" + + - name: Log into registry + # This is where you will update the PAT to GITHUB_TOKEN + run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin + + - name: Push image + run: | + IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME + + # Change all uppercase to lowercase + IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]') + # Strip git ref prefix from version + VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,') + # Strip "v" prefix from tag name + [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//') + # Use Docker `latest` tag convention + [ "$VERSION" == "master" ] && VERSION=latest + echo IMAGE_ID=$IMAGE_ID + echo VERSION=$VERSION + docker tag $IMAGE_NAME $IMAGE_ID:$VERSION + docker push $IMAGE_ID:$VERSION +``` +{% endraw %} + +{% endif %} diff --git a/translations/ja-JP/content/packages/index.md b/translations/ja-JP/content/packages/index.md index fb6feeb34e..2dcc9561e4 100644 --- a/translations/ja-JP/content/packages/index.md +++ b/translations/ja-JP/content/packages/index.md @@ -20,8 +20,8 @@ featuredLinks: - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - label: 'packages' - prefix: 'Packages: ' + label: 'パッケージ' + prefix: 'Packages:' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry 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 9c7d984ebc..c02486cdeb 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 @@ -1,6 +1,6 @@ --- title: GitHub Packagesについて -intro: '{% data variables.product.prodname_registry %}はソフトウェアパッケージのホスティングサービスであり、ソフトウェアパッケージをプライベートもしくはパブリックでホストでき、パッケージをプロジェクト中で依存関係として使えるようになります。' +intro: '{% data variables.product.prodname_registry %}はソフトウェアパッケージのホスティングサービスであり、ソフトウェアパッケージを{% if currentVersion == "github-ae@latest" %}特定のユーザや社内に対し{% else %}非公開または公開でホストでき、{% endif %}パッケージをプロジェクト中で依存関係として使えるようになります。' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/about-github-package-registry @@ -10,32 +10,27 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} ### {% data variables.product.prodname_registry %} について -{% data variables.product.prodname_registry %}はパッケージホスティングサービスで、{% data variables.product.prodname_dotcom %}と完全に統合されています。 {% data variables.product.prodname_registry %}は、ソースコードとパッケージを一カ所にまとめ、統合された権限管理と支払いを提供し、{% data variables.product.product_name %}上でのソフトウェア開発を一元化できるようにします。 +{% data variables.product.prodname_registry %}はパッケージホスティングサービスで、{% data variables.product.prodname_dotcom %}と完全に統合されています。 {% data variables.product.prodname_registry %}は、ソースコードとパッケージを一カ所にまとめ、統合された権限管理{% if currentVersion != "github-ae@latest" %}と支払い{% endif %}を提供し、{% data variables.product.product_name %}上でのソフトウェア開発を一元化できるようにします。 {% data variables.product.prodname_registry %}は、{% data variables.product.product_name %} API、{% data variables.product.prodname_actions %}、webhookと統合して、コード、CI、デプロイメントのソリューションを含むエンドツーエンドのDevOpsワークフローを作成できます。 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 %} +![Diagram showing packages support for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) {% 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 the GitHub Packages hosting urls for npm, RubyGems, Apache Maven, Gradle, Nuget, and Docker](/assets/images/help/package-registry/packages-overview-diagram.png) - {% endif %} #### パッケージの表示 @@ -53,7 +48,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} ### {% data variables.product.prodname_registry %}の支払いについて -{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} 詳細は、「[{% data variables.product.prodname_registry %}の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)」を参照してください。 +{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." {% data reusables.package_registry.container-registry-beta-billing-note %} {% endif %} @@ -63,49 +58,16 @@ versions: {% data variables.product.prodname_registry %}は、パッケージのバージョンの公開とインストールに、すでにおなじみのネイティブのパッケージツールコマンドを使います。 #### パッケージレジストリのサポート -{% if currentVersion == "free-pro-team@latest" %} -パッケージレジストリは、`PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` をパッケージのホスト URL として使用します。`PACKAGE-TYPE` は、パッケージの名前空間に置き換えます。 たとえば、Gemfile は `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` にホストされます。 - -{% else %} - -サイト管理者がさまざまなパッケージのタイプを有効化、無効化できるため、{% data variables.product.product_location %} でサポートされているパッケージのタイプはさまざまです。 詳しい情報については、「[Enterprise 向けの GitHub Packages を管理する](/enterprise/admin/packages)」を参照してください。 - -{% data variables.product.product_location %} が Subdomain Isolation を有効化している場合、パッケージレジストリは `PACKAGE-TYPE.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` をパッケージのホスト URL として使用します。`PACKAGE-TYPE` は、パッケージの名前空間に置き換えます。 たとえば、Dockerfile は `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` にホストされます。 - -{% data variables.product.product_location %} が Subdomain Isolation を無効化している場合、パッケージレジストリは `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` をパッケージのホスト URL として使用します。 たとえば、Gemfile は `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` にホストされます。*HOSTNAME* は、{% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えます。 |{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -| 言語 | 説明 | パッケージフォーマット | パッケージクライアント | パッケージ名前空間 | -| ---------- | ----------------------------- | ------------------------------------- | ------------ | ----------------------------------------------------- | -| JavaScript | Nodeのパッケージマネージャー | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | RubyGemsパッケージマネージャー | `Gemfile` | `gem` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Apache Mavenのプロジェクト管理及び包括的ツール | `pom.xml` | `mvn` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Java用のGradleビルド自動化ツール | `build.gradle` または `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | .NET用のNuGetパッケージ管理 | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | - -{% else %} - -{% data variables.product.product_location %} で Subdomain Isolation を有効化している場合 - -| 言語 | 説明 | パッケージフォーマット | パッケージクライアント | パッケージ名前空間 | -| ---------- | ----------------------------- | ------------------------------------- | ------------ | ----------------------------------------------- | -| JavaScript | Nodeのパッケージマネージャー | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | RubyGemsパッケージマネージャー | `Gemfile` | `gem` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Apache Mavenのプロジェクト管理及び包括的ツール | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Java用のGradleビルド自動化ツール | `build.gradle` または `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | .NET用のNuGetパッケージ管理 | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| なし | Dockerコンテナ管理プラットフォーム | `Dockerfile` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | - -{% data variables.product.product_location %} で Subdomain Isolation を無効化している場合 - -| 言語 | 説明 | パッケージフォーマット | パッケージクライアント | パッケージ名前空間 | -| ---------- | ----------------------------- | ------------------------------------- | ------------ | --------------------------------------------------------- | -| JavaScript | Nodeのパッケージマネージャー | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | RubyGemsパッケージマネージャー | `Gemfile` | `gem` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Apache Mavenのプロジェクト管理及び包括的ツール | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Java用のGradleビルド自動化ツール | `build.gradle` または `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | .NET用のNuGetパッケージ管理 | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` | +| 言語 | 説明 | パッケージフォーマット | パッケージクライアント | +| ---------- | ----------------------------- | ------------------------------------- | ------------ | +| JavaScript | Nodeのパッケージマネージャー | `package.json` | `npm` | +| Ruby | RubyGemsパッケージマネージャー | `Gemfile` | `gem` | +| Java | Apache Mavenのプロジェクト管理及び包括的ツール | `pom.xml` | `mvn` | +| Java | Java用のGradleビルド自動化ツール | `build.gradle` または `build.gradle.kts` | `gradle` | +| .NET | .NET用のNuGetパッケージ管理 | `nupkg` | `dotnet` CLI | +| なし | Dockerコンテナ管理プラットフォーム | `Dockerfile` | `Docker` | +{% if currentVersion ver_gt "enterprise-server@2.22" %} {% note %} **注釈:** Subdomain Isolation が無効化されている場合、Docker はサポートされません。 @@ -116,11 +78,11 @@ Subdomain Isolation の詳しい情報については、「[Subdomain Isolation {% endif %} -For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Package client guides for {% data variables.product.prodname_registry %}](/packages/guides/package-client-guides-for-github-packages)." +{% data variables.product.prodname_registry %}でパッケージクライアントを使用するための設定に関する詳しい情報については、「[{% data variables.product.prodname_registry %}のパッケージクライアントガイド](/packages/guides/package-client-guides-for-github-packages)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} -For more information about Docker and -{% data variables.product.prodname_github_container_registry %}, see "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)." +Dockerおよび +{% data variables.product.prodname_github_container_registry %}に関する詳しい情報については、「[{% data variables.product.prodname_registry %}のコンテナガイド](/packages/guides/container-guides-for-github-packages)」を参照してください。 {% endif %} ### {% data variables.product.prodname_registry %} への認証を行う @@ -132,14 +94,16 @@ For more information about Docker and 例: - リポジトリからパッケージをダウンロードしてインストールするには、トークンは`read:packages`スコープを持っていなければならず、ユーザアカウントはそのリポジトリの読み取り権限を持っていなければなりません。 -- {% data variables.product.product_name %}上の特定バージョンのプライベートパッケージを削除するには、トークンは`delete:packages`及び`repo`スコープを持っていなければなりません。 パブリックなパッケージは削除できません。 詳しい情報については「[パッケージの削除](/packages/manage-packages/deleting-a-package)」を参照してください。 +- {% if currentVersion == "free-pro-team@latest" or if currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.product_name %}上のパッケージを削除するには、トークンが少なくとも`delete:packages`と`read:packages`のスコープを持っている必要があります。 repoのスコープがあるパッケージでは、`repo`スコープも必要です。{% if currentVersion ver_lt "enterprise-server@3.1" %}{% data variables.product.product_name %}上の、プライベートパッケージの特定バージョンを削除するには、トークンが`delete:packages`と`repo`スコープを持っている必要があります。 パブリックなパッケージは削除できません。{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_name %}上の特定のバージョンを削除するには、`delete:packages`および`repo`スコープを持っている必要があります。{% endif %}詳しい情報については、 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」を参照してください。 -| スコープ | 説明 | リポジトリの権限 | -| ----------------- | ------------------------------------------------------------------------------ | --------------- | -| `read:packages` | {% data variables.product.prodname_registry %}からのパッケージのダウンロードとインストール | 読み取り | -| `write:packages` | {% data variables.product.prodname_registry %}へのパッケージのアップロードと公開 | 書き込み | -| `delete:packages` | {% data variables.product.prodname_registry %}からの特定バージョンのプライベートパッケージの削除 | 管理 | -| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write, or admin | +| スコープ | 説明 | リポジトリの権限 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ---------- | +| `read:packages` | {% data variables.product.prodname_registry %}からのパッケージのダウンロードとインストール | 読み取り | +| `write:packages` | {% data variables.product.prodname_registry %}へのパッケージのアップロードと公開 | 書き込み | +| `delete:packages` | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_registry %}からパッケージを削除する {% elsif currentVersion ver_lt "enterprise-server@3.1" %}{% data variables.product.prodname_registry %}からプライベートパッケージの特定バージョンを削除する{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.prodname_registry %}から特定バージョンを削除する{% endif %} | | | +| 管理 | | | +| `repo` | パッケージのアップロードと削除 (`write:packages`または`delete:packages`と併せて) | 書き込みまたは管理者 | {% data variables.product.prodname_actions %}ワークフローを作成する際には、`GITHUB_TOKEN`を使って{% data variables.product.prodname_registry %}にパッケージを公開してインストールでき、個人アクセストークンを保存して管理する必要はありません。 @@ -150,7 +114,27 @@ For more information about Docker and ### パッケージの管理 -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)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.product_name %}ユーザインターフェイスか、 +REST APIを使用してパッケージを削除できます。 詳しい情報については、「[{% data variables.product.prodname_registry %} API](/rest/reference/packages)」を参照してください。 +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %} +{% data variables.product.product_name %}ユーザインターフェイスで +プライベートおよびパブリックパッケージを削除できます。 また、repoスコープのパッケージでは、GraphQLを使用してプライベートパッケージのバージョンを削除できます。 +{% endif %} + +{% if currentVersion ver_lt "enterprise-server@3.1" %} +{% data variables.product.product_name %}ユーザインターフェイス +またはGraphQL APIを使用して、プライベートパッケージのバージョンを削除できます。 +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +{% data variables.product.product_name %}ユーザインターフェイス +またはGraphQL APIを使用して、プライベートパッケージのバージョンを削除できます。 +{% endif %} + +GraphQL APIを使ってプライベートパッケージに対するクエリや削除を行う場合、{% data variables.product.prodname_registry %}の認証に使うのと同じトークンを使わなければなりません。 詳しい情報については、 「{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}」および「"[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。 webhookを設定して、パッケージの公開や更新といったパッケージ関連のイベントにサブスクライブできます。 詳しい情報については、「[`package` webhookイベント](/webhooks/event-payloads/#package)」を参照してください。 diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..dd9e34006a --- /dev/null +++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -0,0 +1,68 @@ +--- +title: カスタムドメインとGitHub Pagesについて +intro: '{% data variables.product.prodname_pages %} では、カスタムドメインを使用する、つまりサイトの URL を ''octocat.github.io'' などのデフォルトからあなたが所有するドメインに変更することができます。' +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 + - /github/working-with-github-pages/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +### サポートされているカスタムドメイン + +{% data variables.product.prodname_pages %} では、サブドメインとApexドメインの 2 種類のドメインを使用できます。 サポートされていないカスタムサブドメインのリストは、「[カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)」を参照してください。 + +| サポートされているカスタムドメインの種類 | サンプル | +| -------------------- | ------------------ | +| `www` サブドメイン | `www.example.com` | +| カスタムサブドメイン | `blog.example.com` | +| Apex ドメイン | `example.com` | + +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." + +Apex ドメインを使用している場合でも、`www` サブドメインを使用することをおすすめします。 When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。 + +ユーザまたは Organization サイトのカスタムドメインを設定すると、カスタムドメインを設定していないアカウントが所有するプロジェクトサイトの URL で、`.github.io` または `.github.io` の部分がカスタムドメインによって置き換えられます。 たとえば、サイトのカスタムドメインが `www.octocat.com` で、`octo-project` というリポジトリから公開されているプロジェクトサイトにまだカスタムドメインを設定していない場合、そのリポジトリの {% data variables.product.prodname_pages %} サイトは、`www.octocat.com/octo-project` で公開されます。 + +### あなたの {% data variables.product.prodname_pages %} サイトにサブドメインを使用する + +サブドメインは、URL のうちルートドメインの前の部分です。 サブドメインは、`www` に設定することも、あるいは `blog.example.com` のようにサイトの独自セクションに設定することもできます。 + +サブドメインは、DNS プロバイダを通じて `CNAME` レコードで設定されます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)」を参照してください。 + +#### `www` サブドメイン + +サブドメインの種類として最もよく使われているのは、`www` サブドメインです。 たとえば、`www.example.com` には `www` サブドメインが含まれています。 + +`www` サブドメインは、カスタムドメインとして最も安定的です。{% data variables.product.product_name %} のサーバの IP アドレスが変更されても、`www` サブドメインは影響を受けないからです。 + +#### カスタムサブドメイン + +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. カスタムサブドメインは、サイトに 2 つの独自セクションを作成したい場合に最もよく使われます。 たとえば、`blog.example.com` というサイトを作成し、`www.example.com` から独自のセクションをカスタマイズできます。 + +### あなたの {% data variables.product.prodname_pages %} サイトに Apex ドメインを使用する + +Apex ドメインは、`example.com` といったようにサブドメインを含まないカスタムドメインです。 Apex ドメインは、ベースドメイン、ベアドメイン、裸ドメイン、ルート Apex ドメイン、ゾーン Apex ドメインなどとも呼ばれます。 + +Apex ドメインは、DNS プロバイダを通じて、`A`、`ALIAS`、`ANAME` レコードで設定されます。 詳しい情報については、「[{% 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 %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." + +### {% data variables.product.prodname_pages %} サイトが無効化された際にカスタムドメインを更新する + +{% data variables.product.prodname_pages %} サイトが無効になっていて、かつカスタムドメインがセットアップされている場合、すぐに DNS プロバイダで DNS レコードを更新するか削除して、ドメイン乗っ取りのリスクを避けてください。 サイトが無効な間に、DNS プロバイダでカスタムドメインを設定していると、サブドメインのいずれかで誰かにサイトをホストされてしまう恐れがあります。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。 + +サイトが自動的に無効化される理由は、いくつかあります。 + +- {% data variables.product.prodname_pro %} から {% data variables.product.prodname_free_user %} へダウングレードすると、アカウント内のプライベートリポジトリから公開されている {% data variables.product.prodname_pages %} のサイトは公開されなくなります。 詳細は「[{% data variables.product.prodname_dotcom %} の支払いプランをダウングレードする](/articles/downgrading-your-github-billing-plan)」を参照してください。 +- {% data variables.product.prodname_free_user %} を利用している個人アカウントへプライベートリポジトリを移譲した場合、そのリポジトリからは {% data variables.product.prodname_pages %} の機能を利用できなくなり、公開されている {% data variables.product.prodname_pages %} は公開されなくなります。 詳細は「[リポジトリを移譲する](/articles/transferring-a-repository)」を参照してください。 + +### 参考リンク + +- [カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages) diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md new file mode 100644 index 0000000000..d855670166 --- /dev/null +++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -0,0 +1,23 @@ +--- +title: GitHub Pages サイトのカスタムドメインを設定する +intro: '{% 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 + - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000..540d6ead46 --- /dev/null +++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,121 @@ +--- +title: GitHub Pages サイトのカスタムドメインを管理する +intro: '特定の DNS レコードとリポジトリ設定を設定または更新し、{% data variables.product.prodname_pages %} サイトのデフォルトドメインをカスタムドメインに指定することができます。' +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 + - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトのカスタムドメインを設定できます。 + +### カスタムドメインの設定について + +DNS プロバイダでカスタムドメインを設定する前に、必ず {% data variables.product.prodname_pages %} サイトをカスタムドメインに追加してください。 カスタムドメインを {% data variables.product.product_name %} に追加せずに DNS プロバイダに設定すると、別のユーザがあなたのサブドメインにサイトをホストできることになります。 + +{% windows %} + +DNS レコードの設定が正しいかどうかを検証するために利用できる`dig` コマンドは、Windows には含まれていません。 DNS レコードが正しく設定されているかを検証する前に、[BIND](https://www.isc.org/bind/) をインストールする必要があります。 + +{% endwindows %} + +{% note %} + +**注釈:** DNS の変更が伝播するには、最大 24 時間かかります。 + +{% endnote %} + +### サブドメインを設定する + +To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings, which will create a CNAME file in your site’s repository. After that, configure a CNAME record with your DNS provider. + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. "Custom domain（カスタムドメイン）" の下で、カスタムドメインを入力して**Save（保存）**をクリックします。 これで_CNAME_ファイルを公開ソースのルートに追加するコミットが作成されます。 ![カスタムドメインの保存ボタン](/assets/images/help/pages/save-custom-subdomain.png) +5. お使いの DNS プロバイダにアクセスし、サブドメインがサイトのデフォルトドメインを指す `CNAME` レコードを作成します。 たとえば、サイトで `www.example.com` というサブドメインを使いたい場合、`www.example.com` が `.github.io` を指す`CNAME` レコードを作成します。 If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `.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 %} + +{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} +{% data reusables.command_line.open_the_multi_os_terminal %} +6. DNS レコードが正しくセットアップされたことを確認するには、 `dig` コマンドを使います。_WWW.EXAMPLE.COM_ は、お使いのサブドメインに置き換えてください。 +```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 %} + +### Apexドメインを設定する + +To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider. + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)." + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. "Custom domain（カスタムドメイン）" の下で、カスタムドメインを入力して**Save（保存）**をクリックします。 これで_CNAME_ファイルを公開ソースのルートに追加するコミットが作成されます。 ![カスタムドメインの保存ボタン](/assets/images/help/pages/save-custom-apex-domain.png) +5. DNS プロバイダに移動し、`ALIAS`、`ANAME`、または `A` レコードを作成します。 {% data reusables.pages.contact-dns-provider %} + - `ALIAS`または`ANAME`レコードを作成するには、Apexドメインをサイトのデフォルトドメインにポイントします。 {% data reusables.pages.default-domain-information %} + - To create `A` records, point your apex domain to the IP addresses for {% 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. DNS レコードが正しく設定されたことを確認するには、 `dig` コマンドを使います。_EXAMPLE.COM_ は、お使いの Apex ドメインに置き換えてください。 結果が、上記の {% data variables.product.prodname_pages %} の IP アドレスに一致することを確認します。 + ```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 %} + +### Configuring an apex domain and the `www` subdomain variant + +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. + +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." + +After you configure the apex domain, you must to configure a CNAME record with your DNS provider. + +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. +```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 +``` +### Removing a custom domain + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain," click **Remove**. ![カスタムドメインの保存ボタン](/assets/images/help/pages/remove-custom-domain.png) + +### 参考リンク + +- [カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages) diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..fb9d8b445d --- /dev/null +++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,65 @@ +--- +title: カスタムドメインとGitHub Pages のトラブルシューティング +intro: '{% data variables.product.prodname_pages %} サイトのカスタムドメインまたは HTTPS について、よくあるエラーを確認して Issue を解決することができます。' +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 + - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +### _CNAME_ エラー + +カスタムドメインは、公開ソースのルートにある _CNAME_ ファイルに保存されます。 このファイルは、リポジトリ設定を通じて、あるいは手動で追加または更新することができます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。 + +サイトが正しいドメインをレンダリングするには、_CNAME_ ファイルがまだリポジトリに存在していることを確認します。 たとえば、静的サイトジェネレータの多くはリポジトリへのプッシュを強制するので、カスタムドメインの設定時にリポジトリに追加された _CNAME_ ファイルを上書きすることができます。 ローカルでサイトをビルドし、生成されたファイルを {% data variables.product.product_name %} にプッシュする場合は、_CNAME_ ファイルをローカルリポジトリに追加したコミットを先にプルして、そのファイルがビルドに含まれるようにする必要があります。 + +次に、_CNAME_ のフォーマットが正しいことも確認します。 + +- _CNAME_ ファイル名は、すべて大文字である必要があります。 +- _CNAME_ ファイルにはドメインを 1 つだけ含めることができます。 複数のドメインをサイトにポイントするには、DNSプロバイダ経由のリダイレクトを設定する必要があります。 +- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`. +- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. たとえば、別のリポジトリの _CNAME_ ファイルに `example.com` が含まれている場合、自分のリポジトリの _CNAME_ ファイルに `example.com` を使用することはできません。 + +### DNS の設定ミス + +デフォルトドメインをカスタムドメインにポイントすることに問題がある場合は、DNS プロバイダに連絡してください。 + +カスタムドメインの DNS レコードを正しく設定しているかどうかも確認できます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。 + +### サポートされていないカスタムドメイン名 + +カスタムドメインがサポートされていない場合、使用しているドメインをサポートされているドメインに変更しなければならないかもしれません。 DNSプロバイダに問い合わせて、ドメイン名の転送サービスを提供しているかどうかを確認することもできます。 + +サイトが以下に当てはまっていないを確認してください。 +- 複数の Apex ドメインを使用している。 たとえば、`example.com` と`anotherexample.com` の両方など。 +- 複数の `www` サブドメインを使用している。 たとえば、`www.example.com` と`www.anotherexample.com` の両方など。 +- Apex ドメインとカスタムサブドメインの両方を使用している。 たとえば、`example.com` と`docs.example.com` の両方など。 + + The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)」を参照してください。 + +{% data reusables.pages.wildcard-dns-warning %} + +サポートされているカスタムサブドメインのリストは、「[カスタムドメインと {% data variables.product.prodname_pages %} について](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)」を参照してください。 + +### HTTPS エラー + +_CNAME_、`ALIAS`、`ANAME` や `A` DNS レコードで適切に設定されたカスタムドメインを使っている {% data variables.product.prodname_pages %} サイトは、HTTPS でアクセスできます。 詳しい情報については[HTTPSで{% data variables.product.prodname_pages %}サイトをセキュアにする](/articles/securing-your-github-pages-site-with-https)を参照してください。 + +カスタムドメインを設定した後、サイトが HTTPS 経由で利用可能になるには最長 1 時間かかります。 既存の DNS 設定をアップデートした後、HTTPS を有効化するプロセスを開始するには、カスタムドメインを削除してサイトのリポジトリに再追加しなければならない可能性があります。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。 + +Certification Authority Authorization (CAA) レコードの使用を選択した場合、HTTPS 経由でサイトにアクセスするには、値が `letsencrypt.org` の CAA レコードが少なくとも 1 つ存在している必要があります。 詳しい情報については、Let's Encrypt ドキュメンテーションの「[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)」を参照してください。 + +### Linux での URL フォーマット + +サイトのURLに、先頭か最後がダッシュのユーザ名もしくは Organization 名が含まれていたり、連続するダッシュが含まれていたりすると、Linux でブラウズするユーザがそのサイトにアクセスしようとするとサーバーエラーを受け取ることになります。 これを修正するには、{% data variables.product.product_name %}のユーザ名から非英数字を取り除くよう変更してください。 詳細は「[{% data variables.product.prodname_dotcom %} ユーザ名を変更する](/articles/changing-your-github-username/)」を参照してください。 + +### ブラウザのキャッシュ + +最近カスタムドメインを変更または削除し、ブラウザで新しい URL にアクセスできない場合は、ブラウザのキャッシュを削除してから新しい URL にアクセスすることが必要になる場合があります。 キャッシュの削除についての詳しい情報については、ブラウザのドキュメントを参照してください。 diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000..be739d7da4 --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -0,0 +1,150 @@ +--- +title: GitHub Pages について +intro: '{% data variables.product.prodname_pages %} を使って、あなたやあなたの Organization、またはあなたのプロジェクトについてのウェブサイトを、{% 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 + - /github/working-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### {% data variables.product.prodname_pages %} について + +{% data variables.product.prodname_pages %} は、{% data variables.product.product_name %} のリポジトリから HTML、CSS、および JavaScript ファイル を直接取得し、任意でビルドプロセスを通じてファイルを実行し、ウェブサイトを公開できる静的なサイトホスティングサービスです。 {% data variables.product.prodname_pages %} サイトの例については、[{% data variables.product.prodname_pages %} サンプル集](https://github.com/collections/github-pages-examples)で見ることができます。 + +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.prodname_dotcom %} の`github.io` ドメインまたはご自身のカスタムドメインで、サイトをホストできます。 詳細は「[{% data variables.product.prodname_pages %} でカスタムドメインを使用する](/articles/using-a-custom-domain-with-github-pages)」を参照してください。 +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +作成方法については、「[{% data variables.product.prodname_pages %} サイトを作成する](/articles/creating-a-github-pages-site)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." +{% endif %} + +### {% data variables.product.prodname_pages %} サイトの種類 + +{% data variables.product.prodname_pages %} サイトには、3 つの種類があります。プロジェクト、ユーザ、そして Organization です。 プロジェクトサイトは、JavaScript ライブラリやレシピ集など、{% data variables.product.product_name %} の特定のプロジェクトに関するものです。 ユーザおよび Organization サイトは、特定の {% data variables.product.product_name %} に関するものです。 + +To publish a user site, you must create a repository owned by your user account that's named {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. 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 %} + +{% if currentVersion == "free-pro-team@latest" %} +If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +カスタムドメインがサイトの URL に与える影響に関する詳しい情報については、「[カスタムドメインと {% 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 %}. プロジェクトサイトの数については、Organization アカウントでもユーザアカウントでも、無制限です。 + +{% if enterpriseServerVersions contains currentVersion %} +サイトが利用できる URL については、{% data variables.product.product_location %} で Subdomain Isolation を有効にしているかどうかで異なります。 + +| サイトの種類 | Subdomain Isolation が有効 | Subdomain isolation が無効 | +| ------ | ----------------------- | ----------------------- | +| | | | + 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///` + +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" %} +{% note %} + +**Note:** Repositories using the legacy `.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://.github.com` to `http(s)://.github.io`. If both a `.github.com` and `.github.io` repository exist, only the `.github.io` repository will be published. + +{% endnote %} +{% endif %} + +### {% 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" %} + +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. + +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. 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/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 %} + +{% else %} + +ユーザおよび Organization サイトの、デフォルトの公開元は `master` ブランチです。 ユーザまたは Organization サイトのリポジトリに `master` ブランチがある場合、サイトはそのブランチから自動的に公開されます。 ユーザや Organization サイトで、別の公開元を選ぶことはできません。 + +プロジェクトサイトの、デフォルトの公開元は `gh-pages` ブランチです。 プロジェクトサイトのリポジトリに `gh-pages` ブランチがある場合、サイトはそのブランチから自動的に公開されます。 + +プロジェクトサイトは、`master` ブランチまたは `master` ブランチ場の `/docs` フォルダから公開することもできます。 これらの公開元からサイトを公開するには、別の公開元を設定する必要があります。 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/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 %} + +デフォルトブランチが`master`または`gh-pages`ではない場合でも、他のブランチからはプロジェクトサイトを公開することはできません。 + +{% endif %} + +### 静的サイトジェネレータ + +{% data variables.product.prodname_pages %} は、リポジトリにプッシュされたあらゆる静的ファイルを公開します。 静的ファイルを自分で作成することも、静的サイトジェネレータでサイトをビルドすることも可能です。 ローカルまたは別のサーバー上で独自のビルドプロセスをカスタマイズすることもできます。 {% data variables.product.prodname_pages %} に組み込まれている静的サイトジェネレータで、ビルドプロセスを容易化できる Jekyll のご利用をおすすめします。 詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll](/articles/about-github-pages-and-jekyll)」を参照してください。 + +{% data variables.product.prodname_pages %} は、デフォルトでは Jekyll を使ってサイトを構築します。 Jekyll 以外の静的サイトジェネレータを使いたい場合、公開元のルートに `.nojekyll` という空のファイルを作成し、お使いの静的サイトジェネレータの指示に従ってローカルでサイトをビルドします。 + +{% data variables.product.prodname_pages %} は、PHP、Ruby、Python などのサーバーサイド言語はサポートしていません。 + +### {% 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 reusables.pages.no_sensitive_data_pages %} +- {% data variables.product.prodname_pages %} の使用には、転売禁止を含めて、[GitHub 利用規約](/articles/github-terms-of-service/)が適用されます。 + +#### 使用制限 +{% endif %} +{% data variables.product.prodname_pages %} サイトには、次の使用制限があります: + + - {% 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 %}のサイトは1GB以上であってはなりません。 +{% if currentVersion == "free-pro-team@latest" %} + - {% data variables.product.prodname_pages %} サイトには、月当たり 100GB の*ソフトな*帯域幅制限があります。 + - {% data variables.product.prodname_pages %} サイトには、時間当たり 10 ビルドの*ソフトな*制限があります。 + +あなたのサイトがこれらの使用割当量を超えている場合、あなたのサイトにサービスを提供できないか、{% data variables.contact.contact_support %} から、あなたのサイトが当社のサーバーに与える影響を減らす方法を示唆するメールが届くことがあります。そうした方法の例としては、サードパーティのコンテンツ配信ネットワーク (CDN) をサイトの前に配置したり、リリースなどの他の {% data variables.product.prodname_dotcom %} 機能を利用したり、ニーズに合った別のホスティングサービスに移行したりすることなどが挙げられます。 + +#### 禁止される用途 + +{% data variables.product.prodname_pages %} は、オンラインビジネス、eコマースサイト、主に商取引の円滑化またはサービスとしての商用ソフトウェアの提供 (SaaS) のどちらかを目的とする、その他のウェブサイトを運営するための無料のウェブホスティングサービスとしての使用を意図したものではなく、またそのような使用を許可するものでもありません。 + +In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. For a list of prohibited uses, see "[{% data variables.product.prodname_dotcom %}'s Additional Product Terms for {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)." +{% endif %} + +### {% data variables.product.prodname_pages %} での MIME タイプ + +MIME タイプとは、ブラウザがリクエストするファイルの性質やフォーマットに関する情報を提供するため、サーバーがブラウザに送信するヘッダのことです。 {% data variables.product.prodname_pages %} は、数千のファイル拡張子にわたり、750 を超える MIME タイプをサポートしています。 サポートする MIME タイプのリストは、[mime-db project](https://github.com/jshttp/mime-db) から生成されます。 + +ファイルごと、リポジトリごとにカスタム MIME タイプを指定することはできませんが、{% data variables.product.prodname_pages %} で使う MIME タイプを追加や変更することは可能です。 詳しい情報については、「[mime-db コントリビューションガイドライン](https://github.com/jshttp/mime-db#adding-custom-media-types)」を参照してください。 + +### 参考リンク + +- {% data variables.product.prodname_learning %} の [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000..e9d770d806 --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,46 @@ +--- +title: テーマ選択画面で GitHub Pages サイトにテーマを追加する +intro: 'サイトの見た目をカスタマイズするため、{% data variables.product.prodname_pages %} サイトにテーマを追加できます。' +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトにテーマを追加するため、テーマ選択画面を使用できます。 + +### テーマ選択画面について + +テーマ選択画面は、リポジトリに Jekyll テーマを追加するためのものです。 Jekyll に関する詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll](/articles/about-github-pages-and-jekyll)」を参照してください。 + +テーマ選択画面の動作は、リポジトリがパブリックかプライベートかにより異なります。 + - {% data variables.product.prodname_pages %} がリポジトリに対して既に有効である場合、テーマ選択画面は、現在の公開元にテーマを追加します。 + - If your repository is public and {% data variables.product.prodname_pages %} is disabled for your repository, using the theme chooser will enable {% data variables.product.prodname_pages %} and configure the default branch as your publishing source. + - リポジトリがプライベートで、{% data variables.product.prodname_pages %}がリポジトリに対して無効である場合、テーマ選択画面を使用する前に、公開元を設定して {% data variables.product.prodname_pages %} を有効にする必要があります。 + +公開元に関する詳しい情報については、「[{% data variables.product.prodname_pages %} について](/articles/about-github-pages#publishing-sources-for-github-pages-sites)」を参照してください。 + +Jekyll テーマをリポジトリに手動で追加したことがある場合には、それらのファイルが、テーマ選択画面を使用した後も適用されることがあります。 競合を避けるため、テーマ選択画面を使用する前に、手動で追加したテーマフォルダおよびファイルをすべて削除してください。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)」を参照してください。 + +### テーマ選択画面でテーマを追加する + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. [{% data variables.product.prodname_pages %}] で、[**Choose a theme**] または [**Change theme**] をクリックします。 ![[Choose a theme] ボタン](/assets/images/help/pages/choose-a-theme.png) +4. ページ上部の、選択したいテーマをクリックし、[**Select theme**] をクリックします。 ![テーマのオプションおよび [Select theme] ボタン](/assets/images/help/pages/select-theme.png) +5. サイトの *README.md* ファイルを編集するようプロンプトが表示される場合があります。 + - ファイルを後で編集する場合、[**Cancel**] をクリックします。 ![ファイルを編集する際の [Cancel] リンク](/assets/images/help/pages/cancel-edit.png) + - ファイルをすぐ編集する場合、「[リポジトリのファイルを編集する](/articles/editing-files-in-your-repository/)」を参照してください。 + +選択したテーマは、リポジトリの Markdown ファイルに自動的に適用されます。 テーマをリポジトリの HTML ファイルに適用するには、各ファイルのレイアウトを指定する YAML front matter を追加する必要があります。 詳しい情報については、Jekyll サイトの「[Front Matter](https://jekyllrb.com/docs/front-matter/)」を参照してください。 + +### 参考リンク + +- Jekyll サイトの「[Themes](https://jekyllrb.com/docs/themes/)」 diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..71c23d4207 --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +redirect_from: + - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published: + +- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS. +- We use a unique subdomain for the private page to ensure that other repositories in your organization cannot publish content on the same origin as the private page. This protects your private page from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain. + +You can see your site's unique subdomain in the pages tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +To use a shorter and more memorable domain for your private {% data variables.product.prodname_pages %} site, you can configure a custom domain. 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインの設定](/pages/configuring-a-custom-domain-for-your-github-pages-site)」を参照してください。 + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. 公開されたサイトを見るには、"{% data variables.product.prodname_pages %}"の下で、サイトのURLをクリックしてください。 ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000..041032f80b --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,38 @@ +--- +title: GitHub Pages サイトの公開元を設定する +intro: '{% data variables.product.prodname_pages %} サイトでデフォルトの公開元を使用している場合、サイトは自動的に公開されます。 You can also choose to publish your{% if currentVersion ver_lt "enterprise-server@3.0" %} project{% endif %} site from a different branch or folder.' +redirect_from: + - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-your-github-pages-site + - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can configure a publishing source for a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +公開元に関する詳しい情報については、「[{% data variables.product.prodname_pages %} について](/articles/about-github-pages#publishing-sources-for-github-pages-sites)」を参照してください。 + +### 公開元を選択する + +Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} 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 %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source. ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +4. Optionally, use the drop-down menu to select a folder for your publishing source. ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. [**Save**] をクリックします。 ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %} +3. [{% data variables.product.prodname_pages %}] で、[**Source**] ドロップダウンメニューから公開元を選択します。 ![公開元を選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-drop-down.png) +{% endif %} + +### {% data variables.product.prodname_pages %} サイトの公開に関するトラブルシューティング + +{% 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)」を参照してください。 diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000..4c807a41f5 --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: GitHub Pages サイトのカスタム 404 ページを作成する +intro: サイト上の存在しないページにアクセスしようとした際に表示される、404 エラーページをカスタマイズできます。 +redirect_from: + - /articles/custom-404-pages/ + - /articles/creating-a-custom-404-page-for-your-github-pages-site + - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +{% data reusables.files.add-file %} +3. ファイル名のフィールドに、`404.html` または `404.md` と入力します。 ![ファイル名フィールド](/assets/images/help/pages/404-file-name.png) +4. ファイル名を `404.md` とした場合、ファイルの先頭に以下の YAML front matter を追加します。 + ```yaml + --- + permalink: /404.html + --- + ``` +5. YAML front matter の下に、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 %} + +### 参考リンク + +- Jekyll ドキュメンテーションの [Front matter](http://jekyllrb.com/docs/frontmatter) diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000..7d3ac8875f --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,63 @@ +--- +title: GitHub Pages サイトを作成する +intro: '新規または既存のリポジトリ内に、{% data variables.product.prodname_pages %} サイトを作成できます。' +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 + - /github/working-with-github-pages/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### サイト用にリポジトリを作成する + +{% data reusables.pages.new-or-existing-repo %} + +{% 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 %} + +### サイトを作成する + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.decide-publishing-source %} +3. 選択した公開元が既に存在する場合、公開元に移動します。 選択した公開元がまだ存在しない場合は、公開元を作成します。 +4. 公開元のルートに、サイトのメインページに表示したいコンテンツを含んだ、`index.md` という名前の新しいファイルを作成します。 +{% data reusables.pages.configure-publishing-source %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### 次のステップ + +新しいファイルを追加で作成することにより、ページを追加できます。 各ファイルは、公開元と同じディレクトリ構造で、サイト上に表示されます。 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.html` で表示されます。 + +また、サイトの見た目をカスタマイズするため、テーマを追加できます。 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 %}." + +サイトを更にカスタマイズするには、Jekyll を使用できます。Jekyll は、{% data variables.product.prodname_pages %} に組み込まれている静的サイトジェネレータです。 詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll](/articles/about-github-pages-and-jekyll)」を参照してください。 + +### 参考リンク + +- [{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーに関するトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites) +- [リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository) +- [新しいファイルの作成](/articles/creating-new-files) diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md new file mode 100644 index 0000000000..33d6498443 --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md @@ -0,0 +1,26 @@ +--- +title: GitHub Pages を使ってみる +intro: '基本的な {% data variables.product.prodname_pages %} サイトを、あなたやあなたの Organization、またはあなたのプロジェクトのためにセットアップできます。' +redirect_from: + - /categories/github-pages-basics + - /articles/additional-customizations-for-github-pages/ + - /articles/getting-started-with-github-pages + - /github/working-with-github-pages/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 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 /changing-the-visibility-of-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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000..71736b5ddb --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,55 @@ +--- +title: HTTPS で GitHub Pages サイトを保護する +intro: 'HTTPS は、他者によるあなたのサイトへのトラフィックの詮索や改ざんを防ぐ暗号化のレイヤーを追加します。 透過的に HTTP リクエストを HTTPS にリダイレクトするために、あなたの {% data variables.product.prodname_pages %} サイトに HTTPS を強制できます。' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/securing-your-github-pages-site-with-https + - /github/working-with-github-pages/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +topics: + - pages +--- + +リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトに強制的に HTTPS を指定できます。 + +### HTTPS と {% data variables.product.prodname_pages %} について + +カスタムドメインが正しく設定されたサイトを含めたすべての {% data variables.product.prodname_pages %} サイトは、HTTPS や HTTPS 強制をサポートします。 カスタムドメインの詳細は、「[カスタムドメインと {% data variables.product.prodname_pages %} について](/articles/about-custom-domains-and-github-pages)」と「[カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)」を参照してください。 + +{% data reusables.pages.no_sensitive_data_pages %} + +{% data reusables.pages.private_pages_are_public_warning %} + +### あなたの {% data variables.product.prodname_pages %} サイトに HTTPS を強制する + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. [{% data variables.product.prodname_pages %}] で、[**Enforce HTTPS**] を選択します。 ![[Enforce HTTPS] チェックボックス](/assets/images/help/pages/enforce-https-checkbox.png) + +### 混在したコンテンツの問題を解決する + +{% data variables.product.prodname_pages %} サイトの HTTPS を有効化したが、サイトの HTML がまだ HTTP 経由で画像、CSS、JavaScript を参照している場合、サイトは*混在したコンテンツ*を提供する場合があります。 混在したコンテンツを提供することで、サイトのセキュリティが下がり、アセットの読み込みに問題が生じる場合があります。 + +サイトでコンテンツの混在を解消するには、サイトの HTML で `http://` を `https://` に変更して、すべてのアセットが HTTPS 経由で提供されるようにしてください。 + +アセットは通常、以下の場所にあります。 +- サイトで Jekyll を使用している場合、HTML ファイルは *_layouts* フォルダにあります。 +- CSS は普通、HTML ファイルの `` セクションにあります。 +- JavaScript は通常、`` セクションまたは閉じタグ `` の直前にあります。 +- 画像はたいてい、`` セクションにあります。 + +{% tip %} + +**ヒント:** サイトのソースファイルでアセットが見つからない場合は、テキストエディタまたは {% data variables.product.product_name %} 上で、サイトのソースファイルから `http`を検索してみましょう。 + +{% endtip %} + +#### HTML ファイルで参照されているアセットの例 + +| アセットのタイプ | HTTP | HTTPS | +|:----------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:| +| CSS | `` | `` | +| JavaScript | `` | `` | +| 画像 | `Logo` | `Logo` | diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000..c5013e457d --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: GitHub Pages サイトを取り下げる +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' +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 + - /github/working-with-github-pages/unpublishing-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can unpublish a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### プロジェクトサイトを取り下げる + +{% data reusables.repositories.navigate-to-repo %} +2. リポジトリに `gh-pages` ブランチが存在する場合は、`gh-pages` ブランチを削除します。 詳しい情報については[リポジトリ内でのブランチの作成と削除](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)を参照してください。 +3. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. {% data variables.product.prodname_pages %} で、[**Source**] ドロップダウンメニューを使用して [**None**] を選択します。 ![公開元を選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} + +### ユーザまたは Organization サイトを取り下げる + +{% data reusables.repositories.navigate-to-repo %} +2. Delete the branch that you're using as a publishing source, or delete the entire repository. 詳細は「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」および「[リポジトリを削除する](/articles/deleting-a-repository)」を参照してください。 +{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000..6b6a3e275f --- /dev/null +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,24 @@ +--- +title: GitHub Pages でサブモジュールを使用する +intro: '{% data variables.product.prodname_pages %} でサブモジュールを使用すると、他のサイトのコードで他のプロジェクトを含めることができます。' +redirect_from: + - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-github-pages + - /github/working-with-github-pages/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +{% data variables.product.prodname_pages %} サイトのリポジトリにサブモジュールが含まれている場合、その内容はサイトをビルドする際に自動的にプルされます。 + +使用できるのは、パブリックリポジトリをポイントするサブモジュールだけです。{% data variables.product.prodname_pages %} サーバーはプライベートリポジトリにはアクセスできないためです。 + +ネストされたサブモジュールも含めて、サブモジュールには `https://` 読み取り専用 URL を使用してください。 この変更は _.gitmodules_ ファイルで行うことができます。 + +### 参考リンク + +- _Pro Git_ ブックの「[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)」 +- [{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーに関するトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites) diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md new file mode 100644 index 0000000000..07d1227d5b --- /dev/null +++ b/translations/ja-JP/content/pages/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages Documentation +shortTitle: GitHub Pages +intro: '{% 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 + - /github/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% link_with_intro /getting-started-with-github-pages %} +{% link_with_intro /setting-up-a-github-pages-site-with-jekyll %} +{% link_with_intro /configuring-a-custom-domain-for-your-github-pages-site %} \ No newline at end of file diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000..f8b3110b35 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -0,0 +1,131 @@ +--- +title: GitHub PagesとJekyllについて +intro: 'Jekyllは、{% 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 + - /github/working-with-github-pages/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### Jekyllについて + +Jekyllは、{% data variables.product.prodname_pages %}に組み込まれている静的サイトジェネレータで、ビルドプロセスを容易化できます。 JekyllはMarkdownおよびHTMLファイルを取り込み、選択したレイアウトに基づいて、完成された静的ウェブサイトを作成します。 Jekyllは、Markdownと、サイトに動的コンテンツを読み込むテンプレート言語のLiquidをサポートします。 詳しい情報については、[Jekyll](https://jekyllrb.com/)を参照してください。 + +Windows は、Jekyll を公式にはサポートしていません。 For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation. + +{% data variables.product.prodname_pages %} ではJekyllを使用することをおすすめします。 お好みに応じて、別の静的サイトジェネレータを使用することも、ローカルまたは別のサーバーにおけるビルドプロセスをカスタマイズすることもできます。 詳しい情報については「[{% data variables.product.prodname_pages %}について](/articles/about-github-pages#static-site-generators)」を参照してください。 + +### {% data variables.product.prodname_pages %}サイトでJekyllを設定する + +*_config.yml*ファイルを編集することにより、サイトのテーマやプラグインなど、Jekyllの設定のほとんどを設定できます。 詳しい情報については、Jekyllのドキュメンテーションの「[Configuration](https://jekyllrb.com/docs/configuration/)」を参照してください。 + +一部の設定は、{% data variables.product.prodname_pages %}サイトで変更できません。 + +```yaml +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 +``` + +デフォルトでは、Jekyllでは以下に当てはまるファイルやフォルダをビルドしません。 +- `/node_modules`または`/vendor`と名付けられたフォルダ内にあるもの +- start with `_`, `.`, or `#` +- 次の文字で終わるもの: `~` +- 設定ファイルの`exclude`設定で除外されているもの + +以上に当てはまるファイルをJekyllで処理したい場合、設定ファイルで`includes`設定を利用できます。 + +### フロントマター + +{% data reusables.pages.about-front-matter %} + +ポストまたはページに`site.github`を追加して、あらゆるリポジトリリファレンスメタデータをサイトに追加できます。 詳しい情報については、Jekyllメタデータドキュメンテーションの「[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)」を参照してください。 + +### テーマ + +{% data reusables.pages.add-jekyll-theme %}詳しい情報については、Jekyllドキュメンテーションの「[Themes](https://jekyllrb.com/docs/themes/)」を参照してください。 + +{% if currentVersion == "free-pro-team@latest" %} +{% 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)." + +テーマのファイルを編集することで、テーマのデフォルトを上書きできます。 詳しい情報については、テーマのドキュメンテーションおよびJekyllドキュメンテーションの「[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)」を参照してください。 + +### プラグイン + +Jekyllプラグインをダウンロードまたは作成すると、サイトでJekyllの機能を拡張できます。 たとえば、[jemoji](https://github.com/jekyll/jemoji)プラグインを使うと、{% data variables.product.prodname_dotcom %}っぽい絵文字を、{% data variables.product.prodname_dotcom %}で使うのと同じように、サイトの任意のページで使用できます。 詳細については、Jekyllのドキュメンテーションで「[プラグイン](https://jekyllrb.com/docs/plugins/)」を参照してください。 + +{% data variables.product.prodname_pages %}で使用されるプラグインはデフォルトで有効になっており、無効にすることはできません。 +- [`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) + +追加のプラグインは、*config.yml*ファイルでそのプラグインのgemを`プラグイン`設定に追加すると有効にできます。 詳しい情報については、Jekyllのドキュメンテーションの「[Configuration](https://jekyllrb.com/docs/configuration/)」を参照してください。 + +サポートされているプラグインのリストについては、{% data variables.product.prodname_pages %}サイトで「[依存関係のバージョン](https://pages.github.com/versions/)」を参照してください。 特定のプラグインの使い方については、そのプラグインのドキュメンテーションを参照してください。 + +{% tip %} + +**ヒント：**{% data variables.product.prodname_pages %} gemを更新していれば、確実に最新のバージョンを使用できます。 詳しい情報については、{% data variables.product.prodname_pages %} サイトの「[Jekyll を使用して GitHub Pages サイトをローカルでテストする](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)」および「[依存関係バージョン](https://pages.github.com/versions/)」を参照してください。 + +{% endtip %} + +{% data variables.product.prodname_pages %}は、サポートされていないプラグインを使用してサイトをビルドすることはできません。 サポートされていないプラグインを使用するには、ローカルでサイトを生成してから、サイトの静的ファイルを{% data variables.product.product_name %}にプッシュできます。 + +### 構文の強調表示 + +サイトを読みやすくするには、{% data variables.product.product_name %}で強調表示されるのと同じように、{% data variables.product.prodname_pages %}サイトでコードスニペットを強調表示します。 {% data variables.product.product_name %}における構文の強調表示については、「[コードブロックの作成と強調表示](/articles/creating-and-highlighting-code-blocks)」を参照してください。 + +デフォルトでは、サイトのコードブロックはJekyllによって強調表示されます。 Jekyllは、[Rouge](https://github.com/jneen/rouge)ハイライターを使用します。これは[Pygments](http://pygments.org/)と互換性があります。 *_config.yml*ファイルでPygmentsを指定した場合、かわりにRougeが使用されます。 Jekyllはこれ以外の構文ハイライターを使用できないため、*_config.yml*ファイルで他の構文ハイライターを指定すると、ページビルド警告が発生します。 詳細については、「[{% data variables.product.prodname_pages %}サイトのJekyllビルドエラーについて](/articles/about-jekyll-build-errors-for-github-pages-sites)」を参照してください。 + +`highlight.js`など、他のハイライターを使用したい場合は、プロジェクトの*_config.yml*ファイルを更新して、Jekyllの構文強調表示を無効にする必要があります。 + +```yaml +kramdown: + syntax_highlighter_opts: + disable : true +``` + +お使いテーマに構文強調表示のCSSが含まれていない場合は、{% data variables.product.prodname_dotcom %}の構文強調表示CSSを生成し、プロジェクトの`style.css`ファイルに追加することができます。 + +```shell +$ rougify style github > style.css +``` + +### サイトをローカルでビルドする + +{% data reusables.pages.test-locally %} diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..e64c329745 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,62 @@ +--- +title: GitHub PagesサイトのJekyllビルドエラーについて +intro: 'ローカルで、または{% data variables.product.product_name %}上で{% data variables.product.prodname_pages %}サイトをビルド中にJekyllでエラーが発生した場合には、詳細情報を伴うエラーメッセージが示されます。' +redirect_from: + - /articles/viewing-jekyll-build-error-messages/ + - /articles/generic-jekyll-build-failures/ + - /articles/about-jekyll-build-errors-for-github-pages-sites + - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### 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" %} +- 変更をプッシュしたユーザーがメールアドレスを検証していない。 詳しい情報については、「[メールアドレスの検証](/articles/verifying-your-email-address)」を参照してください。{% endif %} +- デプロイキーでプッシュしている。 サイトのリポジトリへのプッシュを自動化する場合は、かわりにマシンユーザーを設定できます。 詳しい情報については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys#machine-users)」を参照してください。 +- 公開元をビルドするようにCIサービスを設定していない。 For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. 詳細は、Travis CIまたはCIサービスのドキュメンテーションで、「[ビルドのカスタマイズ](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)」を参照してください。 + +{% note %} + +**メモ:** サイトに対する変更は、その変更を{% data variables.product.product_name %}にプッシュしてから公開されるまでに、最大20分かかることがあります。 + +{% endnote %} + +Jekyllがサイトのビルドを試行せず、エラーが発生した場合は、ビルドエラーメッセージが表示されます。 Jekyll ビルドエラーメッセージには主に 2 つのタイプがあります。 +- 「Page build warning」メッセージは、ビルドは成功したものの、今後問題が生じないようにするために変更を行なう必要がある可能性が存在することを意味します。 +- 「Page build failed」メッセージは、ビルドが完了できなかったことを意味します。 Jekyll が失敗の理由を検出できた場合、説明を含むエラーメッセージが表示されます。 + +ビルドエラーのトラブルシューティングに関する詳しい情報については、「[{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーのトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)」を参照してください。 + +### Jekyll ビルドエラーメッセージを表示する + +サイトのテストをローカルで行なうことをお勧めします。それにより、ビルドエラーメッセージをコマンドラインで表示でき、変更を {% data variables.product.product_name %} にプッシュする前に、あらゆるビルドエラーに対処できます。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトをローカルでテストする](/articles/testing-your-github-pages-site-locally-with-jekyll)」を参照してください。 + +{% data variables.product.product_name %} サイトの公開元を更新するためプルリクエストを作成すると、そのプルリクエストの [**Checks**] タブでビルドエラーメッセージが表示されます。 詳しい情報については[ステータスチェックについて](/articles/about-status-checks)を参照してください。 + +{% data variables.product.product_name %} の公開元に変更をプッシュする際、{% data variables.product.prodname_pages %} はサイトのビルドを試みます。 ビルドが失敗すると、プライマリメールアドレスにメールが送信されます。 また、ビルドの警告についてのメールも送信されます。 {% data reusables.pages.build-failure-email-server %} + +{% data variables.product.product_name %} 上のビルドの失敗については、サイトのリポジトリの、[**Settings**] タブに表示されます。(ただし、ビルドの警告については表示されません。) + +各コミット後にエラーメッセージを表示するように、[Travis CI](https://travis-ci.org/) などのサードパーティサービスを設定できます。 + +1. 公開元のルートに、以下の内容で _Gemfile_ と呼ばれるファイルをまだ追加していない場合は、追加します。 + ```ruby + source `https://rubygems.org` + gem `github-pages` + ``` + +2. 選択したテストサービス用にサイトのリポジトリを設定します。 例えば、[Travis CI](https://travis-ci.org/) を利用するには、以下の内容の _.travis.yml_ ファイルを、公開元のルートに追加します。 + ```yaml + language: ruby + rvm: + - 2.3 + script: "bundle exec jekyll build" + ``` +3. サードパーティのテストサービス内で、リポジトリを有効にする必要があるかもしれません。 詳しい情報については、お使いのテストサービスのドキュメンテーションを参照してください。 diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..7645b09785 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,71 @@ +--- +title: Jekyll を使用して GitHub Pages サイトにテーマを追加する +intro: テーマを追加およびカスタマイズすることにより、Jekyll サイトをパーソナライズできます。 +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +リポジトリへの書き込み権限があるユーザは、Jekyll を使用して {% data variables.product.prodname_pages %} サイトにテーマを追加できます。 + +{% data reusables.pages.test-locally %} + +### テーマを追加する + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +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) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### テーマの CSS をカスタマイズする + +{% 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. _/assets/css/style.scss_ という新しいファイルを作成します。 +2. ファイルの先頭に、以下の内容を追加します。 + ```scss + --- + --- + + @import "{{ site.theme }}"; + ``` +3. カスタム CSS または Sass (インポートファイルも含む) があれば `@import` 行の直後に追加します。 + +### テーマの HTML レイアウトをカスタマイズする + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +1. {% data variables.product.prodname_dotcom %} 上で、テーマのソースリポジトリにアクセスします。 たとえば、Minima のソースリポジトリは https://github.com/jekyll/minima です。 +2. *_layouts* フォルダ内で、テーマの _default.html_ ファイルに移動します。 +3. ファイルのコンテンツをコピーします。 +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +6. *_layouts/default.html* というファイルを作成します。 +7. 先ほどコピーしたデフォルトのレイアウトコンテンツを貼り付けます。 +8. 必要に応じてレイアウトをカスタマイズします。 + +### 参考リンク + +- [新しいファイルの作成](/articles/creating-new-files) diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..a75e943244 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,72 @@ +--- +title: Jekyll を使用して GitHub Pages サイトにコンテンツを追加する +intro: '{% data variables.product.prodname_pages %} の Jekyll サイトに、新規ページや投稿を追加できます。' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/adding-content-to-your-github-pages-site-using-jekyll + - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +リポジトリへの書き込み権限があるユーザは、Jekyll を使用して {% data variables.product.prodname_pages %} サイトにコンテンツを追加できます。 + +### Jekyll サイトのコンテンツについて + +{% data variables.product.prodname_pages %} で Jekyll サイトにコンテンツを追加する前に、Jekyll サイトを作成する必要があります。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトを作成する](/articles/creating-a-github-pages-site-with-jekyll)」を参照してください。 + +Jekyll サイトのコンテンツとして 2 つの主なタイプは、ページと投稿です。 ページとは、特定の日付に紐付けられていない、「About」ページなどの独立したコンテンツです。 デフォルトの Jekyll サイトには、`about.md` という名前のファイルが含まれ、サイトの `YOUR-SITE-URL/about` でページとして表示されます。 このファイルのコンテンツを編集して、「About」ページをパーソナライズできます。また、新しいページを作成するため、「About」ページをテンプレートとして使用できます。 詳しい情報については、Jekyll ドキュメンテーションの「[Pages](https://jekyllrb.com/docs/pages/)」を参照してください。 + +投稿とは、ブログ記事のことです。 デフォルトの Jekyll サイトには、デフォルト投稿ファイルがある、`_posts` という名前のディレクトリが含まれています。 この投稿のコンテンツを編集し、デフォルト投稿を、新規投稿を作成するためのテンプレートとして使用できます。 詳しい情報については、Jekyllのドキュメンテーションの「[Posts](https://jekyllrb.com/docs/posts/)」を参照してください。 + +テーマには、デフォルトのレイアウト、およびサイトの新規ページや新規投稿に自動的に適用されるスタイルシートが含まれますが、これらのデフォルト設定はオーバーライドできます。 詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll](/articles/about-github-pages-and-jekyll#themes)」を参照してください。 + +{% data reusables.pages.about-front-matter %} + +{% data reusables.pages.test-locally %} + +### 新規ページをサイトに追加する + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. ページを作成するため、公開元のルートに _PAGE-NAME.md_ という名前の新規ファイルを作成します。_PAGE-NAME_ は、ページを示す、意味のあるファイル名に置き換えてください。 +4. 以下の YAML frontmatter を、ファイルの先頭に追加します。_PAGE TITLE_ はページのタイトルに、_URL-PATH_ はページの URL として指定したい URL に置き換えてください。 たとえば、サイトのベース URL が `https://octocat.github.io` で、_URL-PATH_ が `/about/contact/` である場合、ページの場所は `https://octocat.github.io/about/contact` となります。 + ```shell + layout: page + title: "PAGE TITLE" + permalink: /URL-PATH/ + ``` +5. frontmatter の下に、ページのコンテンツを追加します。 +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### 新規投稿をサイトに追加する + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. `_posts` ディレクトリに移動します。 +4. _YYYY-MM-DD-NAME-OF-POST.md_ という名前の新規ファイルを作成します。_YYYY-MM-DD_ は投稿の日時に、_NAME-OF-POST_ は投稿の名前に置き換えてください。 +4. 以下の YAML frontmatter を、ファイルの先頭に追加します。 _POST TITLE_ は投稿のタイトルに、 _YYYY-MM-DD hh:mm:ss -0000_ は投稿の日時に置き換え、投稿に追加したいカテゴリを _CATEGORY-1_、_CATEGORY-2_ のように好きなだけ追加し、カテゴリの名前に置き換えてください。 + ```shell + layout: post + title: "POST TITLE" + date: YYYY-MM-DD hh:mm:ss -0000 + categories: CATEGORY-1 CATEGORY-2 + ``` +5. frontmatter の下に、投稿のコンテンツを追加します。 +{% 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`. + +### 次のステップ + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000..786d1f4758 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,116 @@ +--- +title: Jekyll を使用して GitHub Pages サイトを作成する +intro: '新規または既存のリポジトリ内に、{% data variables.product.prodname_pages %} Jekyll を使用してサイトを作成できます。' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/creating-a-github-pages-site-with-jekyll + - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll +permissions: 'リポジトリの管理者権限があるユーザは、Jekyll を使用して {% data variables.product.prodname_pages %} サイトにコンテンツを作成できます。' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### 必要な環境 + +Jekyll を使用して {% data variables.product.prodname_pages %} サイトを作成する前に、Jekyll と Git をインストールする必要があります。 詳しい情報については、Jekyll ドキュメンテーションの [Installation](https://jekyllrb.com/docs/installation/) および「[Git のセットアップ](/articles/set-up-git)」を参照してください。 + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### サイト用にリポジトリを作成する + +{% data reusables.pages.new-or-existing-repo %} + +{% 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.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. リポジトリのローカルコピーがまだない場合、サイトのソースファイルを保存したい場所に移動します。_PARENT-FOLDER_ は、リポジトリを保存したいフォルダの名前に置き換えてください。 + ```shell + $ cd PARENT-FOLDER + ``` +3. ローカルの Git リポジトリをまだ初期化していない場合は、初期化します。 _REPOSITORY-NAME_ は、リポジトリの名前に置き換えてください。 + ```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. ディレクトリをリポジトリに変更します。 + ```shell + $ cd REPOSITORY-NAME + # Changes the working directory + ``` +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. + ```shell + $ mkdir docs + # Creates a new folder called docs + $ cd docs + ``` + サイトを `gh-pages` ブランチから公開する場合には、`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. To create a new Jekyll site, use the `jekyll new` command: + ```shell + $ jekyll new . + # Creates a Jekyll site in the current directory + ``` +8. Open the Gemfile that Jekyll created. +1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line. +1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to: + + ```shell + gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins + ``` + + Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)." + + The correct version Jekyll will be installed as a dependency of the `github-pages` gem. +10. Gemfile を保存して閉じます。 +11. From the command line, run `bundle update`. +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. +```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. リポジトリを {% data variables.product.product_name %} にプッシュします。 _BRANCH_ は、作業を行なっているブランチの名前に置き換えてください。 + ```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.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### 次のステップ + +サイトに新しいページを追加したり、投稿したりするには、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトにコンテンツを追加する](/articles/adding-content-to-your-github-pages-site-using-jekyll)」を参照してください。 + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md new file mode 100644 index 0000000000..27bf6ff473 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md @@ -0,0 +1,25 @@ +--- +title: Jekyll を使用して GitHub Pages サイトを設定する +intro: '静的サイトジェネレータとして広く利用されている Jekyll を使用して、{% 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 + - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..9f8f56b900 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,36 @@ +--- +title: Jekyll を使用して、GitHub Pages サイトの Markdown プロセッサを設定する +intro: 'Markdown プロセッサを選択して、{% data variables.product.prodname_pages %} サイトで Markdown をどのようにレンダリングするかを決めることができます。' +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 + - /github/working-with-github-pages/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: '*' +topics: + - pages +--- + +リポジトリへの書き込み権限があるユーザは、{% 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_dotcom %} フレーバーの Markdown はどちらのプロセッサでも使用できますが、{% data variables.product.product_name %} に表示される結果と一致するのは常に CommonMark プロセッサのみです。 + +{% data reusables.pages.navigate-site-repo %} +2. リポジトリの *_config.yml* ファイルを開きます。 +{% data reusables.repositories.edit-file %} +4. `markdown` で始まる行を見つけ、値を `kramdown` または `GFM`に変更します。 ![config.yml での Markdown 設定](/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 %} + +### 参考リンク + +- [kramdown のドキュメント](https://kramdown.gettalong.org/documentation.html) +- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/) diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000..d0fe6ae7e7 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,62 @@ +--- +title: Jekyll を使用して GitHub Pages サイトをローカルでテストする +intro: '{% data variables.product.prodname_pages %} サイトをローカルでビルドすると、サイトに対する変更のプレビューとテストを行うことができます。' +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 + - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +リポジトリへの書き込み権限があるユーザは、{% data variables.product.prodname_pages %} サイトをローカルでテストできます。 + +### 必要な環境 + +Jekyll を使用してサイトをテストする前に、以下の操作が必要です。 + - [Jekyll](https://jekyllrb.com/docs/installation/) をインストールする。 + - Jekyll サイトを作成する。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトを作成する](/articles/creating-a-github-pages-site-with-jekyll)」を参照してください。 + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### サイトをローカルでビルドする + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.pages.navigate-publishing-source %} +3. Run `bundle install`. +3. ローカルで Jekyll サイトを実行します. + ```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. サイトをプレビューするには、ウェブブラウザで `http://localhost:4000` を開きます。 + +### {% data variables.product.prodname_pages %} gem の更新 + +Jekyll は、頻繁に更新されているアクティブなオープンソースプロジェクトです。 お使いのコンピュータ上の `github-pages` gem が {% data variables.product.prodname_pages %} サーバー上の `github-pages` gem と比較して古くなっている場合は、ローカルでビルドしたときと {% data variables.product.product_name %} に公開したときで、サイトの見え方が異なることがあります。 こうならないように、お使いのコンピュータ上の `github-pages` gem は常にアップデートしておきましょう。 + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. `github-pages` gem をアップデートします。 + - Bundler をインストールしている場合は、`bundle update github-pages` を実行します。 + - Bundler をインストールしていない場合は、`gem update github-pages` を実行します。 + +### 参考リンク + +- Jekyll ドキュメンテーションの [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..83f2020f86 --- /dev/null +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,191 @@ +--- +title: GitHub Pages サイトの Jekyll ビルドエラーに関するトラブルシューティング +intro: 'Jekyll ビルドエラーのメッセージを利用して、{% 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 + - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### ビルドエラーのトラブルシューティング + +{% data variables.product.prodname_pages %} サイトをローカルで、または {% data variables.product.product_name %} 上でビルドしているときに 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" %} +- リポジトリがリポジトリサイズの制限を超えている。 詳しい情報については「[私のディスク容量はいくつですか？](/articles/what-is-my-disk-quota)」を参照してください。{% endif %} +- *_config.yml* ファイルで `source` の設定を変更した。 ビルドプロセス中に、この設定は {% data variables.product.prodname_pages %} によってオーバーライドされます。 +- 公開ソースにあるファイル名にコロン (`:`) が含まれている。コロンは使用できません。 + +具体的なエラーメッセージが表示された場合は、エラーメッセージに関する以下のトラブルシューティング情報を確認してください。 + +エラーを修正したら、ソースを公開しているサイトにその変更をプッシュし、{% data variables.product.product_name %} でもう一度ビルドを実行します。 + +### Config file error + +このエラーメッセージは、*_config.yml* ファイルに構文エラーがあるためにサイトのビルドに失敗したことを意味します。 + +トラブルシューティングの際は、*_config.yml* ファイルが次のルールに従っていることを確認してください。 + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +### Date is not a valid datetime + +このエラーは、サイトのいずれかのページに無効な日付データが含まれていることを意味します。 + +トラブルシューティングするには、エラーメッセージで示されたファイルおよびファイルのレイアウトで、日付関連の Liquid フィルタをコールしている箇所を探します。 日付関連の Liquid フィルタに渡される変数に、すべてのケースで値があることと、`nil`または `""` を渡していないことを確認します。 詳細は、Liquid のドキュメンテーションで「[Liquid フィルタ](https://help.shopify.com/en/themes/liquid/filters)」を参照してください。 + +### File does not exist in includes directory + +このエラーは、*_includes* ディレクトリに存在していないファイルをコードで参照していることを意味します。 + +{% data reusables.pages.search-for-includes %} 参照していたファイルのいずれかが *_includes* ディレクトリに存在しない場合は、そのファイルを *_includes* ディレクトリにコピーまたは移動してください。 + +### File is a symlink + +このエラーは、サイトの公開ソースに存在しないシンボリックリンクされたファイルをコードで参照していることを意味します。 + +{% data reusables.pages.search-for-includes %} 参照していたファイルのいずれかがシンボリックリンクされている場合は、そのファイルを *_includes* ディレクトリにコピーまたは移動してください。 + +### File is not properly UTF-8 encoded + +このエラーは、`日本語`などアルファベット以外の文字を使用したことを意味します。 + +トラブルシューティングするには、*_config.yml* ファイルに次の行を追加して UTF-8 エンコーディングを指定します。 +```yaml +encoding: UTF-8 +``` + +### Invalid highlighter language + +このエラーは、設定ファイルで [Rouge](https://github.com/jneen/rouge) または [Pygments](http://pygments.org/) 以外の構文ハイライターを指定したことを意味します。 + +トラブルシューティングするには、*_config.yml* ファイルを更新して [Rouge](https://github.com/jneen/rouge) または [Pygments](http://pygments.org/) を指定します。 詳しい情報については、「[{% data variables.product.product_name %} と Jekyll について](/articles/about-github-pages-and-jekyll#syntax-highlighting)」を参照してください。 + +### Invalid post date + +このエラーメッセージは、サイトでの投稿で、ファイル名または YAML フロントマターに無効な日付が含まれていることを意味します。 + +トラブルシューティングするには、日付がすべて YYYY-MM-DD HH:MM:SS 形式の UTC 時間で、実際のカレンダー日付であることを確認します。 UTC との時差があるタイムゾーンを指定する場合は、YYYY-MM-DD HH:MM:SS +/-TTTT 形式を使用し、たとえば `2014-04-18 11:30:00 +0800` のように指定します。 + +*_config.yml* ファイルで日付形式を指定している場合は、その形式が正しいことを確認してください。 + +### Invalid Sass or SCSS + +このエラーは、リポジトリに無効な内容の Sass または SCSS ファイルが含まれていることを意味します。 + +トラブルシューティングするには、エラーメッセージに含まれている行番号を確認して、無効な Sass または SCSS を探します。 今後のエラーを防ぐために、お好みのテキストエディター用の Sass または SCSS 文法チェッカーをインストールします。 + +### Invalid submodule + +このエラーは、適切に初期化されていないサブモジュールがリポジトリに含まれていることを意味します。 + +{% data reusables.pages.remove-submodule %} + +そのサブモジュールを使用する必要がある場合は、サブモジュールを参照するとき、必ず `https://` (`http://` ではなく) を使用し、そのサブモジュールをパブリックリポジトリに配置してください。 + +### Invalid YAML in data file + +このエラーは、*_data* フォルダの 1 つ以上のファイルに無効な YAML が含まれていることを意味します。 + +トラブルシューティングするには、*_data* フォルダの YAML ファイルが次のルールに従っていることを確認します。 + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +Jekyll データファイルの詳細は、Jekyll のドキュメンテーションで「[データファイル](https://jekyllrb.com/docs/datafiles/)」を参照してください。 + +### Markdown errors + +このエラーは、リポジトリ Markdown エラーがあることを意味します。 + +トラブルシューティングするには、必ずサポートされている Markdown プロセッサを使用するようにします。 詳細は、「[Jekyll を使用して、{% data variables.product.prodname_pages %} サイトの Markdown プロセッサを設定する](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)」を参照してください。 + +次に、エラーメッセージで示されているファイルが有効な Markdown 構文を使っていることを確認します。 詳細は、Daring Fireball の「[Markdown: 構文](https://daringfireball.net/projects/markdown/syntax)」を参照してください。 + +### Missing docs folder + +This error means that you have chosen the `docs` folder on a branch as your publishing source, but there is no `docs` folder in the root of your repository on that branch. + +To troubleshoot, if your `docs` folder was accidentally moved, try moving the `docs` folder back to the root of your repository on the branch you chose for your publishing source. `docs` フォルダを誤って削除した場合は、次のいずれかの方法が可能です。 +- Git を使用して削除を revert する、つまり取り消す。 詳細は、Git のドキュメンテーションで「[git-revert](https://git-scm.com/docs/git-revert.html)」を参照してください。 +- Create a new `docs` folder in the root of your repository on the branch you chose for your publishing source and add your site's source files to the folder. 詳細は「[新しいファイルを作成する](/articles/creating-new-files)」を参照してください。 +- 公開ソースを変更する。 詳細は「[{% data variables.product.prodname_pages %} の公開ソースを設定する](/articles/configuring-a-publishing-source-for-github-pages)」を参照してください。 + +### Missing submodule + +このエラーは、存在しない、または適切に初期化されていないサブモジュールがリポジトリに含まれていることを意味します。 + +{% data reusables.pages.remove-submodule %} + +サブモジュールを使用する必要がある場合は、そのサブモジュールを初期化します。 詳細は、_Pro Git_ ブックで「[Git Tools - Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules)」を参照してください。 + +### Relative permalinks configured + +このエラーは、*_config.yml* ファイルで相対パーマリンクを使用していることを意味します。相対パーマリンクは {% data variables.product.prodname_pages %} でサポートされていません。 + +パーマリンクとは、サイトの特定ページを参照している恒久的な URL です。 絶対パーマリンクはサイトのルートから始まり、相対パーマリンクは参照先ページを含むフォルダで始まります。 {% data variables.product.prodname_pages %} と Jekyll では、相対パーマリンクがサポートされなくなっています。 詳細は、Jekyll のドキュメンテーションで「[パーマリンク](https://jekyllrb.com/docs/permalinks/)」を参照してください。 + +トラブルシューティングするには、*_config.yml* ファイルから `relative_permalinks` の行を削除し、サイトに相対パーマリンクがある場合は絶対パーマリンクに直します。 詳細は「[リポジトリのファイルを編集する](/articles/editing-files-in-your-repository)」を参照してください。 + +### Symlink does not exist within your site's repository + +このエラーは、サイトの公開ソースに存在しないシンボリックリンク (symlink) がサイトに含まれていることを意味します。 シンボリックリンクの詳細は、Wikipedia で「[Symbolic link](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 %} + +### Syntax error in 'for' loop + +このエラーは、 Liquid の `for` ループ宣言で無効な構文が含まれていることを意味します。 + +トラブルシューティングするには、エラーメッセージで示されているファイルですべての `for` ループの構文が正しいことを確認します。 `for` ループの正しい構文についての詳しい情報は、Liquid のドキュメンテーションで「[反復タグ](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)」を参照してください。 + +### Tag not properly closed + +このエラーメッセージは、コードに含まれる論理タグが正しく閉じていないことを意味します。 たとえば、{% raw %}`{% capture example_variable %}` は `{% endcapture %}`{% endraw %} で閉じる必要があります。 + +トラブルシューティングするには、エラーメッセージで示されているファイルの論理タグがすべて適切に閉じられていることを確認します。 詳細は、Liquid のドキュメンテーションで「[Liquid タグ](https://help.shopify.com/en/themes/liquid/tags)」を参照してください。 + +### Tag not properly terminated + +このエラーは、正しく閉じられていない出力タグがコードに含まれていることを意味します。 たとえば、{% raw %}`{{ page.title }}`{% endraw %} となるはずが {% raw %}`{{ page.title }`{% endraw %} となっているような場合です。 + +トラブルシューティングするには、エラーメッセージで示されているファイルの出力タグがすべて `}}` で適切に閉じられていることを確認します。 詳細は、Liquid のドキュメンテーションで「[Liquid オブジェクト](https://help.shopify.com/en/themes/liquid/objects)」を参照してください。 + +### Unknown tag error + +このエラーは、コードに認識されない Liquid タグが含まれていることを意味します。 + +トラブルシューティングするには、エラーメッセージで示されているファイルの Liquid タグがすべて Jekyll のデフォルトの変数に一致し、タグ名に誤入力がないことを確認します。 For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation. + +認識されないタグの主な原因は、サポート対象外のプラグインです。 サイトをローカルで生成し、静的なファイルを {% data variables.product.product_name %} にプッシュすることで、サポート対象外のプラグインを使用している場合は、そのプラグインで Jekyll のデフォルトの変数と異なるタグが使われていないかどうか確認してください。 サポート対象のプラグインについては、「[{% data variables.product.prodname_pages %} と Jekyll について](/articles/about-github-pages-and-jekyll#plugins)」を参照してください。 diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md index 53b2dc4976..bf4295afab 100644 --- a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md @@ -170,7 +170,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap 同様に、[認証済みのユーザにリポジトリを表示][user repos api]できます。 ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -207,7 +207,7 @@ $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=own 詳細情報や設定オプションを含んだいくつかのJSONを`POST`する必要があります。 ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -242,7 +242,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog GitHub.comと同じように、Issues APIは認証されたユーザがIssueを表示するためのメソッドをいくつか提供します。 [すべてのIssueを表示][get issues api]するには、`GET /issues`を呼び出します。 ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -250,7 +250,7 @@ $ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ /orgs//issues`を呼び出します。 ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -283,7 +283,7 @@ Issueのリストでページネーションを行う方法を確認したので Issueを作成するには認証される必要があるので、ヘッダにOAuthトークンを渡します。 また、タイトル、本文、およびJSONの本文にあるラベルを、Issueを作成したい、リポジトリ以下の`/issues`パスに渡します。 ```shell -$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ +$ curl -i -H 'Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/ja-JP/content/rest/reference/enterprise-admin.md b/translations/ja-JP/content/rest/reference/enterprise-admin.md index bd40396c8b..aed4ee4bd9 100644 --- a/translations/ja-JP/content/rest/reference/enterprise-admin.md +++ b/translations/ja-JP/content/rest/reference/enterprise-admin.md @@ -100,7 +100,7 @@ IdP は、SCIM エンドポイントとして `{% data variables.product.api_url {% note %} -**注釈:** Enterprise SCIM API は、[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Enterprise でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 +**注釈:** Enterprise SCIM API は、[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Enterprise でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/rest/reference/migrations.md b/translations/ja-JP/content/rest/reference/migrations.md index 99d908655f..bb8500f046 100644 --- a/translations/ja-JP/content/rest/reference/migrations.md +++ b/translations/ja-JP/content/rest/reference/migrations.md @@ -16,7 +16,7 @@ topics: ## Organization -移行 API を使用できるのは、認証済みの Organization オーナーのみです。 詳細については、「[Organization の権限レベル](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)」と「[その他の認証方式](/rest/overview/other-authentication-methods)」を参照してください。 +移行 API を使用できるのは、認証済みの Organization オーナーのみです。 For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/ja-JP/content/rest/reference/repos.md b/translations/ja-JP/content/rest/reference/repos.md index 15e5e3954b..52572a33e8 100644 --- a/translations/ja-JP/content/rest/reference/repos.md +++ b/translations/ja-JP/content/rest/reference/repos.md @@ -193,7 +193,7 @@ Repo Merging API は、リポジトリ内にあるブランチのマージをサ ## ページ -{% data variables.product.prodname_pages %} API は、{% data variables.product.prodname_pages %} の設定や、ビルドのステータスについての情報を取得します。 Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/github/working-with-github-pages/about-github-pages)」を参照してください。 +{% data variables.product.prodname_pages %} API は、{% data variables.product.prodname_pages %} の設定や、ビルドのステータスについての情報を取得します。 Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。 レスポンスに `status` キーを持つ {% data variables.product.prodname_pages %} API エンドポイントにおいては、値は以下のいずれかになります。 * `null`: サイトはまだビルドされていません。 @@ -205,7 +205,7 @@ Repo Merging API は、リポジトリ内にあるブランチのマージをサ GitHub Pages サイトの情報を返す {% data variables.product.prodname_pages %} API エンドポイントにおいては、JSON のレスポンスには以下が含まれます。 * `html_url`: レンダリングされた Pages サイトの絶対 URL (スキームを含む) 。 たとえば、`https://username.github.io` などです。 * `source`: レンダリングされた Pages サイトのソースブランチおよびディレクトリを含むオブジェクト。 これは以下のものが含まれます。 - - `branch`: [サイトのソースファイル](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)を公開するために使用するリポジトリのブランチ。 たとえば、_main_ or _gh-pages_ などです。 + - `branch`: [サイトのソースファイル](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)を公開するために使用するリポジトリのブランチ。 たとえば、_main_ or _gh-pages_ などです。 - `path`: サイトの公開元のリポジトリディレクトリ。 `/` または `/docs` のどちらかとなります。 {% for operation in currentRestOperations %} diff --git a/translations/ja-JP/content/rest/reference/scim.md b/translations/ja-JP/content/rest/reference/scim.md index 6c0a510c05..f82adacbee 100644 --- a/translations/ja-JP/content/rest/reference/scim.md +++ b/translations/ja-JP/content/rest/reference/scim.md @@ -14,7 +14,7 @@ SCIM API は SCIM を有効にしたアイデンティティプロバイダ (IdP {% note %} -**注釈:** SCIM API は、[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Organization でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 +**注釈:** SCIM API は、[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上の Organization でのみ使用できます。 SCIM に関する詳細は「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/content/rest/reference/teams.md b/translations/ja-JP/content/rest/reference/teams.md index d74c370fdb..79f33432c8 100644 --- a/translations/ja-JP/content/rest/reference/teams.md +++ b/translations/ja-JP/content/rest/reference/teams.md @@ -18,7 +18,7 @@ topics: ## ディスカッション -Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." ディスカッションの投稿に対するコメントの詳細については、「[Team ディスカッションのコメント API](/rest/reference/teams#discussion-comments)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。 +Team ディスカッション API を使用すると、Team のページに投稿されたディスカッションを取得、作成、編集、削除できます。 Team のディスカッションは、リポジトリやプロジェクトに原生されない会話をするために利用できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッション投稿を作成や表示できます。 For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." ディスカッションの投稿に対するコメントの詳細については、「[Team ディスカッションのコメント API](/rest/reference/teams#discussion-comments)」を参照してください。 この API は、Team の Organization の、認証済みメンバーのみが利用できます。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -26,7 +26,7 @@ Team ディスカッション API を使用すると、Team のページに投 ## ディスカッションコメント -Team ディスカッションコメント API を使用すると、[Team ディスカッション](/rest/reference/teams#discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." この API は、Team の Organization の、認証済みメンバーのみが利用できます。 +Team ディスカッションコメント API を使用すると、[Team ディスカッション](/rest/reference/teams#discussions)投稿のコメントを取得、作成、編集、削除できます。 Team の [Organization](/rest/reference/orgs) に属する全メンバーが、公開のディスカッションについたコメントを作成や表示できます。 For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." この API は、Team の Organization の、認証済みメンバーのみが利用できます。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -39,7 +39,7 @@ Team ディスカッションコメント API を使用すると、[Team ディ {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**ノート: ** Organizationのアイデンティティプロバイダ（Idp）でTeamに同期をセットアップしている場合、Teamのメンバーシップを変更するためのこのAPIを使おうとすると、エラーが返されます。 グループのメンバーシップを管理するためにIdpにアクセスできるなら、GitHubのTeamメンバーシップをアイデンティティプロバイダを通じて管理できます。そうすれば、Organizationで自動的にTeamメンバーの追加や削除が行われます。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。 +**ノート: ** Organizationのアイデンティティプロバイダ（Idp）でTeamに同期をセットアップしている場合、Teamのメンバーシップを変更するためのこのAPIを使おうとすると、エラーが返されます。 グループのメンバーシップを管理するためにIdpにアクセスできるなら、GitHubのTeamメンバーシップをアイデンティティプロバイダを通じて管理できます。そうすれば、Organizationで自動的にTeamメンバーの追加や削除が行われます。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。 {% endnote %} @@ -54,7 +54,7 @@ Team ディスカッションコメント API を使用すると、[Team ディ Team Synchronization API では、{% data variables.product.product_name %} Team と外部アイデンティティプロバイダ (IdP) グループとの間の接続を管理できます。 この API を使用するには、認証されたユーザーがチームメンテナまたは Team に関連づけられた Organization のコードオーナーである必要があります。 また、認証に使用するトークンも、お使いの IdP (SSO) プロバイダーで使用するための認可を受けている必要があります。 詳しい情報についてはSAML シングルサインオンの Organization で使うために個人アクセストークンを認可するを参照してください。 -Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理できます。 Team Synchronization API を使用するには、チーム同期が有効である必要があります。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。 +Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理できます。 Team Synchronization API を使用するには、チーム同期が有効である必要があります。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} diff --git a/translations/ja-JP/data/release-notes/2-20/15.yml b/translations/ja-JP/data/release-notes/2-20/15.yml index aa3c664487..1d49fea65e 100644 Binary files a/translations/ja-JP/data/release-notes/2-20/15.yml and b/translations/ja-JP/data/release-notes/2-20/15.yml differ diff --git a/translations/ja-JP/data/release-notes/2-21/12.yml b/translations/ja-JP/data/release-notes/2-21/12.yml index 2771ffc8b7..6b871ba524 100644 --- a/translations/ja-JP/data/release-notes/2-21/12.yml +++ b/translations/ja-JP/data/release-notes/2-21/12.yml @@ -6,7 +6,7 @@ sections: bugs: - 'baneldログに秒とマイクロ秒の間のセパレータが欠けていました。 {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' - 'Enterpriseアカウントの"Repository visibility change"ポリシーが"Enabled"に設定されている場合、OrganizationオーナーがOrganization内のリポジトリの可視性を変更できませんでした。 {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - - '監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。{% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + - '監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。{{% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' known_issues: - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/17.yml b/translations/ja-JP/data/release-notes/2-21/17.yml index 2eaabd3407..e8bc1fe868 100644 --- a/translations/ja-JP/data/release-notes/2-21/17.yml +++ b/translations/ja-JP/data/release-notes/2-21/17.yml @@ -1,6 +1,6 @@ --- date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. +intro: 複数のお客様に影響する重大なバグのため、ダウンロードは無効になりました。修正は次回のパッチで利用可能になります。 sections: security_fixes: - '**高:** GitHubPagesのサイトをビルドする際に利用される可能性があるリモートコード実行の脆弱性が、GitHub Enterprise Serverで特定されました。GitHub Pagesが使用するユーザが制御する設定オプションが十分に厳密ではなく、環境変数を上書きできてしまい、GitHub Enterprise Serverインスタンス上でコマンドを実行できてしまいます。この脆弱性を利用するには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.0.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.3、2.22.9、2.21.17で修正されました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告され、CVE-2021-22864が割り当てられました。' @@ -18,8 +18,8 @@ sections: - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - リポジトリへのプッシュをコマンドラインで行うと、セキュリティアラートが報告されません。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance: + ログのローテーションが新しいログファイルへの移行をサービスに通知するのに失敗し、古いログファイルが使われ続け、最終的にルートディスクの領域が枯渇してしまうことがあります。 + この問題を緩和し、回避するために、以下のコマンドを[管理シェル](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH)で実行するか、 [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)あるいは[GitHub Premium Support](https://premium.githubsupport.com/)に連絡して支援を求めてください。 ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/ja-JP/data/release-notes/2-21/18.yml b/translations/ja-JP/data/release-notes/2-21/18.yml new file mode 100644 index 0000000000..e0f34bb0a9 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/18.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**高:** GitHub Appの[Web認証フロー](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow)から生成されたアクセストークンに対し、適切な権限が許可されていなくてもREST APIを通じてプライベートなリポジトリのメタデータを読めるようにしてしまう、不適切なアクセス制御の脆弱性がGitHub Enterprise Serverで特定されました。この脆弱性を利用するには、攻撃者はそのインスタンス上でGitHub Appを作成し、Web認証フローを通じてそのアプリケーションを認証するユーザが必要です。返されるプライベートリポジトリのメタデータは、そのトークンが特定するユーザが所有するリポジトリに限定されます。この脆弱性は3.0.4以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.4、2.22.10、2.21.18で修正されました。この脆弱性にはCVE-2021-22865が割り当てられ、 [GitHub Bug Bounty Program](https://bounty.github.com)を通じて報告されました。" + - パッケージは最新のセキュリティバージョンにアップデートされました。 + bugs: + - ログローテーションの一部としてサービスが新しいログファイルに移行せず、ディスクの使用量が増大しました。 + - インターナルリポジトリの検索結果上のラベルが"Internal"ではなく"Private"と表示されました。 + known_issues: + - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。 + - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 + - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 + - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 + - リポジトリへのプッシュをコマンドラインで行うと、セキュリティアラートが報告されません。 diff --git a/translations/ja-JP/data/release-notes/2-21/6.yml b/translations/ja-JP/data/release-notes/2-21/6.yml index 8638d1d9cd..1026a01102 100644 Binary files a/translations/ja-JP/data/release-notes/2-21/6.yml and b/translations/ja-JP/data/release-notes/2-21/6.yml differ diff --git a/translations/ja-JP/data/release-notes/2-22/10.yml b/translations/ja-JP/data/release-notes/2-22/10.yml new file mode 100644 index 0000000000..28b70872e1 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-22/10.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**高:** GitHub Appの[Web認証フロー](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow)から生成されたアクセストークンに対し、適切な権限が許可されていなくてもREST APIを通じてプライベートなリポジトリのメタデータを読めるようにしてしまう、不適切なアクセス制御の脆弱性がGitHub Enterprise Serverで特定されました。この脆弱性を利用するには、攻撃者はそのインスタンス上でGitHub Appを作成し、Web認証フローを通じてそのアプリケーションを認証するユーザが必要です。返されるプライベートリポジトリのメタデータは、そのトークンが特定するユーザが所有するリポジトリに限定されます。この脆弱性は3.0.4以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.4、2.22.10、2.21.18で修正されました。この脆弱性にはCVE-2021-22865が割り当てられ、 [GitHub Bug Bounty Program](https://bounty.github.com)を通じて報告されました。" + - パッケージは最新のセキュリティバージョンにアップデートされました。 + bugs: + - GitHub Enterprise 11.10.x以前で設定されたタイムゾーンが一部のサービスで利用されず、デフォルトのUTC時間になっていました。 + - ログローテーションの一部としてサービスが新しいログファイルに移行せず、ディスクの使用量が増大しました。 + - インターナルリポジトリの検索結果上のラベルが"Internal"ではなく"Private"と表示されました。 + known_issues: + - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。 + - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 + - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 + - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 diff --git a/translations/ja-JP/data/release-notes/2-22/4.yml b/translations/ja-JP/data/release-notes/2-22/4.yml index 0fb3aa956a..12194fda0b 100644 --- a/translations/ja-JP/data/release-notes/2-22/4.yml +++ b/translations/ja-JP/data/release-notes/2-22/4.yml @@ -7,7 +7,7 @@ sections: - baneldログに秒とマイクロ秒の間のセパレータが欠けていました。 {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} - ホットパッチでGHESをアップグレードした後、`ghe-actions-precheck`及び`ghe-packages-precheck`コマンドが`"docker load" accepts no arguments`というエラーで失敗します。{% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} - Enterpriseアカウントの"Repository visibility change"ポリシーが"Enabled"に設定されている場合、OrganizationオーナーがOrganization内のリポジトリの可視性を変更できませんでした。 {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} - - 監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。{% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + - 監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。{{% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} known_issues: - 新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/9.yml b/translations/ja-JP/data/release-notes/2-22/9.yml index 586df30031..6803e9f59c 100644 --- a/translations/ja-JP/data/release-notes/2-22/9.yml +++ b/translations/ja-JP/data/release-notes/2-22/9.yml @@ -1,6 +1,6 @@ --- date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. +intro: 複数のお客様に影響する重大なバグのため、ダウンロードは無効になりました。修正は次回のパッチで利用可能になります。 sections: security_fixes: - '**高:** GitHubPagesのサイトをビルドする際に利用される可能性があるリモートコード実行の脆弱性が、GitHub Enterprise Serverで特定されました。GitHub Pagesが使用するユーザが制御する設定オプションが十分に厳密ではなく、環境変数を上書きできてしまい、GitHub Enterprise Serverインスタンス上でコマンドを実行できてしまいます。この脆弱性を利用するには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.0.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.3、2.22.9、2.21.17で修正されました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告され、CVE-2021-22864が割り当てられました。' @@ -24,8 +24,8 @@ sections: - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance: + ログのローテーションが新しいログファイルへの移行をサービスに通知するのに失敗し、古いログファイルが使われ続け、最終的にルートディスクの領域が枯渇してしまうことがあります。 + この問題を緩和し、回避するために、以下のコマンドを[管理シェル](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH)で実行するか、 [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)あるいは[GitHub Premium Support](https://premium.githubsupport.com/)に連絡して支援を求めてください。 ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/ja-JP/data/release-notes/3-0/0.yml b/translations/ja-JP/data/release-notes/3-0/0.yml index a903749486..a8f4b694cc 100644 --- a/translations/ja-JP/data/release-notes/3-0/0.yml +++ b/translations/ja-JP/data/release-notes/3-0/0.yml @@ -128,12 +128,12 @@ sections: - ユーザが、すべてのチェックボックスをチェックすることなく必須のメッセージを閉じることができます。 - '[pre-receiveフックスクリプト](/admin/policies/enforcing-policy-with-pre-receive-hooks)は一時ファイルを書くことができず、そのためにスクリプトの実行が失敗することがあります。pre-receiveフックを使うユーザは、ステージング環境でスクリプトが書き込みアクセス権を必要とするかを確認するためのテストをするべきです。' - リポジトリの[デプロイキー](/developers/overview/managing-deploy-keys)が、LFSオブジェクトを含むリポジトリで使用できません。 - - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 - 依存関係グラフがPythonの`setup.py`マニフェストファイルのパースに失敗し、HTTP 500エラーがログに残されます。これが重複されるロギングの問題と組み合わさると、ルートボリュームの使用率が増大します。 - レース条件によって依存関係グラフデータベースの移行が失敗したように見えることがあります。 - 以前のGitHub Enterprise Serverのリリースからアップグレードされた、カスタムのタイムゾーンを持つインスタンスは、Web UIに不正確なタイムスタンプがあることがあります。 - - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). + - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。 deprecations: - heading: GitHub Enterprise Server 2.19の非推奨化 diff --git a/translations/ja-JP/data/release-notes/3-0/1.yml b/translations/ja-JP/data/release-notes/3-0/1.yml index 36d0bcedf8..c665554e37 100644 --- a/translations/ja-JP/data/release-notes/3-0/1.yml +++ b/translations/ja-JP/data/release-notes/3-0/1.yml @@ -40,11 +40,11 @@ sections: - 'ユーザが、すべてのチェックボックスをチェックすることなく必須のメッセージを閉じることができます。' - '[pre-receiveフックスクリプト](/admin/policies/enforcing-policy-with-pre-receive-hooks)は一時ファイルを書くことができず、そのためにスクリプトの実行が失敗することがあります。pre-receiveフックを使うユーザは、ステージング環境でスクリプトが書き込みアクセス権を必要とするかを確認するためのテストをするべきです。' - 'リポジトリの[デプロイキー](/developers/overview/managing-deploy-keys)が、LFSオブジェクトを含むリポジトリで使用できません。' - - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 - 'Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。' - '依存関係グラフがJavaScriptの`yarn.lock`マニフェストファイルのパースに失敗し、ログにHTTP 500エラーが残ります。' - '以前のGitHub Enterprise Serverのリリースからアップグレードされた、カスタムのタイムゾーンを持つインスタンスは、Web UIに不正確なタイムスタンプがあることがあります。' - - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).' + - 'Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。' - | ユーザは、アバターのようなアセットがロードされないことや、コードのプッシュ/プルの失敗を体験するかもしれません。これは、`haproxy-cluster-proxy`サービス内のPIDミスマッチによって生じることがあります。影響されたインスタンスがあるかは、以下のようにして判断します。 diff --git a/translations/ja-JP/data/release-notes/3-0/2.yml b/translations/ja-JP/data/release-notes/3-0/2.yml index 11527b3c07..e72af6e790 100644 --- a/translations/ja-JP/data/release-notes/3-0/2.yml +++ b/translations/ja-JP/data/release-notes/3-0/2.yml @@ -28,9 +28,9 @@ sections: - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)もしくは[GitHub Premium Support](https://premium.githubsupport.com/)にお問い合わせください。 - - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 - - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). + - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。 - | ユーザは、アバターのようなアセットがロードされないことや、コードのプッシュ/プルの失敗を体験するかもしれません。これは、`haproxy-cluster-proxy`サービス内のPIDミスマッチによって生じることがあります。影響されたインスタンスがあるかは、以下のようにして判断します。 diff --git a/translations/ja-JP/data/release-notes/3-0/3.yml b/translations/ja-JP/data/release-notes/3-0/3.yml index 458cbea7ee..6668da7e69 100644 --- a/translations/ja-JP/data/release-notes/3-0/3.yml +++ b/translations/ja-JP/data/release-notes/3-0/3.yml @@ -1,6 +1,6 @@ --- date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. +intro: 複数のお客様に影響する重大なバグのため、ダウンロードは無効になりました。修正は次回のパッチで利用可能になります。 sections: security_fixes: - '**高:** GitHubPagesのサイトをビルドする際に利用される可能性があるリモートコード実行の脆弱性が、GitHub Enterprise Serverで特定されました。GitHub Pagesが使用するユーザが制御する設定オプションが十分に厳密ではなく、環境変数を上書きできてしまい、GitHub Enterprise Serverインスタンス上でコマンドを実行できてしまいます。この脆弱性を利用するには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.0.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.3、2.22.9、2.21.17で修正されました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告され、CVE-2021-22864が割り当てられました。' @@ -27,12 +27,12 @@ sections: - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)もしくは[GitHub Premium Support](https://premium.githubsupport.com/)にお問い合わせください。 - - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 - - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). + - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance: + ログのローテーションが新しいログファイルへの移行をサービスに通知するのに失敗し、古いログファイルが使われ続け、最終的にルートディスクの領域が枯渇してしまうことがあります。 + この問題を緩和し、回避するために、以下のコマンドを[管理シェル](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH)で実行するか、 [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)あるいは[GitHub Premium Support](https://premium.githubsupport.com/)に連絡して支援を求めてください。 ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/ja-JP/data/release-notes/3-0/4.yml b/translations/ja-JP/data/release-notes/3-0/4.yml new file mode 100644 index 0000000000..da9f9f66b4 --- /dev/null +++ b/translations/ja-JP/data/release-notes/3-0/4.yml @@ -0,0 +1,25 @@ +--- +date: '2021-04-01' +intro: '{% data variables.product.prodname_ghe_server %} 3.0以降では最小のインフラストラクチャの要件が増加されました。詳しい情報については「[GitHub Enterprise Server 3.0以降に対する最小要件について](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)」を参照してください。' +sections: + security_fixes: + - "**高:** GitHub Appの[Web認証フロー](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow)から生成されたアクセストークンに対し、適切な権限が許可されていなくてもREST APIを通じてプライベートなリポジトリのメタデータを読めるようにしてしまう、不適切なアクセス制御の脆弱性がGitHub Enterprise Serverで特定されました。この脆弱性を利用するには、攻撃者はそのインスタンス上でGitHub Appを作成し、Web認証フローを通じてそのアプリケーションを認証するユーザが必要です。返されるプライベートリポジトリのメタデータは、そのトークンが特定するユーザが所有するリポジトリに限定されます。この脆弱性は3.0.4以前のすべてのバージョンのGitHub Enterprise Serverに影響し、3.0.4、2.22.10、2.21.18で修正されました。この脆弱性にはCVE-2021-22865が割り当てられ、 [GitHub Bug Bounty Program](https://bounty.github.com)を通じて報告されました。" + - パッケージは最新のセキュリティバージョンにアップデートされました。 + bugs: + - メンテナンスモードが有効になっている場合に、一部のサービスは実行中であることが期待され、リストに表示されるべきではないにも関わらず、"active processes"としてリストされ続けました。 + - GitHub Actionsを有効化して2.22.xから3.0.xへアップグレードした後、セルフホストランナーのバージョンが更新されず、セルフホストの更新が行われませんでした。 + - 古いGitHub Pagesのビルドがクリーンアップされず、ディスク使用量の増大につながりました。 + - 'アクティブなレプリカ上で`memcached`が動作していませんでした。' + - GitHub Actionsが有効化されている場合に、ファイル権限の更新時に更新が失敗しました。 + - GitHub Enterprise 11.10.x以前で設定されたタイムゾーンが一部のサービスで利用されず、デフォルトのUTC時間になっていました。 + - ログローテーションの一部としてサービスが新しいログファイルに移行せず、ディスクの使用量が増大しました。 + - コマンドラインユーティリティの`ghe-saml-mapping-csv`が警告メッセージを生成しました。 + - インターナルリポジトリの検索結果上のラベルが"Internal"ではなく"Private"と表示されました。 + known_issues: + - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。 + - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 + - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 + - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 + - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 + - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 diff --git a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md index 9dc66e2e3f..106536697d 100644 --- a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md @@ -4,5 +4,7 @@ | `completed_workflow_run` | ワークフローのステータスが`completed`に変更されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 | | `created_workflow_run` | ワークフローの実行が作成されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[サンプルワークフローの作成](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)」を参照してください。 | | `delete_workflow_run` | ワークフローの実行が削除されたときにトリガーされます。 詳しい情報については「[ワークフローの実行の削除](/actions/managing-workflow-runs/deleting-a-workflow-run)」を参照してください。 | +| `disable_workflow` | Triggered when a workflow is disabled. | +| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`. | | `delete_workflow_run` | ワークフローの実行が再実行されたときにトリガーされます。 詳しい情報については「[ワークフローの再実行](/actions/managing-workflow-runs/re-running-a-workflow)」を参照してください。 | | `prepared_workflow_job` | ワークフロージョブが開始されたときにトリガーされます。 ジョブに渡されたシークレットのリストを含みます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。 | diff --git a/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md index 7bea00d8da..8d489c69d2 100644 --- a/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md +++ b/translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md @@ -2,4 +2,4 @@ リポジトリ管理者がOrganizationのリポジトリで{% data variables.product.prodname_advanced_security %}の機能を有効化できるようにするかをコントロールするポリシーを適用できます。 Enterpriseアカウントが所有するすべてのOrganizationに対して、あるいは選択した個々のOrganizationに対してポリシーを設定できます。 -Organizationに対して{% data variables.product.prodname_advanced_security %}を不許可にすれば、リポジトリ管理者が追加のリポジトリで{% data variables.product.prodname_advanced_security %}の機能を有効化できないようにすることができますが、そうしても機能がすでに有効化されていたリポジトリでは機能は無効化されません。 {% data variables.product.prodname_advanced_security %}機能の設定に関する詳しい情報については「[Organizationのセキュリティ及び分析の設定管理](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」あるいは「[リポジトリのセキュリティ及び分析の設定管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 +Organizationに対して{% data variables.product.prodname_advanced_security %}を不許可にすれば、リポジトリ管理者が追加のリポジトリで{% data variables.product.prodname_advanced_security %}の機能を有効化できないようにすることができますが、そうしても機能がすでに有効化されていたリポジトリでは機能は無効化されません。 {% data variables.product.prodname_advanced_security %}機能の設定に関する詳しい情報については「[Organizationのセキュリティ及び分析の設定管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」あるいは「[リポジトリのセキュリティ及び分析の設定管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/branches/set-default-branch.md b/translations/ja-JP/data/reusables/branches/set-default-branch.md index f212f673a1..225b533a0a 100644 --- a/translations/ja-JP/data/reusables/branches/set-default-branch.md +++ b/translations/ja-JP/data/reusables/branches/set-default-branch.md @@ -1 +1 @@ -新しいリポジトリのためのデフォルトブランチの名前を設定できます。 詳しい情報については、「[リポジトリのデフォルトブランチの管理](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)」、「[Organization内のリポジトリのデフォルトブランチ名の管理](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)」、{% if currentVersion == "free-pro-team@latest" %}「[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 %}「[Enterpriseでのリポジトリ管理ポリシーの強制](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)」{% endif %}を参照してください。 +新しいリポジトリのためのデフォルトブランチの名前を設定できます。 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](/organizations/managing-organization-settings/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 %} diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-visibility.md index 8aa3627a20..5d05ec6e3d 100644 --- a/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ 課題のためのリポジトリは、パブリックにもプライベートにもできます。 プライベートリポジトリを使うと、学生あるいはTeamだけが提供されたフィードバックを見ることができます。 -また、課題のためのリポジトリに対する管理権限を学生に与えるかを決定することもできます。 学生が課題のリポジトリに対して管理タスクを行えなければならないのであれば、管理権限を与えてください。 詳しい情報については「[リポジトリの可視性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」及び「[Organizationのためのリポジトリの権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)」を参照してください。 +また、課題のためのリポジトリに対する管理権限を学生に与えるかを決定することもできます。 学生が課題のリポジトリに対して管理タスクを行えなければならないのであれば、管理権限を与えてください。 詳しい情報については「[リポジトリの可視性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」及び「[Organizationのためのリポジトリの権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)」を参照してください。 "Repository visibility（リポジトリの可視性）"の下で、可視性を選択してください。 あるいは、**Grant students admin access to their repository（リポジトリに対する管理アクセスを学生に付与）**を選択してください。 diff --git a/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md b/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md index 1360bac28b..22fff854a2 100644 --- a/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. Organizationのリスト中で、クラスルームに使いたいOrganizationをクリックしてください。 あるいは、新しいOrganizationを作成することもできます。 詳しい情報については、「[新しい Organization をゼロから作成する](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)」を参照してください。 ![新しいクラスルームを作成する、Organizationリスト中のOrganization](/assets/images/help/classroom/click-organization.png) +1. Organizationのリスト中で、クラスルームに使いたいOrganizationをクリックしてください。 あるいは、新しいOrganizationを作成することもできます。 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。 ![新しいクラスルームを作成する、Organizationリスト中のOrganization](/assets/images/help/classroom/click-organization.png) 1. クラスルーム名を入力してください。 ![クラスルーム名を入力するテキストフィールド](/assets/images/help/classroom/type-classroom-name.png) 1. **Create classroom（クラスルームの作成）**をクリックしてください。 ![クラスルーム名を入力するテキストフィールド](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/ja-JP/data/reusables/code-scanning/click-alert-in-list.md b/translations/ja-JP/data/reusables/code-scanning/click-alert-in-list.md index 67bec521b6..79f5af10bf 100644 --- a/translations/ja-JP/data/reusables/code-scanning/click-alert-in-list.md +++ b/translations/ja-JP/data/reusables/code-scanning/click-alert-in-list.md @@ -1 +1,6 @@ -1. "Code scanning"の下で、調べたいアラートをクリックしてください。 ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/help/repository/code-scanning-click-alert.png) +1. "Code scanning"の下で、調べたいアラートをクリックしてください。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% 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 338bf00e96..bba112ff1c 100644 --- a/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -セキュリティあるいはバージョンアップデートを実行する際に、エコシステムによってはアップデートが成功したことを検証するためにすべての依存関係をソースから解決できなければならないことがあります。 マニフェストあるいはロックファイルにプライベートの依存関係が含まれているなら、{% data variables.product.prodname_dependabot %}はそれらの依存関係がホストされている場所にアクセスできなければなりません。 Organizationのオーナーは、同じOrganization内のプロジェクトに対する依存関係を含むプライベートリポジトリへのアクセス権を{% data variables.product.prodname_dependabot %}に付与できます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)」を参照してください。 リポジトリの_dependabot.yml_設定ファイル中で、プライベートリポジトリへのアクセスを設定できます。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries) 」を参照してください。 +セキュリティあるいはバージョンアップデートを実行する際に、エコシステムによってはアップデートが成功したことを検証するためにすべての依存関係をソースから解決できなければならないことがあります。 マニフェストあるいはロックファイルにプライベートの依存関係が含まれているなら、{% data variables.product.prodname_dependabot %}はそれらの依存関係がホストされている場所にアクセスできなければなりません。 Organizationのオーナーは、同じOrganization内のプロジェクトに対する依存関係を含むプライベートリポジトリへのアクセス権を{% data variables.product.prodname_dependabot %}に付与できます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)」を参照してください。 リポジトリの_dependabot.yml_設定ファイル中で、プライベートリポジトリへのアクセスを設定できます。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries) 」を参照してください。 diff --git a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md index 315316eba6..bb2555adea 100644 --- a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md @@ -6,7 +6,7 @@ | パッケージマネージャー | YAML値 | サポートされているバージョン | プライベートリポジトリ | プライベートレジストリ | ベンダー | | -------------- | ---------------- | -------------------------- |:-----------:|:-----------:|:-----:| -| Bundler | `bundler` | v1 | | **✓** | **✓** | +| Bundler | `bundler` | v1, v2 | | **✓** | **✓** | | Cargo | `cargo` | v1 | **✓** | **✓** | | | Composer | `composer` | v1, v2 | **✓** | **✓** | | | Docker | `docker` | v1 | **✓** | **✓** | | diff --git a/translations/ja-JP/data/reusables/dotcom_billing/coupon-expires.md b/translations/ja-JP/data/reusables/dotcom_billing/coupon-expires.md new file mode 100644 index 0000000000..c59a6f6fed --- /dev/null +++ b/translations/ja-JP/data/reusables/dotcom_billing/coupon-expires.md @@ -0,0 +1 @@ +サブスクリプションの支払いにクーポンを使う場合、クーポンが期限切れになると、支払い方法にサブスクリプションのコストすべてが課金されます。 保存された支払い方法がない場合、アカウントはユーザアカウントなら{% data variables.product.prodname_free_user %}に、もしくはOrganizationなら{% data variables.product.prodname_free_team %}にダウングレードされます。 diff --git a/translations/ja-JP/data/reusables/education/about-github-education-link.md b/translations/ja-JP/data/reusables/education/about-github-education-link.md index 8402f201d9..2db937981a 100644 --- a/translations/ja-JP/data/reusables/education/about-github-education-link.md +++ b/translations/ja-JP/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -個人の割引を適用する前に、あなたの学習コミュニティがすでに弊社と{% data variables.product.prodname_education %}学校としてパートナーになっているかを確認してください。 詳しい情報については、「[{% data variables.product.prodname_education %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)」を参照してください。 +個人の割引を適用する前に、あなたの学習コミュニティがすでに弊社と{% data variables.product.prodname_campus_program %}学校としてパートナーになっているかを確認してください。 詳しい情報については、「[{% data variables.product.prodname_campus_program %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md index e860480c16..52f14d01b0 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md @@ -1,2 +1 @@ -1. Under "{% octicon "gear" aria-label="The Settings gear" %} Settings", click **Hooks**. - ![Hooks tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-hooks-tab.png) +1. "{% octicon "gear" aria-label="The Settings gear" %} Setteings（{{ octicon-gear The Settings gear }}設定）"の下で、**Hooks（フック）**をクリックしてください。 ![Enterpriseアカウント設定サイドバー内のフックタブ](/assets/images/help/business-accounts/settings-hooks-tab.png) diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md index af9df45fdd..e848750d16 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md @@ -1,2 +1 @@ -1. Under **{% octicon "gear" aria-label="The Settings gear" %} Settings**, click **Messages**. - ![Messages tab in the enterprise settings sidebar](/assets/images/enterprise/business-accounts/settings-messages-tab.png) +1. "{% octicon "gear" aria-label="The Settings gear" %} Setteings（{{ octicon-gear The Settings gear }}設定）"の下で、**Messages（メッセージ）**をクリックしてください。 ![Enterprise設定サイドバー内のメッセージタブ](/assets/images/enterprise/business-accounts/settings-messages-tab.png) diff --git a/translations/ja-JP/data/reusables/enterprise_installation/replica-limit.md b/translations/ja-JP/data/reusables/enterprise_installation/replica-limit.md index 21bd197854..53cf234957 100644 --- a/translations/ja-JP/data/reusables/enterprise_installation/replica-limit.md +++ b/translations/ja-JP/data/reusables/enterprise_installation/replica-limit.md @@ -1,7 +1,7 @@ {% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note:** There is a maximum of 8 high availability replicas (both passive and active/geo replicas) allowed for {% data variables.product.product_name %}. +**ノート:** {% data variables.product.product_name %}では、最大で8つのHigh Availabilityレプリカ（パッシブ及びアクティブ/Goのいずれでも）が利用できます。 {% endnote %} 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 35598cce54..cb9e133446 100644 --- a/translations/ja-JP/data/reusables/gated-features/code-scanning.md +++ b/translations/ja-JP/data/reusables/gated-features/code-scanning.md @@ -1,4 +1,6 @@ -{% 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. -{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{% data variables.product.prodname_code_scanning_capc %}は、Organizationが所有する{% data variables.product.prodname_GH_advanced_security %}が有効化されたすべてのパブリック及びプライベートリポジトリで利用できます。 +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %}は、リポジトリで{% data variables.product.prodname_GH_advanced_security %}が有効化されていれば利用できます。 +{%- elsif currentVersion == "github-ae@latest" %} +{% data variables.product.prodname_code_scanning_capc %}は、ベータリリースの間は無料の{% data variables.product.prodname_GH_advanced_security %}の一部として利用できます。 {%- 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 %} +{% 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/ja-JP/data/reusables/gated-features/security-center.md b/translations/ja-JP/data/reusables/gated-features/security-center.md index 3006b19baa..98ebdbb2aa 100644 --- a/translations/ja-JP/data/reusables/gated-features/security-center.md +++ b/translations/ja-JP/data/reusables/gated-features/security-center.md @@ -1,4 +1,4 @@ {% if currentVersion == "github-ae@latest" %} -The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release. +{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているなら、Organizationのセキュリティの概要が利用できます。これは、ベータリリースの間は無料です。 {% else %} -The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているなら、Organizationのセキュリティの概要が利用できます。{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ja-JP/data/reusables/github-actions/actions-github-connect-requirement.md b/translations/ja-JP/data/reusables/github-actions/actions-github-connect-requirement.md new file mode 100644 index 0000000000..1b65d60bcb --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/actions-github-connect-requirement.md @@ -0,0 +1 @@ +{% data variables.product.prodname_ghe_server %}が{% data variables.product.prodname_dotcom_the_website %}から直接アクションを使えるようにするには、{% data variables.product.prodname_github_connect %}が利用できます。 「[{% data variables.product.prodname_github_connect %}を利用した{% data variables.product.prodname_dotcom_the_website %}アクションへの自動アクセスの有効化](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」に記載されているように、"Server can use actions from {% data variables.product.prodname_dotcom_the_website %} in workflows runs（ワークフローの実行で{% data variables.product.prodname_dotcom_the_website %}からのアクションをサービスが利用可能）"の設定を有効化しなければなりません。 diff --git a/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md b/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md index 6e4c7338be..8bebbd6544 100644 --- a/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md @@ -2,16 +2,17 @@ スターターワークフローテンプレートは、X64プラットフォーム用のOpenJDK 8を含む`PATH`をセットアップします。 異なるバージョンのJavaを使いたい場合、あるいは異なるアーキテクチャ（`x64`あるいは`x86`）をターゲットとしたい場合には、`setup-java`アクションを使って異なるJavaランタイム環境を選択できます。 -たとえば、x64プラットフォーム用のバージョン9.0.4のJDKを使いたい場合、 `setup-java`アクションを使って `java-version`及び`architecture`パラメーターを`'9.0.4'`と`x64`に設定できます。 +たとえば、x64プラットフォーム上でAdoptiumが提供するJDKのバージョン11を使うには、`setup-java`アクションを使って`java-version`、`distribution`、`architecture` パラメータを`'11'`、`'adopt'`、`x64`に設定できます。 {% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 + - name: Set up JDK 11 for x64 + uses: actions/setup-java@v2 with: - java-version: '9.0.4' + java-version: '11' + distribution: 'adopt' architecture: x64 ``` {% endraw %} diff --git a/translations/ja-JP/data/reusables/github-insights/events-tab.md b/translations/ja-JP/data/reusables/github-insights/events-tab.md index e17ffdc31b..cd46b46fa9 100644 --- a/translations/ja-JP/data/reusables/github-insights/events-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/events-tab.md @@ -1,2 +1 @@ -1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Events**. - ![Events tab](/assets/images/help/insights/events-tab.png) +1. **{% octicon "gear" aria-label="The gear icon" %} Settings（{{ octicon-gear The gear icon }}設定）**の下で**Events（イベント）**をクリックしてください。 ![イベントタブ](/assets/images/help/insights/events-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md b/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md index 32d4cbb997..8d2c48e427 100644 --- a/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md @@ -1,2 +1 @@ -1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Exclude files**. - ![Exclude files tab](/assets/images/help/insights/exclude-files-tab.png) +1. **{% octicon "gear" aria-label="The gear icon" %} Settings（{{ octicon-gear The gear icon }}設定）**の下で**Exclude files（ファイルの除外）**をクリックしてください。 ![ファイルの除外タブ](/assets/images/help/insights/exclude-files-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md b/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md index f4670fb260..6888dfbacb 100644 --- a/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md @@ -1,2 +1 @@ -1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Repo groups**. - ![Repo groups tab](/assets/images/help/insights/repo-groups-tab.png) +1. **{% octicon "gear" aria-label="The gear icon" %} Settings（{{ octicon-gear The gear icon }}設定）**の下で**Repo groups（リポジトリグループ）**をクリックしてください。 ![リポジトリグループタブ](/assets/images/help/insights/repo-groups-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/repositories-tab.md b/translations/ja-JP/data/reusables/github-insights/repositories-tab.md index 6dae008abb..1492f7d8e3 100644 --- a/translations/ja-JP/data/reusables/github-insights/repositories-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/repositories-tab.md @@ -1,2 +1 @@ -1. Under "**{% octicon "gear" aria-label="The gear icon" %} Settings**", click **Repositories**. - ![Repositories tab](/assets/images/help/insights/repositories-tab.png) +1. **{% octicon "gear" aria-label="The gear icon" %} Settings（{{ octicon-gear The gear icon }}設定）**の下で**Repositories（リポジトリ）**をクリックしてください。 ![[Repositories] タブ](/assets/images/help/insights/repositories-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/settings-tab.md b/translations/ja-JP/data/reusables/github-insights/settings-tab.md index 3dc57e9b30..5ae66b9039 100644 --- a/translations/ja-JP/data/reusables/github-insights/settings-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/settings-tab.md @@ -1,2 +1 @@ -1. In {% data variables.product.prodname_insights %}, click **{% octicon "gear" aria-label="The gear icon" %} Settings**. - ![Settings tab](/assets/images/help/insights/settings-tab.png) +1. {% data variables.product.prodname_insights %}で、**{% octicon "gear" aria-label="The gear icon" %} Settings（{{ octicon-gear The gear icon }}の設定）**をクリックしてください。 ![設定タブ](/assets/images/help/insights/settings-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/teams-tab.md b/translations/ja-JP/data/reusables/github-insights/teams-tab.md index 545533de53..e5ea1c6527 100644 --- a/translations/ja-JP/data/reusables/github-insights/teams-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/teams-tab.md @@ -1,2 +1 @@ -1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Teams**. - ![Teams tab](/assets/images/help/insights/teams-tab.png) +1. **{% octicon "gear" aria-label="The gear icon" %} Settings（{{ octicon-gear The gear icon }}設定）**の下で**Teams**をクリックしてください。 ![Teamsタブ](/assets/images/help/insights/teams-tab.png) 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 index dbe463ea1f..1359d2cbf6 100644 --- 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 @@ -1,5 +1,5 @@ {% warning %} -**警告:** OrganizationがTeamの同期を使用しているなら、ユーザのSSOのアイデンティティを取り消すと、そのユーザはIdPグループにマップされたすべてのTeamから削除されます。 詳しい情報については「[アイデンティティプロバイダとTeamの同期](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 +**警告:** OrganizationがTeamの同期を使用しているなら、ユーザのSSOのアイデンティティを取り消すと、そのユーザはIdPグループにマップされたすべてのTeamから削除されます。 詳しい情報については「[アイデンティティプロバイダとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 {% endwarning %} diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 39cd3dafb9..4674c65c3c 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -Team同期を有効化すると、チームメンテナとOrganizationのオーナーは、{% data variables.product.prodname_dotcom %}上で、あるいはAPIを通じてTeamをIdPグループに接続できます。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」及び「[Teamの同期](/rest/reference/teams#team-sync)」を参照してください。 +Team同期を有効化すると、チームメンテナとOrganizationのオーナーは、{% data variables.product.prodname_dotcom %}上で、あるいはAPIを通じてTeamをIdPグループに接続できます。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」及び「[Teamの同期](/rest/reference/teams#team-sync)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm-saml.md index 5e5df97e97..5f967325f5 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm-saml.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-confirm-saml.md @@ -1 +1 @@ -3. SAML SSO が有効であることを確認します。 詳細は「[Organization で SAML シングルサインオンを管理する](/articles/managing-saml-single-sign-on-for-your-organization)」を参照してください。 +3. SAML SSO が有効であることを確認します。 詳細は「[Organization で SAML シングルサインオンを管理する](/organizations/managing-saml-single-sign-on-for-your-organization/)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md index 2a2f1fb88c..2d55dec2ca 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md @@ -1,5 +1,5 @@ OktaのTeam同期を有効化するには、あなたもしくはIdPの管理者は以下を実行しなければなりません。 -- Oktaを利用するOrganizationでSAML SSOとSCIMを有効化する。 詳しい情報については「[Oktaを使用したSAMLシングルサインオンとSCIMの設定](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)」を参照してください。 +- Oktaを利用するOrganizationでSAML SSOとSCIMを有効化する。 詳しい情報については「[Oktaを使用したSAMLシングルサインオンとSCIMの設定](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)」を参照してください。 - OktaインスタンスのテナントURLを提供してください。 - Okta環境にサービスユーザとして読み取りのみの管理権限を持つ、有効なSSWSトークンを生成してください。 詳しい情報についてはOktaのドキュメンテーションの[トークンの生成](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/)及び[サービスユーザ](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm)を参照してください。 diff --git a/translations/ja-JP/data/reusables/organizations/filter-security-overview.md b/translations/ja-JP/data/reusables/organizations/filter-security-overview.md index f13a2d07cb..8190420a77 100644 --- a/translations/ja-JP/data/reusables/organizations/filter-security-overview.md +++ b/translations/ja-JP/data/reusables/organizations/filter-security-overview.md @@ -1 +1 @@ -1. Optionally, filter the list of alerts. You can click multiple filters in the drop-down filter menus to narrow your search. You can also type search qualifiers in the **Search repositories** field. For more information about the available qualifiers, see "[Filtering the list of alerts](#filtering-the-list-of-alerts)." ![The drop-down filter menus and Search repositories field in the security overview](/assets/images/help/organizations/security-overview-filter-alerts.png) \ No newline at end of file +1. あるいは、アラートのリストをフィルタしてください。 検索を絞り込むために、ドロップダウンのフィルタメニュー内で複数のフィルタをクリックできます。 また、**Search repositories（リポジトリを検索）**フィールドに、検索修飾子を入力することもできます。 利用可能な修飾子に関する詳しい情報については「[アラートのリストのフィルタリング](#filtering-the-list-of-alerts)」を参照してください。 ![セキュリティの概要のドロップダウンフィルタメニューとリポジトリの検索フィールド](/assets/images/help/organizations/security-overview-filter-alerts.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/organizations/security-overview.md b/translations/ja-JP/data/reusables/organizations/security-overview.md index f900c33c67..8bfb59b056 100644 --- a/translations/ja-JP/data/reusables/organizations/security-overview.md +++ b/translations/ja-JP/data/reusables/organizations/security-overview.md @@ -1 +1 @@ -1. Under your organization name, click {% octicon "shield" aria-label="The Security shield" %} **Security**. ![Organization security button](/assets/images/help/organizations/organization-security-tab.png) \ No newline at end of file +1. Organization名の下で、{% octicon "shield" aria-label="The Security shield" %}**Security（セキュリティ）**をクリックしてください。 ![Organizationのセキュリティボタン](/assets/images/help/organizations/organization-security-tab.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/ja-JP/data/reusables/organizations/team-discussions-are-for-orgs.md index 48bdda7a01..edfb167d57 100644 --- a/translations/ja-JP/data/reusables/organizations/team-discussions-are-for-orgs.md +++ b/translations/ja-JP/data/reusables/organizations/team-discussions-are-for-orgs.md @@ -1 +1 @@ -Teamディスカッションは、OrganizationのTeamページでのみ利用できます。 詳しい情報については[Team ディスカッションについて](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)を参照してください。 +Teamディスカッションは、OrganizationのTeamページでのみ利用できます。 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)を参照してください。 diff --git a/translations/ja-JP/data/reusables/organizations/team-security-overview.md b/translations/ja-JP/data/reusables/organizations/team-security-overview.md index 8e112f5dc3..1c306d7b47 100644 --- a/translations/ja-JP/data/reusables/organizations/team-security-overview.md +++ b/translations/ja-JP/data/reusables/organizations/team-security-overview.md @@ -1 +1 @@ -1. At the top of the team's page, click {% octicon "shield" aria-label="The security icon" %} **Security**. ![Team security overview](/assets/images/help/teams/org-team-page-security-overview.png) +1. Teamのページの上部で{% octicon "shield" aria-label="The security icon" %}**Security（セキュリティ）**をクリックしてください。 ![Teamセキュリティの概要](/assets/images/help/teams/org-team-page-security-overview.png) diff --git a/translations/ja-JP/data/reusables/organizations/team-synchronization.md b/translations/ja-JP/data/reusables/organizations/team-synchronization.md index 7dcec09dbc..299092f1e5 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" or currentVersion == "github-ae@latest" %} -Teamの同期を使い、アイデンティティプロバイダを通じてOrganizationのメンバーのTeamへの追加や削除を自動的に行えます。 詳しい情報については「[Team をアイデンティティプロバイダグループと同期する](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 +Teamの同期を使い、アイデンティティプロバイダを通じてOrganizationのメンバーのTeamへの追加や削除を自動的に行えます。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md b/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md index fe71ce0fff..b9f3248ed6 100644 --- a/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md +++ b/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md @@ -11,5 +11,5 @@ - [OrganizationメンバーのTeamからの削除](/articles/removing-organization-members-from-a-team) - [既存のTeamメンバーのチームメンテナへの昇格](/articles/giving-team-maintainer-permissions-to-an-organization-member) - リポジトリへのTeamのアクセスの削除{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -- [Teamのためのコードレビューの割り当て管理](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} +- [Teamのためのコードレビューの割り当て管理](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [プルリクエストのスケジュールされたリマインダーの管理](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md index 4584a46d12..d05ee36620 100644 --- a/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. 実行したいタスクに対して適切なスコープを持つ新しい個人アクセストークン（PAT）を作成してください。 OrganizationがSSOを必須としている場合は、新しいトークンでSSOを有効化しなければなりません。 {% warning %} - **ノート:** `write:packages`スコープを選択した場合、PATを作成する際には`repo`スコープのせんたくを解除してください。 リポジトリのシークレットとして`repo`スコープを持つPATを追加すると、そのクレデンシャルはリポジトリのすべてのコラボレータからアクセスできるようになります。 そうすると、アクション内で`repo`スコープを持つPATが使われた場合、不要なアクセス権が追加で与えられることになります。 アクションのセキュリティのベストプラクティスに関する詳しい情報については「[GitHub Actionsのセキュリティ強化](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)」を参照してください。 + **ノート:** デフォルトでは、ユーザインターフェース内で個人アクセストークン（PAT）に対して`write:packages`スコープを選択すると、`repo`スコープも選択されます。 `repo`は不要に広いアクセス権を提供するので、特にGitHub Actionsのワークフローでの利用は避けることをおすすめします。 詳しい情報については「[GitHub Actionsのためのセキュリティ強化](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)」を参照してください。 回避策として、以下のURLでユーザインターフェース内でPATに`write:packages`スコープだけを選択することができます。 `https://github.com/settings/tokens/new?scopes=write:packages` {% endwarning %} diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index cc5c4e7c2f..991f1d2931 100644 --- a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,5 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} +PATはアカウントに対する広汎なアクセスを許可できます。 {% data variables.product.prodname_container_registry %}での認証のためのPATを作成する際には、必要な`read:packages`、`write:packages`、`delete:packages`スコープだけを選択すべきです。 + {% data variables.product.prodname_actions %}ワークフロー内で{% data variables.product.prodname_github_container_registry %}の認証を受けるには、最善のセキュリティと体験のために`GITHUB_TOKEN`を使ってください。 個人アクセストークンで`ghcr.io`の認証を受けるワークフローの更新に関するガイダンスとしては、「[`ghcr.io`にアクセスするワークフローのアップグレード](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/package_registry/checksum-maven-plugin.md b/translations/ja-JP/data/reusables/package_registry/checksum-maven-plugin.md index b89ac62089..2078a10901 100644 --- a/translations/ja-JP/data/reusables/package_registry/checksum-maven-plugin.md +++ b/translations/ja-JP/data/reusables/package_registry/checksum-maven-plugin.md @@ -1,5 +1,5 @@ {%- if currentVersion == "github-ae@latest" %} -1. In the `plugins` element of the *pom.xml* file, add the [checksum-maven-plugin](http://checksum-maven-plugin.nicoulaj.net/index.html) plugin, and configure the plugin to send at least SHA-256 checksums. +1. *pom.xml*ファイルの`plugins`要素に[checksum-maven-plugin](http://checksum-maven-plugin.nicoulaj.net/index.html)プラグインを追加し、そのプラグインを最低でもSHA-256のチェックサムを送信するように設定してください。 ```xml diff --git a/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md b/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md index 2838a57470..78f59f68cc 100644 --- a/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md +++ b/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md @@ -1 +1 @@ -You can publish packages in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository ({% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} packages) to share with {% if currentVersion == "free-pro-team@latest" %}all of {% data variables.product.prodname_dotcom %}{% else %}everyone on your enterprise{% endif %}, or in a private repository (private packages) to share with collaborators or an organization. +{% if currentVersion == "github-ae@latest" %}インターナル{% else %}パブリック{% endif %}リポジトリで（{% if currentVersion == "github-ae@latest" %}インターナル{% else %}パブリック{% endif %}パッケージ）パッケージを公開して、{% data variables.product.prodname_dotcom %}全体{% else %}Enterpriseの全員{% endif %}と、もしくはプライベートリポジトリ（プライベートパッケージ）でパッケージを公開して、コラボレータあるいはOrganizationと共有できます。 diff --git a/translations/ja-JP/data/reusables/pages/choose-visibility.md b/translations/ja-JP/data/reusables/pages/choose-visibility.md index 4809b5b057..85c1493272 100644 --- a/translations/ja-JP/data/reusables/pages/choose-visibility.md +++ b/translations/ja-JP/data/reusables/pages/choose-visibility.md @@ -1 +1 @@ -1. あるいは、プロジェクトサイトを{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationが所有しているプライベートもしくはインターナルリポジトリから公開している場合、サイトの可視性を選択してください。 "{% data variables.product.prodname_pages %}"の下で、**{% data variables.product.prodname_pages %} visibility（{% data variables.product.prodname_pages %}の可視性）**ドロップダウンメニューを選択し、可視性をクリックしてください。 詳しい情報については「[{% data variables.product.prodname_pages %}サイトの可視性の変更](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)」をクリックしてください。 ![サイトの可視性を選択するドロップダウンメニュー](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file +1. あるいは、プロジェクトサイトを{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationが所有しているプライベートもしくはインターナルリポジトリから公開している場合、サイトの可視性を選択してください。 "{% data variables.product.prodname_pages %}"の下で、**{% data variables.product.prodname_pages %} visibility（{% data variables.product.prodname_pages %}の可視性）**ドロップダウンメニューを選択し、可視性をクリックしてください。 詳しい情報については「[{% data variables.product.prodname_pages %}サイトの可視性の変更](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)」をクリックしてください。 ![サイトの可視性を選択するドロップダウンメニュー](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md index d4025d3b45..615cb8c89f 100644 --- a/translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md +++ b/translations/ja-JP/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**ノート:** Organizationのオーナーは、Organizationが所有しているリポジトリからの{% data variables.product.prodname_pages %}サイトの公開を制限できます。 詳しい情報については「[{% data variables.product.prodname_pages %}サイトの公開の管理](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照してください。 +**ノート:** Organizationのオーナーは、Organizationが所有しているリポジトリからの{% data variables.product.prodname_pages %}サイトの公開を制限できます。 詳しい情報については「[{% data variables.product.prodname_pages %}サイトの公開の管理](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照してください。 {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md b/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md index 8ded4eaa66..f74dc92725 100644 --- a/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/ja-JP/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ {% warning %} -**警告**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}サイト管理者がPublic Pagesを有効化したなら、{% endif %}{% data variables.product.prodname_pages %}サイトは{% if currentVersion == "free-pro-team@latest" %}デフォルトで{% endif %}、サイトのリポジトリがプライベートもしくはインターナルであっても、インターネット上で公開利用できます。{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %}そうでない場合は、もし{% else %}もし{% endif %}センシティブなデータがサイトのリポジトリにあるなら、公開前にそのデータを削除しておくとよいでしょう。 詳しい情報については、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 「[Enterpriseの{% 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){% if currentVersion == "free-pro-team@latest" %}」及び「[{% data variables.product.prodname_pages %}サイトの可視性の変更](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)」{% else %}」{% endif %}を参照してください。 +**警告**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}サイト管理者がPublic Pagesを有効化したなら、{% endif %}{% data variables.product.prodname_pages %}サイトは{% if currentVersion == "free-pro-team@latest" %}デフォルトで{% endif %}、サイトのリポジトリがプライベートもしくはインターナルであっても、インターネット上で公開利用できます。{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %}そうでない場合は、もし{% else %}もし{% endif %}センシティブなデータがサイトのリポジトリにあるなら、公開前にそのデータを削除しておくとよいでしょう。 詳しい情報については、{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 「[Enterpriseの{% 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){% if currentVersion == "free-pro-team@latest" %}」及び「[{% data variables.product.prodname_pages %}サイトの可視性の変更](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)」{% else %}」{% endif %}を参照してください。 {% endwarning %} diff --git a/translations/ja-JP/data/reusables/pages/sidebar-pages.md b/translations/ja-JP/data/reusables/pages/sidebar-pages.md new file mode 100644 index 0000000000..71a074df8c --- /dev/null +++ b/translations/ja-JP/data/reusables/pages/sidebar-pages.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +1. 左のサイドバーで**Pages（ページ）**をクリックしてください。 ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png) +{% endif %} diff --git a/translations/ja-JP/data/reusables/pages/update_your_dns_settings.md b/translations/ja-JP/data/reusables/pages/update_your_dns_settings.md index 6af95c8673..ffc0cd1b0e 100644 --- a/translations/ja-JP/data/reusables/pages/update_your_dns_settings.md +++ b/translations/ja-JP/data/reusables/pages/update_your_dns_settings.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" %}1. サイトで有効化されているカスタムドメインがあるなら、ドメインの乗っ取りを避けるためにDNSの設定を更新してください。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインの設定](/articles/configuring-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. サイトで有効化されているカスタムドメインがあるなら、ドメインの乗っ取りを避けるためにDNSの設定を更新してください。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインの設定](/pages/configuring-a-custom-domain-for-your-github-pages-site)」を参照してください。{% endif %} diff --git a/translations/ja-JP/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/ja-JP/data/reusables/pages/www-and-apex-domain-recommendation.md index 26fb027fe9..c03afe5fda 100644 --- a/translations/ja-JP/data/reusables/pages/www-and-apex-domain-recommendation.md +++ b/translations/ja-JP/data/reusables/pages/www-and-apex-domain-recommendation.md @@ -1 +1 @@ -カスタムドメインとして Apex ドメインを使用している場合は、`www` サブドメインもセットアップすることをおすすめします。 DNSプロバイダを通じて各ドメインの種類のための正しいレコードを設定しているなら、{% data variables.product.prodname_pages %}は自動的にドメイン間のリダイレクトを生成します。 たとえば`www.example.com`をサイトのカスタムドメインとして設定しており、Apex及び`www`ドメイン用に`ALIAS`及び`CNAME`レコードを持っているなら、`example.com`は`www.example.com`にリダイレクトされます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)」を参照してください。 +カスタムドメインとして Apex ドメインを使用している場合は、`www` サブドメインもセットアップすることをおすすめします。 DNSプロバイダを通じて各ドメインの種類のための正しいレコードを設定しているなら、{% data variables.product.prodname_pages %}は自動的にドメイン間のリダイレクトを生成します。 たとえば、サイトに`www.example.com`をカスタムドメインとして設定し、{% data variables.product.prodname_pages %}のDNSレコードをapex及び`www`ドメインに対してセットアップしているなら、`example.com`は`www.example.com`にリダイレクトされます。 自動のリダイレクトは、`www`サブドメインにのみ適用されることに注意してください。 自動リダイレクトは、`blog`といったようなその他のサブドメインには適用されません。 diff --git a/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md b/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md index 82549b4331..b5138c7dd4 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md +++ b/translations/ja-JP/data/reusables/pre-release-program/machine-man-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** To access the API with your GitHub App, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` Header for your requests. +**ノート:** GitHub AppでこのAPIにアクセスするには、カスタムの[メディアタイプ](/rest/overview/media-types)をリクエストの`Accept`ヘッダで渡さなければなりません。 `application/vnd.github.machine-man-preview+json` diff --git a/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md b/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md index ac0d210355..189d8989ad 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md +++ b/translations/ja-JP/data/reusables/pre-release-program/sailor-v-preview.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% note %} -**Note:** You can now use the REST API to add a reason when you lock an issue, and you will see lock reasons in responses that include issues or pull requests. You will also see lock reasons in `locked` events. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) for full details. To access this feature, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: +**ノート:** Issueをロックする際に理由を追加するREST APIを利用できるようになりました。ロックの理由は、IssueやPull Requestを含むレスポンス中で見ることができます。 ロックの理由は、`locked`イベント中でも見ることができます。 この機能は現在プレビューとして開発者が利用できます。 完全な詳細については[ブログポスト](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview)を参照してください。 この機能にアクセスするには、カスタムの[メディアタイプ](/rest/overview/media-types)を`Accept`ヘッダで渡さなければなりません。 ``` application/vnd.github.sailor-v-preview+json diff --git a/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md b/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md index 138455a9eb..f328d56a9b 100644 --- a/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md +++ b/translations/ja-JP/data/reusables/pre-release-program/starfox-preview.md @@ -1,8 +1,8 @@ {% note %} -**Note:** Project card details are now shown in REST API responses for project-related issue and timeline events. This feature is now available for developers to preview. For details, see the [blog post](https://developer.github.com/changes/2018-09-05-project-card-events). +**ノート:** プロジェクトカードの詳細は、プロジェクト関連のissue及びタイムラインイベントのREST APIレスポンス中に示されるようになりました。 この機能は、プレビューとして開発者が利用できるようになりました。 詳細については[ブログポスト](https://developer.github.com/changes/2018-09-05-project-card-events)を参照してください。 -To receive the `project_card` attribute, project boards must be [enabled](/articles/disabling-project-boards-in-a-repository) for a repository, and you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header: +`project_card` 属性を受け取るには、リポジトリでプロジェクトボードが[有効化](/articles/disabling-project-boards-in-a-repository)されていなければならず、カスタムの[メディアタイプ](/rest/overview/media-types)を`Accept`ヘッダで提供しなければなりません。 ``` application/vnd.github.starfox-preview+json diff --git a/translations/ja-JP/data/reusables/products/product-roadmap.md b/translations/ja-JP/data/reusables/products/product-roadmap.md index f2159b2387..2976317728 100644 --- a/translations/ja-JP/data/reusables/products/product-roadmap.md +++ b/translations/ja-JP/data/reusables/products/product-roadmap.md @@ -1 +1 @@ -For information on planned features and products, see the [{% data variables.product.prodname_roadmap %}]({% data variables.product.prodname_roadmap_link %}). +計画されている機能や製品に関する情報については、[{% data variables.product.prodname_roadmap %}]({% data variables.product.prodname_roadmap_link %})を参照してください。 diff --git a/translations/ja-JP/data/reusables/profile/profile-readme.md b/translations/ja-JP/data/reusables/profile/profile-readme.md index 45bee18454..2043509f74 100644 --- a/translations/ja-JP/data/reusables/profile/profile-readme.md +++ b/translations/ja-JP/data/reusables/profile/profile-readme.md @@ -1 +1 @@ -If you add a README file to the root of a public repository with the same name as your username, that README will automatically appear on your profile page. You can edit your profile README with {% data variables.product.company_short %} Flavored Markdown to create a personalized section on your profile. 詳しい情報については、「[プロフィール README の管理](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)」を参照してください。 +自分のユーザ名と同じ名前のパブリックリポジトリのルートにREADMEファイルを追加したなら、そのREADMEは自動的に自分のプロフィールページに表示されます。 プロフィールのREADMEは、{% data variables.product.company_short %}形式のMarkdownで編集し、プロフィール中にパーソナライズされたセクションを作成できます。 詳しい情報については、「[プロフィール README の管理](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md b/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md index 10747dfaf1..c5830b3d11 100644 --- a/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md +++ b/translations/ja-JP/data/reusables/profile/user_profile_page_block_or_report.md @@ -1 +1 @@ -1. In the left sidebar, under the user's profile picture, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block or report user**. ![ユーザのブロックもしくはレポートのリンク](/assets/images/help/profile/profile-block-or-report-button.png) +1. 左のサイドバーのユーザのプロフィール写真の下にある [{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}] をクリックしてから、[**Block or report user（ユーザをブロックもしくは報告）**] をクリックします。 ![ユーザのブロックもしくはレポートのリンク](/assets/images/help/profile/profile-block-or-report-button.png) diff --git a/translations/ja-JP/data/reusables/project-management/choose-visibility.md b/translations/ja-JP/data/reusables/project-management/choose-visibility.md index a17daff3d9..a3d8eb13a0 100644 --- a/translations/ja-JP/data/reusables/project-management/choose-visibility.md +++ b/translations/ja-JP/data/reusables/project-management/choose-visibility.md @@ -1 +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 %} +1. "Visibility（可視性）"の下で、プロジェクトボードを{% if currentVersion == "github-ae@latest" %}インターナル{% else %}パブリック{% endif %}あるいはプライベートにするかを選択してください。 詳しい情報については「[プロジェクトボードの可視性を変更する](/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-import-with-api.md b/translations/ja-JP/data/reusables/project-management/project-board-import-with-api.md index 8844e0f08a..622c9aa9d9 100644 --- a/translations/ja-JP/data/reusables/project-management/project-board-import-with-api.md +++ b/translations/ja-JP/data/reusables/project-management/project-board-import-with-api.md @@ -1 +1 @@ -{% data variables.product.prodname_dotcom %}のAPIを使って、プロジェクトボードをインポートできます。 For more information, see "[importProject](/graphql/reference/mutations#importproject/)." +{% data variables.product.prodname_dotcom %}のAPIを使って、プロジェクトボードをインポートできます。 詳しい情報については「[importProject](/graphql/reference/mutations#importproject/)」を参照してください。 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 acf775d7ca..e3acaf1d1e 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 @@ -デフォルトでは、プロジェクトボードはプライベートに設定されており、プロジェクトボードへの読み取り、書き込み、または管理者権限を持つメンバーだけが表示できます。 {% 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. +デフォルトでは、プロジェクトボードはプライベートに設定されており、プロジェクトボードへの読み取り、書き込み、または管理者権限を持つメンバーだけが表示できます。 {% if currentVersion == "github-ae@latest" %}インターナル{% else %}パブリック{% endif %}プロジェクトボードは、プロジェクトボードのURLを知っていれば{% if currentVersion == "github-ae@latest" %}Enterpriseのメンバーは誰でも{% else %}誰でも{% endif %}見ることができます。 diff --git a/translations/ja-JP/data/reusables/project-management/project-progress-locations.md b/translations/ja-JP/data/reusables/project-management/project-progress-locations.md index 9ac6c41be9..4c9eca1692 100644 --- a/translations/ja-JP/data/reusables/project-management/project-progress-locations.md +++ b/translations/ja-JP/data/reusables/project-management/project-progress-locations.md @@ -1 +1 @@ -If progress tracking is enabled, a progress bar appears above the project board, on the project listing page, in the issue sidebar, and in references to the project on other project boards. +進捗の追跡が有効になっている場合、プロジェクトボードの上部、プロジェクトリストのページ、Issueのサイドバー、他のプロジェクトボードのプロジェクトへの参照に、プログレスバーが表示されます。 diff --git a/translations/ja-JP/data/reusables/projects/disabled-projects.md b/translations/ja-JP/data/reusables/projects/disabled-projects.md index 9f6e391db7..74ba6577ab 100644 --- a/translations/ja-JP/data/reusables/projects/disabled-projects.md +++ b/translations/ja-JP/data/reusables/projects/disabled-projects.md @@ -1 +1 @@ -You only see this event in responses when project boards have been [enabled](/articles/disabling-project-boards-in-a-repository) in the repository. +プロジェクトボードがリポジトリで[有効化](/articles/disabling-project-boards-in-a-repository)されている場合にのみ、レスポンス中にこのイベントが示されます。 diff --git a/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md index df90cb5e1a..bda9747604 100644 --- a/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -You can link a pull request to an issue to{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} show that a fix is in progress and to{% endif %} automatically close the issue when someone merges the pull request. 詳しい情報については「[プルリクエストのIssueへのリンク](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 +Pull RequestをIssueにリンクして、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}修正が進んでいることを示すとともに、{% endif %}誰かがそのPull Requestをマージしたときに自動的にそのIssueをクローズさせることができます。 詳しい情報については「[プルリクエストのIssueへのリンク](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md b/translations/ja-JP/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md index b832ddb27e..82b38fc920 100644 --- a/translations/ja-JP/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md +++ b/translations/ja-JP/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md @@ -1 +1 @@ -1. Collect the name and email address for each co-author.{% if currentVersion == "free-pro-team@latest" %} If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy.{% endif %} +1. 各 co-author (共同作者) の名前とメールアドレスを収集してください。{% if currentVersion == "free-pro-team@latest" %}メールアドレスをプライベートにしておきたい人がいる場合、そのプライバシーを保護するためにその人には {% data variables.product.product_name %} が提供する`no-reply`メールを使わなければなりません。{% endif %} diff --git a/translations/ja-JP/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/ja-JP/data/reusables/pull_requests/pull_request_merges_and_contributions.md index eac91c7bce..d44f3d43c2 100644 --- a/translations/ja-JP/data/reusables/pull_requests/pull_request_merges_and_contributions.md +++ b/translations/ja-JP/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" %} - プロフィールのコントリビューショングラフに表示されるためには、co-authoredコミットは一人の作者によるコミットと同じ条件を満たさなければなりません。{% endif %} - コミットをリベースする際には、コミットのオリジナルの作者と、コマンドラインか{% data variables.product.product_location %}かによらずコミットをリベースした人が、コントリビューションクレジットを受け取ります。 diff --git a/translations/ja-JP/data/reusables/pull_requests/re-request-review.md b/translations/ja-JP/data/reusables/pull_requests/re-request-review.md index b04a7a46ce..e4698798d6 100644 --- a/translations/ja-JP/data/reusables/pull_requests/re-request-review.md +++ b/translations/ja-JP/data/reusables/pull_requests/re-request-review.md @@ -1 +1 @@ -You can re-request a review, for example, after you've made substantial changes to your pull request. To request a fresh review from a reviewer, in the sidebar of the **Conversation** tab, click the {% octicon "sync" aria-label="The sync icon" %} icon. +たとえばPull Requestに相当の変更を加えた後に、レビューを再度リクエストできます。 レビュー担当者からの新たなレビューをリクエストするには、**Conversation（会話）**タブのサイドバーから、{% octicon "sync" aria-label="The sync icon" %}アイコンをクリックしてください。 diff --git a/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md index 77d7f1bad7..95ba9ada3a 100644 --- a/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ プルリクエストをリベースしてマージするには、リポジトリへの[書き込み権限](/articles/repository-permission-levels-for-an-organization/)が必要で、リポジトリでは[リベースマージが許可](/articles/configuring-commit-rebasing-for-pull-requests/)されていなければなりません。 -{% data variables.product.product_name %}上でのリベースとマージの振る舞いは、`gitのリベース`とは少し異なっています。 {% data variables.product.prodname_dotcom %}上でのリベースとマージは、常にコミッターの情報を更新し、新しいSHAを生成しますが、{% data variables.product.prodname_dotcom %}外での`git rebase`は祖先のコミット上でリベースが生じたときにコミッター情報を変更しません。 For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). +{% data variables.product.product_name %}上でのリベースとマージの振る舞いは、`gitのリベース`とは少し異なっています。 {% data variables.product.prodname_dotcom %}上でのリベースとマージは、常にコミッターの情報を更新し、新しいSHAを生成しますが、{% data variables.product.prodname_dotcom %}外での`git rebase`は祖先のコミット上でリベースが生じたときにコミッター情報を変更しません。 `git rebase`に関する詳しい情報については[公式のGitのドキュメンテーション](https://git-scm.com/docs/git-rebase)を参照してください。 `git rebase`の視覚的な表現については、[書籍_Pro Git_の"Git Branching - Rebasing"の章](https://git-scm.com/book/en/Git-Branching-Rebasing)を参照してください。 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 3526e39a78..f3f24fb992 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 +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. +リポジトリ管理者はすべてのPull Requestに対し、保護されたブランチにPull Requestを誰かがマージできるようになる前に受けなければならない承認レビューの数を指定できます。 リポジトリに書き込み権限を持っている人か、指定されたコードオーナーからの承認レビューを必須とすることができます。 diff --git a/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md b/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md index 917e7d9452..26f513bb0c 100644 --- a/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -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)." +すべてのマージの要件が満たされたときに、自動的にマージされるようにPull Requestを設定できます。 詳しい情報については「[Pull Requestの自動マージ](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/reminders/scheduled-reminders-limitations.md b/translations/ja-JP/data/reusables/reminders/scheduled-reminders-limitations.md index ab1ca73e19..49ebc04629 100644 --- a/translations/ja-JP/data/reusables/reminders/scheduled-reminders-limitations.md +++ b/translations/ja-JP/data/reusables/reminders/scheduled-reminders-limitations.md @@ -1,2 +1,2 @@ -{% data variables.product.product_name %} will only trigger reminders for up to five repositories per owner and 20 pull requests per repository. +{% data variables.product.product_name %}は、オーナーごとに5つのリポジトリまで、リポジトリごとに20のPull Requestまでしかリマインダーをトリガーしません。 diff --git a/translations/ja-JP/data/reusables/repositories/a-vulnerability-is.md b/translations/ja-JP/data/reusables/repositories/a-vulnerability-is.md index d133898fa2..e994af1862 100644 --- a/translations/ja-JP/data/reusables/repositories/a-vulnerability-is.md +++ b/translations/ja-JP/data/reusables/repositories/a-vulnerability-is.md @@ -1 +1 @@ -脆弱性とは、プロジェクトあるいはそのコードを利用する他のプロジェクトにおいて、秘密性、一貫性、可用性を損なうために悪用されうる、プロジェクトコードの問題です。 Vulnerabilities vary in type, severity, and method of attack. +脆弱性とは、プロジェクトあるいはそのコードを利用する他のプロジェクトにおいて、秘密性、一貫性、可用性を損なうために悪用されうる、プロジェクトコードの問題です。 脆弱性の種類、重要度、攻撃の方法は様々です。 diff --git a/translations/ja-JP/data/reusables/repositories/about-internal-repos.md b/translations/ja-JP/data/reusables/repositories/about-internal-repos.md index 61358584cd..164da73c6d 100644 --- a/translations/ja-JP/data/reusables/repositories/about-internal-repos.md +++ b/translations/ja-JP/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 %}. +インターナルリポジトリを使って、Enterprise内で「インナーソース」を実践できます。 Enterpriseアカウントのメンバーは、{% if enterpriseServerVersions contains currentVersion %}プライベートモードを無効化されていても、{% endif %}プロプライエタリな情報をパブリックに共有することなく、オープンソースの方法論を用いてコラボレートできます。 diff --git a/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md index 679cb19a0b..0abccd4a1f 100644 --- a/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md +++ b/translations/ja-JP/data/reusables/repositories/actions-scheduled-workflow-example.md @@ -1,6 +1,6 @@ [POSIX クーロン構文](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07)を使用して、特定の UTC 時間にワークフローを実行できるようスケジュール設定できます。 スケジュールしたワークフローは、デフォルトまたはベースブランチの直近のコミットで実行されます。 スケジュールされたワークフローを実行できる最短の間隔は、5 分ごとに 1 回です。 -This example triggers the workflow every day at 5:30 and 17:30 UTC: +この例では、ワークフローは毎日UTCの5:30と17:30にトリガーされます。 ```yaml on: diff --git a/translations/ja-JP/data/reusables/repositories/actions-workflow-status-badge-into.md b/translations/ja-JP/data/reusables/repositories/actions-workflow-status-badge-into.md index c114fe9a36..935795ad95 100644 --- a/translations/ja-JP/data/reusables/repositories/actions-workflow-status-badge-into.md +++ b/translations/ja-JP/data/reusables/repositories/actions-workflow-status-badge-into.md @@ -1,3 +1,3 @@ -A status badge shows whether a workflow is currently failing or passing. ステータスバッジを追加する一般的な場所は、リポジトリのREADME.mdファイル中ですが、任意の好きなWebページに追加できます。 By default, badges display the status of your default branch. 特定のブランチやイベントに対するワークフローの実行のステータスを、URL中の`branch`及び`event`クエリパラメータを使って表示することもできます。 +ステータスバッジは、ワークフローが現在失敗しているかパスしているかを示します。 ステータスバッジを追加する一般的な場所は、リポジトリのREADME.mdファイル中ですが、任意の好きなWebページに追加できます。 デフォルトでは、バッジはデフォルトブランチのステータスを示します。 特定のブランチやイベントに対するワークフローの実行のステータスを、URL中の`branch`及び`event`クエリパラメータを使って表示することもできます。 -![example status badge](/assets/images/help/repository/actions-workflow-status-badge.png) +![ステータスバッジの例](/assets/images/help/repository/actions-workflow-status-badge.png) diff --git a/translations/ja-JP/data/reusables/repositories/administrators-can-disable-issues.md b/translations/ja-JP/data/reusables/repositories/administrators-can-disable-issues.md index c21943def0..d3cfabbf31 100644 --- a/translations/ja-JP/data/reusables/repositories/administrators-can-disable-issues.md +++ b/translations/ja-JP/data/reusables/repositories/administrators-can-disable-issues.md @@ -1 +1 @@ -Repository administrators can disable issues for a repository. 詳細は「[Issue を無効化する](/github/managing-your-work-on-github/disabling-issues)」を参照してください。 +リポジトリの管理者は、リポジトリのIssueを無効化できます。 詳細は「[Issue を無効化する](/github/managing-your-work-on-github/disabling-issues)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/allow-maintainers-user-forks.md b/translations/ja-JP/data/reusables/repositories/allow-maintainers-user-forks.md index d5c63aa911..428521f007 100644 --- a/translations/ja-JP/data/reusables/repositories/allow-maintainers-user-forks.md +++ b/translations/ja-JP/data/reusables/repositories/allow-maintainers-user-forks.md @@ -2,6 +2,6 @@ {% warning %} - **Warning:** If your fork contains {% data variables.product.prodname_actions %} workflows, the option is **Allow edits and access to secrets by maintainers**. Allowing edits on a fork's branch that contains {% data variables.product.prodname_actions %} workflows also allows a maintainer to edit the forked repository's workflows, which can potentially reveal values of secrets and grant access to other branches. + **警告:** フォークに{% data variables.product.prodname_actions %}ワークフローが含まれているなら、オプションは**Allow edits and access to secrets by maintainers（メンテナからの編集とシークレットへのアクセスを許可）**になります。 {% data variables.product.prodname_actions %}ワークフローを含むフォークのブランチの編集を許可すると、メンテナにフォークされたリポジトリのワークフローの編集も許可することになり、シークレットの値を明らかにして他のブランチへのアクセスも許可してしまう可能性があります。 {% endwarning %} diff --git a/translations/ja-JP/data/reusables/repositories/blocked-passwords.md b/translations/ja-JP/data/reusables/repositories/blocked-passwords.md index a4b1206ee7..20f22fa781 100644 --- a/translations/ja-JP/data/reusables/repositories/blocked-passwords.md +++ b/translations/ja-JP/data/reusables/repositories/blocked-passwords.md @@ -1,6 +1,6 @@ {% if currentVersion == "free-pro-team@latest" %} -When you type a password to sign in, create an account, or change your password, -{% data variables.product.product_name %} will check if the password you entered is considered weak according to datasets like HaveIBeenPwned. 以前にまったく使ったことがないパスワードでも、弱いと判定されることがあります。 +サインイン、アカウントの作成、パスワードの変更時にパスワードを入力すると、 +{% data variables.product.product_name %}は入力されたパスワードが弱いかどうかを、HaveIBeenPwnedのようなデータセットに基づいてチェックします。 以前にまったく使ったことがないパスワードでも、弱いと判定されることがあります。 {% data variables.product.product_name %}がパスワードを検査するのは入力の際だけであり、入力されたパスワードが平文で保存されることはありません。 詳しい情報については[ HaveIBeenPwned](https://haveibeenpwned.com/)を参照してください。 {% endif %} 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 ea81704455..54e06e4955 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 @@ -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*`. +リポジトリ内のブランチ保護ルールは、特定のブランチ、あるいはすべてのブランチや`fnmatch`構文で指定した名前のパターンにマッチするブランチに対して作成できます。 たとえば、`release`という語を含む任意のブランチを保護するには、ブランチルールを`*release*`に対して作成できます。 diff --git a/translations/ja-JP/data/reusables/repositories/changed-files.md b/translations/ja-JP/data/reusables/repositories/changed-files.md index 382627a093..8de6a56c1f 100644 --- a/translations/ja-JP/data/reusables/repositories/changed-files.md +++ b/translations/ja-JP/data/reusables/repositories/changed-files.md @@ -1,5 +1,5 @@ -1. On the pull request, click -{% octicon "diff" aria-label="The file diff icon" %} **Files changed**. +1. Pull Requestで +{% octicon "diff" aria-label="The file diff icon" %}**Files changed（変更されたファイル）**をクリックしてください。 {% if currentVersion ver_lt "github-enterprise@3.0" %} ![プルリクエストの変更されたファイルタブ](/assets/images/enterprise/2.22/pull-request-tabs-changed-files.png){% else %} ![Pull Request Files changed tab](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) diff --git a/translations/ja-JP/data/reusables/repositories/choose-repo-visibility.md b/translations/ja-JP/data/reusables/repositories/choose-repo-visibility.md index 30eb0d9bef..9340e610c0 100644 --- a/translations/ja-JP/data/reusables/repositories/choose-repo-visibility.md +++ b/translations/ja-JP/data/reusables/repositories/choose-repo-visibility.md @@ -1 +1 @@ -1. Choose a repository visibility. 詳細は「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」を参照してください。 ![リポジトリの可視性を選択するラジオボタン](/assets/images/help/repository/create-repository-public-private.png) +1. リポジトリの可視性を選択してください。 詳細は「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」を参照してください。 ![リポジトリの可視性を選択するラジオボタン](/assets/images/help/repository/create-repository-public-private.png) diff --git a/translations/ja-JP/data/reusables/repositories/copy-clone-url.md b/translations/ja-JP/data/reusables/repositories/copy-clone-url.md index e0c53e7f8c..ad79617c2e 100644 --- a/translations/ja-JP/data/reusables/repositories/copy-clone-url.md +++ b/translations/ja-JP/data/reusables/repositories/copy-clone-url.md @@ -1,15 +1,15 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} 1. リポジトリ名の下で**Clone or download（クローンもしくはダウンロード）**をクリックしてください。 ![Clone or downloadボタン](/assets/images/help/repository/clone-repo-clone-url-button.png) -2. To clone the repository using HTTPS, under "Clone with HTTPS", click -{% 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" %}. +2. HTTPSを使ってリポジトリをクローンするには、"Clone with HTTPS（HTTPSでクローン）"の下で、 +{% octicon "clippy" aria-label="The clipboard icon" %}をクリックしてください。 +Organization の SSH 認証局から発行された証明書を含む SSH キーを使用してリポジトリのクローンを作成するには、**Use SSH（SSHを使用）**をクリックし、続いて +{% octicon "clippy" aria-label="The clipboard icon" %}をクリックしてください。 ![クローンURLボタン](/assets/images/help/repository/https-url-clone.png) {% else %} -1. Above the list of files, click {% octicon "download" aria-label="The download icon" %} **Code**. !["Code" button](/assets/images/help/repository/code-button.png) -1. To clone the repository using HTTPS, under "Clone with HTTPS", click -{% 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 %} - ![The clipboard icon for copying the URL to clone a repository](/assets/images/help/repository/https-url-clone.png) +1. ファイルのリストの上にある{% octicon "download" aria-label="The download icon" %} **Code（コード）**をクリックしてください。 !["Code"ボタン](/assets/images/help/repository/code-button.png) +1. HTTPSを使ってリポジトリをクローンするには、"Clone with HTTPS（HTTPSでクローン）"の下で、 +{% octicon "clippy" aria-label="The clipboard icon" %}をクリックしてください。 Organizationの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 %}を使ってリポジトリをクローンするには、**Use {% 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" %} - ![The clipboard icon for copying the URL to clone a repository with GitHub CLI](/assets/images/help/repository/https-url-clone-cli.png){% endif %} + ![GitHub CLIでリポジトリをクローンするためのURLをコピーするためのクリップボードアイコン](/assets/images/help/repository/https-url-clone-cli.png){% endif %} {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/create-repo.md b/translations/ja-JP/data/reusables/repositories/create-repo.md index 59c1040772..26cb0683b8 100644 --- a/translations/ja-JP/data/reusables/repositories/create-repo.md +++ b/translations/ja-JP/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/ja-JP/data/reusables/repositories/default-issue-templates.md b/translations/ja-JP/data/reusables/repositories/default-issue-templates.md index d10446495f..7c6eb52818 100644 --- a/translations/ja-JP/data/reusables/repositories/default-issue-templates.md +++ b/translations/ja-JP/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 %}. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 +Organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}もしくはユーザアカウント{% endif %}用に、デフォルトのIssueテンプレート{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}及びIssueテンプレートのためのデフォルトの設定ファイル{% endif %}を作成できます。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index 3d524bd65d..95c29899e8 100644 --- a/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/ja-JP/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -6,6 +6,6 @@ - [LDAP Syncが有効化されている](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync)場合、リポジトリから個人を削除すると、その人はアクセス権を失いますが、その人のフォークは削除されません。 元々のOrganizationのリポジトリへのアクセスできるように3ヶ月以内にその人がTeamに追加されたなら、次回の同期の際にフォークへのアクセスは自動的に回復されます。{% 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. 詳しい情報については「[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 %}リポジトリに対する管理権限を持っている人は、そのリポジトリのフォークを禁止でき、OrganizationのオーナーはOrganization内の任意のプライベート{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}もしくはインターナル{% endif %}リポジトリのフォークを禁止できます。 For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} diff --git a/translations/ja-JP/data/reusables/repositories/dependency-review.md b/translations/ja-JP/data/reusables/repositories/dependency-review.md index e780074c3c..72b74b98ec 100644 --- a/translations/ja-JP/data/reusables/repositories/dependency-review.md +++ b/translations/ja-JP/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 %}は、リポジトリのデフォルトブランチに対して作成されたPull Request中で追加、更新、削除された依存関係のレビューを行うことができ、プロジェクトに脆弱性をもたらすような変更にフラグを立てることができます。 これによって、脆弱な依存関係がコードベースに達したあとではなく、達する前に特定して対処できるようになります。 詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/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/ja-JP/data/reusables/repositories/deploy-keys.md b/translations/ja-JP/data/reusables/repositories/deploy-keys.md index 3f3948dc84..05c1a3b25c 100644 --- a/translations/ja-JP/data/reusables/repositories/deploy-keys.md +++ b/translations/ja-JP/data/reusables/repositories/deploy-keys.md @@ -1 +1 @@ -You can launch projects from a {% data variables.product.product_name %} repository to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal user account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)." +デプロイキーを使用して、{% data variables.product.product_name %}リポジトリからサーバーへプロジェクトを起動できます。デプロイキーは、単一のリポジトリへのアクセスを許可するSSHキーです。 {% data variables.product.product_name %}は個人ユーザアカウントの代わりに、リポジトリに直接キーのパブリックな部分をアタッチし、キーのプライベートな部分はサーバーに残ります。 詳しい情報については「[デプロイメントのデリバリー](/rest/guides/delivering-deployments)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/desktop-fork.md b/translations/ja-JP/data/reusables/repositories/desktop-fork.md index 87352ea86d..71edf4bcf1 100644 --- a/translations/ja-JP/data/reusables/repositories/desktop-fork.md +++ b/translations/ja-JP/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/ja-JP/data/reusables/repositories/enable-security-alerts.md b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md index 5381a8c1d1..08b233e710 100644 --- a/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md +++ b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md @@ -1,4 +1,4 @@ {% if enterpriseServerVersions contains currentVersion %} -Your site administrator must enable -{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. 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/ja-JP/data/reusables/repositories/github-reviews-security-advisories.md b/translations/ja-JP/data/reusables/repositories/github-reviews-security-advisories.md index 12933fe659..4f84799a05 100644 --- a/translations/ja-JP/data/reusables/repositories/github-reviews-security-advisories.md +++ b/translations/ja-JP/data/reusables/repositories/github-reviews-security-advisories.md @@ -1,3 +1,3 @@ -{% data variables.product.prodname_dotcom %} will review each published security advisory, add it to the {% data variables.product.prodname_advisory_database %}, and may use the security advisory to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. セキュリティアドバイザリがフォークから生ずる場合、ユニークな名前の下でパブリックなパッケージレジストリに公開されたパッケージをフォークが所有しているときにのみアラートが送信されます。 このプロセスには最大で72時間がかかり、{% data variables.product.prodname_dotcom %}がさらなる情報を求めてあなたに連絡することがあります。 +{% data variables.product.prodname_dotcom %}は、公開されたそれぞれのセキュリティアドバイザリをレビューし、{% data variables.product.prodname_advisory_database %}に追加し、そのセキュリティアドバイザリを使って影響されるリポジトリに{% data variables.product.prodname_dependabot_alerts %}を送信することがあります。 セキュリティアドバイザリがフォークから生ずる場合、ユニークな名前の下でパブリックなパッケージレジストリに公開されたパッケージをフォークが所有しているときにのみアラートが送信されます。 このプロセスには最大で72時間がかかり、{% data variables.product.prodname_dotcom %}がさらなる情報を求めてあなたに連絡することがあります。 -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)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-dependabot-security-updates)." For more information about {% data variables.product.prodname_advisory_database %}, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)." +{% data variables.product.prodname_dependabot_alerts %}に関する詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)」 および「[{% data variables.product.prodname_dependabot_security_updates %}について](/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-dependabot-security-updates)」を参照してください。 {% data variables.product.prodname_advisory_database %}に関する詳しい情報については、「[{% data variables.product.prodname_advisory_database %}におけるセキュリティ脆弱性をブラウズする](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/new-pull-request.md b/translations/ja-JP/data/reusables/repositories/new-pull-request.md index a55d4f0c5c..231ffcdf9b 100644 --- a/translations/ja-JP/data/reusables/repositories/new-pull-request.md +++ b/translations/ja-JP/data/reusables/repositories/new-pull-request.md @@ -1,7 +1,7 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -1. Branchメニューの右の**New pull request（新規プルリクエスト）**をクリックしてください。 !["Pull request" link above list of files](/assets/images/help/pull_requests/pull-request-start-review-button.png) +1. Branchメニューの右の**New pull request（新規プルリクエスト）**をクリックしてください。 ![ファイルのリスト上の"Pull request" リンク](/assets/images/help/pull_requests/pull-request-start-review-button.png) {% else %} -1. Above the list of files, click -{% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull request**. - !["Pull request" link above list of files](/assets/images/help/pull_requests/pull-request-start-review-button.png) +1. ファイルのリスト上で、 +{% octicon "git-pull-request" aria-label="The pull request icon" %}**Pull Request**をクリックしてください。 + ![ファイルのリスト上の"Pull request" リンク](/assets/images/help/pull_requests/pull-request-start-review-button.png) {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/open-with-github-desktop.md b/translations/ja-JP/data/reusables/repositories/open-with-github-desktop.md index ba7b805693..2891195271 100644 --- a/translations/ja-JP/data/reusables/repositories/open-with-github-desktop.md +++ b/translations/ja-JP/data/reusables/repositories/open-with-github-desktop.md @@ -1,11 +1,10 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} 1. リポジトリ名の下にある**Clone or download**をクリックします。 ![Clone or downloadボタン](/assets/images/help/repository/clone-repo-clone-url-button.png) -1. Click **Open in Desktop** to clone the repository and open it in -{% data variables.product.prodname_desktop %}. +1. **Open in Desktop（デスクトップでオープン）**をクリックして、リポジトリをクローンして +{% data variables.product.prodname_desktop %}でオープンしてください。 ![Open in Desktopボタン](/assets/images/help/desktop/open-in-desktop-button.png) {% else %} -1. Above the list of files, click {% octicon "download" aria-label="The download icon" %} **Code**. !["Code" button](/assets/images/help/repository/code-button.png) -1. 下向きの三角形アイコン -{% octicon "desktop-download" aria-label="The GitHub Desktop download icon" %} **Open with {% data variables.product.prodname_desktop %}** to clone and open the repository with {% data variables.product.prodname_desktop %}. - !["Open with {% data variables.product.prodname_desktop %}" button](/assets/images/help/repository/open-with-desktop.png) +1. ファイルのリストの上にある{% octicon "download" aria-label="The download icon" %} **Code（コード）**をクリックしてください。 !["Code"ボタン](/assets/images/help/repository/code-button.png) +1. {% octicon "desktop-download" aria-label="The GitHub Desktop download icon" %} **Open with {% data variables.product.prodname_desktop %}（{% data variables.product.prodname_desktop %}でオープン）**をクリックして、リポジトリをクローンして{% data variables.product.prodname_desktop %}でオープンしてください。 + !["{% data variables.product.prodname_desktop %}でオープン"ボタン](/assets/images/help/repository/open-with-desktop.png) {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/permissions-statement-read.md b/translations/ja-JP/data/reusables/repositories/permissions-statement-read.md index 241fdd2ba8..f378ed27fe 100644 --- a/translations/ja-JP/data/reusables/repositories/permissions-statement-read.md +++ b/translations/ja-JP/data/reusables/repositories/permissions-statement-read.md @@ -1 +1 @@ -Read access to the repository is required to perform these steps. +これらのステップを実行するには、リポジトリへの読み取りアクセスが必要です。 diff --git a/translations/ja-JP/data/reusables/repositories/permissions-statement-write.md b/translations/ja-JP/data/reusables/repositories/permissions-statement-write.md index 457fe04724..fc9c60aac5 100644 --- a/translations/ja-JP/data/reusables/repositories/permissions-statement-write.md +++ b/translations/ja-JP/data/reusables/repositories/permissions-statement-write.md @@ -1 +1 @@ -Write access to the repository is required to perform these steps. +これらのステップを実行するには、リポジトリへの書き込みアクセスが必要です。 diff --git a/translations/ja-JP/data/reusables/repositories/releases.md b/translations/ja-JP/data/reusables/repositories/releases.md index 199023d712..08793d20ee 100644 --- a/translations/ja-JP/data/reusables/repositories/releases.md +++ b/translations/ja-JP/data/reusables/repositories/releases.md @@ -4,6 +4,6 @@ {% else %} -1. To the right of the list of files, click **Releases** or **Latest release**. ![Releases section in right-hand sidebar](/assets/images/help/releases/release-link.png) +1. ファイルのリストの右で、**Releases（リリース）**もしくは**Latest release（最新のリリース）**をクリックしてください。 ![右側のサイドバー内のリリースセクション](/assets/images/help/releases/release-link.png) {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/ja-JP/data/reusables/repositories/sidebar-code-scanning-alerts.md index 49bd07ce71..bd7b0d7b66 100644 --- a/translations/ja-JP/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ b/translations/ja-JP/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -1 +1 @@ -1. 左のサイドバーで、**Code scanning alerts（コードスキャンニングアラート）**をクリックしてください。 あるいは、利用しているコードスキャンニングツールを選択してください。 !["コードスキャンニングアラート"タブ](/assets/images/help/repository/sidebar-code-scanning-alerts.png) +1. 左のサイドバーで、**Code scanning alerts（コードスキャンニングアラート）**をクリックしてください。 !["コードスキャンニングアラート"タブ](/assets/images/help/repository/sidebar-code-scanning-alerts.png) diff --git a/translations/ja-JP/data/reusables/saml/about-linked-identities.md b/translations/ja-JP/data/reusables/saml/about-linked-identities.md index f3f3627d37..93ec9dbbd4 100644 --- a/translations/ja-JP/data/reusables/saml/about-linked-identities.md +++ b/translations/ja-JP/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -メンバーが自分の{% data variables.product.product_name %}アカウントにリンクしたシングルサインオンのアイデンティティを見ることができます。 利用できる場合には、このエントリにはSCIMデータが含まれます。 詳しい情報については「[SCIMについて](/github/setting-up-and-managing-organizations-and-teams/about-scim)」を参照してください。 +メンバーが自分の{% data variables.product.product_name %}アカウントにリンクしたシングルサインオンのアイデンティティを見ることができます。 利用できる場合には、このエントリにはSCIMデータが含まれます。 詳しい情報については「[SCIMについて](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 メンバーが誤ったアイデンティティを{% data variables.product.product_name %}アカウントにリンクしている場合、リンクされたアイデンティティを取り消してメンバーにやり直してもらうことができます。 diff --git a/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md b/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md index 89c450ce81..44ed7f997f 100644 --- a/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,5 @@ {% note %} -**Note:** 外部のコラボレータは、SAML SSOを使っているOrganization内のリソースにアクセスするために、IdPでの認証を受ける必要はありません。 外部コラボレーターに関する詳しい情報については「[Organization の権限レベル](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)」を参照してください。 +**Note:** 外部のコラボレータは、SAML SSOを使っているOrganization内のリソースにアクセスするために、IdPでの認証を受ける必要はありません。 外部コラボレーターに関する詳しい情報については「[Organization の権限レベル](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)」を参照してください。 {% endnote %} 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 index 0559438bb6..e75538fe3d 100644 --- 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 @@ -7,6 +7,7 @@ | 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 | +| Asana | Asana Personal Access Token | asana_personal_access_token | | 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 | @@ -37,8 +38,12 @@ | 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 | +| Grafana | Grafana API Key | grafana_api_key | | Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | | Hubspot | Hubspot API Key | hubspot_api_key | +| Intercom | Intercom Access Token | intercom_access_token | +| Lob | Lob Live API Key | lob_live_api_key | +| Lob | Lob Test API Key | lob_test_api_key | | Mailchimp | Mailchimp API Key | mailchimp_api_key | | Mailgun | Mailgun API Key | mailgun_api_key | | npm | npm Access Token | npm_access_token | @@ -51,6 +56,7 @@ | Proctorio | Proctorio Secret Key | proctorio_secret_key | | Pulumi | Pulumi Access Token | pulumi_access_token | | PyPI | PyPI API Token | pypi_api_token | +| RubyGems | RubyGems API Key | rubygems_api_key | | Samsara | Samsara API Token | samsara_api_token | | Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | | SendGrid | SendGrid API Key | sendgrid_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 index c9a8d65306..ebc268a20d 100644 --- 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 @@ -50,6 +50,7 @@ | Proctorio | Proctorio Secret Key | | Pulumi | Pulumi Access Token | | PyPI | PyPI API Token | +| RubyGems | RubyGems API Key | | Samsara | Samsara API Token | | Samsara | Samsara OAuth Access Token | | Shopify | Shopify App Shared Secret | diff --git a/translations/ja-JP/data/reusables/sponsors/choose-updates.md b/translations/ja-JP/data/reusables/sponsors/choose-updates.md index ade59cf05b..93f8807013 100644 --- a/translations/ja-JP/data/reusables/sponsors/choose-updates.md +++ b/translations/ja-JP/data/reusables/sponsors/choose-updates.md @@ -1 +1 @@ -4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) +4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/ja-JP/data/reusables/sponsors/click-add-tier.md b/translations/ja-JP/data/reusables/sponsors/click-add-tier.md index 6453315069..8ee0602d01 100644 --- a/translations/ja-JP/data/reusables/sponsors/click-add-tier.md +++ b/translations/ja-JP/data/reusables/sponsors/click-add-tier.md @@ -1 +1 @@ -1. ページの下部にある**Add a tier（層の追加）**をクリックしてください。 ![層の追加ボタン](/assets/images/help/sponsors/add-a-tier-button.png) +1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![層の追加ボタン](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/ja-JP/data/reusables/sponsors/enable-custom-amounts.md b/translations/ja-JP/data/reusables/sponsors/enable-custom-amounts.md new file mode 100644 index 0000000000..1889367cb9 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/enable-custom-amounts.md @@ -0,0 +1,2 @@ +1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png) +1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png) diff --git a/translations/ja-JP/data/reusables/sponsors/feedback.md b/translations/ja-JP/data/reusables/sponsors/feedback.md new file mode 100644 index 0000000000..b358580842 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/feedback.md @@ -0,0 +1 @@ +{% data variables.product.prodname_sponsors %} に関するフィードバックを {% data variables.product.company_short %} と共有できます。 To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)." diff --git a/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md index 0cd08d5382..b47ac0599d 100644 --- a/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md +++ b/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md @@ -1 +1 @@ -You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)." +You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)." diff --git a/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md b/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md index f201de957c..32f6b098f7 100644 --- a/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md +++ b/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md @@ -1 +1 @@ -1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Due today", click **Pay prorated $X.XX today**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file +1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md b/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md index 56a047d867..9e560bf708 100644 --- a/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/ja-JP/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. +If you're starting a monthly sponsorship on behalf of your user account, you'll 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/ja-JP/data/reusables/sponsors/review-and-publish-tier.md b/translations/ja-JP/data/reusables/sponsors/review-and-publish-tier.md index 36441759fd..a84fd2930a 100644 --- a/translations/ja-JP/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/ja-JP/data/reusables/sponsors/review-and-publish-tier.md @@ -1 +1 @@ -1. 層の内容を確認してから、**Publish tier（層の公開）**をクリックしてください。 ![層の公開ボタン](/assets/images/help/sponsors/publish-tier-button.png) +1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/ja-JP/data/reusables/sponsors/review-tiers-to-select.md b/translations/ja-JP/data/reusables/sponsors/review-tiers-to-select.md new file mode 100644 index 0000000000..523a2c0a96 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/review-tiers-to-select.md @@ -0,0 +1 @@ +1. ページの右側で、"Select a tire（層の選択）"の下で利用可能なスポンサーシップ層をレビューしてください。 If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png) diff --git a/translations/ja-JP/data/reusables/sponsors/select-a-tier.md b/translations/ja-JP/data/reusables/sponsors/select-a-tier.md index 9e00725e09..1da5bab143 100644 --- a/translations/ja-JP/data/reusables/sponsors/select-a-tier.md +++ b/translations/ja-JP/data/reusables/sponsors/select-a-tier.md @@ -1 +1 @@ -1. ページの右側で、"Select a tire（層の選択）"の下で利用可能なスポンサーシップ層をレビューしてください。 そして、選択したい層の右で**Select（選択）**をクリックしてください。 ![層の選択ボックス](/assets/images/help/sponsors/select-a-tier-box.png) +1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![層の選択ボックス](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md b/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md index 06efbfc160..1b1f4699d5 100644 --- a/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md +++ b/translations/ja-JP/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. スポンサーシップは、既存の支払日、支払い方法、領収書を共有します。 +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 one-time or monthly payment amounts and benefits that are set by the sponsored account. スポンサーシップは、既存の支払日、支払い方法、領収書を共有します。 diff --git a/translations/ja-JP/data/reusables/sponsors/tier-details.md b/translations/ja-JP/data/reusables/sponsors/tier-details.md index e0c2029356..48ce54ab0e 100644 --- a/translations/ja-JP/data/reusables/sponsors/tier-details.md +++ b/translations/ja-JP/data/reusables/sponsors/tier-details.md @@ -1,3 +1,3 @@ -スポンサーが選択できる層として、最大で10個のスポンサーシップ層を作成できます。 各層にはそれぞれの米ドルでの月額と、新バージョンへの早期アクセスやプロジェクトのREADMEで取り上げられたりするといったメリットがあります。 +スポンサーが選択できる層として、最大で10個のスポンサーシップ層を作成できます。 Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). -Once you have published a tier, you can't edit the price of that tier. その代わりに、その層を止めて新しい層を作成できます。 既存のスポンサーは、スポンサーシップ層を変更するかキャンセルするまで、止められた層に残ります。 +Once you have published a tier, you can't edit the price of that tier. その代わりに、その層を止めて新しい層を作成できます。 Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/ja-JP/data/reusables/support/accessing-premium-content.md b/translations/ja-JP/data/reusables/support/accessing-premium-content.md index 6e2a4f23d5..e70d802bd4 100644 --- a/translations/ja-JP/data/reusables/support/accessing-premium-content.md +++ b/translations/ja-JP/data/reusables/support/accessing-premium-content.md @@ -1,4 +1,4 @@ ### プレミアムコンテンツにアクセスする -{% data variables.contact.contact_enterprise_portal %}にサインインすることによりプレミアムコンテンツにアクセスできます。 +{% data variables.contact.contact_landing_page_portal %}にサインインすることによりプレミアムコンテンツにアクセスできます。 diff --git a/translations/ja-JP/data/reusables/support/contacting-premium-support.md b/translations/ja-JP/data/reusables/support/contacting-premium-support.md index 7de1648fc4..4017bec593 100644 --- a/translations/ja-JP/data/reusables/support/contacting-premium-support.md +++ b/translations/ja-JP/data/reusables/support/contacting-premium-support.md @@ -1,4 +1,4 @@ ### {% data variables.contact.premium_support %} への連絡 -{% data variables.contact.premium_support %}の顧客は、{% data variables.contact.contact_enterprise_portal %} を使って問題を英語の文面でレポートできます。 電話を介して英語のサポートを受けることもできます。 {% data variables.contact.premium_support %}の電話番号については、{% data variables.contact.enterprise_portal %}の「[24x7 電話 サポート](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)」を参照してください。 +{% data variables.contact.premium_support %}の顧客は、{% data variables.contact.contact_landing_page_portal %} を使って問題を英語の文面でレポートできます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user_settings/billing_plans.md b/translations/ja-JP/data/reusables/user_settings/billing_plans.md new file mode 100644 index 0000000000..8d26ab1479 --- /dev/null +++ b/translations/ja-JP/data/reusables/user_settings/billing_plans.md @@ -0,0 +1 @@ +1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png) diff --git a/translations/ja-JP/data/variables/contact.yml b/translations/ja-JP/data/variables/contact.yml index 4c26836d8e..6f788ad1e7 100644 --- a/translations/ja-JP/data/variables/contact.yml +++ b/translations/ja-JP/data/variables/contact.yml @@ -24,9 +24,12 @@ contact_enterprise_portal: '[GitHub Enterprise Supportポータル](https://ente #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)' -#GitHub Support portal (for dotcom) +#GitHub Support portal (for dotcom - this sends users to a contact form) support_portal: 'GitHub Support ページ' contact_support_portal: '[GitHub Support ページ](https://support.github.com/contact)' +#GitHub Support portal (this sends users to the Support landing page) +landing_page_portal: 'GitHub Support ページ' +contact_landing_page_portal: '[GitHub Support ページ](https://support.github.com/)' #The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) community_support: 'GitHub Community Support' #The GitHub Community forum 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 28b45e002d..e5df3c50a6 100644 --- a/translations/ko-KR/content/actions/creating-actions/about-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/about-actions.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' topics: - - Action development - - Fundamentals + - 'Action development' + - 'Fundamentals' --- {% 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 0caa471152..aee84a97bc 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Action development + - 'Action development' --- {% 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 9a2b277f05..cd8d4abd44 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 @@ -1,6 +1,6 @@ --- title: Creating a Docker container action -intro: This guide shows you the minimal steps required to build a Docker container action. +intro: 'This guide shows you the minimal steps required to build a Docker container action.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Action development - - Docker + - 'Action development' + - 'Docker' --- {% 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 d2a0315692..10c738784f 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 @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Action development - - JavaScript + - 'Action development' + - 'JavaScript' --- {% 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 ecf66617a4..8b3e788429 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 @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: '참조' --- {% data reusables.actions.enterprise-beta %} 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 fe78546f07..11ca3c6367 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 @@ -12,7 +12,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: '참조' --- {% data reusables.actions.enterprise-beta %} @@ -58,7 +58,7 @@ inputs: When you specify an input to an action in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters. -For example, if a workflow defined the numOctocats and octocatEyeColor inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables. +For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables. #### `inputs.` @@ -76,6 +76,10 @@ For example, if a workflow defined the numOctocats and octocatEyeColor inputs, t **Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file. +#### `inputs..deprecationMessage` + +**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives. + ### `outputs` **Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions. For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input. 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 3d3706d537..41716d3e05 100644 --- a/translations/ko-KR/content/actions/guides/about-continuous-integration.md +++ b/translations/ko-KR/content/actions/guides/about-continuous-integration.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' topics: - - CI - - CD + - 'CI' + - 'CD' --- {% 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 a1e061aba6..6ab199b25f 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 @@ -9,9 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' topics: - - 패키징 + - '패키징' --- {% 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 d83decc5c6..da26176a8f 100644 --- a/translations/ko-KR/content/actions/guides/about-service-containers.md +++ b/translations/ko-KR/content/actions/guides/about-service-containers.md @@ -9,10 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' topics: - - Containers - - Docker + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md b/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md index 33711a86bb..5321565cfa 100644 --- a/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md +++ b/translations/ko-KR/content/actions/guides/adding-labels-to-issues.md @@ -1,15 +1,15 @@ --- title: Adding labels to issues -intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.' +intro: You can use {% data variables.product.prodname_actions %} to automatically label issues. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% 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 e263dfdd59..95ec085763 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CI - - Java - - Ant + - 'CI' + - 'Java' + - 'Ant' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Ant run: ant -noinput -buildfile build.xml ``` @@ -70,7 +71,7 @@ jobs: This workflow performs the following steps: 1. The `checkout` step downloads a copy of your repository on the runner. -2. The `setup-java` step configures the Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. The "Build with Ant" step runs the default target in your `build.xml` in non-interactive mode. The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs. @@ -91,9 +92,10 @@ If you use different commands to build your project, or you want to run a differ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Ant jar target run: ant -noinput -buildfile build-ci.xml jar ``` @@ -109,7 +111,11 @@ Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ant -noinput -buildfile build.xml - uses: actions/upload-artifact@v2 with: 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 24297bd6e3..9b0ecae80e 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CI - - Java - - Gradle + - 'CI' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Gradle run: ./gradlew build ``` @@ -70,7 +71,7 @@ jobs: This workflow performs the following steps: 1. The `checkout` step downloads a copy of your repository on the runner. -2. The `setup-java` step configures the Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. The "Build with Gradle" step runs the `gradlew` wrapper script to ensure that your code builds, tests pass, and a package can be created. The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs. @@ -91,9 +92,10 @@ If you use different commands to build your project, or you want to use a differ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Gradle package task run: ./gradlew -b ci.gradle package ``` @@ -107,10 +109,11 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Gradle packages uses: actions/cache@v2 with: @@ -143,7 +146,11 @@ Gradle will usually create output files like JARs, EARs, or WARs in the `build/l ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ./gradlew build - uses: actions/upload-artifact@v2 with: 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 98c85e4fbf..334218a0c6 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CI - - Java - - Maven + - 'CI' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Maven run: mvn --batch-mode --update-snapshots verify ``` @@ -70,7 +71,7 @@ jobs: This workflow performs the following steps: 1. The `checkout` step downloads a copy of your repository on the runner. -2. The `setup-java` step configures the Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. The "Build with Maven" step runs the Maven `package` target in non-interactive mode to ensure that your code builds, tests pass, and a package can be created. The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs. @@ -91,9 +92,10 @@ If you use different commands to build your project, or you want to use a differ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Maven verify phase run: mvn --batch-mode --update-snapshots verify ``` @@ -107,10 +109,11 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Maven packages uses: actions/cache@v2 with: @@ -134,7 +137,10 @@ Maven will usually create output files like JARs, EARs, or WARs in the `target` ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 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 index abe38e84c5..8b182bd3ba 100644 --- a/translations/ko-KR/content/actions/guides/building-and-testing-net.md +++ b/translations/ko-KR/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: ['3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -81,7 +81,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet: [ '2.2.103', '3.0', '3.1.x' ] + dotnet: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -201,7 +201,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 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 0365d27281..95f1845fa5 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 @@ -9,11 +9,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CI - - Node - - JavaScript + - 'CI' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} 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 f4c75808a4..5ad582cc75 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 @@ -8,10 +8,10 @@ versions: github-ae: '*' authors: - potatoqualitee -type: tutorial +type: '튜토리얼' topics: - - CI - - Powershell + - 'CI' + - 'Powershell' --- {% 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 66a850fb9f..a6e8299ce6 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 @@ -8,10 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CI - - Python + - 'CI' + - 'Python' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md b/translations/ko-KR/content/actions/guides/building-and-testing-ruby.md index 66ee7b2eee..150a865491 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 @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CI - - Ruby + - 'CI' + - 'Ruby' --- {% 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 a16b3c3fdf..796eb70073 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,9 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows + - 'Workflows' --- {% data reusables.actions.ae-beta %} diff --git a/translations/ko-KR/content/actions/guides/closing-inactive-issues.md b/translations/ko-KR/content/actions/guides/closing-inactive-issues.md index 6cd1cb2179..33fab07bef 100644 --- a/translations/ko-KR/content/actions/guides/closing-inactive-issues.md +++ b/translations/ko-KR/content/actions/guides/closing-inactive-issues.md @@ -1,15 +1,15 @@ --- title: Closing inactive issues -intro: 'You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time.' +intro: You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md index c1120b2731..e1a5d6a54c 100644 --- a/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/ko-KR/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md @@ -1,15 +1,15 @@ --- title: Commenting on an issue when a label is added -intro: 'You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied.' +intro: You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 ef6e505a25..3e63dd8087 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Containers - - Docker + - 'Containers' + - 'Docker' --- {% 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 0813690c69..9f54c46f4c 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Containers - - Docker + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md index afcce12612..c82f62a66c 100644 --- a/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/ko-KR/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CD - - Containers - - Amazon ECS + - 'CD' + - 'Containers' + - 'Amazon ECS' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md b/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md index 29e6186c7a..657442da55 100644 --- a/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/ko-KR/content/actions/guides/deploying-to-azure-app-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CD - - Containers - - Azure App Service + - 'CD' + - 'Containers' + - 'Azure App Service' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md index 01f388a439..ae8228915a 100644 --- a/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/ko-KR/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CD - - Containers - - Google Kubernetes Engine + - 'CD' + - 'Containers' + - 'Google Kubernetes Engine' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/ko-KR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 5d2fdaf714..41d6a57799 100644 --- a/translations/ko-KR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/ko-KR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CI - - Xcode + - 'CI' + - 'Xcode' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/moving-assigned-issues-on-project-boards.md b/translations/ko-KR/content/actions/guides/moving-assigned-issues-on-project-boards.md index f82ea01330..a21c0866ee 100644 --- a/translations/ko-KR/content/actions/guides/moving-assigned-issues-on-project-boards.md +++ b/translations/ko-KR/content/actions/guides/moving-assigned-issues-on-project-boards.md @@ -1,15 +1,15 @@ --- title: Moving assigned issues on project boards -intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.' +intro: You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 18d6bfd142..814c6eb432 100644 --- a/translations/ko-KR/content/actions/guides/publishing-docker-images.md +++ b/translations/ko-KR/content/actions/guides/publishing-docker-images.md @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - 패키징 - - Publishing - - Docker + - '패키징' + - 'Publishing' + - 'Docker' --- {% 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 c26453dc80..e41d8f01bf 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - 패키징 - - Publishing - - Java - - Gradle + - '패키징' + - 'Publishing' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -143,9 +144,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -209,9 +211,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to the Maven Central Repository run: gradle publish env: 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 0e6792bf63..c70aa2b43f 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - 패키징 - - Publishing - - Java - - Maven + - '패키징' + - 'Publishing' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -147,9 +148,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: mvn --batch-mode deploy env: @@ -183,9 +185,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java for publishing to Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -195,9 +198,10 @@ jobs: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to GitHub Packages run: mvn --batch-mode deploy env: 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 0bfbb66685..d467fa2fdd 100644 --- a/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md @@ -9,12 +9,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - 패키징 - - Publishing - - Node - - JavaScript + - '패키징' + - 'Publishing' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index fbdec485ed..f09609238c 100644 --- a/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/ko-KR/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -1,15 +1,15 @@ --- title: Removing a label when a card is added to a project board column -intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board.' +intro: You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md b/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md index 583eea26e7..4603d933f9 100644 --- a/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md +++ b/translations/ko-KR/content/actions/guides/scheduling-issue-creation.md @@ -1,15 +1,15 @@ --- title: Scheduling issue creation -intro: 'You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews.' +intro: You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index c9a5df2b4a..897e8497e1 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 @@ -12,10 +12,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows - - CI + - 'Workflows' + - 'CI' --- {% 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 49f4fea150..a043c5b2ae 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 @@ -12,9 +12,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Workflows + - 'Workflows' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/using-github-actions-for-project-management.md b/translations/ko-KR/content/actions/guides/using-github-actions-for-project-management.md index d1b1191979..be3bc7e6f2 100644 --- a/translations/ko-KR/content/actions/guides/using-github-actions-for-project-management.md +++ b/translations/ko-KR/content/actions/guides/using-github-actions-for-project-management.md @@ -1,14 +1,14 @@ --- title: Using GitHub Actions for project management -intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.' +intro: You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' topics: - - Project management + - 'Project management' --- You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board. 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 8a3b96d95c..2cad6a79f2 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -125,7 +125,7 @@ You must ensure that the self-hosted runner has appropriate network access to co For example, if your instance name is `octoghae`, then you will need to allow the self-hosted runner to access `octoghae.github.com`. If you use an IP address allow list for your -{% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)." +{% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)." {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -145,7 +145,7 @@ pkg-containers.githubusercontent.com pkg-containers-az.githubusercontent.com ``` -If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". +If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". {% else %} 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 697a86c796..013cbf8835 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 cbfa198d10..0a1bd76bcc 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +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 41e25d5c29..2d9ab60cce 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 2079b28a0d..2e64614f5d 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 @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +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 d56c4d03b4..d0dc0fa771 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 beef57365d..a029c37570 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 0dcede94a7..96edf127bf 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 @@ -5,7 +5,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 e67d3b62d6..6c1c2735f7 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' --- {% data reusables.actions.ae-self-hosted-runners-notice %} diff --git a/translations/ko-KR/content/actions/index.md b/translations/ko-KR/content/actions/index.md index d32dfec985..0f1b4b9341 100644 --- a/translations/ko-KR/content/actions/index.md +++ b/translations/ko-KR/content/actions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /actions/reference/encrypted-secrets changelog: label: 'actions' - prefix: 'GitHub Actions: ' + prefix: 'GitHub Actions:' product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ 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 2456069c27..603300b653 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' topics: - - Fundamentals + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} 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 26bc483559..e36f3b6259 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 @@ -10,9 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '개요' topics: - - Fundamentals + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} 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 27e5288030..87eca23b14 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Azure Pipelines - - Migration - - CI - - CD + - 'Azure Pipelines' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 7c87a322a0..f13ba6f769 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - CircleCI - - Migration - - CI - - CD + - 'CircleCI' + - 'Migration' + - 'CI' + - 'CD' --- {% 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 0013d4bf65..bfbbd784da 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 @@ -5,12 +5,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - GitLab - - Migration - - CI - - CD + - 'GitLab' + - 'Migration' + - 'CI' + - 'CD' --- {% 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 f067a9d771..68c038f5a6 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Jenkins - - Migration - - CI - - CD + - 'Jenkins' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 a1e7afda06..0bb17f5320 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '튜토리얼' topics: - - Travis CI - - Migration - - CI - - CD + - 'Travis CI' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 5eb77d6e2e..0a2f05840e 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,13 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: overview + github-ae: '*' +type: '개요' topics: - - 보안 + - '보안' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### 개요 @@ -22,9 +24,9 @@ This guide explains how to configure security hardening for certain {% data vari ### Using secrets -Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}. +Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}. -Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps the minimize risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime. +Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps minimize the risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime. To help prevent accidental disclosure, {% data variables.product.product_name %} uses a mechanism that attempts to redact any secrets that appear in run logs. This redaction looks for exact matches of any configured secrets, as well as common encodings of the values, such as Base64. However, because there are multiple ways a secret value can be transformed, this redaction is not guaranteed. As a result, there are certain proactive steps and good practices you should follow to help ensure secrets are redacted, and to limit other risks associated with secrets: @@ -41,7 +43,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %} - **Audit and rotate registered secrets** - Periodically review the registered secrets to confirm they are still required. Remove those that are no longer needed. - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - **Consider requiring review for access to secrets** - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)." {% endif %} @@ -75,7 +77,7 @@ This means that a compromise of a single action within a workflow can be very si ### Considering cross-repository access -{% data variables.product.product_name %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so having the `GITHUB_TOKEN` for one repository grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators. +{% data variables.product.prodname_actions %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so allowing the `GITHUB_TOKEN` for one repository to grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators. We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended. @@ -115,33 +117,68 @@ Some customers might attempt to partially mitigate these risks by implementing s You can use the audit log to monitor administrative tasks in an organization. The audit log records the type of action, when it was run, and which user account performed the action. -For example, you can use the audit log to track the `action:org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png) +For example, you can use the audit log to track the `org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png) -The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." + +{% if currentVersion == "free-pro-team@latest" %} +#### Events for environments + +| 동작 | 설명 | +| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `environment.remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Events for configuration changes +| 동작 | 설명 | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +{% endif %} #### Events for secret management -| 동작 | 설명 | -| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `action:org.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). | -| `action:org.remove_actions_secret` | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:org.update_actions_secret` | Triggered when a organization admin updates a {% data variables.product.prodname_actions %} secret. | -| `action:repo.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). | -| `action:repo.remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:repo.update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret. | +| 동작 | 설명 | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `org.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)." | +| `org.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed. | +| `org.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated. | +| `repo.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." | +| `repo.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed. | +| `repo.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated. | #### Events for self-hosted runners -| 동작 | 설명 | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.register_self_hosted_runner` | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | -| `action:org.remove_self_hosted_runner` | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | -| `action:repo.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). | -| `action:repo.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). | +| 동작 | 설명 | +| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% else %} | | +| `enterprise.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an enterprise](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)." | +| `enterprise.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. | +| `enterprise.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." | +| `enterprise.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI. This event is not included when you export the audit log as JSON data or a CSV file. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" and "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."{% endif %} +| `org.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." | +| `org.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see [Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | +| `org.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." | +| `org.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `org.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | +| `repo.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `repo.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." | +| `repo.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | #### Events for self-hosted runner groups -| 동작 | 설명 | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.runner_group_created` | Triggered when an organization admin [creates a self-hosted runner group](/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` | Triggered when an organization admin removes a self-hosted runner group. | -| `action:org.runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | -| `action:org.runner_group_runners_added` | Triggered when an organization admin [adds a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +| 동작 | 설명 | +| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `enterprise.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an enterprise](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)." | +| `enterprise.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `enterprise.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. | +| `enterprise.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." | +| `enterprise.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `org.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." | +| `org.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `org.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." | +| `org.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | + +#### Events for workflow activities + +{% data reusables.actions.actions-audit-events-workflow %} diff --git a/translations/ko-KR/content/actions/quickstart.md b/translations/ko-KR/content/actions/quickstart.md index aeecba6e21..a2fa4e00b8 100644 --- a/translations/ko-KR/content/actions/quickstart.md +++ b/translations/ko-KR/content/actions/quickstart.md @@ -1,6 +1,6 @@ --- title: Quickstart for GitHub Actions -intro: 'Add a {% data variables.product.prodname_actions %} workflow to an existing repository in 5 minutes or less.' +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates @@ -19,57 +19,58 @@ topics: ### Introduction -You only need an existing {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that lints multiple coding languages using the [{% data variables.product.prodname_dotcom %} Super-Linter action](https://github.com/github/super-linter). The workflow uses Super-Linter to validate your source code every time a new commit is pushed to your repository. +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. + +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. ### Creating your first workflow -1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `superlinter.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." -2. Copy the following YAML contents into the `superlinter.yml` file. **Note:** If your default branch is not `main`, update the value of `DEFAULT_BRANCH` to match your repository's default branch name. +1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." +2. Copy the following YAML contents into the `github-actions-demo.yml` file: {% raw %} ```yaml{:copy} - name: Super-Linter - - # Run this workflow every time a new commit pushed to your repository - on: push - + name: GitHub Actions Demo + 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 + Explore-GitHub-Actions: runs-on: ubuntu-latest - steps: - # Checks out a copy of your repository on the ubuntu-latest machine - - name: Checkout code + - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event." + - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!" + - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}." + - name: Check out repository code uses: actions/checkout@v2 + - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner." + - run: echo "🖥️ The workflow is now ready to test your code on the runner." + - name: List files in the repository + run: | + ls ${{ github.workspace }} + - run: echo "🍏 This job's status is ${{ job.status }}." - # 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. To run your workflow, scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. ![Commit workflow file](/assets/images/commit-workflow-file.png) +3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. ![Commit workflow file](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -Committing the workflow file in your repository triggers the `push` event and runs your workflow. +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. ### Viewing your workflow results {% 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" or currentVersion == "github-ae@latest" %} -1. Under **Jobs** or in the visualization graph, click the **Lint code base** job. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) -{% else %} -1. In the left sidebar, click the **Lint code base** job. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) -{% endif %} -{% data reusables.repositories.view-failed-job-results-superlinter %} +1. In the left sidebar, click the workflow you want to see. + + ![Workflow list in left sidebar](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +1. From the list of workflow runs, click the name of the run you want to see. + + ![Name of workflow run](/assets/images/help/repository/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. + + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. + + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) ### More workflow templates @@ -77,74 +78,12 @@ Committing the workflow file in your repository triggers the `push` event and ru ### 다음 단계 -The super-linter workflow you just added runs each time code is pushed to your repository to help you spot errors and inconsistencies in your code. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}: +The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}: -- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial -- "[Guides](/actions/guides)" for specific uses cases and examples -- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action +- Your repository can contain multiple workflows that trigger different jobs based on different events. +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. - +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial. +- "[Guides](/actions/guides)" for specific uses cases and examples. diff --git a/translations/ko-KR/content/actions/reference/environment-variables.md b/translations/ko-KR/content/actions/reference/environment-variables.md index b127119509..9044dde564 100644 --- a/translations/ko-KR/content/actions/reference/environment-variables.md +++ b/translations/ko-KR/content/actions/reference/environment-variables.md @@ -22,6 +22,7 @@ versions: To set custom environment variables, you need to specify the variables in the workflow file. 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. For more information, see "[Workflow syntax for {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)." +{% raw %} ```yaml jobs: weekday_job: @@ -30,13 +31,14 @@ jobs: DAY_OF_WEEK: Mon steps: - name: "Hello world when it's Monday" - if: env.DAY_OF_WEEK == 'Mon' + if: ${{ env.DAY_OF_WEEK == 'Mon' }} run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" env: FIRST_NAME: Mona middle_name: The Last_Name: Octocat ``` +{% endraw %} To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables. diff --git a/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md b/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md index 925a17ae92..016b0ba975 100644 --- a/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/ko-KR/content/actions/reference/usage-limits-billing-and-administration.md @@ -70,7 +70,7 @@ You can configure the artifact and log retention period for your repository, org For more information, see: - [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your repository](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) -- [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) - [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your enterprise](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) {% endif %} @@ -80,7 +80,7 @@ For more information, see: For more information, see: - "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)" -- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} +- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" for {% data variables.product.prodname_ghe_cloud %}{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} diff --git a/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 078de4a7b6..8ba7bb0a34 100644 --- a/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/ko-KR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -21,7 +21,7 @@ After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_ma * Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization. * Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}. -For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, 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)." +For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ### 빌드전 요구 사양 diff --git a/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index 39ec7320c8..bd4976949b 100644 --- a/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/ko-KR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -28,7 +28,7 @@ The provisioning application on your IdP communicates with {% data variables.pro {% data reusables.scim.supported-idps %} -When you set up user provisioning with a supported IdP, you can also assign or unassign the application for {% data variables.product.product_name %} to groups of users. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. 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)." +When you set up user provisioning with a supported IdP, you can also assign or unassign the application for {% data variables.product.product_name %} to groups of users. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ### 빌드전 요구 사양 diff --git a/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index 0fd0e9dcd6..98e7414d45 100644 --- a/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/ko-KR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -13,7 +13,7 @@ By default, authorized users can access your enterprise from any IP address. Ent {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance. diff --git a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md index 661f8edb15..36389bf8a0 100644 --- a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md +++ b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md @@ -37,7 +37,7 @@ In addition to all of the benefits of {% data variables.contact.enterprise_suppo {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} For more information, see "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)." +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md index da58f75816..b2d3179141 100644 --- a/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md +++ b/translations/ko-KR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md @@ -35,7 +35,7 @@ In addition to all of the benefits of {% data variables.contact.enterprise_suppo {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} For more information, see "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)." +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/ko-KR/content/admin/github-actions/index.md b/translations/ko-KR/content/admin/github-actions/index.md index c9e97cc4b5..8347208b5f 100644 --- a/translations/ko-KR/content/admin/github-actions/index.md +++ b/translations/ko-KR/content/admin/github-actions/index.md @@ -32,6 +32,7 @@ topics: {% 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 /using-the-latest-version-of-the-official-bundled-actions %} {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} {% topic_link_in_list /advanced-configuration-and-troubleshooting %} 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 e7c51c42e8..d478e0a9f8 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 @@ -28,8 +28,21 @@ The `actions-sync` tool can only download actions from {% data variables.product ### 빌드전 요구 사양 -* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." * You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. + + {% note %} + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + + {% endnote %} + + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." + + ```shell + ghe-org-admin-promote -u USERNAME -o actions + ``` ### Example: Using the `actions-sync` tool diff --git a/translations/ko-KR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ko-KR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md new file mode 100644 index 0000000000..7e1334cdf4 --- /dev/null +++ b/translations/ko-KR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md @@ -0,0 +1,45 @@ +--- +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '>=2.22' +topics: + - 엔터프라이즈 +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server). + +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}. + +Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}: + +- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}. +- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions. + +These options are described in more detail in the following sections. + +### Using actions-sync to update a bundled action + +To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." + +### Using actions from {% data variables.product.prodname_dotcom_the_website %} + +{% data reusables.github-actions.actions-github-connect-requirement %} + +Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file. + +### Using the latest version by removing the specific action's tag + +{% data reusables.github-actions.actions-github-connect-requirement %} + +If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)." + +For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}: + +1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository. +1. Create a workflow that uses `actions/setup-python` with the `v2` tag. + +When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}. 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 7310297fd2..64ba147984 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 @@ -1,6 +1,6 @@ --- title: Installing GitHub Enterprise Server on Hyper-V -intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2016.' +intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2019.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v @@ -13,7 +13,7 @@ topics: ### 빌드전 요구 사양 - {% data reusables.enterprise_installation.software-license %} -- You must have Windows Server 2008 through Windows Server 2016, which support Hyper-V. +- You must have Windows Server 2008 through Windows Server 2019, which support Hyper-V. - Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). However, we recommend using the Windows PowerShell command-line shell for initial setup. Examples using PowerShell are included below. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)." ### Hardware considerations diff --git a/translations/ko-KR/content/admin/overview/github-ae-release-notes.md b/translations/ko-KR/content/admin/overview/github-ae-release-notes.md index 6096736201..c5692d467b 100644 --- a/translations/ko-KR/content/admin/overview/github-ae-release-notes.md +++ b/translations/ko-KR/content/admin/overview/github-ae-release-notes.md @@ -29,7 +29,7 @@ During this beta, {% data variables.product.prodname_advanced_security %} featur #### Manage teams from your identity provider (IdP) -Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group. 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)." +Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." #### IP allow lists beta @@ -37,7 +37,7 @@ Enterprise and organization owners can now use IP allow lists to restrict traffi This functionality is provided in addition to the ability to request network security group changes that filter traffic to the entirety of the {% data variables.product.product_name %} tenant. -For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." #### Pull request auto-merge @@ -47,8 +47,8 @@ With auto-merge, pull requests can be set to merge automatically when all merge #### Developer changes -- [Organization owners can now disable publication](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites. -- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). +- [Organization owners can now disable publication](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites. +- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - When writing an issue or pull request, the list syntax for bullets, numbers, and tasks will now be autocompleted after you press `return` or `enter`. - You can now delete a directory in a repository from the repository page. When navigating to a directory, a new kebab button next to the "Add file" button gives the option to delete the directory. - It’s now easier and faster to [reference issues or pull requests](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), with search across multiple words after the "#". @@ -65,7 +65,7 @@ With auto-merge, pull requests can be set to merge automatically when all merge ##### Default branch renaming -Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[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)." +Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." Existing repositories are unaffected by these settings, and their default branch name will not be changed. 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 ba25c4ecd0..b152cffc44 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 @@ -66,17 +66,16 @@ Mandatory messages have a variety of uses. - 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 %} -{% note %} - -**Note:** After you configure a mandatory message for {% data variables.product.product_location %}, you cannot change or remove the message. - -{% endnote %} - - 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)." +{% note %} + +**Note:** If you change the mandatory message for {% data variables.product.product_location %}, users who have already acknowledged the message will not see the new message. + +{% endnote %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} diff --git a/translations/ko-KR/content/code-security/secret-security/about-secret-scanning.md b/translations/ko-KR/content/code-security/secret-security/about-secret-scanning.md index 32817e265e..ed0efc5acd 100644 --- a/translations/ko-KR/content/code-security/secret-security/about-secret-scanning.md +++ b/translations/ko-KR/content/code-security/secret-security/about-secret-scanning.md @@ -45,7 +45,7 @@ When {% data variables.product.prodname_secret_scanning %} detects a set of cred {% 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)." +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](/organizations/keeping-your-organization-secure/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. diff --git a/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md index 9469c2c6e0..93f89e6686 100644 --- a/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md +++ b/translations/ko-KR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md @@ -70,4 +70,4 @@ You can also ignore individual alerts from {% data variables.product.prodname_se ### 더 읽을거리 -- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/ko-KR/content/code-security/secure-coding/index.md b/translations/ko-KR/content/code-security/secure-coding/index.md index 55fe02fa94..080af21b9c 100644 --- a/translations/ko-KR/content/code-security/secure-coding/index.md +++ b/translations/ko-KR/content/code-security/secure-coding/index.md @@ -1,7 +1,7 @@ --- title: Finding security vulnerabilities and errors in your code shortTitle: Secure coding -intro: 'Keep your code secure by using secret scanning to identify and fix potential security vulnerabilities and other errors in your code.' +intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code diff --git a/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md index 5428cb4663..37a2cfa6a5 100644 --- a/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ko-KR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md @@ -45,7 +45,14 @@ You need write permission to view a summary of all the alerts for a repository o {% 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) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} +1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) @@ -57,7 +64,11 @@ If you have write permission for a repository, you can view fixed alerts by view 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +{% else %} +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} @@ -110,11 +121,19 @@ To dismiss or delete alerts: 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) +{% else %} + ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) +{% endif %} 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) diff --git a/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md index 9a83541df3..5479a16cfb 100644 --- a/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md +++ b/translations/ko-KR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md @@ -32,7 +32,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -72,7 +72,11 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} {% endnote %} @@ -98,7 +102,11 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% else %} + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) +{% endif %} The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. diff --git a/translations/ko-KR/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/ko-KR/content/code-security/security-advisories/editing-a-security-advisory.md index 1f5cfbc3a9..6b38fafeb7 100644 --- a/translations/ko-KR/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/ko-KR/content/code-security/security-advisories/editing-a-security-advisory.md @@ -17,6 +17,8 @@ You can credit people who helped discover, report, or fix a security vulnerabili If someone accepts credit, the person's username appears in the "Credits" section of the security advisory. Anyone with read access to the repository can see the advisory and the people who accepted credit for it. +If you believe you should be credited for a security advisory, please contact the person who created the advisory and ask them to edit the advisory to include your credit. Only the creator of the advisory can credit you, so please don't contact GitHub Support about credits for security advisories. + ### Editing a security advisory {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/ko-KR/content/code-security/security-overview/exploring-security-alerts.md b/translations/ko-KR/content/code-security/security-overview/exploring-security-alerts.md index ea7c8b5269..a607a226e9 100644 --- a/translations/ko-KR/content/code-security/security-overview/exploring-security-alerts.md +++ b/translations/ko-KR/content/code-security/security-overview/exploring-security-alerts.md @@ -11,7 +11,7 @@ versions: ### About the security overview -You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository)." +You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)." diff --git a/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md index 8da4971bf9..64eeb4ab94 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md @@ -49,9 +49,9 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} diff --git a/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md index c6775c87fe..d831bca031 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/about-dependabot-version-updates.md @@ -12,8 +12,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot_version_updates %} {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. diff --git a/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md index db9d230aa4..ba216c85df 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/about-the-dependency-graph.md @@ -90,6 +90,6 @@ The recommended formats explicitly define which versions are used for all direct - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md index 180dcc02a5..242aad727b 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md @@ -11,8 +11,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About the *dependabot.yml* file The {% data variables.product.prodname_dependabot %} configuration file, *dependabot.yml*, uses YAML syntax. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." @@ -323,7 +321,7 @@ updates: {% note %} -**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. 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-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." +**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." {% endnote %} diff --git a/translations/ko-KR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md index 2c2def289a..759c05fc6f 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md @@ -49,7 +49,7 @@ If security updates are not enabled for your repository and you don't know why, 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)." +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](/organizations/keeping-your-organization-secure/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)." diff --git a/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md index 70d6d1706f..7040d60150 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md @@ -16,7 +16,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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" %} diff --git a/translations/ko-KR/content/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/customizing-dependency-updates.md index 7ca4077ba2..f058194f72 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/customizing-dependency-updates.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/customizing-dependency-updates.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About customizing dependency updates After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could: diff --git a/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md index 86e61e527a..784a8ccb2f 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md @@ -12,8 +12,6 @@ topics: -{% data reusables.dependabot.beta-note-no-link %} - ### About version updates for dependencies You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a *dependabot.yml* configuration file in to your repository's `.github` directory. {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. For each package manager's dependencies that you want to update, you must specify the location of the package manifest files and how often to check for updates to the dependencies listed in those files. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -117,7 +115,7 @@ updates: interval: "daily" # Overwrite any ignores created using `@dependabot ignore` commands ignore: - # Ignore updates to packages that start 'aws' + # Ignore updates to packages that start with 'aws' # Wildcards match zero or more arbitrary characters - dependency-name: "aws*" # Ignore some updates to the 'express' package diff --git a/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md index 3462677b7e..d6a8cc3580 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md @@ -74,7 +74,7 @@ For public repositories, the dependents view shows how the repository is used by Repository administrators can enable or disable the dependency graph for private repositories. -You can also enable or disable the dependency graph 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)." +You can also enable or disable the dependency graph 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -114,7 +114,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ### 더 읽을거리 - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)" {% endif %} diff --git a/translations/ko-KR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/ko-KR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md index 9a5d8f1580..848ee2aac5 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot_version_updates %} for actions Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/ko-KR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md index 0f1e222c63..b58accff31 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Viewing dependencies monitored by {% data variables.product.prodname_dependabot %} After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." diff --git a/translations/ko-KR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/ko-KR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md index 899d763033..53a261fe7d 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot %} pull requests {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md index 82aa1248e8..cb1f319553 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md @@ -11,8 +11,6 @@ topics: - 보안 --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot %} errors {% data reusables.dependabot.pull-request-introduction %} 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 c2570784ec..bf92e4ba84 100644 --- a/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/authorizing-oauth-apps.md @@ -86,18 +86,18 @@ Exchange this `code` for an access token: By default, the response takes the following form: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer You can also receive the content in different formats depending on the Accept header: Accept: application/json - {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} + {"access_token":"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} Accept: application/xml bearer repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} #### 3. Use the access token to access the API @@ -207,7 +207,7 @@ Once the user has authorized, the app will receive an access token that can be u ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "user" } @@ -304,3 +304,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} * "[Device flow errors](#errors-for-the-device-flow)" {% endif %} + +### 더 읽을거리 + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md index 19283607b5..744300593a 100644 --- a/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ko-KR/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -54,16 +54,18 @@ The person creating the app will be redirected to a GitHub page with an input fi ##### GitHub App Manifest parameters - | 이름 | 유형 | 설명 | - | --------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `문자열` | The name of the GitHub App. | - | `url` | `문자열` | **Required.** The homepage of your GitHub App. | - | `hook_attributes` | `개체` | The configuration of the GitHub App's webhook. | - | `redirect_url` | `문자열` | The full URL to redirect to after the person installs the GitHub App. | - | `설명` | `문자열` | A description of the GitHub App. | - | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | - | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | - | `default_permissions` | `개체` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | + | 이름 | 유형 | 설명 | + | --------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `문자열` | The name of the GitHub App. | + | `url` | `문자열` | **Required.** The homepage of your GitHub App. | + | `hook_attributes` | `개체` | The configuration of the GitHub App's webhook. | + | `redirect_url` | `문자열` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %} + | `callback_url` | `문자열` | A full URL to redirect to after someone authorizes an installation.{% endif %} + | `설명` | `문자열` | A description of the GitHub App. | + | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | + | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | + | `default_permissions` | `개체` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | The `hook_attributes` object has the following key: @@ -96,7 +98,10 @@ This example uses a form on a web page with a button that triggers the `POST` re "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -111,10 +116,11 @@ This example uses a form on a web page with a button that triggers the `POST` re }) ``` + This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app. ```html -
+ Create a GitHub App Manifest:
@@ -127,7 +133,10 @@ This example uses a form on a web page with a button that triggers the `POST` re "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -147,11 +156,11 @@ This example uses a form on a web page with a button that triggers the `POST` re When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. 예시: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. 예시: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 #### 3. You exchange the temporary code to retrieve the app configuration diff --git a/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md index b0ed9ea5e3..da8f787f5e 100644 --- a/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/ko-KR/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -22,9 +22,15 @@ The person creating the app can edit the preselected values from the {% data var The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: - ``` - {% 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 - ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} +``` +{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite +``` +{% else %} +``` +{% 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 +``` +{% endif %} The complete list of available query parameters, permissions, and events is listed in the sections below. @@ -34,8 +40,9 @@ The complete list of available query parameters, permissions, and events is list | -------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | `문자열` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. | | `설명` | `문자열` | A description of the {% data variables.product.prodname_github_app %}. | - | `url` | `문자열` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage. | - | `callback_url` | `문자열` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. | + | `url` | `문자열` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} + | `callback_url` | `문자열` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} | `request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. | | `setup_url` | `문자열` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation. | | `setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed. | 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 929b29f815..b74fb51eca 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 @@ -845,7 +845,7 @@ Here are a few common problems and some suggested solutions. If you run into any **A:** If you see the following error, you haven't deleted the checkout of the repository in one or both of the `initiate_check_run` or `take_requested_action` methods: ```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.: + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: ``` Compare your code to the `server.rb` file to ensure you have the same code in your `initiate_check_run` and `take_requested_action` methods. diff --git a/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 0ba43f069e..e5a28daece 100644 --- a/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ko-KR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -94,9 +94,9 @@ By default, the response takes the following form. The response parameters `expi ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -106,7 +106,7 @@ By default, the response takes the following form. The response parameters `expi By default, the response takes the following form: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer {% endif %} @@ -934,3 +934,11 @@ While most of your API interaction should occur using your server-to-server inst * [Get a workflow](/rest/reference/actions#get-a-workflow) * [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### 더 읽을거리 + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md index bad8d34b5a..922a4bae2a 100644 --- a/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,9 +42,9 @@ This callback request will send you a new access token and a new refresh token. ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" @@ -73,3 +73,11 @@ If you want your app to use non-expiring user-to-server access tokens, you can d Existing {% data variables.product.prodname_github_app %}s using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app. Enabling expiring user tokens for existing {% data variables.product.prodname_github_app %}s requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### 더 읽을거리 + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md b/translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md index cb527f39f6..05f9449eb8 100644 --- a/translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md +++ b/translations/ko-KR/content/developers/github-marketplace/about-marketplace-badges.md @@ -13,7 +13,7 @@ Certain apps on the {% data variables.product.prodname_marketplace %} have the { - Verified ownership of their domain and has a verified badge on their profile - Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization -- Required two-factor authentication for their organization. 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)." +- Required two-factor authentication for their organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)." ![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png) diff --git a/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md index 28a9dd01c3..9644f96029 100644 --- a/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md +++ b/translations/ko-KR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -22,8 +22,8 @@ To offer paid plans for your app, the app must be owned by an organization and y 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) 1. Under "Publisher Verification", complete the information in the checklist: - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. - - Ensure that Two-factor authentication is enabled for your organization. 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)." - - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + - Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)." + - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) diff --git a/translations/ko-KR/content/developers/overview/managing-deploy-keys.md b/translations/ko-KR/content/developers/overview/managing-deploy-keys.md index 975af736c0..1bbe0cb7ab 100644 --- a/translations/ko-KR/content/developers/overview/managing-deploy-keys.md +++ b/translations/ko-KR/content/developers/overview/managing-deploy-keys.md @@ -112,6 +112,36 @@ You can then use the hostname's alias to interact with the repository using SSH, $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` +### Server-to-server tokens + +If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. + +Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps). + +##### Pros + +- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API). +- Dedicated rate limits that grow with your organization. +- Decoupled from GitHub user identities, so they do not consume any licensed seats. +- Never granted a password, so cannot be directly signed in to. + +##### Cons + +- Additional setup is needed to create the GitHub App. +- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code. + +##### Setup + +1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private. +1. Determine the permissions your GitHub App requires, such as read-only access to repository contents. +1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app). +1. Note your GitHub App `id`. +1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key). +1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization. +1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). +1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). +1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client. + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/ko-KR/content/developers/overview/secret-scanning.md b/translations/ko-KR/content/developers/overview/secret-scanning.md index a6e755ac9c..6df6574480 100644 --- a/translations/ko-KR/content/developers/overview/secret-scanning.md +++ b/translations/ko-KR/content/developers/overview/secret-scanning.md @@ -17,12 +17,6 @@ When a match of your secret format is found in a public repository, a payload is When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -{% note %} - -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. - -{% endnote %} - This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. ### The {% data variables.product.prodname_secret_scanning %} process diff --git a/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md b/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md index 72814d2867..0b298c73fe 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/github-event-types.md @@ -183,6 +183,20 @@ This event returns an empty `payload` object. {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} +### PullRequestReviewEvent + +{% data reusables.webhooks.pull_request_review_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Event `payload` object + +| 키 | 유형 | 설명 | +| -------------- | ----- | ------------------------------------------------ | +| `동작` | `문자열` | The action that was performed. Can be `created`. | +| `pull_request` | `개체` | The pull request the review pertains to. | +| `검토` | `개체` | The review that was affected. | + ### PullRequestReviewCommentEvent {% data reusables.webhooks.pull_request_review_comment_short_desc %} @@ -200,6 +214,8 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} +#### Event `payload` object + | 키 | 유형 | 설명 | | -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `push_id` | `integer` | Unique identifier for the push. | diff --git a/translations/ko-KR/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/ko-KR/content/developers/webhooks-and-events/securing-your-webhooks.md index 7f618b9d0c..2e64cf8de1 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/securing-your-webhooks.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -93,4 +93,4 @@ Your language and server implementations may differ from this example code. Howe * Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 0e31a82227..989c74f53c 100644 --- a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -19,7 +19,7 @@ With {% data variables.product.prodname_discussions %}, the community for your p You don't need to close a discussion like you close an issue or a pull request. -If a repository administrator or project maintainer enables discussions for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +If a repository administrator or project maintainer enables discussions for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." For more information about management of discussions for your repository, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." diff --git a/translations/ko-KR/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/ko-KR/content/discussions/guides/best-practices-for-community-conversations-on-github.md index c0ff62f47a..1eed00c153 100644 --- a/translations/ko-KR/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/ko-KR/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -29,7 +29,7 @@ You can use {% data variables.product.prodname_discussions %} to discuss big pic Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see "[About issues](/articles/about-issues)." Pull requests allow you to comment directly on proposed changes. For more information, see "[About pull requests](/articles/about-pull-requests)" and "[Commenting on a pull request](/articles/commenting-on-a-pull-request)." -{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." ### Following contributing guidelines diff --git a/translations/ko-KR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/ko-KR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 8ded0aaa3a..6c12ee38c7 100644 --- a/translations/ko-KR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/ko-KR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -21,7 +21,7 @@ The most helpful contributors for the past 30 days are highlighted on the {% dat People with triage permissions for a repository can help moderate a project's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." -For more information about repository permission levels and {% data variables.product.prodname_discussions %}, see "[Repository permissions levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +For more information about repository permission levels and {% data variables.product.prodname_discussions %}, see "[Repository permissions levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." ### Step 3: Change permissions levels for top contributors diff --git a/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index e75e4628a9..561e475606 100644 --- a/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -12,7 +12,7 @@ versions: {% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." -Organization owners can choose the permissions required to create a discussion for repositories owned by the organization. For more information, see "[Managing discussion creation for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization)." +Organization owners can choose the permissions required to create a discussion for repositories owned by the organization. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)." As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating a code of conduct or contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md index 72f6d0950d..eb1f42f298 100644 --- a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -16,3 +16,7 @@ Professors, teachers and mentors can use the Campus Advisors online training to **Note:** As an instructor, you can't create {% data variables.product.prodname_dotcom %} accounts for your students. Students must create their own {% data variables.product.prodname_dotcom %} accounts. {% endnote %} + +Teachers can manage a course on software development with {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} allows you to distribute code, provide feedback, and manage coursework using {% data variables.product.product_name %}. For more information, see "[Manage coursework with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)." + +If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" or "[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/)." diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md index 1dad791c70..fb124ca41c 100644 --- a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -9,4 +9,6 @@ versions: free-pro-team: '*' --- -Learn public speaking skills, technical writing, community leadership, and software development skills as a {% data variables.product.prodname_dotcom %} Campus Expert. For more information, see "[Campus Experts](https://education.github.com/students/experts)." +Learn public speaking skills, technical writing, community leadership, and software development skills as a {% data variables.product.prodname_dotcom %} Campus Expert. + +To learn more about training programs for student leaders and teachers, see "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)" and "[Campus Advisors](https://education.github.com/teachers/advisors)." diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md new file mode 100644 index 0000000000..207dcedc5d --- /dev/null +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Campus Program +intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes: + +- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments +- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our Campus Advisor program +- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners +- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} + +Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join. + +For more information, see the [official {% data variables.product.prodname_campus_program %}](https://education.github.com/schools) page. + +If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" or "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)." diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md index 9dda1a2a4f..46f1c88ab4 100644 --- a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -13,7 +13,7 @@ versions: ### Table of Contents {% topic_link_in_list /use-github-at-your-educational-institution %} - {% link_in_list /about-github-education %} + {% link_in_list /about-github-campus-program %} {% link_in_list /about-campus-experts %} {% link_in_list /about-campus-advisors %} {% topic_link_in_list /use-github-for-your-schoolwork %} diff --git a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index fd3a69a222..f2df61e155 100644 --- a/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/ko-KR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -59,11 +59,11 @@ For more information, see: ### Ineligible student status You're ineligible for a {% data variables.product.prodname_student_pack %} if: -- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. - You're pursuing a degree which will be terminated in the current academic session. - You're under 13 years old. -Your instructor may still apply for a {% data variables.product.prodname_education %} discount for classroom use. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools). +Your instructor may still apply for a {% data variables.product.prodname_education %} discount for classroom use. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). ### 더 읽을거리 diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 591c6ca063..f40f6056ae 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -17,7 +17,7 @@ When a student accepts a group assignment, the student can create a new team or {% 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 %}. For more information, see "[About teams](/github/setting-up-and-managing-organizations-and-teams/about-teams)." +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 %}. For more information, see "[About teams](/organizations/organizing-members-into-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)." 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 fd4a6e3a9e..cdf2c14220 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 @@ -20,7 +20,7 @@ redirect_from: After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}. -Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)" and "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom. @@ -34,7 +34,7 @@ When you first share the URL for an assignment with a student, the student must ### 빌드전 요구 사양 -You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." diff --git a/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index 1d77d71a7e..36eef2ec21 100644 --- a/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -26,7 +26,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} in y {% note %} -**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -47,7 +47,7 @@ You can disable all workflows for a repository or set a policy that configures w {% note %} -**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." +**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." {% endif %} diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index cfdbd3bb6d..708fb360ee 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -11,7 +11,11 @@ topics: - repositories --- -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)." +### About auto-merge + +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." + +### Managing auto-merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 29ac507f83..06f8f1b1c3 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 @@ -47,6 +47,9 @@ You can choose whether 6. Type a title and description for your release. ![Releases description](/assets/images/help/releases/releases_description.png) 7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) 8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) +{%- if currentVersion == "free-pro-team@latest" %} +1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} 9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**. ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png) You can also automatically create a release from the command line or in a script. For more information, see "[Releases](/v3/repos/releases/#create-a-release)." 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 0cd7dd5cda..c4891a4c07 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 @@ -106,4 +106,4 @@ Organization owners and repository administrators can only grant access to view ### 더 읽을거리 - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md index 3a2294c767..bcfc24dfda 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -16,7 +16,7 @@ For each repository that you administer on {% data variables.product.prodname_do This overview can help you audit access to your repository, onboard or off-board contractors or employees, and effectively respond to security incidents. -For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." ![Access management overview](/assets/images/help/repository/manage-access-overview.png) @@ -53,4 +53,4 @@ For more information about repository permission levels, see "[Permission levels ### 더 읽을거리 - "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" -- "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" +- "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)" diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index ca9fe332b6..16db66c1f1 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -13,7 +13,7 @@ topics: - repositories --- -An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)." +An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)." {% data reusables.organizations.internal-repos-enterprise %} 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 index 72604410c9..190210ca02 100644 --- 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 @@ -4,7 +4,7 @@ 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: '*' - enterprise-server: '>=3.1' + enterprise-server: '>=3.2' topics: - repositories --- @@ -13,7 +13,9 @@ topics: 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. +When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. + +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. ### Renaming a branch diff --git a/translations/ko-KR/content/github/administering-a-repository/renaming-a-repository.md b/translations/ko-KR/content/github/administering-a-repository/renaming-a-repository.md index ebd64f42cd..e5019d74eb 100644 --- a/translations/ko-KR/content/github/administering-a-repository/renaming-a-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/renaming-a-repository.md @@ -18,7 +18,7 @@ When you rename a repository, all existing information, with the exception of pr * Stars * Followers -For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git push` operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line: @@ -30,7 +30,7 @@ For more information, see "[Managing remote repositories](/github/getting-starte {% if currentVersion == "free-pro-team@latest" %} -If you plan to rename a repository that has a {% data variables.product.prodname_pages %} site, we recommend using a custom domain for your site. This ensures that the site's URL isn't impacted by renaming the repository. For more information, see "[About custom domains and {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/about-custom-domains-and-github-pages)." +If you plan to rename a repository that has a {% data variables.product.prodname_pages %} site, we recommend using a custom domain for your site. This ensures that the site's URL isn't impacted by renaming the repository. For more information, see "[About custom domains and {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)." {% endif %} 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 0c1d26047e..18bdbbd046 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 @@ -16,7 +16,7 @@ topics: ### About repository visibility changes -Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)." +Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." We recommend reviewing the following caveats before you change the visibility of a repository. diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/ko-KR/content/github/authenticating-to-github/about-authentication-to-github.md index c558d94fe2..1bc25fa979 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/ko-KR/content/github/authenticating-to-github/about-authentication-to-github.md @@ -55,3 +55,19 @@ You can access repositories on {% data variables.product.product_name %} from th * You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxys might refuse to allow SSH connections. Using SSH requires you to generate an SSH public/private keypair on your local machine and add the public key to your {% data variables.product.product_name %} account. Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." {% if currentVersion == "free-pro-team@latest" %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### {% data variables.product.company_short %}'s token formats + +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. + +| Token type | Prefix | More information | +|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Personal access token | `ghp_` | "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | + +{% endif %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index 2bf50f1728..a339c6ad67 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/ko-KR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -51,5 +51,5 @@ After an enterprise or organization owner enables or enforces SAML SSO for an or ### 더 읽을거리 -{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} {% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md index 0cd771d0b7..d5bdfd4db8 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/ko-KR/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -36,8 +36,15 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} 7. Click **Generate token**. ![Generate token button](/assets/images/help/settings/generate_token.png) -8. Click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again.{% 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 %} +8. Click +{% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again. + {% if currentVersion == "free-pro-team@latest" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) + {% endif %} {% warning %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/ko-KR/content/github/authenticating-to-github/creating-a-strong-password.md index fe6757c118..ddb66d598f 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/creating-a-strong-password.md +++ b/translations/ko-KR/content/github/authenticating-to-github/creating-a-strong-password.md @@ -20,7 +20,7 @@ To keep your account secure, we recommend you follow these best practices: - Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters. - Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your {% data variables.product.product_name %} account. - Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)." -- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/articles/collaborating-with-groups-in-organizations/)." +- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)." {% data reusables.repositories.blocked-passwords %} 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 72c00b4a21..704c4155ac 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 @@ -193,7 +193,7 @@ An overview of some of the most common actions that are recorded as events in th | `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | | `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | | `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)") | | `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | diff --git a/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-ssh-keys.md b/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-ssh-keys.md index 21e2fb328c..9237b6a71c 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-ssh-keys.md +++ b/translations/ko-KR/content/github/authenticating-to-github/reviewing-your-ssh-keys.md @@ -9,6 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - identity + - access management --- You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid. diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index 26238a70bf..a5422a76cb 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -18,7 +18,7 @@ You can create and participate in issues, pull requests, and team discussions, d Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see "[About issues](/articles/about-issues)." Pull requests allow you to comment directly on proposed changes. For more information, see "[About pull requests](/articles/about-pull-requests)" and "[Commenting on a pull request](/articles/commenting-on-a-pull-request)." -{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." ### Reacting to ideas in comments 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 dffadbe45e..b640d86507 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 @@ -15,7 +15,7 @@ topics: After a pull request is opened, anyone with *read* access can review and comment on the changes it proposes. You can also suggest specific changes to lines of code, which the author can apply directly from the pull request. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." -Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review)." {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. 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 %} +Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review)." {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} Reviews allow for discussion of proposed changes and help ensure that the changes meet the repository's contributing guidelines and other quality standards. You can define which individuals or teams own certain types or areas of code in a CODEOWNERS file. When a pull request modifies code that has a defined owner, that individual or team will automatically be requested as a reviewer. For more information, see "[About code owners](/articles/about-code-owners/)." diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index be5d8366dc..063b7b8993 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -14,7 +14,9 @@ topics: If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks. -Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)." +Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} + +After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback). diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index 50547aed46..e8bbd0d787 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -13,7 +13,7 @@ topics: Owners and collaborators on a repository owned by a user account can assign pull request reviews. Organization members with triage permissions to a repository can assign a pull request review. -Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. 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 %} +Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} {% note %} diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index 3631106cd1..9acbe72a84 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -79,5 +79,5 @@ If you change the visibility of an internal repository and then delete the repos - "[Setting repository visibility](/articles/setting-repository-visibility)" - "[About forks](/articles/about-forks)" - "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" -- "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" - "{% if currentVersion == "free-pro-team@latest" %}[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}" diff --git a/translations/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 0dd1bfc3e1..b344fbe14a 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 @@ -23,7 +23,7 @@ Code owners are automatically requested for review when someone opens a pull req 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 %} +{% 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](/organizations/organizing-members-into-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.22" %} If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md index e62878b22f..edc0500dfe 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -19,7 +19,7 @@ topics: {% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch. -Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist#troubleshooting) for help. +Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help. ### Markup languages diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index 1a74ecee14..dabd0a63d6 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -22,7 +22,7 @@ Private repositories are only accessible to you, people you explicitly share acc Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." {% endif %} -Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md index 69243b563c..d0990e60e8 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -23,13 +23,13 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of ``` 3. Mirror-push to the new repository. ```shell - $ cd old-repository.git + $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` 4. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects @@ -41,7 +41,7 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of ``` 3. Navigate to the repository you just cloned. ```shell - $ cd old-repository.git + $ cd old-repository ``` 4. Pull in the repository's {% data variables.large_files.product_name_long %} objects. ```shell @@ -58,7 +58,7 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of 7. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Mirroring a repository in another location @@ -72,7 +72,7 @@ If you want to mirror a repository in another location, including getting update ``` 3. Set the push location to your mirror. ```shell - $ cd repository-to-mirror.git + $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index 9a4250ad60..c7a0d6029d 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > provide shell access. ``` -If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "About OAuth App access restrictions." +If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "About OAuth App access restrictions." For more information, see [Adding a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account). diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md index 9a62636ef5..fb1cb2e462 100644 --- a/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -1,6 +1,6 @@ --- title: Using Codespaces in Visual Studio -intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vs %} by connecting with your account on {% data variables.product.product_name %}.' +intro: 'This preview has concluded and will no longer be accepting signups.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,50 +10,10 @@ topics: {% note %} -**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. During the beta period, {% data variables.product.prodname_dotcom %} does not make any guarantees about the availability of {% data variables.product.prodname_codespaces %}. [Sign up for the limited public beta](https://github.com/features/codespaces/signup-vs). For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." +**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. During the beta period, {% data variables.product.prodname_dotcom %} does not make any guarantees about the availability of {% data variables.product.prodname_codespaces %}. {% endnote %} ### About codespaces in {% data variables.product.prodname_vs %} -You can create a codespace in {% data variables.product.prodname_vs %} to develop applications in a Windows environment. When you use a codespace in {% data variables.product.prodname_vs %}, you can browse source code, build solutions, and commit changes to your repository. - -You must create a codespace in {% data variables.product.prodname_vs %} to use it with the application. Codespaces created outside of {% data variables.product.prodname_vs %} can not currently be used with {% data variables.product.prodname_vs %}. - -### 빌드전 요구 사양 - -Before you configure a codespace in {% data variables.product.prodname_vs %}, you must download the latest version of [{% data variables.product.prodname_vs %} Preview](https://aka.ms/vspreview). - -#### Enabling the connection between {% data variables.product.prodname_vs %} and {% data variables.product.prodname_github_codespaces %} - -Connecting to {% data variables.product.prodname_github_codespaces %} with the {% data variables.product.prodname_vs %} Preview is not enabled by default, so you will first need to enable the Preview Features option. - -1. In {% data variables.product.prodname_vs %} Preview, use the Tools drop-down menu, then click **Options**. -2. Under **Environment**, select **Preview Features** and check the **Connect to {% data variables.product.prodname_github_codespaces %}** preview feature. ![Check the Connect to {% data variables.product.prodname_github_codespaces %} preview feature](/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png) -3. You will need to restart {% data variables.product.prodname_vs %} for the feature to be available. - -### Creating a codespace in {% data variables.product.prodname_vs %} - -1. When you launch {% data variables.product.prodname_vs %}, the Start Window will show a **Connect to a codespace** button under "Get started". ![Visual Studio Start window with Connect to a codespace](/assets/images/help/codespaces/visual-studio-start-window.png) -2. Click **Connect to a codespace**. -3. Click **Sign in to {% data variables.product.prodname_dotcom %}** and follow the prompts, or click **Create one!** to create a new {% data variables.product.prodname_dotcom %} account and sign into the account. ![Visual Studio sign in to {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/visual-studio-sign-in-to-github.png) -4. Under "Codespace details", type the repository's URL you want {% data variables.product.prodname_github_codespaces %} to clone into your codespace. -5. Optionally, use the Instance type and Suspend after drop-down menus to configure more codespace details. ![Visual Studio codespace details](/assets/images/help/codespaces/visual-studio-codespace-details.png) -6. Click **Create and Connect**. {% data variables.product.prodname_github_codespaces %} will begin preparing the codespace and open {% data variables.product.prodname_vs %} after the codespace is ready. The codespace name will appear in the remote indicator in the menu. ![Visual Studio connected to eShopOnWeb repository codespace](/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png) - -### Opening a codespace in {% data variables.product.prodname_vs %} - -1. Use the File drop-down menu, and click **Connect to a Codespace**. ![Visual Studio File Connect to a codespace menu item](/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png) -2. Under "{% data variables.product.prodname_github_codespaces %}", click the codespace you want to connect to, then click **Connect**. ![Visual Studio displaying available codespaces and details](/assets/images/help/codespaces/visual-studio-connect-codespace.png) - -### Configuring a codespace for {% data variables.product.prodname_vs %} - -A codespace, created with {% data variables.product.prodname_vs %}, can be customized through a new tool called devinit, a command line tool included with {% data variables.product.prodname_vs %}. - -#### devinit - -[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) lets you install additional frameworks and tools into your Windows development codespaces, modify environment variables, and more. - -devinit supports a configuration file called [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). You can add this file to your project if you want to create a customized and repeatable development environment. When you use devinit with a [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) file, your codespaces will be automatically configured on creation. - -For more information about Windows codespace configuration and devinit, see [Customize a codespace](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces) in the {% data variables.product.prodname_vs %} documentation. For more information about devinit, see [Getting started with devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit). +The private preview for GitHub Codespaces in Visual Studio 2019 has concluded. For more information, see the [Visual Studio 2019 documentation](https://docs.microsoft.com/visualstudio/ide/codespaces/codespaces-overview?view=vs-2019). diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 9ef293c051..da6a2dbb13 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -37,7 +37,7 @@ You need write permission to view a summary of all the alerts for a repository o {% 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. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. ![Summary of alerts](/assets/images/enterprise/3.1/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) @@ -49,7 +49,7 @@ If you have write permission for a repository, you can view fixed alerts by view 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. -![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} @@ -102,11 +102,11 @@ To dismiss or delete alerts: 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. - ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![Filter alerts by rule](/assets/images/enterprise/3.1/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. - ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) + ![Open an alert from the summary list](/assets/images/enterprise/3.1/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) diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md index 292cc1fc30..47e24a706d 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -25,7 +25,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -65,7 +65,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endnote %} @@ -91,7 +91,7 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. 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 index d70919325c..99f643824c 100644 --- 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 @@ -38,7 +38,7 @@ 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)." {% endif %} -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)." +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](/organizations/keeping-your-organization-secure/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)." {% endif %} @@ -47,7 +47,7 @@ Once your system is set up, you can enable and disable these features at the org For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. -For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}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)."{% endif %} +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)."{% endif %} {% endif %} 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 2f9465ee55..3916e22772 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 @@ -92,7 +92,7 @@ In addition to the features available with {% data variables.product.prodname_te - {% data variables.contact.enterprise_support %}. For more information, see "{% data variables.product.prodname_ghe_cloud %} support" and "{% data variables.product.prodname_ghe_cloud %} Addendum." - 50,000 {% data variables.product.prodname_actions %} minutes - 50GB {% data variables.product.prodname_registry %} storage -- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime - The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "About enterprise accounts." 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 055d8c8e41..d8086b7096 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 @@ -52,6 +52,7 @@ Below is a list of some of the available keyboard shortcuts. | control z or command z | Undo | | control y or command y | Redo | | cmd + shift + p | Toggles between the **Edit file** and **Preview changes** tabs | +| control s or command s | Write a commit message | For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands). diff --git a/translations/ko-KR/content/github/index.md b/translations/ko-KR/content/github/index.md index a5c31865b4..d97b60cc5d 100644 --- a/translations/ko-KR/content/github/index.md +++ b/translations/ko-KR/content/github/index.md @@ -23,7 +23,7 @@ versions: {% link_in_list /managing-subscriptions-and-notifications-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 %} @@ -57,7 +57,6 @@ versions: {% 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 %} diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 3dd304fb03..6a632d3a71 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -42,9 +42,9 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." -For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} 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 19dfdd3799..8ecbd22dde 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 @@ -13,7 +13,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/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" %} 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 6801e578af..d7d7b97d94 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 @@ -66,7 +66,7 @@ Email notifications also allow flexibility with the types of notifications you r ### About participating and watching notifications -When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on 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" %} @@ -78,7 +78,7 @@ You can configure notifications for a repository on the repository page, or on y #### About custom notifications {% data reusables.notifications-v2.custom-notifications-beta %} You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository. -{% endif %} For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)." +{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. #### 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. @@ -248,16 +248,15 @@ You can also schedule when {% data variables.product.prodname_mobile %} will sen 1. In the bottom menu, tap **Profile**. 2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}. -3. To update your notification settings, tap **Notifications** and then use the toggles to enable or disable your preferred types of push notifications. -4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Receive Notifications**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications. +3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications. +4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications. ### Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %} You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository. -1. On {% data variables.product.prodname_mobile %}, navigate to main page of the repository. +1. On {% data variables.product.prodname_mobile %}, navigate to the main page of the repository. 2. Tap **Watch**. ![The watch button on {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-button.png) 3. To choose what activities you receive notifications for, tap your preferred watch settings. ![Watch settings dropdown menu in {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-settings.png) -{% data reusables.notifications-v2.custom-notifications-beta %} {% endif %} diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index c4a97c716f..a328ba0cd3 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -38,7 +38,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. +**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." {% endtip %} {% endif %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md index 61f6cf19fc..4175c9ee0f 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md @@ -19,14 +19,14 @@ When you downgrade or cancel a sponsorship, the change will become effective on {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Canceling a sponsorship {% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} +{% data reusables.user_settings.billing_plans %} {% data reusables.sponsors.billing-switcher %} -{% data reusables.user_settings.subscriptions-tab %} 3. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored open source contributor, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your sponsored amount, then click **Cancel sponsorship**. ![Cancel sponsorship button](/assets/images/help/billing/edit-sponsor-billing.png) 4. Review the information about canceling your sponsorship, then click **OK**. ![Cancellation confirmation box](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md index 5eac25c5c7..40e537ab5b 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md @@ -14,6 +14,8 @@ topics: {% data variables.product.product_name %} can't issue a refund if you pay for an account before applying a coupon. We also can't transfer a redeemed coupon or give you a new coupon if you apply it to the wrong account. Confirm that you're applying the coupon to the correct account before you redeem a coupon. +{% data reusables.dotcom_billing.coupon-expires %} + You cannot apply coupons to paid plans for {% data variables.product.prodname_marketplace %} apps. ### Redeeming a coupon for your personal account diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md index 755566843f..76d8aaf35c 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md @@ -15,6 +15,8 @@ topics: If you're paying for your {% data variables.product.product_name %} subscription with a coupon, and you aren't using your payment method for any [other paid features or products](/articles/about-billing-on-github) on {% data variables.product.product_name %}, you can remove your credit card or PayPal information. +{% data reusables.dotcom_billing.coupon-expires %} + {% tip %} **Tip:** If you [downgrade your account to a free product](/articles/downgrading-your-github-subscription) and you don't have subscriptions for any other paid features or products, we'll automatically remove your payment information. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md index 273ffaec66..ef933c5fa9 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md @@ -19,5 +19,6 @@ When you upgrade your sponsorship tier, the change will become effective immedia {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md index 2aa264faf7..c0a884a4df 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -59,7 +59,7 @@ You can upgrade your organization from {% data variables.product.prodname_free_t #### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %} -If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/articles/managing-saml-single-sign-on-for-your-organization)." +If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)." If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/articles/about-enterprise-accounts)." diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md index 0aa338416e..2a55ae7412 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md @@ -20,5 +20,5 @@ You can check how many seats your license includes and how many of them are curr The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png) 5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 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)." +6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." 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 index ef8a58ddd1..3065baab02 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### 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.dotcom-saml-explanation %} For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} 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 388a473cdb..2c33330c4e 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 @@ -49,7 +49,7 @@ Enterprise owners can restrict access to assets owned by organizations in an ent {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." #### Adding an allowed IP address diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md index 160f27ffb3..00e1b02611 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md @@ -15,7 +15,7 @@ topics: ### Enforcing a policy for team discussions -Across all organizations owned by your enterprise account, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." +Across all organizations owned by your enterprise account, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 38224795d1..677fc248a1 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 @@ -39,7 +39,7 @@ Organization owners can invite new members to an organization by email address. While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. -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)." +For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/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 index dd6b6dd258..eca5900c21 100644 --- 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 @@ -19,7 +19,7 @@ If you use Azure AD as your IdP, you can enable team synchronization for your en {% 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 can also configure and manage team synchronization for an individual organization. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." ### 빌드전 요구 사양 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md index 94485eb3d9..ffac1820bd 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -11,7 +11,7 @@ topics: ### About email restrictions for your enterprise account -When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md index 12390da38b..40acd8c833 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -14,7 +14,7 @@ topics: ### 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. For more information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." +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. For more information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %} @@ -22,7 +22,7 @@ Organization owners will be able to verify the identity of organization members After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account to approved domains](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)." -Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." ### Verifying your enterprise account's domain 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 05a9128770..21b50cf6c9 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 @@ -53,4 +53,4 @@ When you enable SAML single sign-on for your enterprise account, each enterprise ### 더 읽을거리 -- "[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 managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md index c99afcc9d2..8eb91f55af 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -14,7 +14,7 @@ topics: You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories to the top of the page. -{% 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 %}. For more information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." +{% 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 %}. For more information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." ![Sample verified organization profile page](/assets/images/help/profile/org_profile_verified.png) {% else %} @@ -23,4 +23,4 @@ You can optionally choose to add a description, location, website, and email add ### 더 읽을거리 -- "[About organizations](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" +- "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" 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 d494ef3352..0814709774 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 @@ -25,7 +25,7 @@ Commits will appear on your contributions graph if they meet **all** of the foll - In the repository's default branch - In the `gh-pages` branch (for repositories with project sites) -For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." In addition, **at least one** of the following must be true: - You are a collaborator on the repository or are a member of the organization that owns the repository. @@ -66,7 +66,7 @@ Generic email addresses--such as `jane@computer.local`--cannot be added to {% da #### Commit was not made in the default or `gh-pages` branch -Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following: - [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md index acc130f1bb..039d964d60 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -52,7 +52,7 @@ You can also convert your personal user account directly into an organization. C {% tip %} -**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." +**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)." {% endtip %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index 652003998d..894fa26bcf 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -56,4 +56,4 @@ Repositories owned by an organization can grant more granular access. For more i - "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)" - "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)" - "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)" -- "[Organizing members into teams](/articles/organizing-members-into-teams)" +- "[Organizing members into teams](/organizations/organizing-members-into-teams)" diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md index 59a4924914..7a29d81d68 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -25,4 +25,4 @@ When you create a new repository on {% data variables.product.product_location % ### 더 읽을거리 -- "[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)" +- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md index 6618a72086..f983321c0e 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -13,7 +13,7 @@ Scheduled reminders are used to make sure that users focus on the most important For certain events, you can also enable real-time alerts for scheduled reminders. Real-time alerts get sent to your Slack channel as soon as an important event, such as when you are assigned a review, takes place. -You can set scheduled reminders for personal or team-level review requests for pull requests in organizations you are a member of. Before you can create a scheduled reminder for yourself, an organization owner must authorize your Slack workspace. For more information, see "[Managing scheduled reminders for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)." +You can set scheduled reminders for personal or team-level review requests for pull requests in organizations you are a member of. Before you can create a scheduled reminder for yourself, an organization owner must authorize your Slack workspace. For more information, see "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)." {% data reusables.reminders.scheduled-reminders-limitations %} @@ -50,5 +50,5 @@ You can set scheduled reminders for personal or team-level review requests for p ### 더 읽을거리 -- "[Managing scheduled reminders for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" -- "[Managing scheduled reminders for your team](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" +- "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- "[Managing scheduled reminders for your team](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md index a0f521782f..1ab11a91cc 100644 --- a/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/ko-KR/content/github/site-policy/github-corporate-terms-of-service.md @@ -125,7 +125,7 @@ Customer’s use of the Products must not violate any applicable laws, including Customer’s use of the Service must comply with [GitHub's Acceptable Use Policies](/articles/github-acceptable-use-policies) and [GitHub’s Community Guidelines](/articles/github-community-guidelines). Customer must not use the Service in any jurisdiction for unlawful, obscene, offensive or fraudulent Content or activity, such as advocating or causing harm, interfering with or violating the integrity or security of a network or system, evading filters, sending unsolicited, abusive, or deceptive messages, viruses or harmful code, or violating third party rights. #### 3. 개인 정보 보호 -The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Addendum](/github/site-policy/github-data-protection-addendum) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the GitHub Privacy Statement, particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. +The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Agreement](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the GitHub Privacy Statement, particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. ### D. Content Responsibility; Ownership; License Rights diff --git a/translations/ko-KR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/ko-KR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md new file mode 100644 index 0000000000..cf734eb6be --- /dev/null +++ b/translations/ko-KR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md @@ -0,0 +1,348 @@ +--- +title: GitHub Data Protection Agreement (Non-Enterprise Customers) +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum +versions: + free-pro-team: '*' +--- + +_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._ + +## INTRODUCTION + +The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products. + +In the event of any conflict or inconsistency between the DPA and any other terms in Customer’s agreements with GitHub, the DPA shall prevail. The provisions of the DPA supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Customer Personal Data as defined herein. For clarity, consistent with Clause 10 of the Standard Contractual Clauses in Attachment 1, the Standard Contractual Clauses prevail over any other terms in the DPA. + + +## GITHUB DATA PROTECTION + +### 1. 정의. + +1.1 The "**Applicable Data Protection Laws**" means certain laws, regulations, regulatory frameworks, or other legislations relating to the processing and use of Customer Personal Data, as applicable to Customer's use of GitHub and the GitHub Service, including: + + a. The EU General Data Protection Regulation 2016/679 (**"GDPR"**), along with any implementing or corresponding equivalent national laws or regulations, once in effect and applicable; and + + b. The California Consumer Privacy Act of 2018, Cal. Civ. Code §§1798.100 et seq. (**"CCPA"**); and + + c. The UK Data Protection Act 2018 and implementation of GDPR contained therein. + +1.2 "**Controller**," "**Data Subject**," "**Member State**," "**Personal Data**," "**Personal Data Breach**," "**Processing**," "**Processor**," and "**Supervisory Authority**" have the meanings given to them in the Applicable Data Protection Laws. In the event of a conflict, the meanings given in the GDPR will supersede. + +1.3 "**Customer Personal Data**" means any Personal Data for which Customer is a Controller, whether supplied by Customer for processing by GitHub or generated by GitHub in the course of performing its obligations under the Agreement. It includes data such as billing information, IP addresses, corporate email addresses, and any other Personal Data for which Customer is a Controller. + +1.4 "**Customer Repository Data**" means any data or information that is uploaded or created by Customer into any of its Private Repositories. + +1.5 A "**Data Breach**" means a Personal Data Breach or any other confirmed or reasonably suspected breach of Customer's Protected Data. + +1.6 "**End User**" means an individual Data Subject who controls a GitHub account and has agreed to the GitHub Terms of Service, and whose Personal Data is being transferred, stored, or processed by GitHub. For example, each Customer employee or contractor who has a GitHub account is also a GitHub End User. + +1.7 "**Permitted Purposes**" for data processing are those limited and specific purposes of providing the Service as set forth in the Agreement, the GitHub Privacy Statement, and this Exhibit A, or the purposes for which a Data Subject has authorized the use of Customer Personal Data. + +1.8 "**Protected Data**" includes any Customer Personal Data and any Customer Repository Data processed by GitHub on behalf of Customer under the Agreement. + +1.9 "**Sensitive Data**" means any Customer Personal Data revealing racial or ethnic origin; political opinions, religious or philosophical beliefs or trade union membership; processing of genetic data or biometric data for the purposes of uniquely identifying a natural person; data concerning health, a natural person's sex life or sexual orientation; and data relating to offences, criminal convictions, or security measures. + +### 2. Status and Compliance. + +#### 2.1 Data Processing. +GitHub acts as a Processor in regard to any Customer Personal Data it receives in connection with the Agreement, and GitHub will process Customer Personal Data only for Permitted Purposes in accordance with Customer's instructions as represented by the Agreement and other written communications. In the event that GitHub is unable to comply with Customer's instructions, such as due to conflicts with the Applicable Data Protection Laws, or where processing is required by the Applicable Data Protection Laws or other legal requirements, GitHub will notify Customer to the extent permissible. GitHub processes all Customer Personal Data in the United States or in the European Union; however, GitHub's subprocessors may process data outside of the United States or the European Union. Additionally, GitHub acts as a Processor for any Customer Repository Data. + +#### 2.2 Data Controllers. +GitHub receives Customer Personal Data both from Customer and directly from Data Subjects who create End User accounts. Customer is a Controller only for the Customer Personal Data it transfers directly to GitHub. + +#### 2.3 GitHub Compliance; Data Transfers. +GitHub will comply with Applicable Data Protection Laws in relation to the processing of Customer Personal Data. + +All transfers of Customer Personal Data out of the European Union, European Economic Area, United Kingdom, and Switzerland to provide the Service shall be governed by the Standard Contractual Clauses in Attachment 1 (Standard Contractual Clauses). GitHub will abide by the requirements of European Economic Area and Swiss data protection law regarding the collection, use, transfer, retention, and other processing of Customer Personal Data from the European Economic Area, United Kingdom, and Switzerland. All transfers of Customer Personal Data to a third country or an international organization will be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +In addition, GitHub is certified to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on them as a legal basis for transfers of Personal Data. GitHub agrees to notify Customer if it makes a determination that it can no longer meet its obligation to provide the same level of protection as is required by the Privacy Shield principles. + + +### 3. Data Protection. + +#### 3.1 Purpose Limitation. +GitHub will process and communicate the Protected Data only for Permitted Purposes, unless the Parties agree in writing to an expanded purpose. + +#### 3.2 Data Quality and Proportionality. +GitHub will keep the Customer Personal Data accurate and up to date, or enable Customer to do so. GitHub will take commercially reasonable steps to ensure that any Protected Data it collects on Customer's behalf is adequate, relevant, and not excessive in relation to the purposes for which it is transferred and processed. In no event will GitHub intentionally collect Sensitive Data on Customer's behalf. Customer agrees that the GitHub Service is not intended for the storage of Sensitive Data; if Customer chooses to upload Sensitive Data to the Service, Customer must comply with Article 9 of the GDPR, or equivalent provisions in the Applicable Data Protection Laws. + +#### 3.3 Data Retention and Deletion. +Upon Customer's reasonable request, unless prohibited by law, GitHub will return, destroy, or deidentify all Customer Personal Data and related data at all locations where it is stored after it is no longer needed for the Permitted Purposes within thirty days of request. GitHub may retain Customer Personal Data and related data to the extent required by the Applicable Data Protection Laws, and only to the extent and for such period as required by the Applicable Data Protection Laws, provided that GitHub will ensure that Customer Personal Data is processed only as necessary for the purpose specified in the Applicable Data Protection Laws and no other purpose, and Customer Personal Data remains protected by the Applicable Data Protection Laws. + +#### 3.4 Data Processing. +GitHub provides the following information, required by Article 28(3) of the GDPR, regarding its processing of Customer's Protected Data: + +a. *The subject matter and duration of the processing* of Customer Personal Data are set out in the Agreement and this Addendum. + +b. *The nature and purpose of the processing* of Customer Personal Data is described in Section 3.1 of this Addendum. + +c. *The types of Customer Personal Data to be processed* are described in the GitHub Privacy Statement, and include Customer Personal Data such as user names, passwords, email addresses, and IP addresses. GitHub also processes information necessary for billing Customer's account, but does not process or store credit card information. Customer may choose to supply GitHub with additional Customer Personal Data, such as in Customer's profile settings or by uploading Customer Personal Data to its GitHub repositories. + +d. *The categories of Data Subject to whom the Customer Personal Data relates* are the Customer itself and its End Users. + +e. *The obligations and rights of Customer* are set out in the Agreement and this Addendum. + +### 4. Security and Audit Obligations. + +#### 4.1 Technical and Organizational Security Measures. +Taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, GitHub will implement appropriate technical and organizational measures to ensure a level of security appropriate to the risks, such as against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure or access, presented by processing the Protected Data. GitHub will regularly monitor compliance with these measures and will continue to take appropriate safeguards throughout the duration of the Agreement. + +#### 4.2 Incident Response and Breach Notification. +GitHub will comply with Applicable Data Protection Laws. + +#### 4.3 GitHub Personnel. +GitHub represents and warrants that it will take reasonable steps to ensure that all GitHub personnel processing Protected Data have agreed to keep the Protected Data confidential and have received adequate training on compliance with this Addendum and the Applicable Data Protection Laws. + +#### 4.4 Records. +GitHub will maintain complete, accurate, and up to date written records of all categories of processing activities carried out on behalf of Customer containing the information required under the Applicable Data Protection Laws. To the extent that assistance does not risk the security of GitHub or the privacy rights of individual Data Subjects, GitHub will make these records available to Customer on request as reasonably required, such as to help Customer demonstrate its compliance under the Applicable Data Protection Laws. + +#### 4.5 Assistance. +GitHub will provide reasonable assistance to Customer with concerns such as data privacy impact assessments, Data Subject rights requests, consultations with Supervisory Authorities, and other similar matters, in each case solely in relation to the processing of Customer Personal Data and taking into account the nature of processing. + +### 5. Use and Disclosure of Protected Data. + +#### 5.1 No Use in Marketing. +GitHub will not use the Protected Data for the purposes of advertising third-party content, and will not sell the Protected Data to any third party except as part of a merger or acquisition. + +#### 5.2 GitHub Privacy Statement. +The GitHub Privacy Statement, publicly available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), provides detailed notice of GitHub's privacy and data use practices, including its use of cookies, its dispute resolution process, and further details about GitHub's GDPR compliance. + +### 6. Subprocessing and Onward Transfer. + +#### 6.1 Protection of Data. +GitHub is liable for onward transfers of Protected Data to its subprocessors, such as its third-party payment processor. In the event that GitHub does transfer the Protected Data to a third-party subprocessor, or GitHub installs, uses, or enables a third party or third-party services to process the Protected Data on GitHub's behalf, GitHub will ensure that the third-party subprocessor is bound by written agreement that requires them to provide at least the same level of confidentiality, security, and privacy protection as is required of GitHub by this DPA and the Applicable Data Protection Laws. + +#### 6.2 Acceptance of GitHub Subprocessors. +Customer authorizes GitHub to appoint (and permit each subprocessor appointed in accordance with this Section 6 to appoint) subprocessors in accordance with Section 6 and any other restrictions in the Agreement. GitHub may continue to use those subprocessors currently engaged as of the Effective Date of this Addendum. + +#### 6.3 General Consent for Onward Subprocessing. +Customer provides a general consent for GitHub to engage onward subprocessors, conditional on GitHub's compliance with the following requirements: + +a. Any onward subprocessor must agree in writing to only process data in a country that the European Commission has declared to have an "adequate" level of protection; or to only process data on terms equivalent to the Standard Contractual Clauses, or pursuant to a Binding Corporate Rules approval granted by competent European data protection authorities, or pursuant to compliant and valid EU-US Privacy Shield and Swiss-U.S. Privacy Shield certifications; and + +b. GitHub will restrict the onward subprocessor's access to Customer Personal Data only to what is strictly necessary to perform its services, and GitHub will prohibit the subprocessor from processing the Customer Personal Data for any other purpose. + +#### 6.4 Disclosure of Subprocessor Agreements. +GitHub maintains a list of onward subprocessors it has engaged to process Customer Personal Data at [https://docs.github.com/articles/github-subprocessors-and-cookies](/articles/github-subprocessors-and-cookies), including the categories of Customer Personal Data processed, a description of the type of processing the subprocessor performs, and the location of its processing. GitHub will, upon Customer's written request, provide Customer with this list of subprocessors and the terms under which they process the Customer Personal Data. Pursuant to subprocessor confidentiality restrictions, GitHub may remove any confidential or commercially sensitive information before providing the list and the terms to Customer. In the event that GitHub cannot disclose confidential or sensitive information to Customer, the Parties agree that GitHub will provide all information it reasonably can in connection with its subprocessing agreements. + +#### 6.5 Objection to Subprocessors. +GitHub will provide thirty (30) days' prior written notice of the addition or removal of any subprocessor, including the categories listed in Section 6.4, by announcing changes on its site. If Customer has a reasonable objection to GitHub's engagement of a new subprocessor, Customer must notify GitHub promptly in writing. Where possible, GitHub will use commercially reasonable efforts to provide an alternative solution to the affected Service to avoid processing of data by the objectionable subprocessor. In the event that GitHub is unable to provide an alternative solution and the Parties cannot resolve the conflict within ninety days, Customer may terminate the Agreement. + +### 7. Termination. + +#### 7.1 Suspension. +In the event that GitHub is in breach of its obligations to maintain an adequate level of security or privacy protection, Customer may temporarily suspend the transfer of all Customer Personal Data or prohibit collection and processing of Customer Personal Data on Customer's behalf until the breach is repaired or the Agreement is terminated. + +#### 7.2 Termination with Cause. +In addition to any termination rights Customer has under the Agreement, Customer may terminate the Agreement without prejudice to any other claims at law or in equity in the event that: + +a. GitHub notifies Customer that it can no longer meet its privacy obligations; + +b. the transfer, collection, or processing of all Customer Personal Data has been temporarily suspended for longer than one month pursuant to Section 7.1; + +c. GitHub is in substantial or persistent breach of any warranties or representations under this Addendum; + +d. GitHub is no longer carrying on business, is dissolved, enters receivership, or a winding up order is made on behalf of GitHub; or + +e. Customer objects to a subprocessor pursuant to Section 6.5, and GitHub has not been able to provide an alternative solution within ninety days. + +#### 7.3 Breach. +Failure to comply with the material provisions of this Addendum is considered a material breach under the Agreement. + +#### 7.4 Failure to perform. +In the event that changes in law or regulation render performance of this Addendum impossible or commercially unreasonable, the Parties may renegotiate the Addendum in good faith. If renegotiation would not cure the impossibility, or if the Parties cannot reach an agreement, the Parties may terminate the Agreement after thirty days. + +#### 7.5 Notification. +In the event that GitHub determines that it can no longer meet its privacy obligations under this Addendum, GitHub will notify Customer in writing immediately. + +#### 7.6 Modifications. +GitHub may modify this Addendum from time to time as required by the Applicable Data Protection Laws, with thirty days' notice to Customer. + +#### 7.7 Termination Requirements. +Upon Termination, GitHub must: + +a. take reasonable and appropriate steps to stop processing the Customer Personal Data; + +b. within ninety days of termination, delete or deidentify any Customer Personal Data GitHub stores on Customer's behalf pursuant to Section 3.3; and + +c. provide Customer with reasonable assurance that GitHub has complied with its obligations in Section 7.7. + +### 8. Liability for Data Processing. + +#### 8.1 Limitations. +Except as limited by the Applicable Data Protection Laws, any claims brought under this Addendum will be subject to the terms of the Agreement regarding Limitations of Liability. + +## Attachment 1 – The Standard Contractual Clauses (Processors) +Execution of the applicable agreement by Customer includes execution of this Attachment 1 to the GitHub Data Protection Addendum, which is countersigned by GitHub, Inc. + +In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. + +For the purposes of Article 46(2) of the General Data Protection Regulation (EU 2016/679) for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +#### Clause 1: Definitions +(a) 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in the General Data Protection Regulation (EU 2016/679) on the protection of individuals with regard to the processing of personal data and on the free movement of such data; + +(b) 'the data exporter' means the controller who transfers the personal data; + +(c) 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 45(2) of the General Data Protection Regulation (EU 2016/679); + +(d) 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract; + +(e) 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established; + +(f) 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing. + +#### Clause 2: Details of the transfer +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +#### Clause 3: Third-party beneficiary clause +1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary. + +2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. + +3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law. + +#### Clause 4: Obligations of the data exporter +The data exporter agrees and warrants: + +(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State; + +(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses; + +(c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below; + +(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation; + +(e) that it will ensure compliance with the security measures; + +(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of the General Data Protection Regulation (EU 2016/679); + +(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension; + +(h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information; + +(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and + +(j) that it will ensure compliance with Clause 4(a) to (i). + +#### Clause 5: Obligations of the data importer +The data importer agrees and warrants: + +(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(c) that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred; + +(d) that it will promptly notify the data exporter about: + +(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation, + +(ii) any accidental or unauthorised access, and + +(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so; + +(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + +(f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; + +(g) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter; + +(h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent; + +(i) that the processing services by the subprocessor will be carried out in accordance with Clause 11; and + +(j) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter. + +#### Clause 6: Liability +1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered. + +2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity. The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities. + +3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +#### Clause 7: Mediation and jurisdiction +1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: + +(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; + +(b) to refer the dispute to the courts in the Member State in which the data exporter is established. + +2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. + +#### Clause 8: Cooperation with supervisory authorities +1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law. + +2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law. + +3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5(b). + +#### Clause 9: Governing Law. +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +#### Clause 10: Variation of the contract +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +#### Clause 11: Subprocessing +1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement. + +2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established. + +4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority. + +#### Clause 12: Obligation after the termination of personal data processing services +1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore. + +2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1. + +### Appendix 1 to the Standard Contractual Clauses +Data exporter: Customer is the data exporter. + +**Data importer:** The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects:** Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal information to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following types of data subjects in the Customer Personal Data: + +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Dependents of the above; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users (e.g., customers, clients, patients, visitors, etc.) and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter; +- Stakeholders or individuals who passively interact with data exporter (e.g., because they are the subject of an investigation, research or mentioned in documents or correspondence from or to the data exporter); or +- Professionals with professional privilege (e.g., doctors, lawyers, notaries, religious workers, etc.). + +**Categories of data:** The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Service. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following categories in the Customer Personal Data: +- Authentication data (for example, username, email, password); +- Contact information (for example, email); +- Unique identification numbers and signatures (IP addresses, unique identifier in tracking cookies or similar technology). +- Other unique identifying information. Data subjects may include more data such as real names, avatar images, and other personal information; + +**Special categories of data (if appropriate):** The data importer does not intentionally collect or process any special categories of data in carrying out its services to the data exporter. + +However, because the data importer provides storage services and does not control the categories of data it stores, the data exporter may choose to transfer special categories of data. Consequently, the data exporter is solely responsible for ensuring that it complies with all obligations imposed by applicable laws and regulations relating to the collection and processing of any special categories of data, including obtaining the explicit consent of the data subject prior to processing sensitive personal data. + +**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontractors: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain Customer Personal Data only to deliver the services the data importer has retained them to provide, and they are prohibited from using Customer Personal Data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +**1. Personnel.** Data importer’s personnel will not process Customer Personal Data without authorization. Personnel are obligated to maintain the confidentiality of any Customer Personal Data and this obligation continues even after their engagement ends. + +**2. Data Privacy Contact.** The data privacy officer of the data importer can be reached at the following address: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA + +**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction. + +Signature of GitHub, Inc. appears below. + +Signing the Standard Contractual Clauses, Appendix 1 and Appendix 2 on behalf of the data importer + +![Screen Shot 2020-07-20 at 2 20 29 PM](/assets/images/help/site-policy/docusign-signature.png) + +Lynn Hashimoto, Head of Product & Regulatory Legal + +GitHub, Inc. diff --git a/translations/ko-KR/content/github/site-policy/github-privacy-statement.md b/translations/ko-KR/content/github/site-policy/github-privacy-statement.md index 2d3356e70b..95bd3e8754 100644 --- a/translations/ko-KR/content/github/site-policy/github-privacy-statement.md +++ b/translations/ko-KR/content/github/site-policy/github-privacy-statement.md @@ -192,7 +192,7 @@ Similarly, projects on GitHub may include publicly available User Personal Infor #### Organizations -You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s). +You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/organizations/managing-organization-settings/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s). Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization. @@ -321,7 +321,7 @@ In the unlikely event that a dispute arises between you and GitHub regarding our ### Changes to our Privacy Statement -Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For 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. +Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### 라이선스 diff --git a/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ko-KR/content/github/site-policy/github-subprocessors-and-cookies.md index 7ba4d0f7ad..dd8482b537 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 @@ -13,7 +13,7 @@ topics: - legal --- -Effective date: **January 29, 2021** +Effective date: **April 2, 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). @@ -33,7 +33,6 @@ When we share your information with third party subprocessors, such as our vendo | 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 | -| Monday.com | Team collaboration and project management platform | United States | Israel | | Nexmo | SMS notification provider | United States | United States | | Salesforce.com | Customer relations management | United States | United States | | Sentry.io | Application monitoring provider | 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 9d4e8b3ef8..72c9182c43 100644 --- a/translations/ko-KR/content/github/site-policy/index.md +++ b/translations/ko-KR/content/github/site-policy/index.md @@ -16,6 +16,7 @@ topics: {% 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-agreement-non-enterprise-customers %} {% link_in_list /global-privacy-practices %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} {% link_in_list /github-sponsors-additional-terms %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md index a9d5f1cb9b..81b9554ba6 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -24,7 +24,9 @@ You can set a goal for your sponsorships. For more information, see "[Managing y ### Sponsorship tiers -{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)." +{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)." + +It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. ### Sponsorship payouts @@ -34,5 +36,9 @@ You can set a goal for your sponsorships. For more information, see "[Managing y For more information, see "[Managing your payouts from {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)." +### Sharing feedback about {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.feedback %} + ### 더 읽을거리 - "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md index a279ee1849..35dfbb8cc1 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -37,7 +37,7 @@ To be eligible for the {% data variables.product.prodname_matching_fund %}, you ### Sharing feedback about {% data variables.product.prodname_sponsors %} -This is just the beginning — we'd love your input to make sure {% data variables.product.prodname_sponsors %} serves your needs into the future. Please send us your feedback or suggestions by contacting [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). +{% data reusables.sponsors.feedback %} ### 더 읽을거리 - "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md index 5b8efe069c..de523d754e 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -15,6 +15,8 @@ Your sponsors can choose whether they receive email updates about your work. For For sponsored developer accounts, the update will come from your user account's primary email address. If you've enabled email address privacy on your user account, the update will come from `noreply@github.com` instead. For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +You can also contact any one-time sponsors who contributed within the last 30 days and enabled updates. + ### Contacting your sponsors {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md index 6623eceb6b..39d60b8feb 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md @@ -25,7 +25,7 @@ topics: {% 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 /managing-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 %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md index 1d9a6e18e3..9991858a58 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -13,6 +13,12 @@ You can set a funding goal for your sponsored account and share the goal with yo Your goal can set a target for the number of sponsors you want to have or the amount of money you want to earn each month. You can only set one goal up at a time. After you reach a goal, you can set another goal. +{% note %} + +**Note:** Goals are intended to help people track momentum so only monthly sponsors contribute toward your goal. + +{% endnote %} + ### Setting a goal {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md new file mode 100644 index 0000000000..efb3ada4b5 --- /dev/null +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md @@ -0,0 +1,45 @@ +--- +title: Managing your sponsorship tiers +intro: 'You can add a new sponsorship tier, or edit or retire an existing tier.' +redirect_from: + - /articles/changing-your-sponsorship-tiers + - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +topics: + - sponsors +--- + +### About sponsorship tiers + +{% data reusables.sponsors.tier-details %} + +{% data reusables.sponsors.maximum-tier %} + +### Adding a 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 %} + +### Editing or retiring a tier + +{% 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 %} + +### Enabling tiers with custom amounts + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.enable-custom-amounts %} + +### Disabling tiers with custom amounts + +You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired. diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 3bd53a97f5..cc938afe38 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -48,6 +48,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Submitting your bank information diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index bfa5351d6f..cd2178f54c 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -48,6 +48,7 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Submitting your bank information diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 5367e8b27e..b2d7b7755b 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -1,6 +1,6 @@ --- title: Sponsoring an open source contributor -intro: 'You can make a monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' +intro: 'You can make a one-time or monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' redirect_from: - /articles/sponsoring-a-developer - /articles/sponsoring-an-open-source-contributor @@ -24,11 +24,11 @@ You can sponsor an account on behalf of your user account to invest in projects - 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 pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +You use your normal payment method to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% 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 %} +When you sponsor an account the change is effective immediately, unless you are sponsoring on behalf of an organization that pays by invoice. {% data reusables.sponsors.prorated-sponsorship %} Your sponsorship is included in the next scheduled payment to the sponsored account. {% data reusables.sponsors.manage-updates-for-orgs %} @@ -53,6 +53,7 @@ Before you can sponsor an account, you must have a verified email address. For m - To sponsor a developer, under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png) - To sponsor an organization, to the right of the organization's name, click **Sponsor**. ![Sponsor button](/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) +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} diff --git a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index c94acc9ab9..3dcbc26360 100644 --- a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -89,6 +89,6 @@ The recommended formats explicitly define which versions are used for all direct - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index a7dd28bba0..fa569244f8 100644 --- a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -68,7 +68,7 @@ For public repositories, the dependents view shows how the repository is used by Repository administrators can enable or disable the dependency graph for private repositories. -You can also enable or disable the dependency graph 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)." +You can also enable or disable the dependency graph 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](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -109,7 +109,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ### 더 읽을거리 - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)" {% endif %} diff --git a/translations/ko-KR/content/github/working-with-github-support/submitting-a-ticket.md b/translations/ko-KR/content/github/working-with-github-support/submitting-a-ticket.md index c0a4fc60f7..584a649b34 100644 --- a/translations/ko-KR/content/github/working-with-github-support/submitting-a-ticket.md +++ b/translations/ko-KR/content/github/working-with-github-support/submitting-a-ticket.md @@ -11,7 +11,7 @@ topics: If your account uses a paid {% data variables.product.prodname_dotcom %} product, you can directly contact {% data variables.contact.github_support %}. If your account uses {% data variables.product.prodname_free_user %} for user accounts and organizations, you can contact {% data variables.contact.contact_support %} to report account, security, and abuse issues. For more information, see "[About GitHub Support](/github/working-with-github-support/about-github-support)." -If you use {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %}, or the {% data variables.product.premium_support_plan %} you must submit tickets using the {% data variables.contact.enterprise_portal %}. +If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)." ### Submitting a ticket using the {% data variables.contact.support_portal %} 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 eaa67a64c2..a33cd2a88a 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 @@ -33,7 +33,7 @@ If your site administrator has disabled private mode, you can also use anonymous 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. +- You subscribe to a gist, by clicking **Subscribe** at the top of any gist. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} @@ -55,13 +55,15 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, ### Creating a gist -You can also drag and drop a text file from your desktop directly into the gist editor. +Follow the steps below to create a gist. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% note %} 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. +Alternatively, you can drag and drop a text file from your desktop directly into the editor. + {% endnote %} {% endif %} diff --git a/translations/ko-KR/content/index.md b/translations/ko-KR/content/index.md index 8a144eecbf..61bbd813cd 100644 --- a/translations/ko-KR/content/index.md +++ b/translations/ko-KR/content/index.md @@ -13,5 +13,43 @@ featuredLinks: - /github/getting-started-with-github/managing-remote-repositories - /github/working-with-github-pages versions: '*' +children: + - github + - admin + - organizations + - code-security + - actions + - 패키지 + - developers + - rest + - graphql + - insights + - discussions + - 커뮤니티 + - pages + - education + - desktop + - early-access +externalProducts: + cli: + id: cli + name: GitHub CLI + href: 'https://cli.github.com/manual' + external: true + atom: + id: atom + name: Atom + href: 'https://atom.io/docs' + external: true + electron: + id: electron + name: Electron + href: 'https://electronjs.org/docs' + external: true + codeql: + id: codeql + name: 'CodeQL' + href: 'https://codeql.github.com/docs' + external: true --- diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md new file mode 100644 index 0000000000..f2dda89e95 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -0,0 +1,33 @@ +--- +title: About organizations +intro: Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. +redirect_from: + - /articles/about-organizations + - /github/setting-up-and-managing-organizations-and-teams/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} +### Organizations and enterprise accounts + +Enterprise accounts allow owners to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations. + +For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account. + +{% data reusables.gated-features.enterprise-accounts %} + +{% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." + +### Terms of service and data protection for organizations + +An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)." + +{% endif %} diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md new file mode 100644 index 0000000000..6b42ae2b62 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -0,0 +1,49 @@ +--- +title: About your organization dashboard +intro: 'As an organization member, you can visit your organization''s dashboard throughout the day to stay updated on recent activity and keep track of issues and pull requests you''re working on or following in the organization.' +redirect_from: + - /articles/about-your-organization-dashboard + - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Accessing your organization dashboard + +{% data reusables.dashboard.access-org-dashboard %} + +### Finding your recent activity + +In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests in your organization. + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### Finding repositories in your organization + +In the left sidebar of your dashboard, you can access your organization's top repositories you're active in. + +![List of repositories you're most active in from your organization](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) + +### Staying updated with activity from the organization + +In the "All activity" section of your news feed, you can view updates from other teams and repositories in your organization. + +The "All activity" section shows all recent activity in the organization, including activity in repositories you're not subscribed to and of people you're not following. 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)." + +For instance, the organization news feed shows updates when someone in the organization: + - Creates a new branch. + - Comments on an issue or pull request. + - Submits a pull request review comment. + - Forks a repository. + - Creates a wiki page. + - Pushes commits.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - Creates a public repository.{% endif %} + +### Further information + +- "[About your personal dashboard](/articles/about-your-personal-dashboard)" diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md new file mode 100644 index 0000000000..728b1ac690 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -0,0 +1,26 @@ +--- +title: About your organization’s news feed +intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization. +redirect_from: + - /articles/news-feed/ + - /articles/about-your-organization-s-news-feed + - /articles/about-your-organizations-news-feed + - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}. + +### Accessing your organization's news feed + +1. {% data variables.product.signin_link %} to your {% data variables.product.product_name %} account. +2. Open your {% data reusables.user_settings.personal_dashboard %}. +3. Click the account context switcher in the upper-left corner of the page. ![Context switcher button in 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 %} +![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md new file mode 100644 index 0000000000..eab2e56131 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -0,0 +1,34 @@ +--- +title: Accessing your organization's settings +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 + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings +intro: 'The organization account settings page provides several ways to manage the account, such as billing, team membership, and repository settings.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Tip:** Only organization owners and billing managers can see and change the billing information and account settings for an organization. {% 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/ko-KR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000..6717a61c90 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md @@ -0,0 +1,28 @@ +--- +title: Creating a new organization from scratch +intro: Create an organization to apply fine-grained access permissions to repositories. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /articles/creating-a-new-organization-from-scratch + - /admin/user-management/creating-organizations + - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch +topics: + - organizations + - teams +--- + +When you create a new organization from scratch, it doesn't have any repositories associated with it. For more information on adding repositories to your organization, see "[Creating a new repository](/articles/creating-a-new-repository)" and "[Transferring a repository](/articles/transferring-a-repository)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create your organization. {% 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 %} + +### 더 읽을거리 + +{% if currentVersion == "free-pro-team@latest" %} +- "[Setting your billing email](/articles/setting-your-billing-email)"{% endif %} +- "[About organizations](/articles/about-organizations)" diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/index.md new file mode 100644 index 0000000000..1cff1af763 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/index.md @@ -0,0 +1,22 @@ +--- +title: Collaborating with groups in organizations +intro: Groups of people can collaborate across many projects at the same time in organization accounts. +redirect_from: + - /articles/creating-a-new-organization-account/ + - /articles/collaborating-with-groups-in-organizations + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000..cd6acca725 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -0,0 +1,50 @@ +--- +title: Viewing insights for your organization +intro: 'Organization insights provide data about your organization''s activity, contributions, and dependencies.' +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/viewing-insights-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +All members of an organization can view organization insights. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." + +You can use organization activity insights to help you better understand how members of your organization are using {% data variables.product.product_name %} to collaborate and work on code. Dependency insights can help you track, report, and act on your organization's open source usage. + +### Viewing organization activity insights + +{% note %} + +**Note:** Organization activity insights are currently in public beta and subject to change. + +{% endnote %} + +With organization activity insights you can view weekly, monthly, and yearly data visualizations of your entire organization or specific repositories, including issue and pull request activity, top languages used, and cumulative information about where your organization members spend their time. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**. ![Click the organization insights tab](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Optionally, in the upper-right corner of the page, choose to view data for the last **1 week**, **1 month**, or **1 year**. ![Choose time period to view org insights](/assets/images/help/organizations/org-insights-time-period.png) +5. Optionally, in the upper-right corner of the page, choose to view data for up to three repositories and click **Apply**. ![Choose repositories to view org insights](/assets/images/help/organizations/org-insights-repos.png) + +### Viewing organization dependency insights +With dependency insights you can view vulnerabilities, licenses, and other important information for the open source projects your organization depends on. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**. ![Insights tab in the main organization navigation bar](/assets/images/help/organizations/org-nav-insights-tab.png) +4. To view dependencies for this organization, click **Dependencies**. ![Dependencies tab under the main organization navigation bar](/assets/images/help/organizations/org-insights-dependencies-tab.png) +5. To view dependency insights for all your {% data variables.product.prodname_ghe_cloud %} organizations, click **My organizations**. ![My organizations button under dependencies tab](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) +6. You can click the results in the **Open security advisories** and **Licenses** graphs to filter by a vulnerability status, a license, or a combination of the two. ![My organizations vulnerabilities and licenses graphs](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +7. You can click on {% octicon "package" aria-label="The package icon" %} **dependents** next to each vulnerability to see which dependents in your organization are using each library. ![My organizations vulnerable dependents](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) + +### 더 읽을거리 + - "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" + - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" + - "[Changing the visibility of your organization's dependency insights](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)" + - "[Enforcing a policy on dependency insights in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)" diff --git a/translations/ko-KR/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/ko-KR/content/organizations/collaborating-with-your-team/about-team-discussions.md new file mode 100644 index 0000000000..364b135d72 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -0,0 +1,49 @@ +--- +title: About team discussions +intro: 'Your team can plan together, update one another, or talk about any topic you''d like in discussion posts on your team''s page in an organization.' +redirect_from: + - /articles/about-team-discussions + - /github/building-a-strong-community/about-team-discussions + - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 커뮤니티 +--- + +{% data reusables.organizations.team-discussions-purpose %} + +Any organization member can post on your team's page or participate in a public discussion. {% data reusables.organizations.team-discussions-permissions %} + +![Discussions tab of team page with public and private discussions](/assets/images/help/organizations/team-page-discussions-tab.png) + +You can link to any team discussion to reference it elsewhere. You can pin important posts to your team's page for quick reference later. For more information, see "[Pinning a team discussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion)." + +![Pinned discussions tab of team page with pinned discussion](/assets/images/help/organizations/team-discussions-pinned.png) + +{% data reusables.organizations.team-discussions-default %} Owners can disable team discussions for the entire organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." + +### Notifications for team discussions + +When someone posts or replies to a public discussion on a team's page, members of the team and members of any child teams receive email or web notifications. When someone posts or replies to a private discussion on a team's page, only members of the team receive notifications. + +{% tip %} + +**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." + +{% endtip %} + +By default, if your username is mentioned in a team discussion, you'll receive notifications for the post mentioning your username and any replies to that post. Also, by default, if you reply to a post, you will receive notifications for other replies to the post. + +To turn off notifications for team discussions, you can unsubscribe to a specific discussion post or change your notification settings to unwatch or completely ignore a specific team's discussions. You can subscribe to notifications for a specific discussion post even if you're unwatching that team's discussions. + +For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)." + +### 더 읽을거리 + +- "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)" +- "[About teams](/articles/about-teams)" +- "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)" +- "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/ko-KR/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/ko-KR/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md new file mode 100644 index 0000000000..ef7402b62a --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md @@ -0,0 +1,30 @@ +--- +title: Creating a team discussion +intro: 'Any organization member can create a _public_ team discussion post. To create a _private_ team discussion post, you must be a member of the team or an organization owner.' +redirect_from: + - /articles/creating-a-team-discussion + - /github/building-a-strong-community/creating-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 커뮤니티 +--- + +{% data reusables.organizations.team-discussions-permissions %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/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. Type a team discussion title and a comment to start a conversation. ![New team discussions comment](/assets/images/help/projects/team-discussions-comment.png) +7. Optionally, select whether you want your post to be private or public using the drop-down menu. ![Team discussions privacy settings menu](/assets/images/help/projects/team-discussions-privacy-menu.png) +8. Click **Comment**. ![Create new team discussions comment button](/assets/images/help/projects/team-discussions-comment-button.png) + +### 더 읽을거리 + + - "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" + - "[Pinning a team discussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/ko-KR/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/ko-KR/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000..7a315ca453 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,28 @@ +--- +title: Editing or deleting a team discussion +intro: 'Organization members can edit or delete discussions on a team''s page. If you''re an organization member, you can edit or delete the discussion.' +redirect_from: + - /articles/editing-or-deleting-a-team-discussion + - /github/building-a-strong-community/editing-or-deleting-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 커뮤니티 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. Click {% octicon "kebab-horizontal" aria-label="The edit icon" %} next to the team discussion you want to edit or delete. +7. Click **Edit**. Optionally, click **Delete**. ![Edit team discussion button](/assets/images/help/projects/edit-team-discussions-button.png) +8. Modify the team discussion title and comment as needed, and click **Update comment**. ![Update comment button](/assets/images/help/projects/update-comment-button.png) + +### 더 읽을거리 + + - "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Pinning a team discussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/ko-KR/content/organizations/collaborating-with-your-team/index.md b/translations/ko-KR/content/organizations/collaborating-with-your-team/index.md new file mode 100644 index 0000000000..eab148a3e3 --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-your-team/index.md @@ -0,0 +1,19 @@ +--- +title: Collaborating with your team +intro: 'Within an organization, your team can work together across projects using team discussions.' +redirect_from: + - /articles/collaborating-with-your-team + - /github/building-a-strong-community/collaborating-with-your-team + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 커뮤니티 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/ko-KR/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md new file mode 100644 index 0000000000..2aa7bd997b --- /dev/null +++ b/translations/ko-KR/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +title: Pinning a team discussion +intro: 'You can pin important discussions to your organization''s team pages for easy reference, and unpin discussions that are no longer relevant.' +redirect_from: + - /articles/pinning-a-team-discussion + - /github/building-a-strong-community/pinning-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 커뮤니티 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +5. Click {% octicon "pin" aria-label="The pin icon" %} next to the team discussion you want to pin. You can also unpin a discussion by clicking the icon. ![Pin a discussion](/assets/images/help/projects/pin-discussion-button.png) + +### 더 읽을거리 + + - "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000..cb53bfc24c --- /dev/null +++ b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,26 @@ +--- +title: About two-factor authentication and SAML single sign-on +intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-two-factor-authentication-and-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's {% data variables.product.product_name %} account could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)." + +To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)." + +If both 2FA and SAML SSO are enabled, organization members must do the following: +- Use 2FA to log in to their {% data variables.product.product_name %} account +- Use single sign-on to access the organization +- Use an authorized token for API or Git access and use single sign-on to authorize the token + +### 더 읽을거리 + +- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md new file mode 100644 index 0000000000..9406a2c559 --- /dev/null +++ b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -0,0 +1,16 @@ +--- +title: Granting access to your organization with SAML single sign-on +intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.' +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000..7d1a4231f3 --- /dev/null +++ b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,25 @@ +--- +title: Managing bots and service accounts with SAML single sign-on +intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP). + +{% warning %} + +**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization. + +{% endwarning %} + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000..f01747fae3 --- /dev/null +++ b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,64 @@ +--- +title: Viewing and managing a member's SAML access to your organization +intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.' +permissions: Organization owners can view and manage a member's SAML access to an organization. +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About SAML access to your organization + +When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing {% data variables.product.product_name %} account. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a personal access token or SSH key that the member has authorized for use with your organization. + +You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page. + +### Viewing and revoking a linked identity + +{% 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 %} + +### Viewing and revoking an active SAML session + +{% 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 %} + +### Viewing and revoking authorized credentials + +{% 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 %} + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[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)" diff --git a/translations/ko-KR/content/organizations/index.md b/translations/ko-KR/content/organizations/index.md new file mode 100644 index 0000000000..0cfd817912 --- /dev/null +++ b/translations/ko-KR/content/organizations/index.md @@ -0,0 +1,32 @@ +--- +title: Organizations and teams +shortTitle: Organizations +intro: Collaborate across many projects while managing access to projects and data and customizing settings for your organization. +redirect_from: + - /articles/about-improved-organization-permissions/ + - /categories/setting-up-and-managing-organizations-and-teams + - /github/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_with_intro /collaborating-with-groups-in-organizations %} +{% link_with_intro /managing-membership-in-your-organization %} +{% link_with_intro /managing-peoples-access-to-your-organization-with-roles %} +{% link_with_intro /organizing-members-into-teams %} +{% link_with_intro /collaborating-with-your-team %} +{% link_with_intro /managing-access-to-your-organizations-repositories %} +{% link_with_intro /managing-access-to-your-organizations-project-boards %} +{% link_with_intro /managing-access-to-your-organizations-apps %} +{% link_with_intro /managing-organization-settings %} +{% link_with_intro /restricting-access-to-your-organizations-data %} +{% link_with_intro /keeping-your-organization-secure %} +{% link_with_intro /managing-saml-single-sign-on-for-your-organization %} +{% link_with_intro /granting-access-to-your-organization-with-saml-single-sign-on %} +{% link_with_intro /managing-git-access-to-your-organizations-repositories %} +{% link_with_intro /migrating-to-improved-organization-permissions %} diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/index.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/index.md new file mode 100644 index 0000000000..f3cdc109bd --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/index.md @@ -0,0 +1,24 @@ +--- +title: Keeping your organization secure +intro: 'Organization owners have several features to help them keep their projects and data secure. 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.' +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure + - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000..e89cbfb4a9 --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Managing allowed IP addresses for your organization +intro: You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect. +product: '{% data reusables.gated-features.allowed-ip-addresses %}' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage allowed IP addresses for an organization. + +### About allowed IP addresses + +You can restrict access to organization assets by configuring an allow list for specific IP addresses. {% 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 %} + +You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see {% if currentVersion == "github-ae@latest" %}"[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." {% else %}"[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)."{% endif %} + +### Adding an allowed IP address + +{% 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 %} + +### Enabling allowed IP addresses + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +3. Under "IP allow list", select **Enable IP allow list**. ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) +4. Click **Save**. + +### Editing an allowed IP address + +{% 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. Click **Update**. + +### Deleting an allowed IP address + +{% 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 %} + +### Using {% data variables.product.prodname_actions %} with an IP allow list + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-actions.ip-allow-list-hosted-runners %} + +{% else %} + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +{% endif %} diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000..2ba1a26ae5 --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,143 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +topics: + - organizations + - teams +--- + +### 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. {% 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 %} + +### 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 all security and analysis features for the repositories in your organization. + +{% if currentVersion == "free-pro-team@latest" %}If your organization belongs to an enterprise with 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. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %}If you have 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. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} + +{% if currentVersion == "github-ae@latest" %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features.{% 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)." +2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + !["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 %} + {% if currentVersion == "github-ae@latest" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +3. Optionally, enable the feature by default for new repositories in your organization. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + !["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 %} +4. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% endif %} + {% if currentVersion == "github-ae@latest" %} +3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} + + {% data reusables.security.displayed-information %} + +### 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)." +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% if currentVersion == "github-ae@latest" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Allowing {% data variables.product.prodname_dependabot %} to access private dependencies + +{% 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. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. 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. + +If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." + +To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository: + +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 "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**. ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. Start typing the name of the repository you want to allow. ![Add repositories button](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Click the repository you want to allow. + +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. !["X" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization + +You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization. + +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. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. The size of your license is shown for organization-level licenses. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)." +1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}. +1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}. + +{% note %} + +**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning. + +{% endnote %} + +{% 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 %}{% if currentVersion != "github-ae@latest" %} +- "[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)"{% endif %} diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..a23a4647fe --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Preparing to require two-factor authentication in your organization +intro: 'Before requiring two-factor authentication (2FA), you can notify users about the upcoming change and verify who already uses 2FA.' +redirect_from: + - /articles/preparing-to-require-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +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. + +When you require use of two-factor authentication for your organization, members, outside collaborators, and billing managers (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. + +Before requiring 2FA in your organization, we recommend that you: + - [Enable 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) on your personal account + - Ask the people in your organization to set up 2FA for their accounts + - See whether [users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/) + - Warn users that once 2FA is enabled, those without 2FA are automatically removed from the organization diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..e3ec2feb8d --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,80 @@ +--- +title: Requiring two-factor authentication in your organization +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.' +redirect_from: + - /articles/requiring-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +### 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)." + +{% if currentVersion == "free-pro-team@latest" %} + +You can also require two-factor authentication for organizations in an enterprise. 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#requiring-two-factor-authentication-for-organizations-in-your-enterprise-account)." + +{% endif %} + +{% warning %} + +**Warnings:** + +- 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. They will also lose access to their forks of the organization's private repositories. You can [reinstate their access privileges and settings](/articles/reinstating-a-former-member-of-your-organization) if they enable two-factor authentication for their personal account within three months of their removal from 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. +- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization. + +{% endwarning %} + +{% data reusables.two_fa.auth_methods_2fa %} + +### 빌드전 요구 사양 + +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 %}. For more information, see "[Securing your account with two-factor authentication (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. For more information, see "[Viewing whether users in your organization have 2FA enabled](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)." + +### Requiring two-factor authentication in your organization + +{% 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. If any members or outside collaborators are removed from the organization, we recommend sending them an invitation that can reinstate their former privileges and access to your organization. They must enable two-factor authentication before they can accept your invitation. +{% endif %} + +### Viewing people who were removed from your organization + +To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search your organization's audit log](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log) for people removed from your organization. The audit log event will show if a person was removed for 2FA non-compliance. + +![Audit log event showing a user removed for 2FA non-compliance](/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. Enter your search query. To search for: + - Organization members removed, use `action:org.remove_member` in your search query + - Outside collaborators removed, use `action:org.remove_outside_collaborator` in your search query{% if currentVersion == "free-pro-team@latest" %} + - Billing managers removed, use `action:org.remove_billing_manager`in your search query{% endif %} + + You can also view people who were removed from your organization by using a [time frame](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) in your search. + +### Helping removed members and outside collaborators rejoin your organization + +If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization. + +### 더 읽을거리 + +- "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)" +- "[Reinstating a former outside collaborator's access to your organization](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000..d4e2d5c231 --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,31 @@ +--- +title: Restricting email notifications to an approved domain +intro: 'To prevent organization information from leaking into personal accounts, organization owners can restrict email notifications about organization activity to a verified domain.' +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### 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. For more information, see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)." + +Outside collaborators are not subject to restrictions on email notifications for verified domains. For more information on outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/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)." + +### Restricting email notifications to an approved domain + +{% 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. Click **Save**. diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000..eb260e3d1c --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,643 @@ +--- +title: Reviewing the audit log for your organization +intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-the-audit-log-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Accessing the audit log + +The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.audit_log.audit_log_sidebar_for_org_admins %} + +### Searching the audit log + +{% data reusables.audit_log.audit-log-search %} + +#### Search based on the action performed + +To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories: + +| Category name | 설명 | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`계정`](#account-category-actions) | Contains all activities related to your organization account. | +| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| [`결제`](#billing-category-actions) | Contains all activities related to your organization's billing. | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization. | +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." | +| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. | +| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page. | +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page. | +| [`후크`](#hook-category-actions) | Contains all activities related to webhooks. | +| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | +| [`이슈`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. | +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |{% endif %} +| [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`패키지`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. | +| [`프로젝트`](#project-category-actions) | Contains all activities related to project boards. | +| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. | +| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | +| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} | | +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| [`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 %} +| [`팀`](#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. 예시: + + * `action:team` finds all events grouped within the team category. + * `-action:hook` excludes all events in the webhook category. + +Each category has a set of associated actions that you can filter on. 예시: + + * `action:team.create` finds all events where a team was created. + * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered. + +#### Search based on time of action + +Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +예시: + + * `created:2014-07-08` finds all events that occurred on July 8th, 2014. + * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. + * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. + * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. + +The audit log contains data for the past 90 days, but you can use the `created` qualifier to search for events earlier than that. + +#### Search based on location + +Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. 예시: + + * `country:de` finds all events that occurred in Germany. + * `country:Mexico` finds all events that occurred in Mexico. + * `country:"United States"` all finds events that occurred in the United States. + +{% if currentVersion == "free-pro-team@latest" %} +### Exporting the audit log + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### Using the audit log API + +You can interact with the audit log using the GraphQL API{% if currentVersion == "free-pro-team@latest" %} or the REST API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Using the GraphQL API + +{% endif %} + +{% note %} + +**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +To ensure a secure IP and maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audit-log-api-info %} + +{% if currentVersion == "free-pro-team@latest" %} +Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)." +{% endif %} + +The GraphQL response can include data for up to 90 to 120 days. + +For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)." + +{% if currentVersion == "free-pro-team@latest" %} + +#### Using the REST API + +{% note %} + +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. + +{% endnote %} + +To ensure a secure IP and maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audit-log-api-info %} +* Git events, such as cloning, fetching, and pushing + +{% data reusables.audit_log.audit-log-git-events-retention %} + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endif %} + +### Audit log actions + +An overview of some of the most common actions that are recorded as events in the audit log. + +{% if currentVersion == "free-pro-team@latest" %} + +#### `account` category actions + +| 동작 | 설명 | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes. | +| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes. | +| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). | +| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/). | + +#### `advisory_credit` category actions + +| 동작 | 설명 | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." | +| `create` | Triggered when the administrator of a security advisory adds someone to the credit section. | +| `decline` | Triggered when someone declines credit for a security advisory. | +| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. | + +#### `billing` category actions + +| 동작 | 설명 | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). | +| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes. | + +#### `dependabot_alerts` category actions + +| 동작 | 설명 | +| ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `활성화` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +#### `dependabot_alerts_new_repos` category actions + +| 동작 | 설명 | +| ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `활성화` | 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 + +| 동작 | 설명 | +| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `비활성화` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `활성화` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. | + +#### `dependabot_security_updates_new_repos` category actions + +| 동작 | 설명 | +| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `활성화` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. | + +#### `dependency_graph` category actions + +| 동작 | 설명 | +| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `활성화` | Triggered when an organization owner enables the dependency graph for all existing repositories. | + +#### `dependency_graph_new_repos` category actions + +| 동작 | 설명 | +| ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `활성화` | Triggered when an organization owner enables the dependency graph for all new repositories. | + +{% endif %} + +#### `discussion_post` category actions + +| 동작 | 설명 | +| --------- | --------------------------------------------------------------------------------------------------------------- | +| `업데이트` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). | + +#### `discussion_post_reply` category actions + +| 동작 | 설명 | +| --------- | -------------------------------------------------------------------------------------------------------------------------- | +| `업데이트` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### `enterprise` category actions + +{% data reusables.actions.actions-audit-events-for-enterprise %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `environment` category actions + +| 동작 | 설명 | +| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `git` category actions + +{% note %} + +**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| 동작 | 설명 | +| ------ | ----------------------------------------------------- | +| `클론` | Triggered when a repository is cloned. | +| `가져오기` | Triggered when changes are fetched from a repository. | +| `푸시` | Triggered when changes are pushed to a repository. | + +{% endif %} + +#### `hook` category actions + +| 동작 | 설명 | +| ---------------- | -------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization. | +| `config_changed` | Triggered when an existing hook has its configuration altered. | +| `destroy` | Triggered when an existing hook was removed from a repository. | +| `events_changed` | Triggered when the events on a hook have been altered. | + +#### `integration_installation_request` category actions + +| 동작 | 설명 | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. | +| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. | + +#### `issue` category actions + +| 동작 | 설명 | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `destroy` | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository. | + +{% if currentVersion == "free-pro-team@latest" %} + +#### `marketplace_agreement_signature` category actions + +| 동작 | 설명 | +| -------- | -------------------------------------------------------------------------------------------------- | +| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. | + +#### `marketplace_listing` category actions + +| 동작 | 설명 | +| --------- | --------------------------------------------------------------------------------------------------------------- | +| `승인` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. | +| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. | +| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. | +| `redraft` | Triggered when your listing is sent back to draft state. | +| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +#### `members_can_create_pages` category actions + +For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." + +| 동작 | 설명 | +|:------ |:---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `활성화` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | +| `비활성화` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | + +{% endif %} + +#### `org` category actions + +| 동작 | 설명 | +| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `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](/communities/maintaining-your-safety-on-github/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 {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/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" %} +| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization. | +| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %} +| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% if currentVersion != "github-ae@latest" %} +| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %} +| `invite_member` | Triggered when [a new user was invited to join your organization](/articles/adding-organization-members-to-a-team).{% if currentVersion == "free-pro-team@latest" %} +| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). | +| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization. | +| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." | +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. +{% endif %} +| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization. | +| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/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` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." | +| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/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` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | +| `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | +| `runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% 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` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."{% endif %} +| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members. | +| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner. | +| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% if currentVersion == "free-pro-team@latest" %} +| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated. | +| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `org_credential_authorization` category actions + +| 동작 | 설명 | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `revoke` | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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" %} +#### `organization_label` category actions + +| 동작 | 설명 | +| --------- | ------------------------------------------ | +| `create` | Triggered when a default label is created. | +| `업데이트` | Triggered when a default label is edited. | +| `destroy` | Triggered when a default label is deleted. | + +{% endif %} + +#### `oauth_application` category actions + +| 동작 | 설명 | +| --------------- | ------------------------------------------------------------------------------------------------------------------ | +| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. | +| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. | +| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. | +| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. | +| `전송` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +#### `packages` category actions + +| 동작 | 설명 | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `package_version_published` | Triggered when a package version is published. | +| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `payment_method` category actions + +| 동작 | 설명 | +| -------- | ------------------------------------------------------------------------------------------ | +| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method). | +| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account. | +| `업데이트` | Triggered when an existing payment method is updated. | + +{% endif %} + +#### `profile_picture` category actions +| 동작 | 설명 | +| ---- | --------------------------------------------------------------------- | +| 업데이트 | Triggered when you set or update your organization's profile picture. | + +#### `project` category actions + +| 동작 | 설명 | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Triggered when a project board is created. | +| `link` | Triggered when a repository is linked to a project board. | +| `rename` | Triggered when a project board is renamed. | +| `업데이트` | Triggered when a project board is updated. | +| `delete` | Triggered when a project board is deleted. | +| `unlink` | Triggered when a repository is unlinked from a project board. | +| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. | +| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. | +| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed. | + +#### `protected_branch` category actions + +| 동작 | 설명 | +| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when branch protection is enabled on a branch. | +| `destroy` | Triggered when branch protection is disabled on a branch. | +| `update_admin_enforced` | Triggered when branch protection is enforced for repository administrators. | +| `update_require_code_owner_review` | Triggered when enforcement of required Code Owner review is updated on a branch. | +| `dismiss_stale_reviews` | Triggered when enforcement of dismissing stale pull requests is updated on a branch. | +| `update_signature_requirement_enforcement_level` | Triggered when enforcement of required commit signing is updated on a branch. | +| `update_pull_request_reviews_enforcement_level` | Triggered when enforcement of required pull request reviews is updated on a branch. | +| `update_required_status_checks_enforcement_level` | Triggered when enforcement of required status checks is updated on a branch. | +| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | +| `rejected_ref_update` | Triggered when a branch update attempt is rejected. | +| `policy_override` | Triggered when a branch protection requirement is overridden by a repository administrator.{% 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` | Triggered when force pushes are enabled or disabled for a protected branch. | +| `update_allow_deletions_enforcement_level` | Triggered when branch deletion is enabled or disabled for a protected branch. | +| `update_linear_history_requirement_enforcement_level` | Triggered when required linear commit history is enabled or disabled for a protected branch. | +{% endif %} + +#### `repo` category actions + +| 동작 | 설명 | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `액세스` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. | +| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +| `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" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for 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)." | +| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for 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).".{% 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.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 {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} +| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `비활성화` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %} +| `활성화` | 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 {% data variables.product.prodname_actions %} secret is removed.{% 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 new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/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).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `전송` | 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 {% data variables.product.prodname_actions %} secret is updated.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `repository_advisory` category actions + +| 동작 | 설명 | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | +| `open` | Triggered when someone opens a draft security advisory. | +| `publish` | Triggered when someone publishes a security advisory. | +| `reopen` | Triggered when someone reopens as draft security advisory. | +| `업데이트` | Triggered when someone edits a draft or published security advisory. | + +#### `repository_content_analysis` category actions + +| 동작 | 설명 | +| ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `활성화` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | +| `비활성화` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | + +{% endif %}{% if currentVersion != "github-ae@latest" %} + +#### `repository_dependency_graph` category actions + +| 동작 | 설명 | +| ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | +| `활성화` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### `repository_secret_scanning` category actions + +| 동작 | 설명 | +| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | +| `활성화` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### `repository_vulnerability_alert` category actions + +| 동작 | 설명 | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when {% data variables.product.product_name %} creates a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | +| `해제` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. | +| `해결` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### `repository_vulnerability_alerts` category actions + +| 동작 | 설명 | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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)." | +| `비활성화` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. | +| `활성화` | 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" or currentVersion == "github-ae@latest" %} +#### `secret_scanning` category actions + +| 동작 | 설명 | +| ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | 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)." | +| `활성화` | 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 + +| 동작 | 설명 | +| ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | Triggered when an organization owner disables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | +| `활성화` | Triggered when an organization owner enables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `sponsors` category actions + +| 동작 | 설명 | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo_funding_link_button_toggle` | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `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 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 "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| sponsored_developer_update_newsletter_send | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `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 %} + +#### `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.{% 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](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/managing-peoples-access-to-your-organization-with-roles/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 + +| 동작 | 설명 | +| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `비활성화` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." | +| `활성화` | Triggered when an organization owner enables team discussions for an organization. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +#### `workflows` category actions + +{% data reusables.actions.actions-audit-events-workflow %} + +{% endif %} + +### 더 읽을거리 + +- "[Keeping your organization secure](/articles/keeping-your-organization-secure)" diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000..4e7d59f603 --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,25 @@ +--- +title: Reviewing your organization's installed integrations +intro: You can review the permission levels for your organization's installed integrations and configure each integration's access to organization repositories. +redirect_from: + - /articles/reviewing-your-organization-s-installed-integrations + - /articles/reviewing-your-organizations-installed-integrations + - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. In the left sidebar, click **Installed {% data variables.product.prodname_github_app %}s**. ![Installed {% data variables.product.prodname_github_app %}s tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png) +6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png) + - To give the {% data variables.product.prodname_github_app %} access to all of your organization's repositories, select **All repositories**. + - To choose specific repositories to give the application access to, select **Only select repositories**, then type a repository name. +7. Click **Save**. diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000..ef3c1ce752 --- /dev/null +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,30 @@ +--- +title: Viewing whether users in your organization have 2FA enabled +intro: 'You can see which organization owners, members, and outside collaborators have enabled two-factor authentication.' +redirect_from: + - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled + - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% 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. For more information, see "[Requiring two-factor authentication in your organization](/articles/requiring-two-factor-authentication-in-your-organization)." + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. To view organization members, including organization owners, who have enabled or disabled two-factor authentication, on the right, click **2FA**, and select **Enabled** or **Disabled**. ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png) +5. To view outside collaborators in your organization, under the "People" tab, click **Outside collaborators**. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) +6. To view which outside collaborators have enabled or disabled two-factor authentication, on the right, click **2FA**, and select **Enabled** or **Disabled**. ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) + +### 더 읽을거리 + +- "[Viewing people's roles in an organization](/articles/viewing-people-s-roles-in-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000..8e2654625e --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,40 @@ +--- +title: Adding GitHub App managers in your organization +intro: 'Organization owners can grant users the ability to manage some or all {% data variables.product.prodname_github_app %}s owned by the organization.' +redirect_from: + - /articles/adding-github-app-managers-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization#github-app-managers)." + +### Giving someone the ability to manage all {% data variables.product.prodname_github_app %}s owned by the organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Under "Management", type the username of the person you want to designate as a {% data variables.product.prodname_github_app %} manager in the organization, and click **Grant**. ![Add a {% data variables.product.prodname_github_app %} manager](/assets/images/help/organizations/add-github-app-manager.png) + +### Giving someone the ability to manage an individual {% 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. Under "{% 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. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Under "App managers", type the username of the person you want to designate as a GitHub App manager for the app, and click **Grant**. ![Add a {% data variables.product.prodname_github_app %} manager for a specific app](/assets/images/help/organizations/add-github-app-manager-for-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### 더 읽을거리 + +- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/index.md new file mode 100644 index 0000000000..07610efc3f --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -0,0 +1,18 @@ +--- +title: Managing access to your organization's apps +intro: 'As an organization owner, you can allow individual organization members to manage {% data variables.product.prodname_github_app %}s in your organization.' +redirect_from: + - /articles/managing-access-to-your-organization-s-apps + - /articles/managing-access-to-your-organizations-apps + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /adding-github-app-managers-in-your-organization %} +{% link_in_list /removing-github-app-managers-from-your-organization %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000..94d97f9e03 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,40 @@ +--- +title: Removing GitHub App managers from your organization +intro: 'Organization owners can revoke {% data variables.product.prodname_github_app %} manager permissions that were granted to a member of the organization.' +redirect_from: + - /articles/removing-github-app-managers-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization#github-app-managers)." + +### Removing a {% data variables.product.prodname_github_app %} manager's permissions for the entire organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Under "Management", find the username of the person you want to remove {% data variables.product.prodname_github_app %} manager permissions from, and click **Revoke**. ![Revoke {% data variables.product.prodname_github_app %} manager permissions](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) + +### Removing a {% data variables.product.prodname_github_app %} manager's permissions for an individual {% 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. Under "{% 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. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Under "App managers", find the username of the person you want to remove {% data variables.product.prodname_github_app %} manager permissions from, and click **Revoke**. ![Revoke {% data variables.product.prodname_github_app %} manager permissions](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### 더 읽을거리 + +- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000..26843c4457 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Adding an outside collaborator to a project board in your organization +intro: 'As an organization owner or project board admin, you can add an outside collaborator and customize their permissions to a project board.' +redirect_from: + - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a project board in your 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 %} +9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or {% data variables.product.prodname_dotcom %} email. ![The Collaborators section with the Octocat's username entered in the search field](/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/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/index.md new file mode 100644 index 0000000000..22f18b40c8 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -0,0 +1,22 @@ +--- +title: Managing access to your organization’s project boards +intro: 'As an organization owner or project board admin, you can give organization members, teams, and outside collaborators different levels of access to project boards owned by your organization.' +redirect_from: + - /articles/managing-access-to-your-organization-s-project-boards + - /articles/managing-access-to-your-organizations-project-boards + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000..fddfd4fe1e --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,39 @@ +--- +title: Managing access to a project board for organization members +intro: 'As an organization owner or project board admin, you can set a default permission level for a project board for all organization members.' +redirect_from: + - /articles/managing-access-to-a-project-board-for-organization-members + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +By default, organization members have write access to their organization's project boards unless organization owners or project board admins set different permissions for specific project boards. + +### Setting a baseline permission level for all organization members + +{% tip %} + +**Tip:** You can give an organization member higher permissions to project board. For more information, see "[Project board permissions for an organization](/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. Under "Organization member permission", choose a baseline permission level for all organization members: **Read**, **Write**, **Admin**, or **None**. ![Baseline project board permission options for all organization members](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. Click **Save**. + +### 더 읽을거리 + +- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..4f99ed5d09 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,62 @@ +--- +title: Managing an individual’s access to an organization project board +intro: 'As an organization owner or project board admin, you can manage an individual member''s access to a project board owned by your organization.' +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-project-board + - /articles/managing-an-individuals-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% note %} + +**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." + +{% endnote %} + +### Giving an organization member access to a project board + +{% 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. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email. ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} + +### Changing an organization member's access to a project board + +{% 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 %} + +### Removing an organization member's access to a project board + +When you remove a collaborator from a project board, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a project board, you must remove access for each role the person has. For instance, a person may have access to the project board as an organization member or team member. For more information, see "[Project board permissions for an organization](/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 %} + +### 더 읽을거리 + +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..14426751a6 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,52 @@ +--- +title: Managing team access to an organization project board +intro: 'As an organization owner or project board admin, you can give a team access to a project board owned by your organization.' +redirect_from: + - /articles/managing-team-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% warning %} + +**Warnings:** +- You can change a team's permission level if the team has direct access to a project board. If the team's access to the project board is inherited from a parent team, you must change the parent team's access to the project board. +- If you add or remove project board access for a parent team, each of that parent's child teams will also receive or lose access to the project board. For more information, see "[About teams](/articles/about-teams)." + +{% endwarning %} + +### Giving a team access to a project board + +You can give an entire team the same permission level to a project board. + +{% note %} + +**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a project board, and a project board admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the project board. For more information see, "[Project board permissions for an organization](/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. In the left sidebar, click **Teams**. +9. To add a team, click **Add a team: Select team**. Then, choose a team from the drop-down menu or search for the team you'd like to add. ![Add a team drop-down menu with list of teams in organization](/assets/images/help/projects/add-a-team.png) +10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**. ![Team permissions drop-down menu with read, write, and admin options](/assets/images/help/projects/org-project-team-choose-permissions.png) + +### Configuring a team's access to a project board + +If a team's access to a project board is inherited from a parent team, you must change the parent team's access to the project board to update access to the child teams. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**. ![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png) +5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png) diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000..288b0c8e65 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -0,0 +1,44 @@ +--- +title: Project board permissions for an organization +intro: 'Organization owners and people with project board admin permissions can customize who has read, write, and admin permissions to your organization’s project boards.' +redirect_from: + - /articles/project-board-permissions-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Permissions overview + +There are three levels of permissions to a project board for people and teams: + +{% data reusables.project-management.project-board-permissions %} + +Organization owners and people with admin permissions can give a person access to an organization project board individually, as an outside collaborator or organization member, or through their membership in a team or organization. An outside collaborator is someone who is not an organization member but given permissions to collaborate in your organization. + +Organization owners and people with admin permissions to a project board can also: +- Set default project board permissions for all organization members. +- Manage access to the project board for organization members, teams, and outside collaborators. For more information, see "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)", "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)", or "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." +- Manage project board visibility. For more information, see "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." + +### Cascading permissions for project boards + +{% data reusables.project-management.cascading-permissions %} + +For example, if an organization owner has given all organization members read permissions to a project board, and a project board admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the project board. + +### 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)." + +### 더 읽을거리 + +- "[Changing project board visibility](/articles/changing-project-board-visibility)" +- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)" +- "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000..4c2d3ff3cf --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,23 @@ +--- +title: Removing an outside collaborator from an organization project board +intro: 'As an organization owner or project board admin, you can remove an outside collaborator''s access to a project board.' +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000..54b1ae8667 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,42 @@ +--- +title: Adding outside collaborators to repositories in your organization +intro: 'An *outside collaborator* is a person who isn''t explicitly a member of your organization, but who has Read, Write, or Admin permissions to one or more repositories in your organization.' +redirect_from: + - /articles/adding-outside-collaborators-to-repositories-in-your-organization + - github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} add outside collaborators to a repository, unless an organization owner has restricted the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/articles/setting-permissions-for-adding-outside-collaborators)." + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% if currentVersion != "github-ae@latest" %} +If your organization [requires members and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), they must enable two-factor authentication before they can accept your invitation to collaborate on an organization repository. +{% 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. In the search field, start typing the name of person you want to invite, then click a name in the list of matches. ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png) +6. Under "Choose a role", select the permissions to grant to the person, then click **Add NAME to REPOSITORY**. ![Selecting permissions for the person](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +{% else %} +5. In the left sidebar, click **Collaborators & teams**. ![Repository settings sidebar with Collaborators & teams highlighted](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**. ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. Next to the new collaborator's name, choose the appropriate permission level: *Write*, *Read*, or *Admin*. ![The repository permissions picker](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +{% endif %} + +### 더 읽을거리 + +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000..3570e12c1d --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,24 @@ +--- +title: Canceling an invitation to become an outside collaborator in your organization +intro: You can cancel all invitations for a person to become an outside collaborator on repositories owned by your organization. +permissions: Organization owners can cancel an invitation to become an outside collaborator in the organization. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +You can view a list of all people with pending invitations to become an outside collaborator on any repository owned by your organization. + +For each pending collaborator, you can cancel all invitations to join organization repositories at the same time. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% 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 cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000..1b6e64d02f --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,44 @@ +--- +title: Converting an organization member to an outside collaborator +intro: 'If a current member of your organization only needs access to certain repositories, such as consultants or temporary employees, you can convert them to an *outside collaborator*.' +redirect_from: + - /articles/converting-an-organization-member-to-an-outside-collaborator + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} convert organization members into outside collaborators. + +{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} + +After converting an organization member to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The person will no longer be an explicit member of the organization, and will no longer be able to: + +- Create teams +- See all organization members and teams +- @mention any visible team +- Be a team maintainer + +For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)." + +We recommend reviewing the organization member's access to repositories to ensure their access is as you expect. For more information, see "[Managing an individual's access to an organization repository](/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. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Select the person or people you'd like to convert to outside collaborators. ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Above the list of members, use the drop-down menu and click **Convert to outside collaborator**. ![Drop-down menu with option to convert members to outside collaborators](/assets/images/help/teams/user-bulk-management-options.png) +6. Read the information about converting members to outside collaborators, then click **Convert to outside collaborator**. ![Information on outside collaborators permissions and Convert to outside collaborators button](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) + +### 더 읽을거리 + +- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)" +- "[Converting an outside collaborator to an organization member](/articles/converting-an-outside-collaborator-to-an-organization-member)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000..93aa773e28 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,41 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization owners can {% if currentVersion == "free-pro-team@latest" %}invite users to join{% else %}add users to{% endif %} an organization.' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization is on a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}{% endif %} + +{% 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 %} +{% 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. 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. 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 %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### 더 읽을거리 + +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..b8b30ba6d4 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/index.md @@ -0,0 +1,28 @@ +--- +title: Managing access to your organization's repositories +intro: Organization owners can manage individual and team access to the organization's repositories. Team maintainers can also manage a team's repository access. +redirect_from: + - /articles/permission-levels-for-an-organization-repository/ + - /articles/managing-access-to-your-organization-s-repositories + - /articles/managing-access-to-your-organizations-repositories + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000..4abce445c7 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,39 @@ +--- +title: Managing an individual's access to an organization repository +intro: You can manage a person's access to a repository owned by your organization. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +People with admin permissions can manage the access of organization members and outside collaborators to an organization repository. + +### Removing access to repositories + +When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository. + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +### Managing an individual's access to an organization repository + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png) +5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. ![The manage access link](/assets/images/help/organizations/member-manage-access.png) +6. On the "Manage access" page, next to the repository, click **Manage access**. ![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png) +7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership. ![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png) + +### 더 읽을거리 + +{% if currentVersion == "free-pro-team@latest" %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %} +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000..bc73db6729 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +title: Managing team access to an organization repository +intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.' +redirect_from: + - /articles/managing-team-access-to-an-organization-repository-early-access-program/ + - /articles/managing-team-access-to-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository. + +{% warning %} + +**Warnings:** +- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository. +- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)." + +{% endwarning %} + +### Giving a team access to a repository + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. Above the list of repositories, click **Add repository**. ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png) +6. Type the name of a repository, then click **Add repository to team**. ![Repository search field](/assets/images/help/organizations/team-repositories-add.png) +7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team. ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png) + +### Removing a team's access to a repository + +You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams. + +{% 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. Select the repository or repositories you'd like to remove from the team. ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png) +6. Above the list of repositories, use the drop-down menu, and click **Remove from team**. ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png) +7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**. ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png) + +### 더 읽을거리 + +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000..8652e704ea --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Reinstating a former outside collaborator's access to your organization +intro: 'You can reinstate a former outside collaborator''s access permissions for organization repositories, forks, and settings.' +redirect_from: + - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization + - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +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. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +When you reinstate a former outside collaborator, you can restore: + - The user's former access to organization repositories + - Any private forks of repositories owned by the organization + - Membership in the organization's teams + - Previous access and permissions for the organization's repositories + - Stars for organization repositories + - Issue assignments in the organization + - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity) + +{% tip %} + +**Tips**: + - Only organization owners can reinstate outside collaborators' access to an organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." + - The reinstating a member flow on {% data variables.product.product_location %} may use the term "member" to describe reinstating an outside collaborator but if you reinstate this person and keep their previous privileges, they will only have their previous [outside collaborator permissions](/articles/permission-levels-for-an-organization/#outside-collaborators).{% if currentVersion == "free-pro-team@latest" %} + - If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."{% endif %} + +{% 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. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Invite and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Invite and start fresh**. + + {% warning %} + + **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Invite and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Invite and reinstate** instead. Once this person accepts the invitation, you can convert them to an organization member by [inviting them to join the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Add and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Add and start fresh**. + + {% warning %} + + **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Add and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Add and reinstate** instead. Then, you can convert them to an organization member by [adding them to the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Send invitation**. ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Add member**. ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +8. The invited person will receive an email inviting them to the organization. They will need to accept the invitation before becoming an outside collaborator in the organization. {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### 더 읽을거리 + +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000..e4c41b9dab --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,57 @@ +--- +title: Removing an outside collaborator from an organization repository +intro: Owners and repository admins can remove an outside collaborator's access to a repository. +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Warning:** +- When removing an outside collaborator from a private repository, the paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." + +- You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. + +{% endwarning %} + +{% endif %} + +While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository. + +### Removing outside collaborators from all repositories in an organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Select the outside collaborator or outside collaborators you'd like to remove from the organization. ![List of outside collaborators with two outside collaborators selected](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) +6. Above the list of outside collaborators, use the drop-down menu, and click **Remove from all repositories**. ![Drop-down menu with option to remove outside collaborators ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) +7. Review the outside collaborator or outside collaborators who will be removed from the organization, then click **Remove outside collaborators**. ![List of outside collaborators who will be removed and Remove outside collaborators button](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) + +### Removing an outside collaborator from a particular repository in an organization + +If you only want to remove an outside collaborator from certain repositories in your organization, you can remove this person's access to one specific repository at a time. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. To the right of the username of the person you want to remove, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. ![Manage access button](/assets/images/help/organizations/member-manage-access.png) +6. To the right of the repository that you want to remove the outside collaborator from, click **Manage access**. ![Select manage access button next to a repository the outside collaborator has access to](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) +7. To completely remove the outside collaborator's access to the repository, in the upper right corner, click **Remove access to this repository**. ![Remove access to this repository button](/assets/images/help/organizations/remove-access-to-this-repository.png) +8. To confirm, click **Remove access**. ![Confirm outside collaborator who will be removed from the repository](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) + +### 더 읽을거리 + +- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000..2eb382ae1a --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -0,0 +1,181 @@ +--- +title: Repository permission levels for an organization +intro: 'You can customize access to each repository in your organization with granular permission levels, giving people access to the features and tasks they need.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +People with admin permissions can manage individual and team access to an organization-owned repository. + +### Permission levels for repositories owned by an organization + +You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization. Each permission level progressively increases access to a repository's content and settings. Choose the level that best fits each person or team's role in your project without giving people more access to the project than they need. + +From least access to most access, the permission levels for an organization repository are: +- **Read**: Recommended for non-code contributors who want to view or discuss your project +- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access +- **Write**: Recommended for contributors who actively push to your project +- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions +- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +For more information about giving people and teams access to repositories, see "[Managing access to your organization's repositories](/articles/managing-access-to-your-organizations-repositories)." + +Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." + +Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)." + +In addition to managing organization-level settings, organization owners have admin permissions for every repository owned by the organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." + +{% warning %} + +**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization. + +{% endwarning %} + +### Repository access for each permission level +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** Repository permissions required to use security features are listed in "[Permission requirements for security features](#permission-requirements-for-security-features)" below. + +{% endnote %} + +{% 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](/communities/maintaining-your-safety-on-github/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" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [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](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/communities/moderating-comments-and-conversations/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" or currentVersion == "github-ae@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** | +| | | | | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **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](/communities/moderating-comments-and-conversations/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](/organizations/managing-access-to-your-organizations-repositories/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" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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" %} +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +{% endif %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +#### Permission requirements for security features + +In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_advanced_security %} features. + +| Repository action | Read | 심사 | Write | Maintain | Admin | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:| +| {% if currentVersion == "free-pro-team@latest" %} | | | | | | +| 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** | +| 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.22" or currentVersion == "github-ae@latest" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** | +| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| [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@3.0" or currentVersion == 'github-ae@next' %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% if currentVersion == "enterprise-server@3.0" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +[1] Repository writers and maintainers can only see alert information for their own commits. +{% endif %} +{% endif %} + +### 더 읽을거리 + +- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)" +- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000..db327b23e4 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -0,0 +1,36 @@ +--- +title: Setting base permissions for an organization +intro: You can set base permissions for the repositories that an organization owns. +permissions: Organization owners can set base permissions for an organization. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### About base permissions for an organization + +You can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. Base permissions do not apply to outside collaborators. + +{% if currentVersion == "free-pro-team@latest" %}By default, members of an organization will have **Read** permissions to the organization's repositories.{% endif %} + +If someone with admin permissions to an organization's repository grants a member a higher level of permission for the repository, the higher level of permission overrides the base permission. + +### Setting base permissions + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Base permissions", use the drop-down to select new base permissions. ![Selecting new permission level from base permissions drop-down](/assets/images/help/organizations/base-permissions-drop-down.png) +6. Review the changes. To confirm, click **Change default permission to PERMISSION**. ![Reviewing and confirming change of base permissions](/assets/images/help/organizations/base-permissions-confirm.png) + +### 더 읽을거리 + +- "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" +- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000..70fba13ca5 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,41 @@ +--- +title: Viewing people with access to your repository +intro: 'Organization owners can view people’s access to a repository within an organization. Owners of organizations using {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} can also export a CSV list of people who have access to a repository.' +redirect_from: + - /articles/viewing-people-with-access-to-your-repository + - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Administrators can use this information to help off-board people, gather data for compliance, and other general security checkups. + +![Repository people permissions list](/assets/images/help/repository/repository-permissions-list.png) + +### Viewing people with access to your repository + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note**: You can also see a combined overview of teams and people with access to your repository. For more information, see "[Managing teams and people with access to your repository](/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 %} + +### Exporting a list of people with access to your repository + +Owners of organizations on {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} can export a CSV list of people who have access to a repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} +4. Click **Export CSV**. ![People tab in the repository sidebar](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000..7b371b9ae4 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -0,0 +1,47 @@ +--- +title: About SSH certificate authorities +intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.' +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/about-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)." + +After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with 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 %} + +For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. + +When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +``` + +You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +{% if currentVersion == "free-pro-team@latest" %} + +Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, personal access tokens, and their own SSH keys. + +{% endif %} + +To prevent authentication errors, organization members should use a special URL that includes the organization ID to clone repositories using signed certificates. Anyone with read access to the repository can find this URL on the repository page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." diff --git a/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..8bdd4f0224 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -0,0 +1,19 @@ +--- +title: Managing Git access to your organization's repositories +intro: You can add an SSH certificate authority (CA) to your organization and allow members to access the organization's repositories over Git using keys signed by the SSH CA. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /about-ssh-certificate-authorities %} +{% link_in_list /managing-your-organizations-ssh-certificate-authorities %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000..775efdaa45 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,38 @@ +--- +title: Managing your organization's SSH certificate authorities +intro: You can add or delete SSH certificate authorities from your organization. +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-your-organizations-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage an organization's SSH certificate authorities (CA). + +You can allow members to access your organization's repositories using SSH certificates you provide by adding an SSH CA to your organization. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)." + +### Adding an SSH certificate authority + +{% 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 %} + +### Deleting an SSH certificate authority + +{% 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/ko-KR/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md new file mode 100644 index 0000000000..1c449992dc --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -0,0 +1,29 @@ +--- +title: Adding people to your organization +intro: 'You can make anyone a member of your organization using their {% data variables.product.product_name %} username or email address.' +redirect_from: + - /articles/adding-people-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization +versions: + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization owners can add people to an organization.' +--- + +{% if currentVersion != "github-ae@latest" %} +If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization. +{% 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 %} + +### 더 읽을거리 +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ko-KR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000..f13fa6a80f --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,21 @@ +--- +title: Can I create accounts for people in my organization? +intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization + - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Because you access an organization by logging in to a personal account, each of your team members needs a personal account. Once you have user names for each person you'd like to add to your organization, you can add them to teams. + +### Adding users to your organization + +1. Provide each person instructions to [create a personal account](/articles/signing-up-for-a-new-github-account). +2. Ask for the username of each person you want to give organization membership to. +3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account. diff --git a/translations/ko-KR/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000..7cb91fca47 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Canceling or editing an invitation to join your organization +intro: Organization owners can edit or cancel an invitation to become a member of your organization any time before the user accepts. +redirect_from: + - /articles/canceling-or-editing-an-invitation-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. On the People tab, click **Pending invitation**. ![Pending invitation link](/assets/images/help/organizations/pending-invitation-link.png) +5. Next to the username or email address of the person whose invitation you'd like to edit or cancel, click **Edit invitation**. ![Edit invitation button](/assets/images/help/organizations/edit-invitation-button.png) + + You may need to click **View all invitations** at the bottom of the window to find the person you're looking for. +6. Decide whether to edit or cancel the user's invitation to join your organization. ![Update invitation and cancel invitation buttons](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) + - To edit the user's invitation, select a different role or team, then click **Update invitation**. + - To cancel the user's invitation to join your organization, click **Cancel invitation**. + +### 더 읽을거리 + +{% if currentVersion == "free-pro-team@latest" %} +- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" +{% endif %} +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ko-KR/content/organizations/managing-membership-in-your-organization/index.md b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/index.md new file mode 100644 index 0000000000..f28c95e40d --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/index.md @@ -0,0 +1,23 @@ +--- +title: Managing membership in your organization +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. You can also remove members of the organization, and reinstate former members.' +redirect_from: + - /articles/removing-a-user-from-your-organization/ + - /articles/managing-membership-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000..2698e9c563 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Inviting users to join your organization +intro: 'You can invite anyone to become a member of your organization using their {% data variables.product.product_name %} username or email address.' +permissions: Organization owners can invite users to join an organization. +redirect_from: + - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ + - /articles/inviting-users-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Tips**: +- If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% 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](/organizations/keeping-your-organization-secure/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)." + +{% 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 %} + +### 더 읽을거리 +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ko-KR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000..d761d9071c --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,63 @@ +--- +title: Reinstating a former member of your organization +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.' +redirect_from: + - /articles/reinstating-a-former-member-of-your-organization + - /github/setting-up-and-managing-organizations-and-teams/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. +topics: + - organizations + - teams +--- + +### 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. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +When you reinstate a former organization member, you can restore: + - The user's role in the organization + - Any private forks of repositories owned by the organization + - Membership in the organization's teams + - Previous access and permissions for the organization's repositories + - Stars for organization repositories + - Issue assignments in the organization + - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity) + +{% if enterpriseServerVersions contains currentVersion %} +If an organization member was removed from the organization because they did not use two-factor authentication and your organization still requires members to use 2FA, the former member must enable two-factor authentication before you can reinstate their membership. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +If your organization has a paid per-user subscription, an unused license must be available before you can 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 %} + +### Reinstating a former member of your organization + +{% 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. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Invite and reinstate** or **Invite and start fresh**. ![Choose to restore info or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Add and reinstate** or **Add and start fresh**. ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Send invitation**. ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Add member**. ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### 더 읽을거리 + +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/ko-KR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000..a81f545508 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -0,0 +1,60 @@ +--- +title: Removing a member from your organization +intro: 'If members of your organization no longer require access to any repositories owned by the organization, you can remove them from the organization.' +redirect_from: + - /articles/removing-a-member-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Only organization owners can remove members from an organization. + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Warning:** When you remove members from an organization: +- The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." +- Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. +- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. + +{% endwarning %} + +{% else %} + +{% warning %} + +**Warning:** When you remove members from an organization: + - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. + - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. + +{% endwarning %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +To help the person you're removing from your organization transition and help ensure they delete confidential information or intellectual property, we recommend sharing a checklist of best practices for leaving your organization. For an example, see "[Best practices for leaving your company](/articles/best-practices-for-leaving-your-company/)." + +{% endif %} + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} + +### Revoking the user's membership + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Select the member or members you'd like to remove from the organization. ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Above the list of members, use the drop-down menu, and click **Remove from organization**. ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png) +6. Review the member or members who will be removed from the organization, then click **Remove members**. ![List of members who will be removed and Remove members button](/assets/images/help/teams/confirm-remove-members-bulk.png) + +### 더 읽을거리 + +- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000..2b4f1b54a6 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Allowing people to delete issues in your organization +intro: Organization owners can allow certain people to delete issues in repositories owned by your organization. +redirect_from: + - /articles/allowing-people-to-delete-issues-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +By default, issues cannot be deleted in an organization's repositories. An organization owner must enable this feature for all of the organization's repositories first. + +Once enabled, organization owners and people with admin permissions in an organization-owned repository can delete issues. People with admin permissions in a repository include organization members and outside collaborators with admin privileges. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)" and "[Deleting an issue](/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. Under "Issue deletion", select **Allow members to delete issues for this organization**. ![Checkbox to allow people to delete issues](/assets/images/help/settings/issue-deletion.png) +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/ko-KR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000..c262ff9885 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,24 @@ +--- +title: Changing the visibility of your organization's dependency insights +intro: You can allow all organization members to view dependency insights for your organization or limit viewing to organization owners. +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/changing-the-visibility-of-your-organizations-dependency-insights + - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default. + +Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing a policy on dependency insights in your enterprise account](/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. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**. ![Checkbox to allow members to view insights](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000..a10c0b1708 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,22 @@ +--- +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.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} +{% data reusables.organizations.settings-sidebar-actions %} +{% data reusables.github-actions.change-retention-period-for-artifacts-logs %} diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/ko-KR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000..134897705c --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -0,0 +1,33 @@ +--- +title: Converting an organization into a user +intro: 'It''s not possible to convert an organization into a personal user account, but you can create a new user account and transfer the organization''s repositories to it.' +redirect_from: + - /articles/converting-an-organization-into-a-user + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +1. [Sign up](/articles/signing-up-for-a-new-github-account) for a new GitHub user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. +5. [Delete the organization](/articles/deleting-an-organization-account). +6. [Rename the user](/articles/changing-your-github-username) to the organization's name. + +{% else %} + +1. Sign up for a new GitHub Enterprise user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. +5. [Delete the organization](/articles/deleting-an-organization-account). +6. [Rename the user](/articles/changing-your-github-username) to the organization's name. + +{% endif %} diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/ko-KR/content/organizations/managing-organization-settings/deleting-an-organization-account.md new file mode 100644 index 0000000000..9ab30b3656 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -0,0 +1,34 @@ +--- +title: Deleting an organization account +intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% 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 %}' +redirect_from: + - /articles/deleting-an-organization-account + - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content. + +{% endtip %} + +{% endif %} + +### 1. Back up your organization content + +Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. + +### 2. Delete the organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Near the bottom of the organization's settings page, click **Delete this Organization**. ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000..ba9aed9fc1 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,85 @@ +--- +title: Disabling or limiting GitHub Actions for your organization +intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### About {% data variables.product.prodname_actions %} permissions for your organization + +{% data reusables.github-actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." + +You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %} + +Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### Managing {% data variables.product.prodname_actions %} permissions for your organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Under **Local and third-party Actions**, select an option. ![Enable, disable, or limit actions for this organization](/assets/images/help/repository/enable-org-actions.png) +1. Click **Save**. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### Managing {% data variables.product.prodname_actions %} permissions for your organization + +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 %} + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Under **Policies**, select an option. ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png) +1. Click **Save**. + +### Allowing specific actions to run + +{% 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. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Click **Save**. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling workflows for private repository forks + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configuring the private fork policy for an organization + +{% 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/ko-KR/content/organizations/managing-organization-settings/index.md b/translations/ko-KR/content/organizations/managing-organization-settings/index.md new file mode 100644 index 0000000000..407237383f --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/index.md @@ -0,0 +1,39 @@ +--- +title: Managing organization settings +intro: 'Organization administrators can change several settings, including the names of repositories that belong to the organization and Owners team membership. In addition, organization admins can delete the organization and all of its repositories.' +redirect_from: + - /articles/managing-organization-settings + - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 /managing-the-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 %} diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/ko-KR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000..b030323d20 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,26 @@ +--- +title: Integrating Jira with your organization project board +intro: 'You can integrate Jira Cloud with your organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.' +redirect_from: + - /articles/integrating-jira-with-your-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. In the left sidebar under **Organization settings**, click the name of your organization. ![Sidebar organization name](/assets/images/help/settings/organization-settings-from-sidebar.png) +3. In the left sidebar under **Developer settings**, click **OAuth applications**. ![OAuth applications tab in the left sidebar](/assets/images/help/organizations/org-oauth-applications-ghe.png) +4. Click **Register a new application**. +5. Under **Application name**, type "Jira". +6. Under **Homepage URL**, type the full URL to your Jira instance. +7. Under **Authorization callback URL**, type the full URL to your Jira instance. +8. Click **Register application**. ![Register application button](/assets/images/help/oauth/register-application-button.png) +9. Under **Organization owned applications**, note the "Client ID" and "Client Secret" values. ![Client ID and Client Secret](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### 더 읽을거리 + +- ["Integrating Jira with your personal projects"](/articles/integrating-jira-with-your-personal-projects) +- Connect Jira Cloud to GitHub (Atlassian documentation) diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..091dc044ff --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,67 @@ +--- +title: Managing default labels for repositories in your organization +intro: You can customize the labels that are included in every new repository in your organization. +redirect_from: + - /articles/managing-default-labels-for-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage default labels for repositories in the organization. + +Default labels are included in every new repository in your organization, but anyone with write access to the repository can edit or delete the labels in that repository later. Adding, editing, or deleting a default label does not add, edit, or delete the label from existing repositories. + +### Creating a default label + +{% 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. Under "Repository labels", click **New label**. ![New label button](/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 %} + +### Editing a default label + +{% 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 %} + +### Deleting a default label + +{% 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 %} + +### 더 읽을거리 + +- "[About labels](/articles/about-labels)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..d4f133241b --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,30 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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. Click **Save**. !["Save" button for discussions settings](/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)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000..2cc24d79d5 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,66 @@ +--- +title: Managing scheduled reminders for your organization +intro: You can get reminders in Slack for all pull requests that teams in your organization have been requested to review. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About scheduled reminders for pull requests + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Organization owners can schedule a reminder for one or more teams in their organization, for all pull requests the team or teams have been requested to review. + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Creating a scheduled reminder for an organization +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Scheduled reminders button](/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. Under "Filter by team assigned to review code", click the **Add a team** dropdown and choose one or more teams. You can add up to 100 teams. If the team you select doesn't have access to the "Tracked repositories" selected above, you won't be able to create the scheduled reminder. ![Add a team dropdown](/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 %} + +### Managing a scheduled reminder for an organization +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Deleting a scheduled reminder for an organization +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.delete %} + +### 더 읽을거리 + +- "[Managing your scheduled reminders](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" +- "[Managing scheduled reminders for your team](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..9713588602 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Managing the default branch name for repositories in your organization +intro: 'You can set the default branch name for repositories that members create in your organization.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +permissions: Managing the default branch name for your repositories +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +### About the default branch name + +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. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization 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 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)." + +### Setting the default branch name + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. Under "Repository default branch", click **Change default branch name now**. ![Override button](/assets/images/help/organizations/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png) +5. Click **Update**. ![Update button](/assets/images/help/organizations/repo-default-name-update.png) + +### 더 읽을거리 + +- /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000..625d7c1471 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,28 @@ +--- +title: Managing the display of member names in your organization +intro: You can allow members of your organization to see a comment author's profile name in private repositories in the organization. +product: '{% data reusables.gated-features.display-names %}' +redirect_from: + - /articles/managing-the-display-of-member-names-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage the display of member names in an organization. + +![Commenter's profile name displayed in comment](/assets/images/help/issues/commenter-full-name.png) + +Each organization member chooses their own profile name in their settings. For more information, see "[Personalizing your profile](/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. Under "Admin repository permissions", select or unselect **Allow members to see comment author's profile name in private repositories**. ![Checkbox to allow members to see comment author's full name in private repositories](/assets/images/help/organizations/allow-members-to-view-full-names.png) +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000..929e867288 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Managing the forking policy for your organization +intro: 'You can can allow or prevent the forking of any private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories owned by your organization.' +redirect_from: + - /articles/allowing-people-to-fork-private-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization +permissions: Organization owners can manage the forking policy for an organization. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +By default, new organizations are configured to disallow the forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories. + +If you allow forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." + +{% data reusables.organizations.internal-repos-enterprise %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository forking", select **Allow forking of private repositories** or **Allow forking of private and internal repositories**. ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png) +6. Click **Save**. + +### 더 읽을거리 + +- "[About forks](/articles/about-forks)" +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..88fdb4c460 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-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 %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Click **Save**. + +### 더 읽을거리 + +- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ko-KR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..f659cf43cf --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,28 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +topics: + - organizations + - teams +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +The developers and organizations that your organization sponsors can send you updates about their work. You can manage the email address that receives these updates. + +You can also disable updates from accounts your organization sponsors. For more information, see "[Managing your sponsorship](/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. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. Click **Update profile**. ![Update profile button](/assets/images/help/organizations/update-profile-button.png) + +### 더 읽을거리 + +- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/renaming-an-organization.md new file mode 100644 index 0000000000..1b457fc4c5 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -0,0 +1,50 @@ +--- +title: Renaming an organization +intro: 'If your project or company has changed names, you can update the name of your organization to match.' +redirect_from: + - /articles/what-happens-when-i-change-my-organization-s-name/ + - /articles/renaming-an-organization + - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Tip:** Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +### What happens when I change my organization's name? + +After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect. + +#### Changes that occur automatically + +- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories. Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change. +- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +- Previous Git commits will also be correctly attributed to users within your organization. + +#### Changes that aren't automatic + +After changing your organization's name: +- Links to your previous organization profile page, such as `https://{% data variables.command_line.backticks %}/previousorgname`, will return a 404 error. 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 %}. +- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests. +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} + +### Changing your organization's name + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Near the bottom of the settings page, under "Rename organization", click **Rename Organization**. ![Rename organization button](/assets/images/help/settings/settings-rename-organization.png) + +### 더 읽을거리 + +* "[Why are my commits linked to the wrong user?](/articles/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000..f004cf1151 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,35 @@ +--- +title: Restricting repository creation in your organization +intro: 'To protect your organization''s data, you can configure permissions for creating repositories in your organization.' +redirect_from: + - /articles/restricting-repository-creation-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +You can choose whether members can create repositories in your organization. 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)." + +Organization owners can always create any type of repository. + +{% 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 %} + +{% warning %} + +**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/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. Under "Repository creation", select one or more options. ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..45fc59cefc --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Restricting repository visibility changes in your organization +intro: 'To protect your organization''s data, you can configure permissions for changing repository visibility in your organization.' +redirect_from: + - /articles/restricting-repository-visibility-changes-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +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 %} + +**Warning**: If enabled, this setting allows people with admin permissions to change an existing repository to any visibility, even if you do not allow that type of repository to be created. For more information about restricting the visibility of repositories during creation, see "[Restricting repository creation in your organization](/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. Under "Repository visibility change", deselect **Allow members to change repository visibilities for this organization**. ![Checkbox to allow members to change repository visibility](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) +6. Click **Save**. + +### 더 읽을거리 + +- "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000..acec392575 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,28 @@ +--- +title: Setting permissions for adding outside collaborators +intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.' +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners, and members with admin privileges for a repository, can invite outside collaborators to work on the repository. You can also restrict outside collaborator invite permissions to only organization owners. + +{% 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. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %} +![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %} +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000..9db1d155b8 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,24 @@ +--- +title: Setting permissions for deleting or transferring repositories +intro: 'You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.' +redirect_from: + - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ + - /articles/setting-permissions-for-deleting-or-transferring-repositories + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Owners can set permissions for deleting or transferring repositories in an organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository deletion and transfer", select or deselect **Allow members to delete or transfer repositories for this organization**. ![Checkbox to allow members to delete repositories](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000..c641903238 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Setting team creation permissions in your organization +intro: You can allow all organization members to create teams or limit team creation to organization owners. +redirect_from: + - /articles/setting-team-creation-permissions-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can set team creation permissions. + +If you do not set team creation permissions, all organization members will be able to create teams by default. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Team creation rules", select or deselect **Allow members to create teams**. ![Checkbox to allow members to create teams](/assets/images/help/organizations/allow-members-to-create-teams.png) +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/ko-KR/content/organizations/managing-organization-settings/transferring-organization-ownership.md new file mode 100644 index 0000000000..36919bf9d1 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -0,0 +1,29 @@ +--- +title: 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.' +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership + - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +1. If you're the only member with *owner* privileges, give another organization member the owner role. For more information, see "[Appointing an organization owner](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)." +2. Contact the new owner and make sure he or she is able to [access the organization's settings](/articles/accessing-your-organization-s-settings). +{% if currentVersion == "free-pro-team@latest" %} +3. If you are currently responsible for paying for GitHub in your organization, you'll also need to have the new owner or a [billing manager](/articles/adding-a-billing-manager-to-your-organization/) update the organization's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)." + + {% warning %} + + **Warning**: Removing yourself from the organization **does not** update the billing information on file for the organization account. The new owner or a billing manager must update the billing information on file to remove your credit card or PayPal information. + + {% endwarning %} + +{% endif %} +4. [Remove yourself](/articles/removing-yourself-from-an-organization) from the organization. diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/ko-KR/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000..fae8f49e93 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,24 @@ +--- +title: Upgrading to the Corporate Terms of Service +intro: Organizations can upgrade from the Standard Terms of Service to the Corporate Terms of Service. +redirect_from: + - /articles/upgrading-to-the-corporate-terms-of-service + - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +The Standard Terms of Service is an agreement between {% data variables.product.prodname_dotcom %} and you as an individual. To enter into an agreement with {% data variables.product.prodname_dotcom %} on behalf of an entity, such as a company, non-profit, or group, organization owners can upgrade to the Corporate Terms of Service. + +1. Contact {% data variables.contact.contact_support %} to request an upgrade to the Corporate Terms of Service. They will enable a banner on your organization's dashboard that will allow you to accept the Corporate Terms of Service. +{% data reusables.dashboard.access-org-dashboard %} +3. At the top of the page, to the right of the Terms of Service banner, click **Sign now**. ![Sign now button](/assets/images/help/organizations/sign-now-button.png) +4. Read the information about the Corporate Terms of Service, then select **Yes, I want to sign these terms on behalf of my business.** ![Check box to sign on behalf of your business](/assets/images/help/organizations/sign-on-behalf-business.png) +5. Type the name of the company, non-profit, or group that owns the organization account. This is the entity that will enter into an agreement with {% data variables.product.prodname_dotcom %}. ![Business name field](/assets/images/help/organizations/business-name-field.png) +6. To agree to the Corporate Terms of Service on behalf of your entity, click **Accept terms**. ![Accept terms button](/assets/images/help/organizations/accept-terms-button.png) + +### 더 읽을거리 +- "[GitHub Corporate Terms of Service](/articles/github-corporate-terms-of-service/)" diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md b/translations/ko-KR/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md new file mode 100644 index 0000000000..995e8278ef --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md @@ -0,0 +1,42 @@ +--- +title: Verifying your organization's domain +intro: 'You can verify the domains controlled by your organization to confirm your organization''s identity on {% data variables.product.product_name %}.' +redirect_from: + - /articles/verifying-your-organization-s-domain + - /articles/verifying-your-organizations-domain + - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About domain verification + +To verify domains on {% data variables.product.product_name %}, you must have owner permissions in the organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." You will also need access to modify domain records with your domain hosting service. + +After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "[Upgrading to the Corporate Terms of Service](/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)." + +{% data reusables.organizations.verified-domains-details %} + +On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications to an approved domain](/articles/restricting-email-notifications-to-an-approved-domain)." + +### Verifying your organization's domain + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +5. Click **Add a domain**. ![Add a domain button](/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. You should see your new TXT record listed in the command output. + ```shell + $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT + ``` +8. After confirming your TXT record is added to your DNS, navigate to the Verified domains tab in your organization's settings. You can follow steps one through four above to locate the Verified domains tab. ![Verified domains settings page with pending domain](/assets/images/help/organizations/pending-domain-verification.png) +{% data reusables.organizations.continue-verifying-domain %} +11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service. ![Verified badge](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000..ab0b67ba16 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,57 @@ +--- +title: Adding a billing manager to your organization +intro: 'A *billing manager* is a user who manages the billing settings for your organization, such as updating payment information. This is a great option if regular members of your organization don''t typically have access to billing resources.' +redirect_from: + - /articles/adding-a-billing-manager-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - 결제 +--- + +Members of your organization's Owners team can give *billing manager* permissions to people. Once a person accepts their invitation to become a billing manager for your organization, they can invite additional people to be billing managers. + +{% note %} + +**Note:** Billing managers do not use paid licenses in your organization's subscription. + +{% endnote %} + +### Permissions for billing managers + +Billing managers can: + +- Upgrade or downgrade the account +- Add, update, or remove payment methods +- View payment history +- Download receipts +- View, invite, and remove billing managers + +In addition, all billing managers will receive billing receipts by email on the organization's billing date. + +Billing managers **are not** able to: + +- Create or access repositories in your organizations +- See private members of your organization +- Be seen in the list of organization members +- Purchase, edit, or cancel subscriptions for {% data variables.product.prodname_marketplace %} apps + +{% tip %} + +**Tip:** If your organization [requires members, billing managers, and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), the user must enable two-factor authentication before they can accept your invitation to become a billing manager for the organization. + +{% endtip %} + +### Inviting a billing manager + +The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a GitHub account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Next to Billing managers, click **Add a billing manager**. ![Invite billing manager](/assets/images/help/billing/settings_billing_managers_list.png) +6. Type the username or email address of the person you want to add and click **Send invitation**. ![Invite billing manager page](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000..481560522e --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,29 @@ +--- +title: Giving "team maintainer" permissions to an organization member +intro: 'An organization owner can promote any member of the organization to *team maintainer* for a team, giving them a subset of privileges available to organization owners.' +redirect_from: + - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ + - /articles/giving-team-maintainer-permissions-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team_maintainers_can %} + +### Promoting an organization member to team maintainer + +Before promoting an organization member to team maintainer, the person must already be a member of the team. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +4. Select the person or people you'd like to promote to team maintainer. ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png) +5. Above the list of team members, use the drop-down menu and click **Change role...**. ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png) +6. Select a new role and click **Change role**. ![Radio buttons for Maintainer or Member roles](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md new file mode 100644 index 0000000000..a6fedeb7bc --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -0,0 +1,21 @@ +--- +title: Managing people's access to your organization with roles +intro: 'A person''s role in your organization defines their level of access to your organization, its settings, and your data. You can make people owners, members, or billing managers for your organization, or you can give them team maintainer permissions.' +redirect_from: + - /articles/managing-people-s-access-to-your-organization-with-roles + - /articles/managing-peoples-access-to-your-organization-with-roles + - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000..07a0373218 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Maintaining ownership continuity for your organization +intro: Organizations can have more than one organization owner to avoid lapses in ownership. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization +permissions: Organization owners can promote any member of an organization to an organization owner. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### About maintaining ownership continuity for your organization + +{% data reusables.organizations.org-ownership-recommendation %} + +Organization owners have full administrative access to the organization. {% data reusables.organizations.new-org-permissions-more-info %} + +### Appointing an organization owner + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Select the person or people you'd like to promote to owner. ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Above the list of members, use the drop-down menu and click **Change role**. ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png) +6. Select a new role for the person or people, then click **Change role**. ![Radio buttons with owner and member roles and Change role button](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md new file mode 100644 index 0000000000..d43f7d4192 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -0,0 +1,147 @@ +--- +title: Permission levels for an organization +intro: 'After you [create an organization](/articles/creating-a-new-organization-account), you should give Owner permissions to a small group of people who will manage the organization account.' +redirect_from: + - /articles/permission-levels-for-an-organization-early-access-program/ + - /articles/permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Permission levels for an organization + +Organization members can have *owner*{% if currentVersion == "free-pro-team@latest" %}, *billing manager*,{% endif %} or *member* roles: + +- **Owners** have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." +{% if currentVersion == "free-pro-team@latest" %} +- **Billing managers** allow a person to manage billing settings. For more information, see "[Adding a billing manager to your organization](/articles/adding-a-billing-manager-to-your-organization)". +{% endif %} +- **Members** are the default role for everyone else. + +{% if currentVersion == "free-pro-team@latest" %} + + +| Organization action | Owners | Members | Billing managers | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:-------:|:----------------:| +| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** | | +| View and edit billing information | **X** | | **X** | +| Invite people to join the organization | **X** | | | +| Edit and cancel invitations to join the organization | **X** | | | +| Remove members from the organization | **X** | | | +| Reinstate former members to the organization | **X** | | | +| Add and remove people from **all teams** | **X** | | | +| Promote organization members to *team maintainer* | **X** | | | +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | +| Add collaborators to **all repositories** | **X** | | | +| Access the organization audit log | **X** | | | +| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" for details) | **X** | | | +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | | +| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | +| Delete **all teams** | **X** | | | +| Delete the organization account, including all repositories | **X** | | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | | +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | +| See all organization members and teams | **X** | **X** | | +| @mention any visible team | **X** | **X** | | +| Can be made a *team maintainer* | **X** | **X** | | +| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **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](/organizations/managing-organization-settings/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** | | | +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | +| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | +| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | +| [Manage a user's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | | +| Transfer repositories | **X** | | | +| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | | +| List apps in {% data variables.product.prodname_marketplace %} | **X** | | | +| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **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** | | | +| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | +| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** | | | + +{% else %} + + +| Organization action | Owners | Members | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------------------------------------------------------------------------------------------------:| +| Invite people to join the organization | **X** | | +| Edit and cancel invitations to join the organization | **X** | | +| Remove members from the organization | **X** | | | +| Reinstate former members to the organization | **X** | | | +| Add and remove people from **all teams** | **X** | | +| Promote organization members to *team maintainer* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Add collaborators to **all repositories** | **X** | | +| Access the organization audit log | **X** | | +| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" for details) | **X** | | | +| Delete **all teams** | **X** | | +| Delete the organization account, including all repositories | **X** | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | +| See all organization members and teams | **X** | **X** | +| @mention any visible team | **X** | **X** | +| Can be made a *team maintainer* | **X** | **X** | +| Transfer repositories | **X** | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | +{% endif %} +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Export a list of people with access to an organization repository](/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" %} +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | +{% endif %} +{% if currentVersion == "github-ae@latest" %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} + +{% endif %} + +### {% data variables.product.prodname_github_app %} managers + +By default, only organization owners can manage the settings of {% data variables.product.prodname_github_app %}s owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_app %}s owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions. + +When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_app %}s owned by the organization. For more information, see: + +- "[Adding GitHub App managers in your organization](/articles/adding-github-app-managers-in-your-organization)" +- "[Removing GitHub App managers from your organization](/articles/removing-github-app-managers-from-your-organization)" + +### Outside collaborators + +To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %} + +### 더 읽을거리 + +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" +- "[About teams](/articles/about-teams)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000..ce02006dd9 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Removing a billing manager from your organization +intro: 'If a person with the *billing manager* role no longer needs to view or change your organization''s billing information, you can remove their access to the organization.' +redirect_from: + - /articles/removing-a-billing-manager-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - 결제 +--- + +{% warning %} + +**Note:** {% 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. In the Billing managers list, next to the name of the person you want to remove, click {% octicon "x" aria-label="X symbol" %}. ![Remove billing manager](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000..b190d38a4e --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,62 @@ +--- +title: About identity and access management with SAML single sign-on +intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% 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 + - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About SAML SSO + +{% data reusables.saml.dotcom-saml-explanation %} + +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. + +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 %} + +Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." + +For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." + +Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue. + +To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." + +The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's {% data variables.product.prodname_dotcom %} account, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[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)." + +If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +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 %} + +Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +### Adding members to an organization using SAML SSO + +After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." + +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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### 더 읽을거리 + +- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md new file mode 100644 index 0000000000..afa207f38c --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -0,0 +1,31 @@ +--- +title: About SCIM +intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-scim + - /github/setting-up-and-managing-organizations-and-teams/about-scim +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. + +If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. + +These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% data variables.product.product_name %} API documentation. +- 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)." + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)" +- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" +- "[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)" diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000..e626026611 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,31 @@ +--- +title: Accessing your organization if your identity provider is unavailable +intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/). + +{% note %} + +**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours. + +{% endnote %} + +1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on. ![Link to enter your recovery code](/assets/images/help/saml/saml_use_recovery_code.png) +2. In the "Recovery Code" field, type your recovery code. ![Field to enter your recovery code](/assets/images/help/saml/saml_recovery_code_entry.png) +3. Click **Verify**. ![Button to verify your recovery code](/assets/images/help/saml/saml_verify_recovery_codes.png) + +After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code. + +### 더 읽을거리 + +- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000..008cf8898a --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,81 @@ +--- +title: Configuring SAML single sign-on and SCIM using Okta +intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta +product: '{% data reusables.gated-features.saml-sso %}' +permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization. +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About SAML and SCIM with Okta + +You can control access to your {% data variables.product.prodname_dotcom %} organization and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP). + +SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your {% data variables.product.prodname_dotcom %} organization when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta. + +| Feature | 설명 | +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Push New Users | When you create a new user in Okta, the user will receive an email to join your {% data variables.product.prodname_dotcom %} organization. | +| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your {% data variables.product.prodname_dotcom %} organization. | +| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your {% data variables.product.prodname_dotcom %} organization. | +| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your {% data variables.product.prodname_dotcom %} organization. | + +### 빌드전 요구 사양 + +{% data reusables.saml.use-classic-ui %} + +### Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +4. To the right of "Github Enterprise Cloud - Organization", click **Add**. ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png) + +5. In the **GitHub Organization** field, type the name of your {% data variables.product.prodname_dotcom %} organization. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`. ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png) + +6. Click **Done**. + +### Enabling and testing SAML SSO + +{% 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. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)." + +### Configuring access provisioning with SCIM in 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. Click **Authenticate with Github Enterprise Cloud - Organization**. !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) + +7. To the right of your organization's name, click **Grant**. !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) + + {% note %} + + **Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." + + {% endnote %} +1. Click **Authorize OktaOAN**. !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} + +### 더 읽을거리 + +- "[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 your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000..2b53aee047 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Connecting your identity provider to your organization +intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/connecting-your-identity-provider-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Before [enabling SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) in your {% data variables.product.product_name %} organization, you'll need to connect your identity provider (IdP) to your organization. + +You can find the SAML and SCIM implementation details for your IdP in their documentation: +- 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) and [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) and [SCIM](http://developer.okta.com/standards/SCIM/) +- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [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 %} + +**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. For more information about SCIM, see "[About SCIM](/articles/about-scim)." + +{% endnote %} + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000..6e4c005b6b --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,36 @@ +--- +title: Downloading your organization's SAML single sign-on recovery codes +intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.' +redirect_from: + - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes + - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes + - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/). + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**. ![Link to view and save your recovery codes](/assets/images/help/saml/saml_recovery_codes.png) +6. Save your recovery codes by clicking **Download**, **Print**, or **Copy**. ![Buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png) + + {% note %} + + **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated. + + {% endnote %} + +7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on. + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..3178e32b47 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,51 @@ +--- +title: Enabling and testing SAML single sign-on for your organization +intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization. + +If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." + +{% data reusables.saml.outside-collaborators-exemption %} + +Prior to enforcing SAML SSO in your organization, ensure that you've set up your identity provider (IdP). For more information, see "[Preparing to enforce SAML single sign-on in your organization](/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. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/saml/saml_enable.png) + + {% note %} + + **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)." + + {% endnote %} + +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.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. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests. ![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 organization, 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) + + {% tip %} + + **Tip:** {% data reusables.saml.testing-saml-sso %} + + {% endtip %} +11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." ![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png) +12. Click **Save**. ![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png) + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..dc0d04b565 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Enforcing SAML single sign-on for your organization +intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enforcing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +If you enforce SAML SSO in your organization, any members, including admins who have not authenticated via your SAML identity provider (IdP), will be removed from the organization and will receive an email notifying them about the removal. Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed. For more information on bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)." You can restore organization members once they successfully complete single sign-on. + +If your organization is owned by an enterprise account, enabling SAML for the enterprise account will override your organization-level SAML configuration. 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)." + +{% tip %} + +**Tip:** {% data reusables.saml.testing-saml-sso %} + +{% endtip %} + +1. Enable and test SAML SSO for your organization. For more information on this process, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)." +2. After you select **Require SAML SSO authentication for all members of the SAML SSO Org organization**, organization members who haven't authenticated via your IdP will be shown. If you enforce SAML SSO, these members will be removed from the organization. +3. Click **Enforce SAML SSO** to enforce SAML SSO and remove the listed organization members. + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md new file mode 100644 index 0000000000..6dc52297a3 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -0,0 +1,24 @@ +--- +title: Managing SAML single sign-on for your organization +intro: Organization administrators can manage organization members' identities and access to the organization with SAML single sign-on (SSO). +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000..51361dedb7 --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,79 @@ +--- +title: Managing team synchronization for your organization +intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% 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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization +permissions: Organization owners can manage team synchronization for an organization. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### About team synchronization + +You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. + +{% 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 %} + +You can also enable team synchronization for organizations owned by 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 team synchronization + +The steps to enable team synchronization depend on the IdP you want to use. There are prerequisites to enable team synchronization that apply to every IdP. Each individual IdP has additional prerequisites. + +#### 빌드전 요구 사양 + +{% data reusables.identity-and-permissions.team-sync-required-permissions %} + +You must enable SAML single sign-on for your organization and your supported IdP. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." + +You must authenticate to your organization using SAML SSO and the supported IdP. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." + +#### Enabling team synchronization for 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. Review the identity provider tenant information you want to connect to your organization, 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) + +#### Enabling team synchronization for 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. Under your organization's name, type a valid SSWS token and the URL to your Okta instance. ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) +6. Review the identity provider tenant information you want to connect to your organization, then click **Create**. ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png) + +### Disabling team synchronization + +{% 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. Under "Team synchronization", click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000..6a4509e18e --- /dev/null +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Preparing to enforce SAML single sign-on in your organization +intro: 'Before you enforce SAML single sign-on in your organization, you should verify your organization''s membership and configure the connection settings to your identity provider.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +When you [enforce SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) in your organization, members that haven't authenticated via your identity provider (IdP) will be removed from the organization and will receive an email notifying them about the removal. + +Before enforcing SAML SSO in your organization, you should: + +- [Add](/articles/inviting-users-to-join-your-organization) or [remove](/articles/removing-a-member-from-your-organization) members from your organization if needed. +- If you haven't already, connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)." +- Ensure that your organization members have signed in and linked their accounts with the IdP. + +{% data reusables.saml.outside-collaborators-exemption %} + +### 더 읽을거리 + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..30f8dcea86 --- /dev/null +++ b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,32 @@ +--- +title: Converting an admin team to improved organization permissions +intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.' +redirect_from: + - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ + - /articles/converting-an-admin-team-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +You can remove the ability for members of legacy admin teams to create repositories by creating a new team for these members, ensuring that the team has necessary access to the organization's repositories, then deleting the legacy admin team. + +For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)." + +{% warning %} + +**Warnings:** +- If there are members of your legacy Admin team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories. +- To prevent the loss of private forks made by members of the legacy Admin team, you must follow steps 1-3 below before deleting the legacy Admin team. +- Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on. + +{% endwarning %} + +1. [Create a new team](/articles/creating-a-team). +2. [Add each of the members](/articles/adding-organization-members-to-a-team) of your legacy admin team to the new team. +3. [Give the new team equivalent access](/articles/managing-team-access-to-an-organization-repository) to each of the repositories the legacy team could access. +4. [Delete the legacy admin team](/articles/deleting-a-team). diff --git a/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..e0ea5adcb5 --- /dev/null +++ b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,52 @@ +--- +title: Converting an Owners team to improved organization permissions +intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. The "Owner" is now an administrative role given to individual members of your organization. Members of your legacy Owners team are automatically given owner privileges.' +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +You have a few options to convert your legacy Owners team: + +- Give the team a new name that denotes the members have a special status in the organization. +- Delete the team after ensuring all members have been added to teams that grant necessary access to the organization's repositories. + +### Give the Owners team a new name + +{% tip %} + + **Note:** Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. In the team name field, choose a new name for the Owners team. 예시: + - If very few members of your organization were members of the Owners team, you might name the team "Core". + - If all members of your organization were members of the Owners team so that they could [@mention teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), you might name the team "Employees". ![The team name field, with the Owners team renamed to Core](/assets/images/help/teams/owners-team-new-name.png) +6. Under the team description, click **Save and continue**. ![The Save and continue button](/assets/images/help/teams/owners-team-save-and-continue.png) +7. Optionally, [make the team *public*](/articles/changing-team-visibility). + +### Delete the legacy Owners team + +{% warning %} + +**Warning:** If there are members of your Owners team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. At the bottom of the page, review the warning and click **Delete the Owners team**. ![Link for deleting the Owners team](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/index.md new file mode 100644 index 0000000000..5a0539da2a --- /dev/null +++ b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/index.md @@ -0,0 +1,20 @@ +--- +title: Migrating to improved organization permissions +intro: 'If your organization was created after September 2015, your organization includes improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved organization permissions model.' +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000..fd5c3fb2f1 --- /dev/null +++ b/translations/ko-KR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,44 @@ +--- +title: Migrating admin teams to improved organization permissions +intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.' +redirect_from: + - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ + - /articles/migrating-admin-teams-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +By default, all organization members can create repositories. If you restrict [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) to organization owners, and your organization was created under the legacy organization permissions structure, members of legacy admin teams will still be able to create repositories. + +Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure. + +You can remove this ability by migrating your legacy admin teams to the improved organization permissions. + +For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." + +{% warning %} + +**Warning:** If your organization has disabled [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories. + +{% endwarning %} + +### Migrating all of your organization's legacy admin teams + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +1. Review your organization's legacy admin teams, then click **Migrate all teams**. ![Migrate all teams button](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) +1. Read the information about possible permissions changes for members of these teams, then click **Migrate all teams.** ![Confirm migration button](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) + +### Migrating a single admin team + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +1. In the team description box, click **Migrate team**. ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/about-teams.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/about-teams.md new file mode 100644 index 0000000000..0f68e3e886 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/about-teams.md @@ -0,0 +1,79 @@ +--- +title: About teams +intro: Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions. +redirect_from: + - /articles/about-teams + - /github/setting-up-and-managing-organizations-and-teams/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +![List of teams in an organization](/assets/images/help/teams/org-list-of-teams.png) + +Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file. + +For more information, see: +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" +- "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" +- "[About code owners](/articles/about-code-owners/)" + +![Image of a team mention](/assets/images/help/teams/team-mention.png) + +{% if enterpriseServerVersions contains currentVersion %} + +You can also use LDAP Sync to synchronize {% data variables.product.product_location %} team members and team roles against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.product_location %}. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)." + +{% endif %} + +{% data reusables.organizations.team-synchronization %} + +### Team visibility + +{% data reusables.organizations.types-of-team-visibility %} + +### Team pages + +Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page. + +Organization members can create and participate in discussions with the team. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." + +![Team page listing team members and discussions](/assets/images/help/organizations/team-page-discussions-tab.png) + +### Nested teams + +You can reflect your group or company's hierarchy within your {% data variables.product.product_name %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. + +Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people. + +For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification. + +![Teams page with a parent team and child teams](/assets/images/help/teams/nested-teams-eng-example.png) + +To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team. + +![Parent team page with all members of child teams](/assets/images/help/teams/team-and-subteam-members.png) + +You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)." + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +### Preparing to nest teams in your organization + +If your organization already has existing teams, you should audit each team's repository access permissions before you nest teams above or below it. You should also consider the new structure you'd like to implement for your organization. + +At the top of the team hierarchy, you should give parent teams repository access permissions that are safe for every member of the parent team and its child teams. As you move toward the bottom of the hierarchy, you can grant child teams additional, more granular access to more sensitive repositories. + +1. Remove all members from existing teams +2. Audit and adjust each team's repository access permissions and give each team a parent +3. Create any new teams you'd like to, choose a parent for each new team, and give them repository access +4. Add people directly to teams + +### 더 읽을거리 + +- "[Creating a team](/articles/creating-a-team)" +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000..e44aef4ffe --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,32 @@ +--- +title: Adding organization members to a team +intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% if currentVersion == "free-pro-team@latest" %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.' +redirect_from: + - /articles/adding-organization-members-to-a-team-early-access-program/ + - /articles/adding-organization-members-to-a-team + - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. Above the list of team members, click **Add a member**. ![Add member button](/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 %} + +### 더 읽을거리 + +- "[About teams](/articles/about-teams)" +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/changing-team-visibility.md new file mode 100644 index 0000000000..d8450c6b27 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/changing-team-visibility.md @@ -0,0 +1,29 @@ +--- +title: Changing team visibility +intro: Team maintainers and organization owners can determine whether a team is *visible* or *secret*. +redirect_from: + - /articles/changing-team-visibility + - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.types-of-team-visibility %} + +{% tip %} + +**Tip:** If a team has [child or parent teams](/articles/about-teams), you cannot make it a secret team. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +3. Select the team or teams whose visibility you'd like to change. ![List of teams with two teams selected](/assets/images/help/teams/list-of-teams-selected.png) +4. Above the list of teams, use the drop-down menu and click **Change visibility**. ![Drop-down menu with option to change team visibility](/assets/images/help/teams/team-bulk-management-options.png) +5. Choose whether to make the team or teams visible or secret, then click **Change visibility**. ![Radio buttons for making a team visible or secret and Change visibility button](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/creating-a-team.md new file mode 100644 index 0000000000..03648ddbd4 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -0,0 +1,38 @@ +--- +title: Creating a team +intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people. +redirect_from: + - /articles/creating-a-team-early-access-program/ + - /articles/creating-a-team + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/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. Optionally, if your organization or enterprise account uses team synchronization, to connect an identity provider group to your team, use the "Identity Provider Groups" drop-down menu, and select up to 5 identity provider groups. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +{% endif %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} +9. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository). + +### 더 읽을거리 + +- "[About teams](/articles/about-teams)" +- "[Changing team visibility](/articles/changing-team-visibility)" +- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/deleting-a-team.md new file mode 100644 index 0000000000..8dcd1238cb --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/deleting-a-team.md @@ -0,0 +1,27 @@ +--- +title: Deleting a team +intro: Organization owners can delete teams at any time from the team's settings page. +redirect_from: + - /articles/deleting-a-team + - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Tip:** Only organization owners can delete parent teams. For more information, see "[About teams](/articles/about-teams)." + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Select the team or teams you'd like to delete. ![List of teams with two teams selected](/assets/images/help/teams/list-of-teams-selected.png) +5. Above the list of teams, use the drop-down menu and click **Delete**. ![Drop-down menu with option to change team visibility](/assets/images/help/teams/team-bulk-management-options.png) +6. Review the team or teams that will be deleted, then click **I understand, delete teams**. ![List of teams that will be deleted and Delete teams button](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000..bef774e006 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Disabling team discussions for your organization +intro: Organization owners can choose to disable or enable team discussions across the organization. +redirect_from: + - /articles/disabling-team-discussions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team-discussions-default %} For more information on team discussions, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +5. Under "Team discussions", unselect **Enable team discussions for this organization**. ![Checkbox to enable or disable team discussions for an organization](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) +6. Click **Save**. diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/index.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/index.md new file mode 100644 index 0000000000..0efd481006 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/index.md @@ -0,0 +1,38 @@ +--- +title: Organizing members into teams +intro: You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions. +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 + - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000..7bb33d871c --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,51 @@ +--- +title: Managing code review assignment for your team +intro: Code review assignments clearly indicate which members of a team are expected to submit a review for a pull request. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +Team maintainers and organization owners can configure code review assignments. + +### About code review assignments + +By using code review assignments, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. Code review assignments allow you to decide whether the whole team or just a subset of team members are notified when a team is requested for review. + +When code owners are automatically requested for review, the team is still removed and replaced with individuals. The individual approvals don't satisfy the requirement for code owner approval in a protected branch. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." + +### Routing algorithms + +Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. + +The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. + +The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period. + +### Configuring code review assignment +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. In the left sidebar, click **Code review assignment** ![Code review assignment button](/assets/images/help/teams/review-assignment-button.png) +6. Select **Enable auto assignment**. ![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png) +7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request. ![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png) +8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)." ![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png) +9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip. ![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png) +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png) +11. Click **Save changes**. + +### Disabling code review assignment +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Select **Enable auto assignment** to remove the checkmark. ![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png) +6. Click **Save changes**. diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000..f528b24234 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,69 @@ +--- +title: Managing scheduled reminders for your team +intro: You can get reminders in Slack when your team has pull requests waiting for review. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About scheduled reminders for teams + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Team maintainers and organization owners can set scheduled reminders for any pull requests that a team has been requested to review. Before you can create a scheduled reminder for your team, an organization owner must authorize your Slack workspace. For more information, see "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)." + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Creating a scheduled reminder for a team +{% 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 %} +![Scheduled reminders button](/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 %} + +### Managing a scheduled reminder for a team +{% 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 %} +![Scheduled reminders button](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Deleting a scheduled reminder for a team +{% 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 %} +![Scheduled reminders button](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.delete %} + +### 더 읽을거리 + +- "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- "[Managing your scheduled reminders](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000..8fd51ec39d --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,42 @@ +--- +title: Moving a team in your organization’s hierarchy +intro: 'Team maintainers and organization owners can nest a team under a parent team, or change or remove a nested team''s parent.' +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 + - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can change the parent of any team. Team maintainers can change a team's parent if they are maintainers in both the child team and the parent team. Team maintainers without maintainer permissions in the child team can request to add a parent or child team. For more information, see "[Requesting to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)" and "[Requesting to add a child team](/articles/requesting-to-add-a-child-team)." + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% tip %} + +**팁:** +- You cannot change a team's parent to a secret team. For more information, see "[About teams](/articles/about-teams)." +- You cannot nest a parent team beneath one of its child teams. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. In the list of teams, click the name of the team whose parent you'd like to change. ![List of the organization's teams](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Use the drop-down menu to choose a parent team, or to remove an existing parent, select **Clear selected value**. ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png) +7. Click **Update**. +{% data reusables.repositories.changed-repository-access-permissions %} +9. Click **Confirm new parent team**. ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png) + +### 더 읽을거리 + +- "[About teams](/articles/about-teams)" diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000..9af60f3276 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,23 @@ +--- +title: Removing organization members from a team +intro: 'People with *owner* or *team maintainer* permissions can remove team members from a team. This may be necessary if a person no longer needs access to a repository the team grants, or if a person is no longer focused on a team''s projects.' +redirect_from: + - /articles/removing-organization-members-from-a-team-early-access-program/ + - /articles/removing-organization-members-from-a-team + - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. Select the person or people you'd like to remove. ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png) +5. Above the list of team members, use the drop-down menu and click **Remove from team**. ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/renaming-a-team.md new file mode 100644 index 0000000000..b62593f46d --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/renaming-a-team.md @@ -0,0 +1,21 @@ +--- +title: Renaming a team +intro: Team maintainers and organization owners can edit the name and description of a team. +redirect_from: + - /articles/renaming-a-team + - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Type a new name or description for the team. ![Fields for team name and description](/assets/images/help/teams/team-name-description.png) +6. Click **Update**. diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000..a3c3a9ba44 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,36 @@ +--- +title: Requesting to add a child team +intro: 'If you have maintainer permissions in a team, you can request to nest an existing team under your team in your organization’s hierarchy.' +redirect_from: + - /articles/requesting-to-add-a-child-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +When you request to add a team as a child, a request is sent to the maintainers of the child team. Once a maintainer of the child team approves your request, the child team is nested under the parent team in your organization's hierarchy. + +If you're an organization owner or you have team maintainer permissions in both the child team and the parent team, you can add the child team without requesting approval or change the child team's parent from the child team's settings page. For more information, see "[Moving a team in your organization's hierarchy](/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. In the list of teams, click the name of the team where you'd like to add the child team. ![List of the organization's teams](/assets/images/help/teams/click-team-name.png) +5. At the top of the team page, click {% octicon "people" aria-label="The people icon" %} **Teams**. ![Teams tab on a team page](/assets/images/help/teams/team-teams-tab.png) +6. Click **Add a team**. ![Add a team button on a team page](/assets/images/help/teams/add-a-team.png) +7. Type the name of the team you'd like to add as a child team, and select it from the drop-down list. ![Text box to type and drop-down menu to select the name of the child team](/assets/images/help/teams/type-child-team-name.png) +{% data reusables.repositories.changed-repository-access-permissions %} +9. Click **Confirm changes** to send a request to add the child team. ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png) + +### 더 읽을거리 + +- "[About teams](/articles/about-teams)" +- "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Requesting to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)" diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000..2f49c9fc12 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,36 @@ +--- +title: Requesting to add or change a parent team +intro: 'If you have maintainer permissions in a team, you can request to nest your team under a parent team in your organization''s hierarchy.' +redirect_from: + - /articles/requesting-to-add-or-change-a-parent-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +When you request to add or change your team's parent, a request is sent to the maintainers of the parent team. When a maintainer of the new parent team approves your request, your team is nested as a child team under the parent team in your organization's hierarchy. + +If you're an organization owner or you have team maintainer permissions in the child team and the parent team, you can add the parent team without requesting approval or change your team's parent from your team's settings page. For more information, see "[Moving a team in your organization's hierarchy](/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. In the list of teams, click the name of the team you'd like to nest under a parent. ![List of the organization's teams](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Under "Parent team", use the "Select parent team" drop-down menu and click the name of the new parent team. ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png) +7. Click **Save changes**. +{% data reusables.repositories.changed-repository-access-permissions %} +9. Click **Confirm changes** to send a request to add or change your team's parent. ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png) + +### 더 읽을거리 + +- "[About teams](/articles/about-teams)" +- "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Requesting to add a child team](/articles/requesting-to-add-a-child-team)" diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000..03cac455eb --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,24 @@ +--- +title: Setting your team's profile picture +intro: 'Team maintainers and organization owners can set a profile picture for a team, which is displayed on the team''s page.' +redirect_from: + - /articles/setting-your-team-s-profile-picture + - /articles/setting-your-teams-profile-picture + - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Unless you set a profile picture for a team, the team profile picture will match the organization's profile picture. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Click **Upload new picture** and select your desired profile picture. ![Upload new picture](/assets/images/help/teams/org-team-profile-picture-upload.png) +6. Click and drag to crop the image as needed, then click **Set new team avatar**. ![Set new team avatar](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000..b28ee589e3 --- /dev/null +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,99 @@ +--- +title: Synchronizing a team with an identity provider group +intro: 'You can synchronize a {% data variables.product.product_name %} team with an identity provider (IdP) group to automatically add and remove team members.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group +product: '{% data reusables.gated-features.team-synchronization %}' +permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### About team synchronization + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% if currentVersion == "free-pro-team@latest" %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif currentVersion == "github-ae@latest" %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. + +{% if currentVersion == "free-pro-team@latest" %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} + +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 %}{% if currentVersion == "free-pro-team@latest" %} or using the API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} +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)." +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs. +{% endif %} + +Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)." + +To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." + +{% if currentVersion == "free-pro-team@latest" %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Requirements for members of synchronized teams + +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.product_name %} only if: +- The person is a member of the organization on {% data variables.product.product_name %}. +- The person has already logged in with their user account on {% data variables.product.product_name %} 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.product_name %} 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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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)" 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 "[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)." + +{% endif %} + +### 빌드전 요구 사양 + +{% if currentVersion == "free-pro-team@latest" %} +Before you can connect a {% data variables.product.product_name %} 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](/organizations/managing-saml-single-sign-on-for-your-organization/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. + +You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." + +{% elsif currentVersion == "github-ae@latest" %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." + +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. For more information, see [Configure automatic user provisioning to GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) in the Microsoft Docs. +{% endif %} + +### Connecting an IdP group to a team + +When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% if currentVersion == "github-ae@latest" %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. Click **Save changes**. + +### Disconnecting an IdP group from a team + +If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% if currentVersion == "github-ae@latest" %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Click **Save changes**. diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000..0fea6c2efd --- /dev/null +++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -0,0 +1,60 @@ +--- +title: About OAuth App access restrictions +intro: 'Organizations can choose which {% data variables.product.prodname_oauth_app %}s have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.' +redirect_from: + - /articles/about-third-party-application-restrictions/ + - /articles/about-oauth-app-access-restrictions + - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_app %}s they'd like to use, and organization owners receive a notification of pending requests. + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% tip %} + +**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources. + +{% endtip %} + +### Setting up {% data variables.product.prodname_oauth_app %} access restrictions + +When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time: + +- **Applications that are owned by the organization** are automatically given access to the organization's resources. +- **{% data variables.product.prodname_oauth_app %}s** immediately lose access to the organization's resources. +- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys). +- **SSH keys created by {% data variables.product.prodname_oauth_app %}s during or after February 2014** immediately lose access to the organization's resources. +- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_app %}s. +- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_app %}s. In addition, there are no privileged create, update, or delete actions on public organization resources. +- **Hooks created by users and hooks created before May 2014** will not be affected. +- **Private forks of organization-owned repositories** are subject to the organization's access restrictions. + +### Resolving SSH access failures + +When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place. + +### Webhooks + +When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching. + +When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted). + +### Re-enabling access restrictions + +If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources. + +### 더 읽을거리 + +- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" +- "[Approving {% data variables.product.prodname_oauth_app %}s for your organization](/articles/approving-oauth-apps-for-your-organization)" +- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)" +- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" +- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" +- "[Requesting organization approval for {% data variables.product.prodname_oauth_app %}s](/articles/requesting-organization-approval-for-oauth-apps)" +- "[Authorizing {% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps)" diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000..b97c4983a3 --- /dev/null +++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Approving OAuth Apps for your organization +intro: 'When an organization member requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.' +redirect_from: + - /articles/approving-third-party-applications-for-your-organization/ + - /articles/approving-oauth-apps-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members must [request approval](/articles/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Next to the application you'd like to approve, click **Review**. ![Review request link](/assets/images/help/settings/settings-third-party-approve-review.png) +6. After you review the information about the requested application, click **Grant access**. ![Grant access button](/assets/images/help/settings/settings-third-party-approve-grant.png) + +### 더 읽을거리 + +- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000..c66ed142f3 --- /dev/null +++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,20 @@ +--- +title: Denying access to a previously approved OAuth App for your organization +intro: 'If an organization no longer requires a previously authorized {% data variables.product.prodname_oauth_app %}, owners can remove the application''s access to the organization''s resources.' +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 + - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="The edit icon" %}. ![Edit icon](/assets/images/help/settings/settings-third-party-deny-edit.png) +6. Click **Deny access**. ![Deny confirmation button](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..5e5847e2c7 --- /dev/null +++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Disabling OAuth App access restrictions for your organization +intro: 'Organization owners can disable restrictions on the {% data variables.product.prodname_oauth_app %}s that have access to the organization''s resources.' +redirect_from: + - /articles/disabling-third-party-application-restrictions-for-your-organization/ + - /articles/disabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% danger %} + +**Warning**: When you disable {% data variables.product.prodname_oauth_app %} access restrictions for your organization, any organization member will automatically authorize {% data variables.product.prodname_oauth_app %} access to the organization's private resources when they approve an application for use in their personal account settings. + +{% enddanger %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Click **Remove restrictions**. ![Remove restrictions button](/assets/images/help/settings/settings-third-party-remove-restrictions.png) +6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**. ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..857938eae1 --- /dev/null +++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Enabling OAuth App access restrictions for your organization +intro: 'Organization owners can enable {% data variables.product.prodname_oauth_app %} access restrictions to prevent untrusted apps from accessing the organization''s resources while allowing organization members to use {% data variables.product.prodname_oauth_app %}s for their personal accounts.' +redirect_from: + - /articles/enabling-third-party-application-restrictions-for-your-organization/ + - /articles/enabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% warning %} + +**Warnings**: +- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_app %}s and SSH keys. For more information, see "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)." +- Once you've set up {% data variables.product.prodname_oauth_app %} access restrictions, make sure to re-authorize any {% data variables.product.prodname_oauth_app %} that require access to the organization's private data on an ongoing basis. All organization members will need to create new SSH keys, and the organization will need to create new deploy keys as needed. +- When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, applications can use an OAuth token to access information about {% data variables.product.prodname_marketplace %} transactions. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Under "Third-party application access policy," click **Setup application access restrictions**. ![Set up restrictions button](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) +6. After you review the information about third-party access restrictions, click **Restrict third-party application access**. ![Restriction confirmation button](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/index.md new file mode 100644 index 0000000000..9cf976f93a --- /dev/null +++ b/translations/ko-KR/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -0,0 +1,19 @@ +--- +title: Restricting access to your organization's data +intro: '{% data variables.product.prodname_oauth_app %} access restrictions allow organization owners to restrict an untrusted app''s access to the organization''s data. Organization members can then use {% data variables.product.prodname_oauth_app %}s for their personal user accounts while keeping organization data safe.' +redirect_from: + - /articles/restricting-access-to-your-organization-s-data + - /articles/restricting-access-to-your-organizations-data + - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/packages/index.md b/translations/ko-KR/content/packages/index.md index 56deb1e548..0272fdedfa 100644 --- a/translations/ko-KR/content/packages/index.md +++ b/translations/ko-KR/content/packages/index.md @@ -20,8 +20,8 @@ featuredLinks: - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - label: 'packages' - prefix: 'Packages: ' + label: '패키지' + prefix: 'Packages:' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..a9627ca034 --- /dev/null +++ b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -0,0 +1,68 @@ +--- +title: About custom domains and GitHub Pages +intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.' +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 + - /github/working-with-github-pages/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +### Supported custom domains + +{% data variables.product.prodname_pages %} works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)." + +| Supported custom domain type | 예시 | +| ---------------------------- | ------------------ | +| `www` subdomain | `www.example.com` | +| Custom subdomain | `blog.example.com` | +| Apex domain | `example.com` | + +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." + +We recommend always using a `www` subdomain, even if you also use an apex domain. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. 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)." + +After you configure a custom domain for a user or organization site, the custom domain will replace the `.github.io` or `.github.io` portion of the URL for any project sites owned by the account that do not have a custom domain configured. For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`. + +### Using a subdomain for your {% data variables.product.prodname_pages %} site + +A subdomain is the part of a URL before the root domain. You can configure your subdomain as `www` or as a distinct section of your site, like `blog.example.com`. + +Subdomains are configured with a `CNAME` record through your DNS provider. 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#configuring-a-subdomain)." + +#### `www` subdomains + +A `www` subdomain is the most commonly used type of subdomain. For example, `www.example.com` includes a `www` subdomain. + +`www` subdomains are the most stable type of custom domain because `www` subdomains are not affected by changes to the IP addresses of {% data variables.product.product_name %}'s servers. + +#### Custom subdomains + +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called `blog.example.com` and customize that section independently from `www.example.com`. + +### Using an apex domain for your {% data variables.product.prodname_pages %} site + +An apex domain is a custom domain that does not contain a subdomain, such as `example.com`. Apex domains are also known as base, bare, naked, root apex, or zone apex domains. + +An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through your DNS provider. 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#configuring-an-apex-domain)." + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." + +### Updating custom domains when your {% data variables.product.prodname_pages %} site is disabled + +If your {% data variables.product.prodname_pages %} site is disabled but has a custom domain set up, you should immediately update or remove your DNS records with your DNS provider to avoid the risk of a domain takeover. Having a custom domain configured with your DNS provider while your site is disabled could result in someone else hosting a site on one of your subdomains. 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)." + +There are a couple of reasons your site might be automatically disabled. + +- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[Downgrading your {% data variables.product.prodname_dotcom %} billing plan](/articles/downgrading-your-github-billing-plan)." +- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[Transferring a repository](/articles/transferring-a-repository)." + +### 더 읽을거리 + +- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md new file mode 100644 index 0000000000..9e748a4882 --- /dev/null +++ b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -0,0 +1,23 @@ +--- +title: Configuring a custom domain for your GitHub Pages site +intro: 'You can customize the domain name of your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000..0174984647 --- /dev/null +++ b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,121 @@ +--- +title: Managing a custom domain for your GitHub Pages site +intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.' +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 + - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site. + +### About custom domain configuration + +Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains. + +{% windows %} + +The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/). + +{% endwindows %} + +{% note %} + +**Note:** DNS changes can take up to 24 hours to propagate. + +{% endnote %} + +### Configuring a subdomain + +To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings, which will create a CNAME file in your site’s repository. After that, configure a CNAME record with your DNS provider. + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. ![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png) +5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `.github.io`. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `.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 %} + +{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} +{% data reusables.command_line.open_the_multi_os_terminal %} +6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain. +```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 %} + +### Configuring an apex domain + +To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider. + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)." + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. ![Save custom domain button](/assets/images/help/pages/save-custom-apex-domain.png) +5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. {% data reusables.pages.contact-dns-provider %} + - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %} + - To create `A` records, point your apex domain to the IP addresses for {% 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. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above. + ```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 %} + +### Configuring an apex domain and the `www` subdomain variant + +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. + +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." + +After you configure the apex domain, you must to configure a CNAME record with your DNS provider. + +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. +```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 +``` +### Removing a custom domain + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain," click **Remove**. ![Save custom domain button](/assets/images/help/pages/remove-custom-domain.png) + +### 더 읽을거리 + +- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..3b7ee96541 --- /dev/null +++ b/translations/ko-KR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,65 @@ +--- +title: Troubleshooting custom domains and GitHub Pages +intro: 'You can check for common errors to resolve issues with custom domains or HTTPS for your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +### _CNAME_ errors + +Custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. 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)." + +For your site to render at the correct domain, make sure your _CNAME_ file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the _CNAME_ file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to {% data variables.product.product_name %}, make sure to pull the commit that added the _CNAME_ file to your local repository first, so the file will be included in the build. + +Then, make sure the _CNAME_ file is formatted correctly. + +- The _CNAME_ filename must be all uppercase. +- The _CNAME_ file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider. +- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`. +- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository. + +### DNS misconfiguration + +If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider. + +You can also test whether your custom domain's DNS records are configured correctly. 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)." + +### Custom domain names that are unsupported + +If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names. + +Make sure your site does not: +- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`. +- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`. +- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`. + + The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)." + +{% data reusables.pages.wildcard-dns-warning %} + +For a list of supported custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)." + +### HTTPS errors + +{% data variables.product.prodname_pages %} sites using custom domains that are correctly configured with _CNAME_, `ALIAS`, `ANAME`, or `A` DNS records can be accessed over HTTPS. For more information, see "[Securing your {% data variables.product.prodname_pages %} site with HTTPS](/articles/securing-your-github-pages-site-with-https)." + +It can take up to an hour for your site to become available over HTTPS after you configure your custom domain. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. 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)." + +If you're using Certification Authority Authorization (CAA) records, at least one CAA record must exist with the value `letsencrypt.org` for your site to be accessible over HTTPS. For more information, see "[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)" in the Let's Encrypt documentation. + +### URL formatting on Linux + +If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.product_name %} username to remove non-alphanumeric characters. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username/)." + +### Browser cache + +If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new URL. For more information on clearing your cache, see your browser's documentation. diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000..6a4c5d33f7 --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -0,0 +1,150 @@ +--- +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/ + - /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 + - /github/working-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### About {% 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. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +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@3.0" %} +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." +{% endif %} + +### Types of {% data variables.product.prodname_pages %} sites + +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 %} + +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" %} +If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +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 %}. 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 %}. + +| 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///` + +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" %} +{% note %} + +**Note:** Repositories using the legacy `.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://.github.com` to `http(s)://.github.io`. If both a `.github.com` and `.github.io` repository exist, only the `.github.io` repository will be published. + +{% endnote %} +{% endif %} + +### Publishing sources for {% data variables.product.prodname_pages %} sites + +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" %} + +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. + +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`. 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 %} + +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. + +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. + +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`. 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 %} + +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 %} 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 %} 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 %} does not support server-side languages such as PHP, Ruby, or Python. + +### Guidelines for using {% data variables.product.prodname_pages %} + +{% if currentVersion == "free-pro-team@latest" %} +- {% 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 %} +- 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 %} 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 %} + - 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. + +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 %} 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). + +In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. For a list of prohibited uses, see "[{% data variables.product.prodname_dotcom %}'s Additional Product Terms for {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)." +{% endif %} + +### MIME types on {% data variables.product.prodname_pages %} + +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). + +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). + +### 더 읽을거리 + +- [{% 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/ko-KR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000..eecd249777 --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,46 @@ +--- +title: Adding a theme to your GitHub Pages site with the theme chooser +intro: 'You can add a theme to your {% data variables.product.prodname_pages %} site to customize your site’s look and feel.' +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site. + +### About the theme chooser + +The theme chooser adds a Jekyll theme to your repository. For more information about Jekyll, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." + +How the theme chooser works depends on whether your repository is public or private. + - If {% data variables.product.prodname_pages %} is already enabled for your repository, the theme chooser will add your theme to the current publishing source. + - If your repository is public and {% data variables.product.prodname_pages %} is disabled for your repository, using the theme chooser will enable {% data variables.product.prodname_pages %} and configure the default branch as your publishing source. + - If your repository is private and {% data variables.product.prodname_pages %} is disabled for your repository, you must enable {% data variables.product.prodname_pages %} by configuring a publishing source before you can use the theme chooser. + +For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." + +If you manually added a Jekyll theme to your repository in the past, those files may be applied even after you use the theme chooser. To avoid conflicts, remove all manually added theme folders and files before using the theme chooser. 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)." + +### Adding a theme with the theme chooser + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}," click **Choose a theme** or **Change theme**. ![Choose a theme button](/assets/images/help/pages/choose-a-theme.png) +4. On the top of the page, click the theme you want, then click **Select theme**. ![Theme options and Select theme button](/assets/images/help/pages/select-theme.png) +5. You may be prompted to edit your site's *README.md* file. + - To edit the file later, click **Cancel**. ![Cancel link when editing a file](/assets/images/help/pages/cancel-edit.png) + - To edit the file now, see "[Editing files in your repository](/articles/editing-files-in-your-repository/)." + +Your chosen theme will automatically apply to markdown files in your repository. To apply your theme to HTML files in your repository, you need to add YAML front matter that specifies a layout to each file. For more information, see "[Front Matter](https://jekyllrb.com/docs/front-matter/)" on the Jekyll site. + +### 더 읽을거리 + +- [Themes](https://jekyllrb.com/docs/themes/) on the Jekyll site diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..d765eb4e9f --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +redirect_from: + - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published: + +- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS. +- We use a unique subdomain for the private page to ensure that other repositories in your organization cannot publish content on the same origin as the private page. This protects your private page from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain. + +You can see your site's unique subdomain in the pages tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +To use a shorter and more memorable domain for your private {% data variables.product.prodname_pages %} site, you can configure a custom domain. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site)." + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. To see your published site, under "{% data variables.product.prodname_pages %}", click your site's URL. ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000..8fc3589bbb --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,38 @@ +--- +title: Configuring a publishing source for your GitHub Pages site +intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your{% if currentVersion ver_lt "enterprise-server@3.0" %} project{% endif %} site from a different branch or folder.' +redirect_from: + - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-your-github-pages-site + - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can configure a publishing source for a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." + +### Choosing a publishing source + +Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} 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 %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source. ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +4. Optionally, use the drop-down menu to select a folder for your publishing source. ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. Click **Save**. ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %} +3. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select a publishing source. ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +{% endif %} + +### Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site + +{% 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. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)." diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000..230704114b --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Creating a custom 404 page for your GitHub Pages site +intro: You can display a custom 404 error page when people try to access nonexistent pages on your site. +redirect_from: + - /articles/custom-404-pages/ + - /articles/creating-a-custom-404-page-for-your-github-pages-site + - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +{% data reusables.files.add-file %} +3. In the file name field, type `404.html` or `404.md`. ![File name field](/assets/images/help/pages/404-file-name.png) +4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file: + ```yaml + --- + permalink: /404.html + --- + ``` +5. Below the YAML front matter, if present, add the content you want to display on your 404 page. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### 더 읽을거리 + +- [Front matter](http://jekyllrb.com/docs/frontmatter) in the Jekyll documentation diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000..d20ebffabc --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,63 @@ +--- +title: Creating a GitHub Pages site +intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.' +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 + - /github/working-with-github-pages/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Creating a repository for your site + +{% data reusables.pages.new-or-existing-repo %} + +{% 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 %} + +### Creating your site + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.decide-publishing-source %} +3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source. +4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site. +{% data reusables.pages.configure-publishing-source %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### 다음 단계 + +You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. 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.html`. + +You can also add a theme to customize your site’s look and feel. 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 %}." + +To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." + +### 더 읽을거리 + +- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" +- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)" +- "[Creating new files](/articles/creating-new-files)" diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/index.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/index.md new file mode 100644 index 0000000000..6dcbaf8ab7 --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/index.md @@ -0,0 +1,26 @@ +--- +title: Getting started with GitHub Pages +intro: 'You can set up a basic {% data variables.product.prodname_pages %} site for yourself, your organization, or your project.' +redirect_from: + - /categories/github-pages-basics + - /articles/additional-customizations-for-github-pages/ + - /articles/getting-started-with-github-pages + - /github/working-with-github-pages/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 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 /changing-the-visibility-of-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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000..cb9bf8e593 --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,55 @@ +--- +title: Securing your GitHub Pages site with HTTPS +intro: 'HTTPS adds a layer of encryption that prevents others from snooping on or tampering with traffic to your site. You can enforce HTTPS for your {% data variables.product.prodname_pages %} site to transparently redirect all HTTP requests to HTTPS.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/securing-your-github-pages-site-with-https + - /github/working-with-github-pages/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +topics: + - pages +--- + +People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site. + +### About HTTPS and {% data variables.product.prodname_pages %} + +All {% data variables.product.prodname_pages %} sites, including sites that are correctly configured with a custom domain, support HTTPS and HTTPS enforcement. For more information about custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" and "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)." + +{% data reusables.pages.no_sensitive_data_pages %} + +{% data reusables.pages.private_pages_are_public_warning %} + +### Enforcing HTTPS for your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}," select **Enforce HTTPS**. ![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png) + +### Resolving problems with mixed content + +If you enable HTTPS for your {% data variables.product.prodname_pages %} site but your site's HTML still references images, CSS, or JavaScript over HTTP, then your site is serving *mixed content*. Serving mixed content may make your site less secure and cause trouble loading assets. + +To remove your site's mixed content, make sure all your assets are served over HTTPS by changing `http://` to `https://` in your site's HTML. + +Assets are commonly found in the following locations: +- If your site uses Jekyll, your HTML files will probably be found in the *_layouts* folder. +- CSS is usually found in the `` section of your HTML file. +- JavaScript is usually found in the `` section or just before the closing `` tag. +- Images are often found in the `` section. + +{% tip %} + +**Tip:** If you can't find your assets in your site's source files, try searching your site's source files for `http` in your text editor or on {% data variables.product.product_name %}. + +{% endtip %} + +#### Examples of assets referenced in an HTML file + +| Asset type | HTTP | HTTPS | +|:----------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:| +| CSS | `` | `` | +| JavaScript | `` | `` | +| Image | `Logo` | `Logo` | diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000..26904123a8 --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Unpublishing a GitHub Pages site +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' +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 + - /github/working-with-github-pages/unpublishing-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can unpublish a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### Unpublishing a project site + +{% data reusables.repositories.navigate-to-repo %} +2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)." +3. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.** ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} + +### Unpublishing a user or organization site + +{% data reusables.repositories.navigate-to-repo %} +2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)." +{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000..bfcf25bd24 --- /dev/null +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,24 @@ +--- +title: Using submodules with GitHub Pages +intro: 'You can use submodules with {% data variables.product.prodname_pages %} to include other projects in your site''s code.' +redirect_from: + - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-github-pages + - /github/working-with-github-pages/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +If the repository for your {% data variables.product.prodname_pages %} site contains submodules, their contents will automatically be pulled in when your site is built. + +You can only use submodules that point to public repositories, because the {% data variables.product.prodname_pages %} server cannot access private repositories. + +Use the `https://` read-only URL for your submodules, including nested submodules. You can make this change in your _.gitmodules_ file. + +### 더 읽을거리 + +- "[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" from the _Pro Git_ book +- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/ko-KR/content/pages/index.md b/translations/ko-KR/content/pages/index.md new file mode 100644 index 0000000000..785c270206 --- /dev/null +++ b/translations/ko-KR/content/pages/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages Documentation +shortTitle: GitHub 페이지 +intro: 'You can create a website directly from a {% data variables.product.product_name %} repository.' +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 + - /github/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% link_with_intro /getting-started-with-github-pages %} +{% link_with_intro /setting-up-a-github-pages-site-with-jekyll %} +{% link_with_intro /configuring-a-custom-domain-for-your-github-pages-site %} \ No newline at end of file diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000..e9ada225c6 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -0,0 +1,131 @@ +--- +title: About GitHub Pages and Jekyll +intro: 'Jekyll is a static site generator with built-in support for {% 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 + - /github/working-with-github-pages/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### About Jekyll + +Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. Jekyll takes Markdown and HTML files and creates a complete static website based on your choice of layouts. Jekyll supports Markdown and Liquid, a templating language that loads dynamic content on your site. For more information, see [Jekyll](https://jekyllrb.com/). + +Jekyll is not officially supported for Windows. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation. + +We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)." + +### Configuring Jekyll in your {% data variables.product.prodname_pages %} site + +You can configure most Jekyll settings, such as your site's theme and plugins, by editing your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. + +Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites. + +```yaml +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 +``` + +By default, Jekyll doesn't build files or folders that: +- are located in a folder called `/node_modules` or `/vendor` +- start with `_`, `.`, or `#` +- end with `~` +- are excluded by the `exclude` setting in your configuration file + +If you want Jekyll to process any of these files, you can use the `includes` setting in your configuration file. + +### Front matter + +{% data reusables.pages.about-front-matter %} + +You can add `site.github` to a post or page to add any repository references metadata to your site. For more information, see "[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)" in the Jekyll Metadata documentation. + +### Themes + +{% data reusables.pages.add-jekyll-theme %} For more information, see "[Themes](https://jekyllrb.com/docs/themes/)" in the Jekyll documentation. + +{% if currentVersion == "free-pro-team@latest" %} +You can add a supported theme to your site on {% data variables.product.prodname_dotcom %}. For more information, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and "[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)." + +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)." + +You can override any of your theme's defaults by editing the theme's files. For more information, see your theme's documentation and "[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" in the Jekyll documentation. + +### Plugins + +You can download or create Jekyll plugins to extend the functionality of Jekyll for your site. For example, the [jemoji](https://github.com/jekyll/jemoji) plugin lets you use {% data variables.product.prodname_dotcom %}-flavored emoji in any page on your site the same way you would on {% data variables.product.prodname_dotcom %}. For more information, see "[Plugins](https://jekyllrb.com/docs/plugins/)" in the Jekyll documentation. + +{% data variables.product.prodname_pages %} uses plugins that are enabled by default and cannot be disabled: +- [`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) + +You can enable additional plugins by adding the plugin's gem to the `plugins` setting in your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. + +For a list of supported plugins, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. For usage information for a specific plugin, see the plugin's documentation. + +{% tip %} + +**Tip:** You can make sure you're using the latest version of all plugins by keeping the {% data variables.product.prodname_pages %} gem updated. For more information, see "[Testing your GitHub Pages site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" and "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. + +{% endtip %} + +{% data variables.product.prodname_pages %} cannot build sites using unsupported plugins. If you want to use unsupported plugins, generate your site locally and then push your site's static files to {% data variables.product.product_name %}. + +### Syntax highlighting + +To make your site easier to read, code snippets are highlighted on {% data variables.product.prodname_pages %} sites the same way they're highlighted on {% data variables.product.product_name %}. For more information about syntax highlighting on {% data variables.product.product_name %}, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)." + +By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). If you specify Pygments in your *_config.yml* file, Rouge will be used instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." + +If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file. + +```yaml +kramdown: + syntax_highlighter_opts: + disable : true +``` + +If your theme doesn't include CSS for syntax highlighting, you can generate {% data variables.product.prodname_dotcom %}'s syntax highlighting CSS and add it to your project's `style.css` file. + +```shell +$ rougify style github > style.css +``` + +### Building your site locally + +{% data reusables.pages.test-locally %} diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..9b2ffcb839 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,62 @@ +--- +title: About Jekyll build errors for GitHub Pages sites +intro: 'If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you''ll receive an error message with more information.' +redirect_from: + - /articles/viewing-jekyll-build-error-messages/ + - /articles/generic-jekyll-build-failures/ + - /articles/about-jekyll-build-errors-for-github-pages-sites + - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### About Jekyll build errors + +Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} +- The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} +- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)." +- You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation. + +{% note %} + +**Note:** It can take up to 20 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}. + +{% endnote %} + +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. +- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. +- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. + +For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." + +### Viewing Jekyll build error messages + +We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." + +When you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/articles/about-status-checks)." + +When you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} + +You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. + +You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit. + +1. If you haven't already, add a file called _Gemfile_ in the root of your publishing source, with the following content: + ```ruby + source `https://rubygems.org` + gem `github-pages` + ``` + +2. Configure your site's repository for the testing service of your choice. For example, to use [Travis CI](https://travis-ci.org/), add a file named _.travis.yml_ in the root of your publishing source, with the following content: + ```yaml + language: ruby + rvm: + - 2.3 + script: "bundle exec jekyll build" + ``` +3. You may need to activate your repository with the third-party testing service. For more information, see your testing service's documentation. diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..97dd568ed3 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,71 @@ +--- +title: Adding a theme to your GitHub Pages site using Jekyll +intro: You can personalize your Jekyll site by adding and customizing a theme. +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +People with write permissions for a repository can add a theme to a {% data variables.product.prodname_pages %} site using Jekyll. + +{% data reusables.pages.test-locally %} + +### Adding a theme + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +2. Navigate to *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Add a new line to the file for the theme name. + - 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. For a list of supported themes, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site. ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png) + - To use any other Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, type `remote_theme: THEME-NAME`, replacing THEME-NAME with the name of the theme as shown in the README of the theme's repository. ![Unsupported theme in config file](/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 %} + +### Customizing your theme's CSS + +{% 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. Create a new file called _/assets/css/style.scss_. +2. Add the following content to the top of the file: + ```scss + --- + --- + + @import "{{ site.theme }}"; + ``` +3. Add any custom CSS or Sass (including imports) you'd like immediately after the `@import` line. + +### Customizing your theme's HTML layout + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +1. On {% data variables.product.prodname_dotcom %}, navigate to your theme's source repository. For example, the source repository for Minima is https://github.com/jekyll/minima. +2. In the *_layouts* folder, navigate to your theme's _default.html_ file. +3. Copy the contents of the file. +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +6. Create a file called *_layouts/default.html*. +7. Paste the default layout content you copied earlier. +8. Customize the layout as you'd like. + +### 더 읽을거리 + +- "[Creating new files](/articles/creating-new-files)" diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..d5fbd11fef --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,72 @@ +--- +title: Adding content to your GitHub Pages site using Jekyll +intro: 'You can add a new page or post to your Jekyll site on {% data variables.product.prodname_pages %}.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/adding-content-to-your-github-pages-site-using-jekyll + - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +People with write permissions for a repository can add content to a {% data variables.product.prodname_pages %} site using Jekyll. + +### About content in Jekyll sites + +Before you can add content to a Jekyll site on {% data variables.product.prodname_pages %}, you must create a Jekyll site. For more information, see "[Creating a {% data variables.product.prodname_pages %} site with Jekyll](/articles/creating-a-github-pages-site-with-jekyll)." + +The main types of content for Jekyll sites are pages and posts. A page is for standalone content that isn't associated with a specific date, such as an "About" page. The default Jekyll site contains a file called `about.md`, which renders as a page on your site at `YOUR-SITE-URL/about`. You can edit the contents of that file to personalize your "About" page, and you can use the "About" page as a template to create new pages. For more information, see "[Pages](https://jekyllrb.com/docs/pages/)" in the Jekyll documentation. + +A post is a blog post. The default Jekyll site contains a directory named `_posts` that contains a default post file. You can edit the contents of that post, and you can use the default post as a template to create new posts. For more information, see "[Posts](https://jekyllrb.com/docs/posts/)" in the Jekyll documentation. + +Your theme includes default layouts, includes, and stylesheets that will automatically be applied to new pages and posts on your site, but you can override any of these defaults. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#themes)." + +{% data reusables.pages.about-front-matter %} + +{% data reusables.pages.test-locally %} + +### Adding a new page to your site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. In the root of your publishing source, create a new file for your page called _PAGE-NAME.md_, replacing _PAGE-NAME_ with a meaningful filename for the page. +4. Add the following YAML frontmatter to the top of the file, replacing _PAGE TITLE_ with the page's title and _URL-PATH_ with a path you want for the page's URL. For example, if the base URL of your site is `https://octocat.github.io` and your _URL-PATH_ is `/about/contact/`, your page will be located at `https://octocat.github.io/about/contact`. + ```shell + layout: page + title: "PAGE TITLE" + permalink: /URL-PATH/ + ``` +5. Below the frontmatter, add content for your page. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Adding a new post to your site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. Navigate to the `_posts` directory. +4. Create a new file called _YYYY-MM-DD-NAME-OF-POST.md_, replacing _YYYY-MM-DD_ with the date of your post and _NAME-OF-POST_ with the name of your post. +4. Add the following YAML frontmatter to the top of the file, replacing _POST TITLE_ with the post's title, _YYYY-MM-DD hh:mm:ss -0000_ with the date and time for the post, and _CATEGORY-1_ and _CATEGORY-2_ with as many categories you want for your post. + ```shell + layout: post + title: "POST TITLE" + date: YYYY-MM-DD hh:mm:ss -0000 + categories: CATEGORY-1 CATEGORY-2 + ``` +5. Below the frontmatter, add content for your post. +{% 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`. + +### 다음 단계 + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000..39b14667f6 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,116 @@ +--- +title: Creating a GitHub Pages site with Jekyll +intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/creating-a-github-pages-site-with-jekyll + - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll +permissions: 'People with admin permissions for a repository can create a {% data variables.product.prodname_pages %} site with Jekyll.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### 빌드전 요구 사양 + +Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Creating a repository for your site + +{% data reusables.pages.new-or-existing-repo %} + +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} + +### Creating your site + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository. + ```shell + $ cd PARENT-FOLDER + ``` +3. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository. + ```shell + $ git init REPOSITORY-NAME + > Initialized empty Git repository in /Users/octocat/my-site/.git/ + # Creates a new folder on your computer, initialized as a Git repository + ``` + 4. Change directories to the repository. + ```shell + $ cd REPOSITORY-NAME + # Changes the working directory + ``` +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. + ```shell + $ mkdir docs + # Creates a new folder called docs + $ cd docs + ``` + If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch. + ```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. To create a new Jekyll site, use the `jekyll new` command: + ```shell + $ jekyll new . + # Creates a Jekyll site in the current directory + ``` +8. Open the Gemfile that Jekyll created. +1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line. +1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to: + + ```shell + gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins + ``` + + Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)." + + The correct version Jekyll will be installed as a dependency of the `github-pages` gem. +10. Save and close the Gemfile. +11. From the command line, run `bundle update`. +11. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." +12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository. +```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. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on. + ```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.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### 다음 단계 + +To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)." + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md new file mode 100644 index 0000000000..90f13f8482 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md @@ -0,0 +1,25 @@ +--- +title: Setting up a GitHub Pages site with Jekyll +intro: 'You can use Jekyll, a popular static site generator, to further customize your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..9ecdc932b8 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,36 @@ +--- +title: Setting a Markdown processor for your GitHub Pages site using Jekyll +intro: 'You can choose a Markdown processor to determine how Markdown is rendered on your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/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: '*' +topics: + - pages +--- + +People with write permissions for a repository can set the Markdown processor for a {% data variables.product.prodname_pages %} site. + +{% 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 %}. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." + +You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor, but only our CommonMark processor will always match the results you see on {% data variables.product.product_name %}. + +{% data reusables.pages.navigate-site-repo %} +2. In your repository, browse to the *_config.yml* file. +{% data reusables.repositories.edit-file %} +4. Find the line that starts with `markdown:` and change the value to `kramdown` or `GFM`. ![Markdown setting in 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 %} + +### 더 읽을거리 + +- [kramdown Documentation](https://kramdown.gettalong.org/documentation.html) +- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000..b78c9281e1 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,62 @@ +--- +title: Testing your GitHub Pages site locally with Jekyll +intro: 'You can build your {% data variables.product.prodname_pages %} site locally to preview and test changes to your site.' +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 + - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +Anyone with read permissions for a repository can test a {% data variables.product.prodname_pages %} site locally. + +### 빌드전 요구 사양 + +Before you can use Jekyll to test a site, you must: + - Install [Jekyll](https://jekyllrb.com/docs/installation/). + - Create a Jekyll site. For more information, see "[Creating a {% data variables.product.prodname_pages %} site with Jekyll](/articles/creating-a-github-pages-site-with-jekyll)." + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Building your site locally + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.pages.navigate-publishing-source %} +3. Run `bundle install`. +3. Run your Jekyll site locally. + ```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. To preview your site, in your web browser, navigate to `http://localhost:4000`. + +### Updating the {% data variables.product.prodname_pages %} gem + +Jekyll is an active open source project that is updated frequently. If the `github-pages` gem on your computer is out of date with the `github-pages` gem on the {% data variables.product.prodname_pages %} server, your site may look different when built locally than when published on {% data variables.product.product_name %}. To avoid this, regularly update the `github-pages` gem on your computer. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Update the `github-pages` gem. + - If you installed Bundler, run `bundle update github-pages`. + - If you don't have Bundler installed, run `gem update github-pages`. + +### 더 읽을거리 + +- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in the Jekyll documentation diff --git a/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..907cb3c671 --- /dev/null +++ b/translations/ko-KR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,191 @@ +--- +title: Troubleshooting Jekyll build errors for GitHub Pages sites +intro: 'You can use Jekyll build error messages to troubleshoot problems with your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### Troubleshooting build errors + +If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you can use error messages to troubleshoot. For more information about error messages and how to view them, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." + +If you received a generic error message, check for common issues. +- You're using unsupported plugins. 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" %} +- Your repository has exceeded our repository size limits. For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota)"{% endif %} +- You changed the `source` setting in your *_config.yml* file. {% data variables.product.prodname_pages %} overrides this setting during the build process. +- A filename in your publishing source contains a colon (`:`) which is not supported. + +If you received a specific error message, review the troubleshooting information for the error message below. + +After you've fixed any errors, push the changes to your site's publishing source to trigger another build on {% data variables.product.product_name %}. + +### Config file error + +This error means that your site failed to build because the *_config.yml* file contains syntax errors. + +To troubleshoot, make sure that your *_config.yml* file follows these rules: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +### Date is not a valid datetime + +This error means that one of the pages on your site includes an invalid datetime. + +To troubleshoot, search the file in the error message and the file's layouts for calls to any date-related Liquid filters. Make sure that any variables passed into date-related Liquid filters have values in all cases and never pass `nil` or `""`. For more information, see "[Liquid filters](https://help.shopify.com/en/themes/liquid/filters)" in the Liquid documentation. + +### File does not exist in includes directory + +This error means that your code references a file that doesn't exist in your *_includes* directory. + +{% data reusables.pages.search-for-includes %} If any of the files you've referenced aren't in the *_includes* directory, copy or move the files into the *_includes* directory. + +### File is a symlink + +This error means that your code references a symlinked file that does not exist in the publishing source for your site. + +{% data reusables.pages.search-for-includes %} If any of the files you've referenced are symlinked, copy or move the files into the *_includes* directory. + +### File is not properly UTF-8 encoded + +This error means that you used non-Latin characters, like `日本語`, without telling the computer to expect these symbols. + +To troubleshoot, force UTF-8 encoding by adding the following line to your *_config.yml* file: +```yaml +encoding: UTF-8 +``` + +### Invalid highlighter language + +This error means that you specified any syntax highlighter other than [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/) in your configuration file. + +To troubleshoot, update your *_config.yml* file to specify [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/). For more information, see "[About {% data variables.product.product_name %} and Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)." + +### Invalid post date + +This error means that a post on your site contains an invalid date in the filename or YAML front matter. + +To troubleshoot, make sure all dates are formatted as YYYY-MM-DD HH:MM:SS for UTC and are actual calendar dates. To specify a time zone with an offset from UTC, use the format YYYY-MM-DD HH:MM:SS +/-TTTT, like `2014-04-18 11:30:00 +0800`. + +If you specify a date format in your *_config.yml* file, make sure the format is correct. + +### Invalid Sass or SCSS + +This error means your repository contains a Sass or SCSS file with invalid content. + +To troubleshoot, review the line number included in the error message for invalid Sass or SCSS. To help prevent future errors, install a Sass or SCSS linter for your favorite text editor. + +### Invalid submodule + +This error means that your repository includes a submodule that hasn't been properly initialized. + +{% data reusables.pages.remove-submodule %} + +If do you want to use the submodule, make sure you use `https://` when referencing the submodule (not `http://`) and that the submodule is in a public repository. + +### Invalid YAML in data file + +This error means that one of more files in the *_data* folder contains invalid YAML. + +To troubleshoot, make sure the YAML files in your *_data* folder follow these rules: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +For more information about Jekyll data files, see "[Data Files](https://jekyllrb.com/docs/datafiles/)" in the Jekyll documentation. + +### Markdown errors + +This error means that your repository contains Markdown errors. + +To troubleshoot, make sure you are using a supported Markdown processor. For more information, see "[Setting a Markdown processor for your {% data variables.product.prodname_pages %} site using Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)." + +Then, make sure the file in the error message uses valid Markdown syntax. For more information, see "[Markdown: Syntax](https://daringfireball.net/projects/markdown/syntax)" on Daring Fireball. + +### Missing docs folder + +This error means that you have chosen the `docs` folder on a branch as your publishing source, but there is no `docs` folder in the root of your repository on that branch. + +To troubleshoot, if your `docs` folder was accidentally moved, try moving the `docs` folder back to the root of your repository on the branch you chose for your publishing source. If the `docs` folder was accidentally deleted, you can either: +- Use Git to revert or undo the deletion. For more information, see "[git-revert](https://git-scm.com/docs/git-revert.html)" in the Git documentation. +- Create a new `docs` folder in the root of your repository on the branch you chose for your publishing source and add your site's source files to the folder. For more information, see "[Creating new files](/articles/creating-new-files)." +- Change your publishing source. For more information, see "[Configuring a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)." + +### Missing submodule + +This error means that your repository includes a submodule that doesn't exist or hasn't been properly initialized. + +{% data reusables.pages.remove-submodule %} + +If you do want to use a submodule, initialize the submodule. For more information, see "[Git Tools - Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" in the _Pro Git_ book. + +### Relative permalinks configured + +This errors means that you have relative permalinks, which are not supported by {% data variables.product.prodname_pages %}, in your *_config.yml* file. + +Permalinks are permanent URLs that reference a particular page on your site. Absolute permalinks begin with the root of the site, while relative permalinks begin with the folder containing the referenced page. {% data variables.product.prodname_pages %} and Jekyll no longer support relative permalinks. For more information about permalinks, see "[Permalinks](https://jekyllrb.com/docs/permalinks/)" in the Jekyll documentation. + +To troubleshoot, remove the `relative_permalinks` line from your *_config.yml* file and reformat any relative permalinks in your site with absolute permalinks. For more information, see "[Editing files in your repository](/articles/editing-files-in-your-repository)." + +### Symlink does not exist within your site's repository + +This error means that your site includes a symbolic link (symlink) that does not exist in the publishing source for your site. For more information about symlinks, see "[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)" on Wikipedia. + +To troubleshoot, determine if the file in the error message is used to build your site. If not, or if you don't want the file to be a symlink, delete the file. If the symlinked file is necessary to build your site, make sure the file or directory the symlink references is in the publishing source for your site. 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 %} + +### Syntax error in 'for' loop + +This error means that your code includes invalid syntax in a Liquid `for` loop declaration. + +To troubleshoot, make sure all `for` loops in the file in the error message have proper syntax. For more information about proper syntax for `for` loops, see "[Iteration tags](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" in the Liquid documentation. + +### Tag not properly closed + +This error message means that your code includes a logic tag that is not properly closed. For example, {% raw %}`{% capture example_variable %}` must be closed by `{% endcapture %}`{% endraw %}. + +To troubleshoot, make sure all logic tags in the file in the error message are properly closed. For more information, see "[Liquid tags](https://help.shopify.com/en/themes/liquid/tags)" in the Liquid documentation. + +### Tag not properly terminated + +This error means that your code includes an output tag that is not properly terminated. For example, {% raw %}`{{ page.title }` instead of `{{ page.title }}`{% endraw %}. + +To troubleshoot, make sure all output tags in the file in the error message are terminated with `}}`. For more information, see "[Liquid objects](https://help.shopify.com/en/themes/liquid/objects)" in the Liquid documentation. + +### Unknown tag error + +This error means that your code contains an unrecognized Liquid tag. + +To troubleshoot, make sure all Liquid tags in the file in the error message match Jekyll's default variables and there are no typos in the tag names. For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation. + +Unsupported plugins are a common source of unrecognized tags. If you use an unsupported plugin in your site by generating your site locally and pushing your static files to {% data variables.product.product_name %}, make sure the plugin is not introducing tags that are not in Jekyll's default variables. For a list of supported plugins, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)." diff --git a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md index c7d69c3b82..02236c362c 100644 --- a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md @@ -170,7 +170,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap In the same way, we can [view repositories for the authenticated user][user repos api]: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -207,7 +207,7 @@ Fetching information for existing repositories is a common use case, but the we need to `POST` some JSON containing the details and configuration options. ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -242,7 +242,7 @@ The UI for Issues on {% data variables.product.product_name %} aims to provide ' Just like github.com, the API provides a few methods to view issues for the authenticated user. To [see all your issues][get issues api], call `GET /issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -250,7 +250,7 @@ To get only the [issues under one of your {% data variables.product.product_name /orgs//issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -283,7 +283,7 @@ Now that we've seen how to paginate lists of issues, let's [create an issue][cre To create an issue, we need to be authenticated, so we'll pass an OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON body to the `/issues` path underneath the repository in which we want to create the issue: ```shell -$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ +$ curl -i -H 'Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/ko-KR/content/rest/reference/enterprise-admin.md b/translations/ko-KR/content/rest/reference/enterprise-admin.md index 8c38a0527c..a069da35c0 100644 --- a/translations/ko-KR/content/rest/reference/enterprise-admin.md +++ b/translations/ko-KR/content/rest/reference/enterprise-admin.md @@ -100,7 +100,7 @@ The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% endnote %} diff --git a/translations/ko-KR/content/rest/reference/migrations.md b/translations/ko-KR/content/rest/reference/migrations.md index cf2d0ec6ba..e8a1297433 100644 --- a/translations/ko-KR/content/rest/reference/migrations.md +++ b/translations/ko-KR/content/rest/reference/migrations.md @@ -16,7 +16,7 @@ topics: ## 조직 -The Migrations API is only available to authenticated organization owners. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." +The Migrations API is only available to authenticated organization owners. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/ko-KR/content/rest/reference/repos.md b/translations/ko-KR/content/rest/reference/repos.md index 49203a6618..bec87c0716 100644 --- a/translations/ko-KR/content/rest/reference/repos.md +++ b/translations/ko-KR/content/rest/reference/repos.md @@ -193,7 +193,7 @@ The authenticated user will be the author of any merges done through this endpoi ## Pages -The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." +The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." In {% data variables.product.prodname_pages %} API endpoints with a `status` key in their response, the value can be one of: * `null`: The site has yet to be built. @@ -205,7 +205,7 @@ In {% data variables.product.prodname_pages %} API endpoints with a `status` key In {% data variables.product.prodname_pages %} API endpoints that return GitHub Pages site information, the JSON responses include these fields: * `html_url`: The absolute URL (including scheme) of the rendered Pages site. For example, `https://username.github.io`. * `source`: An object that contains the source branch and directory for the rendered Pages site. 여기에는 다음이 포함됩니다. - - `branch`: The repository branch used to publish your [site's source files](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. + - `branch`: The repository branch used to publish your [site's source files](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. - `path`: The repository directory from which the site publishes. Will be either `/` or `/docs`. {% for operation in currentRestOperations %} diff --git a/translations/ko-KR/content/rest/reference/scim.md b/translations/ko-KR/content/rest/reference/scim.md index 2b601ca324..7a92b22cb2 100644 --- a/translations/ko-KR/content/rest/reference/scim.md +++ b/translations/ko-KR/content/rest/reference/scim.md @@ -14,7 +14,7 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% endnote %} diff --git a/translations/ko-KR/content/rest/reference/teams.md b/translations/ko-KR/content/rest/reference/teams.md index 7f6b2a3bf4..d98f01e647 100644 --- a/translations/ko-KR/content/rest/reference/teams.md +++ b/translations/ko-KR/content/rest/reference/teams.md @@ -18,7 +18,7 @@ This API is only available to authenticated members of the team's [organization] ## Discussions -The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. +The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -26,7 +26,7 @@ The team discussions API allows you to get, create, edit, and delete discussion ## Discussion comments -The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." This API is only available to authenticated members of the team's organization. +The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -39,7 +39,7 @@ This API is only available to authenticated members of the team's organization. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "Synchronizing teams between your identity provider and GitHub." +**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "Synchronizing teams between your identity provider and GitHub." {% endnote %} @@ -54,7 +54,7 @@ This API is only available to authenticated members of the team's organization. The Team Synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups. To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "Authorizing a personal access token for use with a SAML single sign-on organization." -You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." +You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} diff --git a/translations/ko-KR/data/release-notes/2-21/18.yml b/translations/ko-KR/data/release-notes/2-21/18.yml new file mode 100644 index 0000000000..e27f2fe4a0 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/18.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. + - Security alerts are not reported when pushing to a repository on the command line. diff --git a/translations/ko-KR/data/release-notes/2-21/6.yml b/translations/ko-KR/data/release-notes/2-21/6.yml index d85f716f13..24127f581c 100644 Binary files a/translations/ko-KR/data/release-notes/2-21/6.yml and b/translations/ko-KR/data/release-notes/2-21/6.yml differ diff --git a/translations/ko-KR/data/release-notes/2-22/10.yml b/translations/ko-KR/data/release-notes/2-22/10.yml new file mode 100644 index 0000000000..fd5aa5a1d8 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-22/10.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. diff --git a/translations/ko-KR/data/release-notes/3-0/4.yml b/translations/ko-KR/data/release-notes/3-0/4.yml new file mode 100644 index 0000000000..b3a39c1743 --- /dev/null +++ b/translations/ko-KR/data/release-notes/3-0/4.yml @@ -0,0 +1,25 @@ +--- +date: '2021-04-01' +intro: 'The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - When maintenance mode was enabled, some services continued to be listed as "active processes" even though they were expected to be running, and should not have been listed. + - After upgrading from 2.22.x to 3.0.x with GitHub Actions enabled, the self-hosted runner version was not updated and no self-hosted updates were made. + - Old GitHub Pages builds were not cleaned up leading to increased disk usage. + - '`memcached` was not running on active replicas.' + - Upgrade failed when updating file permissions when GitHub Actions was enabled. + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The `ghe-saml-mapping-csv` command-line utility produced a warning message. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. + - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text. diff --git a/translations/ko-KR/data/reusables/actions/actions-audit-events-workflow.md b/translations/ko-KR/data/reusables/actions/actions-audit-events-workflow.md index 40ed66434c..18b8d2c4eb 100644 --- a/translations/ko-KR/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/ko-KR/data/reusables/actions/actions-audit-events-workflow.md @@ -4,5 +4,7 @@ | `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." | | `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)." | | `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)." | +| `disable_workflow` | Triggered when a workflow is disabled. | +| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`. | | `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)." | | `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." | diff --git a/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md index baa32fddac..b6abfe68c7 100644 --- a/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md +++ b/translations/ko-KR/data/reusables/advanced-security/about-ghas-organization-policy.md @@ -2,4 +2,4 @@ You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose. -Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_advanced_security %} features, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." diff --git a/translations/ko-KR/data/reusables/branches/set-default-branch.md b/translations/ko-KR/data/reusables/branches/set-default-branch.md index 20d94881f6..61c5fb0903 100644 --- a/translations/ko-KR/data/reusables/branches/set-default-branch.md +++ b/translations/ko-KR/data/reusables/branches/set-default-branch.md @@ -1 +1 @@ -You can set the name of the default branch for new repositories. 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 %} +You can set the name of the default branch for new repositories. 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](/organizations/managing-organization-settings/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 %} diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-visibility.md index 3f4f17e1b2..303bb3669b 100644 --- a/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ The repositories for an assignment can be public or private. If you use private repositories, only the student or team can see the feedback you provide. -You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" and "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. diff --git a/translations/ko-KR/data/reusables/classroom/guide-create-new-classroom.md b/translations/ko-KR/data/reusables/classroom/guide-create-new-classroom.md index e554d4b605..b005e29ebd 100644 --- a/translations/ko-KR/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/ko-KR/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) +1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) 1. Type the name for your classroom. ![Text field for typing name of classroom](/assets/images/help/classroom/type-classroom-name.png) 1. Click **Create classroom**. ![Text field for typing name of classroom](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/ko-KR/data/reusables/code-scanning/click-alert-in-list.md b/translations/ko-KR/data/reusables/code-scanning/click-alert-in-list.md index af80aac75d..50f6e6458e 100644 --- a/translations/ko-KR/data/reusables/code-scanning/click-alert-in-list.md +++ b/translations/ko-KR/data/reusables/code-scanning/click-alert-in-list.md @@ -1 +1,6 @@ -1. Under "Code scanning," click the alert you'd like to explore. ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +1. Under "Code scanning," click the alert you'd like to explore. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% 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 7dd8f996d0..c3b22f4515 100644 --- a/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -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-dependencies)." You can configure access to private registries in a repository's _dependabot.yml_ configuration file. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." +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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)." You can configure access to private registries in a repository's _dependabot.yml_ configuration file. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." diff --git a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md index 0ec034c050..d405e1471a 100644 --- a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md @@ -6,7 +6,7 @@ The following table shows, for each package manager: | Package manager | YAML value | Supported versions | Private repositories | Private registries | Vendoring | | --------------- | ---------------- | ------------------------------ |:--------------------:|:------------------:|:---------:| -| 번들러 | `bundler` | v1 | | **✓** | **✓** | +| 번들러 | `bundler` | v1, v2 | | **✓** | **✓** | | Cargo | `cargo` | v1 | **✓** | **✓** | | | Composer | `composer` | v1, v2 | **✓** | **✓** | | | Docker | `docker` | v1 | **✓** | **✓** | | diff --git a/translations/ko-KR/data/reusables/dotcom_billing/coupon-expires.md b/translations/ko-KR/data/reusables/dotcom_billing/coupon-expires.md new file mode 100644 index 0000000000..71beb790aa --- /dev/null +++ b/translations/ko-KR/data/reusables/dotcom_billing/coupon-expires.md @@ -0,0 +1 @@ +If you use a coupon to pay for a subscription, when the coupon expires, your payment method will be charged the full cost of your subscription. If you do not have a saved payment method, your account will be downgraded to {% data variables.product.prodname_free_user %} for user accounts or {% data variables.product.prodname_free_team %} for organizations. diff --git a/translations/ko-KR/data/reusables/education/about-github-education-link.md b/translations/ko-KR/data/reusables/education/about-github-education-link.md index 84a5d61418..4106c559a9 100644 --- a/translations/ko-KR/data/reusables/education/about-github-education-link.md +++ b/translations/ko-KR/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_education %} school. For more information, see "[About {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)." +Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)." diff --git a/translations/ko-KR/data/reusables/github-actions/actions-github-connect-requirement.md b/translations/ko-KR/data/reusables/github-actions/actions-github-connect-requirement.md new file mode 100644 index 0000000000..8b36658e05 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/actions-github-connect-requirement.md @@ -0,0 +1 @@ +To allow {% data variables.product.prodname_ghe_server %} to use actions directly from {% data variables.product.prodname_dotcom_the_website %}, you can use {% data variables.product.prodname_github_connect %}. You will need to enable the setting for "Server can use actions from {% data variables.product.prodname_dotcom_the_website %} in workflows runs," as described in "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." diff --git a/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md b/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md index 33c7bd3120..2814ee964b 100644 --- a/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/ko-KR/data/reusables/github-actions/java-jvm-architecture.md @@ -2,16 +2,17 @@ The starter workflow template sets up the `PATH` to contain OpenJDK 8 for the x64 platform. If you want to use a different version of Java, or target a different architecture (`x64` or `x86`), you can use the `setup-java` action to choose a different Java runtime environment. -For example, to use version 9.0.4 of the JDK for the x64 platform, you can use the `setup-java` action and configure the `java-version` and `architecture` parameters to `'9.0.4'` and `x64`. +For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'adopt'` and `x64`. {% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 + - name: Set up JDK 11 for x64 + uses: actions/setup-java@v2 with: - java-version: '9.0.4' + java-version: '11' + distribution: 'adopt' architecture: x64 ``` {% endraw %} 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 index b2c935e893..046848b19c 100644 --- 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 @@ -1,5 +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)." +**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](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endwarning %} diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 125c285ead..0b4022951d 100644 --- a/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/ko-KR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." +After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md index a0e1a12947..3ebd07b725 100644 --- a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md +++ b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md @@ -1 +1 @@ -3. Confirm that SAML SSO is enabled. For more information, see "[Managing SAML single sign-on for your organization](/articles/managing-saml-single-sign-on-for-your-organization)." +3. Confirm that SAML SSO is enabled. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/)." diff --git a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md index f8ebbf4246..08aa1fad59 100644 --- a/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md +++ b/translations/ko-KR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md @@ -1,5 +1,5 @@ To enable team synchronization for Okta, you or your IdP administrator must: -- Enable SAML SSO and SCIM for your organization using Okta. For more information, see "[Configuring SAML single sign-on and SCIM using Okta](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)." +- Enable SAML SSO and SCIM for your organization using Okta. For more information, see "[Configuring SAML single sign-on and SCIM using Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)." - Provide the tenant URL for your Okta instance. - Generate a valid SSWS token with read-only admin permissions for your Okta installation as a service user. For more information, see [Create the token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) and [Service users](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) in Okta's documentation. diff --git a/translations/ko-KR/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/ko-KR/data/reusables/organizations/team-discussions-are-for-orgs.md index cb0f53f8ed..656bb6a3b7 100644 --- a/translations/ko-KR/data/reusables/organizations/team-discussions-are-for-orgs.md +++ b/translations/ko-KR/data/reusables/organizations/team-discussions-are-for-orgs.md @@ -1 +1 @@ -Team discussions are only available on team pages in organizations. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +Team discussions are only available on team pages in organizations. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." diff --git a/translations/ko-KR/data/reusables/organizations/team-synchronization.md b/translations/ko-KR/data/reusables/organizations/team-synchronization.md index a609ef11b9..94743620fb 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" or currentVersion == "github-ae@latest" %} -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)." +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](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/ko-KR/data/reusables/organizations/team_maintainers_can.md b/translations/ko-KR/data/reusables/organizations/team_maintainers_can.md index 586a4657f5..8c68c29077 100644 --- a/translations/ko-KR/data/reusables/organizations/team_maintainers_can.md +++ b/translations/ko-KR/data/reusables/organizations/team_maintainers_can.md @@ -11,5 +11,5 @@ Members with team maintainer permissions can: - [Remove organization members from the team](/articles/removing-organization-members-from-a-team) - [Promote an existing team member to team maintainer](/articles/giving-team-maintainer-permissions-to-an-organization-member) - Remove the team's access to repositories{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -- [Manage code review assignment for the team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} +- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [Manage scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md index d502dc5ee9..1581f1cf5e 100644 --- a/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/ko-KR/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. Create a new personal access token (PAT) with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token. {% warning %} - **Note:** If you select the `write:packages` scope, deselect the `repo` scope when creating the PAT. Adding a PAT with the `repo` scope as a secret in your repository allows the credential to be accessible to all collaborators in the repository. This gives unnecessary additional access when a PAT with the `repo` scope is used within an action. For more information on security best practices for actions, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." + **Note:** By default, when you select the `write:packages` scope for your personal access token (PAT) in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for GitHub Actions workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://github.com/settings/tokens/new?scopes=write:packages`. {% endwarning %} diff --git a/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index fb85de55b5..666a293400 100644 --- a/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/ko-KR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,5 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} +PATs can grant broad access to your account. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}. + To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)." diff --git a/translations/ko-KR/data/reusables/pages/choose-visibility.md b/translations/ko-KR/data/reusables/pages/choose-visibility.md index bd794a90d7..9ed7fac761 100644 --- a/translations/ko-KR/data/reusables/pages/choose-visibility.md +++ b/translations/ko-KR/data/reusables/pages/choose-visibility.md @@ -1 +1 @@ -1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md index fc98787aaa..26d5ca7f58 100644 --- a/translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md +++ b/translations/ko-KR/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md b/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md index 04d4ddeb1c..e8de190b64 100644 --- a/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/ko-KR/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} {% endwarning %} diff --git a/translations/ko-KR/data/reusables/pages/sidebar-pages.md b/translations/ko-KR/data/reusables/pages/sidebar-pages.md new file mode 100644 index 0000000000..41713183cc --- /dev/null +++ b/translations/ko-KR/data/reusables/pages/sidebar-pages.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +1. In the left sidebar, click **Pages**. ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png) +{% endif %} diff --git a/translations/ko-KR/data/reusables/pages/update_your_dns_settings.md b/translations/ko-KR/data/reusables/pages/update_your_dns_settings.md index 67317a2a04..6bb9bacc45 100644 --- a/translations/ko-KR/data/reusables/pages/update_your_dns_settings.md +++ b/translations/ko-KR/data/reusables/pages/update_your_dns_settings.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" %}1. If there's a custom domain enabled for your site, to avoid a domain takeover, update your DNS settings. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-custom-domain-for-your-github-pages-site)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. If there's a custom domain enabled for your site, to avoid a domain takeover, update your DNS settings. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site)."{% endif %} diff --git a/translations/ko-KR/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/ko-KR/data/reusables/pages/www-and-apex-domain-recommendation.md index 83de39755f..f94b04d6d4 100644 --- a/translations/ko-KR/data/reusables/pages/www-and-apex-domain-recommendation.md +++ b/translations/ko-KR/data/reusables/pages/www-and-apex-domain-recommendation.md @@ -1 +1 @@ -If you are using an apex domain as your custom domain, we recommend also setting up a `www` subdomain. If you configure the correct records for each domain type through your DNS provider, {% data variables.product.prodname_pages %} will automatically create redirects between the domains. For example, if you configure `www.example.com` as your custom domain for your site, and you have `ALIAS` and `CNAME` records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." +If you are using an apex domain as your custom domain, we recommend also setting up a `www` subdomain. If you configure the correct records for each domain type through your DNS provider, {% data variables.product.prodname_pages %} will automatically create redirects between the domains. For example, if you configure `www.example.com` as the custom domain for your site, and you have {% data variables.product.prodname_pages %} DNS records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. Note that automatic redirects only apply to the `www` subdomain. Automatic redirects do not apply to any other subdomains, such as `blog`. diff --git a/translations/ko-KR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/ko-KR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index 979cf68329..3dc1d84355 100644 --- a/translations/ko-KR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/ko-KR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -6,6 +6,6 @@ - When [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync), if you remove a person from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync.{% endif %} - You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- 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. For more information, see "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." +- 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. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} diff --git a/translations/ko-KR/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/ko-KR/data/reusables/repositories/sidebar-code-scanning-alerts.md index 90992a248f..e5b3502439 100644 --- a/translations/ko-KR/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ b/translations/ko-KR/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -1 +1 @@ -1. In the left sidebar, click **Code scanning alerts**. Optionally, select the code scanning tool you used. !["Code scanning alerts" tab](/assets/images/help/repository/sidebar-code-scanning-alerts.png) +1. In the left sidebar, click **Code scanning alerts**. !["Code scanning alerts" tab](/assets/images/help/repository/sidebar-code-scanning-alerts.png) diff --git a/translations/ko-KR/data/reusables/saml/about-linked-identities.md b/translations/ko-KR/data/reusables/saml/about-linked-identities.md index 4f489081c2..f879d16402 100644 --- a/translations/ko-KR/data/reusables/saml/about-linked-identities.md +++ b/translations/ko-KR/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. When available, the entry will include SCIM data. For more information, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." If a member links the wrong identity to their {% data variables.product.product_name %} account, you can revoke the linked identity to allow the member to try again. diff --git a/translations/ko-KR/data/reusables/saml/outside-collaborators-exemption.md b/translations/ko-KR/data/reusables/saml/outside-collaborators-exemption.md index f2936af1c5..598f6e88d5 100644 --- a/translations/ko-KR/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/ko-KR/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Outside collaborators aren't required to authenticate with an IdP to access the resources in an organization with SAML SSO. For more information on outside collaborators, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." +**Note:** Outside collaborators aren't required to authenticate with an IdP to access the resources in an organization with SAML SSO. For more information on outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)." {% endnote %} 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 index 0559438bb6..e75538fe3d 100644 --- 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 @@ -7,6 +7,7 @@ | 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 | +| Asana | Asana Personal Access Token | asana_personal_access_token | | 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 | @@ -37,8 +38,12 @@ | 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 | +| Grafana | Grafana API Key | grafana_api_key | | Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | | Hubspot | Hubspot API Key | hubspot_api_key | +| Intercom | Intercom Access Token | intercom_access_token | +| Lob | Lob Live API Key | lob_live_api_key | +| Lob | Lob Test API Key | lob_test_api_key | | Mailchimp | Mailchimp API Key | mailchimp_api_key | | Mailgun | Mailgun API Key | mailgun_api_key | | npm | npm Access Token | npm_access_token | @@ -51,6 +56,7 @@ | Proctorio | Proctorio Secret Key | proctorio_secret_key | | Pulumi | Pulumi Access Token | pulumi_access_token | | PyPI | PyPI API Token | pypi_api_token | +| RubyGems | RubyGems API Key | rubygems_api_key | | Samsara | Samsara API Token | samsara_api_token | | Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | | SendGrid | SendGrid API Key | sendgrid_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 index c9a8d65306..ebc268a20d 100644 --- 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 @@ -50,6 +50,7 @@ | Proctorio | Proctorio Secret Key | | Pulumi | Pulumi Access Token | | PyPI | PyPI API Token | +| RubyGems | RubyGems API Key | | Samsara | Samsara API Token | | Samsara | Samsara OAuth Access Token | | Shopify | Shopify App Shared Secret | diff --git a/translations/ko-KR/data/reusables/sponsors/choose-updates.md b/translations/ko-KR/data/reusables/sponsors/choose-updates.md index ade59cf05b..93f8807013 100644 --- a/translations/ko-KR/data/reusables/sponsors/choose-updates.md +++ b/translations/ko-KR/data/reusables/sponsors/choose-updates.md @@ -1 +1 @@ -4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) +4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/ko-KR/data/reusables/sponsors/click-add-tier.md b/translations/ko-KR/data/reusables/sponsors/click-add-tier.md index 3b8ad38edf..0859f1368e 100644 --- a/translations/ko-KR/data/reusables/sponsors/click-add-tier.md +++ b/translations/ko-KR/data/reusables/sponsors/click-add-tier.md @@ -1 +1 @@ -1. On the bottom of the page, click **Add a tier**. ![Add a tier button](/assets/images/help/sponsors/add-a-tier-button.png) +1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![Add a tier button](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/ko-KR/data/reusables/sponsors/enable-custom-amounts.md b/translations/ko-KR/data/reusables/sponsors/enable-custom-amounts.md new file mode 100644 index 0000000000..1889367cb9 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/enable-custom-amounts.md @@ -0,0 +1,2 @@ +1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png) +1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png) diff --git a/translations/ko-KR/data/reusables/sponsors/feedback.md b/translations/ko-KR/data/reusables/sponsors/feedback.md new file mode 100644 index 0000000000..44c1bb7d3f --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/feedback.md @@ -0,0 +1 @@ +You can share your feedback about {% data variables.product.prodname_sponsors %} with {% data variables.product.company_short %}. To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)." diff --git a/translations/ko-KR/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/ko-KR/data/reusables/sponsors/manage-updates-for-orgs.md index 0cd08d5382..b47ac0599d 100644 --- a/translations/ko-KR/data/reusables/sponsors/manage-updates-for-orgs.md +++ b/translations/ko-KR/data/reusables/sponsors/manage-updates-for-orgs.md @@ -1 +1 @@ -You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)." +You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)." diff --git a/translations/ko-KR/data/reusables/sponsors/pay-prorated-amount.md b/translations/ko-KR/data/reusables/sponsors/pay-prorated-amount.md index f201de957c..32f6b098f7 100644 --- a/translations/ko-KR/data/reusables/sponsors/pay-prorated-amount.md +++ b/translations/ko-KR/data/reusables/sponsors/pay-prorated-amount.md @@ -1 +1 @@ -1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Due today", click **Pay prorated $X.XX today**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file +1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/sponsors/prorated-sponsorship.md b/translations/ko-KR/data/reusables/sponsors/prorated-sponsorship.md index 56a047d867..9e560bf708 100644 --- a/translations/ko-KR/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/ko-KR/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. +If you're starting a monthly sponsorship on behalf of your user account, you'll 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/ko-KR/data/reusables/sponsors/review-and-publish-tier.md b/translations/ko-KR/data/reusables/sponsors/review-and-publish-tier.md index 6d239c6919..a84fd2930a 100644 --- a/translations/ko-KR/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/ko-KR/data/reusables/sponsors/review-and-publish-tier.md @@ -1 +1 @@ -1. Proofread your tier, then click **Publish tier**. ![Publish tier button](/assets/images/help/sponsors/publish-tier-button.png) +1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/ko-KR/data/reusables/sponsors/review-tiers-to-select.md b/translations/ko-KR/data/reusables/sponsors/review-tiers-to-select.md new file mode 100644 index 0000000000..06e7cbd768 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/review-tiers-to-select.md @@ -0,0 +1 @@ +1. On the right side of the page, under "Select a tier", review the sponsorship tiers available. If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png) diff --git a/translations/ko-KR/data/reusables/sponsors/select-a-tier.md b/translations/ko-KR/data/reusables/sponsors/select-a-tier.md index 6ba1b8d427..b126110e6a 100644 --- a/translations/ko-KR/data/reusables/sponsors/select-a-tier.md +++ b/translations/ko-KR/data/reusables/sponsors/select-a-tier.md @@ -1 +1 @@ -1. On the right side of the page, under "Select a tier", review the sponsorship tiers available. Then, to the right of the tier you want, click **Select**. ![Select a tier box](/assets/images/help/sponsors/select-a-tier-box.png) +1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![Select a tier box](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/ko-KR/data/reusables/sponsors/sponsorship-details.md b/translations/ko-KR/data/reusables/sponsors/sponsorship-details.md index 6542580736..5f36b22238 100644 --- a/translations/ko-KR/data/reusables/sponsors/sponsorship-details.md +++ b/translations/ko-KR/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. Your sponsorship will share your account's existing billing date, payment method, and receipt. +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 one-time or monthly payment amounts and benefits that are set by the sponsored account. Your sponsorship will share your account's existing billing date, payment method, and receipt. diff --git a/translations/ko-KR/data/reusables/sponsors/tier-details.md b/translations/ko-KR/data/reusables/sponsors/tier-details.md index 9b80bb5aea..78c40c1054 100644 --- a/translations/ko-KR/data/reusables/sponsors/tier-details.md +++ b/translations/ko-KR/data/reusables/sponsors/tier-details.md @@ -1,3 +1,3 @@ -You can create up to ten sponsorship tiers for sponsors to choose from. Each tier has its own monthly payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. +You can create up to ten sponsorship tiers for sponsors to choose from. Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). -Once you have published a tier, you can't edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier or cancel their sponsorship. +Once you have published a tier, you can't edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/ko-KR/data/reusables/support/accessing-premium-content.md b/translations/ko-KR/data/reusables/support/accessing-premium-content.md index 95aae9361d..36beb80ba8 100644 --- a/translations/ko-KR/data/reusables/support/accessing-premium-content.md +++ b/translations/ko-KR/data/reusables/support/accessing-premium-content.md @@ -1,4 +1,4 @@ ### Accessing premium content -You can access premium content by signing in to the {% data variables.contact.contact_enterprise_portal %}. +You can access premium content by signing in to the {% data variables.contact.contact_landing_page_portal %}. diff --git a/translations/ko-KR/data/reusables/support/contacting-premium-support.md b/translations/ko-KR/data/reusables/support/contacting-premium-support.md index c3e8440e39..5e11eb52c6 100644 --- a/translations/ko-KR/data/reusables/support/contacting-premium-support.md +++ b/translations/ko-KR/data/reusables/support/contacting-premium-support.md @@ -1,4 +1,4 @@ ### Contacting {% data variables.contact.premium_support %} -{% data variables.contact.premium_support %} customers can use the {% data variables.contact.contact_enterprise_portal %} to report issues in writing, in English. You can also receive English-language support over the phone. For the {% data variables.contact.premium_support %} phone number, see "[24x7 Phone Support](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)" in the {% data variables.contact.enterprise_portal %}. +{% data variables.contact.premium_support %} customers can use the {% data variables.contact.contact_landing_page_portal %} to report issues in writing, in English. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/user_settings/billing_plans.md b/translations/ko-KR/data/reusables/user_settings/billing_plans.md new file mode 100644 index 0000000000..8d26ab1479 --- /dev/null +++ b/translations/ko-KR/data/reusables/user_settings/billing_plans.md @@ -0,0 +1 @@ +1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png) diff --git a/translations/ko-KR/data/variables/contact.yml b/translations/ko-KR/data/variables/contact.yml index 890e996840..6af47c26ee 100644 --- a/translations/ko-KR/data/variables/contact.yml +++ b/translations/ko-KR/data/variables/contact.yml @@ -24,9 +24,12 @@ contact_enterprise_portal: '[GitHub Enterprise Support portal](https://enterpris #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)' -#GitHub Support portal (for dotcom) +#GitHub Support portal (for dotcom - this sends users to a contact form) support_portal: 'GitHub Support portal' contact_support_portal: '[GitHub Support portal](https://support.github.com/contact)' +#GitHub Support portal (this sends users to the Support landing page) +landing_page_portal: 'GitHub Support portal' +contact_landing_page_portal: '[GitHub Support portal](https://support.github.com/)' #The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) community_support: 'GitHub Community Support' #The GitHub Community forum 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 5231157111..a3be6f5184 100644 --- a/translations/pt-BR/content/actions/creating-actions/about-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/about-actions.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' topics: - - Desenvolvimento da ação - - Princípios básicos + - 'Desenvolvimento da ação' + - 'Princípios básicos' --- {% 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 698228ee69..a57db31ac4 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 @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'referência' --- {% data reusables.actions.enterprise-beta %} 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 add311f28a..467a64d678 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 @@ -12,7 +12,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'referência' --- {% data reusables.actions.enterprise-beta %} @@ -58,7 +58,7 @@ inputs: Quando você especifica uma entrada para uma ação em um arquivo de fluxo de trabalho ou usa um valor de entrada padrão, o {% data variables.product.prodname_dotcom %} cria uma variável de ambiente para a entrada com o nome `INPUT_`. A variável de ambiente criada altera os nomes de entrada para letras maiúsculas e substitui espaços por caracteres `_`. -Por exemplo, se um fluxo de trabalho definiu as entradas numOctocats e octocatEyeColor, o código da ação lê os valores das entradas usando as variáveis de ambiente `INPUT_NUMOCTOCATS` e `INPUT_OCTOCATEYECOLOR`. +Por exemplo, se um fluxo de trabalho definiu as entradas `numOctocats` e `octocatEyeColor`, o código de ação poderia ler os valores das entradas usando as variáveis de ambiente do `INPUT_NUMTOCATS` e `INPUT_OCTOCATEYECOLOR`. #### `inputs.` @@ -76,6 +76,10 @@ Por exemplo, se um fluxo de trabalho definiu as entradas numOctocats e octocatEy **Opcional**: uma `string` que representa o valor padrão. O valor padrão é usado quando um parâmetro de entrada não é especificado em um arquivo de fluxo de trabalho. +#### `inputs..deprecationMessage` + +**Opcional** Se o parâmetro de entrada for usado, esta `string` será registrada como uma mensagem de aviso. Você pode usar este aviso para notificar os usuários de que o valor de entrada está obsoleto e mencionar outras alternativas. + ### `outputs (saídas)` **Opcional** Os parâmetros de saída permitem que você declare os dados definidos por uma ação. As ações executadas posteriormente em um fluxo de trabalho podem usar os dados de saída definidos em ações executadas anteriormente. Por exemplo, se uma ação executou a adição de duas entradas (x + y = z), a ação poderia usar o resultado da soma (z) como entrada em outras ações. @@ -280,7 +284,7 @@ runs: #### `pre-entrypoint` -**Opcional** Permite que você execute um script antes de a ação do `entrypoint` começar. Por exemplo, você pode usar o `pre-entrypoint:` para executar um pré-requisito do script da configuração. {% data variables.product.prodname_actions %} usa a `execução do docker` para lançar esta ação e executa o script dentro de um novo contêiner que usa a mesma imagem-base. Isso significa que o momento de execução é diferente do contêiner principal doentrypoint e quaisquer status que você precisar devem ser acessados na área de trabalho, em `HOME` ou como uma variável `STATE_`. A ação `pre-entrypoint:` é sempre executada por padrão, mas você pode substituí-la usando [`pre-if`](#pre-if). +**Opcional** Permite que você execute um script antes de a ação do `entrypoint` começar. Por exemplo, você pode usar o `pre-entrypoint:` para executar um pré-requisito do script da configuração. {% data variables.product.prodname_actions %} usa a `execução do docker` para lançar esta ação e executa o script dentro de um novo contêiner que usa a mesma imagem-base. Isso significa que o momento de execução é diferente do contêiner principal do `entrypoint` e qualquer status de que você precisar devem ser acessado na área de trabalho, em `HOME`, ou como uma variável `STATE_`. A ação `pre-entrypoint:` é sempre executada por padrão, mas você pode substituí-la usando [`pre-if`](#pre-if). O aplicativo especificado com a sintaxe [`using`](#runsusing) executará esse arquivo. 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 b7feb41560..ebacaec093 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 @@ -20,10 +20,10 @@ type: 'how_to' O {% data variables.product.prodname_dotcom %} usa o código de saída para definir o status de execução de verificação da ação, que pode ser `sucesso` ou `falha`. -| Status de saída | Status de verificação de execução | Descrição | -| --------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `0` | `success` | A ação foi concluída com êxito, outras tarefas que dependem dela podem começar. | -| Nonzero value (any integer but 0) | `failure` | Qualquer outro código de saída indica falha na ação. Quando uma ação falha, todas as ações simultâneas são canceladas e as ações futuras são ignoradas. A execução de verificação e o conjunto de verificações ficam com status `failure`. | +| Status de saída | Status de verificação de execução | Descrição | +| ---------------------------------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `0` | `success` | A ação foi concluída com êxito, outras tarefas que dependem dela podem começar. | +| Valor diferente de zero (qualquer número inteiro que não seja 0) | `failure` | Qualquer outro código de saída indica falha na ação. Quando uma ação falha, todas as ações simultâneas são canceladas e as ações futuras são ignoradas. A execução de verificação e o conjunto de verificações ficam com status `failure`. | ### Definir um código de saída de falha em uma ação JavaScript 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 e11baa847e..994e4de04b 100644 --- a/translations/pt-BR/content/actions/guides/about-continuous-integration.md +++ b/translations/pt-BR/content/actions/guides/about-continuous-integration.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' topics: - - CI - - CD + - 'CI' + - 'CD' --- {% 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 041142a1bd..4ee8b4f6ed 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 @@ -9,9 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' topics: - - Empacotando + - 'Empacotando' --- {% 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 5e9a1a463e..8a63c558fc 100644 --- a/translations/pt-BR/content/actions/guides/about-service-containers.md +++ b/translations/pt-BR/content/actions/guides/about-service-containers.md @@ -9,10 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' topics: - - Contêineres - - Docker + - 'Contêineres' + - 'Docker' --- {% 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 e033ece1b1..129db4fc16 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Ant run: ant -noinput -buildfile build.xml ``` @@ -70,7 +71,7 @@ jobs: Este fluxo de trabalho executa os seguintes passos: 1. O `checkout` faz o download de uma cópia do seu repositório no executor. -2. A etapa `setup-java` configura o Java 1.8 JDK. +2. A etapa `setup-java` configura o Java 11 JDK pelo Adoptium. 3. A etapa "Criar com Ant" executa o alvo-padrão em seu `build.xml` de modo não interativo. Os modelos-padrão do fluxo de trabalho são excelentes pontos de partida ao criar seu fluxo de trabalho de compilação e teste, e você pode personalizar o modelo para atender às necessidades do seu projeto. @@ -91,9 +92,10 @@ Se você usa comandos diferentes para criar seu projeto ou se você quer executa ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Ant jar target run: ant -noinput -buildfile build-ci.xml jar ``` @@ -109,7 +111,11 @@ De modo geral, o Ant cria arquivos de saída como JARs, EARs ou WARs no diretór ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ant -noinput -buildfile build.xml - uses: actions/upload-artifact@v2 with: 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 399d95c52c..baa99dfffc 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Gradle run: ./gradlew build ``` @@ -70,7 +71,7 @@ jobs: Este fluxo de trabalho executa os seguintes passos: 1. O `checkout` faz o download de uma cópia do seu repositório no executor. -2. A etapa `setup-java` configura o Java 1.8 JDK. +2. A etapa `setup-java` configura o Java 11 JDK pelo Adoptium. 3. A etapa "Criar com Gradle" executa o script wrapper `gradlew` para garantir que o seu código seja criado, o seu teste seja aprovado e que seja possível criar um pacote. Os modelos-padrão do fluxo de trabalho são excelentes pontos de partida ao criar seu fluxo de trabalho de compilação e teste, e você pode personalizar o modelo para atender às necessidades do seu projeto. @@ -91,9 +92,10 @@ Se você usa comandos diferentes para criar seu projeto ou se você desejar usar ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Gradle package task run: ./gradlew -b ci.gradle package ``` @@ -107,10 +109,11 @@ Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, v ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Gradle packages uses: actions/cache@v2 with: @@ -143,7 +146,11 @@ De modo geral, o Gradle cria arquivos de saída como JARs, EARs ou WARs no diret ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ./gradlew build - uses: actions/upload-artifact@v2 with: 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 dcd1d4fb11..fa5de2f1f1 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 @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Maven run: mvn --batch-mode --update-snapshots verify ``` @@ -70,7 +71,7 @@ jobs: Este fluxo de trabalho executa os seguintes passos: 1. O `checkout` faz o download de uma cópia do seu repositório no executor. -2. A etapa `setup-java` configura o Java 1.8 JDK. +2. A etapa `setup-java` configura o Java 11 JDK pelo Adoptium. 3. A etapa "Construir com Maven" executa o `pacote`-alvo Maven alvo de modo não interativo para garantir que seu código de seja criado, o seu teste seja aprovado e que seja possível criar um pacote. Os modelos-padrão do fluxo de trabalho são excelentes pontos de partida ao criar seu fluxo de trabalho de compilação e teste, e você pode personalizar o modelo para atender às necessidades do seu projeto. @@ -91,9 +92,10 @@ Se você usa comandos diferentes para criar seu projeto ou se desejar usar um al ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Maven verify phase run: mvn --batch-mode --update-snapshots verify ``` @@ -107,10 +109,11 @@ Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, v ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Maven packages uses: actions/cache@v2 with: @@ -134,7 +137,10 @@ De modo geral, o Maven criará arquivos de saída como JARs, EARs ou WARs no dir ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 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 index d512b5d11d..893608336b 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-net.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: ['3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -81,7 +81,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet: [ '2.2.103', '3.0', '3.1.x' ] + dotnet: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -201,7 +201,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 diff --git a/translations/pt-BR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/pt-BR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 1c4c36dbd1..3afbd184de 100644 --- a/translations/pt-BR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/pt-BR/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -1,6 +1,6 @@ --- -title: Installing an Apple certificate on macOS runners for Xcode development -intro: 'You can sign Xcode apps within your continuous integration (CI) workflow by installing an Apple code signing certificate on {% data variables.product.prodname_actions %} runners.' +title: Instalar um certificado da Apple em executores do macOS para desenvolvimento do Xcode +intro: 'Você pode assinar aplicativos Xcode na sua integração contínua (CI) instalando um certificado de assinatura de código da Apple nos executores de {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' @@ -18,7 +18,7 @@ topics: ### Introdução -This guide shows you how to add a step to your continuous integration (CI) workflow that installs an Apple code signing certificate and provisioning profile on {% data variables.product.prodname_actions %} runners. This will allow you to sign your Xcode apps for publishing to the Apple App Store, or distributing it to test groups. +Este guia mostra como adicionar uma etapa ao fluxo de trabalho de integração contínua (CI) que instala um certificado de assinatura de código da Apple e o perfil de provisionamento em executores de {% data variables.product.prodname_actions %}. Isso permitirá que você assine seus aplicativos Xcode para publicar na Apple App Store ou distribuí-los para testar grupos. ### Pré-requisitos @@ -27,49 +27,49 @@ Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.produ - "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" - "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)" -You should have an understanding of Xcode app building and signing. For more information, see the [Apple developer documentation](https://developer.apple.com/documentation/). +Você deve ter um entendimento de criação e assinatura do aplicativo Xcode. Para obter mais informações, consulte a [Documentação de desenvolvedor da Apple](https://developer.apple.com/documentation/). -### Creating secrets for your certificate and provisioning profile +### Criar segredos para seu certificado e perfil de provisionamento -The signing process involves storing certificates and provisioning profiles, transferring them to the runner, importing them to the runner's keychain, and using them in your build. +O processo de assinatura envolve o armazenamento de certificados e provisionamento de perfis, transferindo-os para o executor, importando-os para a keychain e usando-os na sua compilação. -To use your certificate and provisioning profile on a runner, we strongly recommend that you use {% data variables.product.prodname_dotcom %} secrets. For more information on creating secrets and using them in a workflow, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +Para usar seu certificado e perfil de provisionamento em um executor, é altamente recomendado que você use segredos de {% data variables.product.prodname_dotcom %}. Para obter mais informações sobre a criação de segredos e usá-los em um fluxo de trabalho, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)". -Create secrets in your repository or organization for the following items: +Crie segredos no seu repositório ou organização para os seguintes itens: -* Your Apple signing certificate. +* Seu certificado de assinatura Apple. - - This is your `p12` certificate file. For more information on exporting your signing certificate from Xcode, see the [Xcode documentation](https://help.apple.com/xcode/mac/current/#/dev154b28f09). + - Este é seu arquivo de certificado `p12`. Para obter mais informações sobre como exportar seu certificado de assinatura a partir do Xcode, consulte a [documentação do Xcode](https://help.apple.com/xcode/mac/current/#/dev154b28f09). - - You should convert your certificate to Base64 when saving it as a secret. In this example, the secret is named `BUILD_CERTIFICATE_BASE64`. + - Você deve converter seu certificado em Base64 ao salvá-lo como um segredo. Neste exemplo, o segredo é denominado `BUILD_CERTIFICATE_BASE64`. - - Use the following command to convert your certificate to Base64 and copy it to your clipboard: + - Use o comando a seguir para converter seu certificado para Base64 e copiá-lo para a sua área de transferência: ```shell base64 build_certificate.p12 | pbcopy ``` -* The password for your Apple signing certificate. - - In this example, the secret is named `P12_PASSWORD`. +* A senha para seu certificado de assinatura da Apple. + - Neste exemplo, o segredo é denominado `P12_PASSWORD`. -* Your Apple provisioning profile. +* O seu perfil de provisionamento da Apple. - - For more information on exporting your provisioning profile from Xcode, see the [Xcode documentation](https://help.apple.com/xcode/mac/current/#/deva899b4fe5). + - Para obter mais informações sobre a exportação do seu perfil de provisionamento a partir do Xcode, consulte a [documentação do Xcode](https://help.apple.com/xcode/mac/current/#/deva899b4fe5). - - You should convert your provisioning profile to Base64 when saving it as a secret. In this example, the secret is named `BUILD_PROVISION_PROFILE_BASE64`. + - Você deve converter o seu perfil de provisionamento para Base64 ao salvá-lo como segredo. Neste exemplo, o segredo é denominado `BUILD_PROVISION_PROFILE_BASE64`. - - Use the following command to convert your provisioning profile to Base64 and copy it to your clipboard: + - Use o comando a seguir para converter o seu perfil de provisionamento para Base64 e copiá-lo para a sua área de transferência: ```shell base64 provisioning_profile.mobileprovision | pbcopy ``` -* A keychain password. +* Uma senha da keychain. - - A new keychain will be created on the runner, so the password for the new keychain can be any new random string. In this example, the secret is named `KEYCHAIN_PASSWORD`. + - Uma nova keychain será criada no executo. Portanto, a senha para a nova keychain pode ser qualquer nova string aleatória. Neste exemplo, o segredo se chama `KEYCHAIN_PASSWORD`. -### Add a step to your workflow +### Adicionar uma etapa ao seu fluxo de trabalho -This example workflow includes a step that imports the Apple certificate and provisioning profile from the {% data variables.product.prodname_dotcom %} secrets, and installs them on the runner. +Este fluxo de trabalho de exemplo inclui uma etapa que importa o certificado da Apple e o perfil de provisionamento dos segredos de {% data variables.product.prodname_dotcom %} e os instala no executor. {% raw %} ```yaml{:copy} @@ -116,13 +116,13 @@ jobs: ``` {% endraw %} -### Required clean-up on self-hosted runners +### Limpeza necessária nos executores auto-hospedados -{% data variables.product.prodname_dotcom %}-hosted runners are isolated virtual machines that are automatically destroyed at the end of the job execution. This means that the certificates and provisioning profile used on the runner during the job will be destroyed with the runner when the job is completed. +Executores hosperados em {% data variables.product.prodname_dotcom %} são máquinas virtuais isoladas destruídas automaticamente no final da execução do trabalho. Isso significa que os certificados e o perfil de provisionamento usados no executor durante o trabalho serão destruídos com o executor quando o trabalho for concluído. -On self-hosted runners, the `$RUNNER_TEMP` directory is cleaned up at the end of the job execution, but the keychain and provisioning profile might still exist on the runner. +Nos executores auto-hospedados, o diretório `$RUNNER_TEMP` é limpo no final da execução do trabalho, mas a keychain e o perfil de provisionamento ainda existem no executor. -If you use self-hosted runners, you should add a final step to your workflow to help ensure that these sensitive files are deleted at the end of the job. The workflow step shown below is an example of how to do this. +Se você usa executores auto-hospedados, você deve adicionar uma última etapa ao seu fluxo de trabalho para ajudar a garantir que esses arquivos sensíveis sejam excluídos no final do trabalho. A etapa do fluxo de trabalho abaixo é um exemplo de como fazer isso. {% raw %} ```yaml 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 cfcaef82a9..e09e6461d9 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 @@ -75,21 +75,22 @@ Na etapa de implementação, você deverá definir variáveis de ambiente para o {% raw %} ```yaml{:copy} -nome: Publicar pacote no Repositório Central do Maven -em: - versão: - tipos: [created] -trabalhos: - publicar: +name: Publish package to the Maven Central Repository +on: + release: + types: [created] +jobs: + publish: runs-on: ubuntu-latest - etapas: - - usa: actions/checkout@v2 - - nome: Configurar Java - usa: actions/setup-java@v1 - com: - java-version: 1.8 - - nome: Publicar pacote - executar: gradle publish + steps: + - uses: actions/checkout@v2 + - name: Set up Java + uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - name: Publish package + run: gradle publish env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -134,20 +135,21 @@ Com essa configuração, é possível criar um fluxo de trabalho que publica seu {% raw %} ```yaml{:copy} -nome: Publicar pacote nos pacotes do GitHub -em: - versão: - tipos: [created] -trabalhos: - publicar: +name: Publish package to GitHub Packages +on: + release: + types: [created] +jobs: + publish: runs-on: ubuntu-latest - etapas: - - usa: actions/checkout@v2 - - usa: actions/setup-java@v1 - com: - java-version: 1.8 - - nome: Publicar pacote - executar: publicação do gradle + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - name: Publish package + run: gradle publish env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` @@ -199,21 +201,22 @@ Com esta configuração, você pode criar um fluxo de trabalho que publica seu p {% raw %} ```yaml{:copy} -nome: Publicar pacote no Repositório Central do Maven e nos Pacotes do GitHub -em: - versão: - tipos: [created] -trabalhos: - publicar: +name: Publish package to the Maven Central Repository and GitHub Packages +on: + release: + types: [created] +jobs: + publish: runs-on: ubuntu-latest - etapas: - - usa: actions/checkout@v2 - - nome: Configura o Java - usa: actions/setup-java@v1 - com: - java-version: 1.8 - - nome: Publica no Repositório Central do Maven - executa: publicação do gradle + steps: + - uses: actions/checkout@v2 + - name: Set up Java + uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - name: Publish to the Maven Central Repository + run: gradle publish env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} 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 877e676a00..8561886f6f 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 @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -147,9 +148,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: mvn --batch-mode deploy env: @@ -183,9 +185,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java for publishing to Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -195,9 +198,10 @@ jobs: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to GitHub Packages run: mvn --batch-mode deploy env: diff --git a/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md b/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md index ce7d8999d2..8c33aafa5c 100644 --- a/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md +++ b/translations/pt-BR/content/actions/guides/scheduling-issue-creation.md @@ -66,7 +66,7 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a ``` {% endraw %} 4. Personalize os parâmetros no seu arquivo do fluxo de trabalho: - - Altere o valor de `on.schagen` para ditar quando você deseja que este fluxo de trabalho seja executado. In the example above, the workflow will run every Monday at 7:20 UTC. Para obter mais informações sobre fluxos de trabalho agendados, consulte "[Eventos agendados](/actions/reference/events-that-trigger-workflows#scheduled-events)". + - Altere o valor de `on.schagen` para ditar quando você deseja que este fluxo de trabalho seja executado. No exemplo acima, o fluxo de trabalho será executado todas as segundas às 7h20 UTC. Para obter mais informações sobre fluxos de trabalho agendados, consulte "[Eventos agendados](/actions/reference/events-that-trigger-workflows#scheduled-events)". - Altere o valor de `responsáveis` para a lista de nomes de usuário de {% data variables.product.prodname_dotcom %} que você deseja atribuir ao problema. - Altere o valor das etiquetas de `` para a lista de etiquetas que você deseja aplicar ao problema. - Altere o valor do `título` para o título que você deseja que o problema tenha. @@ -77,7 +77,7 @@ No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a ### Resultados esperados -Based on the `schedule` parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. Se você definir `fixado` como `verdadeiro`, o fluxo de trabalho irá fixar o problema no repositório. Se você definir `close-previous` como verdadeiro, o fluxo de trabalho fechará o problema mais recente com etiquetas correspondentes. +Baseado no parâmetro `agendar` (por exemplo, toda segunda-feira às 7h20 UTC), seu fluxo de trabalho criará um novo problema com os responsáveis, etiquetas, título e texto que você especificou. Se você definir `fixado` como `verdadeiro`, o fluxo de trabalho irá fixar o problema no repositório. Se você definir `close-previous` como verdadeiro, o fluxo de trabalho fechará o problema mais recente com etiquetas correspondentes. {% data reusables.actions.schedule-delay %} diff --git a/translations/pt-BR/content/actions/guides/using-github-actions-for-project-management.md b/translations/pt-BR/content/actions/guides/using-github-actions-for-project-management.md index c00d568852..9176c2c2d7 100644 --- a/translations/pt-BR/content/actions/guides/using-github-actions-for-project-management.md +++ b/translations/pt-BR/content/actions/guides/using-github-actions-for-project-management.md @@ -1,14 +1,14 @@ --- title: Usar o GitHub Actions para gerenciamento de projetos -intro: 'Você pode usar {% data variables.product.prodname_actions %} para automatizar muitas das suas tarefas de gerenciamento de projeto.' +intro: Você pode usar {% data variables.product.prodname_actions %} para automatizar muitas das suas tarefas de gerenciamento de projeto. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' topics: - - Gerenciamento de projeto + - 'Gerenciamento de projeto' --- Você pode usar {% data variables.product.prodname_actions %} para automatizar suas tarefas de gerenciamento de projeto, criando fluxos de trabalho. Cada fluxo de trabalho contém uma série de tarefas que são executadas automaticamente toda vez que o fluxo de trabalho é executado. Por exemplo, você pode criar um fluxo de trabalho que é executado toda vez que um problema é criado para adicionar uma etiqueta, deixar um comentário e transferir um problema para um quadro de projeto. 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 70accef2ec..3d0ad48377 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -125,7 +125,7 @@ URL de {% data variables.product.prodname_ghe_managed %}. Por exemplo, se o nome da sua instância for `octoghae`, você precisará permitir que o executor auto-hospedado acesse `octoghae.github.com`. Se você usa uma lista de endereços IP para a -conta da sua organização ou empresa de {% data variables.product.prodname_dotcom %}, você deverá adicionar o endereço IP do seu executor auto-hospedado à lista de permissão. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)". +conta da sua organização ou empresa de {% data variables.product.prodname_dotcom %}, você deverá adicionar o endereço IP do seu executor auto-hospedado à lista de permissão. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -145,7 +145,7 @@ pkg-containers.githubusercontent.com pkg-containers-az.githubusercontent.com ``` -Se você usar uma lista de endereços IP permitida para a sua a sua organização ou conta corporativa do {% data variables.product.prodname_dotcom %}, você deverá adicionar o endereço IP do executor auto-hospedado à lista de permissões. Para obter mais informações consulte "[Gerenciar endereços IP permitidos para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" ou "[Aplicar as configurações de segurança na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". +Se você usar uma lista de endereços IP permitida para a sua a sua organização ou conta corporativa do {% data variables.product.prodname_dotcom %}, você deverá adicionar o endereço IP do executor auto-hospedado à lista de permissões. Para obter mais informações consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" ou "[Aplicar as configurações de segurança na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". {% else %} 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 a39ca068a8..16749f126f 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,10 +7,18 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' +type: 'tutorial' --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} + +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)." @@ -44,13 +52,15 @@ 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. {% if currentVersion == "free-pro-team@latest" %} Para adicionar um executor auto-hospedado a uma conta corporativa, você deve ser proprietário da organização. -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} +{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} Para adicionar um executor auto-hospedado no nível de empresa de {% data variables.product.product_location %}, você deve ser um administrador do site. {% endif %} @@ -62,3 +72,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/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 1a1dfbab80..01354493b1 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,11 +7,14 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' type: 'tutorial' --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} Para obter informações sobre como criar etiquetas-padrão e etiquetas personalizadas, consulte "[Usando etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". @@ -29,7 +32,7 @@ Um executor auto-hospedado recebe automaticamente certas etiquetas ao ser adicio * `auto-hospedado`: Etiqueta-padrão aplicada a todos os executores auto-hospedados. * `Linux`, `Windows`, ou `macOS`: Aplicado, dependendo do sistema operacional. -* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. +* `x64`, `ARM`, ou `ARM64`: Aplicado dependendo da arquitetura do hardware. Você pode usar o YAML do seu fluxo de trabalho para enviar trabalhos para uma combinação dessas etiquetas. Neste exemplo, um executor auto-hospedado que corresponde a todas as três etiquetas será elegível para executar a o trabalho: @@ -66,7 +69,7 @@ Estas etiquetas operam cumulativamente. Portanto, as etiquetas de um executor au Ao encaminhar um trabalho para um executor auto-hospedado, {% data variables.product.prodname_dotcom %} procura um executor que corresponde às etiquetas `runs-on` do trabalho: -1. {% data variables.product.prodname_dotcom %} primeiro procura um executor no nível do repositório, depois no nível da organização{% if currentVersion ver_gt "enterprise-server@2.21" %} e, por fim, no nível empresarial{% endif %}. +1. {% data variables.product.prodname_dotcom %} primeiro pesquisa um executor no nível do repositório, depois no nível da organização% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} e, em seguida, no nível corporativo{% endif %}. 2. Em seguida, o trabalho é enviado para o primeiro executor correspondente que está on-line e inativo. - Se todos os executores on-line estiverem ocupados, o trabalho será agendado no nível com o maior número de executores on-line. - Se todos os runners correspondentes estiverem off-line, a tarefa será listada no nível com o maior número de executores off-line correspondentes. diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md index c233057f61..a478e27de8 100644 --- a/translations/pt-BR/content/actions/index.md +++ b/translations/pt-BR/content/actions/index.md @@ -22,8 +22,8 @@ featuredLinks: - /actions/reference/environment-variables - /actions/reference/encrypted-secrets changelog: - label: 'actions' - prefix: 'GitHub Actions: ' + label: 'ações' + prefix: 'GitHub Actions:' product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ 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 c8854079db..9dca00feb6 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' topics: - - Princípios básicos + - 'Princípios básicos' --- {% data reusables.actions.enterprise-beta %} 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 3ee3c1e6f2..291f9a0691 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 @@ -10,9 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'visão Geral' topics: - - Princípios básicos + - 'Princípios básicos' --- {% 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 17dc573c37..a55659f442 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,27 +1,29 @@ --- -title: Managing complex workflows -shortTitle: Managing complex workflows -intro: 'This guide shows you how to use the advanced features of {% data variables.product.prodname_actions %}, with secret management, dependent jobs, caching, build matrices,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} environments,{% endif %} and labels.' +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 segredos, trabalhos dependentes, cache, matrizes de criação{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} ambientes,{% endif %} e etiquetas.' versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' type: 'how_to' topics: - - 'Workflows' + - 'Fluxos de trabalho' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### Overview +### Visão Geral -This article describes some of the advanced features of {% data variables.product.prodname_actions %} that help you work create more complex workflows. +Este artigo descreve alguns dos recursos avançados de {% data variables.product.prodname_actions %} que ajudam você a trabalhar criar fluxos de trabalho mais complexos. -### Storing secrets +### Armazenar segredos -If your workflows use sensitive data, such as passwords or certificates, you can save these in {% data variables.product.prodname_dotcom %} as _secrets_ and then use them in your workflows as environment variables. This means that you will be able to create and share workflows without having to embed sensitive values directly in the YAML workflow. +Se os seus fluxos de trabalho usarem dados confidenciais, como senhas ou certificados, você pode salvá-los em {% data variables.product.prodname_dotcom %} como _segredos_ e usá-los nos seus fluxos de trabalho como variáveis de ambiente. Isto significa que você poderá criar e compartilhar fluxos de trabalho sem ter de incorporar valores sensíveis diretamente no fluxo de trabalho de YAML. -This example action demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command. +Esta ação de exemplo demonstra como fazer referência a um segredo existente como uma variável de ambiente e enviá-lo como um parâmetro para um comando de exemplo. {% raw %} ```yaml @@ -37,13 +39,13 @@ jobs: ``` {% endraw %} -For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." +Para obter mais informações, consulte "[Criar e armazenar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". -### Creating dependent jobs +### Criar trabalhos dependentes -By default, the jobs in your workflow all run in parallel at the same time. So if you have a job that must only run after another job has completed, you can use the `needs` keyword to create this dependency. If one of the jobs fails, all dependent jobs are skipped; however, if you need the jobs to continue, you can define this using the [`if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) conditional statement. +Por padrão, os trabalhos do seu fluxo de trabalho são executadas em paralelo e ao mesmo tempo. Portanto, se você tem um trabalho que só deve ser executado após a conclusão de outro trabalho, você pode usar a palavra-chave `needs` para criar esta dependência. Se um dos trabalhos falhar, todos os trabalhos dependentes serão suprimidos. No entanto, se você precisa que os trabalhos continuem, você pode definir isso usando a declaração condicional [`se`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif). -In this example, the `setup`, `build`, and `test` jobs run in series, with `build` and `test` being dependent on the successful completion of the job that precedes them: +Neste exemplo, os trabalhos de `configuração`, `criação` e `teste` executados em série, com `criação` e `teste` sendo dependentes da conclusão bem-sucedida do trabalho que os precede: ```yaml jobs: @@ -63,11 +65,11 @@ jobs: - run: ./test_server.sh ``` -For more information, see [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). +Para obter mais informações, consulte [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds). -### Using a build matrix +### Usar uma matriz de criação -You can use a build matrix if you want your workflow to run tests across multiple combinations of operating systems, platforms, and languages. The build matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this build matrix will run the job multiple times, using different versions of Node.js: +Você pode usar uma matriz de criação se quiser que seu fluxo de trabalho execute testes em várias combinações de sistemas operacionais, plataformas e linguagens. A matriz de criação é criada usando a palavra-chave `estratégia`, que recebe as opções de compilação como um array. Por exemplo, essa matriz de criação irá executar o trabalho várias vezes, usando diferentes versões do Node.js: {% raw %} ```yaml @@ -84,13 +86,14 @@ jobs: ``` {% endraw %} -For more information, see [`jobs..strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). +Para obter mais informações, consulte [`>jobs..strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix). -### Caching dependencies +{% if currentVersion == "free-pro-team@latest" %} +### Memorizar dependências -{% data variables.product.prodname_dotcom %}-hosted runners are started as fresh environments for each job, so if your jobs regularly reuse dependencies, you can consider caching these files to help improve performance. Once the cache is created, it is available to all workflows in the same repository. +Executores hospedados em {% data variables.product.prodname_dotcom %} são iniciados como ambientes novos para cada trabalho. Portanto, se os seus trabalhos reutilizam dependências regularmente, você pode considerar fazer armazenamento em cache desses arquivos para ajudar a melhorar o desempenho. Após a criação do armazenamento em cache, ele fica disponível para todos os fluxos de trabalho no mesmo repositório. -This example demonstrates how to cache the ` ~/.npm` directory: +Este exemplo demonstra como armazenar em cache o diretório `~/.npm`: {% raw %} ```yaml @@ -109,11 +112,12 @@ jobs: ``` {% endraw %} -For more information, see "Caching dependencies to speed up workflows." +Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +{% endif %} -### Using databases and service containers +### Usar bancos de dados e contêineres de serviço -If your job requires a database or cache service, you can use the [`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) keyword to create an ephemeral container to host the service; the resulting container is then available to all steps in that job and is removed when the job has completed. This example demonstrates how a job can use `services` to create a `postgres` container, and then use `node` to connect to the service. +Se sua tarefa exigir um banco de dados ou serviço de cache, você poderá usar a palavra-chave [`serviços`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) para criar um contêiner efêmero para hospedar o serviço; o contêiner resultante ficará disponível em todas as etapas do trabalho e será removido quando o trabalho for concluído. Este exemplo demonstra como um trabalho pode usar `serviços` para criar um contêiner `postgres` e, em seguida, usar o `nó` para conectar-se ao serviço. ```yaml jobs: @@ -135,39 +139,47 @@ jobs: POSTGRES_PORT: 5432 ``` -For more information, see "[Using databases and service containers](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)." +Para obter mais informações, consulte "[Usar bancos de dados e contêineres de serviço](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)". -### Using labels to route workflows +### Usar etiquetas para encaminhar fluxos de trabalho -This feature helps you assign jobs to a specific self-hosted runner. If you want to be sure that a particular type of runner will process your job, you can use labels to control where jobs are executed. You can assign labels to a self-hosted runner, and then refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way. +Esse recurso ajuda você a atribuir tarefas a um executor hospedado específico. Se você quiser ter certeza de que um determinado tipo de executor irá processar seu trabalho, você pode usar etiquetas para controlar os locais onde os trabalhos são executados. Você pode atribuir etiquetas a um corredor hospedado e, em seguida, consultá-las no fluxo de trabalho de YAML, garantindo que o trabalho seja encaminhado de uma forma previsível. -This example shows how a workflow can use labels to specify the required runner: +{% if currentVersion == "github-ae@latest" %} +Este exemplo mostra como um fluxo de trabalho pode usar etiquetas para especificar o executor obrigatório: +```yaml +jobs: + example-job: + runs-on: [AE-runner-for-CI] +``` + +Para obter mais informações, consulte ["Usar etiquetas com {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners)". +{% else %} ```yaml jobs: example-job: runs-on: [self-hosted, linux, x64, gpu] ``` -For more information, see ["Using labels with self-hosted runners](/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" %} -### Using environments - -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)." +Para obter mais informações, consulte ["Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". {% endif %} -### Using a workflow template +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Usar ambientes + +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. 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) +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) -### Next steps +### Próximas etapas -To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." +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/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/security-hardening-for-github-actions.md index 8656a0c352..eed60ccf6a 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,13 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: overview + github-ae: '*' +type: 'visão Geral' topics: - - Segurança + - 'Segurança' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### Visão Geral @@ -22,7 +24,7 @@ Este guia explica como configurar o fortalecimento de segurança para certos rec ### Usar segredos -Valores sensíveis nunca devem ser armazenados como texto simples em arquivos de fluxo de trabalho, mas como segredos. [Os segredos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) podem ser configurados na organização{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repositório, ambiente{% else %} ou níveis do repositório{% endif %} e permitem que você armazene informações confidenciais em {% data variables.product.product_name %}. +Valores sensíveis nunca devem ser armazenados como texto simples em arquivos de fluxo de trabalho, mas como segredos. [Os segredos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) podem ser configurados no nível da organização{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, repositório, ambiente{% else %} ou repositório {% endif %} e permitir que você armazene informações confidenciais em {% data variables.product.product_name %}. Os segredos usam [caixas fechadas de Libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) de modo que sejam criptografadas antes de atingir {% data variables.product.product_name %}. Isso ocorre quando o segredo é enviado [usando a interface de usuário](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) ou através da [API REST](/rest/reference/actions#secrets). Esta criptografia do lado do cliente ajuda a minimizar os riscos relacionados ao registro acidental (por exemplo, registros de exceções e de solicitação, entre outros) dentro da infraestrutura do {% data variables.product.product_name %}. Uma vez realizado o upload do segredo, o {% data variables.product.product_name %} poderá descriptografá-lo para que possa ser injetado no tempo de execução do fluxo de trabalho. @@ -41,7 +43,7 @@ Para ajudar a prevenir a divulgação acidental, o {% data variables.product.pro - **Audite e gire os segredos registrados** - Reveja, periodicamente, os segredos registrados para confirmar se ainda são necessários. Remova aqueles que não são mais necessários. - Gire os segredos periodicamente para reduzir a janela de tempo durante a qual um segredo comprometido é válido. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - **Considere a necessidade de revisão para acesso a segredos** - Você pode usar revisores necessários para proteger os segredos do ambiente. Um trabalho de fluxo de trabalho não pode acessar segredos de ambiente até que a aprovação seja concedida por um revisor. Para mais informações sobre armazenar segredos em ambientes ou exigir revisões para ambientes, consulte "[segredos criptografados](/actions/reference/encrypted-secrets)" e "[Ambientes](/actions/reference/environments)". {% endif %} @@ -75,7 +77,7 @@ Isso significa que comprometer uma única ação dentro de um fluxo de trabalho ### Considerar acesso entre repositórios -O {% data variables.product.product_name %} tem um escopo intencional para um único repositório por vez. O `GITHUB_TOKEN` concede o mesmo nível de acesso que um usuário com acesso de gravação, porque qualquer usuário com acesso de gravação pode acessar esse token criando ou modificando arquivos de fluxo de trabalho. Os usuários têm permissões específicas para cada repositório. Portanto, fazer com que o `GITHUB_TOKEN` para um repositório conceda acesso a outro impactaria o modelo de permissão {% data variables.product.prodname_dotcom %} se não for implementado cuidadosamente. Da mesma forma, deve-se ter cuidado ao adicionar tokens de autenticação de {% data variables.product.prodname_dotcom %} a um fluxo de trabalho, porque isto também pode afetar o modelo de permissão de {% data variables.product.prodname_dotcom %} concedendo inadvertidamente amplo acesso aos colaboradores. +O {% data variables.product.prodname_actions %} tem um escopo intencional para um único repositório por vez. O `GITHUB_TOKEN` concede o mesmo nível de acesso que um usuário com acesso de gravação, porque qualquer usuário com acesso de gravação pode acessar esse token criando ou modificando arquivos de fluxo de trabalho. Usuários têm permissões específicas para cada repositório. Portanto, permitir que o `GITHUB_TOKEN` de um repositório conceda acesso a outro teria impacto no modelo de permissão de {% data variables.product.prodname_dotcom %} se não fosse implementado cuidadosamente. Da mesma forma, deve-se ter cuidado ao adicionar tokens de autenticação de {% data variables.product.prodname_dotcom %} a um fluxo de trabalho, porque isto também pode afetar o modelo de permissão de {% data variables.product.prodname_dotcom %} concedendo inadvertidamente amplo acesso aos colaboradores. Temos [ um plano no roteiro de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap/issues/74) para suportar um fluxo que permite o acesso de todos os repositórios em {% data variables.product.product_name %}, embora ainda não seja um recurso compatível. Atualmente, a única maneira de executar interações privilegiadas entre repositórios é colocar um token de autenticação do {% data variables.product.prodname_dotcom %} ou chave SSH como um segredo dentro do fluxo de trabalho. Uma vez que muitos tipos de token de autenticação não permitem acesso granular a recursos específicos, há um risco significativo no uso do tipo incorreto de token, pois ele pode conceder acesso muito mais amplo do que o pretendido. @@ -115,33 +117,68 @@ Alguns clientes podem tentar mitigar parcialmente esses riscos implementando sis Você pode usar o log de auditoria para monitorar tarefas administrativas em uma organização. O log de auditoria registra o tipo de ação, quando foi executado, e qual conta de usuário executou a ação. -Por exemplo, você pode usar o log de auditoria para monitorar o evento de `action:org.update_actions_secret`, que controla as alterações nos segredos da organização: ![Entradas do log de auditoria](/assets/images/help/repository/audit-log-entries.png) +Por exemplo, você pode usar o log de auditoria para acompanhar o evento `org.update_actions_secret`, que controla as alterações nos segredos da organização: ![Entradas do log de auditoria](/assets/images/help/repository/audit-log-entries.png) -As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_actions %} que você pode encontrar no log de auditoria. Para obter mais informações sobre como usar o log de auditoria, consulte [Revisar o log de auditoria para a sua organização](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)". +As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_actions %} que você pode encontrar no log de auditoria. Para obter mais informações sobre como usar o log de auditoria, consulte [Revisar o log de auditoria para a sua organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)". + +{% if currentVersion == "free-pro-team@latest" %} +#### Eventos para ambientes + +| Ação | Descrição | +| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.create_actions_secret` | Acionada quando um segredo é criado em um ambiente. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)". | +| `environment.delete` | Acionada quando um ambiente é excluído. Para obter mais informações, consulte ["Excluir um ambiente](/actions/reference/environments#deleting-an-environment)". | +| `environment.remove_actions_secret` | Acionada quando um segredo é removido de um ambiente. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)". | +| `environment.update_actions_secret` | Acionada quando um segredo em um ambiente é atualizado. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)". | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Eventos para alterações nas configurações +| Ação | Descrição | +| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.actions_enabled` | Acionada quando {% data variables.product.prodname_actions %} está habilitado para um repositório. Pode ser visto usando a interface do usuário. Este evento não fica visível quando você acessar o log de auditoria usando a API REST. Para obter mais informações, consulte "[Usar a API REST](#using-the-rest-api)". | +{% endif %} #### Eventos para gerenciamento de segredo -| Ação | Descrição | -| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.create_actions_secret` | Acionado quando um administrador da organização [cria um segredo de {% data variables.product.prodname_actions %}](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization). . | -| `action:org.remove_actions_secret` | Acionado quando um administrador da organização remove um segredo de {% data variables.product.prodname_actions %}. | -| `action:org.update_actions_secret` | Acionado quando um administrador da organização atualiza um segredo de {% data variables.product.prodname_actions %}. | -| `action:repo.create_actions_secret` | Acionado quando um administrador do repositório [cria um segredo de {% data variables.product.prodname_actions %}](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository). | -| `action:repo.remove_actions_secret` | Acionado quando um administrador do repositório remove um segredo de {% data variables.product.prodname_actions %}. | -| `action:repo.update_actions_secret` | Acionado quando um administrador do repositório atualiza um segredo de {% data variables.product.prodname_actions %}. | +| Ação | Descrição | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `org.create_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é criado na organização. Para obter mais informações, consulte "[Criar segredos criptografados para uma organização](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)". | +| `org.remove_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é removido. | +| `org.update_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é atualizado. | +| `repo.create_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é criado em um repositório. Para obter mais informações, consulte "[Criar segredos criptografados para um repositório](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". | +| `repo.remove_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é removido. | +| `repo.update_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é atualizado. | #### Eventos para executores auto-hospedados -| Ação | Descrição | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.register_self_hosted_runner` | Acionado quando um proprietário da organização [registra um novo executor auto-hospedado](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | -| `action:org.remove_self_hosted_runner` | Acionado quando um proprietário da organização [remove um executor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | -| `action:repo.register_self_hosted_runner` | Acionado quando um administrador do repositório [registra um novo executor auto-hospedado](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). | -| `action:repo.remove_self_hosted_runner` | Acionado quando um administrador do repositório [remove um executor auto-hospedado](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository). | +| Ação | Descrição | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% else %} | | +| `enterprise.register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma empresa](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)". | +| `enterprise.remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. | +| `enterprise.runner_group_runners_updated` | Acionada quando a lista de integrantes do grupo de executor é atualizada. Para obter mais informações, consulte "[Definir executores auto-hospedados em um grupo para uma organização](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". | +| `enterprise.self_hosted_runner_updated` | Acionada quando o executor é atualizado. Pode ser visualizado usando a API REST e a interface do usuário. Este evento não está incluído quando você exportar o log de auditoria como dados JSON ou um arquivo CSV. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" e "[Revisar o log de auditoria para a sua organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)".{% endif %} +| `org.register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma organização](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | +| `org.remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. Para obter mais informações, consulte [Remover um executor de uma organização](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | +| `org.runner_group_runners_updated` | Acionada quando a lista de integrantes do grupo de executor é atualizada. Para obter mais informações, consulte "[Definir executores auto-hospedados em um grupo para uma organização](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". | +| `org.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores 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)". | +| `org.self_hosted_runner_updated` | Acionada quando o executor é atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | +| `repo.register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a um repositório](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). ". | +| `repo.remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. Para obter mais informações, consulte "[Remover um executor de um repositório](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | +| `repo.self_hosted_runner_updated` | Acionada quando o executor é atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | #### Eventos para grupos de executores auto-hospedados -| Ação | Descrição | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.runner_group_created` | Acionada quando um administrador da organização [cria um grupo de executores 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` | Acionado quando um administrador da organização remove um grupo de executores auto-hospedados. | -| `action:org.runner_group_renamed` | Acionado quando um administrador da organização renomeia um grupo de executores auto-hospedados. | -| `action:org.runner_group_runners_added` | Acionada quando um administrador da organização [adiciona um executor auto-hospedado a um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | -| `action:org.runner_group_runners_removed` | Acionado quando um administrador da organização remove um grupo de executores auto-hospedados. | +| Ação | Descrição | +| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise.runner_group_created` | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Criar um grupo de um executor auto-hospedado para uma empresa](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)". | +| `enterprise.runner_group_removed` | Acionada quando um grupo de executores auto-hospedados é removido. Para obter mais informações, consulte "[Remover um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | +| `enterprise.runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. | +| `enterprise.runner_group_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-hospedado para um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". | +| `enterprise.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores 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)". | +| `org.runner_group_created` | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Criar um grupo de executores auto-hospedados para uma organização](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | +| `org.runner_group_removed` | Acionada quando um grupo de executores auto-hospedados é removido. Para obter mais informações, consulte "[Remover um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | +| `org.runner_group_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-hospedado para um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". | +| `org.runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. Para obter mais informações, consulte "[Remover um executor auto-hospedado de um grupo para uma organização](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | + +#### Eventos para atividades no fluxo de trabalho + +{% data reusables.actions.actions-audit-events-workflow %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md index d18b984948..06969242de 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -15,7 +15,7 @@ versions: Os trabalhos que fazem referência a um ambiente configurado com os revisores necessários irão aguardar a aprovação antes de serem iniciados. Enquanto um trabalho está aguardando aprovação, ele tem um status de "Aguardando". Se um trabalho não for aprovado em 30 dias, a execução do fluxo de trabalho será automaticamente cancelada. -For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} +Para obter mais informações sobre ambientes e aprovações necessárias, consulte "[Ambientes](/actions/reference/environments). {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} Para obter informações sobre como revisar implantações com a API REST, consulte "[Execuções de fluxo de trabalho](/rest/reference/actions#workflow-runs)."{% endif %} ### Aprovar ou rejeitar um trabalho diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md index edef296874..d3d3155680 100644 --- a/translations/pt-BR/content/actions/quickstart.md +++ b/translations/pt-BR/content/actions/quickstart.md @@ -1,6 +1,6 @@ --- title: Início rápido para GitHub Actions -intro: 'Adicione um fluxo de trabalho do {% data variables.product.prodname_actions %} a um repositório existente em até 5 minutos ou menos.' +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates @@ -19,57 +19,58 @@ topics: ### Introdução -Você só precisa de um repositório de {% data variables.product.prodname_dotcom %} existente para criar e executar um fluxo de trabalho de {% data variables.product.prodname_actions %}. Neste guia, você adicionará um fluxo de trabalho que cria várias linguagens de codificação usando a [Ação de Super-Linter de {% data variables.product.prodname_dotcom %}](https://github.com/github/super-linter). O fluxo de trabalho usa o Super-Linter para validar o seu código-fonte toda vez que um novo commit é subido para o seu repositório. +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. + +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. ### Criar o seu primeiro fluxo de trabalho -1. Do seu repositório no {% data variables.product.prodname_dotcom %}, crie um novo arquivo no diretório `.github/workflows` denominado `superlinter.yml`. Para obter mais informações, consulte "[Criar arquivos](/github/managing-files-in-a-repository/creating-new-files)". -2. Copie o conteúdo de YAML a seguir para o arquivo `superlinter.yml`. **Observação:** Se seu branch-padrão não for `principal`, atualize o valor de `DEFAULT_BRANCH` para corresponder ao nome do branch-padrão do seu repositório. +1. Do seu repositório no {% data variables.product.prodname_dotcom %}, crie um novo arquivo no diretório `.github/workflows` denominado `github-actions-demo.yml`. Para obter mais informações, consulte "[Criar arquivos](/github/managing-files-in-a-repository/creating-new-files)". +2. Copie o conteúdo de YAML a seguir para o arquivo `github-actions-demo.yml`: {% raw %} ```yaml{:copy} - name: Super-Linter - - # Run this workflow every time a new commit pushed to your repository - on: push - + name: GitHub Actions Demo + 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 + Explore-GitHub-Actions: runs-on: ubuntu-latest - steps: - # Checks out a copy of your repository on the ubuntu-latest machine - - name: Checkout code + - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event." + - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!" + - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}." + - name: Check out repository code uses: actions/checkout@v2 + - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner." + - run: echo "🖥️ The workflow is now ready to test your code on the runner." + - name: List files in the repository + run: | + ls ${{ github.workspace }} + - run: echo "🍏 This job's status is ${{ job.status }}." - # 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 executar seu fluxo de trabalho, desça a barra de rolagem da página e selecione **Criar um novo branch para este commit e iniciar um pull request**. Em seguida, para criar um pull request, clique em **Propor novo arquivo**. ![Arquivo do fluxo de trabalho do commit](/assets/images/commit-workflow-file.png) +3. Vá até o final da página e selecione **Criar um novo branch para este commit e iniciar um pull request**. Em seguida, para criar um pull request, clique em **Propor novo arquivo**. ![Arquivo do fluxo de trabalho do commit](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -Fazer commit do arquivo de fluxo de trabalho no repositório aciona o evento `push` e executa seu fluxo de trabalho. +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. ### Visualizar seus resultados do fluxo de trabalho {% 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" or currentVersion == "github-ae@latest" %} -1. Em **Trabalhos** ou no gráfico de visualização, clique no trabalho de **base de código Lint**. ![Lint do trabalho do código-base](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) -{% else %} -1. Na barra lateral esquerda, clique no trabalho **Lint de código-bsee**. ![Lint do trabalho do código-base](/assets/images/help/repository/superlinter-lint-code-base-job.png) -{% endif %} -{% data reusables.repositories.view-failed-job-results-superlinter %} +1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja ver. + + ![Lista de fluxo de trabalho na barra lateral esquerda](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +1. Na lista de execuções do fluxo de trabalho, clique no nome da execução que você deseja visualizar. + + ![Nome da execução do fluxo de trabalho](/assets/images/help/repository/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. + + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. + + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) ### Mais modelos de fluxo de trabalho @@ -77,74 +78,12 @@ Fazer commit do arquivo de fluxo de trabalho no repositório aciona o evento `pu ### Próximas etapas -O fluxo de trabalho do super-linter que você acabou de adicionar é executado sempre que o código é enviado para o seu repositório para ajudá-lo a detectar erros e inconsistências no seu código. Mas este é 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 example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. Mas este é apenas o início do que você pode fazer com {% data variables.product.prodname_actions %}: -- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para obter um tutorial aprofundado -- "[Guias](/actions/guides)" para casos e exemplos específicos de uso -- [github/super-linter](https://github.com/github/super-linter) para obter mais informações sobre a configuração da ação de Super-Linter +- O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos. +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. - +- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para obter um tutorial aprofundado. +- "[Guias](/actions/guides)" para casos e exemplos específicos de uso. diff --git a/translations/pt-BR/content/actions/reference/environment-variables.md b/translations/pt-BR/content/actions/reference/environment-variables.md index 0e2d1a4ce4..71d49a99d5 100644 --- a/translations/pt-BR/content/actions/reference/environment-variables.md +++ b/translations/pt-BR/content/actions/reference/environment-variables.md @@ -22,6 +22,7 @@ versions: Para definir as variáveis do ambiente personalizadas, você deverá especificar as variáveis no arquivo do fluxo de trabalho. Você pode definir as variáveis de ambiente para uma etapa, trabalho ou para todo um fluxo de trabalho, usando as palavras-chave [`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). Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)". +{% raw %} ```yaml jobs: weekday_job: @@ -30,13 +31,14 @@ jobs: DAY_OF_WEEK: Mon steps: - name: "Hello world when it's Monday" - if: env.DAY_OF_WEEK == 'Mon' + if: ${{ env.DAY_OF_WEEK == 'Mon' }} run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" env: FIRST_NAME: Mona middle_name: The Last_Name: Octocat ``` +{% endraw %} Para usar o valor de uma variável de ambiente em um arquivo do fluxo de trabalho, você deve usar o [contexto` env`](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). Se você deseja usar o valor de uma variável de ambiente dentro de um executor, você poderá usar o método normal do sistema operacional do executor para ler variáveis de ambiente. @@ -54,7 +56,7 @@ Você também pode usar o {% if currentVersion == "free-pro-team@latest" or curr | `GITHUB_WORKFLOW` | Nome do fluxo de trabalho. | | `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} | `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} -| `GITHUB_JOB` | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. | +| `GITHUB_JOB` | O [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual. | | `GITHUB_ACTION` | Identificador único (`id`) da ação. | | `GITHUB_ACTIONS` | Definido sempre como `verdadeiro` quando {% data variables.product.prodname_actions %} estiver executando o fluxo de trabalho. Você pode usar esta variável para diferenciar quando os testes estão sendo executados localmente ou por {% data variables.product.prodname_actions %}. | | `GITHUB_ACTOR` | Nome da pessoa ou aplicativo que iniciou o fluxo de trabalho. Por exemplo, `octocat`. | diff --git a/translations/pt-BR/content/actions/reference/environments.md b/translations/pt-BR/content/actions/reference/environments.md index aadcdff404..c5ffbabc03 100644 --- a/translations/pt-BR/content/actions/reference/environments.md +++ b/translations/pt-BR/content/actions/reference/environments.md @@ -16,12 +16,12 @@ versions: Você pode configurar ambientes com regras de proteção e segredos. Quando um trabalho de fluxo de trabalho faz referência a um ambiente, o trabalho não será iniciado até que todas as regras de proteção do ambiente sejam aprovadas. Um trabalho também não pode acessar segredos definidos em ambiente até que todas as regras de proteção do ambiente sejam aprovadas. {% if currentVersion == "free-pro-team@latest" %} -Environment protection rules and environment secrets are only available on public repositories and private repositories on an enterprise plan. If you convert a repository from public to private on a non-enterprise plan, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. Se você converter seu repositório de volta para público, você terá acesso a todas as regras de proteção e segredos de ambiente previamente configurados. +As regras de protecção do ambiente e os segredos de ambiente só estão disponíveis em repositórios públicos e repositórios privados em um plano corporativo. Se você converter um repositório de público para privado em um plano não corporativo, todas as regras de proteção configuradas ou segredos de ambiente serão ignorados e você não será capaz de configurar nenhum ambiente. Se você converter seu repositório de volta para público, você terá acesso a todas as regras de proteção e segredos de ambiente previamente configurados. {% endif %} #### Regras de proteção de ambiente -As normas de proteção do ambiente exigem a aprovação de condições específicas antes que um trabalho que faz referência ao ambiente possa prosseguir. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %} +As normas de proteção do ambiente exigem a aprovação de condições específicas antes que um trabalho que faz referência ao ambiente possa prosseguir. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}Você pode usar regras de proteção do ambiente para exigir uma aprovação manual, atrasar um trabalho ou restringir o ambiente a certos branches.{% else %}Você pode usar as regras de proteção de ambiente para exigir uma aprovação manual ou atrasar um trabalho.{% endif %} ##### Revisores necessários @@ -59,7 +59,7 @@ Os segredos armazenados em um ambiente só estão disponíveis para trabalhos de 1. Insira um nome para o ambiente e clique em **Configurar ambiente**. Os nomes de ambiente não diferenciam maiúsculas de minúsculas. Um nome de ambiente não pode exceder 255 caracteres e deve ser único dentro do repositório. 1. Configure todas as regras de proteção de ambiente ou segredos de ambiente. -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}Você também pode criar e configurar ambientes por meio da API REST. Para obter mais informações, consulte "[Ambientes](/rest/reference/repos#environments)" e "[Segredos](/rest/reference/actions#secrets)."{% endif %} Executar um fluxo de trabalho que faz referência a um ambiente que não existe criará um ambiente com o nome referenciado. O novo ambiente não terá nenhuma regra de proteção ou segredos configurados. Qualquer pessoa que possa editar fluxos de trabalho no repositório pode criar ambientes por meio de um arquivo de fluxo de trabalho, mas apenas os administradores do repositório podem configurar o ambiente. @@ -83,4 +83,4 @@ A exclusão de um ambiente apagará todos os segredos e regras de proteção ass 1. Próximo o ambiente que você deseja excluir, clique em {% octicon "trashcan" aria-label="The trashcan icon" %}. 2. Clique em **Eu entendi, exclua este ambiente**. -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}Você também pode excluir ambientes por meio da API REST. Para obter mais informações, consulte "[Ambientes](/rest/reference/repos#environments)."{% endif %} 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 b910a1acd5..2e1ce3d93e 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 @@ -165,9 +165,9 @@ em: ### Eventos webhook -You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Alguns eventos são acionados por mais de um tipo de atividade. Se mais de um tipo de atividade acionar o evento, especifique quais tipos de atividade ativarão a execução do fluxo de trabalho. Para obter mais informações, consulte "[Webhooks](/webhooks). +Você pode configurar seu fluxo de trabalho para executar quando eventos de webhook forem gerados em {% data variables.product.product_name %}. Alguns eventos são acionados por mais de um tipo de atividade. Se mais de um tipo de atividade acionar o evento, especifique quais tipos de atividade ativarão a execução do fluxo de trabalho. Para obter mais informações, consulte "[Webhooks](/webhooks). -Not all webhook events trigger workflows. For the complete list of available webhook events and their payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." +Nem todos os eventos de webhook acionam fluxos de trabalho. Para obter a lista completa de eventos de webhook disponíveis e suas cargas, consulte "[Eventos e cargas de webhook](/developers/webhooks-and-events/webhook-events-and-payloads)". #### `check_run` diff --git a/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md index 686c7f399e..82a7095316 100644 --- a/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/pt-BR/content/actions/reference/usage-limits-billing-and-administration.md @@ -70,7 +70,7 @@ Além dos limites de uso, você deve garantir que você usa Para obter mais informações, consulte: - [Configurar o período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros no seu repositório](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) -- [Configurar o período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros na sua organização](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [Configurar o período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros na sua organização](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) - [Configurar o período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros na sua empresa](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) {% endif %} @@ -80,7 +80,7 @@ Para obter mais informações, consulte: Para obter mais informações, consulte: - "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para um repositório](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)" -- "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} +- "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Aplicar as políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" para {% data variables.product.prodname_ghe_cloud %}{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} 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 7f99343208..154b4dce58 100644 --- a/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/workflow-syntax-for-github-actions.md @@ -1,7 +1,7 @@ --- -title: Workflow syntax for GitHub Actions -shortTitle: Workflow syntax -intro: A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your workflow configuration. +title: Sintaxe de fluxo de trabalho para o GitHub Actions +shortTitle: Sintaxe de fluxo de trabalho +intro: Um fluxo de trabalho é um processo automatizado configurável constituído de um ou mais trabalhos. Você deve criar um arquivo YAML para definir a configuração do seu fluxo de trabalho. product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/workflow-syntax-for-github-actions @@ -10,50 +10,52 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### About YAML syntax for workflows +### Sobre sintaxe YAML para fluxos de trabalho -Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." +Arquivos de fluxo de trabalho usam sintaxe YAML e devem ter uma extensão de arquivo `.yml` ou `.yaml`. {% data reusables.actions.learn-more-about-yaml %} -You must store workflow files in the `.github/workflows` directory of your repository. +Você deve armazenar os arquivos de fluxo de trabalho no diretório `.github/workflows` do seu repositório. ### `name` -The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository. +Nome do fluxo de trabalho. O {% data variables.product.prodname_dotcom %} exibe os nomes dos fluxos de trabalho na página de ações do repositório. Se você omitir o `nome`, o {% data variables.product.prodname_dotcom %} irá defini-lo como o caminho do arquivo do fluxo de trabalho relativo à raiz do repositório. ### `on` -**Required** The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. You can provide a single event `string`, `array` of events, `array` of event `types`, or an event configuration `map` that schedules a workflow or restricts the execution of a workflow to specific files, tags, or branch changes. For a list of available events, see "[Events that trigger workflows](/articles/events-that-trigger-workflows)." +**Obrigatório**. O nome do evento de {% data variables.product.prodname_dotcom %} que aciona o fluxo de trabalho. Você pode fornecer uma única `string` de evento, um `array` de eventos, um `array` de `types` (tipos) de eventos ou um `map` (mapa) de configuração de eventos que programe um fluxo de trabalho ou restrinja a execução do fluxo de trabalho a alterações em determinados arquivos, tags ou branches. Para obter uma lista de eventos disponíveis, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows)". {% data reusables.github-actions.actions-on-examples %} ### `on..types` -Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is `published`, `unpublished`, `created`, `edited`, `deleted`, or `prereleased`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary. +Seleciona os tipos de atividades que acionarão a execução de um fluxo de trabalho. A maioria dos eventos GitHub são acionados por mais de um tipo de atividade. Por exemplo, o evento para o recurso release (versão) é acionado quando uma versão é `published` (publicada), `unpublished` (a publicação é cancelada), `created` (criada), `edited` (editada), `deleted` (excluída) ou `prereleased` (versão prévia). A palavra-chave `types` (tipos) permite que você limite a atividade que faz com que o fluxo de trabalho seja executado. Quando somente um tipo de atividade aciona um evento de webhook, a palavra-chave `types` (tipos) é desnecessária. -You can use an array of event `types`. For more information about each event and their activity types, see "[Events that trigger workflows](/articles/events-that-trigger-workflows#webhook-events)." +É possível usar um array de `types` (tipos) de evento. Para obter mais informações sobre cada evento e seus tipos de atividades, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows#webhook-events)". ```yaml -# Trigger the workflow on pull request activity +# Aciona o fluxo de trabalho na atividade de pull request on: release: - # Only use the types keyword to narrow down the activity types that will trigger your workflow. + # Usa apenas a palavra-chave types (tipos) para limitar os tipos de atividades que acionam o fluxo de trabalho. types: [published, created, edited] ``` ### `on..` -When using the `push` and `pull_request` events, you can configure a workflow to run on specific branches or tags. For a `pull_request` event, only branches and tags on the base are evaluated. If you define only `tags` or only `branches`, the workflow won't run for events affecting the undefined Git ref. +Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado em branches ou tags específicos. Para um evento de `pull_request`, são avaliados apenas os branches e tags na base. Se você definir apenas `tags` ou `branches`, o fluxo de trabalho não será executado para eventos que afetam o Git ref indefinido. -The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one branch or tag name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." +As palavras-chave `branches`, `branches-ignore`, `tags` e `tags-ignore` aceitam padrões glob que usam os caracteres curinga `*` e `**` para coincidir com mais de um nome de branch ou tag. Para obter mais informações, consulte a "[Folha de consulta de filtro padrão](#filter-pattern-cheat-sheet)". -#### Example including branches and tags +#### Exemplo com branches e tags -The patterns defined in `branches` and `tags` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**` will match the `refs/heads/releases/10` Git ref. +Os padrões definidos nos `branches` e `tags` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**` corresponderá ao Git ref `refs/heads/releases/10`. ```yaml on: @@ -72,37 +74,37 @@ on: - v1.* # Push events to v1.0, v1.1, and v1.9 tags ``` -#### Example ignoring branches and tags +#### Exemplo desconsiderando branches e tags -Anytime a pattern matches the `branches-ignore` or `tags-ignore` pattern, the workflow will not run. The patterns defined in `branches-ignore` and `tags-ignore` are evaluated against the Git ref's name. For example, defining the pattern `mona/octocat` in `branches` will match the `refs/heads/mona/octocat` Git ref. The pattern `releases/**-alpha` in `branches` will match the `refs/releases/beta/3-alpha` Git ref. +Sempre que um padrão corresponde ao padrão `branches-ignore` ou `tags-ignore`, o fluxo de trabalho não será executado. Os padrões definidos em `branches-ignore` e `tags-ignore` são avaliados relativamente ao nome do Git ref. Por exemplo, definir o padrão `mona/octocat` nos `branches` corresponde ao Git ref `refs/heads/mona/octocat`. O padrão `releases/**-alpha` em `branches` corresponderá ao Git ref `refs/releases/beta/3-alpha`. ```yaml -on: +em: push: - # Sequence of patterns matched against refs/heads + # Sequência de padrões que correspondem a refs/heads branches-ignore: - # Push events to branches matching refs/heads/mona/octocat + # Push de eventos para branches que correspondem a refs/heads/mona/octocat - 'mona/octocat' - # Push events to branches matching refs/heads/releases/beta/3-alpha + # Push de eventos para branches que correspondem a refs/heads/releases/beta/3-alpha - 'releases/**-alpha' - # Sequence of patterns matched against refs/tags + # Sequência de padrões que correspondem a refs/tags tags-ignore: - v1.* # Push events to tags v1.0, v1.1, and v1.9 ``` -#### Excluding branches and tags +#### Excluir branches e tags -You can use two types of filters to prevent a workflow from running on pushes and pull requests to tags and branches. -- `branches` or `branches-ignore` - You cannot use both the `branches` and `branches-ignore` filters for the same event in a workflow. Use the `branches` filter when you need to filter branches for positive matches and exclude branches. Use the `branches-ignore` filter when you only need to exclude branch names. -- `tags` or `tags-ignore` - You cannot use both the `tags` and `tags-ignore` filters for the same event in a workflow. Use the `tags` filter when you need to filter tags for positive matches and exclude tags. Use the `tags-ignore` filter when you only need to exclude tag names. +Você pode usar dois tipos de filtros para impedir a execução de um fluxo de trabalho em pushes e pull requests para tags e branches. +- `branches` ou `branches-ignore` - não é possível usar os dois filtros `branches` e `branches-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `branches` quando você precisa filtrar branches para correspondências positivas e excluir branches. Use o filtro `branches-ignore` quando você só precisa excluir nomes de branches. +- `tags` ou `tags-ignore` - não é possível usar os dois filtros `tags` e `tags-ignore` para o mesmo evento em um fluxo de trabalho. Use o filtro `tags` quando você precisa filtrar tags para correspondências positivas e excluir tags. Use o filtro `tags-ignore` quando você só precisa excluir nomes de tags. -#### Example using positive and negative patterns +#### Exemplo com padrões positivos e negativos -You can exclude `tags` and `branches` using the `!` character. The order that you define patterns matters. - - A matching negative pattern (prefixed with `!`) after a positive match will exclude the Git ref. - - A matching positive pattern after a negative match will include the Git ref again. +Você pode excluir `tags` e `branches` usando o caractere `!`. A ordem de definição dos padrões é importante. + - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o Git ref. + - Um padrão positivo correspondente após uma correspondência negativa incluirá a Git ref novamente. -The following workflow will run on pushes to `releases/10` or `releases/beta/mona`, but not on `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern. +O fluxo de trabalho a seguir será executado em pushes para `releases/10` ou `releases/beta/mona`, mas não em `releases/10-alpha` ou `releases/beta/3-alpha`, pois o padrão negativo `!releases/**-alpha` está na sequência do padrão positivo. ```yaml on: @@ -114,13 +116,13 @@ on: ### `on..paths` -When using the `push` and `pull_request` events, you can configure a workflow to run when at least one file does not match `paths-ignore` or at least one modified file matches the configured `paths`. Path filters are not evaluated for pushes to tags. +Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado quando pelo menos um arquivo não corresponde a `paths-ignore` ou pelo menos um arquivo modificado corresponde ao `paths` configurado. Flitros de caminho não são avaliados em pushes para tags. -The `paths-ignore` and `paths` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." +As palavras-chave `paths-ignore` e `paths` aceitam padrões glob que usam os caracteres curinga `*` e `**` para coincidir com mais de um nome de caminho. Para obter mais informações, consulte a "[Folha de consulta de filtro padrão](#filter-pattern-cheat-sheet)". -#### Example ignoring paths +#### Exemplo desconsiderando caminhos -Anytime a path name matches a pattern in `paths-ignore`, the workflow will not run. {% data variables.product.prodname_dotcom %} evaluates patterns defined in `paths-ignore` against the path name. A workflow with the following path filter will only run on `push` events that include at least one file outside the `docs` directory at the root of the repository. +Quando todos os caminhos de nome correspondem a padrões em `paths-ignore`, o fluxo de trabalho não será executado. O {% data variables.product.prodname_dotcom %} avalia os padrões definidos em `paths-ignore` com relação ao nome do caminho. Um fluxo de trabalho com o seguinte filtro de caminho só será executado em eventos `push` que tiverem pelo menos um arquivo fora do diretório `docs` na raiz do repositório. ```yaml on: @@ -129,9 +131,9 @@ on: - 'docs/**' ``` -#### Example including paths +#### Exemplo incluindo caminhos -If at least one path matches a pattern in the `paths` filter, the workflow runs. To trigger a build anytime you push a JavaScript file, you can use a wildcard pattern. +Se pelo menos um caminho corresponder a um padrão no filtro `paths`, o fluxo de trabalho será executado. Para acionar uma compilação sempre que você fizer push de um arquivo JavaScript, você pode usar um padrão curinga. ```yaml on: @@ -140,19 +142,19 @@ on: - '**.js' ``` -#### Excluding paths +#### Excluir caminhos -You can exclude paths using two types of filters. You cannot use both of these filters for the same event in a workflow. -- `paths-ignore` - Use the `paths-ignore` filter when you only need to exclude path names. -- `paths` - Use the `paths` filter when you need to filter paths for positive matches and exclude paths. +Você pode excluir caminhos com dois tipos de filtros. Não é possível usar ambos os filtros para o mesmo evento em um fluxo de trabalho. +- `paths-ignore` - use o filtro `paths-ignore` quando você precisa somente excluir nomes de caminhos. +- `paths` - use o filtro `paths` quando você precisa filtrar caminhos para correspondências positivas e excluir caminhos. -#### Example using positive and negative patterns +#### Exemplo com padrões positivos e negativos -You can exclude `paths` using the `!` character. The order that you define patterns matters: - - A matching negative pattern (prefixed with `!`) after a positive match will exclude the path. - - A matching positive pattern after a negative match will include the path again. +Você pode excluir `paths` usando o caractere `!`. A ordem de definição dos padrões é importante: + - Um padrão negativo (precedido por `!`) depois de uma correspondência positiva excluirá o caminho. + - Um padrão positivo correspondente após uma correspondência negativa incluirá o caminho novamente. -This example runs anytime the `push` event includes a file in the `sub-project` directory or its subdirectories, unless the file is in the `sub-project/docs` directory. For example, a push that changed `sub-project/index.js` or `sub-project/src/index.js` will trigger a workflow run, but a push changing only `sub-project/docs/readme.md` will not. +Este exemplo é executado sempre que o evento `push` inclui um arquivo no diretório `sub-project` ou seus subdiretórios, a menos que o arquivo esteja no diretório `sub-project/docs`. Por exemplo, um push que alterou `sub-project/index.js` ou `sub-project/src/index.js` acionará uma execução de fluxo de trabalho, mas um push que altere somente`sub-project/docs/readme.md` não acionará. ```yaml on: @@ -162,55 +164,55 @@ on: - '!sub-project/docs/**' ``` -#### Git diff comparisons +#### Comparações Git diff {% note %} -**Note:** If you push more than 1,000 commits, or if {% data variables.product.prodname_dotcom %} does not generate the diff due to a timeout (diffs that are too large diffs), the workflow will always run. +**Observação:** se você fizer push de mais de 1.000 commits ou se o {% data variables.product.prodname_dotcom %} não gera o diff devido a um tempo limite esgotado (diffs muito grandes), o fluxo de trabalho sempre será executado. {% endnote %} -The filter determines if a workflow should run by evaluating the changed files and running them against the `paths-ignore` or `paths` list. If there are no files changed, the workflow will not run. +O filtro determina se um fluxo de trabalho deve ser executado avaliando os arquivos alterados e comparando-os à lista de `paths-ignore` ou `paths`. Se não houver arquivos alterados, o fluxo de trabalho não será executado. -{% data variables.product.prodname_dotcom %} generates the list of changed files using two-dot diffs for pushes and three-dot diffs for pull requests: -- **Pull requests:** Three-dot diffs are a comparison between the most recent version of the topic branch and the commit where the topic branch was last synced with the base branch. -- **Pushes to existing branches:** A two-dot diff compares the head and base SHAs directly with each other. -- **Pushes to new branches:** A two-dot diff against the parent of the ancestor of the deepest commit pushed. +O {% data variables.product.prodname_dotcom %} gera a lista de arquivos alterados usando diffs de dois pontos para pushes e diffs de três pontos para pull requests: +- **Pull requests:** diffs de três pontos são uma comparação entre a versão mais recente do branch de tópico e o commit onde o branch de tópico foi sincronizado pela última vez com o branch de base. +- **Pushes para branches existentes:** um diff de dois pontos compara os SHAs head e base, um com o outro. +- **Pushes para novos branches:** um diff de dois pontos compara o principal do ancestral do commit mais extenso que foi feito push. -For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)." +Para obter mais informações, consulte "[Sobre comparação de branches em pull requests](/articles/about-comparing-branches-in-pull-requests)". ### `on.schedule` {% data reusables.repositories.actions-scheduled-workflow-example %} -For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)." +Para obter mais informações sobre a sintaxe cron, consulte "[Eventos que acionam fluxos de trabalho](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)". ### `env` -A `map` of environment variables that are available to all jobs and steps in the workflow. You can also set environment variables that are only available to a job or step. For more information, see [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +Um `mapa` das variáveis de ambiente que estão disponíveis para as etapas de todos os trabalhos do fluxo de trabalho. Também é possível definir variáveis de ambiente que estão disponíveis apenas para as etapas de um único trabalho ou para uma única etapa. Para obter mais informações, consulte [`jobs..env`](#jobsjob_idenv) e [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### Example +#### Exemplo ```yaml env: SERVER: production ``` -### `defaults` +### `padrões` -A `map` of default settings that will apply to all jobs in the workflow. You can also set default settings that are only available to a job. For more information, see [`jobs..defaults`](#jobsjob_iddefaults). +Um `mapa` das configurações-padrão que serão aplicadas a todos os trabalhos do fluxo de trabalho. Você também pode definir as configurações-padrão disponíveis para um trabalho. Para obter mais informações, consulte [`jobs..defaults`](#jobsjob_iddefaults). {% data reusables.github-actions.defaults-override %} ### `defaults.run` -You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a workflow. You can also set default settings for `run` that are only available to a job. For more information, see [`jobs..defaults.run`](#jobsjob_iddefaultsrun). You cannot use contexts or expressions in this keyword. +Você pode fornecer opções-padrão de `shell` e `working-directory` para todas as etapas de [`executar`](#jobsjob_idstepsrun) em um fluxo de trabalho. Você também pode definir as configurações-padrão para `execução` apenas disponíveis para um trabalho. Para obter mais informações, consulte [`jobs..defaults.run`](#jobsjob_iddefaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave. {% data reusables.github-actions.defaults-override %} -#### Example +#### Exemplo ```yaml defaults: @@ -221,19 +223,19 @@ defaults: ### `jobs` -A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs..needs` keyword. +A execução de um fluxo de trabalho consiste em um ou mais trabalhos. Por padrão, os trabalhos são executados paralelamente. Para executar trabalhos sequencialmente, você pode definir dependências em outros trabalhos usando a palavra-chave `jobs..needs`. -Each job runs in a runner environment specified by `runs-on`. +Cada trabalho é executado em um ambiente de executor especificado por `runs-on`. -You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. +Você pode executar quantos trabalhos desejar, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados. -If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." +Se você precisar encontrar o identificador exclusivo de um trabalho e execução em um fluxo de trabalho, você poderá usar a API {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Trabalhos do fluxo de trabalho](/rest/reference/actions#workflow-jobs)". ### `jobs.` -Each job must have an id to associate with the job. The key `job_id` is a string and its value is a map of the job's configuration data. You must replace `` with a string that is unique to the `jobs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. +Cada trabalho deve ter um id associado. A chave `job_id` é uma string, e seu valor é um mapa dos dados de configuração do trabalho. Você deve substituir `` por uma string exclusiva para o objeto `jobs`. `` deve começar por uma letra ou `_`, além de conter somente caracteres alfanuméricos, `-` ou `_`. -#### Example +#### Exemplo ```yaml jobs: @@ -245,13 +247,13 @@ jobs: ### `jobs..name` -The name of the job displayed on {% data variables.product.prodname_dotcom %}. +Nome do trabalho no {% data variables.product.prodname_dotcom %}. ### `jobs..needs` -Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. +Identifica todos os trabalhos a serem concluídos com êxito antes da execução deste trabalho. Esse código pode ser uma string ou array de strings. Se houver falha em um trabalho, todos os trabalhos que dependem dele serão ignorados, a menos que os trabalhos usem uma expressão condicional que faça o trabalho continuar. -#### Example requiring dependent jobs to be successful +#### Exemplo que exige que trabalhos dependentes sejam bem sucedidos ```yaml jobs: @@ -262,15 +264,15 @@ jobs: needs: [job1, job2] ``` -In this example, `job1` must complete successfully before `job2` begins, and `job3` waits for both `job1` and `job2` to complete. +Neste exemplo, `job1` deve ser concluído com êxito antes do início de `job2`, e `job3` aguarda a conclusão de `job1` e `job2`. -The jobs in this example run sequentially: +Os trabalhos neste exemplo são executados sequencialmente: 1. `job1` 2. `job2` 3. `job3` -#### Example not requiring dependent jobs to be successful +#### Exemplo que não exige que trabalhos dependentes sejam bem sucedidos ```yaml jobs: @@ -282,58 +284,75 @@ jobs: needs: [job1, job2] ``` -In this example, `job3` uses the `always()` conditional expression so that it always runs after `job1` and `job2` have completed, regardless of whether they were successful. For more information, see "[Context and expression syntax](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)." +Neste exemplo, `job3` usa a expressão condicional `always()` para que ela sempre seja executada depois de `job1` e `job2` terem sido concluídos, independentemente de terem sido bem sucedidos. Para obter mais informações, consulte "[sintaxe de contexto e expressão](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)". ### `jobs..runs-on` -**Required** The type of machine to run the job on. The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner. +**Obrigatório**. O tipo de máquina na qual se executa o trabalho. A máquina pode ser ou um executor hospedado em {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado. +{% if currentVersion == "github-ae@latest" %} +#### {% data variables.actions.hosted_runner %}s + +Se você usar um {% data variables.actions.hosted_runner %}, cada trabalho será executado em uma instância atualizada de um ambiente virtual especificado por `runs-on`. + +##### Exemplo + +```yaml +runs-on: [AE-runner-for-CI] +``` + +Para obter mais informações, consulte "[Sobre {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)". + +{% else %} {% data reusables.actions.enterprise-github-hosted-runners %} -#### {% data variables.product.prodname_dotcom %}-hosted runners +#### Runners hospedados no {% data variables.product.prodname_dotcom %} -If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a virtual environment specified by `runs-on`. +Se você usar um executor hospedado no {% data variables.product.prodname_dotcom %}, cada trabalho será executado em uma nova instância de um ambiente virtual especificado por `runs-on`. -Available {% data variables.product.prodname_dotcom %}-hosted runner types are: +Os tipos de executor disponíveis para {% data variables.product.prodname_dotcom %} são: {% data reusables.github-actions.supported-github-runners %} -{% data reusables.github-actions.ubuntu-runner-preview %} +{% data reusables.github-actions.macos-runner-preview %} -##### Example +##### Exemplo ```yaml runs-on: ubuntu-latest ``` -For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." +Para obter mais informações, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". +{% endif %} -#### Self-hosted runners +#### Executores auto-hospedados + +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### Example +##### Exemplo ```yaml runs-on: [self-hosted, linux] ``` -For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." +Para obter mais informações, consulte "[Sobre executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)" e "[Usar executores auto-hospedados em um fluxo de trabalho](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} ### `jobs..environment` -The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +O ambiente ao qual o trabalho faz referência. Todas as regras de proteção do ambiente têm de ser aprovadas para que um trabalho que faça referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Ambientes](/actions/reference/environments)". -You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)." +Você pode fornecer o ambiente apenas como o `nome` do ambiente, ou como um objeto de ambiente com o `nome` e `url`. A URL é mapeada com `environment_url` na API de implantações. Para obter mais informações sobre a API de implantações, consulte "[Implantações](/rest/reference/repos#deployments)". -##### Example using a single environment name +##### Exemplo de uso de um único nome de ambiente ```yaml -environment: staging_environment +ambiente: staging_environment ``` -##### Example using environment name and URL +##### Exemplo de uso de nome de ambiente e URL ```yaml environment: @@ -341,9 +360,9 @@ environment: url: https://github.com ``` -The URL can be an expression and can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +A URL pode ser uma expressão e pode usar qualquer contexto, exceto o contexto de `segredos`. Para obter mais informações sobre expressões, consulte "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -#### Example +#### Exemplo {% raw %} ```yaml environment: @@ -355,13 +374,13 @@ environment: ### `jobs..outputs` -A `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs..needs`](#jobsjob_idneeds). +Um `mapa` de saídas para um trabalho. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre a definição de dependências de trabalhos, consulte [`jobs..needs`](#jobsjob_idneeds). -Job outputs are strings, and job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}. +As saídas de trabalho são strings e saídas de trabalho que contêm expressões são avaliadas no executor ao final de cada trabalho. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}. -To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)." +Para usar as saídas de trabalho em um trabalho dependente, você poderá usar o contexto `needs`. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)". -#### Example +#### Exemplo {% raw %} ```yaml @@ -387,11 +406,11 @@ jobs: ### `jobs..env` -A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps[*].env`](#jobsjob_idstepsenv). +Um `map` (mapa) das variáveis de ambiente que estão disponíveis para todos as etapas do trabalho. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou uma etapa individual. Para obter mais informações, consulte [`env`](#env) e [`jobs..steps[*].env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### Example +#### Exemplo ```yaml jobs: @@ -402,19 +421,19 @@ jobs: ### `jobs..defaults` -A `map` of default settings that will apply to all steps in the job. You can also set default settings for the entire workflow. For more information, see [`defaults`](#defaults). +Um `mapa` com as configurações- padrão que serão aplicadas a todas as etapas do trabalho. Você também pode definir as configurações-padrão para todo o fluxo de trabalho. Para obter mais informações, consulte [`padrão`](#defaults). {% data reusables.github-actions.defaults-override %} ### `jobs..defaults.run` -Provide default `shell` and `working-directory` to all `run` steps in the job. Context and expression are not allowed in this section. +Forneça o `shell` e `working-directory` para todas as etapas do trabalho `executar`. Não são permitidos contexto e expressão nesta seção. -You can provide default `shell` and `working-directory` options for all [`run`](#jobsjob_idstepsrun) steps in a job. You can also set default settings for `run` for the entire workflow. For more information, see [`jobs.defaults.run`](#defaultsrun). You cannot use contexts or expressions in this keyword. +Você pode fornecer as opções-padrão de `shell` e `working-directory` para todas as etapas de [`execução`](#jobsjob_idstepsrun) de um trabalho. Você também pode definir as configurações-padrão para `execução` para todo o fluxo de trabalho. Para obter mais informações, consulte [`jobs.defaults.run`](#defaultsrun). Você não pode usar contextos ou expressões nesta palavra-chave. {% data reusables.github-actions.defaults-override %} -#### Example +#### Exemplo ```yaml jobs: @@ -428,17 +447,17 @@ jobs: ### `jobs..if` -You can use the `if` conditional to prevent a job from running unless a condition is met. You can use any supported context and expression to create a conditional. +Você pode usar a condicional `if` (se) para evitar que um trabalho seja executado a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional. -{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". ### `jobs..steps` -A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job. +Trabalhos contêm sequências de tarefas chamadas `steps`. As etapas podem executar comandos, executar trabalhos de configuração ou executar ações no seu repositório, em repositórios públicos, ou ações publicadas em registros do Docker. Nem todas as etapas executam ações, mas todas as ações são executadas como etapas. Cada etapa é executada em seu próprio processo no ambiente do executor, tendo acesso ao espaço de trabalho e ao sistema de arquivos. Como as etapas são executadas em seus próprios processos, as alterações nas variáveis de ambiente não são preservadas entre as etapas. O {% data variables.product.prodname_dotcom %} fornece etapas integradas para configurar e concluir trabalhos. -You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. +Você pode executar quantas etapas quiser, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte "[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" para limites de uso de executores auto-hospedados. -#### Example +#### Exemplo {% raw %} ```yaml @@ -464,17 +483,17 @@ jobs: ### `jobs..steps[*].id` -A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +Identificador exclusivo da etapa. Você pode usar `id` para fazer referência à etapa em contextos. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". ### `jobs..steps[*].if` -You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional. +Você pode usar a condicional `if` (se) para evitar que uma etapa trabalho seja executada a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional. -{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -#### Example using contexts +#### Exemplo usando contextos - This step only runs when the event type is a `pull_request` and the event action is `unassigned`. + Essa etapa somente é executada quando o tipo de evento é uma `pull_request` e a ação do evento é `unassigned` (não atribuída). ```yaml steps: @@ -483,9 +502,9 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -#### Example using status check functions +#### Exemplo usando funções de verificação de status -The `my backup step` only runs when the previous step of a job fails. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)." +A função `my backup step` (minha etapa de backup) somente é executada quando houver falha em uma etapa anterior do trabalho. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)". ```yaml steps: @@ -498,27 +517,27 @@ steps: ### `jobs..steps[*].name` -A name for your step to display on {% data variables.product.prodname_dotcom %}. +Nome da etapa no {% data variables.product.prodname_dotcom %}. ### `jobs..steps[*].uses` -Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/). +Seleciona uma ação para executar como parte de uma etapa no trabalho. A ação é uma unidade reutilizável de código. Você pode usar uma ação definida no mesmo repositório que o fluxo de trabalho, um repositório público ou em uma [imagem publicada de contêiner Docker](https://hub.docker.com/). -We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update. -- Using the commit SHA of a released action version is the safest for stability and security. -- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work. -- Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break. +É altamente recomendável incluir a versão da ação que você está usando ao especificar um número de tag Docker, SHA ou ref do Git. Se você não especificar uma versão, ela poderá interromper seus fluxos de trabalho ou causar um comportamento inesperado quando o proprietário da ação publicar uma atualização. +- Usar o commit SHA de uma versão de ação lançada é a maneira mais garantida de obter estabilidade e segurança. +- Usar a versão principal da ação permite receber correções importantes e patches de segurança sem perder a compatibilidade. Fazer isso também garante o funcionamento contínuo do fluxo de trabalho. +- Usar o branch-padrão de uma ação pode ser conveniente, mas se alguém lançar uma nova versão principal com uma mudança significativa, seu fluxo de trabalho poderá ter problemas. -Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required. +Algumas ações requerem entradas que devem ser definidas com a palavra-chave [`with`](#jobsjob_idstepswith) (com). Revise o arquivo README da ação para determinar as entradas obrigatórias. -Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on). +Ações são arquivos JavaScript ou contêineres Docker. Se a ação em uso for um contêiner do Docker, você deverá executar o trabalho em um ambiente do Linux. Para obter mais detalhes, consulte [`runs-on`](#jobsjob_idruns-on). -#### Example using versioned actions +#### Exemplo usando ações com versão ```yaml steps: # Reference a specific commit - - uses: actions/setup-node@74bc508 + - uses: actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e # Reference the major version of a release - uses: actions/setup-node@v1 # Reference a minor version of a release @@ -527,11 +546,11 @@ steps: - uses: actions/setup-node@main ``` -#### Example using a public action +#### Exemplo usando uma ação pública `{owner}/{repo}@{ref}` -You can specific branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository. +Você pode especificar um branch, ref ou SHA em um repositório público {% data variables.product.prodname_dotcom %}. ```yaml jobs: @@ -545,11 +564,11 @@ jobs: uses: actions/aws@v2.0.1 ``` -#### Example using a public action in a subdirectory +#### Exemplo usando uma ação pública em um subdiretório `{owner}/{repo}/{path}@{ref}` -A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA. +Subdiretório em um repositório público do {% data variables.product.prodname_dotcom %} em um branch, ref ou SHA específico. ```yaml jobs: @@ -559,11 +578,11 @@ jobs: uses: actions/aws/ec2@main ``` -#### Example using action in the same repository as the workflow +#### Exemplo usando a ação no mesmo repositório que o fluxo de trabalho `./path/to/dir` -The path to the directory that contains the action in your workflow's repository. You must check out your repository before using the action. +Caminho para o diretório que contém a ação no repositório do seu fluxo de trabalho. Você deve reservar seu repositório antes de usar a ação. ```yaml jobs: @@ -575,50 +594,86 @@ jobs: uses: ./.github/actions/my-action ``` -#### Example using a Docker Hub action +#### Exemplo usando uma ação do Docker Hub `docker://{image}:{tag}` -A Docker image published on [Docker Hub](https://hub.docker.com/). +Imagem Docker publicada no [Docker Hub](https://hub.docker.com/). ```yaml -jobs: +empregos: my_first_job: - steps: - - name: My first step - uses: docker://alpine:3.8 + passos: + - nome: Meu primeiro passo + usa: docker://alpine:3.8 ``` -#### Example using a Docker public registry action +{% if currentVersion == "free-pro-team@latest" %} +##### Exemplo de uso de {% data variables.product.prodname_github_container_registry %} `docker://{host}/{image}:{tag}` -A Docker image in a public registry. +Uma imagem do Docker no {% data variables.product.prodname_github_container_registry %}. +```yaml +jobs: + meu_primeiro_trabalho: + steps: + - name: minha primeira etapa + uses: docker://ghcr.io/OWNER/IMAGE_NAME +``` +{% endif %} +##### Exemplo usando uma ação do registro público do Docker Hub + +`docker://{host}/{image}:{tag}` + +Imagem Docker em um registro público. Este exemplo usa o Registro de Contêiner do Google em `gcr.io`. + +```yaml +jobs: + meu_primeiro_trabalho: + steps: + - name: minha primeira etapa + uses: docker://gcr.io/cloud-builders/gradle +``` + +#### Exemplo de uso de ação dentro de um repositório privado diferente do fluxo de trabalho + +Seu fluxo de trabalho deve fazer checkout no repositório privado e referenciar a ação localmente. + +{% raw %} ```yaml jobs: my_first_job: steps: - - name: My first step - uses: docker://gcr.io/cloud-builders/gradle + - name: Check out repository + uses: actions/checkout@v2 + with: + repository: octocat/my-private-repo + ref: v1.0 + token: ${{ secrets.GITHUB_TOKEN }} + path: ./.github/actions/my-private-repo + - name: Run my action + uses: ./.github/actions/my-private-repo/my-action ``` +{% endraw %} ### `jobs..steps[*].run` -Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command. +Executa programas de linha de comando usando o shell do sistema operacional. Se você não informar um `name`, o nome da etapa será configurado por padrão como o texto indicado no comando `run`. -Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see "[Using a specific shell](#using-a-specific-shell)." +Por padrão, os comandos run usam shells de não login. Você pode escolher um shell diferente e personalizar o shell usado para executar comandos. Para obter mais informações, consulte "[Usar um shell específico](#using-a-specific-shell)". -Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. For example: +Cada palavra-chave `run` representa um novo processo e shell no ambiente do executor. Quando você fornece comandos de várias linhas, cada linha será executada no mesmo shell. Por exemplo: -* A single-line command: +* Um comando de linha única: ```yaml - name: Install Dependencies run: npm install ``` -* A multi-line command: +* Um comando de várias linhas: ```yaml - name: Clean install dependencies and build @@ -627,7 +682,7 @@ Each `run` keyword represents a new process and shell in the runner environment. npm run build ``` -Using the `working-directory` keyword, you can specify the working directory of where to run the command. +Com a palavra-chave `working-directory` (diretório de trabalho), é possível especificar o diretório de trabalho de onde o comando será executado. ```yaml - name: Clean temp directory @@ -635,20 +690,21 @@ Using the `working-directory` keyword, you can specify the working directory of working-directory: ./temp ``` -#### Using a specific shell +#### Usar um shell específico -You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. +Você pode anular as configurações padrão de shell no sistema operacional do executor usando a palavra-chave `shell`. É possível usar palavras-chave integradas a `shell` ou definir um conjunto personalizado de opções de shell. -| Supported platform | `shell` parameter | Description | Command run internally | -|--------------------|-------------------|-------------|------------------------| -| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` | -| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` | -| All | `python` | Executes the python command. | `python {0}` | -| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | This is the default shell used on Windows. The Desktop PowerShell. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. | +| Plataforma compatível | Parâmetro `shell` | Descrição | Comando executado internamente | +| --------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| Todas | `bash` | O shell padrão em plataformas que não sejam Windows como uma alternativa para `sh`. Ao especificar um shell bash no Windows, é utilizado o shell bash incluído no Git para Windows. | `bash --noprofile --norc -eo pipefail {0}` | +| Todas | `pwsh` | Powershell Core. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. | `pwsh -command ". '{0}'"` | +| Todas | `python` | Executa o comando python. | `python {0}` | +| Linux / macOS | `sh` | Comportamento alternativo para plataformas que não sejam Windows se nenhum shell for fornecido e o `bash` não for encontrado no caminho. | `sh -e {0}` | +| Windows | `cmd` | O {% data variables.product.prodname_dotcom %} anexa a extensão `.cmd` ao nome do script e a substitui por `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | Essa é a shell padrão usada no Windows. Powershell Core. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. Se o seu executor do Windows auto-hospedado não tiver o _PowerShell Core_ instalado, será usado o _PowerShell Desktop_. | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | O PowerShell Desktop. O {% data variables.product.prodname_dotcom %} anexa a extensão `.ps1` ao nome do script. | `powershell -command ". '{0}'"`. | -#### Example running a script using bash +#### Exemplo de execução de um script usando bash: ```yaml steps: @@ -657,7 +713,7 @@ steps: shell: bash ``` -#### Example running a script using Windows `cmd` +#### Exemplo de execução de um script usando Windows `cmd` ```yaml steps: @@ -666,7 +722,7 @@ steps: shell: cmd ``` -#### Example running a script using PowerShell Core +#### Exemplo de execução de um script usando PowerShell Core ```yaml steps: @@ -675,7 +731,16 @@ steps: shell: pwsh ``` -#### Example running a python script +#### Exemplo: Usar o PowerShell Desktop para executar um script + +```yaml +steps: + - name: Display the path + run: echo ${env:PATH} + shell: powershell +``` + +#### Exemplo de execução de um script python ```yaml steps: @@ -686,35 +751,53 @@ steps: shell: python ``` -#### Custom shell +#### Shell personalizado -You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`. +Você pode usar o valor `shell` em um string modelo usando `command […options] {0} [..more_options]`. O {% data variables.product.prodname_dotcom %} interpreta a primeira palavra da string delimitada por um espaço em branco como o comando e insere o nome do arquivo para o script temporário em `{0}`. -#### Exit codes and error action preference +Por exemplo: -For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts. +```yaml +steps: + - name: Display the environment variables and their values + run: | + print %ENV + shell: perl {0} +``` + +O comando usado, `perl` neste exemplo, deve ser instalado no executor. + + +{% if currentVersion == "github-ae@latest" %}Para instruções instruções sobre como ter certeza de que o seu {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". +{% else %} +Para informações sobre o software incluído nos executores hospedados no GitHub, consulte "[Especificações para os executores hospedados no GitHub](/actions/reference/specifications-for-github-hosted-runners#supported-software)." +{% endif %} + +#### Preferências de ação de erro e códigos de saída + +Para palavras-chave de shell integradas, fornecemos os seguintes padrões usados por executores hospedados no {% data variables.product.prodname_dotcom %}. Você deve seguir estas diretrizes quando executar scripts shell. - `bash`/`sh`: - - Fail-fast behavior using `set -e o pipefail`: Default for `bash` and built-in `shell`. It is also the default when you don't provide an option on non-Windows platforms. - - You can opt out of fail-fast and take full control by providing a template string to the shell options. For example, `bash {0}`. - - sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code. + - Comportamento de falha rápido que usa `set -eo pipefail`: Padrão para `bash` e `shell` embutido. Também é o padrão quando você não der opção em plataformas que não sejam Windows. + - Você pode cancelar o fail-fast e assumir o controle fornecendo uma string de modelo para as opções do shell. Por exemplo, `bash {0}`. + - Shells do tipo sh saem com o código de saída do último comando executado em um script, que também é o comportamento padrão das ações. O executor relatará o status da etapa como falha/êxito com base nesse código de saída. - `powershell`/`pwsh` - - Fail-fast behavior when possible. For `pwsh` and `powershell` built-in shell, we will prepend `$ErrorActionPreference = 'stop'` to script contents. - - We append `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` to powershell scripts so action statuses reflect the script's last exit code. - - Users can always opt out by not using the built-in shell, and providing a custom shell option like: `pwsh -File {0}`, or `powershell -Command "& '{0}'"`, depending on need. + - Comportamento fail-fast quando possível. Para shell integrado `pwsh` e `powershell`, precederemos `$ErrorActionPreference = 'stop'` para conteúdos de script. + - Vincularemos `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` a scripts powershell para que os status da ação reflitam o código de saída mais recente do script. + - Os usuários podem sempre optar por não usar o shell integrado e fornecer uma opção personalizada, como: `pwsh -File {0}` ou `powershell -Command "& '{0}'"`, dependendo da situação. - `cmd` - - There doesn't seem to be a way to fully opt into fail-fast behavior other than writing your script to check each error code and respond accordingly. Because we can't actually provide that behavior by default, you need to write this behavior into your script. - - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. This behavior is internally consistent with the previous `sh` and `pwsh` default behavior and is the `cmd.exe` default, so this behavior remains intact. + - Parece não haver uma forma de optar totalmente por um comportamento fail-fast que não seja gravar seu script para verificar cada código de erro e reagir de acordo. Como não podemos fornecer esse comportamento por padrão, você precisa gravá-lo em seu script. + - `cmd.exe` sairá com o nível de erro do último programa que executou e retornará o código de erro para o executor. Este comportamento é internamente consistente o padrão de comportamento anterior `sh` e `pwsh`, e é o padrão `cmd.exe`; portanto, ele fica intacto. ### `jobs..steps[*].with` -A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case. +Um `map` (mapa) dos parâmetros de entrada definidos pela ação. Cada parâmetro de entrada é um par chave/valor. Parâmetros de entrada são definidos como variáveis de ambiente. A variável é precedida por `INPUT_` e convertida em letras maiúsculas. -#### Example +#### Exemplo -Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables. +Define os três parâmetros de entrada (`first_name`, `middle_name` e `last_name`) definidos pela ação `hello_world`. Essas variáveis de entrada estarão acessíveis para a ação `hello-world` como variáveis de ambiente `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` e `INPUT_LAST_NAME`. ```yaml jobs: @@ -730,9 +813,9 @@ jobs: ### `jobs..steps[*].with.args` -A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. An `array of strings` is not supported by this parameter. +Uma `string` que define as entradas para um contêiner Docker. O {% data variables.product.prodname_dotcom %} entrega os `args` ao `ENTRYPOINT` do contêiner quando o contêiner inicia. Um `array de strings` não é compatível com esse parâmetro. -#### Example +#### Exemplo {% raw %} ```yaml @@ -745,17 +828,17 @@ steps: ``` {% endraw %} -The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference: +`args` são usados em substituição à instrução `CMD` em um `Dockerfile`. Se você usar `CMD` no `Dockerfile`, use as diretrizes ordenadas por preferência: -1. Document required arguments in the action's README and omit them from the `CMD` instruction. -1. Use defaults that allow using the action without specifying any `args`. -1. If the action exposes a `--help` flag, or something similar, use that as the default to make your action self-documenting. +1. Documente os argumentos necessários no README das ações e omita-os da instrução `CMD`. +1. Use padrões que permitam o uso da ação sem especificação de `args`. +1. Se a ação expõe um sinalizador `--help` ou similar, use isso como padrão para que a ação se documente automaticamente. ### `jobs..steps[*].with.entrypoint` -Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run. +Anula o `ENTRYPOINT` Docker no `Dockerfile` ou define-o caso ainda não tenha sido especificado. Diferentemente da instrução Docker `ENTRYPOINT` que tem um formulário shell e exec, a palavra-chave `entrypoint` aceita apena uma única string que define o executável. -#### Example +#### Exemplo ```yaml steps: @@ -765,83 +848,83 @@ steps: entrypoint: /a/different/executable ``` -The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. +A palavra-chave `entrypoint` é para ser usada com ações de contêiner Docker, mas você também pode usá-la com ações JavaScript que não definem nenhuma entrada. ### `jobs..steps[*].env` -Sets environment variables for steps to use in the runner environment. You can also set environment variables for the entire workflow or a job. For more information, see [`env`](#env) and [`jobs..env`](#jobsjob_idenv). +Define variáveis de ambiente para etapas a serem usadas no ambiente do executor. Também é possível definir variáveis de ambiente para todo o fluxo de trabalho ou para um trabalho. Para obter mais informações, consulte [`env`](#env) e [`jobs..env`](#jobsjob_idenv). {% data reusables.repositories.actions-env-var-note %} -Public actions may specify expected environment variables in the README file. If you are setting a secret in an environment variable, you must set secrets using the `secrets` context. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +Ações públicas podem especificar variáveis de ambiente esperadas no arquivo LEIAME. Se você está configurando um segredo em uma variável de ambiente, use o contexto `secrets`. Para obter mais informações, consulte "[Usar variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)e "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -#### Example +#### Exemplo {% raw %} ```yaml steps: - - name: My first action - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - FIRST_NAME: Mona - LAST_NAME: Octocat + - name: minha primeira ação + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + FIRST_NAME: Mona + LAST_NAME: Octocat ``` {% endraw %} ### `jobs..steps[*].continue-on-error` -Prevents a job from failing when a step fails. Set to `true` to allow a job to pass when this step fails. +Impede a falha de um trabalho se uma etapa não funcionar. Defina `true` (verdadeiro) para permitir que um trabalho aconteça quando essa etapa falhar. ### `jobs..steps[*].timeout-minutes` -The maximum number of minutes to run the step before killing the process. +Número máximo de minutos para executar a etapa antes de interromper o processo. ### `jobs..timeout-minutes` -The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360 +Número máximo de minutos para permitir a execução de um trabalho o antes que o {% data variables.product.prodname_dotcom %} o cancele automaticamente. Padrão: 360 ### `jobs..strategy` -A strategy creates a build matrix for your jobs. You can define different variations to run each job in. +Estratégias criam matrizes de compilação para os trabalhos. Você pode definir variações diferentes variações nas quais executar os trabalhos. ### `jobs..strategy.matrix` -You can define a matrix of different job configurations. A matrix allows you to create multiple jobs by performing variable substitution in a single job definition. For example, you can use a matrix to create jobs for more than one supported version of a programming language, operating system, or tool. A matrix reuses the job's configuration and creates a job for each matrix you configure. +Você pode definir uma matriz de diferentes configurações de trabalho. Uma matriz permite que você crie vários trabalhos que realizam a substituição de variável em uma definição de trabalho único. Por exemplo, você pode usar uma matriz para criar trabalhos para mais de uma versão compatível de uma linguagem de programação, sistema operacional ou ferramenta. Uma matriz reutiliza a configuração do trabalho e cria trabalho para cada matriz que você configurar. {% data reusables.github-actions.usage-matrix-limits %} -Each option you define in the `matrix` has a key and value. The keys you define become properties in the `matrix` context and you can reference the property in other areas of your workflow file. For example, if you define the key `os` that contains an array of operating systems, you can use the `matrix.os` property as the value of the `runs-on` keyword to create a job for each operating system. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +Cada opção que você define na `matriz` tem uma chave e um valor. As chaves que você define tornam-se propriedades no contexto da `matriz` e você pode fazer referência à propriedade em outras áreas do seu arquivo de fluxo de trabalho. Por exemplo, se você definir a chave `os` que contém um array de sistemas operacionais, você poderá usar a propriedade `matrix.os` como o valor da palavra-chave `runs-on` para criar um trabalho para cada sistema operacional. Para obter mais informações, consulte "[Contexto e sintaxe de expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. +A ordem que você define uma `matriz` importa. A primeira opção que você definir será a primeira que será executada no seu fluxo de trabalho. -#### Example running with more than one version of Node.js +#### Exemplo de execução com mais de uma versão do Node.js -You can specify a matrix by supplying an array for the configuration options. For example, if the runner supports Node.js versions 6, 8, and 10, you could specify an array of those versions in the `matrix`. +Você pode especificar uma matriz ao fornecer um array para as opções de configuração. Por exemplo, se o executor for compatível com as versões 6, 8 e 10 do Node.js versões, você poderá especificar um array dessas versões na `matriz`. -This example creates a matrix of three jobs by setting the `node` key to an array of three Node.js versions. To use the matrix, the example sets the `matrix.node` context property as the value of the `setup-node` action's input parameter `node-version`. As a result, three jobs will run, each using a different Node.js version. +Este exemplo cria uma matriz de três trabalhos, definindo a chave `nó` para um array de três versões do Node.js. Para usar a matriz, o exemplo define a propriedade do contexto `matrix.node` como o valor do parâmetro `setup-node` de entrada da ação `node-version`. Como resultado, três trabalhos serão executados, cada uma usando uma versão diferente do Node.js. {% raw %} ```yaml -strategy: - matrix: - node: [6, 8, 10] -steps: - # Configures the node version used on GitHub-hosted runners - - uses: actions/setup-node@v1 - with: - # The Node.js version to configure +estratégia: + matriz: + nó: [6, 8, 10] +etapas: + # Configura a versão do nó usada nos executores hospedados no GitHub + - usa: actions/setup-node@v1 + com: + # A versão do Node.js a ser configurada node-version: ${{ matrix.node }} ``` {% endraw %} -The `setup-node` action is the recommended way to configure a Node.js version when using {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see the [`setup-node`](https://github.com/actions/setup-node) action. +A ação setup-node `` é a forma recomendada de configurar uma versão do Node.js ao usar executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a ação [`setup-node`](https://github.com/actions/setup-node). -#### Example running with more than one operating system +#### Exemplo de execução com mais de um sistema operacional -You can create a matrix to run workflows on more than one runner operating system. You can also specify more than one matrix configuration. This example creates a matrix of 6 jobs: +Você pode criar uma matriz para executar fluxos de trabalho em mais de um sistema operacional do executor. Você também pode especificar mais de uma configuração da matriz. Este exemplo cria uma matriz de 6 trabalhos: -- 2 operating systems specified in the `os` array -- 3 Node.js versions specified in the `node` array +- 2 sistemas operacionais especificados na array `os` +- 3 versões do Node.js especificadas na array do `nó` {% data reusables.repositories.actions-matrix-builds-os %} @@ -859,11 +942,13 @@ steps: ``` {% endraw %} -To find supported configuration options for {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." +{% if currentVersion == "github-ae@latest" %}Para encontrar opções de configuração suportadas para {% data variables.actions.hosted_runner %}s, consulte "[Especificações de software](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)". +{% else %}Para encontrar opções de configuração compatíveis com executores hospedados em {% data variables.product.prodname_dotcom %}, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)." +{% endif %} -#### Example including additional values into combinations +#### Exemplo de inclusão valores adicionais em combinações -You can add additional configuration options to a build matrix job that already exists. For example, if you want to use a specific version of `npm` when the job that uses `windows-latest` and version 4 of `node` runs, you can use `include` to specify that additional option. +Você pode adicionar opções de configurações para um trabalho de matriz de compilação existente. Por exemplo, se você quer usar uma versão específica do `npm` quando o trabalho que usa o `windows-latest` e a versão 4 do `nó` é executado, você pode usar `incluir` para especificar a opção adicional. {% raw %} ```yaml @@ -881,9 +966,9 @@ strategy: ``` {% endraw %} -#### Example including new combinations +#### Exemplo de inclusão novas combinações -You can use `include` to add new jobs to a build matrix. Any unmatched include configurations are added to the matrix. For example, if you want to use `node` version 12 to build on multiple operating systems, but wanted one extra experimental job using node version 13 on Ubuntu, you can use `include` to specify that additional job. +Você pode usar `incluir` para adicionar novos trabalhos a uma matriz de criação. Qualquer configuração sem correspondência de incluir será adicionadas à matriz. Por exemplo, se você quiser usar a versão 12 do `nó` para compilar em vários sistemas operacionais, mas quiser uma tarefa experimental extra usando o node 13 no Ubuntu, você poderá usar `incluir` para especificar essa tarefa adicional. {% raw %} ```yaml @@ -899,9 +984,9 @@ strategy: ``` {% endraw %} -#### Example excluding configurations from a matrix +#### Exemplo excluindo configurações de uma matriz -You can remove a specific configurations defined in the build matrix using the `exclude` option. Using `exclude` removes a job defined by the build matrix. The number of jobs is the cross product of the number of operating systems (`os`) included in the arrays you provide, minus any subtractions (`exclude`). +Você pode remover uma configuração específica definida na matriz de compilação usando a opção `exclude` (excluir). `exclude` remove um trabalho definido pela matriz de compilação. O número de trabalhos é o produto cruzado do número de sistemas operacionais (`os`) incluídos nos arrays fornecidos por você, menos quaisquer subtrações (`exclude`). {% raw %} ```yaml @@ -919,23 +1004,23 @@ strategy: {% note %} -**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded. +**Observação:** Todas as combinações de `incluir` são processadas depois de `excluir`. Isso permite que você use `incluir` para voltar a adicionar combinações que foram excluídas anteriormente. {% endnote %} -##### Using environment variables in a matrix +##### Usando variáveis de ambiente em uma matriz -You can add custom environment variables for each test combination by using the `include` key. You can then refer to the custom environment variables in a later step. +Você pode adicionar variáveis de ambiente personalizadas para cada combinação de testes usando a chave `include`. Em seguida, você pode se referir às variáveis de ambiente personalizadas em um passo posterior. {% data reusables.github-actions.matrix-variable-example %} ### `jobs..strategy.fail-fast` -When set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs if any `matrix` job fails. Default: `true` +Quando definido como `true`, o {% data variables.product.prodname_dotcom %} cancela todos os trabalhos em andamento em caso de falha de algum trabalho de `matrix`. Padrão: `true` ### `jobs..strategy.max-parallel` -The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. By default, {% data variables.product.prodname_dotcom %} will maximize the number of jobs run in parallel depending on the available runners on {% data variables.product.prodname_dotcom %}-hosted virtual machines. +Número máximo de trabalhos que podem ser executados simultaneamente ao usar uma estratégia de trabalho de `matrix`. Por padrão, o {% data variables.product.prodname_dotcom %} maximizará o número de trabalhos executados em paralelo dependendo dos executores disponíveis nas máquinas virtuais hospedadas no {% data variables.product.prodname_dotcom %}. ```yaml strategy: @@ -944,11 +1029,11 @@ strategy: ### `jobs..continue-on-error` -Prevents a workflow run from failing when a job fails. Set to `true` to allow a workflow run to pass when this job fails. +Impede que ocorra falha na execução de um fluxo de trabalho quando ocorrer uma falha em um trabalho. Defina como `verdadeiro` para permitir que uma execução de um fluxo de trabalho passe quando este trabalho falhar. -#### Example preventing a specific failing matrix job from failing a workflow run +#### Exemplo do impedimento de uma matriz falha específica de gerar uma falha na execução do fluxo de trabalho -You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `13` to fail without failing the workflow run. +Você pode permitir que as tarefas específicas em uma matriz de tarefas falhem sem que ocorra falha na execução do fluxo de trabalho. Por exemplo, se você deseja permitir apenas um trabalho experimental com o `nó` definido como `13` sem falhar a execução do fluxo de trabalho. {% raw %} ```yaml @@ -969,11 +1054,11 @@ strategy: ### `jobs..container` -A container to run any steps in a job that don't already specify a container. If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts. +Contêiner para executar qualquer etapa em um trabalho que ainda não tenha especificado um contêiner. Se você tiver etapas que usam ações de script e de contêiner, as ações de contêiner serão executadas como contêineres irmãos na mesma rede e com as mesmas montagens de volume. -If you do not set a `container`, all steps will run directly on the host specified by `runs-on` unless a step refers to an action configured to run in a container. +Se você não definir um `container`, todas as etapas serão executadas diretamente no host especificado por `runs-on`, a menos que uma etapa se refira a uma ação configurada para execução em um contêiner. -#### Example +#### Exemplo ```yaml jobs: @@ -989,7 +1074,7 @@ jobs: options: --cpus 1 ``` -When you only specify a container image, you can omit the `image` keyword. +Ao especificar somente uma imagem de contêiner, você pode omitir a palavra-chave `image`. ```yaml jobs: @@ -999,15 +1084,15 @@ jobs: ### `jobs..container.image` -The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name. +Imagem Docker a ser usada como contêiner para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um {% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2.23" %}nome de registro{% endif %} público. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} ### `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -#### Example +#### Exemplo {% raw %} ```yaml @@ -1022,23 +1107,23 @@ container: ### `jobs..container.env` -Sets a `map` of environment variables in the container. +Define um `mapa` das variáveis de ambiente no contêiner. ### `jobs..container.ports` -Sets an `array` of ports to expose on the container. +Define um `array` de portas para expor no contêiner. ### `jobs..container.volumes` -Sets an `array` of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. +Define um `array` de volumes para uso do contêiner. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host. -To specify a volume, you specify the source and destination path: +Para especificar um volume, especifique o caminho de origem e destino: `:`. -The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. +`` é um nome de volume ou caminho absoluto na máquina host, e `` é um caminho absoluto no contêiner. -#### Example +#### Exemplo ```yaml volumes: @@ -1049,49 +1134,49 @@ volumes: ### `jobs..container.options` -Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." +Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". ### `jobs..services` {% data reusables.github-actions.docker-container-os-support %} -Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner automatically creates a Docker network and manages the life cycle of the service containers. +Usado para hospedar contêineres de serviço para um trabalho em um fluxo de trabalho. Contêineres de serviço são úteis para a criação de bancos de dados ou serviços armazenamento em cache como o Redis. O executor cria automaticamente uma rede do Docker e gerencia o ciclo de vida dos contêineres do serviço. -If you configure your job to run in a container, or your step uses container actions, you don't need to map ports to access the service or action. Docker automatically exposes all ports between containers on the same Docker user-defined bridge network. You can directly reference the service container by its hostname. The hostname is automatically mapped to the label name you configure for the service in the workflow. +Se você configurar seu trabalho para ser executado em um contêiner, ou a sua etapa usar ações ao contêiner, você não precisará mapear as portas para acessar o serviço ou a ação. O Docker expõe automaticamente todas as portas entre os contêineres da mesma rede de ponte definida pelo usuário. Você pode fazer referência ao contêiner de serviço diretamente pelo seu nome de host. O nome do host é mapeado automaticamente com o nome da etiqueta que você configurar para o serviço no fluxo de trabalho. -If you configure the job to run directly on the runner machine and your step doesn't use a container action, you must map any required Docker service container ports to the Docker host (the runner machine). You can access the service container using localhost and the mapped port. +Se você configurar a tarefa para executar diretamente na máquina do executor e sua etapa não usar uma ação de contêiner, você deverá mapear todas as portas de contêiner de serviço do Docker necessárias para o host do Docker (a máquina do executor). Você pode acessar o contêiner de serviço usando host local e a porta mapeada. -For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)." +Para obter mais informações sobre as diferenças entre os contêineres de serviço de rede, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers)". -#### Example using localhost +#### Exemplo de uso de host local -This example creates two services: nginx and redis. When you specify the Docker host port but not the container port, the container port is randomly assigned to a free port. {% data variables.product.prodname_dotcom %} sets the assigned container port in the {% raw %}`${{job.services..ports}}`{% endraw %} context. In this example, you can access the service container ports using the {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} and {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} contexts. +Este exemplo cria dois serviços: nginx e redis. Ao especificar a porta do host do Docker mas não a porta do contêiner, a porta do contêiner será atribuída aleatoriamente a uma porta livre. O {% data variables.product.prodname_dotcom %} define a porta de contêiner atribuída no contexto {% raw %}`${{job.services..ports}}`{% endraw %}. Neste exemplo, você pode acessar as portas do contêiner de serviço usando os contextos {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} e {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %}. ```yaml -services: +serviços: nginx: - image: nginx - # Map port 8080 on the Docker host to port 80 on the nginx container - ports: + imagem: nginx + # Mapeia a porta 8080 no host do Docker com a porta 80 no contêiner nginx + portas: - 8080:80 redis: - image: redis - # Map TCP port 6379 on Docker host to a random free port on the Redis container - ports: + imagem: redis + # Mapeia a porta port 6379 TCP no host do Docker com uma porta livre aleatória no contêiner Redis + portas: - 6379/tcp ``` ### `jobs..services..image` -The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}public{% endif %} registry name. +Imagem Docker a ser usada como contêiner de serviço para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um {% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2.23" %}nome de registro{% endif %} público. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} ### `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -#### Example +#### Exemplo {% raw %} ```yaml @@ -1112,23 +1197,23 @@ services: ### `jobs..services..env` -Sets a `map` of environment variables in the service container. +Define um `maá` das variáveis de ambiente no contêiner do serviço. ### `jobs..services..ports` -Sets an `array` of ports to expose on the service container. +Define um `array` de portas para expor no contêiner de serviço. ### `jobs..services..volumes` -Sets an `array` of volumes for the service container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host. +Define um `array` de volumes para uso do contêiner de serviço. É possível usar volumes para compartilhar dados entre serviços ou outras etapas em um trabalho. Você pode especificar volumes de nome Docker, volumes Docker anônimos ou vincular montagens no host. -To specify a volume, you specify the source and destination path: +Para especificar um volume, especifique o caminho de origem e destino: `:`. -The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. +`` é um nome de volume ou caminho absoluto na máquina host, e `` é um caminho absoluto no contêiner. -#### Example +#### Exemplo ```yaml volumes: @@ -1139,63 +1224,63 @@ volumes: ### `jobs..services..options` -Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)." +Opções adicionais de recursos do contêiner Docker. Para obter uma lista de opções, consulte "[opções `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". -### Filter pattern cheat sheet +### Folha de consulta de filtro padrão -You can use special characters in path, branch, and tag filters. +Você pode usar caracteres especiais nos filtros de caminhos, branches e tags. -- `*`: Matches zero or more characters, but does not match the `/` character. For example, `Octo*` matches `Octocat`. -- `**`: Matches zero or more of any character. -- `?`: Matches zero or one single character. For example, `Octoc?t` matches `Octocat`. -- `+`: Matches one or more of the preceding character. -- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-f]` matches any digits or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`. -- `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character. +- `*`: Corresponde a zero ou mais caracteres, mas não Corresponde ao caractere `/`. Por exemplo, `Octo*` corresponde a `Octocat`. +- `**`: Corresponde a zero ou mais de qualquer caractere. +- `?`: Corresponde a zero ou a um único caractere. Por exemplo, `Octoc?t` corresponde a `Octocat`. +- `+`: Corresponde a um ou mais dos caracteres anteriores. +- `[]` Corresponde a um caractere listado entre colchetes ou incluído nos intervalos. Os intervalos só podem incluir valores de `a-z`, `A-Z`, e `0-9`. Por exemplo, o intervalo`[0-9a-z]` corresponde a qualquer letra maiúscula ou minúscula. Por exemplo, `[CB]at` corresponde a `Cat` ou `Bat` e `[1-2]00` corresponde a `100` e `200`. +- `!` No início de um padrão faz com que ele anule padrões positivos anteriores. Não tem nenhum significado especial caso não seja o primeiro caractere. -The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. +Os caracteres `*`, `[` e `!` são caracteres especiais em YAML. Se você iniciar um padrão com `*`, `[` ou `!`, você deverá colocá-lo entre aspas. ```yaml -# Valid +# Válido - '**/README.md' -# Invalid - creates a parse error that -# prevents your workflow from running. +# Inválido - Cria um erro de análise que +# impede que o seu fluxo de trabalho seja executado. - **/README.md ``` -For more information about branch, tag, and path filter syntax, see "[`on..`](#onpushpull_requestbranchestags)" and "[`on..paths`](#onpushpull_requestpaths)." +Para obter mais informações sobre a sintaxe de filtros de branches, tags e caminhos, consulte "[`on..`](#onpushpull_requestbranchestags)" e "[`on..paths`](#onpushpull_requestpaths)". -#### Patterns to match branches and tags +#### Padrões para corresponder branches e tags -| Pattern | Description | Example matches | -|---------|------------------------|---------| -| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). | -`feature/my-branch`
-`feature/your-branch` | -| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | -`feature/beta-a/my-branch`
-`feature/your-branch`
-`feature/mona/the/octocat` | -| -`main`
-`releases/mona-the-octcat` | Matches the exact name of a branch or tag name. | -`main`
-`releases/mona-the-octocat` | -| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`main`
-`releases` | -| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | -`all/the/branches`
-`every/tag` | -| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`mona-feature`
-`feature`
-`ver-10-feature` | -| `v2*` | Matches branch and tag names that start with `v2`. | -`v2`
-`v2.0`
-`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning tags with major version 1 or 2 | -`v1.10.1`
-`v2.0.0` | +| Padrão | Descrição | Exemplos de correspondências | +| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `feature/*` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). | `feature/my-branch`

`feature/your-branch` | +| `feature/**` | `**` correspondem a qualquer caractere, incluindo a barra (`/`) em nomes de branches e tags. | `feature/beta-a/my-branch`

`feature/your-branch`

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

`releases/mona-the-octcat` | Corresponde ao nome exato de um branch ou tag. | `main`

`releases/mona-the-octocat` | +| `'*'` | Corresponde a todos os nomes de branches e tags que não contêm uma barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `main`

`releases` | +| `'**'` | Corresponde a todos os nomes de branches e tags. Esse é o comportamento padrão quando você não usa um filtro de `branches` ou `tags`. | `all/the/branches`

`every/tag` | +| `'*feature'` | O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `mona-feature`

`feature`

`ver-10-feature` | +| `v2*` | Corresponde aos nomes de branches e tags que iniciam com `v2`. | `v2`

`v2.0`

`v2.9` | +| `v[12].[0-9]+.[0-9]+` | Corresponde a todas as tags de versão de branch semântica com a versão principal 1 ou 2 | `v1.10.1`

`v2.0.0` | -#### Patterns to match file paths +#### Padrões para corresponder a caminhos de arquivos -Path patterns must match the whole path, and start from the repository's root. +Padrões de caminhos devem corresponder ao caminho completo e iniciar a partir da raiz do repositório. -| Pattern | Description of matches | Example matches | -|---------|------------------------|-----------------| -| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | -`README.md`
-`server.rb` | -| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | -`page.js`
-`page.jsx` | -| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | -`all/the/files.md` | -| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | -`app.js`
-`index.js` -| `'**.js'` | Matches all `.js` files in the repository. | -`index.js`
-`js/index.js`
-`src/js/app.js` | -| `docs/*` | All files within the root of the `docs` directory, at the root of the repository. | -`docs/README.md`
-`docs/file.txt` | -| `docs/**` | Any files in the `/docs` directory at the root of the repository. | -`docs/README.md`
-`docs/mona/octocat.txt` | -| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | -`docs/README.md`
-`docs/mona/hello-world.md`
-`docs/a/markdown/file.md` -| `'**/docs/**'` | Any files in a `docs` directory anywhere in the repository. | -`/docs/hello.md`
-`dir/docs/my-file.txt`
-`space/docs/plan/space.doc` -| `'**/README.md'` | A README.md file anywhere in the repository. | -`README.md`
-`js/README.md` -| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | -`a/src/app.js`
-`my-src/code/js/app.js` -| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | -`my-post.md`
-`path/their-post.md` | -| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | -`migrate-10909.sql`
-`db/migrate-v1.0.sql`
-`db/sept/migrate-v1.sql` | -| -`*.md`
-`!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | -`hello.md`
_Does not match_
-`README.md`
-`docs/hello.md` | -| -`*.md`
-`!README.md`
-`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | -`hello.md`
-`README.md`
-`README.doc`| +| Padrão | Descrição das correspondências | Exemplos de correspondências | +| ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `'*'` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). O caractere `*` é um caractere especial em YAML. Ao inciar um padrão com `*`, você deve usar aspas. | `README.md`

`server.rb` | +| `'*.jsx?'` | O caractere `?` corresponde a zero ou a um dos caracteres anteriores. | `page.js`

`page.jsx` | +| `'**'` | `**` corresponde a qualquer caractere incluindo a barra (`/`). Esse é o comportamento padrão quando você não usa um filtro de `path`. | `all/the/files.md` | +| `'*.js'` | O caractere curinga `*` corresponde a qualquer caractere, mas não à barra (`/`). Corresponde a todos os arquivos `.js` na raiz do repositório. | `app.js`

`index.js` | +| `'**.js'` | Corresponde a todos os arquivos `.js` no repositório. | `index.js`

`js/index.js`

`src/js/app.js` | +| `docs/*` | Todos os arquivos dentro da raiz do diretório `docs`, na raiz do repositório. | `docs/README.md`

`docs/file.txt` | +| `docs/**` | Qualquer arquivo no diretório `docs`, na raiz do repositório. | `docs/README.md`

`docs/mona/octocat.txt` | +| `docs/**/*.md` | Um arquivo com um sufixo `.md` em qualquer local do diretório `docs`. | `docs/README.md`

`docs/mona/hello-world.md`

`docs/a/markdown/file.md` | +| `'**/docs/**'` | Qualquer arquivo no diretório `docs`, em qualquer local do repositório. | `/docs/hello.md`

`dir/docs/my-file.txt`

`space/docs/plan/space.doc` | +| `'**/README.md'` | Um arquivo README.md em qualquer local do repositório. | `README.md`

`js/README.md` | +| `'**/*src/**'` | Qualquer arquivo em uma pasta com o sufixo `src` em qualquer local do repositório. | `a/src/app.js`

`my-src/code/js/app.js` | +| `'**/*-post.md'` | Um arquivo com o sufixo `-post.md` em qualquer local do repositório. | `my-post.md`

`path/their-post.md` | +| `'**/migrate-*.sql'` | Um arquivo com o prefixo `migrate-` e sufixo `.sql` em qualquer local do repositório. | `migrate-10909.sql`

`db/migrate-v1.0.sql`

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

`!README.md` | Usar um sinal de exclamação (`!`) na frente de um padrão o anula. Quando um arquivo corresponde a um padrão e também corresponde a um padrão negativo definido posteriormente no arquivo, o arquivo não será incluído. | `hello.md`

_Does not match_

`README.md`

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

`!README.md`

`README*` | Os padrões são verificados sequencialmente. Um padrão que anula um padrão anterior irá incluir caminhos de arquivos novamente. | `hello.md`

`README.md`

`README.doc` | diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 32b8f364b4..d4def6e4b6 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -21,7 +21,7 @@ Após habilitar o SAML SSO e SCIM durante {% data variables.product.prodname_ghe * Atribua o aplicativo {% data variables.product.prodname_ghe_managed %} a um grupo IdP no Azure AD para criar automaticamente e conceder acesso a contas de usuário em {% data variables.product.product_name %} para todos os integrantes do grupo IdP. Além disso, o grupo IdP está disponível em {% data variables.product.prodname_ghe_managed %} para conexão com uma equipe e sua organização principal. * Desatribua o aplicativo de {% data variables.product.prodname_ghe_managed %} de um grupo de IdP para desativar as contas de usuário de {% data variables.product.product_name %} de todos os usuários de IdP que tiveram acesso somente através desse grupo de IdP e remova os usuários da organização principal. O grupo IdP será desconectado de qualquer equipe em {% data variables.product.product_name %}. -Para obter mais informações sobre gerenciamento de identidade e acesso para a sua empresa em {% data variables.product.product_location %}, consulte "[Gerenciar identidade e acesso da sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". Para obter mais informações sobre como sincronizar equipes com grupos de IdP, consulte "[Sincronizar 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)". +Para obter mais informações sobre gerenciamento de identidade e acesso para a sua empresa em {% data variables.product.product_location %}, consulte "[Gerenciar identidade e acesso da sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". Para obter mais informações sobre como sincronizar equipes com grupos de IdP, consulte "[Sincronizar uma equipe com um grupo de provedores de identidade](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". ### Pré-requisitos diff --git a/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index bbc4819f26..4c2142ac56 100644 --- a/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -28,7 +28,7 @@ O aplicativo de provisionamento no seu IdP comunica-se com {% data variables.pro {% data reusables.scim.supported-idps %} -Ao configurar o provisionamento de usuário com um IdP compatível, você também pode atribuir ou desatribuir a do aplicativo de {% data variables.product.product_name %} para grupos de usuários. Estes grupos são disponibilizados para os proprietários da organização e mantenedores de equipe em {% data variables.product.product_location %} para mapear para equipes de {% data variables.product.product_name %}. 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)." +Ao configurar o provisionamento de usuário com um IdP compatível, você também pode atribuir ou desatribuir a do aplicativo de {% data variables.product.product_name %} para grupos de usuários. Estes grupos são disponibilizados para os proprietários da organização e mantenedores de equipe em {% data variables.product.product_location %} para mapear para equipes de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ### Pré-requisitos diff --git a/translations/pt-BR/content/admin/authentication/using-saml.md b/translations/pt-BR/content/admin/authentication/using-saml.md index 3304f0e048..1124621ef4 100644 --- a/translations/pt-BR/content/admin/authentication/using-saml.md +++ b/translations/pt-BR/content/admin/authentication/using-saml.md @@ -8,6 +8,8 @@ redirect_from: intro: 'O SAML é um padrão de autenticação e autorização baseado em XML. O {% data variables.product.prodname_ghe_server %} pode agir como provedor de serviços (SP, Service Provider) com seu provedor de identidade (IdP, Identity Provider) SAML interno.' versions: enterprise-server: '*' +topics: + - enterprise --- {% data reusables.enterprise_user_management.built-in-authentication %} @@ -46,7 +48,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`. @@ -79,7 +81,7 @@ Os atributos a seguir estão disponíveis. Você pode alterar seus nomes no [con {% endtip %} -5. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location %}. ![Configuração desativar administrador SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) +5. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location %}. ![Configuração de desabilitar administrador de SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) 6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTP ou HTTPS do seu IdP para solicitações de logon único. Esse valor é fornecido pela configuração do IdP. Se o nome do host só estiver disponível na rede interna, talvez seja necessário [configurar a {% data variables.product.product_location %} para usar servidores de nomes internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticação SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png) 7. Como alternativa, no campo **Issuer** (Emissor), digite o nome do emissor de SAML. Fazer isso verifica a autenticidade das mensagens enviadas para a {% data variables.product.product_location %}. ![Emissor SAML](/assets/images/enterprise/management-console/saml-issuer.png) 8. 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 SAML para verificar a integridade das solicitações do {% data variables.product.product_location %}. Especifique o formato no menu suspenso **Name Identifier Format** (Formato de identificador de nome). ![Método SAML ](/assets/images/enterprise/management-console/saml-method.png) diff --git a/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index f3d823f8cf..cb6b653cab 100644 --- a/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -13,7 +13,7 @@ Por padrão, os usuários autorizados podem acessar sua empresa a partir de qual {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -Você também pode configurar endereços IP permitidos para uma organização individual. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)". +Você também pode configurar endereços IP permitidos para uma organização individual. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)". Por padrão, as regras do grupo de segurança de rede do Azure (NSG) deixam todo o tráfego de entrada aberto nas portas 22, 80, 443 e 25. Proprietários de empresa podem entrar em contato com {% data variables.contact.github_support %} para configurar as restrições de acesso para sua instância. diff --git a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md index 0a015c3eca..90181f93a5 100644 --- a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md @@ -37,7 +37,7 @@ Além de todos os benefícios do {% data variables.contact.enterprise_support %} {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} Para obter mais informações, consulte "[Entrar em contato com o Suporte do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/reaching-github-support)". +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md index 8e6a4f27a4..2422d5c749 100644 --- a/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md +++ b/translations/pt-BR/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md @@ -35,7 +35,7 @@ Além de todos os benefícios do {% data variables.contact.enterprise_support %} {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} Para obter mais informações, consulte "[Entrar em contato com o Suporte do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/reaching-github-support)". +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/pt-BR/content/admin/github-actions/index.md b/translations/pt-BR/content/admin/github-actions/index.md index c9656f633c..d1e28f9e2c 100644 --- a/translations/pt-BR/content/admin/github-actions/index.md +++ b/translations/pt-BR/content/admin/github-actions/index.md @@ -32,6 +32,7 @@ topics: {% 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 /using-the-latest-version-of-the-official-bundled-actions %} {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} {% topic_link_in_list /advanced-configuration-and-troubleshooting %} 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 fbbc8cb9e2..b4fb234413 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 @@ -28,8 +28,21 @@ A ferramenta `actions-sync` só pode fazer download de ações de {% data variab ### Pré-requisitos -* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino já existam na instância corporativa. O exemplo a seguir demonstra como sincronizar ações com uma organização denominada `synced-actions` em uma instância corporativa. Para obter mais informações, consulte "[Criar uma nova organização do zero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". +* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino já existam na instância corporativa. O exemplo a seguir demonstra como sincronizar ações com uma organização denominada `synced-actions` em uma instância corporativa. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". * Você deve criar um token de acesso pessoal (PAT) na instância corporativa que pode criar e gravar em repositórios nas organizações de destino. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. + + {% note %} + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + + {% endnote %} + + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." + + ```shell + ghe-org-admin-promote -u USERNAME -o actions + ``` ### Exemplo: Usando a ferramenta de `actions-sync` diff --git a/translations/pt-BR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/pt-BR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md new file mode 100644 index 0000000000..95824cc97e --- /dev/null +++ b/translations/pt-BR/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md @@ -0,0 +1,45 @@ +--- +title: Usar a versão mais recente das ações agrupadas oficialmente +intro: 'Você pode atualizar as ações que estão empacotadas com sua instância de {% data variables.product.prodname_ghe_server %} ou usar ações diretamente de {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '>=2.22' +topics: + - enterprise +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +A sua instância de {% data variables.product.prodname_ghe_server %} inclui uma série de ações integradas que você pode usar nos seus fluxos de trabalho. Para obter mais informações sobre as ações agrupadas, consulte ["Ações oficiais agrupadas com {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server). + +Essas ações agrupadas são um instantâneo no momento das ações oficiais encontradas em https://github.com/actions; como resultado, essas ações podem ser versões anteriores que podem ser atualizadas. Para atualizar estas ações, você pode usar `actions-sync` para recuperar versões atualizadas de {% data variables.product.prodname_dotcom_the_website %}. + +Como alternativa, se sua instância do {% data variables.product.prodname_ghe_server %} tiver {% data variables.product.prodname_github_connect %} habilitado, você terá opções adicionais para usar as últimas ações de {% data variables.product.prodname_dotcom_the_website %}: + +- O seu arquivo de fluxo de trabalho pode referir-se diretamente a uma tag específica que só existe em {% data variables.product.prodname_dotcom_the_website %}. +- Para forçar o arquivo do fluxo de trabalho a usar as ações em {% data variables.product.prodname_dotcom_the_website %}, você poderá editar a tag atribuída às ações agrupadas. + +Estas opções são descritas com mais detalhes nas seções a seguir. + +### Usar sincronismo de ações para atualizar uma ação empacotada + +Para atualizar as ações agrupadas, você poderá usar a ferramenta de `actions-sync` para sincronizar as ações com {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre como usar `actions-sync`, consulte "[Sincronizar as ações manualmente de {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)". + +### Usar as ações de {% data variables.product.prodname_dotcom_the_website %} + +{% data reusables.github-actions.actions-github-connect-requirement %} + +Uma vez configurado, você poderá usar uma nova versão de uma ação a partir de {% data variables.product.prodname_dotcom_the_website %}, especificando, manualmente, a versão necessária no arquivo de fluxo de trabalho. Por exemplo, para usar a versão `v2.2.` de `actions/setup-python` de {% data variables.product.prodname_dotcom_the_website %}, você pode especificar a tag `actions/setup-python@v2.2.1` no seu arquivo de fluxo de trabalho. + +### Usar a versão mais recente removendo a tag da ação específica + +{% data reusables.github-actions.actions-github-connect-requirement %} + +Se você remover a tag de versão que foi atribuída anteriormente a uma ação, {% data variables.product.prodname_ghe_server %} verificará {% data variables.product.prodname_dotcom_the_website %} com relação à tag necessária. Para obter mais informações sobre como trabalhar com tags, consulte "[Visualizar tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)". + +Por exemplo, para usar a versão `v2.2.1` de `actions/setup-python` de {% data variables.product.prodname_dotcom_the_website %}: + +1. Em {% data variables.product.prodname_ghe_server %}, exclua a tag `v2` do repositório `actions/setup-python`. +1. Crie um fluxo de trabalho que usa `actions/setup-python` com a tag `v2`. + +Quando o fluxo de trabalho não consegue encontrar a tag `v2` especificada no {% data variables.product.prodname_ghe_server %}, ele irá verificar a tag necessária de {% data variables.product.prodname_dotcom_the_website %} Se encontrar uma versão com tag dessa ação, {% data variables.product.prodname_ghe_server %} usará a versão de {% data variables.product.prodname_dotcom_the_website %}. 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 6853ebe9ae..f82e7807c1 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 @@ -33,7 +33,7 @@ Para usar este guia, você deve conhecer os seguintes conceitos do AWS: ### Determinar o tipo de instância -Before launching {% data variables.product.product_location %} on AWS, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." +Antes de lançar {% data variables.product.product_location %} no AWS, você deverá determinar o tipo de máquina que melhor se adequa às necessidades da sua organização. Para revisar os requisitos mínimos para {% data variables.product.product_name %}, consulte "[Requisitos mínimos](#minimum-requirements)". {% data reusables.enterprise_installation.warning-on-scaling %} 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 051bcb9045..1e45ed3360 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 @@ -24,13 +24,13 @@ Você pode implantar o {% data variables.product.prodname_ghe_server %} no Azure ### Determinar o tipo de máquina virtual -Before launching {% data variables.product.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." +Antes de lançar {% data variables.product.product_location %} no Azure, você deverá determinar o tipo de máquina que melhor atende às necessidades da sua organização. Para revisar os requisitos mínimos para {% data variables.product.product_name %}, consulte "[Requisitos mínimos](#minimum-requirements)". {% data reusables.enterprise_installation.warning-on-scaling %} -O appliance do {% data variables.product.prodname_ghe_server %} requer um disco de dados de armazenamento premium e é compatível com qualquer VM do Azure que tenha suporte ao armazenamento premium. Azure VM types with the `s` suffix support premium storage. For more information, see "[What disk types are available in Azure?](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd)" and "[Azure premium storage: design for high performance](https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance)" in the Azure documentation. +O appliance do {% data variables.product.prodname_ghe_server %} requer um disco de dados de armazenamento premium e é compatível com qualquer VM do Azure que tenha suporte ao armazenamento premium. Tipos de Azure VM com `s` sufixo são compatíveis com o armazenamento premium. Para obter mais informações, consulte "[Quais tipos de disco estão disponíveis no Azure?](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd)" e "[Armazenamento premium do Azure: design para alto desempenho](https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance)" na documentação do Azure. -{% data variables.product.company_short %} recommends a memory-optimized VM for {% data variables.product.prodname_ghe_server %}. For more information, see "[Memory optimized virtual machine sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory)" in the Azure documentation. +{% data variables.product.company_short %} recomenda uma VM com memória otimizada para {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Tamanhos de máquinas virtuais com memória otimizada ](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory)" na documentação do Azure. O {% data variables.product.prodname_ghe_server %} dá suporte a qualquer região compatível com o seu tipo de VM. Para obter mais informações sobre as regiões compatíveis com cada VM, consulte "[Produtos disponíveis por região](https://azure.microsoft.com/regions/services/)". 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 ac6933af49..86b767f24d 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 @@ -22,11 +22,11 @@ topics: ### Determinar o tipo de máquina -Antes de iniciar a {% data variables.product.product_location %} no Google Cloud Platform, você terá que determinar o tipo de máquina virtual que melhor se adapta às demandas da sua organização. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." +Antes de iniciar a {% data variables.product.product_location %} no Google Cloud Platform, você terá que determinar o tipo de máquina virtual que melhor se adapta às demandas da sua organização. Para revisar os requisitos mínimos para {% data variables.product.product_name %}, consulte "[Requisitos mínimos](#minimum-requirements)". {% data reusables.enterprise_installation.warning-on-scaling %} -{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation. +{% data variables.product.company_short %} recomenda uma máquina de uso geral e de alta memória para {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Tipos de máquina](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" na documentação do Google Compute Engine. ### Selecionar a imagem do {% data variables.product.prodname_ghe_server %} 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 0e33f2639d..d2623e5f20 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 @@ -1,6 +1,6 @@ --- title: Instalar o GitHub Enterprise Server no Hyper-V -intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Hyper-V, você deve fazer a implantação em uma máquina que execute o Windows Server 2008 através do Windows Server 2016.' +intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Hyper-V, você deve fazer a implantação em uma máquina que execute o Windows Server 2008 através do Windows Server 2019.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v @@ -13,7 +13,7 @@ topics: ### Pré-requisitos - {% data reusables.enterprise_installation.software-license %} -- Seu sistema operacional deve estar entre o Windows Server 2008 e o Windows Server 2016, que são compatíveis com o Hyper-V. +- Seu sistema operacional deve estar entre o Windows Server 2008 e o Windows Server 2019, que são compatíveis com o Hyper-V. - A maioria das ações necessárias para criar sua máquina virtual (VM) também pode ser executada usando o [Gerenciador do Hyper-V](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). No entanto, a configuração inicial é recomendável com o shell de linha de comando do Windows PowerShell. Veja abaixo alguns exemplos com o PowerShell. Para obter mais informações, consulte "[Introdução ao Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)" no guia da Microsoft. ### Considerações de hardware diff --git a/translations/pt-BR/content/admin/overview/github-ae-release-notes.md b/translations/pt-BR/content/admin/overview/github-ae-release-notes.md index ffecb67944..257f06b2fb 100644 --- a/translations/pt-BR/content/admin/overview/github-ae-release-notes.md +++ b/translations/pt-BR/content/admin/overview/github-ae-release-notes.md @@ -29,7 +29,7 @@ Durante este beta, as funcionalidades de {% data variables.product.prodname_adva #### Gerenciar equipes do seu provedor de identidade (IdP) -Os clientes que usam o SCIM (System para Gerenciamento de Identidade entre Domínios) agora podem sincronizar grupos de segurança no Azure Active Directory com equipes de {% data variables.product.company_short %}. Após uma equipe ser vinculada a um grupo de segurança a associação será atualizada automaticamente em {% data variables.product.product_name %} quando um usuário for adicionado ou removido do seu grupo de segurança atribuído. 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)." +Os clientes que usam o SCIM (System para Gerenciamento de Identidade entre Domínios) agora podem sincronizar grupos de segurança no Azure Active Directory com equipes de {% data variables.product.company_short %}. Após uma equipe ser vinculada a um grupo de segurança a associação será atualizada automaticamente em {% data variables.product.product_name %} quando um usuário for adicionado ou removido do seu grupo de segurança atribuído. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." #### Beta de listas de permissões de IP @@ -37,7 +37,7 @@ Os proprietários de empresas e organizações agora podem usar o IP permitir li Essa funcionalidade é fornecida, além da capacidade de solicitar alterações no grupo de segurança de rede que filtram o tráfego na totalidade do inquilino de {% data variables.product.product_name %}. -Para mais informações, consulte "[Restringir tráfego de rede a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)" e "[Gerenciar endereços IP permitidos para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)". +Para mais informações, consulte "[Restringir tráfego de rede a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)" e "[Gerenciar endereços IP permitidos para sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)". #### Merge automático de pull request @@ -47,8 +47,8 @@ Com o merge automático, os pull requests podem ser configurados como merge auto #### Mudanças do desenvolvedor -- [Os proprietários da organização agora podem desabilitar a publicação](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization) de sites de {% data variables.product.prodname_pages %} de repositórios na organização. Esta ação não irá cancelar a publicação de sites existentes. -- Os repositórios que usam {% data variables.product.prodname_pages %} agora podem [fazer a criação e implantação a partir de qualquer branch](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). +- [Os proprietários da organização agora podem desabilitar a publicação](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) de sites de {% data variables.product.prodname_pages %} de repositórios na organização. Esta ação não irá cancelar a publicação de sites existentes. +- Os repositórios que usam {% data variables.product.prodname_pages %} agora podem [fazer a criação e implantação a partir de qualquer branch](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - Ao escrever um problema ou pull request, a sintaxe da lista para itens, números, e tarefas agora será concluída automaticamente após você pressionar `return` ou `enter`. - Agora, você pode excluir um diretório em um repositório da página do repositório. Ao acessar diretório, um novo botão kebab ao lado do botão "Adicionar arquivo" dá a opção de excluir o diretório. - Agora é mais fácil e rápido [fazer referência a problemas ou pull requests](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), com pesquisa entre várias palavras após "#". @@ -65,7 +65,7 @@ Com o merge automático, os pull requests podem ser configurados como merge auto ##### Renomeação do branch padrão -Os proprietários de empresas e organizações agora podem definir o nome do branch padrão para novos repositórios. Os proprietários de empresas também podem aplicar a sua escolha do nome padrão do branch em todas as organizações ou permitir que as organizações individuais escolham suas próprias. Para mais informações consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" e "[Gerenciar o nome do branch padrão para os repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)". +Os proprietários de empresas e organizações agora podem definir o nome do branch padrão para novos repositórios. Os proprietários de empresas também podem aplicar a sua escolha do nome padrão do branch em todas as organizações ou permitir que as organizações individuais escolham suas próprias. Para mais informações consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" e "[Gerenciar o nome do branch padrão para os repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)". Os repositórios existentes não são afetados por essas configurações, e seu nome de branch padrão não será alterado. diff --git a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md index 98376df2a7..ae5010d2c2 100644 --- a/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md +++ b/translations/pt-BR/content/admin/policies/creating-a-pre-receive-hook-script.md @@ -14,91 +14,91 @@ topics: Veja exemplos de hooks pre-receive para o {% data variables.product.prodname_ghe_server %} no repositório [`github/platform-samples`](https://github.com/github/platform-samples/tree/master/pre-receive-hooks). ### Gravar um script de hook pre-receive -A pre-receive hook script executes in a pre-receive hook environment on {% data variables.product.product_location %}. When you create a pre-receive hook script, consider the available input, output, exit status, and environment variables. +Um script de hook pre-receive é executado em um ambiente de hook pre-receive em {% data variables.product.product_location %}. Ao criar um script de hook pre-receive, considere a entrada, saída, estado de saída e variáveis de ambiente disponíveis. -#### Input (`stdin`) -After a push occurs and before any refs are updated for the remote repository, the `git-receive-pack` process on {% data variables.product.product_location %} invokes the pre-receive hook script. Standard input for the script, `stdin`, is a string containing a line for each ref to update. Each line contains the old object name for the ref, the new object name for the ref, and the full name of the ref. +#### Entrada (`stdin`) +Depois que um push ocorrer e antes que qualquer ref seja atualizado para o repositório remoto, o processo `git-receive-pack` em {% data variables.product.product_location %} irá invocar o script de do hook pre-receive. A entrada padrão para o script, `stdin`, é uma string que contém uma linha atualizar cada ref. Cada linha contém o nome antigo do objeto para ref, o novo nome do objeto para o ref e o nome completo do ref. ``` SP SP LF ``` -This string represents the following arguments. +Essa frase representa os argumentos a seguir. | Argumento | Descrição | |:------------------- |:------------------------------------------------------------------------------------------------- | -| `` | Old object name stored in the ref.
When you create a new ref, the value is 40 zeroes. | -| `` | New object name to be stored in the ref.
When you delete a ref, the value is 40 zeroes. | -| `` | The full name of the ref. | +| `` | Nome de objeto antigo armazenado na ref.
Ao criar uma nova ref, o valor será 40 zeros. | +| `` | Novo nome de objeto a ser armazenado na ref.
Ao excluir uma ref, o valor será 40 zeros. | +| `` | O nome completo da ref. | -For more information about `git-receive-pack`, see "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" in the Git documentation. For more information about refs, see "[Git References](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" in *Pro Git*. +Para obter mais informações sobre `git-receive-pack`, consulte "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" na documentação do Git. Para obter mais informações sobre refs, consulte "[Referências do Git](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" no *Pro Git*. -#### Output (`stdout`) +#### Saída (`stdout`) -The standard output for the script, `stdout`, is passed back to the client. Any `echo` statements will be visible to the user on the command line or in the user interface. +A saída padrão do script, `stdout`, é remetida de volta para o cliente. Qualquer `echo` será visível para o usuário na linha de comando ou na interface do usuário. #### Status de saída -The exit status of a pre-receive script determines if the push will be accepted. +O status de saída de um script pre-receive determina se o push será aceito. -| Exit-status value | Ação | -|:----------------- |:---------------------- | -| 0 | O push será aceito. | -| Diferente de zero | O push será rejeitado. | +| Valor de status de saída | Ação | +|:------------------------ |:---------------------- | +| 0 | O push será aceito. | +| Diferente de zero | O push será rejeitado. | #### Variáveis de ambiente -In addition to the standard input for your pre-receive hook script, `stdin`, {% data variables.product.prodname_ghe_server %} makes the following variables available in the Bash environment for your script's execution. For more information about `stdin` for your pre-receive hook script, see "[Input (`stdin`)](#input-stdin)." +Além da entrada padrão para o seu script do hook pre-receive, `stdin`, {% data variables.product.prodname_ghe_server %} disponibiliza as variáveis a seguir no ambiente Bash para a execução do seu script. Para obter mais informações sobre `stdin` para o seu script de hook de pre-receive, consulte "[Entrada (`stdin`)](#input-stdin)". -Different environment variables are available to your pre-receive hook script depending on what triggers the script to run. +Diferentes variáveis de ambiente estão disponíveis para o seu script de hook pre-receive dependendo do que acionar o script. -- [Always available](#always-available) -- [Available for pushes from the web interface or API](#available-for-pushes-from-the-web-interface-or-api) -- [Available for pull request merges](#available-for-pull-request-merges) -- [Available for pushes using SSH authentication](#available-for-pushes-using-ssh-authentication) +- [Sempre disponível](#always-available) +- [Disponível para pushes a partir da interface web ou API](#available-for-pushes-from-the-web-interface-or-api) +- [Disponível para merge de pull request](#available-for-pull-request-merges) +- [Disponível para pushes que usam autenticação SSH](#available-for-pushes-using-ssh-authentication) -##### Always available +##### Sempre disponível -The following variables are always available in the pre-receive hook environment. +As seguintes variáveis estão sempre disponíveis no ambiente de do hook pre-receive. -| Variável | Descrição | Valor de exemplo | -|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------ | -| 
$GIT_DIR
| Path to the remote repository on the instance | /data/user/repositories/a/ab/
a1/b2/34/100001234/1234.git | -| 
$GIT_PUSH_OPTION_COUNT
| The number of push options that were sent by the client with `--push-option`. For more information, see "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" in the Git documentation. | 1 | -| 
$GIT\_PUSH\_OPTION\_N
| Quando _N_ for um número inteiro a partir de 0, esta variável vai conter a string de opção de push enviada pelo cliente. The first option that was sent is stored in `GIT_PUSH_OPTION_0`, the second option that was sent is stored in `GIT_PUSH_OPTION_1`, and so on. Para obter mais informações sobre as opções de push, consulte "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" na documentação do Git. | abcd |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| 
$GIT_USER_AGENT
| User-agent string sent by the Git client that pushed the changes | git/2.0.0{% endif %} -| 
$GITHUB_REPO_NAME
| Name of the repository being updated in _NAME_/_OWNER_ format | octo-org/hello-enterprise | -| 
$GITHUB_REPO_PUBLIC
| Boolean representing whether the repository being updated is public |
  • true: Repository's visibility is public
  • false: Repository's visibility is private or internal
| -| 
$GITHUB_USER_IP
| IP address of client that initiated the push | 192.0.2.1 | -| 
$GITHUB_USER_LOGIN
| Username for account that initiated the push | octocat | +| Variável | Descrição | Valor de exemplo | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------ | +| 
$GIT_DIR
| Caminho para o repositório remoto na instância | /data/user/repositories/a/ab/
a1/b2/34/100001234/1234.git | +| 
$GIT_PUSH_OPTION_COUNT
| O número de opções de push enviadas pelo cliente com `--push-option`. Para obter mais informações, consulte "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" na documentação do Git. | 1 | +| 
$GIT\_PUSH\_OPTION\_N
| Quando _N_ for um número inteiro a partir de 0, esta variável vai conter a string de opção de push enviada pelo cliente. A primeira opção enviada é armazenada em `GIT_PUSH_OPTION_0`, a segunda opção enviada é armazenada em `GIT_PUSH_OPTION_1`, e assim por diante. Para obter mais informações sobre as opções de push, consulte "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" na documentação do Git. | abcd |{% if currentVersion ver_gt "enterprise-server@2.21" %} +| 
$GIT_USER_AGENT
| String de usuário-agente enviada pelo cliente Git que realizou push das alterações | git/2.0.0{% endif %} +| 
$GITHUB_REPO_NAME
| Nome do repositório que está sendo atualizado no formato _NAME_/_OWNER_ | octo-org/hello-enterprise | +| 
$GITHUB_REPO_PUBLIC
| Booleano público, que representa se o repositório está sendo atualizado |
  • true: A visibilidade do repositório é pública
  • false: A visibilidade do repositório é privada ou interna
| +| 
$GITHUB_USER_IP
| Endereço IP do cliente que iniciou o push | 192.0.2.1 | +| 
$GITHUB_USER_LOGIN
| Nome de usuário para a conta que iniciou o push | octocat | -##### Available for pushes from the web interface or API +##### Disponível para pushes a partir da interface web ou API -The `$GITHUB_VIA` variable is available in the pre-receive hook environment when the ref update that triggers the hook occurs via either the web interface or the API for {% data variables.product.prodname_ghe_server %}. The value describes the action that updated the ref. +A variável `$GITHUB_VIA` está disponível no ambiente de pre-receive quando a atualização de ref que aciona o hook por meio da interface da web ou da API para {% data variables.product.prodname_ghe_server %}. O valor descreve a ação que atualizou o ref. -| Valor | Ação | Mais informações | -|:-------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 
auto-merge deployment api
| Automatic merge of the base branch via a deployment created with the API | "[Repositories](/rest/reference/repos#create-a-deployment)" in the REST API documentation | -| 
blob edit
| Change to a file's contents in the web interface | "[Editar arquivos no repositório](/github/managing-files-in-a-repository/editing-files-in-your-repository)" | -| 
branch merge api
| Merge of a branch via the API | "[Repositories](/rest/reference/repos#merge-a-branch)" in the REST API documentation | -| 
branches page delete button
| Deletion of a branch in the web interface | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" | -| 
git refs create api
| Creation of a ref via the API | "[Git database](/rest/reference/git#create-a-reference)" in the REST API documentation | -| 
git refs delete api
| Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation | -| 
git refs update api
| Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation | -| 
git repo contents api
| Change to a file's contents via the API | "[Repositories](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation | -| 
merge base into head
| Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" | -| 
pull request branch delete button
| Deletion of a topic branch from a pull request in the web interface | "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" | -| 
pull request branch undo button
| Restoration of a topic branch from a pull request in the web interface | "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" | -| 
pull request merge api
| Merge of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation | -| 
pull request merge button
| Merge of a pull request in the web interface | "[Fazer merge de uma pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" | -| 
pull request revert button
| Revert of a pull request | "[Reverter uma pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | -| 
releases delete button
| Deletion of a release | "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | -| 
stafftools branch restore
| Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" | -| 
tag create api
| Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation | -| 
slumlord (#SHA)
| Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | -| 
web branch create
| Creation of a branch via the web interface | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" | +| Valor | Ação | Mais informações | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 
auto-merge deployment api
| Merge automático do branch base através de uma implantação criada com a API | "[Repositórios](/rest/reference/repos#create-a-deployment)" na documentação da API REST | +| 
blob edit
| Mudar para o conteúdo de um arquivo na interface web | "[Editar arquivos no repositório](/github/managing-files-in-a-repository/editing-files-in-your-repository)" | +| 
branch merge api
| Merge de um branch através da API | "[Repositórios](/rest/reference/repos#merge-a-branch)" na documentação da API REST | +| 
branches page delete button
| Exclusão de um branch na interface web | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" | +| 
git refs create api
| Criação de um ref através da API | "[Banco de dados Git](/rest/reference/git#create-a-reference)" na documentação da API REST | +| 
git refs delete api
| Exclusão de uma ref através da API | "[Banco de dados Git](/rest/reference/git#delete-a-reference)" na documentação da API REST | +| 
git refs update api
| Atualização de um ref através da API | "[Banco de dados Git](/rest/reference/git#update-a-reference)" na documentação da API REST | +| 
git repo contents api
| Mudança no conteúdo de um arquivo através da API | "[Repositórios](/rest/reference/repos#create-or-update-file-contents)" na documentação da API REST | +| 
merge base into head
| Atualizar o branch de tópico do branch de base quando o branch de base exigir verificações de status rigorosas (via **Atualizar branch** em um pull request, por exemplo) | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" | +| 
pull request branch delete button
| Exclusão de um branch de tópico de um pull request na interface web | "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" | +| 
pull request branch undo button
| Restauração de um branch de tópico de um pull request na interface web | "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" | +| 
pull request merge api
| Merge de um pull request através da API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" na documentação da API REST | +| 
pull request merge button
| Merge de um pull request na interface web | "[Fazer merge de uma pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" | +| 
pull request revert button
| Revert of a pull request | "[Reverter uma pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | +| 
releases delete button
| Deletion of a release | "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | +| 
stafftools branch restore
| Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" | +| 
tag create api
| Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation | +| 
slumlord (#SHA)
| Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | +| 
web branch create
| Creation of a branch via the web interface | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" | -##### Available for pull request merges +##### Disponível para merge de pull request The following variables are available in the pre-receive hook environment when the push that triggers the hook is a push due to the merge of a pull request. @@ -108,7 +108,7 @@ The following variables are available in the pre-receive hook environment when t | 
$GITHUB_PULL_REQUEST_HEAD
| The name of the pull request's topic branch, in the format `USERNAME:BRANCH` | octocat:fix-bug | | 
$GITHUB_PULL_REQUEST_BASE
| The name of the pull request's base branch, in the format `USERNAME:BRANCH` | octocat:main | -##### Available for pushes using SSH authentication +##### Disponível para pushes que usam autenticação SSH | Variável | Descrição | Valor de exemplo | |:-------------------------- |:-------------------------------------------------------------- |:----------------------------------------------- | diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md index 2ceb647952..eaa3e8da8f 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise.md @@ -1,10 +1,10 @@ --- -title: Enforcing policies for Advanced Security in your enterprise -intro: 'Enterprise owners can enforce policies to manage {% data variables.product.prodname_GH_advanced_security %} features for organizations on {% data variables.product.product_location %}.' +title: Aplicar políticas de Segurança Avançada na sua empresa +intro: 'Os proprietários da empresa podem aplicar políticas para gerenciar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para as organizações em {% data variables.product.product_location %}.' product: '{% data reusables.gated-features.ghas %}' versions: enterprise-server: '>=3.1' - github-ae: '*' + github-ae: 'avançar' --- ### Sobre o {% data variables.product.prodname_GH_advanced_security %} 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 e381d21727..1e60e6a615 100644 --- a/translations/pt-BR/content/admin/user-management/audited-actions.md +++ b/translations/pt-BR/content/admin/user-management/audited-actions.md @@ -48,7 +48,7 @@ topics: | Ação | Descrição | | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} -| `business.advanced_security_policy_update` | A site admin creates, updates, or removes a policy for {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."{% endif %} +| `business.advanced_security_policy_update` | Um administrador do site cria, atualiza ou remove uma política para {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".{% endif %} | `business.clear_members_can_create_repos` | Um administrador do site elimina uma restrição de criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | | `business.update_member_repository_creation_permission` | Um administrador do site restringe a criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% if enterpriseServerVersions contains currentVersion %} | `enterprise.config.lock_anonymous_git_access` | Um administrador do site bloqueia acessos de leitura anônimos do Git para impedir que os administradores do repositório alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | 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 de1977b0e0..b18ba34cad 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 @@ -66,17 +66,16 @@ As mensagens obrigatórias têm uma série de usos. - Contar para os usuários como obter ajuda com {% data variables.product.product_location %} - Garantir que todos os usuários leiam seus termos de serviço para usar {% data variables.product.product_location %} -{% note %} - -**Note:** After you configure a mandatory message for {% data variables.product.product_location %}, you cannot change or remove the message. - -{% endnote %} - - Se você incluir caixas de seleção de Markdown na mensagem, todas as caixas de seleção deverão ser selecionadas antes de o usuário poder ignorar a mensagem. Por exemplo, se você incluir seus termos de serviço na mensagem obrigatória, você poderá exigir que cada usuário marque uma caixa de seleção para confirmar que o usuário leu os termos. Cada vez que um usuário vê uma mensagem obrigatória, um evento de log de auditoria é criado. O evento inclui a versão da mensagem que o usuário visualizou. Para obter mais informações, consulte "[Ações auditadas](/admin/user-management/audited-actions)". +{% note %} + +**Observação:** Se você alterar a mensagem obrigatória para {% data variables.product.product_location %}, os usuários que já reconheceram a mensagem não visualizarão a nova mensagem. + +{% endnote %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} diff --git a/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md index bfd9dbae39..7fbdd79e8f 100644 --- a/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md +++ b/translations/pt-BR/content/code-security/getting-started/about-securing-your-repository.md @@ -68,7 +68,7 @@ Essas funcionalidades estão disponíveis {% if currentVersion == "free-pro-team {% endif %} {% if currentVersion == "free-pro-team@latest" %} -- **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." +- **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". {% endif %} {% if currentVersion != "github-ae@latest" %} diff --git a/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md b/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md index 49630ef3f5..605cb8a47a 100644 --- a/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-security/about-secret-scanning.md @@ -45,7 +45,7 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p {% data variables.product.prodname_secret_scanning_caps %} está disponível em todos os repositórios de propriedade da organização como parte de {% data variables.product.prodname_GH_advanced_security %}. Não está disponível em repositórios pertencentes a usuários. {% endif %} -Se você é um administrador de repositório ou um proprietário de uma organização, você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% if currentVersion == "free-pro-team@latest" %} repositórios privados{% endif %} pertencentes 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 na sua organização.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_secret_scanning_caps %} não está disponível para repositórios privados pertencentes a usuários.{% endif %} Para 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)" 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)". +Se você é um administrador de repositório ou um proprietário de uma organização, você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% if currentVersion == "free-pro-team@latest" %} repositórios privados{% endif %} pertencentes a organizações. 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." Quando você faz push dos commits para um repositório{% if currentVersion == "free-pro-team@latest" %} privado{% endif %} com {% data variables.product.prodname_secret_scanning %} habilitado, {% data variables.product.prodname_dotcom %} verifica o conteúdo dos segredos dos commits. diff --git a/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md index f326efef9f..da1635a0ba 100644 --- a/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md +++ b/translations/pt-BR/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md @@ -70,4 +70,4 @@ Você também pode ignorar alertas individuais de {% data variables.product.prod ### 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)" +- "[Gerenciando configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/pt-BR/content/code-security/secret-security/index.md b/translations/pt-BR/content/code-security/secret-security/index.md index 7d2cefd5e7..fd9482bc27 100644 --- a/translations/pt-BR/content/code-security/secret-security/index.md +++ b/translations/pt-BR/content/code-security/secret-security/index.md @@ -1,7 +1,7 @@ --- title: Manter os segredos protegidos shortTitle: Segurança de segredo -intro: 'Let {% data variables.product.company_short %} do the hard work of ensuring that tokens, private keys, and other code secrets are not exposed in your repository.' +intro: 'Permita que {% data variables.product.company_short %} faça o trabalho duro de garantir que tokens, chaves privadas e outros segredos de código não sejam expostos no seu repositório.' product: '{% data reusables.gated-features.secret-scanning %}' versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md b/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md index 307a416c88..f3457d3eb3 100644 --- a/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md +++ b/translations/pt-BR/content/code-security/secure-coding/configuring-code-scanning.md @@ -49,11 +49,11 @@ A varredura do código a cada push para o repositório, e toda vez que um pull r Se você usar o fluxo de trabalho padrão, o {% data variables.product.prodname_code_scanning %} fará a varredura do código no repositório uma vez por semana, além das varreduras acionadas pelos eventos. Para ajustar essa programação, edite o valor `CRON` no fluxo de trabalho. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)". -If you scan on push, then the results appear in the **Security** tab for your repository. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository). " +Se você fizer uma varredura no push, os resultados aparecerão na aba **Segurança** do repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository). " {% note %} -**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below. +**Observação**: se você deseja que os alertas de {% data variables.product.prodname_code_scanning %} sejam exibidos como verificações de pull request, você deverá usar o evento `pull_request` descrito abaixo. {% endnote %} @@ -63,7 +63,7 @@ O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pu Para obter mais informações sobre o evento `pull_request` , consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". -If you scan pull requests, then the results appear as alerts in a pull request check. Para obter mais informações, consulte "[Alertas de varredura de código de triagem em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". +Se você realizar uma varredura de pull requests, os resultados aparecerão como alertas em uma verificação de pull request. Para obter mais informações, consulte "[Alertas de varredura de código de triagem em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". #### Evitar varreduras desnecessárias de pull requests @@ -118,7 +118,7 @@ on: Este fluxo de trabalho faz a varredura: * Cada push para o branch-padrão e o branch protegido * Cada pull request para o branch-padrão -* The default branch every Monday at 14:20 UTC +* O branch padrão toda segunda-feira às 14h20 UTC ### Especificar um sistema operacional diff --git a/translations/pt-BR/content/code-security/secure-coding/index.md b/translations/pt-BR/content/code-security/secure-coding/index.md index 290ac804bc..1ac08d9125 100644 --- a/translations/pt-BR/content/code-security/secure-coding/index.md +++ b/translations/pt-BR/content/code-security/secure-coding/index.md @@ -1,7 +1,7 @@ --- title: Encontrar vulnerabilidades e erros de segurança no seu código shortTitle: Codificação segura -intro: 'Mantenha seu código seguro usando a varredura de segredo para identificar e corrigir potenciais vulnerabilidades de segurança e outros erros no seu código.' +intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code diff --git a/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md index a30f728f7f..f284f1905f 100644 --- a/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md @@ -45,7 +45,14 @@ Você precisa de permissão de gravação para visualizar um resumo de todos os {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -1. Em "{% data variables.product.prodname_code_scanning_capc %}", clique no alerta que você gostaria de explorar. ![Resumo dos alertas](/assets/images/help/repository/code-scanning-click-alert.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} +1. Opcionalmente, use os menus suspensos para filtrar alertas. Por exemplo, você pode filtrar pela ferramenta usada para identificar alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +1. Em "{% data variables.product.prodname_code_scanning_capc %}", clique no alerta que você gostaria de explorar. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Resumo dos alertas](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 1. Opcionalmente, se o alerta destacar um problema com o fluxo de dados, clique em **Mostrar caminhos** para exibir o caminho da fonte de dados até o destino onde é usado. ![O link "Exibir caminhos" em um alerta](/assets/images/help/repository/code-scanning-show-paths.png) 1. Alertas da análise de {% data variables.product.prodname_codeql %} incluem uma descrição do problema. Clique em **Mostrar mais** para obter orientação sobre como corrigir seu código. ![Detalhes para um alerta](/assets/images/help/repository/code-scanning-alert-details.png) @@ -57,7 +64,11 @@ Se você tem permissão de escrita em um repositório, você pode visualizar ale Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtrar alertas por branch](/assets/images/help/repository/code-scanning-branch-filter.png) +{% else %} +![Filtrar alertas por branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} @@ -110,11 +121,19 @@ Para ignorar ou excluir alertas: Opcionalmente, você pode usar os filtros para exibir um subconjunto de alertas e, em seguida, excluir todos os alertas de correspondência de uma só vez. Por exemplo, se você removeu uma consulta da análise de {% data variables.product.prodname_codeql %}, você pode usar o filtro "Regra" para listar apenas os alertas dessa consulta e, em seguida, selecionar e apagar todos esses alertas. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtrar alertas por regra](/assets/images/help/repository/code-scanning-filter-by-rule.png) +{% else %} + ![Filtrar alertas por regra](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) +{% endif %} 1. Se você deseja ignorar um alerta, é importante explorar primeiro o alerta para que você possa escolher o motivo correto para ignorá-lo. Clique no alerta que você deseja explorar. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Abrir um alerta da lista de resumo](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 1. Revise o alerta e clique em **Ignorar** e escolha um motivo para fechar o alerta. ![Escolher um motivo para ignorar um alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) diff --git a/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md b/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md index 722d279e73..bc04346539 100644 --- a/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md +++ b/translations/pt-BR/content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md @@ -19,7 +19,7 @@ topics: Se você estiver configurando {% data variables.product.prodname_code_scanning %} para um idioma compilado e estiver criando o código em um ambiente de contêiner, a análise pode falhar com a mensagem de erro "Nenhum código fonte foi visto durante a compilação." Isso indica que {% data variables.product.prodname_codeql %} não conseguiu monitorar seu código da forma como foi compilado. -Você precisa executar {% data variables.product.prodname_codeql %} no mesmo contêiner em que você cria o seu código. Isto se aplica independentemente de você usar {% data variables.product.prodname_codeql_runner %} ou {% data variables.product.prodname_actions %}. Se você estiver usando {% data variables.product.prodname_codeql_runner %}, execute-o no contêiner onde seu código é criado. For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." Se estiver usando {% data variables.product.prodname_actions %}, configure seu fluxo de trabalho para executar todas as ações no mesmo contêiner. Para obter mais informações, consulte "[Exemplo de fluxo de trabalho](#example-workflow)". +Você precisa executar {% data variables.product.prodname_codeql %} no mesmo contêiner em que você cria o seu código. Isto se aplica independentemente de você usar {% data variables.product.prodname_codeql_runner %} ou {% data variables.product.prodname_actions %}. Se você estiver usando {% data variables.product.prodname_codeql_runner %}, execute-o no contêiner onde seu código é criado. Para obter mais informações sobre {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)". Se estiver usando {% data variables.product.prodname_actions %}, configure seu fluxo de trabalho para executar todas as ações no mesmo contêiner. Para obter mais informações, consulte "[Exemplo de fluxo de trabalho](#example-workflow)". ### Dependências diff --git a/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md b/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md index d2f4f8b06b..b10a221b37 100644 --- a/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md +++ b/translations/pt-BR/content/code-security/secure-coding/sarif-support-for-code-scanning.md @@ -22,7 +22,7 @@ SARIF (Formato de Intercâmbio de Resultados de Análise Estática) é um [OASIS Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. Para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF para o {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)". Para obter mais informações sobre o esquema SARIF 2.1.0 JSON, consulte [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json). -Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." +Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFingerprints` será calculado quando você fizer o upload do arquivo SARIF usando {% data variables.product.prodname_actions %}. Para mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)" ou "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)". {% data variables.product.prodname_dotcom %} usa propriedades no arquivo SARIF para exibir alertas. Por exemplo, `shortDescription` e `fullDescription` aparecem na parte superior de um alerta de {% data variables.product.prodname_code_scanning %}. O `local` permite que {% data variables.product.prodname_dotcom %} mostre anotações no seu arquivo de código. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". diff --git a/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md index 9f4516e68e..3812fc5ea7 100644 --- a/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md +++ b/translations/pt-BR/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md @@ -32,7 +32,7 @@ Você decide como gerar alertas de {% data variables.product.prodname_code_scann {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3. " %}Se {% data variables.product.prodname_code_scanning %} estiver faltando, peça para um proprietário da organização ou administrador de repositório habilitar {% data variables.product.prodname_GH_advanced_security %}. Para mais informações consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" ou "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png) +3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3. " %}Se {% data variables.product.prodname_code_scanning %} estiver faltando, peça para um proprietário da organização ou administrador de repositório habilitar {% data variables.product.prodname_GH_advanced_security %}. Para mais informações consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" ou "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Em "Começar com {% data variables.product.prodname_code_scanning %}", clique em **Configurar este fluxo de trabalho** no {% data variables.product.prodname_codeql_workflow %} ou em um fluxo de trabalho de terceiros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Os fluxos de trabalho são exibidos apenas se forem relevantes para as linguagens de programação detectadas no repositório. O {% data variables.product.prodname_codeql_workflow %} é sempre exibido, mas o botão "Configurar este fluxo de trabalho" só é habilitado se a análise de {% data variables.product.prodname_codeql %} for compatível com as linguagens presentes no repositório.{% endif %} 5. Para personalizar como {% data variables.product.prodname_code_scanning %} faz a varredura do seu código, edite o fluxo de trabalho. @@ -72,7 +72,11 @@ Depois de configurar o {% data variables.product.prodname_code_scanning %} para **Observação:** Se você criou um pull request para adicionar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %} ao repositório, os alertas desse pull request não serão exibidos diretamente na página de {% data variables.product.prodname_code_scanning_capc %} até que o pull request seja mesclado. Se algum alerta for encontrado, você poderá visualizá-los, antes do merge do pull request, clicando no link dos **_n_ alertas encontrados** no banner na página de {% data variables.product.prodname_code_scanning_capc %}. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Clique no link "n alertas encontrados"](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Clique no link "n alertas encontrados"](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} {% endnote %} @@ -98,7 +102,11 @@ Há outras situações em que não pode haver análise para o último commit do Para verificar se um branch foi verificado, acesse a página {% data variables.product.prodname_code_scanning_capc %}, clique no menu suspenso **Branch** e selecione o branch relevante. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Escolha um branch no menu suspenso Branch](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% else %} + ![Escolha um branch no menu suspenso Branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) +{% endif %} A solução nesta situação é adicionar o nome do branch de base para a especificação `on:push` e `on:pull_request` no fluxo de trabalho de {% data variables.product.prodname_code_scanning %} nesse branch e, em seguida, fazer uma alteração que atualize o pull request aberto que você deseja escanear. diff --git a/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md index 87f5317fea..85e68e617e 100644 --- a/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/pt-BR/content/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,7 +28,7 @@ Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com Há muitas opções para configurar {% data variables.product.prodname_code_scanning %} como uma verificação de pull request. Portanto, a configuração exata de cada repositório irá variar e alguns terão mais de uma verificação. A verificação que contém os resultados de {% data variables.product.prodname_code_scanning %} é: **Resultados da varredura de código**. -Se o repositório usar a {% data variables.product.prodname_codeql_workflow %} uma **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)**, executa-se a verificação para cada linguagem antes que a verificação de resultados seja executada. A verificação de análise pode falhar se houver problemas de configuração ou se o pull request altera a criação para uma linguagem que a análise precisa para compilar (por exemplo, C/C++, C#, ou Java). Assim como com outras verificações de pull request, você poderá ver informações completas da falha de verificação na aba de **Verificações**. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" or "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)." +Se o repositório usar a {% data variables.product.prodname_codeql_workflow %} uma **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)**, executa-se a verificação para cada linguagem antes que a verificação de resultados seja executada. A verificação de análise pode falhar se houver problemas de configuração ou se o pull request altera a criação para uma linguagem que a análise precisa para compilar (por exemplo, C/C++, C#, ou Java). Assim como com outras verificações de pull request, você poderá ver informações completas da falha de verificação na aba de **Verificações**. Para obter mais informações sobre configuração e solução de problemas, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" ou "[Solução de problemas do fluxo de trabalho de {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)". ### Triar de um alerta no seu pull request diff --git a/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md b/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md index 8c775b068f..d98f65a385 100644 --- a/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md +++ b/translations/pt-BR/content/code-security/secure-coding/uploading-a-sarif-file-to-github.md @@ -28,7 +28,7 @@ Você pode fazer o upload dos resultados usando {% data variables.product.prodna - {% data variables.product.prodname_actions %} para executar a ação {% data variables.product.prodname_codeql %}, não haverá nenhuma ação adicional necessária. A ação {% data variables.product.prodname_codeql %} faz o upload do arquivo SARIF automaticamente quando ele conclui a análise. - O arquivo SARIF pode ser gerado a partir de uma ferramenta de análise compatível com o SARIF, que você executa no mesmo fluxo de trabalho de {% data variables.product.prodname_actions %} usado para fazer o upload do arquivo. -- {% data variables.product.prodname_dotcom %} exibirá alertas de {% data variables.product.prodname_code_scanning %} do arquivo SARIF carregado em seu repositório. 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_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)"). +- {% 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 envio automático, quando você estiver pronto para enviar resultados, você poderá usar o comando `upload` (para mais informações, consulte "[Executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/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 mais informações, consulte "[Enviar uma análise como dados do SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"). {% data reusables.code-scanning.not-available %} diff --git a/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md index b7a19d3d00..904f6cd553 100644 --- a/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md +++ b/translations/pt-BR/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md @@ -1,63 +1,63 @@ --- -title: About coordinated disclosure of security vulnerabilities -intro: 'Vulnerability disclosure is a coordinated effort between security reporters and repository maintainers.' +title: Sobre a divulgação coordenada de vulnerabilidades de segurança +intro: 'A divulgação das vulnerabilidades é um esforço coordenado entre os relatores de segurança e os mantenedores de repositório.' miniTocMaxHeadingLevel: 4 versions: free-pro-team: '*' --- -### About disclosing vulnerabilities in the industry +### Sobre a divulgação de vulnerabilidades no setor {% data reusables.security-advisory.disclosing-vulnerabilities %} -The initial report of a vulnerability is made privately, and the full details are only published once the maintainer has acknowledged the issue, and ideally made remediations or a patch available, sometimes with a delay to allow more time for the patches to be installed. For more information, see the "[OWASP Cheat Sheet Series about vulnerability disclosure](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)" on the OWASP Cheat Sheet Series website. +O relatório inicial de uma vulnerabilidade é tornado privado, e os detalhes completos só são publicados depois de o mantenedor reconhecer o problema e, idealmente, são disponibilizadas soluções ou atualizações, às vezes com um atraso para dar mais tempo para a instalação das atualizações. Para obter mais informações, consulte a "[Série de Páginas de Referência de OWASP sobre a divulgação de vulnerabilidades](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)" no site da Série de Páginas de Referência de OWASP. -#### Best practices for vulnerability reporters +#### Práticas recomendadas para relatores de vulnerabilidade -It's good practice to report vulnerabilities privately to maintainers. When possible, as a vulnerability reporter, we recommend you avoid: -- Disclosing the vulnerability publicly without giving maintainers a chance to remediate. -- Bypassing the maintainers. -- Disclosing the vulnerability before a fixed version of the code is available. -- Expecting to be compensated for reporting an issue, where no public bounty program exists. +É uma prática recomendada relatar de forma privada vulnerabilidades para os mantenedores. Quando possível, como um relator de vulnerabilidades, recomendamos que você evite: +- Divulgar a vulnerabilidade publicamente sem dar aos mantenedores a oportunidade de remediar. +- Ignorar os mantenedores. +- Divulgar a vulnerabilidade antes de uma versão fixa do código estar disponível. +- Esperar ser compensado por relatar um problema, quando não há nenhum programa de recompensa pública. -It's acceptable for vulnerability reporters to disclose a vulnerability publicly after a period of time, if they have tried to contact the maintainers and not received a response, or contacted them and been asked to wait too long to disclose it. +É aceitável para os relatores de vulnerabilidade revelar uma vulnerabilidade publicamente após um período de tempo, se eles tentaram entrar em contato com os mantenedores e não receberem uma resposta, ou caso tenha entrado em contato com eles e solicitado para esperar muito tempo para divulgá-lo. -We recommend vulnerability reporters clearly state the terms of their disclosure policy as part of their reporting process. Even if the vulnerability reporter does not adhere to a strict policy, it's a good idea to set clear expectations for maintainers in terms of timelines on intended vulnerability disclosures. For an example of disclosure policy, see the "[Security Lab's disclosure policy](https://securitylab.github.com/advisories#policy)" on the GitHub Security Lab website. +Recomendamos que os relatores de vulnerabilidade indiquem claramente os termos da sua política de divulgação como parte do seu processo de relatório. Mesmo que o relator de vulnerabilidade não adira a uma política rigorosa, é bom estabelecer expectativas claras para os mantenedores em termos de cronogramas sobre divulgações de vulnerabilidades intencionais. Para obter um exemplo de política de divulgação, consulte a "[Política de divulgação do Laboratório de Segurança](https://securitylab.github.com/advisories#policy)" no site do GitHub Security Lab. -#### Best practices for maintainers +#### Práticas recomendadas para mantenedores -As a maintainer, it's good practice to clearly indicate how and where you want to receive reports for vulnerabilities. If this information is not clearly available, vulnerability reporters don't know how to contact you, and may resort to extracting developer email addresses from git commit histories to try to find an appropriate security contact. This can lead to friction, lost reports, or the publication of unresolved reports. +Como mantenedor, considera-se uma prática recomendada indicar claramente como e onde você deseja receber relatórios de vulnerabilidades. Se essas informações não estiverem claramente disponíveis, os relatores de vulnerabilidade não saberão como entrar em contato com você, e poderão recorrer à extração de endereços de e-mail do desenvolvedor a partir do histórico de commit do git para tentar encontrar um contato de segurança apropriado. Isso pode gerar atritos, relatórios perdidos ou publicação de relatórios não resolvidos. -Maintainers should disclose vulnerabilities in a timely manner. If there is a security vulnerability in your repository, we recommend you: -- Treat the vulnerability as a security issue rather than a simple bug, both in your response and your disclosure. For example, you'll need to explicitly mention that the issue is a security vulnerability in the release notes. -- Acknowlege receipt of the vulnerability report as quickly as possible, even if no immediate resources are available for investigation. This sends the message that you are quick to respond and act, and it sets a positive tone for the rest of the interaction between you and the vulnerability reporter. -- Involve the vulnerability reporter when you verify the impact and veracity of the report. It's likely the vulnerability reporter has already spent time considering the vulnerability in a variety of scenarios, some of which you may have not considered yourself. -- Remediate the issue in a way that you see fit, taking any concerns and advice provided by the vulnerability reporter into careful consideration. Often the vulnerability reporter will have knowledge of certain corner cases and remediation bypasses that are easy to miss without a security research background. -- Always acknowledge the vulnerability reporter when you credit the discovery. -- Aim to publish a fix as soon as you can. -- Ensure that you make the wider ecosystem aware of the issue and its remediation when you disclose the vulnerability. It is not uncommon to see cases where a recognized security issue is fixed in the current development branch of a project, but the commit or subsequent release is not explicitly marked as a security fix or release. This can cause problems with downstream consumers. +Os mantenedores devem divulgar as vulnerabilidades em tempo oportuno. Se houver uma vulnerabilidade de segurança no seu repositório, recomendamos que você: +- Trate a vulnerabilidade como um problema de segurança em vez de um erro simples, tanto na sua resposta quanto na sua divulgação. Por exemplo, você deverá mencionar explicitamente que o problema é uma vulnerabilidade de segurança nas observações da versão. +- Confirme o recebimento do relatório de vulnerabilidade o mais rapidamente possível, mesmo que não estejam disponíveis recursos imediatos para investigação. Isso envia a mensagem de que você está rapidamente para responder e agir e define um tom positivo para o resto da interação entre você e o relator da vulnerabilidade. +- Envolva o relator da vulnerabilidade após verificar o impacto e a veracidade do relatório. É provável que o relator da vulnerabilidade já tenha gasto tempo considerando a vulnerabilidade em uma série de cenários. alguns dos quais você pode não ter se considerado. +- Remedeie o problema de uma forma que você considere adequada, considerando, de forma ponderada, as preocupações e conselhos fornecidos pelo relator de vulnerabilidade. Muitas vezes, o relator da vulnerabilidade tem conhecimento de certos casos extremos e correções desviadas que são fáceis de perder sem uma pesquisa de segurança em segundo plano. +- Sempre reconheça o relator da vulnerabilidade quando você der crédito para a descoberta. +- Busque publicar uma correção assim que puder. +- Certifique-se de que você conscientize o ecossistema mais amplo sobre o problema e sua correção quando você publicar a vulnerabilidade. Não é incomum ver casos em que um problema de segurança reconhecido é corrigido no branch de desenvolvimento atual de um projeto. mas o commit ou versão posterior não é explicitamente marcado como uma correção ou versão de segurança. Isso pode causar problemas para consumidores em níveis inferiores.. -Publishing the details of a security vulnerability doesn't make maintainers look bad. Security vulnerabilities are present everywhere in software, and users will trust maintainers who have a clear and established process for disclosing security vulnerabilities in their code. +Publicar os detalhes de uma vulnerabilidade de segurança não faz com que os mantenedores pareçam ruins. As vulnerabilidades de segurança estão presentes em todos os lugares no software, e os usuários confiarão nos mantenedores que têm um processo claro e estabelecido para divulgar as vulnerabilidades de segurança no seu código. -### About reporting and disclosing vulnerabilities in projects on {% data variables.product.prodname_dotcom %} +### Sobre relatar e publicar vulnerabilidades em projetos em {% data variables.product.prodname_dotcom %} -The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows: +O processo de relatório e divulgação de vulnerabilidades para projetos em {% data variables.product.prodname_dotcom_the_website %} é o seguinte: - If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository. + Se você é um relator de vulnerabilidades (por exemplo, um pesquisador de segurança) que gostaria de relatar uma vulnerabilidade, primeiro verifique se existe uma política de segurança para o repositório relacionado. Para obter mais informações, consulte "[Sobre políticas de segurança](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)". Se houver uma, siga-a para entender o processo antes de entrar em contato com a equipe de segurança do repositório. - If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use. + Se não houver uma política de segurança, a forma mais eficiente de estabelecer um meio privado de comunicação com os mantenedores é criar uma problema, solicitando um contato de segurança preferido. Vale a pena notar que o problema será imediatamente visível ao público. Portanto, não deve incluir nenhuma informação sobre o erro. Quando a comunicação for estabelecida, você poderá sugerir que os mantenedores definam uma política de segurança para uso futuro. {% note %} -**Note**: _For npm only_ - If we receive a report of malware in an npm package, we try to contact you privately. If you don't address the issue in a timely manner, we will disclose it. For more information, see "[Reporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" on the npm Docs website. +**Observação**: _Somente para o npm_ - Se recebermos um relatório de malware em um pacote npm, tentaremos entrar em contato com você em particular. Se você não resolver o problema em tempo, iremos divulgá-lo. Para obter mais informações, consulte "[Relatar malware em um pacote npm](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" no site do npm Docs. {% endnote %} - If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website. + Se você encontrou uma vulnerabilidade de segurança em {% data variables.product.prodname_dotcom_the_website %}, informe a vulnerabilidade por meio de nosso processo de divulgação coordenada. Para obter mais informações, consulte o site [{% data variables.product.prodname_dotcom %} Recompensa por Erros de Segurança](https://bounty.github.com/). - If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue. + Se for mantenedor, você poderá assumir a propriedade do processo no início do pipeline, configurando uma política de segurança para o seu repositório, ou disponibilizando as instruções de relatórios de segurança de forma clara, por exemplo, no arquivo LEIAME do seu projeto. Para obter informações sobre como adicionar uma política de segurança, consulte "[Sobre políticas de segurança](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository#about-security-policies)". Se não houver política de segurança, é provável que um relator de vulnerabilidade tente enviar um e-mail para você ou entrar em contato com você de forma privada. Como alternativa, alguém pode abrir um problema (público) com detalhes de um problema de segurança. - As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories). + Como mantenedor, para divulgar uma vulnerabilidade no seu código, você primeiro cria um rascunho de uma consultoria de segurança no repositório do pacote em {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories). Para começar, consulte "[Criar um aviso de segurança](/github/managing-security-vulnerabilities/creating-a-security-advisory)." diff --git a/translations/pt-BR/content/code-security/security-advisories/about-github-security-advisories.md b/translations/pt-BR/content/code-security/security-advisories/about-github-security-advisories.md index e85b9cfb57..c97858d2f1 100644 --- a/translations/pt-BR/content/code-security/security-advisories/about-github-security-advisories.md +++ b/translations/pt-BR/content/code-security/security-advisories/about-github-security-advisories.md @@ -17,7 +17,7 @@ topics: ### Sobre o {% data variables.product.prodname_security_advisories %} -{% data reusables.security-advisory.disclosing-vulnerabilities %} For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)." +{% data reusables.security-advisory.disclosing-vulnerabilities %} Para obter mais informações, consulte "[Sobre a divulgação coordenada de vulnerabilidades de segurança](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)". {% data reusables.security-advisory.security-advisory-overview %} @@ -25,7 +25,7 @@ Com {% data variables.product.prodname_security_advisories %}, você pode: 1. Criar um aviso de segurança rascunho e usar o rascunho para discutir em particular o impacto da vulnerabilidade no seu projeto. Para obter mais informações, consulte "[Criar uma consultoria de segurança](/github/managing-security-vulnerabilities/creating-a-security-advisory)". 2. Colaborar de modo particular com a correção da vulnerabilidade em uma bifurcação privada temporária. -3. Publish the security advisory to alert your community of the vulnerability once a patch is released. Para obter mais informações, consulte "[Publicar uma consultoria de segurança](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". +3. Publique a consultoria de segurança para alertar a sua comunidade sobre a vulnerabilidade depois que um patch for lançado. Para obter mais informações, consulte "[Publicar uma consultoria de segurança](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". {% data reusables.repositories.security-advisories-republishing %} @@ -33,13 +33,13 @@ Você pode dar crédito a indivíduos que contribuíram para um aviso de seguran {% data reusables.repositories.security-guidelines %} -If you created a security advisory in your repository, the security advisory will stay in your repository. We publish security advisories for any of the ecosystems supported by the dependency graph to the {% data variables.product.prodname_advisory_database %} on [github.com/advisories](https://github.com/advisories). If a security advisory is specifically for npm, we also publish the advisory to the npm security advisories. For more information, see [npmjs.com/advisories](https://www.npmjs.com/advisories). +Se você criou uma consultoria de segurança no seu repositório, o consultório de segurança permanecerá no seu repositório. Publicamos consultorias de segurança para qualquer um dos ecossistemas compatíveis com o gráfico de dependências para o {% data variables.product.prodname_advisory_database %} em [github.com/advisories](https://github.com/advisories). Se uma consultoria de segurança for especificamente para o npm, nós também publicamos a consultoria nas consultorias de segurança do npm. Para obter mais informações, consulte [npmjs.com/advisories](https://www.npmjs.com/advisories). {% data reusables.repositories.github-security-lab %} ### Números de identificação CVE -{% data variables.product.prodname_security_advisories %} baseia-se na base da lista de Vulnerabilidades e Exposições Comuns (CVE). The security advisory form on {% data variables.product.prodname_dotcom %} is a standardized form that matches the CVE description format. +{% data variables.product.prodname_security_advisories %} baseia-se na base da lista de Vulnerabilidades e Exposições Comuns (CVE). O formulário de consultoria de segurança em {% data variables.product.prodname_dotcom %} é um formulário padronizado que corresponde ao formato de descrição CVE. {% data variables.product.prodname_dotcom %} é uma Autoridade de Numeração CVE (CNA) e está autorizada a atribuir números de identificação CVE. Para obter mais informações, consulte "[Sobre CVE](https://cve.mitre.org/about/index.html)" e "[Autoridades de Numeração CVE](https://cve.mitre.org/cve/cna.html)" no site da CVE. diff --git a/translations/pt-BR/content/code-security/security-advisories/adding-a-security-policy-to-your-repository.md b/translations/pt-BR/content/code-security/security-advisories/adding-a-security-policy-to-your-repository.md index cbb7846c56..4e464075ab 100644 --- a/translations/pt-BR/content/code-security/security-advisories/adding-a-security-policy-to-your-repository.md +++ b/translations/pt-BR/content/code-security/security-advisories/adding-a-security-policy-to-your-repository.md @@ -22,7 +22,7 @@ Você pode criar uma política de segurança padrão para sua organização ou c {% endtip %} -Depois que alguém informar uma vulnerabilidade de segurança no seu projeto, você pode usar o {% data variables.product.prodname_security_advisories %} para divulgar, corrigir e publicar informações sobre a vulnerabilidade. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about {% data variables.product.prodname_security_advisories %}, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)." +Depois que alguém informar uma vulnerabilidade de segurança no seu projeto, você pode usar o {% data variables.product.prodname_security_advisories %} para divulgar, corrigir e publicar informações sobre a vulnerabilidade. Para obter mais informações sobre o processo de relatórios e divulgação de vulnerabilidades em {% data variables.product.prodname_dotcom %}, consulte "[Sobre divulgação coordenada das vulnerabilidades de segurança](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)". Para obter mais informações sobre {% data variables.product.prodname_security_advisories %}, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)." {% data reusables.repositories.github-security-lab %} diff --git a/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md index 3826d70f08..cb105229c4 100644 --- a/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md @@ -17,6 +17,8 @@ Você pode creditar pessoas que ajudaram a descobrir, relatar ou corrigir uma vu Se alguém aceitar o crédito, o nome de usuário da pessoa aparecerá na seção "Créditos" da consultoria de segurança. Qualquer pessoa com acesso de leitura ao repositório pode ver a consultoria e as pessoas que aceitaram o crédito por ela. +Se você acredita que deveria ser creditado por uma consultoria de segurança, entre em contato com a pessoa que criou a consultoria e peça que edite a consultoria para incluir o seu crédito. Somente o criador da consultoria pode dar-lhe crédito. Portanto, não entre em contato com o suporte do GitHub com relação a créditos para consultorias de segurança. + ### Editar uma consultoria de segurança {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md b/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md index c03e8a32d9..ee0cc88ff2 100644 --- a/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md +++ b/translations/pt-BR/content/code-security/security-overview/exploring-security-alerts.md @@ -1,6 +1,6 @@ --- -title: Exploring security alerts -intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place.' +title: Explorar alertas de segurança +intro: 'Você pode visualizar, filtrar e classificar alertas de segurança para repositórios pertencentes à sua organização ou equipe em um só lugar.' product: '{% data reusables.gated-features.security-center %}' versions: free-pro-team: '*' @@ -9,44 +9,44 @@ versions: {% data reusables.security-center.beta %} -### About the security overview +### Sobre a visão geral de segurança -You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. Para obter mais informações, consulte "[Managing team access to an organization repository](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository)." +Você pode usar a visão geral de segurança para uma visão de alto nível do status de segurança da sua organização ou para identificar repositórios problemáticos que exigem intervenção. A nível da organização, a visão geral de segurança exibe informações de segurança agregadas e específicas para repositórios pertencentes à sua organização. No nível da equipe, a visão geral de segurança exibe informações de segurança específicas para repositórios para os quais a equipe tem privilégios de administrador. Para obter mais informações, consulte "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." -The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)." +The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. Para obter mais informações, consulte "[Sobre proteger seu repositório](/code-security/getting-started/about-securing-your-repository). -In the security overview, you can view, sort, and filter alerts to understand the security risks in your organization and in specific repositories. You can apply multiple filters to focus on areas of interest. For example, you can identify private repositories that have a high number of {% data variables.product.prodname_dependabot_alerts %} or repositories that have no {% data variables.product.prodname_code_scanning %} alerts. +No resumo da segurança, é possível visualizar, ordenar e filtrar alertas para entender os riscos de segurança na sua organização e nos repositórios específicos. Você pode aplicar vários filtros para concentrar-se em áreas de interesse. Por exemplo, você pode identificar repositórios privados que têm um número elevado de {% data variables.product.prodname_dependabot_alerts %} ou repositórios que não têm alertas {% data variables.product.prodname_code_scanning %}. -![The security overview for an organization](/assets/images/help/organizations/security-overview.png) +![A visão geral de segurança de uma organização](/assets/images/help/organizations/security-overview.png) -For each repository in the security overview, you will see icons for each type of {% data variables.product.prodname_advanced_security %} feature and how many alerts there are of each type. If an {% data variables.product.prodname_advanced_security %} feature is not enabled for a repository, the icon for that feature will be grayed out. +Para cada repositório na visão de segurança, você verá ícones para cada tipo de recurso de {% data variables.product.prodname_advanced_security %} e quantos alertas existem de cada tipo. Se um recurso de {% data variables.product.prodname_advanced_security %} não estiver habilitado para um repositório, o ícone para esse recurso será cinza. -![Icons in the security overview](/assets/images/help/organizations/security-overview-icons.png) +![Ícones na visão geral de segurança](/assets/images/help/organizations/security-overview-icons.png) -| Icon | Meaning | +| Ícone | Significado | | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | {% octicon "code-square" aria-label="Code scanning alerts" %} | Alertas de {% data variables.product.prodname_code_scanning_capc %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning) | | {% octicon "key" aria-label="Secret scanning alerts" %} | Alertas de {% data variables.product.prodname_secret_scanning_caps %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning) | | {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" | -| {% octicon "check" aria-label="Check" %} | The {% data variables.product.prodname_advanced_security %} feature is enabled, but does not raise alerts in this repository. | -| {% octicon "x" aria-label="x" %} | The {% data variables.product.prodname_advanced_security %} feature is not supported in this repository. | +| {% octicon "check" aria-label="Check" %} | O recurso de {% data variables.product.prodname_advanced_security %} está habilitado, mas não cria alertas neste repositório. | +| {% octicon "x" aria-label="x" %} | O recurso de {% data variables.product.prodname_advanced_security %} não é compatível com este repositório. | -By default, archived repositories are excluded from the security overview for an organization. You can apply filters to view archived repositories in the security overview. For more information, see "[Filtering the list of alerts](#filtering-the-list-of-alerts)." +Por padrão, os repositórios arquivados são excluídos da visão geral de segurança de uma organização. É possível aplicar filtros para visualizar repositórios arquivados na visão geral de segurança. Para obter mais informações, consulte "[Filtrar a lista de alertas](#filtering-the-list-of-alerts)". -The security overview displays active alerts raised by {% data variables.product.prodname_GH_advanced_security %} features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist. +A visão geral de segurança exibe alertas ativos criados por funcionalidades de {% data variables.product.prodname_GH_advanced_security %}. Se não houver alertas na visão geral de segurança de um repositório, as vulnerabilidades de segurança não detectadas ou erros de código ainda poderão existir. -### Viewing the security overview for an organization +### Visualizar a visão geral de segurança de uma organização -Organization owners can view the security overview for an organization. +Os proprietários da organização podem ver a visão geral de segurança para uma organização. {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.security-overview %} -1. To view aggregate information about alert types, click **Show more**. ![Show more button](/assets/images/help/organizations/security-overview-show-more-button.png) +1. Para visualizar informações agregadas sobre tipos de alertas, clique em **Mostrar mais**. ![Botão mostrar mais](/assets/images/help/organizations/security-overview-show-more-button.png) {% data reusables.organizations.filter-security-overview %} -### Viewing the security overview for a team +### Visualizar a visão geral de segurança de uma equipe -Members of a team can see the security overview for repositories that the team has admin privileges for. +Os integrantes de uma equipe podem visualizar a visão geral de segurança dos repositórios para os quais a equipe tem privilégios de administrador. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} @@ -54,38 +54,38 @@ Members of a team can see the security overview for repositories that the team h {% data reusables.organizations.team-security-overview %} {% data reusables.organizations.filter-security-overview %} -### Filtering the list of alerts +### Filtrar a lista de alertas -#### Filter by level of risk for repositories +#### Filtrar por nível de risco para repositórios -The level of risk for a repository is determined by the number and severity of alerts from {% data variables.product.prodname_advanced_security %} features. If one or more {% data variables.product.prodname_advanced_security %} features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by {% data variables.product.prodname_advanced_security %} features, the repository will have a clear level of risk. +O nível de risco para um repositório é determinado pelo número e gravidade de alertas de funcionalidades do {% data variables.product.prodname_advanced_security %}. Se uma ou mais funcionalidades de {% data variables.product.prodname_advanced_security %} não estiverem habilitadas para um repositório, o repositório terá um nível de risco desconhecido. Se um repositório não tiver riscos detectados por funcionalidades de {% data variables.product.prodname_advanced_security %}, o repositório terá um nível claro de risco. -| Qualifier | Descrição | -| -------------- | ---------------------------------------------------------- | -| `risk:high` | Display repositories that are at high risk. | -| `risk:medium` | Display repositories that are at medium risk. | -| `risk:low` | Display repositories that are at low risk. | -| `risk:unknown` | Display repositories that are at an unknown level of risk. | -| `risk:clear` | Display repositories that have no detected level of risk. | +| Qualifier | Descrição | +| -------------- | ----------------------------------------------------------------- | +| `risk:high` | Exibe repositórios que estão em alto risco. | +| `risk:medium` | Exibe repositórios que estão em risco médio. | +| `risk:low` | Exibe repositórios que estão em risco baixo. | +| `risk:unknown` | Exibir repositórios que estão com um nível de risco desconhecido. | +| `risk:clear` | Exibe repositórios que não tem um nível de risco identificado. | -#### Filter by number of alerts +#### Filtrar por número de alertas -| Qualifier | Descrição | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -| code-scanning-alerts:n | Display repositories that have *n* {% data variables.product.prodname_code_scanning %} alerts. This qualifier can use > and < comparison operators. | -| secret-scanning-alerts:n | Display repositories that have *n* {% data variables.product.prodname_secret_scanning %} alerts. This qualifier can use > and < comparison operators. | -| dependabot-alerts:n | Display repositories that have *n* {% data variables.product.prodname_dependabot_alerts %}. This qualifier can use > and < comparison operators. | +| Qualifier | Descrição | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| code-scanning-alerts:n | Exibe repositórios que têm *n* alertas de {% data variables.product.prodname_code_scanning %}. Este qualificador pode usar os operadores > e < de comparação. | +| secret-scanning-alerts:n | Exibe repositórios que têm *n* alertas de {% data variables.product.prodname_secret_scanning %}. Este qualificador pode usar os operadores > e < de comparação. | +| dependabot-alerts:n | Exibir repositórios que têm *n* {% data variables.product.prodname_dependabot_alerts %}. Este qualificador pode usar os operadores > e < de comparação. | -#### Filter by whether {% data variables.product.prodname_advanced_security %} features are enabled +#### Filtrar por se as funcionalidades de {% data variables.product.prodname_advanced_security %} estão habilitadas -| Qualifier | Descrição | -| ------------------------------- | -------------------------------------------------------------------------------------------------------- | -| `enabled:code-scanning` | Display repositories that have {% data variables.product.prodname_code_scanning %} enabled. | -| `not-enabled:code-scanning` | Display repositories that do not have {% data variables.product.prodname_code_scanning %} enabled. | -| `enabled:secret-scanning` | Display repositories that have {% data variables.product.prodname_secret_scanning %} enabled. | -| `not-enabled:secret-scanning` | Display repositories that have {% data variables.product.prodname_secret_scanning %} enabled. | -| `enabled:dependabot-alerts` | Display repositories that have {% data variables.product.prodname_dependabot_alerts %} enabled. | -| `not-enabled:dependabot-alerts` | Display repositories that do not have {% data variables.product.prodname_dependabot_alerts %} enabled. | +| Qualifier | Descrição | +| ------------------------------- | ---------------------------------------------------------------------------------------------------- | +| `enabled:code-scanning` | Exibe repositórios com {% data variables.product.prodname_code_scanning %} habilitado. | +| `not-enabled:code-scanning` | Exibe repositórios que não têm {% data variables.product.prodname_code_scanning %} habilitado. | +| `enabled:secret-scanning` | Exibe repositórios com {% data variables.product.prodname_secret_scanning %} habilitado. | +| `not-enabled:secret-scanning` | Exibe repositórios com {% data variables.product.prodname_secret_scanning %} habilitado. | +| `enabled:dependabot-alerts` | Exibe repositórios com {% data variables.product.prodname_dependabot_alerts %} habilitado. | +| `not-enabled:dependabot-alerts` | Exibe repositórios que não têm {% data variables.product.prodname_dependabot_alerts %} habilitado. | #### Filter by repository type diff --git a/translations/pt-BR/content/code-security/security-overview/index.md b/translations/pt-BR/content/code-security/security-overview/index.md index da995688aa..35fcf0e1f9 100644 --- a/translations/pt-BR/content/code-security/security-overview/index.md +++ b/translations/pt-BR/content/code-security/security-overview/index.md @@ -1,7 +1,7 @@ --- -title: Viewing security alerts for repositories in your organization -shortTitle: Security overview -intro: 'View, sort, and filter the security alerts from across your organization in one place.' +title: Visualizar alertas de segurança em repositórios na sua organização +shortTitle: Visão geral da segurança +intro: 'Visualize, ordene e filtre os alertas de segurança de toda a sua organização em um só lugar.' product: '{% data reusables.gated-features.security-center %}' versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md index b8a9da18f3..c752759db1 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md @@ -49,9 +49,9 @@ Para obter uma lista dos ecossistemas para os quais o {% data variables.product. {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detecta dependências vulneráveis em repositórios _públicos_ e gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. -Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios pertencentes à sua conta de usuário ou organização. Para mais informações consulte "[Gerenciar as configurações de segurança e análise da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciar as configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". +Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios pertencentes à sua conta de usuário ou organização. 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -Para informações sobre os requisitos de permissão para ações relacionadas a {% data variables.product.prodname_dependabot_alerts %}, consulte "[Níveis de permissão do repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)". +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} começa a gerar o gráfico de dependências imediatamente e gera alertas para quaisquer dependências vulneráveis assim que forem identificadas. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Para obter mais informações, consulte "[Gerenciando configurações do uso de dados de seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". {% endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-security-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-security-updates.md index f9e456d370..f141812e76 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-security-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-security-updates.md @@ -17,7 +17,7 @@ topics: {% data variables.product.prodname_dependabot_security_updates %} torna mais fácil para você corrigir dependências vulneráveis no seu repositório. Se você habilitar este recurso, quando um alerta de {% data variables.product.prodname_dependabot %} for criado para uma dependência vulnerável no gráfico de dependências do seu repositório, {% data variables.product.prodname_dependabot %} tenta corrigir isso automaticamente. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis de](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" e "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". -{% data variables.product.prodname_dotcom %} may send {% data variables.product.prodname_dependabot %} alerts to repositories affected by a vulnerability disclosed by a recently published {% data variables.product.prodname_dotcom %} security advisory. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#dependabot-alerts-for-published-security-advisories)". +{% data variables.product.prodname_dotcom %} pode enviar alertas de {% data variables.product.prodname_dependabot %} a repositórios afetados por uma vulnerabilidade revelada por uma consultoria de segurança publicada recentemente em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#dependabot-alerts-for-published-security-advisories)". {% data variables.product.prodname_dependabot %} verifica se é possível atualizar a dependência vulnerável para uma versão fixa sem comprometer o gráfico de dependências para o repositório. Em seguida, {% data variables.product.prodname_dependabot %} levanta um pull request para atualizar a dependência para a versão mínima que inclui o patch e os links do pull request para o alerta de {% data variables.product.prodname_dependabot %} ou relata um erro no alerta. Para obter mais informações, consulte "[Solução de problemas de erros de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md index 017aea28af..1b5dd751fe 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/about-dependabot-version-updates.md @@ -12,8 +12,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Sobre o {% data variables.product.prodname_dependabot_version_updates %} O {% data variables.product.prodname_dependabot %} facilita a manutenção de suas dependências. Você pode usá-lo para garantir que seu repositório se mantenha atualizado automaticamente com as versões mais recentes dos pacotes e aplicações do qual ele depende. diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/about-dependency-review.md index 1ee0859095..572e15e9db 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/about-dependency-review.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/about-dependency-review.md @@ -1,6 +1,6 @@ --- title: Sobre revisão de dependências -intro: 'Dependency review lets you catch vulnerable dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.' +intro: 'A revisão de dependências permite que você capture dependências vulneráveis antes de introduzi-las no seu ambiente e fornece informações sobre licença, dependências e idade das dependências.' versions: free-pro-team: '*' topics: @@ -26,8 +26,8 @@ Revisão de dependência está disponível em: Às vezes, você pode apenas querer atualizar a versão de uma dependência em um manifesto e gerar um pull request. No entanto, se a versão atualizada desta dependência direta também atualizou as dependências, seu pull request pode ter mais alterações do que o esperado. A revisão de dependência para cada manifesto e arquivo de bloqueio fornece uma maneira fácil de ver o que foi alterado e se alguma das novas versões de dependências contém vulnerabilidades conhecidas. -Ao verificar as revisões de dependências em um pull request e alterar todas as dependências sinalizadas como vulneráveis, você pode evitar que vulnerabilidades sejam adicionadas ao seu projeto. For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +Ao verificar as revisões de dependências em um pull request e alterar todas as dependências sinalizadas como vulneráveis, você pode evitar que vulnerabilidades sejam adicionadas ao seu projeto. Para obter mais informações sobre como funciona a revisão de dependências, consulte "[Revisar as alterações de dependência em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". -{% 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 problems at a later date. Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". +{% data variables.product.prodname_dependabot_alerts %} encontrará vulnerabilidades que já estão nas suas dependências, mas é muito melhor evitar a introdução de possíveis problemas do que corrigir problemas em uma data posterior. Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". A revisão de dependências é compatível com as mesmas linguagens e os mesmos ecossistemas de gestão de pacotes do gráfico de dependência. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md index 7220069c05..870108dc8b 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/about-managing-vulnerable-dependencies.md @@ -17,7 +17,7 @@ topics: O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Ele mostra os ecossistemas e pacotes dos quais a sua base de código depende (suas dependências) e os repositórios e pacotes que dependem do seu projeto (suas dependências). As informações no gráfico de dependências são usadas pela revisão das dependências e {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". #### Revisão de dependência -Ao verificar as revisões de dependências nos pull requests, você pode evitar a introdução de vulnerabilidades de dependências na sua base de código. Se os pull requests adicionarem uma dependência vulnerável, ou alterarem a dependência a uma versão vulnerável, isso será destacado na revisão de dependências. Você pode alterar a dependência para uma versão alterada antes de realizar o merge do pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." +Ao verificar as revisões de dependências nos pull requests, você pode evitar a introdução de vulnerabilidades de dependências na sua base de código. Se os pull requests adicionarem uma dependência vulnerável, ou alterarem a dependência a uma versão vulnerável, isso será destacado na revisão de dependências. Você pode alterar a dependência para uma versão alterada antes de realizar o merge do pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". #### {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dotcom %} pode criar {% data variables.product.prodname_dependabot_alerts %} quando detectar dependências vulneráveis no seu repositório. O alerta é exibido na aba Segurança do repositório. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. {% data variables.product.prodname_dotcom %} também notifica os mantenedores do repositório, de acordo com as suas preferências de notificação. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" diff --git a/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md index e5cf12e06a..203fcebe0f 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/about-the-dependency-graph.md @@ -28,7 +28,7 @@ O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armaze Ao fazer push de um commit para {% data variables.product.product_name %} que altera ou adiciona um manifesto compatível ou um arquivo de bloqueio para o branch-padrão, o gráfico de dependências é atualizado automaticamente.{% if currentVersion == "free-pro-team@latest" %} Além disso, o gráfico é atualizado quando alguém faz push de uma alteração no repositório de uma de suas dependências.{% endif %} Para informações sobre os ecossistemas compatíveis e arquivos de manifesto, consulte "[ecossistemas de pacote compatíveis](#supported-package-ecosystems)" abaixo. {% if currentVersion == "free-pro-team@latest" %} -Ao criar um pull request que contém alterações para dependências direcionadas ao branch padrão, {% data variables.product.prodname_dotcom %} usará o gráfico de dependências para adicionar revisões de dependências ao pull request. Eles indicam se as dependências contêm vulnerabilidades e, em caso afirmativo, a versão da dependência na qual a vulnerabilidade foi corrigida. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." +Ao criar um pull request que contém alterações para dependências direcionadas ao branch padrão, {% data variables.product.prodname_dotcom %} usará o gráfico de dependências para adicionar revisões de dependências ao pull request. Eles indicam se as dependências contêm vulnerabilidades e, em caso afirmativo, a versão da dependência na qual a vulnerabilidade foi corrigida. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". {% endif %} ### Dependências incluídas @@ -90,6 +90,6 @@ Os formatos recomendados definem explicitamente quais versões são usadas para - "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia - "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Visualizar ideias para sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md index bbb67674ed..a10b8bf2c1 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md @@ -11,8 +11,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Sobre o arquivo *dependabot.yml* O arquivo de configuração do {% data variables.product.prodname_dependabot %} , *dependabot.yml*, usa a sintaxe YAML. Se você não souber o que é YAMLe quiser saber mais, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". @@ -323,7 +321,7 @@ updates: {% note %} -**Observação**: {% data variables.product.prodname_dependabot %} só pode executar atualizações de versão no manifesto ou em arquivos de bloqueio se puder acessar todas as dependências do arquivo, ainda que você adicione dependências inacessíveis à opção `ignorar` do seu arquivo de configuração. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" e "[Solução de problemas de erros de {% data variables.product.prodname_dependabot %} ](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)". +**Observação**: {% data variables.product.prodname_dependabot %} só pode executar atualizações de versão no manifesto ou em arquivos de bloqueio se puder acessar todas as dependências do arquivo, ainda que você adicione dependências inacessíveis à opção `ignorar` do seu arquivo de configuração. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" e "[Solução de problemas de erros de {% data variables.product.prodname_dependabot %} ](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)". {% endnote %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md index c8715c2e49..45e4e95b41 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md @@ -49,7 +49,7 @@ Se as atualizações de segurança não estiverem habilitadas para o seu reposit Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para um repositório individual (veja abaixo). -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)". +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. 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](/organizations/keeping-your-organization-secure/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)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md index 9e339bb2a9..1686f9bc6a 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md @@ -16,7 +16,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}Quando {% data variables.product.prodname_dependabot %} detecta dependências vulneráveis nos seus repositórios, geramos um alerta {% data variables.product.prodname_dependabot %} e exibimo-lo na aba Segurança do repositório. {% data variables.product.product_name %} notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação.{% else %}Quando {% data variables.product.product_name %} detecta dependências vulneráveis no seu repositório, ele envia alertas de segurança.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} está habilitado por padrão em todos os repositórios públicos. Para {% data variables.product.prodname_dependabot_alerts %}, por padrão, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail, agrupado pela vulnerabilidade específica. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}Se você é proprietário de uma organização, você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios da sua organização com um clique. Você também pode definir se a detecção de dependências vulneráveis será habilitada ou desabilitada para repositórios recém-criados. 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)". +{% if currentVersion == "free-pro-team@latest" %}Se você é proprietário de uma organização, você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios da sua organização com um clique. Você também pode definir se a detecção de dependências vulneráveis será habilitada ou desabilitada para repositórios recém-criados. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/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" %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/customizing-dependency-updates.md index 0581bec427..4d9c0c40d8 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/customizing-dependency-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/customizing-dependency-updates.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Sobre a personalização de atualizações de dependências Depois que você habilitou as atualizações de versão, você pode personalizar a forma como o {% data variables.product.prodname_dependabot %} mantém suas dependências adicionando mais opções ao arquivo *dependabot.yml*. Por exemplo, você pode: diff --git a/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md index 6350b8fe47..0bef6892ae 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md @@ -12,8 +12,6 @@ topics: -{% data reusables.dependabot.beta-note-no-link %} - ### Sobre atualizações de versão para dependências Você habilita {% data variables.product.prodname_dependabot_version_updates %}, verificando um arquivo de configuração *dependabot.yml* no diretório do seu repositório `.github`. Em seguida, o {% data variables.product.prodname_dependabot %} cria um pull request para manter as dependências que você configura atualizadas. Para cada dependência do gerenciador de pacotes que você deseja atualizar, você deve especificar a localização dos arquivos de manifesto do pacote e a frequência de busca por atualizações nas dependências listadas nesses arquivos. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -97,30 +95,30 @@ Quando você desabilita dependências, você pode usar cartões curingas para co O exemplo de arquivo *dependabot.yml* abaixo inclui exemplos das diferentes maneiras de desabilitar atualizações para algumas dependências, ao mesmo tempo que permite que outras atualizações continuem. ```yaml -# arquivo dependabot.yml file com atualizações -# desabilitado para Docker e limitado para npm +# dependabot.yml file with updates +# disabled for Docker and limited for npm version: 2 updates: - # Configuração para Dockerfile + # Configuration for Dockerfile - package-ecosystem: "docker" directory: "/" schedule: interval: "weekly" - # Desabilitar todas as pull requests para dependências Docker + # Disable all pull requests for Docker dependencies open-pull-requests-limit: 0 - # Configuração para npm + # Configuration for npm - package-ecosystem: "npm" directory: "/" schedule: interval: "daily" - # Substituir quaisquer ignores criados usando os comandos "@dependabot ignore" + # Overwrite any ignores created using `@dependabot ignore` commands ignore: - # Ignorar atualizações de pacotes que comecem com "aws" - # Curingas correspondentes a zero ou outros caracteres arbitrários + # Ignore updates to packages that start with 'aws' + # Wildcards match zero or more arbitrary characters - dependency-name: "aws*" - # Ignorar algumas atualizações do pacote "express" + # 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"] diff --git a/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md index 920a49919d..b7df9ff374 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md @@ -74,7 +74,7 @@ Para repositórios públicos, a vista de dependentes mostra como o repositório Os administradores de repositórios podem habilitar ou desabilitar o gráfico de dependências em repositórios privados. -Você também pode habilitar ou desabilitar o gráfico de dependências 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)". +Você também pode habilitar ou desabilitar o gráfico de dependências para todos os repositórios pertencentes à sua conta de usuário ou organização. 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -114,7 +114,7 @@ Se um arquivo de manifesto ou de bloqueio não for processado, suas dependência ### Leia mais - "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- "[Visualizar ideias para sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/github/understanding-how-github-uses-and-protects-your-data)" {% endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md index ff6ccea829..1c69d82d41 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Sobre {% data variables.product.prodname_dependabot_version_updates %} para ações Ações são frequentemente atualizadas com correções de bugs e novos recursos para tornar os processos automatizados mais confiáveis, mais rápidos e mais seguros. Quando você habilitar {% data variables.product.prodname_dependabot_version_updates %} para {% data variables.product.prodname_actions %}, o {% data variables.product.prodname_dependabot %} ajudará a garantir que referências a ações em um arquivo *workflow.yml* de um repositório são mantidas atualizadas. Para cada ação no arquivo, {% data variables.product.prodname_dependabot %} verifica a referência da ação (tipicamente, um número de versão ou identificador de commit associado à ação) em relação à versão mais recente. Se uma versão mais recente da ação estiver disponível, o {% data variables.product.prodname_dependabot %} enviará para você uma pull request que atualizará a referência no arquivo de fluxo de trabalho para a versão mais recente. Para obter mais informações sobre o {% data variables.product.prodname_dependabot_version_updates %}, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". Para obter mais informações sobre a configuração dos fluxos de trabalho para {% data variables.product.prodname_actions %}, consulte "[Aprender {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md index d43069bdfb..07efd820bc 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Visualizando dependências monitoradas por {% data variables.product.prodname_dependabot %} Depois de habilitar as atualizações de versão, você pode confirmar que a sua configuração está correta usando a aba **{% data variables.product.prodname_dependabot %}** no gráfico de dependências para o repositório. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)." diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md index 4de75b1bcb..f676e45d87 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Sobre pull requests {% data variables.product.prodname_dependabot %} {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md index 763f0def61..1055b1eb8c 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md @@ -11,8 +11,6 @@ topics: - segurança --- -{% data reusables.dependabot.beta-note %} - ### Sobre os erros do {% data variables.product.prodname_dependabot %} {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md index 166eb699ae..6038b5f640 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md @@ -1,6 +1,6 @@ --- title: Documentar seu projeto com wikis -shortTitle: Using wikis +shortTitle: Usando wikis intro: 'Você pode usar um wiki para compartilhar informações longas e detalhadas sobre seu projeto.' redirect_from: - /categories/49/articles/ diff --git a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/index.md b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/index.md index aeadbb80a9..9daa838788 100644 --- a/translations/pt-BR/content/communities/maintaining-your-safety-on-github/index.md +++ b/translations/pt-BR/content/communities/maintaining-your-safety-on-github/index.md @@ -1,6 +1,6 @@ --- title: Mantendo sua segurança no GitHub -shortTitle: Maintaining safety +shortTitle: Mantendo a segurança intro: 'Para criar um ambiente positivo e seguro para você e a comunidade para o seu projeto em {% data variables.product.prodname_dotcom %}, você pode bloquear e desbloquear usuários e relatar conteúdo disruptivo.' redirect_from: - /articles/encouraging-positive-contributions-in-your-organization diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md index 0b16946a52..43f98df4d3 100644 --- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md +++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md @@ -1,6 +1,6 @@ --- title: Moderar comentários e conversas -shortTitle: Moderation +shortTitle: Moderação intro: 'A moderação de conversas cria um ambiente acolhedor na comunidade para todos os contribuidores de seu projeto, promovendo uma colaboração sadia e mitigando conflitos. Você pode colocar em prática o código de conduta da comunidade para discussões ao visualizar conteúdo denunciado, editar e excluir comentários e bloquear conversas.' redirect_from: - /articles/moderating-comments-and-conversations 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 622edbcf45..b50c3ca39f 100644 --- a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md @@ -86,18 +86,18 @@ Troque este `código` por um token de acesso: Por padrão, a resposta assume o seguinte formato: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer Você também pode receber o conteúdo em diferentes formatos, dependendo do cabeçalho Aceitar: Accept: application/json - {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} + {"access_token":"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} Accept: application/xml bearer repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} #### 3. Use o token de acesso para acessar a API @@ -207,7 +207,7 @@ Uma vez que o usuário tenha autorizado, o aplicativo receberá um token de aces ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "user" } @@ -304,3 +304,7 @@ Para criar esse vínculo, você precisará do `client_id` dos aplicativos OAuth, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} * "[Erros do fluxo do dispositivo](#errors-for-the-device-flow)" {% endif %} + +### Leia mais + +- "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md index 3d0051eba8..962f88daa0 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -54,16 +54,18 @@ A pessoa que está criando o aplicativo será redirecionada para uma página do ##### Parâmetros do manifesto do aplicativo GitHub - | Nome | Tipo | Descrição | - | --------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `string` | O nome do aplicativo GitHub. | - | `url` | `string` | **Obrigatório.** A página inicial do seu aplicativo GitHub. | - | `hook_attributes` | `objeto` | A configuração do webhook do aplicativo GitHub. | - | `redirect_url` | `string` | A URL completa para onde redirecionar depois que a pessoa instalar o aplicativo GitHub. | - | `descrição` | `string` | Uma descrição do aplicativo GitHub. | - | `público` | `boolean` | Defina como `verdadeiro` quando o seu aplicativo GitHub estiver disponível para o público ou `falso` quando for acessível somente pelo proprietário do aplicativo. | - | `default_events` | `array` | Lista de [eventos](/webhooks/event-payloads) assinada pelo aplicativo GitHub. | - | `default_permissions` | `objeto` | O conjunto de [permissões](/rest/reference/permissions-required-for-github-apps) exigido pelo aplicativo GitHub. O formato do objeto usa o nome de permissão para a chave (por exemplo, `problemas`) e o tipo de acesso para o valor (por exemplo, `gravar`). | + | Nome | Tipo | Descrição | + | --------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `string` | O nome do aplicativo GitHub. | + | `url` | `string` | **Obrigatório.** A página inicial do seu aplicativo GitHub. | + | `hook_attributes` | `objeto` | A configuração do webhook do aplicativo GitHub. | + | `redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array de strigns` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %} + | `callback_url` | `string` | A full URL to redirect to after someone authorizes an installation.{% endif %} + | `descrição` | `string` | Uma descrição do aplicativo GitHub. | + | `público` | `boolean` | Defina como `verdadeiro` quando o seu aplicativo GitHub estiver disponível para o público ou `falso` quando for acessível somente pelo proprietário do aplicativo. | + | `default_events` | `array` | Lista de [eventos](/webhooks/event-payloads) assinada pelo aplicativo GitHub. | + | `default_permissions` | `objeto` | O conjunto de [permissões](/rest/reference/permissions-required-for-github-apps) exigido pelo aplicativo GitHub. O formato do objeto usa o nome de permissão para a chave (por exemplo, `problemas`) e o tipo de acesso para o valor (por exemplo, `gravar`). | O objeto `hook_attributes` tem a chave a seguir: @@ -84,7 +86,7 @@ Este exemplo usa um formulário em uma página web com um botão que aciona a so ```html
- Criar um manifesto do aplicativo GitHub:
+ Create a GitHub App Manifest:
@@ -96,7 +98,10 @@ Este exemplo usa um formulário em uma página web com um botão que aciona a so "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -111,11 +116,12 @@ Este exemplo usa um formulário em uma página web com um botão que aciona a so }) ``` + Este exemplo usa um formulário em uma página web com um botão que aciona a solicitação `POST` para uma conta da organização. Substitua `ORGANIZAÇÃO` pelo nome da conta da organização em que você deseja criar o aplicativo. ```html -
- Criar um manifesto do aplicativo GitHub:
+ + Create a GitHub App Manifest:
@@ -127,7 +133,10 @@ Este exemplo usa um formulário em uma página web com um botão que aciona a so "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -147,11 +156,11 @@ Este exemplo usa um formulário em uma página web com um botão que aciona a so Quando a pessoa clica em **Criar aplicativo GitHub**, O GitHub redireciona para o `redirect_url` com um `código` temporário em um parâmetro de código. Por exemplo: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 Se você forneceu um parâmetro `estado`, você também verá esse parâmetro em `redirect_url`. Por exemplo: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 #### 3. Você troca o código temporário para recuperar a configuração do aplicativo diff --git a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md index dca067aacb..a05deeaa66 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -22,9 +22,15 @@ A pessoa que está criando o aplicativo pode editar os valores pré-selecionados A URL a seguir cria um novo aplicativo pública denominado `octocat-github-app` com uma descrição pré-configurada e URL de chamada de retorno. Esta URL também seleciona permissões de leitura e gravação para `verificações`, inscreve-se nos eventos webhook de check_run` e check_suite` e seleciona a opção de solicitar autorização do usuário (OAuth) durante a instalação: - ``` - {% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite - ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} +``` +{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite +``` +{% else %} +``` +{% 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 +``` +{% endif %} Lista completa de parâmetros de consulta, permissões e eventos disponíveis encontra-se nas seções abaixo. @@ -34,8 +40,9 @@ Lista completa de parâmetros de consulta, permissões e eventos disponíveis en | -------------------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | `string` | O nome do {% data variables.product.prodname_github_app %}. Dê um nome claro e sucinto ao seu aplicativo. Seu aplicativo não pode ter o mesmo nome de um usuário existente no GitHub, a menos que seja o seu próprio nome de usuário ou da sua organização. Uma versão movida do nome do seu aplicativo será exibida na interface do usuário quando sua integração realizar uma ação. | | `descrição` | `string` | Uma descrição do {% data variables.product.prodname_github_app %}. | - | `url` | `string` | A URL completa da página inicial do site do seu {% data variables.product.prodname_github_app %}. | - | `callback_url` | `string` | A URL completa para onde redirecionar após alguém autorizar uma instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. | + | `url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array de strigns` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} + | `callback_url` | `string` | A URL completa para onde redirecionar após alguém autorizar uma instalação. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} | `request_oauth_on_install` | `boolean` | Se seu aplicativo autoriza usuários a usar o fluxo OAuth, você poderá definir essa opção como `verdadeiro` para permitir que pessoas autorizem o aplicativo ao instalá-lo, economizando um passo. Se você selecionar esta opção, `setup_url` irá tornar-se indisponível e os usuários serão redirecionados para sua `callback_url` após instalar o aplicativo. | | `setup_url` | `string` | A URL completa para redirecionamento após alguém instalar o {% data variables.product.prodname_github_app %}, se o aplicativo precisar de configuração adicional após a instalação. | | `setup_on_update` | `boolean` | Defina como `verdadeiro` para redirecionar as pessoas para a URL de configuração quando as instalações forem atualizadas, por exemplo, após os repositórios serem adicionados ou removidos. | 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 755df0916e..b52a736696 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 @@ -845,7 +845,7 @@ Aqui estão alguns problemas comuns e algumas soluções sugeridas. Se você tiv **R:** Se você vir o erro a seguir, você não excluiu o excluiu ou fez o checkout do repositório em um ou ambos os métodos `initiate_check_run` ou `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: o caminho do destino 'Octocat-breeds' já existe e não é um diretório vazio.: + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: ``` Compare seu código com o arquivo `server.rb` para garantir que você tenha o mesmo código nos seus métodos `initiate_check_run` e `take_requested_action`. diff --git a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index ace8434c6c..fae2ecb098 100644 --- a/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -94,9 +94,9 @@ Por padrão, a resposta assume o seguinte formato. Os parâmetros de resposta `e ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -106,7 +106,7 @@ Por padrão, a resposta assume o seguinte formato. Os parâmetros de resposta `e Por padrão, a resposta assume o seguinte formato: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer {% endif %} @@ -934,3 +934,11 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de * [Obter um fluxo de trabalho](/rest/reference/actions#get-a-workflow) * [Obter uso do workflow](/rest/reference/actions#get-workflow-usage) {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Leia mais + +- "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md index ea3dfa0a3d..e3129d0663 100644 --- a/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,9 +42,9 @@ Esta solicitação de retorno de chamada enviará um novo token de acesso e um n ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" @@ -73,3 +73,11 @@ Se você desejar que o seu aplicativo use tokens de acesso do usuário para serv Os {% data variables.product.prodname_github_app %}s existentes que usam tokens de autorização de usuário para servidor são afetados apenas por este novo fluxo quando o proprietário do aplicativo habilita expirar tokens de usuário para seu aplicativo. Habilitar a expiração de tokens de usuário para {% data variables.product.prodname_github_app %}s existentes exige o envio de usuários através do fluxo do OAuth para reemitir tokens de usuário que expirarão em 8 horas e fazer uma solicitação com o token de atualização para obter um novo token de acesso e token de atualização. Para obter mais informações, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Leia mais + +- "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md index 9588be43a1..0f87aed5e5 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 @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - aplicativos oauth --- Ao configurar um aplicativo OAuth no GitHub, os escopos solicitados são exibidos para o usuário no formulário de autorização. @@ -39,19 +41,19 @@ X-Accepted-OAuth-Scopes: user ### Escopos disponíveis | Nome | Descrição | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| **`(sem escopo)`** | Concede acesso somente leitura a informações públicas (inclui informações de perfil do usuário público, informações de repositório público e gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion != "github-ae@latest" %} +| **`(sem escopo)`** | Concede acesso somente leitura a informações públicas (incluindo informações do perfil do usuário, informações do repositório e gists){% endif %}{% 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 aos repositórios, incluindo repositórios privados. 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. Também concede capacidade para gerenciar projetos de usuário. | +|  `repo:status` | Concede acesso de leitura/gravação a {% if currentVersion != "github-ae@latest" %}público{% else %}interno{% endif %} e status do commit do repositório 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 da implementação](/rest/reference/repos#deployments) para {% if currentVersion != "github-ae@latest" %}público{% else %}interno{% endif %} e repositórios privados. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de implantação, *sem* conceder acesso ao código. {% se a correnteVersion != "github-ae@latest" %} +|  `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 como favoritos.{% endif %} |  `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 a eventos de segurança na [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
acesso de leitura e gravação a eventos de segurança na [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
Este escopo só é necessário para conceder acesso de outros usuários ou serviços a eventos de segurança *sem* conceder acesso ao código.{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} |  `security_events` | Concede acesso de leitura e gravação a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning). Este escopo só é necessário para conceder a outros usuários ou serviços acesso a eventos de segurança *sem* conceder acesso ao código.{% 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:repo_hook`** | Concede acesso de leitura, gravação, marcação e exclusão a hooks de repositório em {% if currentVersion != "github-ae@latest" %}público{% else %}interno{% endif %} e repositórios privados. Os escopos do `repositório` {% if currentVersion ! "github-ae@latest" %}e escopos e `public_repo` concedem{% else %}o escopo concede{% endif %} 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, gravação e marcação a hooks em {% if currentVersion != "github-ae@latest" %}público{% else %}interno{% endif %} ou repositórios privados. | +|  `read:repo_hook` | Concede acesso de leitura e gravação a hooks em {% if currentVersion != "github-ae@latest" %}público{% else %}interno{% endif %} ou repositórios 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. | @@ -67,10 +69,10 @@ X-Accepted-OAuth-Scopes: user |  `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" %} +|  `leia:discussion` | Permite acesso de leitura para discussões em equipe.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} | **`write:packages`** | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)". | | **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Instalando um pacote](/github/managing-packages-with-github-packages/installing-a-package)". | -| **`delete:packages`** | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir pacotes](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} +| **`delete:packages`** | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %} | **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | |  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | |  `read:gpg_key` | Liste e visualize informações para as chaves GPG.{% if currentVersion == "free-pro-team@latest" %} @@ -78,11 +80,11 @@ X-Accepted-OAuth-Scopes: user {% note %} -**Observação:** O seu aplicativo OAuth pode solicitar os escopos no redirecionamento inicial. Você pode especificar vários escopos separando-os com um espaço: +**Observação:** O seu aplicativo OAuth pode solicitar os escopos no redirecionamento inicial. Você pode especificar vários escopos separando-os com um espaço usando `%20`: https://github.com/login/oauth/authorize? client_id=...& - scope=user%20public_repo + scope=user%20repo_deployment {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md b/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md index 1136f76487..2676928128 100644 --- a/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md +++ b/translations/pt-BR/content/developers/github-marketplace/about-marketplace-badges.md @@ -13,7 +13,7 @@ Certain apps on the {% data variables.product.prodname_marketplace %} have the { - Verified ownership of their domain and has a verified badge on their profile - Confirmou o endereço de e-mail da empresa, para que o suporte de {% data variables.product.prodname_dotcom %} possa entrar em contato com a empresa -- Exigiu a autenticação de dois fatores para sua organização. Para obter mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." +- Exigiu a autenticação de dois fatores para sua organização. Para obter mais informações, consulte "[Exigir autenticação de dois fatores em sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)". ![Selo do Marketplace para Aplicativos GitHub](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png) diff --git a/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md index 5bcf4dfcc0..08d568e18f 100644 --- a/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md +++ b/translations/pt-BR/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -22,8 +22,8 @@ Para oferecer planos pagos para o seu aplicativo, este deverá pertencer a uma o 1. Em "Configurações de desenvolvedor", clique em **Verificação do publicador**. ![Opção de verificação do editor na barra lateral de configurações da organização](/assets/images/marketplace/publisher-verification-settings-option.png) 1. Em "Verificação do Publicador, preencha as informações na lista de verificação: - Certifique-se de que as suas informações básicas do perfil estejam presentes e precisas. Além disso, certifique-se de incluir o melhor endereço de e-mail para suporte e atualizações de {% data variables.product.company_short %}. - - Certifique-se de que a autenticação de dois fatores esteja habilitada para a sua organização. Para obter mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)." - - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. Para obter informações relacionadas, consulte "[Verificar o domínio da sua organização](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)". + - Certifique-se de que a autenticação de dois fatores esteja habilitada para a sua organização. Para obter mais informações, consulte "[Exigir autenticação de dois fatores em sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)". + - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. Para obter informações relacionadas, consulte "[Verificar o domínio da sua organização](/organizations/managing-organization-settings/verifying-your-organizations-domain)". ![Lista de verificação do publicador](/assets/images/marketplace/publisher-verification-checklist.png) diff --git a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md index 0dd6df694e..7f629bf9ae 100644 --- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md +++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md @@ -124,6 +124,44 @@ $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% el +### Server-to-server tokens + +If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. + +Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps). + + + +##### Prós + +- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API). +- Dedicated rate limits that grow with your organization. +- Decoupled from GitHub user identities, so they do not consume any licensed seats. +- Never granted a password, so cannot be directly signed in to. + + + +##### Contras + +- Additional setup is needed to create the GitHub App. +- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code. + + + +##### Configuração + +1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private. +1. Determine the permissions your GitHub App requires, such as read-only access to repository contents. +1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app). +1. Note your GitHub App `id`. +1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key). +1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization. +1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). +1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). +1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client. + + + ### Usuários máquina Se o seu servidor precisar acessar vários repositórios, você poderá criar uma conta nova no {% data variables.product.product_name %} e anexar uma chave SSH que será usada exclusivamente para automação. Como esta conta do {% data variables.product.product_name %} não será usada por uma pessoa, ela será denominada _usuário máquina_. É possível adicionar o usuário máquina como [colaborador][collaborator] em um repositório pessoal (concedendo acesso de leitura e gravação), como [colaborador externo][outside-collaborator] em um repositório da organização (concedendo leitura, acesso gravação, ou administrador) ou como uma [equipe][team], com acesso aos repositórios que precisa automatizar (concedendo as permissões da equipe). diff --git a/translations/pt-BR/content/developers/overview/secret-scanning.md b/translations/pt-BR/content/developers/overview/secret-scanning.md index 956ab7b739..682e9c6541 100644 --- a/translations/pt-BR/content/developers/overview/secret-scanning.md +++ b/translations/pt-BR/content/developers/overview/secret-scanning.md @@ -17,12 +17,6 @@ Quando uma correspondência do seu formato secreto é encontrada em um repositó Quando uma correspondência do formato do segredo é encontrada em um repositório privado configurado para {% data variables.product.prodname_secret_scanning %}, os administradores do repositório são alertados e podem visualizar e gerenciar os resultados {% data variables.product.prodname_secret_scanning %} em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -{% note %} - -**Observação:** {% data variables.product.prodname_secret_scanning_caps %} para repositórios privados está atualmente em beta. - -{% endnote %} - Este artigo descreve como fazer parceria com {% data variables.product.prodname_dotcom %} como um provedor de serviço e participa do programa de {% data variables.product.prodname_secret_scanning %}. ### O processo de {% data variables.product.prodname_secret_scanning %} 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 1d28c56aa5..26fc2da68d 100644 --- a/translations/pt-BR/content/developers/overview/viewing-deployment-history.md +++ b/translations/pt-BR/content/developers/overview/viewing-deployment-history.md @@ -5,13 +5,18 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- {% 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) +Para visualizar implantações atuais e anteriores, clique em **Ambientes** na página inicial do repositório. +{% if currentVersion == "github-ae@latest" or currentVersion ver_lt "enterprise-server@3.0" %} +![Ambientes](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} A página de implantações exibe a última implantação ativa de cada ambiente do seu repositório. Se a implantação inclui uma URL de ambiente, será exibido um botão "Exibir implantação" que vincula à URL ao lado da implantação. diff --git a/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md index 3123eb3183..77417d6fa5 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/about-webhooks.md @@ -1,34 +1,36 @@ --- -title: About webhooks -intro: Learn the basics of how webhooks work to help you build and set up integrations. +title: Sobre webhooks +intro: Aprenda os princípios básicos de como os webhooks funcionam para ajudá-lo a criar e configurar integrações. redirect_from: - /webhooks versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - webhooks --- -Webhooks allow you to build or set up integrations, such as [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), which subscribe to certain events on GitHub.com. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. You're only limited by your imagination. +Os webhooks permitem que você crie ou configure integrações, como [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) ou [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), que assinam determinados eventos no GitHub.com. Quando um desses eventos é acionado, enviaremos uma carga de POST por HTTP POST para a URL de configuração do webhook. Os webhooks podem ser usados para atualizar um rastreador de problemas externo, acionar criações de CI, atualizar um espelho de backup, ou até mesmo fazer uma implantação no seu servidor de produção. A sua imaginação é o único limite. -Webhooks can be installed on{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} an [organization][org-hooks], a specific [repository][repo-hooks], or a {% data variables.product.prodname_github_app %}. Once installed, the webhook will be sent each time one or more subscribed events occurs. +Os webhooks podem ser instalados em{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} uma [organização][org-hooks], em um repositório[específico][repo-hooks] ou em {% data variables.product.prodname_github_app %}. Uma vez instalado, o webhook será enviado cada vez que ocorrer um ou mais eventos assinados. -You can create up to {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %} webhooks for each event on each installation target {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}({% data variables.product.prodname_ghe_server %} instance, specific organization, or specific repository).{% else %}(specific organization or specific repository).{% endif %} +Você pode criar até {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %} webhooks para cada evento em cada destino de instalação {% if enterpriseServerVersions contains currentVersion or currentVersion or currentVersion == "github-ae@latest" %}(instância de {% data variables.product.prodname_ghe_server %}, organização específica ou repositório específico).{% else %}(organização específica ou repositório específico).{% endif %} -### Events +### Eventos {% data reusables.webhooks.webhooks_intro %} -Each event corresponds to a certain set of actions that can happen to your organization and/or repository. For example, if you subscribe to the `issues` event you'll receive detailed payloads every time an issue is opened, closed, labeled, etc. +Cada evento corresponde a um certo conjunto de ações que podem ocorrer na sua organização e/ou repositório. Por exemplo, se você assinar o evento `problemas`, você receberá cargas detalhadas toda vez que uma tarefa for aberta, fechada, etiquetada, etc. -See "[Webhook event payloads](/webhooks/event-payloads)" for the list of available webhook events and their payloads. +For a complete list of available webhook events and their payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." -### Ping event +### Evento de ping {% data reusables.webhooks.ping_short_desc %} -For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. +Para obter mais informações sobre a carga do webhook do evento de `ping`, consulte o evento [`ping`](/webhooks/event-payloads/#ping). [org-hooks]: /rest/reference/orgs#webhooks/ [repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md b/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md index f7dd0725a7..bf9b284524 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/github-event-types.md @@ -183,6 +183,20 @@ Este evento retorna um objeto de `carga` vazio. {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} +### PullRequestReviewEvent + +{% data reusables.webhooks.pull_request_review_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Objeto da `carga` do evento + +| Tecla | Tipo | Descrição | +| -------------- | -------- | -------------------------------------------- | +| `Ação` | `string` | A ação que foi executada. Pode ser `criado`. | +| `pull_request` | `objeto` | The pull request the review pertains to. | +| `revisar` | `objeto` | A revisão que foi afetada. | + ### PullRequestReviewCommentEvent {% data reusables.webhooks.pull_request_review_comment_short_desc %} @@ -200,6 +214,8 @@ Este evento retorna um objeto de `carga` vazio. {% data reusables.webhooks.events_api_payload %} +#### Objeto da `carga` do evento + | Tecla | Tipo | Descrição | | -------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `push_id` | `inteiro` | Identificador único para o push. | diff --git a/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md index 8d9c3fea5c..5eff572284 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -1,52 +1,53 @@ --- -title: Securing your webhooks -intro: 'Ensure your server is only receiving the expected {% data variables.product.prodname_dotcom %} requests for security reasons.' +title: Protegendo seus webhooks +intro: 'Certifique-se de que seu servidor só esteja recebendo as solicitações esperadas do {% data variables.product.prodname_dotcom %} por motivos de segurança.' redirect_from: - /webhooks/securing versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - webhooks --- -Once your server is configured to receive payloads, it'll listen for any payload sent to the endpoint you configured. For security reasons, you probably want to limit requests to those coming from GitHub. There are a few ways to go about this--for example, you could opt to allow requests from GitHub's IP address--but a far easier method is to set up a secret token and validate the information. +Assim que seu servidor estiver configurado para receber cargas, ele ouvirá qualquer carga enviada para o ponto de extremidade que você configurou. Por motivos de segurança, você provavelmente vai querer limitar os pedidos para aqueles provenientes do GitHub. Existem algumas maneiras de fazer isso. Você poderia, por exemplo, optar por permitir solicitações do endereço IP do GitHub. No entanto, um método muito mais fácil é configurar um token secreto e validar a informação. {% data reusables.webhooks.webhooks-rest-api-links %} -### Setting your secret token +### Definir seu token secreto -You'll need to set up your secret token in two places: GitHub and your server. +Você precisará configurar seu token secreto em dois lugares: no GitHub e no seu servidor. -To set your token on GitHub: +Para definir seu token no GitHub: -1. Navigate to the repository where you're setting up your webhook. -2. Fill out the Secret textbox. Use a random string with high entropy (e.g., by taking the output of `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` at the terminal). -![Webhook secret token field](/assets/images/webhook_secret_token.png) -3. Click **Update Webhook**. +1. Navegue até o repositório onde você está configurando seu webhook. +2. Preencha a caixa de texto do segredo. Use uma string aleatória com alta entropia (por exemplo, pegando a saída de `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` no terminal). ![Campo de webhook e token secreto](/assets/images/webhook_secret_token.png) +3. Clique em **Atualizar o webhook**. -Next, set up an environment variable on your server that stores this token. Typically, this is as simple as running: +Em seguida, configure uma variável de ambiente em seu servidor que armazene este token. Normalmente, isso é tão simples quanto executar: ```shell $ export SECRET_TOKEN=your_token ``` -**Never** hardcode the token into your app! +**Nunca** pré-programe o token no seu aplicativo! -### Validating payloads from GitHub +### Validar cargas do GitHub -When your secret token is set, {% data variables.product.product_name %} uses it to create a hash signature with each payload. This hash signature is included with the headers of each request as {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature`{% endif %}. +Quando seu token secreto está definido, {% data variables.product.product_name %} o utiliza para criar uma assinatura de hash com cada carga. Esta assinatura hash está incluída com os cabeçalhos de cada solicitação como {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" ou currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature`{% endif %}. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**Note:** For backward-compatibility, we also include the `X-Hub-Signature` header that is generated using the SHA-1 hash function. If possible, we recommend that you use the `X-Hub-Signature-256` header for improved security. The example below demonstrate using the `X-Hub-Signature-256` header. +**Observação:** Para compatibilidade com versões anteriores, também incluímos o cabeçalho `X-Hub-Signature` gerado usando a função de hash SHA-1. Se possível, recomendamos que você use o cabeçalho `X-Hub-Signature-256` para melhorar a segurança. O exemplo abaixo demonstra o uso do cabeçalho `X-Hub-Signature-256`. {% endnote %} {% endif %} -For example, if you have a basic server that listens for webhooks, it might be configured similar to this: +Por exemplo, se você tem um servidor básico que ouve webhooks, ele poderá ser configurado de forma semelhante a isso: ``` ruby require 'sinatra' @@ -58,7 +59,7 @@ post '/payload' do end ``` -The intention is to calculate a hash using your `SECRET_TOKEN`, and ensure that the result matches the hash from {% data variables.product.product_name %}. {% data variables.product.product_name %} uses an HMAC hex digest to compute the hash, so you could reconfigure your server to look a little like this: +O objetivo é calcular um hash usando seu `SECRET_TOKEN` e garantir que o resultado corresponda ao hash de {% data variables.product.product_name %}. {% data variables.product.product_name %} usa um resumo hexadecimal HMAC para calcular o hash. Portanto, você pode reconfigurar o seu servidor para que se pareça mais ou menos assim: ``` ruby post '/payload' do @@ -80,10 +81,16 @@ def verify_signature(payload_body) end{% endif %} ``` -Your language and server implementations may differ from this example code. However, there are a number of very important things to point out: +{% note %} -* No matter which implementation you use, the hash signature starts with {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or "github-ae@latest" %}`sha256=`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`sha1=`{% endif %}, using the key of your secret token and your payload body. +**Observação:** As cargas de webhook podem conter caracteres de unicode. Se o seu idioma e a implementação de servidor especificarem uma codificação de caracteres, certifique-se de que você manipula a carga como UTF-8. -* Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. +{% endnote %} -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare +A sua linguagem e implementações do servidor podem ser diferentes deste código de exemplo. No entanto, há uma série de aspectos muito importantes a destacar: + +* Não importa qual implementação você usar, a assinatura hash começa com {% if currentVersion == "free-pro-team@latest" ou currentVersion ver_gt "enterprise-server@2. 2" or "github-ae@latest" %}`sha256=`{% elsif currentVersion ver_lt "enterprise-server@2. 3" %}`sha1=`{% endif %}, usando a chave do seu token secreto e o seu texto de carga. + +* Não **se recomenda** usar um operador simples de`==`. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. + +[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md index c5e7d4cd6b..3b05afa186 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -1,6 +1,6 @@ --- -title: Webhook events and payloads -intro: 'For each webhook event, you can review when the event occurs, an example payload, and descriptions about the payload object parameters.' +title: Eventos de webhook e cargas +intro: 'Para cada evento de webhook, você pode revisar quando o evento ocorrer, uma carga de exemplo, bem como as descrições sobre os parâmetros do objeto da carga.' product: '{% data reusables.gated-features.enterprise_account_webhooks %}' redirect_from: - /early-access/integrations/webhooks/ @@ -10,6 +10,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - webhooks --- @@ -19,44 +21,44 @@ versions: {% data reusables.webhooks.webhooks_intro %} -You can create webhooks that subscribe to the events listed on this page. Each webhook event includes a description of the webhook properties and an example payload. For more information, see "[Creating webhooks](/webhooks/creating/)." +Você pode criar webhooks que assinam os eventos listados nesta página. Cada evento de webhook inclui uma descrição das propriedades do webhook e uma carga de exemplo. Para obter mais informações, consulte "[Criar webhooks](/webhooks/creating/)." -### Webhook payload object common properties +### Propriedades comuns do objeto da carga do webhook -Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections. +Cada carga do evento do webhook também contém propriedades únicas para o evento. Você pode encontrar as propriedades únicas nas seções individuais de tipos de evento. -Key | Type | Description -----|------|------------- -`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event. -{% data reusables.webhooks.sender_desc %} This property is included in every webhook payload. -{% data reusables.webhooks.repo_desc %} Webhook payloads contain the `repository` property when the event occurs from activity in a repository. +| Tecla | Tipo | Descrição | +| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A maioria das cargas de webhook contém uma ação `` propriedade que contém a atividade específica que acionou o evento. | +{% data reusables.webhooks.sender_desc %} Esta propriedade está incluída em todas as cargas do webhook. +{% data reusables.webhooks.repo_desc %} As cargas do webhook contêm a propriedade `repository` quando ocorre o evento a partir da atividade em um repositório. {% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)." +{% data reusables.webhooks.app_desc %} Para obter mais informações, consulte "[Criar um {% data variables.product.prodname_github_app %}](/apps/building-github-apps/). -The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. +As propriedades únicas para um evento de webhook são as mesmas propriedades que você encontrará na propriedade `payload` ao usar a [Eventos API](/rest/reference/activity#events). Uma exceção é o evento de [`push`](#push). As propriedades únicas da carga do webhook do evento `push` e a propriedade `carga` na API de eventos são diferentes. A carga do webhook contém informações mais detalhadas. {% tip %} -**Note:** Payloads are capped at 25 MB. If your event generates a larger payload, a webhook will not be fired. This may happen, for example, on a `create` event if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. +**Observação:** As cargas são limitados a 25 MB. Se o seu evento gerar uma carga maior, um webhook não será disparado. Isso pode acontecer, por exemplo, em um evento `criar`, caso muitos branches ou tags sejam carregados de uma só vez. Sugerimos monitorar o tamanho da sua carga para garantir a entrega. {% endtip %} -#### Delivery headers +#### Cabeçalhos de entrega -HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: +As cargas de HTTP POST que são entregues no ponto de extremidade da URL configurado do seu webhook conterão vários cabeçalhos especiais: -Header | Description --------|-------------| -`X-GitHub-Event`| Name of the event that triggered the delivery. -`X-GitHub-Delivery`| A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -`X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. -`X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% if currentVersion != "github-ae@latest" %} -`X-Hub-Signature`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} -`X-Hub-Signature-256`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.{% endif %} +| Header | Descrição | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `X-GitHub-Event` | Nome do evento que ativou a entrega. | +| `X-GitHub-Delivery` | Um [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) para identificar a entrega.{% if enterpriseServerVersions contém currentVersion or currentVersion == "github-ae@latest" %} +| `X-GitHub-Enterprise-Version` | A versão da instância do {% data variables.product.prodname_ghe_server %} que enviou a carga do HTTP POST. | +| `X-GitHub-Enterprise-Host` | O nome do host da instância de {% data variables.product.prodname_ghe_server %} que enviou a carga HTTP POST.{% endif %}{% if currentVersion != "github-ae@latest" %} +| `X-Hub-Signature` | Este cabeçalho é enviado se o webhook for configurado com um [`secret`](/rest/reference/repos#create-hook-config-params). Este é o resumo hexadecimal de HMAC do texto da solicitação e é gerado usando a função hash SHA-1 e `segredo` como a `chave` de HMAC.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` é fornecido para compatibilidade com integrações existentes, e recomendamos que você use um `X-Hub-Signature-256` mais seguro.{% endif %}{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| `X-Hub-Signature-256` | Este cabeçalho é enviado se o webhook for configurado com um [`secret`](/rest/reference/repos#create-hook-config-params). Este é o resumo hexadecimal HMAC do texto da solicitação e é gerado usando a função hash SHA-256 e a `segredo` como a `chave` HMAC.{% endif %} -Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. +Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hookshot/`. -#### Example delivery +#### Exemplo de entrega ```shell > POST /payload HTTP/1.1 @@ -103,13 +105,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} -#### Availability +#### Disponibilidade -- Repository webhooks only receive payloads for the `created` and `completed` event types in a repository -- Organization webhooks only receive payloads for the `created` and `completed` event types in repositories -- {% data variables.product.prodname_github_app %}s with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_app %}s with the `checks:write` are automatically subscribed to this webhook event. +- Os webhooks de repositório só recebem cargas para os tipos de evento `criados` e `concluídos` em um repositório +- Os webhooks da organização só recebem cargas para os tipos de eventos `criados` e `concluídos` nos repositórios +- Os {% data variables.product.prodname_github_app %}s com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `requested_action`. As cargas do tipo de evento `solicitadas` e `requested_action` são enviadas apenas para o {% data variables.product.prodname_github_app %} que está sendo solicitado. Os {% data variables.product.prodname_github_app %}s com `checks:write` são automaticamente inscritos neste evento webhook. -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.check_run_properties %} {% data reusables.webhooks.repo_desc %} @@ -117,7 +119,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.check_run.created }} @@ -127,13 +129,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} -#### Availability +#### Disponibilidade -- Repository webhooks only receive payloads for the `completed` event types in a repository -- Organization webhooks only receive payloads for the `completed` event types in repositories -- {% data variables.product.prodname_github_app %}s with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_app %}s with the `checks:write` are automatically subscribed to this webhook event. +- Os webhooks de repositório só recebem cargas para os tipos de evento `concluídos` em um repositório +- Os webhooks da organização só recebem cargas para os tipos de eventos `concluídos` nos repositórios +- Os {% data variables.product.prodname_github_app %}s com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `ressolicitados.`. As cargas de evento `solicitadas` e `ressolicitadas` são enviadas apenas para {% data variables.product.prodname_github_app %} que está sendo solicitado. Os {% data variables.product.prodname_github_app %}s com `checks:write` são automaticamente inscritos neste evento webhook. -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.check_suite_properties %} {% data reusables.webhooks.repo_desc %} @@ -141,30 +143,31 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.check_suite.completed }} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ### code_scanning_alert -{% data reusables.webhooks.code_scanning_alert_event_short_desc %} +Os {% data variables.product.prodname_github_app %}s com a permissão `security_events` -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `security_events :read` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de `conteúdo` -#### Webhook payload object +#### Objeto da carga do 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` | If the `action` is `reopened_by_user` or `closed_by_user`, the `sender` object will be the user that triggered the event. The `sender` object is empty for all other actions. +remetente`| objeto` | Se a de ação ` for reopened_by_user` ou `closed_by_user`, o objeto `remetente` será o usuário que ativou o evento. O objeto `remetente` é +{% if currentVersion == "free-pro-team@latest" %}`github` {% elsif currentVersion ver_gt "enterprise-server@3.0" %}`github-enterprise` {% else %}empty {% endif %}para todas as outras ações. -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }} @@ -172,13 +175,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.commit_comment_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.commit_comment_properties %} {% data reusables.webhooks.repo_desc %} @@ -186,7 +189,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.commit_comment.created }} {% endif %} @@ -195,11 +198,11 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.content_reference_short_desc %} -Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. +Os eventos de webhook são acionados com base na especificidade do domínio que você registra. Por exemplo, se você registrar um subdomínio (`https://subdomain.example.com`), apenas as URLs para o subdomínio irão ativar este evento. Se você registrar um domínio (`https://example.com`), as URLs para domínio e todos os subdomínios irão ativar este evento. Consulte "[Crie um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment)" para criar um novo anexo de conteúdo. -Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event. +Apenas os {% data variables.product.prodname_github_app %}s podem receber este evento. Os {% data variables.product.prodname_github_app %}s devem ter a permissão de `content_reference` `gravação` para assinar este evento. -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.content_reference.created }} @@ -209,25 +212,26 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% note %} -**Note:** You will not receive a webhook for this event when you push more than three tags at once. +**Observação:** Você não receberá um webhook para este evento ao fazer push de mais de três tags de uma vez. {% endnote %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.create_properties %} +{% data reusables.webhooks.pusher_type_desc %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.create }} @@ -237,25 +241,26 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% note %} -**Note:** You will not receive a webhook for this event when you delete more than three tags at once. +**Observação:** Você não receberá um webhook para este evento ao excluir mais de três tags de uma só vez. {% endnote %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.delete_properties %} +{% data reusables.webhooks.pusher_type_desc %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.delete }} @@ -263,109 +268,163 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.deploy_key_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks +- Webhooks do repositório +- Webhooks da organização -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.deploy_key_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.deploy_key.created }} -### deployment +### implantação {% data reusables.webhooks.deployment_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `deployments` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de `implantação` -#### Webhook payload object +#### Objeto da carga do webhook -Key | Type | Description -----|------|-------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -`action` |`string` | The action performed. Can be `created`.{% endif %} -`deployment` |`object` | The [deployment](/rest/reference/repos#list-deployments). +| Tecla | Tipo | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} +| `implantação` | `objeto` | The [implantação](/rest/reference/repos#list-deployments). | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.deployment }} -### deployment_status +### implantação_status {% data reusables.webhooks.deployment_status_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `deployments` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de `implantação` -#### Webhook payload object +#### Objeto da carga do webhook -Key | Type | Description -----|------|-------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -`action` |`string` | The action performed. Can be `created`.{% endif %} -`deployment_status` |`object` | The [deployment status](/rest/reference/repos#list-deployment-statuses). -`deployment_status["state"]` |`string` | The new state. Can be `pending`, `success`, `failure`, or `error`. -`deployment_status["target_url"]` |`string` | The optional link added to the status. -`deployment_status["description"]`|`string` | The optional human-readable description added to the status. -`deployment` |`object` | The [deployment](/rest/reference/repos#list-deployments) that this status is associated with. +| Tecla | Tipo | Descrição | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} +| `implantação_status` | `objeto` | O [estado de implantação](/rest/reference/repos#list-deployment-statuses). | +| `deployment_status["state"]` | `string` | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`. | +| `deployment_status["target_url"]` | `string` | O link opcional adicionado ao status. | +| `deployment_status["description"]` | `string` | A descrição opcional legível para pessoas adicionada ao status. | +| `implantação` | `objeto` | A [implantação](/rest/reference/repos#list-deployments) à qual este status está associado. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.deployment_status }} +{% if currentVersion == "free-pro-team@latest" %} +### discussão + +{% data reusables.webhooks.discussions-webhooks-beta %} + +Activity related to a discussion. For more information, see the "[Using the GraphQL API for discussions](/graphql/guides/using-the-graphql-api-for-discussions)." +#### Disponibilidade + +- Webhooks do repositório +- Webhooks da organização +- {% data variables.product.prodname_github_app %}s with the `discussions` permission + +#### Objeto da carga do webhook + +| Tecla | Tipo | Descrição | +| ------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, or `unanswered`. | +{% data reusables.webhooks.discussion_desc %} +{% data reusables.webhooks.repo_desc_graphql %} +{% data reusables.webhooks.org_desc_graphql %} +{% data reusables.webhooks.sender_desc %} + +#### Exemplo de carga de webhook + +{{ webhookPayloadsForCurrentVersion.discussion.created }} + +### discussion_comment + +{% data reusables.webhooks.discussions-webhooks-beta %} + +Activity related to a comment in a discussion. For more information, see "[Using the GraphQL API for discussions](/graphql/guides/using-the-graphql-api-for-discussions)." + +#### Disponibilidade + +- Webhooks do repositório +- Webhooks da organização +- {% data variables.product.prodname_github_app %}s with the `discussions` permission + +#### Objeto da carga do webhook + +| Tecla | Tipo | Descrição | +| ------------ | -------- | ------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser `criado`, `editado` ou `excluído`. | +| `comentário` | `objeto` | The [`discussion comment`](/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) resource. | +{% data reusables.webhooks.discussion_desc %} +{% data reusables.webhooks.repo_desc_graphql %} +{% data reusables.webhooks.org_desc_graphql %} +{% data reusables.webhooks.sender_desc %} + +#### Exemplo de carga de webhook + +{{ webhookPayloadsForCurrentVersion.discussion_comment.created }} +{% endif %} + {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} ### enterprise {% data reusables.webhooks.enterprise_short_desc %} -#### Availability +#### Disponibilidade -- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." +- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)." -#### Webhook payload object +#### Objeto da carga do webhook -Key | Type | Description -----|------|------------- -`action` |`string` | The action performed. Can be `anonymous_access_enabled` or `anonymous_access_disabled`. +| Tecla | Tipo | Descrição | +| ------ | -------- | ------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser `anonymous_access_enabled` ou `anonymous_access_disabled`. | -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }} {% endif %} -### fork +### bifurcação {% data reusables.webhooks.fork_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.fork_properties %} {% data reusables.webhooks.repo_desc %} @@ -373,28 +432,28 @@ Key | Type | Description {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.fork }} ### github_app_authorization -When someone revokes their authorization of a {% data variables.product.prodname_github_app %}, this event occurs. A {% data variables.product.prodname_github_app %} receives this webhook by default and cannot unsubscribe from this event. +Este evento ocorre quando alguém revoga a autorização de um {% data variables.product.prodname_github_app %}. Um {% data variables.product.prodname_github_app %} recebe este webhook por padrão e não pode cancelar a assinatura deste evento. -{% data reusables.webhooks.authorization_event %} For details about user-to-server requests, which require {% data variables.product.prodname_github_app %} authorization, see "[Identifying and authorizing users for {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +{% data reusables.webhooks.authorization_event %} Para obter informações sobre solicitações de usuário para servidor, que exigem autorização do {% data variables.product.prodname_github_app %}, consulte "[Identificando e autorizando usuários para os {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". -#### Availability +#### Disponibilidade - {% data variables.product.prodname_github_app %}s -#### Webhook payload object +#### Objeto da carga do webhook -Key | Type | Description -----|------|------------- -`action` |`string` | The action performed. Can be `revoked`. +| Tecla | Tipo | Descrição | +| ------ | -------- | -------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser `revogada`. | {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }} @@ -402,13 +461,13 @@ Key | Type | Description {% data reusables.webhooks.gollum_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão de ` conteúdo` -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.gollum_properties %} {% data reusables.webhooks.repo_desc %} @@ -416,39 +475,31 @@ Key | Type | Description {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.gollum }} -### installation +### instalação {% data reusables.webhooks.installation_short_desc %} {% note %} -**Note:** This event replaces the deprecated `integration_installation` event. +**Observação:** Você não receberá um webhook para este evento ao excluir mais de três tags de uma só vez. {% endnote %} -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - -**Note:** {% data reusables.pre-release-program.suspend-installation-beta %} For more information, see "[Suspending a {% data variables.product.prodname_github_app %} installation](/apps/managing-github-apps/suspending-a-github-app-installation/)." - -{% endnote %} -{% endif %} - -#### Availability +#### Disponibilidade - {% data variables.product.prodname_github_app %}s -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.installation_properties %} {% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.installation.deleted }} @@ -458,21 +509,21 @@ Key | Type | Description {% note %} -**Note:** This event replaces the deprecated `integration_installation_repositories` event. +`repository` quando ocorre o evento a partir da atividade em um repositório. {% endnote %} -#### Availability +#### Disponibilidade - {% data variables.product.prodname_github_app %}s -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.installation_repositories_properties %} {% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.installation_repositories.added }} @@ -480,177 +531,266 @@ Key | Type | Description {% data reusables.webhooks.issue_comment_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `issues` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão problemas` + -#### Webhook payload object +

Objeto da carga do webhook

-{% data reusables.webhooks.issue_comment_webhook_properties %} -{% data reusables.webhooks.issue_comment_properties %} +

{% data reusables.webhooks.issue_comment_webhook_properties %}

+ +

+

+ +

{% data reusables.webhooks.issue_comment_properties %}

+ +

+

+ +

{% data reusables.webhooks.repo_desc %}

+ +

+

+ +

{% data reusables.webhooks.org_desc %}

+ +

+

+ +

{% data reusables.webhooks.app_desc %}

+ +

+

+ +

{% data reusables.webhooks.sender_desc %}

+ +

Exemplo de carga de webhook

+ +

{{ webhookPayloadsForCurrentVersion.issue_comment.created }}

+ +

Problemas

+ +

{% data reusables.webhooks.issues_short_desc %}

+ +

Disponibilidade

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

Objeto da carga do webhook

+ +

{% data reusables.webhooks.issue_webhook_properties %}

+ +

+

+ +

{% data reusables.webhooks.issue_properties %}

+ +

+

+ +

{% data reusables.webhooks.repo_desc %}

+ +

+

+ +

{% data reusables.webhooks.org_desc %}

+ +

+

+ +

{% data reusables.webhooks.app_desc %}

+ +

+

+ +

{% data reusables.webhooks.sender_desc %}

+ +

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

+ +

{{ webhookPayloadsForCurrentVersion.issues.edited }}

+ +

etiqueta

+ +

{% data reusables.webhooks.label_short_desc %}

+ +

Disponibilidade

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

Objeto da carga do 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 %} +

{% data reusables.webhooks.member_webhook_properties %}

-#### Webhook payload example +

+

-{{ webhookPayloadsForCurrentVersion.member.added }} +

{% data reusables.webhooks.member_properties %}

-### membership +

+

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

{% data reusables.webhooks.repo_desc %}

-#### Availability +

+

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

{% data reusables.webhooks.org_desc %}

-#### Webhook payload object +

+

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

{% data reusables.webhooks.app_desc %}

-#### Webhook payload example +

+

-{{ webhookPayloadsForCurrentVersion.membership.removed }} +

{% data reusables.webhooks.sender_desc %}

-### meta +

Exemplo de carga de webhook

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

{{ webhookPayloadsForCurrentVersion.member.added }}

-#### Availability +

filiação

-- Repository webhooks -- Organization webhooks +

{% data reusables.webhooks.membership_short_desc %}

-#### Webhook payload object +

Disponibilidade

-Key | Type | Description -----|------|------------- -`action` |`string` | The action performed. Can be `deleted`. -`hook_id` |`integer` | The id of the modified webhook. -`hook` |`object` | The modified webhook. This will contain different keys based on the type of webhook it is: repository, organization, business, app, or GitHub Marketplace. +
    +
  • Webhooks da organização
    • +
  • Os {% data variables.product.prodname_github_app %}s com a permissão `membros`
    • +
+ +

Objeto da carga do webhook

+ +

{% data reusables.webhooks.membership_properties %}

+ +

+

+ +

{% data reusables.webhooks.org_desc %}

+ +

+

+ +

{% data reusables.webhooks.app_desc %}

+ +

+

+ +

{% data reusables.webhooks.sender_desc %}

+ +

Exemplo de carga de webhook

+ +

{{ webhookPayloadsForCurrentVersion.membership.removed }}

+ +

meta

+ +

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

+ +

Disponibilidade

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

Objeto da carga do webhook

+ +

+ + + + + + + + + + + +
TeclaTipoDescrição
Ação`

{% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.meta.deleted }} -### milestone +### marco {% data reusables.webhooks.milestone_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão `pull_requests` -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.milestone_properties %} {% data reusables.webhooks.repo_desc %} @@ -658,33 +798,42 @@ Key | Type | Description {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.milestone.created }} -### organization +### organização {% data reusables.webhooks.organization_short_desc %} -#### Availability +#### Disponibilidade {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} -- Organization webhooks only receive the `deleted`, `added`, `removed`, `renamed`, and `invited` events -- {% data variables.product.prodname_github_app %}s with the `members` permission +- Os webhooks do GitHub Enterprise recebem apenas eventos `criados` e `excluídos`. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} +- Os webhooks da organização recebem apenas os eventos `excluídos`, `adicionados`, `removidos`, `renomeado` e `convidados` +- Os {% data variables.product.prodname_github_app %}s com a permissão membros` + -#### Webhook payload object +

Objeto da carga do webhook

-Key | Type | Description -----|------|------------- -`action` |`string` | The action that was performed. Can be one of:{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, or `member_invited`. -`invitation` |`object` | The invitation for the user or email if the action is `member_invited`. -`membership` |`object` | The membership between the user and the organization. Not present when the action is `member_invited`. +

+ + + + + + + + + + + +
TeclaTipoDescrição
Ação`

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

Objeto da carga do webhook

-Key | Type | Description -----|------|------------- -`action` |`string` | The action that was performed. Can be one of `created`, `deleted`, `edited`, `added_to_repository`, or `removed_from_repository`. -`team` |`object` | The team itself. -`changes`|`object` | The changes to the team if the action was `edited`. -`changes[description][from]` |`string` | The previous version of the description if the action was `edited`. -`changes[name][from]` |`string` | The previous version of the name if the action was `edited`. -`changes[privacy][from]` |`string` | The previous version of the team's privacy if the action was `edited`. -`changes[repository][permissions][from][admin]` | `boolean` | The previous version of the team member's `admin` permission on a repository, if the action was `edited`. -`changes[repository][permissions][from][pull]` | `boolean` | The previous version of the team member's `pull` permission on a repository, if the action was `edited`. -`changes[repository][permissions][from][push]` | `boolean` | The previous version of the team member's `push` permission on a repository, if the action was `edited`. -`repository`|`object` | The repository that was added or removed from to the team's purview if the action was `added_to_repository`, `removed_from_repository`, or `edited`. For `edited` actions, `repository` also contains the team's new permission levels for the repository. +

+ + + + + + + + + + + +
TeclaTipoDescrição
Ação`

{% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.team.added_to_repository }} @@ -1255,54 +1411,64 @@ Key | Type | Description {% data reusables.webhooks.team_add_short_desc %} -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `members` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão membros` + -#### Webhook payload object +

Objeto da carga do webhook

-Key | Type | Description -----|------|------------- -`team`|`object` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. +

+ + + + + + + + + + +
TeclaTipoDescrição
equipe`

{% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.team_add }} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -### user +### usuário -When a user is `created` or `deleted`. +Quando um usuário é `criado` ou `excluído`. -#### Availability -- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." +#### Disponibilidade +- Webhooks do GitHub Enterprise. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/)." -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.user.created }} {% endif %} -### watch +### inspecionar {% data reusables.webhooks.watch_short_desc %} -The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. +O ator do evento é o [usuário](/rest/reference/users) que favoritou um repositório, e o repositório do evento é [repositório](/rest/reference/repos) que foi marcado com estrela. -#### Availability +#### Disponibilidade -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `metadata` permission +- Webhooks do repositório +- Webhooks da organização +- Os {% data variables.product.prodname_github_app %}s com a permissão `metadados` -#### Webhook payload object +#### Objeto da carga do webhook {% data reusables.webhooks.watch_properties %} {% data reusables.webhooks.repo_desc %} @@ -1310,20 +1476,20 @@ The event’s actor is the [user](/rest/reference/users) who starred a repositor {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.watch.started }} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### workflow_dispatch -This event occurs when someone triggers a workflow run on GitHub or sends a `POST` request to the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" endpoint. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)." +Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no GitHub ou envia uma solicitação de `POST` para o ponto de extremidade "[Criar um evento de envio de fluxo de trabalho](/rest/reference/actions/#create-a-workflow-dispatch-event)". Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". -#### Availability +#### Disponibilidade -- {% data variables.product.prodname_github_app %}s must have the `contents` permission to receive this webhook. +- Os {% data variables.product.prodname_github_app %}s devem ter a permissão de `conteúdo` para receber este webhook. -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} @@ -1331,22 +1497,21 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### workflow_run -When a {% data variables.product.prodname_actions %} workflow run is requested or completed. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_run)." +Quando uma execução do fluxo de trabalho de {% data variables.product.prodname_actions %} for solicitada ou concluída. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_run)". -#### Availability +#### Disponibilidade -- {% data variables.product.prodname_github_app %}s with the `actions` or `contents` permissions. +- {% data variables.product.prodname_github_app %} com as `ações` ou permissões de `conteúdo`. -#### Webhook payload object +#### Objeto da carga do webhook -Key | Type | Description -----|------|------------- -`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event. +{% data reusables.webhooks.workflow_run_properties %} +{% data reusables.webhooks.workflow_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.workflow_run }} {% endif %} diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index eb352ef1c0..811d211885 100644 --- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -19,7 +19,7 @@ Com {% data variables.product.prodname_discussions %}, a comunidade para o seu p Você não precisa fechar uma discussão como você fecha um problema ou um pull request. -Se um administrador de repositório ou mantenedor do projeto permitir discussões em um repositório, qualquer pessoa que visitar o repositório poderá criar e participar de discussões para o repositório. Os administradores de repositório e mantenedores de projetos podem gerenciar as discussões e categorias de discussão em um repositório e fixar discussões para aumentar a visibilidade da discussão. Os moderadores e colaboradores podem marcar comentários como respostas, travar discussões e converter problemas em discussões. Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". +Se um administrador de repositório ou mantenedor do projeto permitir discussões em um repositório, qualquer pessoa que visitar o repositório poderá criar e participar de discussões para o repositório. Os administradores de repositório e mantenedores de projetos podem gerenciar as discussões e categorias de discussão em um repositório e fixar discussões para aumentar a visibilidade da discussão. Os moderadores e colaboradores podem marcar comentários como respostas, travar discussões e converter problemas em discussões. Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". Para obter mais informações sobre o gerenciamento de discussões para o repositório, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)". diff --git a/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md index 45b4eda27a..1539986e2a 100644 --- a/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -29,7 +29,7 @@ Você pode usar {% data variables.product.prodname_discussions %} para discutir Os problemas são úteis para discutir detalhes específicos de um projeto, como relatórios de erros e melhorias planejadas. Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues)". As pull requests permitem comentar diretamente nas alterações propostas. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)" e "[Comentar em uma pull request](/articles/commenting-on-a-pull-request)". -{% data reusables.organizations.team-discussions-purpose %} Para obter mais informações, consulte "[Sobre discussões de equipe](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +{% data reusables.organizations.team-discussions-purpose %} Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)." ### Seguir diretrizes de contribuição diff --git a/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 8533ad8091..cedf99c4f2 100644 --- a/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -21,7 +21,7 @@ Os contribuidores mais úteis dos últimos 30 dias são destacados no painel de Pessoas com permissões de triagem para um repositório podem ajudar a moderar as discussões de um projeto marcando comentários como respostas, bloqueando discussões que já não são úteis ou prejudicam a comunidade e convertendo os problemas em discussões quando uma ideia ainda está nos primeiros estágios de desenvolvimento. Para obter mais informações, consulte "[Moderação de discussões](/discussions/managing-discussions-for-your-community/moderating-discussions)". -Para obter mais informações sobre os níveis de permissão do repositório e {% data variables.product.prodname_discussions %}, consulte "[Níveis de permissões do repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". +Para obter mais informações sobre os níveis de permissão do repositório e {% data variables.product.prodname_discussions %}, consulte "[Níveis de permissões do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". ### Passo 3: Altere os níveis de permissões para os melhores contribuidores diff --git a/translations/pt-BR/content/discussions/index.md b/translations/pt-BR/content/discussions/index.md index 1af086979a..34212f319d 100644 --- a/translations/pt-BR/content/discussions/index.md +++ b/translations/pt-BR/content/discussions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /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 changelog: - label: 'discussions' + label: 'discussões' product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index bcf4319d25..4dd930ffa6 100644 --- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -12,7 +12,7 @@ versions: {% data reusables.discussions.about-discussions %} Para obter mais informações sobre discussões, consulte[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". -Os proprietários da organização podem escolher as permissões necessárias para criar uma discussão para repositórios pertencentes à organização. Para obter mais informações, consulte "[Gerenciar a criação de discussões para repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization)". +Os proprietários da organização podem escolher as permissões necessárias para criar uma discussão para repositórios pertencentes à organização. Para obter mais informações, consulte "[Gerenciar a criação de discussões para repositórios na sua organização](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)". Como mantenedor de discussões, você pode criar recursos da comunidade para incentivar discussões alinhadas com o objetivo geral do projeto e manter um fórum aberto amigável para os colaboradores. Criar um código de conduta ou diretrizes de contribuição para os colaboradores a seguir ajudará a facilitar um fórum colaborativo e produtivo. Para obter mais informações sobre como criar recursos da comunidade, consulte "[Adicionar um código de conduta ao seu projeto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" e "[Diretrizes de configuração para contribuidores do repositório](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)". diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md index 4ba7023939..6209c5d8d9 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -16,3 +16,7 @@ Os mestres, professores e mentores podem usar o treinamento online Consultores d **Observação:** como um instrutor, você não pode criar contas do {% data variables.product.prodname_dotcom %} para seus alunos. Os estudantes devem criar as próprias contas do {% data variables.product.prodname_dotcom %}. {% endnote %} + +Os professores podem gerenciar um curso sobre desenvolvimento de software com {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} permite distribuir código, fornecer feedback e gerenciar trabalhos do curso usando {% data variables.product.product_name %}. Para obter mais informações, consulte "[Gerenciar cursos com {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)". + +Se você for estudante ou professor acadêmico e sua escola não faz parceria com o {% data variables.product.prodname_dotcom %} como uma escola do {% data variables.product.prodname_campus_program %}, ainda assim é possível solicitar descontos individualmente para usar o {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_dotcom %} para fazer o trabalho de escola](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" ou "[Usar o {% data variables.product.prodname_dotcom %} em sala de aula e em pesquisas](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)". diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md index 6dd8efa3dd..8c531700f1 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -9,4 +9,6 @@ versions: free-pro-team: '*' --- -Aprenda as habilidades de falar em público, escrita técnica, liderança de comunidade e desenvolvimento de software como um Especialista de campus do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Especialistas de campus](https://education.github.com/students/experts)". +Aprenda as habilidades de falar em público, escrita técnica, liderança de comunidade e desenvolvimento de software como um Especialista de campus do {% data variables.product.prodname_dotcom %}. + +Para saber mais sobre programas de treinamento para líderes estudantis e professores, consulte "[especialistas de campus do {% data variables.product.prodname_dotcom %}](https://education.github.com/students/experts)" e "[consultores de campus](https://education.github.com/teachers/advisors)". diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md new file mode 100644 index 0000000000..9e2b30c187 --- /dev/null +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Campus Program +intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes: + +- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments +- Treinamento do professor para domínio do Git e do {% data variables.product.prodname_dotcom %} com nosso programa de consultores de campus +- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners +- Acesso automatizado a recursos premium do {% data variables.product.prodname_education %}, como o {% data variables.product.prodname_student_pack %} + +Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join. + +Para obter mais informações, consulte a página [oficial do {% data variables.product.prodname_campus_program %}](https://education.github.com/schools). + +Se você for estudante ou professor acadêmico e sua escola não faz parceria com o {% data variables.product.prodname_dotcom %} como uma escola do {% data variables.product.prodname_campus_program %}, ainda assim é possível solicitar descontos individualmente para usar o {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_dotcom %} para fazer o trabalho de escola](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" ou "[Usar o {% data variables.product.prodname_dotcom %} em sala de aula e em pesquisas](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)". diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md index 7f8e77e134..578c2d9a59 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -13,7 +13,7 @@ versions: ### Índice {% topic_link_in_list /use-github-at-your-educational-institution %} - {% link_in_list /about-github-education %} + {% link_in_list /about-github-campus-program %} {% link_in_list /about-campus-experts %} {% link_in_list /about-campus-advisors %} {% topic_link_in_list /use-github-for-your-schoolwork %} diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index c7a0f23c5a..eb74647023 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -59,11 +59,11 @@ Para obter mais informações, consulte: ### Status de aluno não qualificado Você não estará qualificado para um {% data variables.product.prodname_student_pack %} se: -- Você está matriculado em um programa de aprendizado informal que não faz parte do [programa de campus do {% data variables.product.prodname_dotcom %}](https://education.github.com/schools) e não está matriculado em um curso superior ou técnico. +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. - You're pursuing a degree which will be terminated in the current academic session. - Tiver menos de 13 anos. -Seu instrutor ainda poderá se candidatar a um desconto {% data variables.product.prodname_education %} para uso em sala de aula. Se você for aluno de uma escola de programação ou de um bootcamp, só estará qualificado para um {% data variables.product.prodname_student_pack %} se a sua instituição de ensino participar do [programa de campus do {% data variables.product.prodname_dotcom %}](https://education.github.com/schools). +Seu instrutor ainda poderá se candidatar a um desconto {% data variables.product.prodname_education %} para uso em sala de aula. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). ### Leia mais diff --git a/translations/pt-BR/content/education/index.md b/translations/pt-BR/content/education/index.md index 6dfce87d3b..f6824010d1 100644 --- a/translations/pt-BR/content/education/index.md +++ b/translations/pt-BR/content/education/index.md @@ -1,7 +1,7 @@ --- title: Documentação do GitHub Education shortTitle: Educação -intro: '{% data variables.product.prodname_education %} ajuda você a ensinar ou aprender desenvolvimento de software com as ferramentas e suporte da plataforma e comunidade de {% data variables.product.company_short %}.' +intro: "{% data variables.product.prodname_education %} ajuda você a ensinar ou aprender desenvolvimento de software com as ferramentas e suporte da plataforma e comunidade de {% data variables.product.company_short %}." introLinks: quickstart: /education/quickstart featuredLinks: @@ -20,7 +20,7 @@ featuredLinks: - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom changelog: - label: 'education' + label: 'educação' layout: product-landing versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 67243163fb..b3ac1dfd7e 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -17,7 +17,7 @@ Quando um aluno aceita uma atividade em grupo, o aluno poderá criar uma nova eq {% data reusables.classroom.about-assignments %} -Você pode decidir quantas equipes uma atividade pode ter e quantos integrantes cada equipe pode ter. Cada equipe que um estudante cria para uma atividade é uma equipe dentro da sua organização em {% data variables.product.product_name %}. A visibilidade da equipe é secreta. Equipes criadas em {% data variables.product.product_name %} não aparecerão em {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Sobre equipes](/github/setting-up-and-managing-organizations-and-teams/about-teams)". +Você pode decidir quantas equipes uma atividade pode ter e quantos integrantes cada equipe pode ter. Cada equipe que um estudante cria para uma atividade é uma equipe dentro da sua organização em {% data variables.product.product_name %}. A visibilidade da equipe é secreta. Equipes criadas em {% data variables.product.product_name %} não aparecerão em {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." Para uma demonstração de vídeo da criação de uma atividade de grupo, consulte "[Fundamentos de configuração de {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)". 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 6e153a82c5..6c65eb039b 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 @@ -20,7 +20,7 @@ redirect_from: Depois de criar uma sala de aula, {% data variables.product.prodname_classroom %} solicitará que você convide assistentes de ensino (ETI) e administradores para a sala de aula. Cada sala de aula pode ter um ou mais administradores. Os administradores podem ser professores, TAs ou qualquer outro administrador do curso o qual que você gostaria que tivesse controle das suas salas de aula em {% data variables.product.prodname_classroom %}. -Convide TAs e administradores para a sua sala de aula, convidando as contas de usuário em {% data variables.product.product_name %} para a sua organização como proprietários e compartilhando a URL da sua sala de aula. Os proprietários da organização podem administrar qualquer sala de aula da organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)" e "[Convidar usuários a participar da sua organização](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)". +Convide TAs e administradores para a sua sala de aula, convidando as contas de usuário em {% data variables.product.product_name %} para a sua organização como proprietários e compartilhando a URL da sua sala de aula. Os proprietários da organização podem administrar qualquer sala de aula da organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)" e "[Convidar usuários a participar da sua organização](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)". Ao terminar de usar uma sala de aula, você pode arquivar a sala de aula e consultar a sala de aula, lista, e recomendações posteriormente, ou você pode excluir a sala de aula se não precisar mais dela. @@ -34,7 +34,7 @@ A primeira vez que você compartilha a URL de uma atividade com um estudante, o ### Pré-requisitos -Você precisa ter uma conta de organização em {% data variables.product.product_name %} para gerenciar as salas de aula em {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.company_short %}](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" e "[Criar uma nova organização do zero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". +Você precisa ter uma conta de organização em {% data variables.product.product_name %} para gerenciar as salas de aula em {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.company_short %}](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" e "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". Você deve autorizar o aplicativo OAuth {% data variables.product.prodname_classroom %} para sua organização gerenciar salas de aula para sua conta da organização. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". 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 9f441bd405..f9ff6065be 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,144 @@ --- 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.' +intro: 'Você pode proteger branches importantes definindo regras de proteção de branch, que definem se os colaboradores podem excluir ou forçar push para o branch e definem os requisitos para todos os pushes para o branch, tais como verificações de status de passagem ou um histórico linear de commits.' 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: '*' +topics: + - repositories --- -### Sobre branches protegidos +### Sobre as regras de proteção do branch -{% data reusables.pull_requests.about-protected-branches %} Você pode optar por aplicar restrições sobre como um pull request é mesclado no seu repositório. +É possível aplicar certos fluxos de trabalho ou requisitos antes que um colaborador possa fazer push de alterações em um branch no repositório, incluindo o merge de um pull request no branch, criando uma regra de proteção de branch. -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. +Por padrão, cada regra de proteção de branch desabilita push forçado para os branches correspondentes e impede que os branches correspondentes sejam excluídos. Você pode, opcionalmente, desabilitar essas restrições e habilitar configurações adicionais de proteção de branches. -{% data reusables.repositories.branch-rules-example %} Para obter mais informações, consulte "[Configurar branches protegidos](/articles/configuring-protected-branches/)." +Por padrão, as restrições de uma regra de proteção de branch não se aplicam a pessoas com permissões de administrador para o repositório. Opcionalmente, você também pode escolher incluir administradores. + +{% data reusables.repositories.branch-rules-example %} Para obter mais informações sobre os padrões de nomes do branch, consulte "[Gerenciar uma regra de proteção de branch](/github/administering-a-repository/managing-a-branch-protection-rule)". {% data reusables.pull_requests.you-can-auto-merge %} -### Priorização de regras de branches protegidos +### Sobre as configurações de proteção do branch -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. +Para cada regra de proteção do branch, você pode escolher habilitar ou desabilitar as seguintes configurações. +- [Exigir revisões de pull request antes do merge](#require-pull-request-reviews-before-merging) +- [Exigir verificações de status antes do merge](#require-status-checks-before-merging) +- [Exigir commits assinados](#require-signed-commits) +- [Exigir histórico linear](#require-linear-history) +- [Incluir administradores](#include-administrators) +- [Restringir quem pode fazer push para branches correspondentes](#restrict-who-can-push-to-matching-branches) +- [Permitir push forçado](#allow-force-pushes) +- [Permitir exclusões](#allow-deletions) -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. +#### Exigir revisões de pull request antes do merge -### Configurações de proteção de branch +{% data reusables.pull_requests.required-reviews-for-prs-summary %} -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)". +Se você habilitar as revisões necessárias, os colaboradores só podem fazer push das alterações em um branch protegido por meio de um pull request aprovado pelo número necessário de revisores com permissões de gravação. -### Leia mais +Se uma pessoa com permissões de administrador escolher a opção **Solicitar alterações** em uma revisão, essa pessoa deverá aprovar o pull request antes que o merge possa ser efetuado. Se um revisor que solicita alterações em um pull request não estiver disponível, qualquer pessoa com permissões de gravação no repositório poderá ignorar a revisão de bloqueio. -- "[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)" +{% data reusables.repositories.review-policy-overlapping-commits %} + +Se um colaborador tentar fazer merge de um pull request com revisões pendentes ou rejeitadas no branch protegido, o colaborador receberá uma mensagem de erro. + +```shell +remote: error: GH006: Protected branch update failed for refs/heads/main. +remote: error: Changes have been requested. +``` + +Opcionalmente, você pode escolher ignorar as aprovações de pull request obsoletas quando commits são enviados por push. Se alguém fizer push de um commit que modifica código para um pull request aprovado, a aprovação será ignorada e o pull request não poderá ser mesclado. Isso não se aplica se o colaborador fizer push de commits que não modificam código, como mesclar o branch de base no branch do pull request. Para obter mais informações sobre branch base, consulte "[Sobre pull requests](/articles/about-pull-requests)". + +Opcionalmente, você pode restringir a capacidade de ignorar comentários de pull request para pessoas ou equipes específicas. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/articles/dismissing-a-pull-request-review)". + +Opcionalmente, você pode optar por exigir análises dos proprietários do código. Se você o fizer, qualquer pull request que afeta código com o proprietário do código deverá ser aprovado pelo proprietário desse código antes que o pull request possa ser mesclada no branch protegido. + +#### Exigir verificações de status antes do merge + +As verificações de status obrigatórias garantem que todos os testes de CI sejam aprovados antes que os colaboradores possam fazer alterações em um branch protegido. Para obter mais informações, consulte "[Configurar branches protegidos](/articles/configuring-protected-branches/)" e "[Habilitar verificações de status obrigatórias](/articles/enabling-required-status-checks)". Para obter mais informações, consulte "[Sobre verificações de status](/github/collaborating-with-issues-and-pull-requests/about-status-checks)". + +Antes de habilitar as verificações de status necessárias, é necessário configurar o repositório para usar a API de status. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#statuses)" na documentação do REST. + +Depois de habilitar a verificação de status obrigatória, todas as verificações de status necessárias deverão passar para que os colaboradores possam fazer merge das alterações no branch protegido. Depois que todas as verificações de status necessárias passarem, quaisquer commits devem ser enviados por push para outro branch e, em seguida, mesclados ou enviados por push diretamente para o branch protegido. + +{% note %} + +**Observação:** Qualquer pessoa ou integração com permissões de gravação em um repositório pode configurar o estado de qualquer verificação de status no repositório. O {% data variables.product.company_short %} não analisa se o autor de uma verificação está autorizado a criar uma verificação com um determinado nome ou modificar um status existente. Antes de realizar o merge de uma pull request, você deve verificar se o autor de cada status, listado na caixa de merge, é esperado. + +{% endnote %} + +Você pode configurar as verificações de status obrigatórias como "flexível" ou "rígida". O tipo de verificação de status obrigatória que você escolher determinará se o branch precisará ser atualizado com o branch base antes do merge. + +| Tipo de verificação de status obrigatória | Configuração | Requisitos de merge | Considerações | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Rígida** | A caixa de seleção **Exigir a atualização dos branches antes de fazer merge** fica marcada. | O branch **precisa** ser atualizado no branch base antes do merge. | Este é o comportamento padrão para verificações de status obrigatórias. Podem ser necessárias mais compilações, já que você precisará atualizar o branch head depois que outros colaboradores fizerem merge de pull requests no branch base protegido. | +| **Flexível** | A caixa de seleção **Exigir a atualização dos branches antes de fazer merge** **não** fica marcada. | O branch **não precisa** ser atualizado no branch base antes do merge. | Serão necessárias menos compilações, já que você não precisará atualizar o branch head depois que outros colaboradores fizerem merge de pull requests. As verificações de status poderão falhar depois que você fizer merge do branch, caso haja alterações incompatíveis com o branch base. | +| **Desabilitada** | A caixa de seleção **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge) **não** fica marcada. | O branch não tem restrições de merge. | Se as verificações de status obrigatórias não estiverem habilitadas, os colaboradores poderão fazer merge do branch a qualquer momento, estando ou não atualizados com o branch base. Isso aumenta a possibilidade de alterações incompatíveis. | + +Para obter informações sobre a solução de problemas, consulte "[Solucionar problemas para as verificações de status obrigatórias](/github/administering-a-repository/troubleshooting-required-status-checks)". + +#### Exigir commits assinados + +Ao habilitar a assinatura de commit obrigatória em um branch, os contribuidores {% if currentVersion == "free-pro-team@latest" %}e bots{% endif %} só podem fazer push de commits que foram assinados e verificados no branch. Para obter mais informações, consulte "[Sobre verificação de assinatura commit](/articles/about-commit-signature-verification)". + +{% note %} + +**Observação:** Se um colaborador fizer push de um commit não assinado para um branch que exige assinaturas de commit, o colaborador deverá fazer rebase do commit para incluir uma assinatura verificada e, em seguida, fazer push forçado no commit reescrito para o branch. + +{% endnote %} + +Você sempre pode fazer push de commits locais para o branch se os commits forem assinados e verificados. {% if currentVersion == "free-pro-team@latest" %}Você também pode fazer merge de commits assinados e verificados no branch usando um pull request em {% data variables.product.product_name %}. No entanto, você não pode realizar a combinação por squash e fazer o merge de um pull request no branch em {% data variables.product.product_name %} a menos que você seja o autor do pull request.{% else %}No entanto, você não pode fazer merge de pull requests no branch em {% data variables.product.product_name %}.{% endif %} Você pode {% if currentVersion == "free-pro-team@latest" %}fazer combinação por squash e {% endif %} fazer merge de pull requests localmente. Para obter mais informações, consulte "[Fazer checkout de pull requests localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)". + +{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações sobre métodos de merge, consulte "[Sobre métodos de merge em {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github){% endif %} + +#### Exigir histórico linear + +Aplicar o histórico linear de commit impede que os colaboradores façam push de commits de merge no branch. Isto significa que quaisquer pull requests mesclada no branch protegido devem usar um merge squash ou um merge rebase. Um histórico de commit estritamente linear pode ajudar as equipes a reverter alterações mais facilmente. Para obter mais informações sobre métodos de merge, consulte "[Sobre merges de pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)". + +Antes de exigir um histórico de commit linear, seu repositório deve permitir merge squash ou merge rebase. Para obter mais informações, consulte "[Configurando merges da pull request](/github/administering-a-repository/configuring-pull-request-merges)". + +#### Incluir administradores + +Por padrão, as regras de branch protegidos não se aplicam a pessoas com permissões de administrador em um repositório. Você pode habilitar essa configuração para incluir administradores em suas regras de branch protegido. + +#### Restringir quem pode fazer push para branches correspondentes + +{% if currentVersion == "free-pro-team@latest" %} +Você pode habilitar restrições de branch se o seu repositório pertencer a uma organização que usa +{% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. +{% endif %} + +Ao habilitar as restrições de branches, apenas usuários, equipes ou aplicativos com permissão podem fazer push para o branch protegido. Você pode visualizar e editar usuários, equipes ou aplicativos com acesso de push a um branch protegido nas configurações do branch protegido. + +Você só pode dar acesso de push a um branch protegido a usuários, equipes ou {% data variables.product.prodname_github_apps %} instalados com acesso de gravação a um repositório. As pessoas e os aplicativos com permissões de administrador em um repositório sempre conseguem fazer push em um branch protegido. + +#### Permitir push forçado + +Por padrão, os blocks do {% data variables.product.product_name %} fazem push forçado em todos os branches protegidos. Quando você habilitar push forçado em um branch protegido, qualquer pessoa com, pelo menos, permissões de gravação no repositório pode forçar o push ao branch, incluindo aqueles com permissões de administrador. + +Habilitar push forçado não irá substituir quaisquer outras regras de proteção de branch. Por exemplo, se um branch exigir um histórico de commit linear, você não poderá forçar commits a mesclar commits para esse branch. + +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Você não pode habilitar push forçados para um branch protegido se um administrador do site bloqueou o push forçado para todos os branches no seu repositório. Para obter mais informações, consulte "[Bloqueando push forçado para repositórios de propriedade de uma conta de usuário ou organização](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." + +Se um administrador do site bloquear pushes forçados apenas para o branch padrão, você ainda pode habilitar pushes forçados para qualquer outro branch protegido.{% endif %} + +#### Permitir exclusões + +Por padrão, você não pode excluir um branch protegido. Ao habilitar a exclusão de um branch protegido, qualquer pessoa com permissão de gravação no repositório pode excluir o branch. diff --git a/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index 7f0650f4ad..748bbc4ee5 100644 --- a/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -26,7 +26,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% note %} -**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. Para obter mais informações, consulte "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" ou {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account). {% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Aplicar políticas de {% data variables.product.prodname_actions %} para a sua empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -47,7 +47,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% note %} -**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. Para obter mais informações, consulte "[Habilitar ou desabilitar {% data variables.product.prodname_actions %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" ou {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account). {% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} para a sua empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". +**Nota:** Talvez você não seja capaz de gerenciar essas configurações se sua organização tem uma política de substituição ou é gerenciada por uma conta corporativa que tem uma política de substituição. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index 0690772790..c6f3c170c0 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -11,7 +11,11 @@ topics: - repositories --- -Se você permitir um merge automático para pull requests no seu repositório, as pessoas podem configurar os pull requests individuais no repositório para fazer merge automaticamente quando todos os requisitos de merge forem atendidos. Para obter mais informações, consulte "[Fazer merge automático de um pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". +### Sobre o merge automático + +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." + +### Managing auto-merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 6a629e0f45..5bdea331b6 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 @@ -65,7 +65,13 @@ Você pode escolher se 7. Opcionalmente, para incluir arquivos binários, como programas compilados em sua versão, arraste e solte ou selecione arquivos manualmente na caixa de binários. ![Fornecer um DMG com a versão](/assets/images/help/releases/releases_adding_binary.gif) -8. Para notificar os usuários que a versão não está pronta para produção e pode ser instável, selecione **This is a pre-release** (Esta é uma versão prévia). ![Caixa de seleção para marcar uma versão como pré-versão](/assets/images/help/releases/prerelease_checkbox.png) +8. Para notificar os usuários que a versão não está pronta para produção e pode ser instável, selecione **This is a pre-release** (Esta é uma versão prévia). ![Caixa de seleção para marcar uma versão como pré-versão](/assets/images/help/releases/prerelease_checkbox.png) + + {%- if currentVersion == "free-pro-team@latest" %} + +1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) + + {%- endif %} 9. Se estiver pronto para tornar pública a sua versão, clique em **Publish release** (Publicar versão). Para trabalhar na versão posteriormente, clique em **Save draft** (Salvar rascunho). ![Botões Publish release (Publicar versão) e Draft release (Rascunhar versão)](/assets/images/help/releases/release_buttons.png) 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 b9c46b6ef7..a310c99a08 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 @@ -106,4 +106,4 @@ Os proprietários da organização e os administradores do repositório só pode ### Leia mais - "[Sobre proteger seu repositório](/github/administering-a-repository/about-securing-your-repository)" -- "[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)" +- "[Gerenciando configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md index ed13fd8b83..10d83abd84 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -16,7 +16,7 @@ Para cada repositório que você administra no {% data variables.product.prodnam Esta visão geral pode ajudá-lo a auditar o acesso ao seu repositório, incluir ou excluir funcionários ou colaboradores, e responder efetivamente aos incidentes de segurança. -Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" e "[Níveis de permissão de repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". +Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" e "[Níveis de permissão de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". ![Acessar visão geral do gerenciamento ](/assets/images/help/repository/manage-access-overview.png) @@ -53,4 +53,4 @@ Para obter mais informações, consulte "[Níveis de permissão para um reposit ### Leia mais - "[Definir a visibilidade de um repositório](/github/administering-a-repository/setting-repository-visibility)" -- "[Configurando permissões de base para uma organização](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" +- "[Configurando permissões de base para uma organização](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index 8c37879409..9ebd1a7a87 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -13,7 +13,7 @@ topics: - repositories --- -Um proprietário da organização deve permitir bifurcações de repositórios privado{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} e internos{% endif %} no nível da organização antes de permitir ou não permitir bifurcações em um repositório específico. Para obter mais informações, consulte "[Gerenciando a política de bifurcação para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)". +Um proprietário da organização deve permitir bifurcações de repositórios privado{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %} e internos{% endif %} no nível da organização antes de permitir ou não permitir bifurcações em um repositório específico. Para obter mais informações, consulte "[Gerenciando a política de bifurcação para sua organização](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)". {% data reusables.organizations.internal-repos-enterprise %} 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 index 6aeb5439d9..395d85fc69 100644 --- 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 @@ -4,7 +4,7 @@ intro: É possível alterar o nome de um branch em um repositório. permissions: As pessoas com permissões de gravação em um repositório podem renomear um branch no repositório. As pessoas com permissões de administrador podem renomear o branch padrão. versions: free-pro-team: '*' - enterprise-server: '>=3.1' + enterprise-server: '>=3.2' topics: - repositories --- @@ -13,7 +13,9 @@ topics: Você pode renomear um branch em um repositório em {% data variables.product.product_location %}. Para obter mais informações sobre os branches, consulte "[Sobre os branches](/github/collaborating-with-issues-and-pull-requests/about-branches)". -Se você renomear um branch, {% data variables.product.prodname_dotcom %} irá redirecionar automaticamente links em {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} que contêm o nome do branch antigo para o link equivalente no branch renomeado. {% data variables.product.prodname_dotcom %} também atualizará as políticas de proteção do branch, bem como o branch de base para pull requests abertos e versões de rascunho. +When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. + +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. ### Renomear um branch diff --git a/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md index b5b49212a4..45fb23b485 100644 --- a/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/renaming-a-repository.md @@ -18,7 +18,7 @@ Quando você renomear um repositório, todas as informações existentes, com ex * Estrelas * Seguidores -Para obter mais informações sobre sites de projeto, consulte "[Sobre {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)". +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Além do redirecionamento do tráfego da web, todas as operações `git clone`, `git fetch` ou `git push` direcionadas ao local antigo continuarão a funcionar como se tivessem sido criadas no novo local. No entanto, para reduzir a confusão, recomendamos que a atualização de quaisquer clones locais existentes apontem para a nova URL do repositório. Você pode fazer isso usando o `git remote` na linha de comando: @@ -30,7 +30,7 @@ For more information, see "[Managing remote repositories](/github/getting-starte {% if currentVersion == "free-pro-team@latest" %} -Se você planeja renomear um repositório que tenha um site do {% data variables.product.prodname_pages %} , recomendamos usar um domínio personalizado para o seu site. Isso garante que a URL do site não seja impactada pela renomeação do repositório. Para obter mais informações, consulte "[Sobre um domínio personalizado e o site {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-custom-domains-and-github-pages)". +Se você planeja renomear um repositório que tenha um site do {% data variables.product.prodname_pages %} , recomendamos usar um domínio personalizado para o seu site. Isso garante que a URL do site não seja impactada pela renomeação do repositório. Para obter mais informações, consulte "[Sobre um domínio personalizado e o site {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)". {% endif %} 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 7fd8db9d0c..161b3a49c4 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 @@ -1,6 +1,6 @@ --- -title: Setting repository visibility -intro: You can choose who can view your repository. +title: Definir a visibilidade de um repositório +intro: Você pode escolher quem pode visualizar seu repositório. redirect_from: - /articles/making-a-private-repository-public/ - /articles/making-a-public-repository-private/ @@ -10,106 +10,104 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - repositories --- -### About repository visibility changes +### Sobre alterações de visibilidade do repositório -Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)." +Os proprietários da organização podem restringir a capacidade de alterar a visibilidade do repositório apenas para os proprietários da organização. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." -We recommend reviewing the following caveats before you change the visibility of a repository. +Recomendamos revisar as seguintes advertências antes de alterar a visibilidade de um repositório. -#### Making a repository private +#### Tornar um repositório privado {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %} -* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} -* If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} -* Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% 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 %} +* O {% data variables.product.product_name %} destacará bifurcações públicas do repositório público e as colocará em uma nova rede. As bifurcações públicas não se convertem em privadas.{% endif %} +* 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 %} não incluirá mais o repositório no {% data variables.product.prodname_archive %}. Para obter mais informações, consulte "[Sobre arquivar 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 currentVersion == "free-pro-team@latest" %} +* As funcionalidades de {% data variables.product.prodname_GH_advanced_security %} como, por exemplo, {% data variables.product.prodname_code_scanning %} irá parar de funcionar a menos que o repositório pertença a uma organização que faz parte de uma empresa com uma licença para {% data variables.product.prodname_advanced_security %} e estações sobressalentes suficientes. {% 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" %} -#### Making a repository internal +#### Tornar um repositório interno {% note %} -**Note:** {% data reusables.gated-features.internal-repos %} +**Observação:** {% data reusables.gated-features.internal-repos %} {% endnote %} -* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" +* Todas as bifurcações do repositório permanecerão na rede do repositório e a {% data variables.product.product_name %} manterá a relação entre o repositório raiz e a bifurcação. Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou muda de visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -#### Making a repository public +#### Tornar um repositório público -* {% 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)." -* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. +* 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)." +* O repositório automaticamente receberá acesso aos recursos de {% data variables.product.prodname_GH_advanced_security %}. -For information about improving repository security, see "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)."{% endif %} +Para obter informações sobre como melhorar a segurança do repositório, consulte "[Sobre como proteger o seu repositório](/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" %} -### Changing a repository's visibility +### Alterar a visibilidade de um repositório {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**. - ![Change visibility button](/assets/images/help/repository/repo-change-vis.png) -4. Select a visibility. - ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png) -5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of. -6. Click **I understand, change repository visibility**. - ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png) - +3. Em "Danger Zone" (Zona de Perigo), à direita de "Alterar a visibilidade do repositório", clique **Alterar visibilidade**. ![Botão de alteração de visibilidade](/assets/images/help/repository/repo-change-vis.png) +4. Selecione uma visibilidade. +{% if currentVersion == "free-pro-team@latest" %} + ![Caixa de diálogo de opções para visibilidade do repositório](/assets/images/help/repository/repo-change-select.png){% else %} +![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %} +5. Para verificar se você está alterando a visibilidade do repositório correto, digite o nome do repositório que deseja alterar a visibilidade. +6. Clique em **Eu entendi, altere a visibilidade do repositório**. +{% if currentVersion == "free-pro-team@latest" %} + ![Confirmar alteração do botão de visibilidade do repositório](/assets/images/help/repository/repo-change-confirm.png){% else %} +![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %} {% endif %} {% if currentVersion ver_lt "enterprise-server@2.22" %} -### Making a repository private +### Tornar um repositório privado {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Under "Danger Zone", next to "Make this repository private", click **Make private**. - ![Make private button](/assets/images/help/repository/repo-makeprivate.png) -4. Read the warnings about making a repository private. - ![Warnings popup](/assets/images/help/repository/repo-privateconfirm.png) -5. Type the name of the repository that you want to make private, for example `accountname/reponame`. -6. Click **I understand, make this repository private**. +3. Em "Zona de perigo", perto de "Tornar este repositório privado", clique em **Tornar privado**. ![Botão Make private (Tornar privado)](/assets/images/help/repository/repo-makeprivate.png) +4. Leia os avisos sobre tornar um repositório privado. ![Pop-up de avisos](/assets/images/help/repository/repo-privateconfirm.png) +5. Insira o nome do repositório que deseja tornar privado, como `accountname/reponame`. +6. Clique em **Eu compreendo, tornar este repositório privado**. -### Making a repository public +### Tornar um repositório público {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Under "Danger Zone", next to "Make this repository public", click **Make public**. - ![Make public button](/assets/images/help/repository/repo-makepublic.png) -4. Read the warnings about making a repository public. - ![Pop-up with information about making a private repository public](/assets/images/help/repository/repo-publicconfirm.png) -5. Type the name of the repository that you want to make public, for example `accountname/reponame`. -6. Click **I understand, make this repository public**. +3. Em "Zona de perigo, perto de "Tornar este repositório público", clique em **Tornar público**. ![Botão Make public (Tornar público)](/assets/images/help/repository/repo-makepublic.png) +4. Leia os avisos sobre tornar um repositório público. ![Pop-up com informações sobre converter repositório privado em público](/assets/images/help/repository/repo-publicconfirm.png) +5. Insira o nome do repositório que deseja tornar público, como `accountname/reponame`. +6. Clique em **Eu compreendo, tornar este repositório público**. {% if currentVersion ver_gt "enterprise-server@2.19" %} -### Making a repository internal +### Tornar um repositório interno {% data reusables.organizations.internal-repos-enterprise %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Under "Danger Zone", next to "Make this repository internal", click **Make internal**. - ![Make internal button](/assets/images/help/repository/repo-makeinternal.png) -4. Read the warnings about making a repository internal. - ![Warnings popup](/assets/images/help/repository/repo-internalconfirm.png) -5. Type the name of the repository that you want to make internal, for example `accountname/reponame`. -6. Click **I understand, make this repository internal**. +3. Em "Zona de perigo", perto de "Tornar este repositório interno", clique em **Tornar interno**. ![Botão Make internal (Tornar interno)](/assets/images/help/repository/repo-makeinternal.png) +4. Leia os avisos sobre tornar um repositório interno. ![Pop-up de avisos](/assets/images/help/repository/repo-internalconfirm.png) +5. Insira o nome do repositório que deseja tornar interno, como `accountname/reponame`. +6. Clique em **Eu compreendo, tornar este repositório interno**. {% endif %} {% endif %} -### Further reading -- "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" +### Leia mais +- "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md index c2ffc2296d..2d40483c4a 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-to-github.md @@ -61,3 +61,22 @@ Você pode acessar repositórios no {% data variables.product.product_name %} pe * Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de SSH, embora os firewalls e proxys possam se recusar a permitir conexões de SSH. Usar o SSH exige que você gere um par de chave pública/privada de SSH no seu computador local e adicione a chave pública à sua conta de {% data variables.product.product_name %}. Sempre que usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você digite a senha da sua chave SSH, a menos que você [tenha armazenado a chave](/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 obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao 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 usar um token de acesso pessoal ou chave SSH para acessar recursos pertencentes a uma organização que usa o logon único do SAML, você também deve autorizar o token pessoal ou chave SSH. Para obter mais informações consulte "[Autorizar um token de acesso pessoal para usar com logon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para uso com o logon único SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on).{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + + + +### {% data variables.product.company_short %}'s token formats + +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. + +| Token type | Prefix | Mais informações | +|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Token de acesso de pessoal | `ghp_` | "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | + + +{% endif %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index cd4198c82a..4ee13ceca7 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -51,5 +51,5 @@ Após o proprietário de uma empresa ou organização habilitar ou aplicar o SSO ### Leia mais -{% if currentVersion == "free-pro-team@latest" %}- "[Sobre identidade e gerenciamento de acesso com logon único SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} {% if currentVersion == "github-ae@latest" %}- "[Sobre identidade e gerenciamento de acesso para a sua empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md index 03ec845613..eeb1b9380c 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/pt-BR/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -36,8 +36,15 @@ Os tokens de acesso pessoal (PATs) são uma alternativa para o uso de senhas par ![Selecionar escopos do token](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} 7. Clique em **Generate token** (Gerar token). ![Botão Generate token (Gerar token)](/assets/images/help/settings/generate_token.png) -8. Clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar o token na sua área de transferência. Por motivos de segurança, depois que você sair da página, você não poderá ver o token novamente.{% 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 %} +8. Clique em +{% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again. + {% if currentVersion == "free-pro-team@latest" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) + {% endif %} {% warning %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/pt-BR/content/github/authenticating-to-github/creating-a-strong-password.md index e3c30f5305..df7ad2700d 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/creating-a-strong-password.md +++ b/translations/pt-BR/content/github/authenticating-to-github/creating-a-strong-password.md @@ -20,7 +20,7 @@ Para manter sua conta protegida, é recomendável seguir estas práticas recomen - Use um gerenciador de senhas, como [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/) para gerar uma senha de pelo menos 15 caracteres. - Gere uma senha exclusiva para o {% data variables.product.product_name %}. Se você usar sua senha do {% data variables.product.product_name %} em outro lugar e esse serviço estiver comprometido, os invasores ou outros atores mal-intencionados podem usar essa informação para acessar sua conta do {% data variables.product.product_name %}. - Configure a autenticação de dois fatores para sua conta pessoal. Para obter mais informações, consulte "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)". -- Nunca compartilhe sua senha, mesmo com um possível colaborador. Cada pessoa deve usar a própria conta pessoal no {% data variables.product.product_name %}. Para obter mais informações sobre maneiras de colaborar, consulte: "[Convidar colaboradores para um repositório pessoal](/articles/inviting-collaborators-to-a-personal-repository)", "[Sobre modelos de desenvolvimento colaborativo](/articles/about-collaborative-development-models/)" ou "[Colaborar com grupos em organizações](/articles/collaborating-with-groups-in-organizations/)". +- Nunca compartilhe sua senha, mesmo com um possível colaborador. Cada pessoa deve usar a própria conta pessoal no {% data variables.product.product_name %}. Para obter mais informações sobre maneiras de colaborar, consulte: "[Convidar colaboradores para um repositório pessoal](/articles/inviting-collaborators-to-a-personal-repository)", "[Sobre modelos de desenvolvimento colaborativo](/articles/about-collaborative-development-models/)" ou "[Colaborar com grupos em organizações](/organizations/collaborating-with-groups-in-organizations/)". {% data reusables.repositories.blocked-passwords %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/error-permission-denied-publickey.md b/translations/pt-BR/content/github/authenticating-to-github/error-permission-denied-publickey.md index 6057153d6b..d348197c18 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/error-permission-denied-publickey.md +++ b/translations/pt-BR/content/github/authenticating-to-github/error-permission-denied-publickey.md @@ -1,58 +1,60 @@ --- -title: 'Error: Permission denied (publickey)' -intro: 'A "Permission denied" error means that the server rejected your connection. There could be several reasons why, and the most common examples are explained below.' +title: 'Erro: permissão negada (publickey)' +intro: 'Uma mensagem de erro "Permission denied" (permissão negada) indica que o servidor rejeitou a sua conexão. Existem diferentes razões para isso acontecer. Os exemplos mais comuns estão descritos abaixo.' redirect_from: - /articles/error-permission-denied-publickey versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - ssh --- -### Should the `sudo` command be used with Git? +### O comando `sudo` deve ser usado com o Git? -You should not be using the `sudo` command with Git. If you have a *very good reason* you must use `sudo`, then ensure you are using it with every command (it's probably just better to use `su` to get a shell as root at that point). If you [generate SSH keys](/articles/generating-an-ssh-key) without `sudo` and then try to use a command like `sudo git push`, you won't be using the same keys that you generated. +Você não deve usar o comando `sudo` com o Git. Caso você tenha uma *razão muito boa* para usar `sudo`, assegure-se de usá-lo com todos os comandos (talvez seja melhor usar `su` para obter um shell como root nesse ponto). Se você [gerar chaves SSH](/articles/generating-an-ssh-key) sem `sudo` e depois tentar usar um comando como `sudo git push`, você não estará usando as mesmas chaves que gerou. -### Check that you are connecting to the correct server +### Verifique se está conectado ao servidor correto -Typing is hard, we all know it. Pay attention to what you type; you won't be able to connect to "githib.com" or "guthub.com". In some cases, a corporate network may cause issues resolving the DNS record as well. +Sabemos que digitar é difícil. Preste atenção ao que digita; você não conseguirá se conectar a "githib.com" ou "guthub.com". Em alguns casos, uma rede corporativa também pode causar problemas ao resolver o registro DNS. -To make sure you are connecting to the right domain, you can enter the following command: +Insira o segunte comando para confirmar que está conectado ao domínio correto: ```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. +> OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 +> debug1: Lendo dados de configuração /Users/you/.ssh/config +> debug1: Lendo dados de configuração /etc/ssh_config +> debug1: Solicitando opções para * +> debug1: Conectando a {% data variables.command_line.codeblock %} [IP ADDRESS] port 22. ``` -The connection should be made on port 22{% if currentVersion == "free-pro-team@latest" %}, unless you're overriding settings to use [SSH over HTTPS](/articles/using-ssh-over-the-https-port){% endif %}. +A conexão deve ser feita na porta 22{% if currentVersion == "free-pro-team@latest" %}, a menos que você esteja substituindo configurações para usar [SSH em vez de HTTPS](/articles/using-ssh-over-the-https-port){% endif %}. -### Always use the "git" user +### Sempre utilize o usuário "git" -All connections, including those for remote URLs, must be made as the "git" user. If you try to connect with your {% data variables.product.product_name %} username, it will fail: +Todas as conexões devem ser feitas como usuário "git", inclusive aquelas para URLs remotas. Se você tentar se conectar com o seu {% data variables.product.product_name %} nome de usuário, ocorrerá um erro: ```shell $ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %} -> Permission denied (publickey). +> Permissão negada (publickey). ``` -If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/articles/changing-a-remote-s-url/). +Se houver uma falha na conexão ao usar um URL remoto com seu nome de usuário {% data variables.product.product_name %}, você pode [alterar a URL remota para o usuário "git"](/github/getting-started-with-github/managing-remote-repositories). -You should verify your connection by typing: +Verifique sua conexão digitando: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! You've successfully authenticated... +> Olá username! Você conseguiu se autenticar... ``` -### Make sure you have a key that is being used +### Garanta que você tem uma chave que está em uso {% mac %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +2. Verifique se você tem uma chave privada gerada e carregada em SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}Se você estiver usnado OpenSSH 6.7 ou anterior: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" @@ -61,7 +63,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) ``` - If you're using OpenSSH 6.8 or newer: + Se estiver usando OpenSSH 6.8 ou posterior: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" @@ -87,13 +89,13 @@ $ ssh -T git@{% data variables.command_line.codeblock %} 1. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +2. Verifique se você tem uma chave privada gerada e carregada em 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) ``` - If you're using OpenSSH 6.8 or newer: + Se estiver usando OpenSSH 6.8 ou posterior: ```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) @@ -109,7 +111,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} {% linux %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +2. Verifique se você tem uma chave privada gerada e carregada em 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)" @@ -118,7 +120,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) ``` - If you're using OpenSSH 6.8 or newer: + Se estiver usando OpenSSH 6.8 ou posterior: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" @@ -131,69 +133,92 @@ $ ssh -T git@{% data variables.command_line.codeblock %} $ 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 %}. +O comando `ssh-add` *deve* imprimir uma longa sequência se números e letras. Caso isso não aconteça, você deverá gerar uma nova chave SSH e associá-la a {% 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. +**Dica**: Na maioria dos sistemas as chaves privada padrão (`~/.ssh/id_rsa` and `~/.ssh/identity`) são automaticamente adicionadas ao agente de autenticação SSH. Não há necessidade de executar ssh-add path/to/key, a não ser que você substitua o nome do arquivo ao gerar uma chave. {% endtip %} -#### Getting more details +#### Obtendo mais detalhes -You can also check that the key is being used by trying to connect to `git@{% data variables.command_line.backticks %}`: +Você também pode verificar a chave que está sendo usada tentando se conectar a `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: Arquivo de identificação /Users/you/.ssh/id_rsa type -1 +> debug1: Arquivo de identificação /Users/you/.ssh/id_rsa-cert type -1 +> debug1: Arquivo de identificação /Users/you/.ssh/id_dsa type -1 +> debug1: Arquivo de identificação /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). +> debug1: Autenticações que podem prosseguir: publickey +> debug1: Próximo método de autenticação: publickey +> debug1: Tentando chave privada: /Users/you/.ssh/id_rsa +> debug1: Tentando chave privada: /Users/you/.ssh/id_dsa +> debug1: Não há mais métodos de autenticação para tentar. +> Permissão negada (publickey). ``` +, a não ser que você substitua o nome do arquivo ao gerar uma chave. -In that example, we did not have any keys for SSH to use. The "-1" at the end of the "identity file" lines means SSH couldn't find a file to use. Later on, the "Trying private key" lines also indicate that no file was found. If a file existed, those lines would be "1" and "Offering public key", respectively: +{% endtip %} + +#### Obtendo mais detalhes + +Você também pode verificar a chave que está sendo usada tentando se conectar a `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: Arquivo de identificação /Users/you/.ssh/id_rsa type -1 +> debug1: Arquivo de identificação /Users/you/.ssh/id_rsa-cert type -1 +> debug1: Arquivo de identificação /Users/you/.ssh/id_dsa type -1 +> debug1: Arquivo de identificação /Users/you/.ssh/id_dsa-cert type -1 > ... -> debug1: Authentications that can continue: publickey -> debug1: Next authentication method: publickey -> debug1: Offering RSA public key: /Users/you/.ssh/id_rsa +> debug1: Autenticações que podem prosseguir: publickey +> debug1: Próximo método de autenticação: publickey +> debug1: Tentando chave privada: /Users/you/.ssh/id_rsa +> debug1: Tentando chave privada: /Users/you/.ssh/id_dsa +> debug1: Não há mais métodos de autenticação para tentar. +> Permissão negada (publickey). + + +Nesse exemplo, não temos nenhuma chave SSH para usar. "-1" ao final das linhas "arquivo de identificação" indica que o SSH não conseguiu encontrar um arquivo para usar. Mais adiante, as linhas "Tentando chave privada" também indicam que o arquivo não foi encontrado. Se existisse um arquivo, as linhas seriam respectivamente "1" e "Apresentando chave pública": + +```shell +$ ssh -vT git@{% data variables.command_line.codeblock %} +> ... +> debug1: arquivo de identificação /Users/you/.ssh/id_rsa type 1 +> ... +> debug1: Autenticações que podem prosseguir: publickey +> debug1: Próximo método de autenticação: publickey +> debug1: Apresentando chave pública RSA: /Users/you/.ssh/id_rsa ``` -### Verify the public key is attached to your account +### Verifique se a chave pública está associada à sua conta -You must provide your public key to {% data variables.product.product_name %} to establish a secure connection. +Forneça sua chave pública a {% data variables.product.product_name %} para estabelecer uma conexão segura. {% mac %} -1. Open Terminal. -2. Start SSH agent in the background. +1. Abra o terminal. +2. Inicie o SSH agent em segundo plano. ```shell $ eval "$(ssh-agent -s)" > Agent pid 59566 ``` -3. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +3. Encontre e anote a impressão digital da chave pública. {% if currentVersion ver_lt "enterprise-server@3.0" %}Se você estiver usando OpenSSH 6.7 ou 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) ``` - If you're using OpenSSH 6.8 or newer: + Se estiver usando OpenSSH 6.8 ou posterior: ```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) @@ -206,26 +231,25 @@ You must provide your public key to {% data variables.product.product_name %} to {% 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. Open the command line. -2. Start SSH agent in the background. - ```shell +6. Compare a lista de chaves SSH com a saída do comando ssh-add. +Lista de chaves SSH em {% data variables.product.product_name %} Abra a linha de comando. +2. Inicie o SSH agent em segundo plano. $ ssh-agent -s > Agent pid 59566 ``` -3. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@3.0" %}If you're using OpenSSH 6.7 or older: +. +Lista de chaves SSH em {% data variables.product.product_name %} Abra a linha de comando. +2. Inicie o SSH agent em segundo plano. + $ ssh-agent -s + > Agent pid 59566 + +3. Encontre e anote a impressão digital da chave pública. {% if currentVersion ver_lt "enterprise-server@3.0" %}Se você estiver usando OpenSSH 6.7 ou 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) ``` - If you're using OpenSSH 6.8 or newer: + Se estiver usando OpenSSH 6.8 ou posterior: ```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) @@ -238,26 +262,27 @@ You must provide your public key to {% data variables.product.product_name %} to {% 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. Open Terminal. -2. Start SSH agent in the background. +6. Compare a lista de chaves SSH com a saída do comando ssh-add. +Lista de chaves SSH em {% data variables.product.product_name %} Abra o terminal. +2. Inicie o SSH agent em segundo plano. ```shell $ eval "$(ssh-agent -s)" > Agent pid 59566 ``` -3. Find and take a note of your public key fingerprint. If you're using OpenSSH 6.7 or older: +. +Lista de chaves SSH em {% data variables.product.product_name %} Abra o terminal. +2. Inicie o SSH agent em segundo plano. + ```shell + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + +3. Encontre e anote a impressão digital da chave pública. Se estiver usando OpenSSH 6.7 ou 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) ``` - If you're using OpenSSH 6.8 or newer: + Se estiver usando OpenSSH 6.8 ou posterior: ```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) @@ -265,15 +290,14 @@ You must provide your public key to {% data variables.product.product_name %} to {% 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) +6. Compare a lista de chaves SSH com a saída do comando `ssh-add`. ![Lista de chaves SSH em {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png) {% endlinux %} -If you don't see your public key in {% data variables.product.product_name %}, you'll need to [add your SSH key to {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account) to associate it with your computer. +Caso não consiga ver sua chave pública em {% data variables.product.product_name %}, será necessário [adicionar a chave SSH a {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account) para associá-la ao seu computador. {% warning %} -**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %}, for further help. An unidentified public key may indicate a possible security concern. For more information, see "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)." +**Aviso**: se você encontrar uma chave SSH com a qual não esteja familiarizado em {% data variables.product.product_name %}, delete-a imediatamente e entre em contato com {% data variables.contact.contact_support %} para obter ajuda. Uma chave pública desconhecida pode indicar um possível problema de segurança. Para obter mais informações, consulte "[Revisar as chaves SSH](/articles/reviewing-your-ssh-keys)". {% endwarning %} diff --git a/translations/pt-BR/content/github/authenticating-to-github/index.md b/translations/pt-BR/content/github/authenticating-to-github/index.md index 30e51c7087..8b61830312 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/index.md +++ b/translations/pt-BR/content/github/authenticating-to-github/index.md @@ -1,7 +1,7 @@ --- -title: Authenticating to GitHub -shortTitle: Authentication -intro: 'Keep your account and data secure with features like {% if currentVersion != "github-ae@latest" %}two-factor authentication, {% endif %}SSH{% if currentVersion != "github-ae@latest" %},{% endif %} and commit signature verification.' +title: Autenticar com o GitHub +shortTitle: Autenticação +intro: 'Mantenha sua conta e dados protegidos com recursos como {% if currentVersion != "github-ae@latest" %}autenticação de dois fatores, {% endif %}SSH{% if currentVersion ! "github-ae@latest" %},{% endif %} e verificação de assinatura do commit.' redirect_from: - /categories/56/articles/ - /categories/ssh/ @@ -17,10 +17,16 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - 2fa + - identidade + - gerenciamento de acesso + - nomes de usuário + - verificação de dispositivo --- -### Table of Contents +### Índice {% topic_link_in_list /keeping-your-account-and-data-secure %} {% link_in_list /about-authentication-to-github %} 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 ae3540b15c..3686f189bc 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 @@ -193,7 +193,7 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev | `sponsored_developer_create` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é criada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `sponsored_developer_profile_update` | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | | `sponsored_developer_request_approval` | Acionada quando você enviar seu aplicativo para {% data variables.product.prodname_sponsors %} para aprovação (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_tier_description_update` | Acionada quando você altera a descrição de um nível de patrocínio (consulte "[Alterar níveis de patrocínio](/articles/changing-your-sponsorship-tiers)") | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | | `sponsored_developer_update_newsletter_send` | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/articles/contacting-your-sponsors)") | | `waitlist_invite_sponsored_developer` | Acionada quando você é convidado a juntar-se a {% data variables.product.prodname_sponsors %} a partir da lista de espera (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `waitlist_join` | Acionada quando você se junta à lista de espera para tornar-se um desenvolvedor patrocinado (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | diff --git a/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md index 75214d3ae8..c2fa9a376a 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md +++ b/translations/pt-BR/content/github/authenticating-to-github/updating-your-github-access-credentials.md @@ -1,6 +1,6 @@ --- -title: Updating your GitHub access credentials -intro: '{% data variables.product.product_name %} credentials include{% if currentVersion != "github-ae@latest" %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.' +title: Atualizar credenciais de acesso do GitHub +intro: 'As credenciais de {% data variables.product.product_name %} incluem{% if currentVersion != "github-ae@latest" %} não apenas sua senha, mas também{% endif %} os tokens de acesso, Chaves SSH e tokens do aplicativo da API que você usa para se comunicar com {% data variables.product.product_name %}. Se houver necessidade, você mesmo pode redefinir todas essas credenciais de acesso.' redirect_from: - /articles/rolling-your-credentials/ - /articles/how-can-i-reset-my-password/ @@ -9,54 +9,55 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - identidade + - gerenciamento de acesso --- {% if currentVersion != "github-ae@latest" %} -### Requesting a new password +### Solicitar uma nova senha -1. To request a new password, visit {% 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. Enter the email address associated with your personal {% data variables.product.product_name %} account, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. - ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png) -3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder. -4. After clicking on the link in your email, you'll be asked to enter a new password. - ![Password recovery box](/assets/images/help/settings/password_recovery_page.png) +1. Para solicitar uma nova senha, acesse {% 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. Digite o endereço de e-mail associado à sua conta pessoal do {% data variables.product.product_name %} e clique em **Send password reset email** (Enviar e-mail de redefinição de senha). O e-mail será enviado para o endereço de e-mail de backup, se você tiver um configurado. ![Caixa de diálogo para solicitar e-mail de redefinição de senha](/assets/images/help/settings/password-recovery-email-request.png) +3. Nós enviaremos por e-mail um link para você redefinir sua senha. Clique nele em até 3 horas após o recebimento do e-mail. Se você não receber o e-mail com o link, verifique sua pasta de spam. +4. Depois de clicar no link contido no e-mail, você precisará digitar uma nova senha.![Caixa para recuperar senha](/assets/images/help/settings/password_recovery_page.png) {% tip %} -To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/). +Para evitar que você perca a senha, sugerimos que você use um gerenciador de senhas seguras, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), ou [Keeper](https://keepersecurity.com/). {% endtip %} -### Changing an existing password +### Alterar uma senha existente {% data reusables.repositories.blocked-passwords %} -1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}. +1. {% data variables.product.signin_link %} para o {% data variables.product.product_name %}. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security %} -4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)" -5. Click **Update password**. +4. Em "Change password" (Alterar senha), insira a senha antiga, digite uma nova senha forte e confirme a nova senha. Consulte "[Criar uma senha forte](/articles/creating-a-strong-password)" para obter ajuda sobre esse assunto. +5. Clique em **Update password** (Atualizar senha). {% tip %} -For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/articles/about-two-factor-authentication) for more details. +Para maior segurança, além de alterar a senha, habilite também a autenticação de dois fatores. Consulte [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication) para ver mais detalhes. {% endtip %} {% endif %} -### Updating your access tokens +### Atualizar tokens de acesso -See "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +Consulte "[Revisar integrações autorizadas](/articles/reviewing-your-authorized-integrations)" para ver instruções sobre como revisar e excluir tokens de acesso. Para gerar novos tokens de acesso, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." -### Updating your SSH keys +### Atualizar chaves SSH -See "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/articles/generating-an-ssh-key)." +Consulte "[Revisar as chaves SSH](/articles/reviewing-your-ssh-keys)" para ver instruções sobre como revisar e excluir chaves SSH. Para gerar e adicionar novas chaves SSH, consulte "[Gerar uma chave SSH](/articles/generating-an-ssh-key)". -### Resetting API tokens +### Redefinir tokens da API -If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/reference/apps#reset-an-authorization)" endpoint. +Se você tiver algum aplicativo registrado no {% data variables.product.product_name %}, talvez precise redefinir os tokens OAuth dele. Para obter mais informações, consulte o ponto de extremidade "[Redefinir uma autorização](/rest/reference/apps#reset-an-authorization)". {% if currentVersion != "github-ae@latest" %} -### Preventing unauthorized access +### Impedir acesso não autorizado -For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)." +Consulte "[Impedir acesso não autorizado](/articles/preventing-unauthorized-access)" para obter mais dicas sobre como proteger a conta e impedir acesso não autorizado. {% endif %} diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index c72fc3681a..8a3efdb391 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -18,7 +18,7 @@ topics: Os problemas são úteis para discutir detalhes específicos de um projeto, como relatórios de erros e melhorias planejadas. Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues)". As pull requests permitem comentar diretamente nas alterações propostas. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)" e "[Comentar em uma pull request](/articles/commenting-on-a-pull-request)". -{% data reusables.organizations.team-discussions-purpose %} Para obter mais informações, consulte "[Sobre discussões de equipe](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +{% data reusables.organizations.team-discussions-purpose %} Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)." ### Reagir às ideias nos comentários 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 c717bc4ab6..8770455ee1 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 @@ -15,7 +15,7 @@ topics: Após a abertura de uma pull request, qualquer pessoa com acesso *de leitura* pode revisar e comentar nas alterações que ela propõe. Você também pode sugerir alterações específicas às linhas de código, que o autor pode aplicar diretamente a partir da pull request. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". -Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/articles/requesting-a-pull-request-review)". {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Você pode especificar um subconjunto de integrantes da equipe a ser atribuído automaticamente no lugar de toda a equipe. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} +Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/articles/requesting-a-pull-request-review)". {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Você pode especificar um subconjunto de integrantes da equipe a ser atribuído automaticamente no lugar de toda a equipe. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} As revisões permitem discussão das alterações propostas e ajudam a garantir que as alterações atendam às diretrizes de contribuição do repositório e outros padrões de qualidade. Você pode definir quais indivíduos ou equipes possuem determinados tipos de área de código em um arquivo CODEOWNERS. Quando uma pull request modifica código que tem um proprietário definido, esse indivíduo ou equipe será automaticamente solicitado como um revisor. Para obter mais informações, consulte "[Sobre proprietários de código](/articles/about-code-owners/)". diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 9ad67bc5e5..ab791c77d0 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -14,7 +14,9 @@ topics: Se você habilitar o merge automático para um pull request, este será mesclado automaticamente quando todas as revisões necessárias forem atendidas e as verificações de status forem aprovadas. O merge automático impede que você espere que os sejam atendidos para que você possa passar para outras tarefas. -Antes de usar o merge automático com um pull request, o merge automático deve ser habilitado para o repositório. Para obter mais informações, consulte "[Gerenciar merge automático para pull requests no seu repositório](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository). +Antes de usar o merge automático com um pull request, o merge automático deve ser habilitado para o repositório. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} + +After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} Você pode fornecer feedback sobre o merge automático [entrando em contato conosco](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback). diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index b0462a695d..b3e1b0604c 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -13,7 +13,7 @@ topics: Proprietários e colaboradores de um repositório pertencente a uma conta de usuário podem atribuir revisões de pull requests. Os integrantes da organização com permissões de triagem em um repositório podem atribuir uma revisão de pull request. -Os proprietários e colaboradores podem atribuir uma revisão de pull request a qualquer pessoa que recebeu explicitamente [acesso de leitura](/articles/access-permissions-on-github) em um repositório pertencente a um usuário. Os integrantes da organização podem atribuir uma revisão de pull request para qualquer pessoa ou equipe com acesso de leitura em um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Se você solicitou uma revisão de uma equipe e a atribuição de código estiver habilitada, será solicitado que integrantes específicos e a equipe sejam removidos como revisores. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} +Os proprietários e colaboradores podem atribuir uma revisão de pull request a qualquer pessoa que recebeu explicitamente [acesso de leitura](/articles/access-permissions-on-github) em um repositório pertencente a um usuário. Os integrantes da organização podem atribuir uma revisão de pull request para qualquer pessoa ou equipe com acesso de leitura em um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Se você solicitou uma revisão de uma equipe e a atribuição de código estiver habilitada, será solicitado que integrantes específicos e a equipe sejam removidos como revisores. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} {% note %} 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 b233d9d4c8..ef0e259703 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 @@ -19,7 +19,7 @@ topics: {% data reusables.dependency-review.feature-overview %} -Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." +Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". ### Revisar as dependências em um pull request diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index 023b00d2aa..975ed6f918 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -79,5 +79,5 @@ Se você alterar a visibilidade de um repositório interno e, em seguida, exclui - "[Definir a visibilidade de um repositório](/articles/setting-repository-visibility)" - "[Sobre bifurcações](/articles/about-forks)" - "[Gerenciando a política de bifurcação de seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" -- "[Gerenciar a política de bifurcação para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" - "{% if currentVersion == "free-pro-team@latest" %}[Aplicar políticas de gerenciamento do repositório na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}" diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md b/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md index ed96783b90..8a187dd3f6 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md @@ -1,9 +1,9 @@ --- -title: Why are my commits linked to the wrong user? +title: Por que meus commits estão vinculados ao usuário errado? redirect_from: - /articles/how-do-i-get-my-commits-to-link-to-my-github-account/ - /articles/why-are-my-commits-linked-to-the-wrong-user -intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% if currentVersion != "github-ae@latest" %}, add an email address to your account email settings, or do both{% endif %}.' +intro: 'O {% data variables.product.product_name %} usa o endereço de e-mail no header do commit para vincular o commit a um usuário do GitHub. Se seus commits estão sendo vinculados a outro usuário, ou não vinculados a um usuário, você pode precisar alterar suas configurações locais de configuração do Git, {% if currentVersion != "github-ae@latest" %}, adicionar um endereço de e-mail nas configurações de e-mail da sua conta ou fazer ambas as coisas{% endif %}.' versions: free-pro-team: '*' enterprise-server: '*' @@ -13,44 +13,42 @@ versions: {% tip %} -**Note**: If your commits are linked to another user, that does not mean the user can access your repository. A user can only access a repository you own if you add them as a collaborator or add them to a team that has access to the repository. +**Observação**: se os commits estiverem vinculados a outro usuário, não significa que o usuário possa acessar o repositório pertencente a você. Um usuário só poderá acessar um repositório seu se você adicioná-lo como colaborador ou incluí-lo em uma equipe que tenha acesso ao repositório. {% endtip %} -### Commits are linked to another user +### Commits vinculados a outro usuário -If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% if currentVersion == "github-ae@latest" %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your {% data variables.product.product_name %} account to link future commits to your account. +Se seus commits estiverem vinculados a outro usuário, isso significa que o endereço de e-mail nas configurações locais do Git está conectado à conta desse usuário em {% data variables.product.product_name %}. Neste caso, você pode alterar o e-mail nas configurações locais do Git, {% if currentVersion == "github-ae@latest" %} ao endereço associado à sua conta em {% data variables.product.product_name %} para vincular seus commits futuros. Os commits antigos não serão vinculados. Para obter mais informações, consulte "[Definir o seu endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git).{% else %} E adicione o novo endereço de e-mail à sua conta de {% data variables.product.product_name %} para vincular futuros commits à sua conta. -1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". If you work on multiple machines, you will need to change this setting on each one. -2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %} +1. Para alterar o endereço de e-mail na sua configuração Git local, siga os passos em "[Definir o seu endereço de e-mail de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". Se você trabalha em várias máquinas, precisa alterar essa configuração em cada uma deles. +2. Adicione o endereço de e-mail da etapa 2 às configurações da sua conta seguindo os passos em "[Adicionar um endereço de e-mail à sua conta GitHub](/articles/adding-an-email-address-to-your-github-account)".{% endif %} -Commits you make from this point forward will be linked to your account. +Os commits criados a partir daí serão vinculados à sua conta. -### Commits are not linked to any user +### Commits não vinculados a nenhum usuário -If your commits are not linked to any user, the commit author's name will not be rendered as a link to a user profile. +Se seus commits não estiverem vinculados a nenhum usuário, o nome do autor do commit não será exibido como um link para o perfil de um usuário. -To check the email address used for those commits and connect commits to your account, take the following steps: +Para verificar o endereço de e-mail usado para esses commits e conectar commits à sua conta, siga estas etapas: -1. Navigate to the commit by clicking the commit message link. -![Commit message link](/assets/images/help/commits/commit-msg-link.png) -2. To read a message about why the commit is not linked, hover over the blue {% octicon "question" aria-label="Question mark" %} to the right of the username. -![Commit hover message](/assets/images/help/commits/commit-hover-msg.png) +1. Navegue até o commit clicando no link da mensagem do commit. ![Link da mensagem do commit](/assets/images/help/commits/commit-msg-link.png) +2. Para ler uma mensagem sobre o motivo do commit não estar vinculado, passe o mouse sobre o {% octicon "question" aria-label="Question mark" %} azul à direita do nome de usuário. ![Mensagem do commit exibida ao passar o mouse](/assets/images/help/commits/commit-hover-msg.png) - - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat. - - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} - - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} + - **Autor não reconhecido (com endereço de e-mail)** Se você vir esta mensagem com um endereço de e-mail, o endereço que você usou para criar o commit não estará conectado à sua conta em {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}Para vincular seus commits, [adicione o endereço de e-mail às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account).{% endif %} Se o endereço de e-mail tiver um Gravatar associado, o Gravatar será exibido ao lado do commit, em vez do Octoact cinza padrão. + - **Autor não reconhecido (sem endereço de e-mail)** Se você vir esta mensagem sem um endereço de e-mail, significa que você usou um endereço de e-mail genérico que não pode ser conectado à sua conta em {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} Você precisará [definir seu endereço de e-mail do commit no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de e-mail do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %} + - **E-mail inválido** O endereço de e-mail nas configurações locais do Git está em branco ou não está formatado como um endereço de e-mail.{% if currentVersion != "github-ae@latest" %} Você precisará [definir seu endereço de e-mail de commit no Git](/articles/setting-your-commit-email-address) e, em seguida, [adicionar o novo endereço às suas configurações de email do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular seus futuros commits. Os commits antigos não serão vinculados.{% endif %} {% if currentVersion == "github-ae@latest" %} -You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)." +Você pode alterar o e-mail nas configurações locais do Git para o endereço associado à sua conta para vincular seus futuros commits. Os commits antigos não serão vinculados. Para obter mais informações, consulte "[Configurar o endereço de e-mail do commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". {% endif %} {% warning %} -If your local Git configuration contained a generic email address, or an email address that was already attached to another user's account, then your previous commits will not be linked to your account. While Git does allow you to change the email address used for previous commits, we strongly discourage this, especially in a shared repository. +Caso a configuração local do Git contenha um endereço de e-mail genérico ou um endereço de e-mail já anexado à conta de outro usuário, os commits anteriores não serão vinculados à sua conta. Embora o Git permita que você altere o endereço de e-mail usado para commits anteriores, é recomendável evitar isso, principalmente em um repositório compartilhado. {% endwarning %} -### Further reading +### Leia mais -* "[Searching commits](/articles/searching-commits)" +* "[Pesquisar commits](/articles/searching-commits)" 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 7389d8d80b..41a992ac39 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 @@ -23,7 +23,7 @@ Solicita-se automaticamente que os proprietários do código revisem quando algu Quando alguém com permissões de administrador ou proprietário tiver habilitado revisões obrigatórias, se desejar, ele também poderá exigir aprovação de um proprietário do código para que o autor possa fazer merge de uma pull request no repositório. Para obter mais informações, consulte "[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 %} +{% 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](/organizations/organizing-members-into-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.22" %} Se um arquivo tiver um proprietário do código, você poderá ver quem é o proprietário do código antes de abrir um pull request. No repositório, é possível pesquisar o arquivo e passar o mouse sobre diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md index f33b751a24..e320f92185 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -19,7 +19,7 @@ topics: {% data variables.product.product_name %} usa [Biblioteca Linguist](https://github.com/github/linguist) a de código aberto para determinar as linguagens de arquivo para destacar a sintaxe e estatísticas do repositório. As estatísticas da linguagem serão atualizadas após você fazer push de alterações no seu branch-padrão. -Alguns arquivos são difíceis de identificar e, às vezes, os projetos contêm mais arquivos de fornecedor e biblioteca do que código primário. Se estiver recebendo resultados incorretos, consulte o [guia de solução de problemas](https://github.com/github/linguist#troubleshooting) do Linguist para obter ajuda. +Alguns arquivos são difíceis de identificar e, às vezes, os projetos contêm mais arquivos de fornecedor e biblioteca do que código primário. Se estiver recebendo resultados incorretos, consulte o [guia de solução de problemas](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) do Linguist para obter ajuda. ### Linguagens markup diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index d5cc5b375f..04d96a0d39 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -22,7 +22,7 @@ Os repositórios só podem ser acessados por você, pelas pessoas com as quais v Os repositórios públicos podem ser acessados por todos na internet. Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização. Os repositórios internos podem ser acessados por todos os integrantes da empresa. Para obter mais informações, consulte "[Sobre repositórios internos](#about-internal-repositories)." {% endif %} -Os proprietários da organização sempre têm acesso a todos os repositórios criados em uma organização. Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". +Os proprietários da organização sempre têm acesso a todos os repositórios criados em uma organização. Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". As pessoas com permissões de administrador para um repositório podem alterar a visibilidade de um repositório existente. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)". diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md index 7eb9f7cf2e..fa7adbbf85 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -23,13 +23,13 @@ Para poder duplicar um repositório e fazer push (ou seja, _espelhamento_) na no ``` 3. Faça espelhamento/push no novo repositório. ```shell - $ cd old-repository.git + $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` 4. Remova o repositório local temporário que você criou anteriormente. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Espelhar um repositório que contém objetos do {% data variables.large_files.product_name_long %} @@ -41,7 +41,7 @@ Para poder duplicar um repositório e fazer push (ou seja, _espelhamento_) na no ``` 3. Navegue até o repositório que você acabou de clonar. ```shell - $ cd old-repository.git + $ cd old-repository ``` 4. Extraia os objetos do {% data variables.large_files.product_name_long %} do repositório. ```shell @@ -58,7 +58,7 @@ Para poder duplicar um repositório e fazer push (ou seja, _espelhamento_) na no 7. Remova o repositório local temporário que você criou anteriormente. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Espelhar um repositório em outro local @@ -72,7 +72,7 @@ Se você deseja espelhar um repositório em outro local e ainda obter atualizaç ``` 3. Defina o local de push no espelho. ```shell - $ cd repository-to-mirror.git + $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index 143cca3c97..01a7f3ba3b 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > fornece acesso shell. ``` -Se o repositório pertencer a uma organização e você estiver usando uma chave SSH gerada por um aplicativo OAuth, o acesso ao aplicativo OAuth poderá ser restringido pelo proprietário da organização. Para obter mais informações, consulte "Sobre as restrições de acesso ao aplicativo OAuth". +Se o repositório pertencer a uma organização e você estiver usando uma chave SSH gerada por um aplicativo OAuth, o acesso ao aplicativo OAuth poderá ser restringido pelo proprietário da organização. For more information, see "About OAuth App access restrictions." Para obter mais informações, consulte [Adicionar uma nova chave SSH à sua conta GitHub](/articles/adding-a-new-ssh-key-to-your-github-account). diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md index f7635d32b0..c607d8a5ea 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -1,6 +1,6 @@ --- title: Usar Codespaces no Visual Studio -intro: 'Você pode desenvolver seu código diretamente em {% data variables.product.prodname_vs %} conectando-se com sua conta no {% data variables.product.product_name %}.' +intro: 'This preview has concluded and will no longer be accepting signups.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,50 +10,10 @@ topics: {% note %} -**Observação:** {% data variables.product.prodname_codespaces %} está atualmente em versão beta pública limitada e sujeito a alterações. Durante o período beta, {% data variables.product.prodname_dotcom %} não faz nenhuma garantia sobre a disponibilidade de {% data variables.product.prodname_codespaces %}. [Cadastre-se para o beta público limitado](https://github.com/features/codespaces/signup-vs). Para obter mais informações sobre fontes de publicação, consulte "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." +**Observação:** {% data variables.product.prodname_codespaces %} está atualmente em versão beta pública limitada e sujeito a alterações. Durante o período beta, {% data variables.product.prodname_dotcom %} não faz nenhuma garantia sobre a disponibilidade de {% data variables.product.prodname_codespaces %}. {% endnote %} ### Sobre os codespaces em {% data variables.product.prodname_vs %} -Você pode criar um código no {% data variables.product.prodname_vs %} para desenvolver aplicativos em um ambiente Windows. Ao usar um código em {% data variables.product.prodname_vs %}, você pode navegar pelo código-fonte, criar soluções e fazer commit de alterações no seu repositório. - -Você deve criar um codespace em {% data variables.product.prodname_vs %} para usá-lo com o aplicativo. Os codespaces criados fora do {% data variables.product.prodname_vs %} não podem ser usados atualmente com {% data variables.product.prodname_vs %}. - -### Pré-requisitos - -Antes de configurar um código em {% data variables.product.prodname_vs %}, você deve fazer o download da última versão da pré-visualização de [{% data variables.product.prodname_vs %}](https://aka.ms/vspreview). - -#### Habilitar a conexão entre {% data variables.product.prodname_vs %} e {% data variables.product.prodname_github_codespaces %} - -A conexão ao {% data variables.product.prodname_github_codespaces %} com a pré-visualização de {% data variables.product.prodname_vs %} não está habilitado por padrão. Portanto, você primeiro deverá habilitar o recurso de pré-visualização. - -1. Na visualização do {% data variables.product.prodname_vs %}, use o menu suspenso Ferramentas e, em seguida, clique em **Opções**. -2. Em **Ambiente**, selecione **Recursos de pré-visualização** e verifique o recurso de pré-visualização **Conectar a {% data variables.product.prodname_github_codespaces %}**. ![Verifique o recurso de pré-visualização conectar ao {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png) -3. Será necessário reiniciar o {% data variables.product.prodname_vs %} para que o recurso esteja disponível. - -### Criar um codespace em {% data variables.product.prodname_vs %} - -1. Quando você iniciar o {% data variables.product.prodname_vs %}, a Janela Inicial irá exibir um botão **Conectar-se a um codespace** em "Iniciar". ![Janela de início do Visual Studio com a conexão a um codespace](/assets/images/help/codespaces/visual-studio-start-window.png) -2. Clique em **Conectar-se a um codespace**. -3. Clique em **Efetuar login em {% data variables.product.prodname_dotcom %}** e siga as instruções ou clique em **Criar uma!** para criar uma nova conta de {% data variables.product.prodname_dotcom %} e entrar na conta. ![Login do Visual Studio em {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/visual-studio-sign-in-to-github.png) -4. Em "Informações de codespace", digite a URL do repositório que você deseja que o {% data variables.product.prodname_github_codespaces %} clone no seu codespace. -5. Opcionalmente, use o tipo de instância e suspenda após os menus suspensos para configurar mais informações do codespace. ![Detalhes do codespace do Visual Studio](/assets/images/help/codespaces/visual-studio-codespace-details.png) -6. Clique em **Criar e conectar**. {% data variables.product.prodname_github_codespaces %} começará a preparar o codespace e abrirá {% data variables.product.prodname_vs %} depois que o codespace estiver pronto. O nome do codespace será exibido no indicador remoto no menu. ![Visual Studio conectado ao codespace do repositório do eShopOnWeb](/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png) - -### Abrir um codespace em {% data variables.product.prodname_vs %} - -1. Use o menu suspenso de arquivos e clique em **Conectar a um codespace**. ![Conexão do Arquivo do Visual Studio a um item de menu do codespace](/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png) -2. Em "{% data variables.product.prodname_github_codespaces %}", clique no codespace ao qual você deseja conectar-se e, em seguida, clique em **Conectar**. ![Visual Studio exibe codespaces e informações disponíveis](/assets/images/help/codespaces/visual-studio-connect-codespace.png) - -### Configurar um codespace para {% data variables.product.prodname_vs %} - -Um codespace, criado com {% data variables.product.prodname_vs %}, pode ser personalizado por meio de uma nova ferramenta denominada devinit, uma ferramenta de linha de comando incluída com {% data variables.product.prodname_vs %}. - -#### devinit - -[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) permite que você instale estruturas e ferramentas adicionais nos seus codespaces de desenvolvimento do Windows, modificar as variáveis de ambiente e muito mais. - -O devinit é compatível com um arquivo de configuração denominado [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). Você pode adicionar este arquivo ao seu projeto se você desejar criar um ambiente de desenvolvimento personalizado e reproduzível. Ao usar devinit com um arquivo [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace), seus codespaces serão configurados automaticamente na criação. - -Para obter mais informações sobre a configuração do codespace do Windows e sobre a devinit, consulte [Personalizar um codespace](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces) na documentação do {% data variables.product.prodname_vs %}. Para obter mais informações sobre devinit, consulte [Primeiros passos com devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit). +The private preview for GitHub Codespaces in Visual Studio 2019 has concluded. For more information, see the [Visual Studio 2019 documentation](https://docs.microsoft.com/visualstudio/ide/codespaces/codespaces-overview?view=vs-2019). 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 c562deae1a..5645913148 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 @@ -2,11 +2,10 @@ title: Sobre a varredura de código intro: 'Você pode usar {% data variables.product.prodname_code_scanning %} para encontrar vulnerabilidades e erros de segurança no código do seu projeto no {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/managing-security-vulnerabilities/about-automated-code-scanning versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - segurança --- {% data reusables.code-scanning.beta %} @@ -20,9 +19,9 @@ 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)." +Para monitorar os resultados de {% data variables.product.prodname_code_scanning %} nos seus repositórios ou organização, você pode usar webhooks e a API de {% data variables.product.prodname_code_scanning %}. Para obter informações sobre os webhooks para {% data variables.product.prodname_code_scanning %}, consulte "[Eventos de webhook e cargas](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". Para obter informações sobre os pontos de extremidade da API, consulte "[{% 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)." +Para começar com {% data variables.product.prodname_code_scanning %}, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)". ### Sobre o {% data variables.product.prodname_codeql %} @@ -34,7 +33,7 @@ Para obter mais informações sobre os pontos de extremidade da API para {% data {% data reusables.code-scanning.supported-languages %} -Você pode visualizar e contribuir para as consultas do {% data variables.product.prodname_code_scanning %} no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %} consultas](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) na documentação do {% data variables.product.prodname_codeql %}. +Você pode visualizar e contribuir para as consultas do {% data variables.product.prodname_code_scanning %} no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %} consultas](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) na documentação do {% data variables.product.prodname_codeql %}. {% if currentVersion == "free-pro-team@latest" %} @@ -54,7 +53,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 6a4cad90c3..fd307b5035 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 @@ -5,8 +5,9 @@ product: '{% data reusables.gated-features.code-scanning %}' permissions: 'Pessoas com permissões de gravação para um repositório podem configurar {% data variables.product.prodname_code_scanning %} para o repositório.' miniTocMaxHeadingLevel: 4 versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - segurança --- {% data reusables.code-scanning.beta %} @@ -14,11 +15,11 @@ versions: ### Sobre a configuração do {% data variables.product.prodname_code_scanning %} -Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}, usando {% data variables.product.prodname_actions %} ou a partir do seu sistema de integração contínua (CI), usando o {% data variables.product.prodname_codeql_runner %}. Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." Para obter mais informações sobre o {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". +Você pode executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}, usando {% data variables.product.prodname_actions %}, ou a partir do seu sistema de integração contínua (CI), ao usar {% data variables.product.prodname_codeql_runner %}. Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." Para obter mais informações sobre o {% data variables.product.prodname_codeql_runner %}, consulte "[Executar {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)". -Este artigo é sobre executar {% data variables.product.prodname_code_scanning %} dentro de {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +Este artigo é sobre a execução de {% data variables.product.prodname_code_scanning %} no {% data variables.product.product_name %}. -Antes de poder configurar o {% data variables.product.prodname_code_scanning %} para um repositório, você deve habilitar o {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho do {% data variables.product.prodname_actions %} ao repositório. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). +Antes de poder configurar o {% data variables.product.prodname_code_scanning %} para um repositório, você deve configurar {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho do {% data variables.product.prodname_actions %} ao repositório. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)". {% data reusables.code-scanning.edit-workflow %} @@ -26,7 +27,7 @@ A análise de {% data variables.product.prodname_codeql %} é apenas um tipo de ### Editing a code scanning workflow -O {% data variables.product.prodname_dotcom %} salva arquivos de fluxo de trabalho no diretório _.github/workflows_ do seu repositório. You can find the workflow by searching for its file name. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. +O {% data variables.product.prodname_dotcom %} salva arquivos de fluxo de trabalho no diretório _.github/workflows_ do seu repositório. Você pode encontrar um fluxo de trabalho que você adicionou procurando o nome do seu arquivo. For example, the default workflow file for CodeQL code scanning is called `codeql-analysis.yml`. 1. No seu repositório, pesquise o arquivo do fluxo de trabalho que você deseja editar. 1. No canto superior direito da vista do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %} para abrir o editor do fluxo de trabalho. ![Edite o botão do arquivo do fluxo de trabalho](/assets/images/help/repository/code-scanning-edit-workflow-button.png) @@ -70,7 +71,7 @@ on: **Observações** * `on:pull_request:paths-ignore` e `on:pull_request:paths` definem condições que determinam se as ações no fluxo de trabalho serão executadas em um pull request. Eles não determinam quais arquivos serão analisados quando as ações _são_ executadas. Quando uma pull request contém quaisquer arquivos não correspondidos por `on:pull_request:paths-ignore` ou `on:pull_request:paths`, o fluxo de trabalho executa as ações e faz a varredura de todos os arquivos alterados no pull request, incluindo aqueles que correspondidos por `on:pull_request:paths-ignore` ou `on:pull_request:paths`, a menos que os arquivos tenham sido excluídos. Para obter informações sobre como excluir arquivos da análise, consulte "[Especificar diretórios a serem varridos](#specifying-directories-to-scan)". -* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. Para resultados precisos, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} precisam conseguir comparar novas alterações com a análise do commit anterior. +* Para arquivos do fluxo de trabalho de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, não use as palavras-chave `paths-ignore` ou `paths` com o evento `on:push`, pois é provável que isso gere análises ausentes. Para resultados precisos, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} precisam conseguir comparar novas alterações com a análise do commit anterior. {% endnote %} @@ -93,15 +94,17 @@ O exemplo a seguir mostra um {% data variables.product.prodname_codeql_workflow ``` yaml on: push: + branches: [main, protected] pull_request: + branches: [main] schedule: - - cron: '0 15 * * 0' + - cron: '40 7 * * 2' ``` Este fluxo de trabalho faz a varredura: * Cada push para o branch-padrão e o branch protegido * Cada pull request para o branch-padrão -* O branch-padrão às 15h. todo domingo +* The default branch every Tuesday at 7:40 UTC ### Especificar um sistema operacional @@ -132,7 +135,7 @@ O arquivo padrão do {% data variables.product.prodname_codeql_workflow %} cont {% data reusables.code-scanning.specify-language-to-analyze %} -Se o seu fluxo de trabalho usar a matriz de linguagem `, o {% data variables.product.prodname_codeql %} será codificado para analisar apenas as linguagens da matriz. Para alterar as linguagens que você deseja analisar, edite o valor da variável da matriz. Você pode remover uma linguagem para evitar que ele seja analisado ou adicionar uma linguagem que não estava presente no repositório quando o {% data variables.product.prodname_code_scanning %} estava habilitado. Por exemplo, se o repositório inicialmente continha apenas JavaScript quando {% data variables.product.prodname_code_scanning %} foi habilitado e, posteriormente, você adicionou o código Python, você precisará adicionar o python` à matriz. +Se o seu fluxo de trabalho usar a matriz de linguagem `, o {% data variables.product.prodname_codeql %} será codificado para analisar apenas as linguagens da matriz. Para alterar as linguagens que você deseja analisar, edite o valor da variável da matriz. Você pode remover uma linguagem para evitar que ele seja analisado ou adicionar uma linguagem que não estava presente no repositório quando o {% data variables.product.prodname_code_scanning %} estava configurado. Por exemplo, se o repositório inicialmente continha apenas JavaScript quando {% data variables.product.prodname_code_scanning %} foi configurado e, posteriormente, você adicionou o código Python, você precisará adicionar o python` à matriz. ```yaml jobs: @@ -199,13 +202,17 @@ jobs: {% data reusables.code-scanning.run-additional-queries %} -Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. +Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. Se as consultas estiverem em um repositório privado, use o parâmetro `external-repository-token` para especificar um token que tenha acesso ao repositório privado. +{% raw %} ``` yaml - uses: github/codeql-action/init@v1 with: queries: COMMA-SEPARATED LIST OF PATHS + # Optional. Forneça uma token para acessar repositórios privados. + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} Você também pode executar suítes de consultas adicionais especificando-os em um arquivo de configuração. Os suítes de consulta são coleções de consultas, geralmente agrupados por finalidade ou linguagem. @@ -215,12 +222,15 @@ Você pode executar consultas adicionais especificando-as em um arquivo de confi Para incluir um ou mais suites de consulta, adicione uma seção `consultas` ao seu arquivo de configuração. +{% raw %} ``` 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 + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} ### Usar uma ferramenta de varredura de código de terceiros @@ -234,7 +244,19 @@ 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. +{% data reusables.code-scanning.custom-configuration-file %} + +Se o arquivo de configuração estiver localizado em um repositório privado externo, use o parâmetro `external-repository-token` da ação `init` para especificar um token que tenha acesso ao repositório privado. + +{% raw %} +```yaml +uses: github/codeql-action/init@v1 +with: + external-repository-token: ${{ secrets.ACCESS_TOKEN }} +``` +{% endraw %} + +As configurações no arquivo de configuração estão escritas no formato YAML. #### Especificar consultas adicionais @@ -278,7 +300,7 @@ paths-ignore: Para linguagens compiladas, se você deseja limitar {% data variables.product.prodname_code_scanning %} a diretórios específicos no seu projeto, você deverá especificar os passos de compilação adequados no fluxo de trabalho. Os comandos que você precisa usar para excluir um diretório da criação dependerão do seu sistema de criação. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". -Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o código em diretórios específicos. Você deverá excluir diretórios nas suas etapas de criação e usar as palavras-chave `paths-ignore` e `caminhos` para [`on.`](https://docs.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) no seu arquivo de fluxo de trabalho. +Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o código em diretórios específicos. Você deverá excluir diretórios nas suas etapas de criação e usar as palavras-chave `paths-ignore` e `caminhos` para [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) no seu arquivo de fluxo de trabalho. #### Exemplo de arquivo de configuração @@ -290,25 +312,6 @@ Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o c {% data reusables.code-scanning.autobuild-add-build-steps %} Para obter mais informações sobre como configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} para linguagens compiladas, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)". -### Acessar repositórios privados - -Se o seu fluxo de trabalho para {% data variables.product.prodname_code_scanning %} acessar repositórios privados no {% data variables.product.prodname_dotcom %}, você deverá configurar o Git para efetuar a autenticação com um token de acesso pessoal. Defina o segredo no ambiente do executor usando `jobs..steps[*].env` no seu fluxo de trabalho antes de qualquer ação do {% data variables.product.prodname_codeql %}. Para mais informações consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" e "[Criar e armazenar segredos criptografados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". - -Por exemplo, a configuração a seguir faz com que o Git substitua todas as URLs para os repositórios de `ghost/foo`, `ghost/bar` e `ghost/baz` em {% data variables.product.prodname_dotcom_the_website %} pelas URLs que incluem o token de acesso pessoal que você armazena na variável de ambiente de `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 %} - ### {% data variables.product.prodname_code_scanning_capc %} usa {% data variables.product.prodname_actions %}. Você pode exibir análise de código de uma ferramenta de terceiros em {% data variables.product.prodname_dotcom %}, adicionando a ação de `upload-sarif` ao seu fluxo de trabalho. Você pode fazer o upload de dados de análise de código com a ação `upload-sarif`. Para obter mais informações, consulte "[Fazer o upload de um arquivo SARIF para o GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 9ba5a8f8ee..a082c81f58 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -37,7 +37,7 @@ Você precisa de permissão de gravação para visualizar um resumo de todos os {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -1. Em "{% data variables.product.prodname_code_scanning_capc %}", clique no alerta que você gostaria de explorar. ![Resumo dos alertas](/assets/images/help/repository/code-scanning-click-alert.png) +1. Em "{% data variables.product.prodname_code_scanning_capc %}", clique no alerta que você gostaria de explorar. ![Resumo dos alertas](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) 1. Opcionalmente, se o alerta destacar um problema com o fluxo de dados, clique em **Mostrar caminhos** para exibir o caminho da fonte de dados até o destino onde é usado. ![O link "Exibir caminhos" em um alerta](/assets/images/help/repository/code-scanning-show-paths.png) 1. Alertas da análise de {% data variables.product.prodname_codeql %} incluem uma descrição do problema. Clique em **Mostrar mais** para obter orientação sobre como corrigir seu código. ![Detalhes para um alerta](/assets/images/help/repository/code-scanning-alert-details.png) @@ -49,7 +49,7 @@ Se você tem permissão de escrita em um repositório, você pode visualizar ale Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico. -![Filtrar alertas por branch](/assets/images/help/repository/code-scanning-branch-filter.png) +![Filtrar alertas por branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} @@ -102,11 +102,11 @@ Para ignorar ou excluir alertas: Opcionalmente, você pode usar os filtros para exibir um subconjunto de alertas e, em seguida, excluir todos os alertas de correspondência de uma só vez. Por exemplo, se você removeu uma consulta da análise de {% data variables.product.prodname_codeql %}, você pode usar o filtro "Regra" para listar apenas os alertas dessa consulta e, em seguida, selecionar e apagar todos esses alertas. - ![Filtrar alertas por regra](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![Filtrar alertas por regra](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) 1. Se você deseja ignorar um alerta, é importante explorar primeiro o alerta para que você possa escolher o motivo correto para ignorá-lo. Clique no alerta que você deseja explorar. - ![Abrir um alerta da lista de resumo](/assets/images/help/repository/code-scanning-click-alert.png) + ![Abrir um alerta da lista de resumo](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) 1. Revise o alerta e clique em **Ignorar** e escolha um motivo para fechar o alerta. ![Escolher um motivo para ignorar um alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md index a47584bd74..00b0db863e 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -25,7 +25,7 @@ Você decide como gerar alertas de {% data variables.product.prodname_code_scann {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3. " %}Se {% data variables.product.prodname_code_scanning %} estiver faltando, peça para um proprietário da organização ou administrador de repositório habilitar {% data variables.product.prodname_GH_advanced_security %}. Para mais informações consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" ou "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png) +3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3. " %}Se {% data variables.product.prodname_code_scanning %} estiver faltando, peça para um proprietário da organização ou administrador de repositório habilitar {% data variables.product.prodname_GH_advanced_security %}. Para mais informações consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" ou "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Em "Começar com {% data variables.product.prodname_code_scanning %}", clique em **Configurar este fluxo de trabalho** no {% data variables.product.prodname_codeql_workflow %} ou em um fluxo de trabalho de terceiros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Os fluxos de trabalho são exibidos apenas se forem relevantes para as linguagens de programação detectadas no repositório. O {% data variables.product.prodname_codeql_workflow %} é sempre exibido, mas o botão "Configurar este fluxo de trabalho" só é habilitado se a análise de {% data variables.product.prodname_codeql %} for compatível com as linguagens presentes no repositório.{% endif %} 5. Para personalizar como {% data variables.product.prodname_code_scanning %} faz a varredura do seu código, edite o fluxo de trabalho. @@ -65,7 +65,7 @@ Depois de configurar o {% data variables.product.prodname_code_scanning %} para **Observação:** Se você criou um pull request para adicionar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %} ao repositório, os alertas desse pull request não serão exibidos diretamente na página de {% data variables.product.prodname_code_scanning_capc %} até que o pull request seja mesclado. Se algum alerta for encontrado, você poderá visualizá-los, antes do merge do pull request, clicando no link dos **_n_ alertas encontrados** no banner na página de {% data variables.product.prodname_code_scanning_capc %}. - ![Clique no link "n alertas encontrados"](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Clique no link "n alertas encontrados"](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endnote %} @@ -91,7 +91,7 @@ Há outras situações em que não pode haver análise para o último commit do Para verificar se um branch foi verificado, acesse a página {% data variables.product.prodname_code_scanning_capc %}, clique no menu suspenso **Branch** e selecione o branch relevante. - ![Escolha um branch no menu suspenso Branch](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Escolha um branch no menu suspenso Branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) A solução nesta situação é adicionar o nome do branch de base para a especificação `on:push` e `on:pull_request` no fluxo de trabalho de {% data variables.product.prodname_code_scanning %} nesse branch e, em seguida, fazer uma alteração que atualize o pull request aberto que você deseja escanear. 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 index 73c6c2efd3..ace4c04704 100644 --- 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 @@ -25,7 +25,7 @@ Uma licença de {% data variables.product.prodname_GH_advanced_security %} forne - **{% data variables.product.prodname_secret_scanning_caps %}** - Detectar segredos, por exemplo, chaves e tokens, que foram verificados no repositório. 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" %} -- **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." +- **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". {% endif %} Para obter informações sobre funcionalidades de {% data variables.product.prodname_advanced_security %} em desenvolvimento, consulte "[Plano de trabalho de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para uma visão geral de todas as funcionalidades de segurança, consulte "[Sobre como proteger seu repositório](/github/administering-a-repository/about-securing-your-repository#setting-up-your-repository-securely)". @@ -38,7 +38,7 @@ O administrador do site deve habilitar {% data variables.product.prodname_advanced_security %} para {% data variables.product.product_location %} antes de poder utilizar estas funcionalidades. Para obter mais informações, consulte "[Configurar funcionalidades avançadas de segurança](/admin/configuration/configuring-advanced-security-features)". {% endif %} -Após configurar o sistema, você poderá habilitar e desabilitar esses recursos no nível da organização ou repositório. Para mais informações, consulte "[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)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +Após configurar o sistema, você poderá habilitar e desabilitar esses recursos no nível da organização ou repositório. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)." {% endif %} @@ -47,7 +47,7 @@ Após configurar o sistema, você poderá habilitar e desabilitar esses recursos Para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}, Essas funcionalidades estão permanentemente habilitadas e só podem ser desabilitadas se você alterar a visibilidade do projeto para que o código não seja mais público. -Para outros repositórios, uma vez que você tenha uma licença da conta corporativa, é possível habilitar e desabilitar essas funcionalidades no nível da organização ou repositório. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Para obter mais informações, consulte "[Gerenciar as configurações de segurança e análise de sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} +Para outros repositórios, uma vez que você tenha uma licença da conta corporativa, é possível habilitar e desabilitar essas funcionalidades no nível da organização ou repositório. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)."{% endif %} {% endif %} 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 56bbc71e53..23ec8350ff 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 @@ -92,7 +92,7 @@ O {% data variables.product.prodname_ghe_cloud %} também inclui: - {% data variables.contact.enterprise_support %}. Para obter mais informações, consulte "{% data variables.product.prodname_ghe_cloud %} suporte" e "{% data variables.product.prodname_ghe_cloud %} Adendo" - 50.000 {% data variables.product.prodname_actions %} minutos - 50GB {% data variables.product.prodname_registry %} de armazenamento -- Controle de acesso para sites de {% data variables.product.prodname_pages %}. Para obter mais informações, consulte Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}" +- Controle de acesso para sites de {% data variables.product.prodname_pages %}. Para obter mais informações, consulte Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}" - Um acordo de nível de serviço para tempo de atividade de 99,9% por mês - A opção de gerenciar de forma centralizada a política e cobrança para várias organizações {% data variables.product.prodname_dotcom_the_website %} com uma conta corporativa. Para obter mais informações, consulte "Sobre contas corporativas". 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 2983f732dc..e4b007a6b8 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 @@ -1,6 +1,6 @@ --- -title: Keyboard shortcuts -intro: 'Nearly every page on {% data variables.product.product_name %} has a keyboard shortcut to perform actions faster.' +title: Atalhos de teclado +intro: 'Quase todas as páginas no {% data variables.product.product_name %} tem um atalho de teclado que executa as ações mais rapidamente.' redirect_from: - /articles/using-keyboard-shortcuts/ - /categories/75/articles/ @@ -13,186 +13,189 @@ versions: --- -### About keyboard shortcuts +### Sobre atalhos do teclado -Typing ? in {% data variables.product.product_name %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate. +Digitar ? no {% data variables.product.product_name %} exibe uma caixa de diálogo que lista os atalhos de teclado disponíveis para aquela página. Você pode usar esses atalhos de teclado para executar ações no site sem precisar usar o mouse para navegar. -Below is a list of some of the available keyboard shortcuts. +Veja abaixo uma lista dos atalhos de teclado disponíveis. -### Site wide shortcuts +### Atalhos para o site -| Keyboard shortcut | Description -|-----------|------------ -|s or / | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/articles/about-searching-on-github)." -|g n | Go to your notifications. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." -|esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in +| Atalho | Descrição | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| s or / | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/articles/about-searching-on-github)". | +| g n | Vai para suas notificações. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." | +| esc | Quando direcionado a um hovercard de usuário, problema ou pull request, fecha o hovercard e redireciona para o elemento no qual o hovercard está | -### Repositories +### Repositórios -| 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)." +| Atalho | Descrição | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| g c | Vai para a aba **Code** (Código) | +| g i | Vai para a aba **Issues** (Problemas). Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues)". | +| g p | Vai para a aba **Pull requests**. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| g a | Acesse a aba de **Ações**. Para obter mais informações, consulte "[Sobre ações](/actions/getting-started-with-github-actions/about-github-actions)".{% endif %} +| g b | Vai para a aba **Projects** (Projetos). Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". | +| g w | Vai para a aba **Wiki**. Para obter mais informações, consulte "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)". | -### Source code editing +### Edição de código-fonte -| Keyboard shortcut | Description -|-----------|------------ -|e | Open source code file in the **Edit file** tab -|control f or command f | Start searching in file editor -|control g or command g | Find next -|shift control g or shift command g | Find previous -|shift control f or command option f | Replace -|shift control r or shift command option f | Replace all -|alt g | Jump to line -|control z or command z | Undo -|control y or command y | Redo -|cmd + shift + p | Toggles between the **Edit file** and **Preview changes** tabs +| Atalho | Descrição | +| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | +| e | Abra o arquivo de código-fonte na aba **Editar arquivo** | +| control f ou command f | Começa a pesquisar no editor de arquivo | +| control g ou command g | Localiza o próximo | +| shift control g ou shift command g | Localiza o anterior | +| shift control f ou command option f | Substitui | +| shift control r ou shift command option f | Substitui todos | +| alt g | Pula para linha | +| control z ou command z | Desfaz | +| control y ou command y | Refaz | +| cmd + shift + p | Alterna entre as abas **Edit file** (Editar aquivo) e **Preview changes** (Visualizar alterações) | +| control s or command s | Write a commit message | -For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands). +Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://codemirror.net/doc/manual.html#commands). -### Source code browsing +### Navegação de código-fonte -| Keyboard shortcut | Description -|-----------|------------ -|t | Activates the file finder -|l | Jump to a line in your code -|w | Switch to a new branch or tag -|y | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)." -|i | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)." -|b | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)." +| Atalho | Descrição | +| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| t | Ativa o localizador de arquivos | +| l | Pula para uma linha no código | +| w | Muda para um novo branch ou tag | +| y | Expande a URL para sua forma canônica. Para obter mais informações, consulte "[Obter links permanentes em arquivos](/articles/getting-permanent-links-to-files)". | +| i | Mostra ou oculta comentários em diffs. Para obter mais informações, consulte "[Comentar no diff de uma pull request](/articles/commenting-on-the-diff-of-a-pull-request)". | +| a | Exibir ou ocultar anotações em diffs | +| b | Abre a vsualização de blame. Para obter mais informações, consulte "[Rastrear alterações em um arquivo](/articles/tracing-changes-in-a-file)". | -### Comments +### Comentários -| Keyboard shortcut | Description -|-----------|------------ -| control b or command b | Inserts Markdown formatting for bolding text -| control i or command i | Inserts Markdown formatting for italicizing text -| control k or command k | Inserts Markdown formatting for creating a link -| control shift p or command shift p| Toggles between the **Write** and **Preview** comment tabs -| control enter | Submits a comment -| control . and then control [saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} -|control g or command g | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} -| r | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | +| Atalho | Descrição | +| -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| control b ou command b | Insere formatação Markdown para texto em negrito | +| control i ou command i | Insere formatação Markdown para texto em itálico | +| control k ou command k | Insere formatação Markdown para criar um link | +| control shift p ou command shift p | Alterna entre as abas de comentários **Write** (Escrever) e **Preview** (Visualizar) | +| control enter | Envia um comentário | +| control . e control [número de resposta salvo] | Abre o menu de respostas salvas e autocompleta o campo de comentário com uma resposta salva. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} +| control g ou command g | Insere uma sugestão. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". +{% endif %} +| r | Cita o texto selecionado em sua resposta. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax#quoting-text)". | -### Issue and pull request lists +### Listas de problemas e pull requests -| Keyboard shortcut | Description -|-----------|------------ -|c | Create an issue -| control / or command / | Focus your cursor on the issues or pull requests search bar. For more information, see "[Using search to filter issues and pull requests](/articles/using-search-to-filter-issues-and-pull-requests)."|| -|u | Filter by author -|l | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." -| alt and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)." -|m | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)." -|a | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)." -|o or enter | Open issue +| Atalho | Descrição | +| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | Cria um problema | +| control / ou command / | Evidencia seu cursor na barra de pesquisa de problemas e pull requests. Para obter mais informações, consulte "[Usar a pesquisa para filtrar problemas e pull requests](/articles/using-search-to-filter-issues-and-pull-requests)".| | +| u | Filtra por autor | +| l | Filtra por ou edita etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| alt e clique | Ao filtrar por etiquetas, exclui etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| m | Filtra por ou edita marcos. Para obter mais informações, consulte "[Filtrar problemas e pull requests por marcos](/articles/filtering-issues-and-pull-requests-by-milestone)". | +| a | Filtra por ou edita um responsável. Para obter mais informações, consulte "[Filtrar problemas e pull requests por responsáveis](/articles/filtering-issues-and-pull-requests-by-assignees)". | +| o ou enter | Abre um problema | -### Issues and pull requests -| Keyboard shortcut | Description -|-----------|------------ -|q | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)." -|m | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)." -|l | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)." -|a | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)." -|cmd + shift + p or control + shift + p | Toggles between the **Write** and **Preview** tabs +### Problemas e pull requests +| Atalho | Descrição | +| ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| q | Solicita um revisor. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/articles/requesting-a-pull-request-review/)". | +| m | Define um marco. Para obter mais informações, consulte "[Associar marcos a problemas e pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)". | +| l | Aplica uma etiqueta. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests/)". | +| a | Define um responsável. Para obter mais informações, consulte "[Atribuir problemas e pull requests a outros usuários {% data variables.product.company_short %}](/articles/assigning-issues-and-pull-requests-to-other-github-users/)". | +| cmd + shift + p ou control + shift + p | Alterna entre as abas **Write** (Escrever) e **Preview** (Visualizar) | -### Changes in pull requests +### Alterações em pull requests -| Keyboard shortcut | Description -|-----------|------------ -|c | Open the list of commits in the pull request -|t | Open the list of changed files in the pull request -|j | Move selection down in the list -|k | Move selection up in the list -| cmd + shift + enter | Add a single comment on a pull request diff | -| alt and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down `alt` and clicking **Show outdated** or **Hide outdated**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| Click, then shift and click | Comment on multiple lines of a pull request by clicking a line number, holding shift, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} +| Atalho | Descrição | +| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | Abre a lista de commits na pull request | +| t | Abre a lista de arquivos alterados na pull request | +| j | Move a seleção para baixo na lista | +| k | Move a seleção para cima na lista | +| cmd + shift + enter | Adiciona um comentário único no diff da pull request | +| alt e clique | Alterna entre recolhimento e expansão de todos os comentários de revisão desatualizados em um pull request, mantendo pressionada a tecla `alt` e clicando em **Mostrar desatualizados** ou **Ocultar desatualizados**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| Clique, em seguida shift e clique | Comente em várias linhas de uma pull request clicando em um número de linha, mantendo pressionado shift, depois clique em outro número de linha. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." +{% endif %} -### Project boards +### Quadros de projeto -#### Moving a column +#### Mover uma coluna -| Keyboard shortcut | Description -|-----------|------------ -|enter or space | Start moving the focused column -|escape | Cancel the move in progress -|enter | Complete the move in progress -|← or h | Move column to the left -|command + ← or command + h or control + ← or control + h | Move column to the leftmost position -|→ or l | Move column to the right -|command + → or command + l or control + → or control + l | Move column to the rightmost position +| Atalho | Descrição | +| ---------------------------------------------------------------------------------------------------- | -------------------------------------------- | +| enter ou space | Começa a mover a coluna em evidência | +| escape | Cancela o movimento em curso | +| enter | Completa o movimento em curso | +| ← ou h | Move a coluna para a esquerda | +| command + ← ou command + h ou control + ← ou control + h | Move a coluna para a posição mais à esquerda | +| → ou l | Move a coluna para a direita | +| command + → ou command + l ou control + → ou control + l | Move a coluna para a posição mais à direita | -#### Moving a card +#### Mover um cartão -| Keyboard shortcut | Description -|-----------|------------ -|enter or space | Start moving the focused card -|escape | Cancel the move in progress -|enter | Complete the move in progress -|↓ or j | Move card down -|command + ↓ or command + j or control + ↓ or control + j | Move card to the bottom of the column -|↑ or k | Move card up -|command + ↑ or command + k or control + ↑ or control + k | Move card to the top of the column -|← or h | Move card to the bottom of the column on the left -|shift + ← or shift + h | Move card to the top of the column on the left -|command + ← or command + h or control + ← or control + h | Move card to the bottom of the leftmost column -|command + shift + ← or command + shift + h or control + shift + ← or control + shift + h | Move card to the top of the leftmost column -|→ | Move card to the bottom of the column on the right -|shift + → or shift + l | Move card to the top of the column on the right -|command + → or command + l or control + → or control + l | Move card to the bottom of the rightmost column -|command + shift + → or command + shift + l or control + shift + → or control + shift + l | Move card to the bottom of the rightmost column +| Atalho | Descrição | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | +| enter ou space | Começa a mover o cartão em evidência | +| escape | Cancela o movimento em curso | +| enter | Completa o movimento em curso | +| ↓ ou j | Move o cartão para baixo | +| command + ↓ ou command + j ou control + ↓ ou control + j | Move o cartão para a parte inferior da coluna | +| ↑ ou k | Move o cartão para cima | +| command + ↑ ou command + k ou control + ↑ ou control + k | Move o cartão para a parte superior da coluna | +| ← ou h | Move o cartão para a parte inferior da coluna à esquerda | +| shift + ← ou shift + h | Move o cartão para a parte superior da coluna à esquerda | +| command + ← ou command + h ou control + ← ou control + h | Move o cartão para a parte inferior da coluna mais à esquerda | +| command + shift + ← ou command + shift + h ou control + shift + ← ou control + shift + h | Move o cartão para a parte superior da coluna mais à esquerda | +| → | Move o cartão para a parte inferior da coluna à direita | +| shift + → ou shift + l | Move o cartão para a parte superior da coluna à direita | +| command + → ou command + l ou control + → ou control + l | Move o cartão para a parte inferior da coluna mais à direita | +| command + shift + → ou command + shift + l ou control + shift + → ou control + shift + l | Move o cartão para a parte inferior da coluna mais à direita | -#### Previewing a card +#### Pré-visualizar um cartão -| Keyboard shortcut | Description -|-----------|------------ -|esc | Close the card preview pane +| Atalho | Descrição | +| -------------- | ---------------------------------------- | +| esc | Fecha o painel de visualização do cartão | {% if currentVersion == "free-pro-team@latest" %} ### {% data variables.product.prodname_actions %} -| 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 +| Atalho | Descrição | +| --------------------------------------------------------- | ------------------------------------------------------------------------------------ | +| command + space ou control + space | No editor de fluxo de trabalho, obtém sugestões para o arquivo de fluxo de trabalho. | +| g f | Acesse o arquivo do fluxo de trabalho | +| shift + t or T | Alternar as marcas de tempo nos registros | +| shift + f ou F | Alternar os registros em tela cheia | +| esc | Sair dos registros em tela cheia | {% endif %} -### Notifications - +### Notificações {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| Keyboard shortcut | Description -|-----------|------------ -|e | Mark as done -| shift + u| Mark as unread -| shift + i| Mark as read -| shift + m | Unsubscribe +| Atalho | Descrição | +| -------------------- | -------------------- | +| e | Marcar como pronto | +| shift + u | Marcar como não lido | +| shift + i | Marca como lido | +| shift + m | Cancelar assinatura | {% else %} -| Keyboard shortcut | Description -|-----------|------------ -|e or I or y | Mark as read -|shift + m | Mute thread +| Atalho | Descrição | +| -------------------------------------------- | --------------- | +| e ou I ou y | Marca como lido | +| shift + m | Desativa o som | {% endif %} -### Network graph +### gráfico de rede -| Keyboard shortcut | Description -|-----------|------------ -|← or h | Scroll left -|→ or l | Scroll right -|↑ or k | Scroll up -|↓ or j | Scroll down -|shift + ← or shift + h | Scroll all the way left -|shift + → or shift + l | Scroll all the way right -|shift + ↑ or shift + k | Scroll all the way up -|shift + ↓ or shift + j | Scroll all the way down +| Atalho | Descrição | +| -------------------------------------------- | -------------------------------- | +| ← ou h | Rola para a esquerda | +| → ou l | Rola para a direita | +| ↑ ou k | Rola para cima | +| ↓ ou j | Rola para baixo | +| shift + ← ou shift + h | Rola até o final para a esquerda | +| shift + → ou shift + l | Rola até o final para a direita | +| shift + ↑ ou shift + k | Rola até o final para cima | +| shift + ↓ ou shift + j | Rola até o final para baixo | diff --git a/translations/pt-BR/content/github/index.md b/translations/pt-BR/content/github/index.md index ea86322b6d..127d526e06 100644 --- a/translations/pt-BR/content/github/index.md +++ b/translations/pt-BR/content/github/index.md @@ -4,7 +4,7 @@ redirect_from: - /articles/ - /common-issues-and-questions/ - /troubleshooting-common-issues/ -intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.' +intro: 'Documentação, guias e tópicos de ajuda para desenvolvedores de software, engenheiros e gerentes de projeto. O conteúdo abrange o uso do Git, pull requests, problemas, wikis, gists e todas as informações necessárias para aproveitar ao máximo os recursos de desenvolvimento do GitHub.' versions: free-pro-team: '*' enterprise-server: '*' @@ -23,9 +23,7 @@ versions: {% 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 %} @@ -33,8 +31,6 @@ versions: {% 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 %} @@ -42,8 +38,6 @@ versions: {% 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 %} @@ -51,9 +45,10 @@ versions: {% link_in_list /administering-a-repository %} {% link_in_list /visualizing-repository-data-with-graphs %} -{% link_in_list /managing-security-vulnerabilities %} -{% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} +{% if currentVersion == "enterprise-server@2.22" %} +{% link_in_list /managing-security-vulnerabilities %} +{% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %}{% endif %} {% link_in_list /managing-files-in-a-repository %} @@ -62,7 +57,6 @@ versions: {% 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 %} diff --git a/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md b/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md index b04c985005..d0e00cc297 100644 --- a/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md +++ b/translations/pt-BR/content/github/managing-large-files/conditions-for-large-files.md @@ -1,6 +1,6 @@ --- -title: Conditions for large files -intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories, and will block a push to a repository if the files are larger than the maximum file limit.' +title: Condições para arquivos grandes +intro: 'O {% data variables.product.product_name %} limita o tamanho dos arquivos permitidos nos repositórios e irá bloquear um push para um repositório se os arquivos forem maiores que o limite máximo de arquivos.' redirect_from: - /articles/conditions-for-large-files versions: @@ -11,10 +11,10 @@ versions: {% data reusables.large_files.use_lfs_tip %} -### Warning for files larger than {% data variables.large_files.warning_size %} +### Aviso para arquivos maiores que {% data variables.large_files.warning_size %} -If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](/github/managing-large-files/removing-files-from-a-repositorys-history)." +Se você tentar adicionar ou atualizar um arquivo maior do que {% data variables.large_files.warning_size %}, você receberá um aviso do Git. As alterações ainda serão carregadas no seu repositório com sucesso, mas você pode considerar remover o commit para minimizar o impacto no desempenho. Para obter mais informações, consulte "[Remover arquivos do histórico de um repositório](/github/managing-large-files/removing-files-from-a-repositorys-history)". -### Blocked pushes for large files +### Pushes bloqueados para arquivos grandes -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %} +{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}Por padrão, {% endif %}{% data variables.product.product_name %} bloqueia pushes que excedem {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %}No entanto, um administrador do site pode configurar um limite diferente para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Definir limites de push do Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 67f9613edb..018b4dd195 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -1,90 +1,99 @@ --- -title: About alerts for vulnerable dependencies -intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.' -redirect_from: - - /articles/about-security-alerts-for-vulnerable-dependencies - - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies +title: Sobre alertas para dependências vulneráveis +intro: '{% data variables.product.product_name %} envia {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} quando detectarmos vulnerabilidades que afetam o repositório.' versions: - free-pro-team: '*' - enterprise-server: '*' + enterprise-server: '<=2.22' +topics: + - segurança --- -### About vulnerable dependencies +### Sobre as dependências vulneráveis {% data reusables.repositories.a-vulnerability-is %} -When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it. +Quando o seu código depende de um pacote que tenha uma vulnerabilidade de segurança, essa dependência vulnerável pode causar uma série de problemas para o seu projeto ou para as pessoas que o usam. -### Detection of vulnerable dependencies +### Detecção de dependências vulneráveis - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %} detecta dependências vulneráveis e envia {% data variables.product.prodname_dependabot_alerts %} alertas{% else %}{% data variables.product.product_name %} detecta dependências vulneráveis e envia alertas de segurança{% endif %} quando: {% if currentVersion == "free-pro-team@latest" %} -- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)." -- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %} -- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}."{% endif %} -- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +- Uma nova vulnerabilidade foi adicionada ao {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança em {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)".{% else %} +- São sincronizados novos dados de consultoria com {% data variables.product.prodname_ghe_server %} a cada hora a partir de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre dados de consultoria, consulte "Procurar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}{% endif %} +- O gráfico de dependências para alterações de repositório. Por exemplo, quando um colaborador faz push de um commit para alterar os pacotes ou versões de que depende{% if currentVersion == "free-pro-team@latest" %} ou quando o código de uma das dependências muda{% endif %}. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". {% data reusables.repositories.dependency-review %} -For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +Para obter uma lista dos ecossistemas para os quais o {% data variables.product.product_name %} pode detectar vulnerabilidades e dependências, consulte "[Ecossistemas de pacotes compatíveis](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". {% note %} -**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use. +**Observação:** É importante manter seus manifestos atualizados e seu arquivos bloqueados. Se o gráfico de dependências não refletir corretamente suas dependências e versões atuais, você poderá perder alertas para dependências vulneráveis que você usar. Você também pode receber alertas de dependências que você já não usa. {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %} -### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies +### Alertas do {% data variables.product.prodname_dependabot %} para dependências vulneráveis {% else %} -### Security alerts for vulnerable dependencies +### Alertas de segurança para dependências vulneráveis {% endif %} {% data reusables.repositories.enable-security-alerts %} -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detecta dependências vulneráveis em repositórios _públicos_ e gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios pertencentes à sua conta de usuário ou organização. 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](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." -{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." + +{% data variables.product.product_name %} começa a gerar o gráfico de dependências imediatamente e gera alertas para quaisquer dependências vulneráveis assim que forem identificadas. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Para obter mais informações, consulte "[Gerenciando configurações do uso de dados de seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)". {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +Quando +{% data variables.product.product_name %} identifica uma dependência vulnerável, geramos um alerta {% data variables.product.prodname_dependabot %} e o exibimos na aba Segurança do repositório. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. {% data variables.product.product_name %} também notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". {% endif %} {% if currentVersion == "free-pro-team@latest" %} -For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +Para repositórios onde +{% data variables.product.prodname_dependabot_security_updates %} estão ativados, o alerta também pode conter um link para uma pull request para atualizar o manifesto ou arquivo de lock para a versão mínima que resolve a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. +Quando +{% data variables.product.product_name %} identifica uma dependência vulnerável, enviamos um alerta de segurança aos mantenedores dos repositórios afetados, com informações sobre a vulnerabilidade, um link para o arquivo afetado no projeto e informações sobre uma versão corrigida. {% endif %} {% warning %} -**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary. +**Observação**: Os recursos de segurança de {% data variables.product.product_name %} não reivindicam garantem que todas as vulnerabilidades sejam detectadas. Embora estejamos sempre tentando atualizar nosso banco de dados de vulnerabilidades e gerar alertas com nossas informações mais atualizadas. não seremos capazes de pegar tudo ou falar sobre vulnerabilidades conhecidas dentro de um período de tempo garantido. Esses recursos não substituem a revisão humana de cada dependência em busca de possíveis vulnerabilidades ou algum outro problema, e nossa sugestão é consultar um serviço de segurança ou realizar uma revisão completa de vulnerabilidade quando necessário. {% endwarning %} -### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts +### Acesso a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %} -You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +É possível ver todos os alertas que afetam um determinado projeto{% if currentVersion == "free-pro-team@latest" %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository){% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre novos +{% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. +Enviamos alertas de segurança para as pessoas com permissões de administrador nos repositórios afetados por padrão. +O {% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. {% endif %} -{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2. 1" %} Para mais informações, consulte "[Escolher o método de entrega para suas notificações](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" %} Para mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} {% if currentVersion == "free-pro-team@latest" %} -### Further reading +Você também pode ver todos os +{% data variables.product.prodname_dependabot_alerts %} que correspondem a uma vulnerabilidade particular em {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Pesquisar vulnerabilidades de segurança no {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)". +{% endif %} -- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +### Leia mais + +- "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" +- "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies.md index 4ed8371db5..265f162e73 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 @@ -13,7 +13,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}Quando {% data variables.product.prodname_dependabot %} detecta dependências vulneráveis nos seus repositórios, geramos um alerta {% data variables.product.prodname_dependabot %} e exibimo-lo na aba Segurança do repositório. {% data variables.product.product_name %} notifica os mantenedores dos repositórios afetados sobre o novo alerta de acordo com suas preferências de notificação.{% else %}Quando {% data variables.product.product_name %} detecta dependências vulneráveis no seu repositório, ele envia alertas de segurança.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} está habilitado por padrão em todos os repositórios públicos. Para {% data variables.product.prodname_dependabot_alerts %}, por padrão, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail, agrupado pela vulnerabilidade específica. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}Se você é proprietário de uma organização, você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios da sua organização com um clique. Você também pode definir se a detecção de dependências vulneráveis será habilitada ou desabilitada para repositórios recém-criados. 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)". +{% if currentVersion == "free-pro-team@latest" %}Se você é proprietário de uma organização, você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios da sua organização com um clique. Você também pode definir se a detecção de dependências vulneráveis será habilitada ou desabilitada para repositórios recém-criados. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/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" %} 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 1c4de9746f..67e9ccb190 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 @@ -66,7 +66,7 @@ As notificações de e-mail também permitem flexibilidade com os tipos de notif ### Sobre notificações de participação e inspeção -Quando você inspeciona um repositório, você assina atualizações de atividade nesse repositório. Da mesma forma, quando você inspeciona as discussões de uma equipe específica, você está inscrito em todas as atualizações de conversa na página daquela equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)". +Quando você inspeciona um repositório, você assina atualizações de atividade nesse repositório. Da mesma forma, quando você inspeciona as discussões de uma equipe específica, você está inscrito em todas as atualizações de conversa na página daquela equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)". Para ver repositórios que você está inspecionando, acesse a sua [página de inspeção](https://github.com/watching). Para obter mais informações, consulte "[Gerenciando assinaturas e notificações do GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} @@ -78,7 +78,7 @@ Você pode configurar as notificações para um repositório na página do repos #### Sobre as notificações personalizadas {% data reusables.notifications-v2.custom-notifications-beta %} É possível personalizar notificações para um repositório. Você pode optar, por exemplo, por receber notificações somente quando atualizações para um ou mais tipos de eventos (problemas, pull request, versões, discussões) ocorrerem dentro de um repositório ou ignorar todas as notificações de um repositório. -{% endif %} Para obter mais informações, consulte "[Visualizar suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)". +{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. #### 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. @@ -248,16 +248,15 @@ Você também pode agendar quando {% data variables.product.prodname_mobile %} e 1. No menu inferior, toque em **Perfil**. 2. Para ver suas configurações, clique em {% octicon "gear" aria-label="The Gear icon" %}. -3. Para atualizar as suas configurações de notificação, toque em **Notificações** e, em seguida, use os atalhos para habilitar ou desabilitar os seus tipos preferidos de notificações de push. -4. Opcionalmente, para agendar quando {% data variables.product.prodname_mobile %} enviará notificações para seu dispositivo móvel, toque em **Receber notificações**, use o **horário de trabalho personalizado**, e em seguida, escolha quando você gostaria de receber notificações de push. +3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications. +4. Opcionalmente, para agendar quando {% data variables.product.prodname_mobile %} enviará notificações de push para seu dispositivo móvel, toque em **Horas de Trabalho**, use o **horário de trabalho personalizado** e, em seguida, escolha quando você gostaria de receber notificações de push. ### Configurar as configurações de inspeção para um repositório individual com {% data variables.product.prodname_mobile %} É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. Você também pode optar por receber notificações apenas sobre {% if currentVersion == "free-pro-team@latest" %}certos tipos de eventos como problemas, pull requests, discussões (se habilitado para o repositório) e {% endif %}novas versões, ou ignorar completamente um repositório individual. -1. Em {% data variables.product.prodname_mobile %}, acesse a página principal do repositório. +1. No {% data variables.product.prodname_mobile %}, navegue até a página principal do repositório. 2. Toque em **Inspecionar**. ![O botão de inspecionar em {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-button.png) 3. Para escolher para quais atividades você recebe notificações, toque nas suas configurações de inspeção preferenciais. ![Manu suspenso de configurações de inspeção em {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-settings.png) -{% data reusables.notifications-v2.custom-notifications-beta %} {% endif %} 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 5e5c8949b4..6ad121421d 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" or currentVersion ver_gt "2.22" %} and mobile{% endif %}.' +title: Gerenciamento de notificações da sua caixa de entrada +intro: 'Use sua caixa de entrada para rastrear e sincronizar rapidamente as notificações nos e-mails{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "2.22" %} e dispositivos móveis{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -8,102 +8,104 @@ versions: free-pro-team: '*' enterprise-server: '>=2.21' github-ae: '*' +topics: + - notificações --- {% if enterpriseServerVersions contains currentVersion %} {% data reusables.mobile.ghes-release-phase %} {% endif %} -### About your inbox +### Sobre sua caixa de entrada {% 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)." +{% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obter mais informações, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". {% endif %} -To access your notifications inbox, in the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}. +Para acessar sua caixa de entrada de notificações, no canto superior direito de qualquer página, clique em {% octicon "bell" aria-label="The notifications bell" %}. - ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png) + ![Notificação indicando qualquer mensagem não lida](/assets/images/help/notifications/notifications_general_existence_indicator.png) -Your inbox shows all of the notifications that you haven't unsubscribed to or marked as **Done.** You can customize your inbox to best suit your workflow using filters, viewing all or just unread notifications, and grouping your notifications to get a quick overview. +Sua caixa de entrada mostra todas as notificações que você não cancelou sua inscrição ou marcou como **Concluído.** Você pode personalizar sua caixa de entrada para melhor se adequar ao seu fluxo de trabalho usando filtros, visualizando todas ou apenas notificações não lidas e agrupando suas notificações para obter uma visão geral. - ![inbox view](/assets/images/help/notifications-v2/inbox-view.png) + ![visualização da caixa de entrada](/assets/images/help/notifications-v2/inbox-view.png) -By default, your inbox will show read and unread notifications. To only see unread notifications, click **Unread** or use the `is:unread` query. +Por padrão, sua caixa de entrada mostrará notificações lidas e não lidas. Para ver apenas notificações não lidas, clique em **Não lidas** ou use a consulta `is:unread`. - ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png) + ![visualização da caixa de entrada não lida](/assets/images/help/notifications-v2/unread-inbox-view.png) -### Triaging options +### Opções de triagem -You have several options for triaging notifications from your inbox. +Você tem várias opções para fazer triagem de notificações a partir de sua caixa de entrada. -| Triaging option | Description | -|-----------------|-------------| -| Save | Saves your notification for later review. To save a notification, to the right of the notification, click {% octicon "bookmark" aria-label="The bookmark icon" %}.

Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day. | -| Done | Marks a notification as completed and removes the notification from your inbox. You can see all completed notifications by clicking **Done** in the sidebar or with the `is:done` query. Notifications marked as **Done** are saved for 5 months. -| Unsubscribe | Automatically removes the notification from your inbox and unsubscribes you from the conversation until you are @mentioned, a team you're on is @mentioned, or you're requested for review. -| Read | Marks a notification as read. To only view read notifications in your inbox, use the `is:read` query. This query doesn't include notifications marked as **Done**. -| Unread | Marks notification as unread. To only view unread notifications in your inbox, use the `is:unread` query. | +| Opções de triagem | Descrição | +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Salvar | Salva a sua notificação para revisão posterior. Para salvar uma notificação, à direita da notificação, clique em {% octicon "bookmark" aria-label="The bookmark icon" %}.

As notificações salvas são mantidas indefinidamente e podem ser vistas clicando em **Salvo** na barra lateral ou com a consulta `is:saved`. Se sua notificação salva tiver mais de 5 meses e tornar-se não salva, a notificação desaparecerá da sua caixa de entrada em um dia. | +| Concluído | Marca uma notificação como concluída e remove a notificação da sua caixa de entrada. Você pode ver todas as notificações concluídas clicando em **Concluido** na barra lateral ou com a consulta `is:done`. Notificações marcadas como **Concluídas** são salvas por 5 meses. | +| Cancelar assinatura | Remove automaticamente a notificação de sua caixa de entrada e cancela sua assinatura da conversa até que você seja @mencionado, uma equipe na qual você esteja seja @mencionada, ou você seja solicitado para revisão. | +| Leitura | Marca uma notificação como lida. Para ver apenas as notificações lidas na sua caixa de entrada, use a consulta `is:read`. Esta consulta não inclui notificações marcadas como **Concluído**. | +| Não lido | Marca uma notificação como não lida. Para ver apenas as notificações não lidas na sua caixa de entrada, use a consulta `is:read`. | -To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)." +Para ver os atalhos de teclado disponíveis, consulte "[Atalhos de teclado](/github/getting-started-with-github/keyboard-shortcuts#notifications)". -Before choosing a triage option, you can preview your notification's details first and investigate. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)." +Antes de escolher uma opção de triagem, primeiro você pode pré-visualizar os detalhes da sua notificação e investigar. Para obter mais informações, consulte “[Fazendo triagem de uma só notificação](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)". -### Triaging multiple notifications at the same time +### Fazer triagem de várias notificações ao mesmo tempo -To triage multiple notifications at once, select the relevant notifications and use the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down to choose a triage option. +Para fazer triagem de várias notificações de uma só vez, selecione as notificações relevantes e use o menu suspenso {% octicon "kebab-horizontal" aria-label="The edit icon" %} para escolher uma opção de triagem. -![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) +![Menu suspenso com opções de triagem e notificações selecionadas](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) -### Default notification filters +### Filtros de notificação padrão -By default, your inbox has filters for when you are assigned, participating in a thread, requested to review a pull request, or when your username is @mentioned directly or a team you're a member of is @mentioned. +Por padrão, sua caixa de entrada tem filtros para quando você é responsável, participa de um thread, é solicitado a rever uma pull request ou quando seu nome de usuário for @mencionado diretamente ou quando uma equipe da qual você é integrante é @mencionada. - ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png) + ![Filtros personalizados padrão](/assets/images/help/notifications-v2/default-filters.png) -### Customizing your inbox with custom filters +### Personalizando sua caixa de entrada com filtros personalizados -You can add up to 15 of your own custom filters. +Você pode adicionar até 15 dos seus próprios filtros personalizados. {% data reusables.notifications.access_notifications %} -2. To open the filter settings, in the left sidebar, next to "Filters", click {% octicon "gear" aria-label="The Gear icon" %}. +2. Para abrir as configurações de filtro, na barra lateral esquerda, próximo de "Filtros", clique em {% octicon "gear" aria-label="The Gear icon" %}. {% tip %} - **Tip:** You can quickly preview a filter's inbox results by creating a query in your inbox view and clicking **Save**, which opens the custom filter settings. + **Dica:** Você pode visualizar rapidamente os resultados da caixa de entrada de um filtro, criando uma consulta na sua caixa de entrada e clicando em **Salvar**, que abre as configurações de filtro personalizado. {% endtip %} -3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)." +3. Adicione um nome para seu filtro e uma consulta de filtro. Por exemplo, para ver apenas notificações para um repositório específico, é possível criar um filtro usando a consulta `repo:octocat/open-source-project-name reason:participating`. Você também pode adicionar emojis com um teclado de emojis nativo. Para obter uma lista de consultas de pesquisa compatíveis, consulte "[Consultas suportadas para filtros personalizados](#supported-queries-for-custom-filters)". - ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png) + ![Exemplo de filtro personalizado](/assets/images/help/notifications-v2/custom-filter-example.png) -4. Click **Create**. +4. Clique em **Criar**. -### Custom filter limitations +### Limitações de filtro personalizadas -Custom filters do not currently support: - - Full text search in your inbox, including searching for pull request or issue titles. - - Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests. - - Creating more than 15 custom filters. - - Changing the default filters or their order. - - Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`. +Filtros personalizados atualmente não suportam: + - Pesquisa de texto completo em sua caixa de entrada, incluindo busca de pull request ou títulos de problema. + - Distinguindo entre filtros de consulta `is:issue`, `is:pr` e `is:pull-request`. Essas consultas retornarão problemas e pull requests. + - Criando mais de 15 filtros personalizados. + - Alterando os filtros padrão ou sua ordenação. + - Pesquise a [exclusão](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) usando `NÃO` ou `-QUALIFICADOR`. -### Supported queries for custom filters +### Consultas suportadas para filtros personalizados -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:`{% if currentVersion == "free-pro-team@latest" %} - - Filter by notification author with `author:` - - Filter by organization with `org:`{% endif %} +Estes são os tipos de filtros que você pode usar: + - Filtrar por repositório com `repo:` + - Filtrar por tipo de discussão com `is:` + - Filtrar por motivo de notificação com `reason:`{% if currentVersion == "free-pro-team@latest" %} + - Filtrar por autor de notificação com `author:` + - Filtrar por organização com `org:`{% endif %} -#### Supported `repo:` queries +#### Consultas de `repo:` compatíveis -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. +Para adicionar um filtro de `repo:`, você deve incluir o proprietário do repositório na consulta: `repo:owner/repository`. Um proprietário é a organização ou o usuário que possui o ativo de {% data variables.product.prodname_dotcom %} que aciona a notificação. Por exemplo, `repo:octo-org/octo-repo` irá mostrar notificações acionadas no repositório octo-repo dentro da organização octo-org. -#### Supported `is:` queries +#### Consultas suportadas `is:` -To filter notifications for specific activity on {% data variables.product.product_name %}, you can use the `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% if currentVersion != "github-ae@latest" %}, and to only see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} security{% endif %} alerts, use `is:repository-vulnerability-alert`.{% endif %} +Para filtrar notificações para uma atividade específica no {% data variables.product.product_name %}, você pode usar a consulta `is`. Por exemplo, para ver apenas atualizações de convite do repositório, use `is:repository-invitation`{% if currentVersion != "github-ae@latest" %}, e para ver somente {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot %}{% else %} alertas de {% endif %} segurança, use `is:repository-vulnerability-alert`.{% endif %} - `is:check-suite` - `is:commit` @@ -117,64 +119,69 @@ To filter notifications for specific activity on {% data variables.product.produ - `is:discussions`{% endif %} {% if currentVersion != "github-ae@latest" %} -For information about reducing noise from notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +Para informações sobre a redução de ruído de notificações para +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". {% endif %} -You can also use the `is:` query to describe how the notification was triaged. +Você também pode usar a consulta `is:` para descrever como a notificação passou pela triagem. - `is:saved` - `is:done` - `is:unread` - `is:read` -#### Supported `reason:` queries +#### Consultas suportadas `reason:` -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)." +Para filtrar notificações por motivos pelos quais recebeu uma atualização, você pode usar a consulta `reason:`. Por exemplo, para ver notificações quando você (ou uma equipe da qual você participa) é solicitado a rever uma pull request, use `reason:review-requested`. Para obter mais informações, consulte "[Sobre notificações](/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. +| Consulta | Descrição | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | +| `reason:assign` | Quando houver uma atualização em um problema ou numa pull request que você tenha sido designado responsável. | +| `reason:author` | Quando você abriu uma pull request ou um problema e houve uma atualização ou novo comentário. | +| `reason:comment` | Quando você comentou em um problema, numa pull request ou numa discussão em equipe. | +| `reason:participating` | Quando você tiver comentado um problema, uma pull request ou numa discussão de equipe ou tiver sido @mencionado. | +| `reason:invitation` | Quando você for convidado para uma equipe, organização ou repositório. | +| `reason:manual` | Quando você clicar em **Assinar** em um problema ou uma pull request que você ainda não estava inscrito. | +| `reason:mention` | Você foi @mencionado diretamente. | +| `reason:review-requested` | Foi solicitado que você ou uma equipe revise um um pull request.{% if currentVersion != "github-ae@latest" %} +| `reason:security-alert` | Quando um alerta de segurança é emitido para um repositório.{% endif %} +| `reason:state-change` | Quando o estado de uma pull request ou um problema é alterado. Por exemplo, um problema é fechado ou uma pull request é mesclada. | +| `reason:team-mention` | Quando uma equipe da qual você é integrante é @mencionada. | +| `reason:ci-activity` | Quando um repositório tem uma atualização de CI, como um novo status de execução de fluxo de trabalho. | {% if currentVersion == "free-pro-team@latest" %} -#### Supported `author:` queries +#### Consultas de `author:` compatíveis -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`. +Para filtrar as notificações por usuário, você pode usar a consulta de `author:`. Um autor é o autor original da corrente (problema, pull request, discussões gist, e assim por diante) referente ao qual você está sendo notificado. Por exemplo, para visualizar notificações referentes a tópicos criados pelo usuário do Octocat use `author:octocat`. -#### Supported `org:` queries +#### Consultas `org:` compatíveis -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. +Para filtrar notificações por organização, você pode usar a consulta `org`. A organização que você precisa especificar na consulta é a organização do repositório, para a qual você está sendo notificado em {% data variables.product.prodname_dotcom %}. Esta consulta é útil se você pertencer a várias organizações e desejar ver as notificações para uma organização específica. -For example, to see notifications from the octo-org organization, use `org:octo-org`. +Por exemplo, para ver notificações da organização octo-org, 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 +### Filtros personalizados de {% data variables.product.prodname_dependabot %} {% 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. +Se você usar +{% data variables.product.prodname_dependabot %} para manter suas dependências atualizadas, você poderá usar e salvar estes filtros personalizados: +- `is:repository_vulnerability_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %} e pull requests das atualizações de segurança. +- `author:app/dependabot` para mostrar as notificações geradas por {% data variables.product.prodname_dependabot %}. Isto inclui {% data variables.product.prodname_dependabot_alerts %}, pull requests para atualizações de segurança e pull requests para atualizações de versão. +Para mais informações sobre -For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." +{% data variables.product.prodname_dependabot %}, consulte "[Sobre o gerenciamento de dependências vulneráveis](/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 %}. +Se você usar +{% data variables.product.prodname_dependabot %} para manter suas dependências atualizadas, você pode usar e salvar o filtro personalizado `é:repository_vulnerability_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %}. +Para mais informações sobre -For more information about {% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +{% data variables.product.prodname_dependabot %}, consulte "[Sobre alertas para dependências vulneráveis](/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/viewing-your-subscriptions.md b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index d23d0c1500..e859617bbb 100644 --- a/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/pt-BR/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -38,7 +38,7 @@ Para ter uma visão geral das assinaturas de seu repositório, consulte "[Revisa {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Dica:** Você pode selecionar os tipos de evento a serem notificados utilizando a opção **Personalizar** na lista suspensa **Inspecionar/Cancelar inspeção** na sua [página](https://github.com/watching) ou em qualquer página de repositório em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Definir as suas configurações de inspeção para um repositório individual](#configuring-your-watch-settings-for-an-individual-repository) abaixo. +**Dica:** Você pode selecionar os tipos de evento a serem notificados utilizando a opção **Personalizar** na lista suspensa **Inspecionar/Cancelar inspeção** na sua [página](https://github.com/watching) ou em qualquer página de repositório em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". {% endtip %} {% 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 273387a467..11cb49b260 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 @@ -1,6 +1,6 @@ --- -title: About issues -intro: 'Use issues to track ideas, enhancements, tasks, or bugs for work on {% data variables.product.product_name %}.' +title: Sobre problemas +intro: 'Use problemas para rastrear ideias, aprimoramentos, tarefas ou erros para trabalhar no {% data variables.product.product_name %}.' redirect_from: - /articles/creating-issues/ - /articles/about-issues/ @@ -8,31 +8,35 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - Pull requests --- -### About issues +### Sobre problemas -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. +Você pode coletar feedback, reportar erros de software e organizar tarefas que deseja realizar com problemas em um repositório. Os problemas podem ser mais do que um lugar para relatar erros de relatório. -Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} +{% if currentVersion == "free-pro-team@latest" %} +Outras conversas são mais adequadas para discussões. {% data reusables.discussions.you-can-use-discussions %} {% data reusables.discussions.you-cannot-convert-a-discussion %} +{% endif %} {% data reusables.pull_requests.close-issues-using-keywords %} -To stay updated on the most recent comments in an issue, you can watch an issue to receive notifications about the latest comments. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +Para se manter atualizado sobre os comentários mais recentes em um problema, você pode inspecionar um problema a fim de recebe notificações sobre os últimos comentários. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." -To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)." +Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)". -### Working with issues +### Trabalhar com problemas -With issues, you can: -- Track and prioritize your work using project boards. For more information, see "[Using project boards](/articles/about-project-boards)." -- Create new issues to track out-of-scope feedback from a comment in an issue or a pull request review. For more information, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." -- Create issue templates to help contributors open meaningful issues. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." -- Transfer open issues to other repositories. For more information, see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)." -- Pin important issues to make them easier to find, preventing duplicate issues and reducing noise. For more information, see "[Pinning an issue to your repository](/articles/pinning-an-issue-to-your-repository)." -- Track duplicate issues using saved replies. For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} -- Report comments that violate {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/articles/github-community-guidelines). For more information, see "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)."{% endif %} +Com problemas, você pode: +- Acompanhar e priorizar seu trabalho usando quadros de projeto. Para obter mais informações, consulte "[Usar quadros de projeto](/articles/about-project-boards)". +- Criar novos problemas para rastrear feedbacks fora do escopo a partir de um comentário em um problema ou de uma revisão de pull request. Para obter mais informações, consulte "[Abrir um problema a partir de um comentário](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". +- Criar modelos de problema para ajudar os contribuidores a abrir problemas significativos. Para obter mais informações, consulte "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)". +- Transferir problemas abertos para outros repositórios. Para obter mais informações, consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)". +- Fixar problemas importantes para que seja mais fácil encontrá-los, evitando a duplicação de problemas e reduzindo ruídos. Para obter mais informações, consulte "[Fixar um problema no seu repositório](/articles/pinning-an-issue-to-your-repository)". +- Acompanhar problemas duplicados usando respostas salvas. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} +- Relatar comentários que violam as [Diretrizes da comunidade](/articles/github-community-guidelines) do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Relatar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)".{% endif %} -Issues can also be [assigned to other users](/articles/assigning-issues-and-pull-requests-to-other-github-users), [tagged with labels](/articles/applying-labels-to-issues-and-pull-requests) for quicker searching, and [grouped together with milestones](/articles/creating-and-editing-milestones-for-issues-and-pull-requests). +Os problemas também podem ser [atribuídos a outros usuários](/articles/assigning-issues-and-pull-requests-to-other-github-users), [marcados com etiquetas](/articles/applying-labels-to-issues-and-pull-requests) para pesquisa mais rápida e [agrupados com marcos](/articles/creating-and-editing-milestones-for-issues-and-pull-requests). diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md index e99658d64f..3995259615 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.md @@ -1,6 +1,6 @@ --- -title: Linking a pull request to an issue -intro: 'You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when the pull request is merged.' +title: Vinculando uma pull request a um problema +intro: Você pode vincular um pull request a um problema para mostrar que uma correção está em andamento e para fechar automaticamente o problema quando o pull request for mesclado. redirect_from: - /articles/closing-issues-via-commit-message/ - /articles/closing-issues-via-commit-messages/ @@ -10,41 +10,41 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - Pull requests --- {% 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.** +**Observação:** As palavras-chave especiais na descrição de um pull request são interpretadas quando o pull request aponta para o branch-padrão do *repositório*. No entanto, se a base do PR's for *qualquer outro branch*, essas palavras-chave serão ignoradas, nenhum link será criado e o merge do PR não terá efeito sobre os problemas. **Se você deseja vincular um pull request a um problema usando uma palavra-chave, o PR deverá estar no branch-padrão.** {% endnote %} -### About linked issues and pull requests +### Sobre problemas e pull requests vinculados -You can link an issue to a pull request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}manually or {% endif %}using a supported keyword in the pull request description. +Você pode vincular um problema a um pull request {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}manualmente ou {% endif %}usando uma palavra-chave compatível na descrição do pull request. -When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue. {% 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 %} +Quando você vincula uma pull request ao problema que a pull request tem de lidar, os colaboradores poderão ver que alguém está trabalhando no problema. {% if currentVersion ver_lt "enterprise-server@2. 1" %}Se o pull request e o problema estiverem em repositórios diferentes, {% data variables.product.product_name %} mostrará o link após o merge do pull request, se a pessoa que mescla o pull request também tiver permissão para fechar o problema.{% endif %} -When you merge a linked pull request into the default branch of a repository, its linked issue is automatically closed. For more information about the default branch, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +Quando você mescla uma pull request vinculada no branch padrão de um repositório, o problema vinculado será fechado automaticamente. Para obter mais informações sobre o branch padrão, consulte "[Configurado o branch padrão](/github/administering-a-repository/setting-the-default-branch). " {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -### Manually linking a pull request to an issue +### Vinculando manualmente uma pull request a um problema -Anyone with write permissions to a repository can manually link a pull request to an issue. +Qualquer pessoa com permissões de gravação em um repositório pode vincular manualmente uma pull request a um problema. -You can manually link up to ten issues to each pull request. The issue and pull request must be in the same repository. +Você pode vincular manualmente até dez problemas para cada pull request. O problema e a pull request devem estar no mesmo repositório. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -3. In the list of pull requests, click the pull request that you'd like to link to an issue. -4. In the right sidebar, click **Linked issues**. - ![Linked issues in the right sidebar](/assets/images/help/pull_requests/linked-issues.png) -5. Click the issue you want to link to the pull request. - ![Drop down to link issue](/assets/images/help/pull_requests/link-issue-drop-down.png) +3. Na lista de pull requests, clique na pull request que você gostaria de vincular a um problema. +4. Na barra lateral direita, clique em **Linked issues** (Problemas vinculados) ![Problemas vinculados na barra lateral direita](/assets/images/help/pull_requests/linked-issues.png) +5. Clique no problema que você deseja associar à pull request. ![Menu suspenso para problemas vinculados](/assets/images/help/pull_requests/link-issue-drop-down.png) {% endif %} -### Linking a pull request to an issue using a keyword +### Vinculando uma pull request a um problema usando uma palavra-chave -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). +Você pode vincular uma solicitação de pull a um problema usando uma palavra-chave compatível na descrição do pull request ou em uma mensagem de commit (observe que a solicitação do pull deve estar no branch-padrão). * close * closes @@ -53,21 +53,21 @@ You can link a pull request to an issue by using a supported keyword in the pull * fixes * fixed * resolve -* resolves +* resolve * resolved -The syntax for closing keywords depends on whether the issue is in the same repository as the pull request. +A sintaxe para fechar palavras-chave depende se o problema está no mesmo repositório que a pull request. -Linked issue | Syntax | Example ---------------- | ------ | ------ -Issue in the same repository | *KEYWORD* #*ISSUE-NUMBER* | `Closes #10` -Issue in a different repository | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` -Multiple issues | Use full syntax for each issue | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` +| Problemas vinculado | Sintaxe | Exemplo | +| ------------------------------------ | --------------------------------------------- | -------------------------------------------------------------- | +| Problema no mesmo repositório | *KEYWORD* #*ISSUE-NUMBER* | `Closes #10` | +| Problema em um repositório diferente | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | +| Múltiplos problemas | Usar sintaxe completa para cada problema | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}Apenas pull requests vinculados manualmente podem ser desvinculados. Para desvincular um problema que você vinculou usando uma palavra-chave, você deve editar a descrição da pull request para remover a palavra-chave.{% endif %} -You can also use closing keywords in a commit message. 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. +Você também pode usar palavras-chave de fechamento em uma mensagem de commit. O problema será encerrado quando você mesclar o commit no branch padrão, mas o pull request que contém o commit não será listado como um pull request vinculado. -### Further reading +### Leia mais -- "[Autolinked references and URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)" +- "[Referências autovinculadas e URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)" 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 305bb5a45e..ae70f285de 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 @@ -1,6 +1,6 @@ --- -title: Managing labels -intro: 'You can classify issues and pull requests by creating, editing, applying, and deleting labels.' +title: Gerenciar etiquetas +intro: 'Você pode classificar problemas e pull requests criando, editando, aplicando e excluindo etiquetas.' redirect_from: - /articles/managing-Labels - /articles/labeling-issues-and-pull-requests @@ -21,58 +21,59 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - Pull requests --- -### About labels +### Sobre etiquetas -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. +Você pode gerenciar seu trabalho no {% data variables.product.product_name %} criando etiquetas para classificar problemas e pull requests. Você pode aplicar etiquetas no repositório em que foram criadas. Uma vez criada a etiqueta, você poderá usá-la em qualquer problema ou pull request desse repositório. -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. +Qualquer pessoa com acesso de leitura a um repositório pode exibir e pesquisar etiquetas do repositório. Qualquer pessoa com acesso de triagem a um repositório pode aplicar/ignorar etiquetas existentes. Para criar, editar, aplicar ou excluir uma etiqueta, é preciso ter acesso de gravação ao repositório. -### About default labels +### Sobre as etiquetas padrão -{% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository. +O {% data variables.product.product_name %} fornece etiquetas padrão para todos os repositórios novos. Você pode usar essas etiquetas padrão para ajudar com a criação de um fluxo de trabalho padronizado em um repositório. -Label | Description ---- | --- -`bug` | Indicates an unexpected problem or unintended behavior{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -`documentation` | Indicates a need for improvements or additions to documentation{% endif %} -`duplicate` | Indicates similar issues or pull requests -`enhancement` | Indicates new feature requests -`good first issue` | Indicates a good issue for first-time contributors -`help wanted` | Indicates that a maintainer wants help on an issue or pull request -`invalid` | Indicates that an issue or pull request is no longer relevant -`question` | Indicates that an issue or pull request needs more information -`wontfix` | Indicates that work won't continue on an issue or pull request +| Etiqueta | Descrição | +| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bug` | Indica um problema inesperado ou um comportamento não intencional{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} +| `documentation` | Indica a necessidade de aprimoramentos ou adições à documentação{% endif %} +| `duplicate` | Indica problemas ou pull requests semelhantes | +| `enhancement` | Indica novas solicitações de recurso | +| `good first issue` | Indica um bom problema para contribuidores principiantes | +| `help wanted` | Indica que um mantenedor deseja ajudar em um problema ou uma pull request | +| `invalid` | Indica que um problema ou uma pull request não é mais relevante | +| `question` | Indica que um problema ou uma pull request precisa de mais informações | +| `wontfix` | Indica que o trabalho não continuará em um problema ou uma pull request | -Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later. +Etiquetas padrão são incluídas em todos os novos repositórios quando criados, mas você pode editar ou excluir as etiquetas posteriormente. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -Organization owners can customize the default labels for repositories in their organization. For more information, see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)." +Os proprietários da organização podem personalizar as etiquetas padrão para repositórios na organização. Para obter mais informações, consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)". {% endif %} -### Creating a label +### Criar uma etiqueta {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} -4. To the right of the search field, click **New label**. +4. À direita do campo de pesquisa, clique em **New label** (Nova etiqueta). {% data reusables.project-management.name-label %} {% data reusables.project-management.label-description %} {% data reusables.project-management.label-color-randomizer %} {% data reusables.project-management.create-label %} -### Applying labels to issues and pull requests +### Aplicar etiquetas a problemas e pull requests {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.repositories.select-items-in-issue-or-pr-list %} -4. In the upper-right corner, click **Label**, then start typing the name of an existing label. Click the label's name to associate it with the selected items. - ![Issues Milestone assignment drop-down](/assets/images/help/issues/issues_applying_labels_dropdown.png) +4. No canto superior direito, clique em **Label** (Etiqueta) e comece a digitar o nome de uma etiqueta existente. Clique no nome da etiqueta para associá-la aos itens selecionados. ![Menu suspenso atribuição Marco Problemas](/assets/images/help/issues/issues_applying_labels_dropdown.png) -### Editing a label +### Editar uma etiqueta {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -83,16 +84,15 @@ Organization owners can customize the default labels for repositories in their o {% data reusables.project-management.label-color-randomizer %} {% data reusables.project-management.save-label %} -### Deleting a label -Deleting a label will remove the label from issues and pull requests. +### Excluir uma etiqueta +Excluir uma etiqueta removerá a etiqueta dos problemas e pull requests. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} {% data reusables.project-management.delete-label %} -### 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 %} +### Leia mais +- "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" ou enterpriseServerVersions contém currentVersion %} +- "[Gerenciar etiquetas padrão para repositórios na organização](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% if currentVersion == "free-pro-team@latest" %} +- "[Incentivar contribuições úteis para o seu projeto com etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md b/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md index 64920e0815..a0d88adc12 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/transferring-an-issue-to-another-repository.md @@ -1,36 +1,35 @@ --- -title: Transferring an issue to another repository -intro: 'To move an issue to a better fitting repository, you can transfer open issues to other repositories.' +title: Transferir um problema para outro repositório +intro: 'Para mover um problema para um repositório mais adequado, você pode transferir problemas abertos para outros repositórios.' redirect_from: - /articles/transferring-an-issue-to-another-repository versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - Pull requests --- -To transfer an open issue to another repository, you must have write permissions on the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." +Para transferir um problema aberto para outro repositório, é preciso ter permissões de gravação no repositório em que o problema está e no repositório para onde você está transferindo o problema. Para obter mais informações, consulte "[Níveis de permissão do repositório para organizações](/articles/repository-permission-levels-for-an-organization)". -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 %} +Você somente pode transferir problemas entre repositórios pertencentes à mesma conta de usuário ou organização. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contém currentVersion %}Você não pode transferir um problema de um repositório privado para um repositório público.{% endif %} -When you transfer an issue, comments and assignees are retained. 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. For more information, see "[About project boards](/articles/about-project-boards)." +Quando você transfere um problema, os comentários e responsáveis são mantidos. As etiquetas e os marcos do problema não são retidos. Esse problema permanecerá em qualquer quadro de projeto pertencente ao usuário ou à organização e será removido dos quadros de projeto de todos os repositórios. Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". -People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access. +As pessoas ou equipes mencionadas no problema receberão uma notificação informando que o problema foi transferido para um novo repositório. O URL original redirecionará para o novo URL do problema. As pessoas que não tenham permissões de leitura no novo repositório verão um banner informando que o problema foi transferido para um novo repositório ao qual elas não têm acesso. -### Transferring an open issue to another repository +### Transferir um problema aberto para outro repositório {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} -3. In the list of issues, click the issue you'd like to transfer. -4. In the right sidebar, click **Transfer issue**. -![Button to transfer issue](/assets/images/help/repository/transfer-issue.png) -5. Use the **Choose a repository** drop-down menu, and select the repository you want to transfer the issue to. -![Choose a repository selection](/assets/images/help/repository/choose-a-repository.png) -6. Click **Transfer issue**. -![Transfer issue button](/assets/images/help/repository/transfer-issue-button.png) +3. Na lista de problemas, clique no problema que deseja transferir. +4. Na barra lateral direita, clique em **Transfer issue** (Transferir problema). ![Botão para transferir problema](/assets/images/help/repository/transfer-issue.png) +5. Use o menu **Choose a repository** (Escolher um repositório) e selecione o repositório para o qual deseja transferir o problema. ![Seleção em Choose a repository (Escolher um repositório)](/assets/images/help/repository/choose-a-repository.png) +6. Clique em **Transfer issue** (Transferir problema). ![Botão Transfer issue (Transferir problema)](/assets/images/help/repository/transfer-issue-button.png) -### Further reading +### Leia mais -- "[About issues](/articles/about-issues)" -- "[Reviewing your security log](/articles/reviewing-your-security-log)" -- "[Reviewing the audit log for your organization](/articles/reviewing-the-audit-log-for-your-organization)" +- "[Sobre problemas](/articles/about-issues)" +- "[Revisar o log de segurança](/articles/reviewing-your-security-log)" +- "[Revisar o log de auditoria da organização](/articles/reviewing-the-audit-log-for-your-organization)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md index 6bdd6564dc..82f4e388a1 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md @@ -19,14 +19,14 @@ Ao fazer o downgrade ou cancelar um patrocínio, a alteração entrará em vigor {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Cancelar um patrocínio {% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} +{% data reusables.user_settings.billing_plans %} {% data reusables.sponsors.billing-switcher %} -{% data reusables.user_settings.subscriptions-tab %} 3. Em "{% data variables.product.prodname_sponsors %}", à direita de um colaborador de código aberto patrocinado, clique em {% octicon "triangle-down" aria-label="The down triangle octicon" %} ao lado do seu valor patrocinado e depois clique em **Cancel sponsorship** (Cancelar patrocínio). ![Botão Cancel sponsorship (Cancelar patrocínio)](/assets/images/help/billing/edit-sponsor-billing.png) 4. Revise as informações sobre cancelamento do patrocínio e clique em **OK**. ![Caixa Cancellation confirmation (Confirmação de cancelamento)](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md index fe1bac9f30..2f2e98546b 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md @@ -14,6 +14,8 @@ topics: O {% data variables.product.product_name %} não poderá efetuar um reembolso se uma conta for paga antes da aplicação de um cupom. Também não poderemos transferir um cupom resgatado ou fornecer um novo cupom se você aplicar o cupom na conta errada. Verifique se você está aplicando o cupom na conta correta antes de resgatá-lo. +{% data reusables.dotcom_billing.coupon-expires %} + Não é possível aplicar cupons em planos pagos para apps {% data variables.product.prodname_marketplace %}. ### Resgatar um cupom na conta pessoal diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md index d7ded63f2e..a54313cac8 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md @@ -15,6 +15,8 @@ topics: Se estiver pagando a assinatura do {% data variables.product.product_name %} com um cupom e não estiver usando a forma de pagamento para qualquer outro [recurso ou produto pago](/articles/about-billing-on-github) no {% data variables.product.product_name %}, você poderá remover as informações do cartão de crédito ou do PayPal. +{% data reusables.dotcom_billing.coupon-expires %} + {% tip %} **Dica:** se você [fizer downgrade da conta para um produto grátis](/articles/downgrading-your-github-subscription) e não tiver assinaturas de outros recursos ou produtos pagos, removeremos automaticamente suas informações de pagamento. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md index abad730195..40b474a5b6 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md @@ -19,5 +19,6 @@ Quando você atualiza a camada do patrocínio, a alteração entra em vigor imed {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md index 3e10b9752e..9a2995e6ae 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -59,7 +59,7 @@ Você pode atualizar sua organização de {% data variables.product.prodname_fre #### Próximas etapas para organizações que usam o {% data variables.product.prodname_ghe_cloud %} -Se você tiver atualizado sua organização para o {% data variables.product.prodname_ghe_cloud %}, você poderá configurar a identidade e a gestão de acesso para a sua organização. For more information, see "[Gerenciar logon único de SAML para sua organização](/articles/managing-saml-single-sign-on-for-your-organization)". +Se você tiver atualizado sua organização para o {% data variables.product.prodname_ghe_cloud %}, você poderá configurar a identidade e a gestão de acesso para a sua organização. For more information, see "[Gerenciar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization)". Caso queira usar uma conta corporativa com o {% data variables.product.prodname_ghe_cloud %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações, consulte "[Sobre contas corporativas](/articles/about-enterprise-accounts)". diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md index 82c804a870..21a65b15f8 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md @@ -20,5 +20,5 @@ Você pode verificar quantas estações a sua licença inclui e quantas delas s A seção "{% data variables.product.prodname_GH_advanced_security %}" mostra os detalhes do uso atual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Se você ficar sem estações, a seção ficará vermelha. Você deve quer reduzir o seu uso de {% data variables.product.prodname_GH_advanced_security %} ou comprar mais estações. Para obter mais informações, consulte "[Sobre licenciamento para licença corporativa de {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)". ![{% data variables.product.prodname_GH_advanced_security %} em configurações de licenciamento corporativo](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. Opcionalmente, para ver uma análise detalhada do uso por organização, clique em **Cobrança**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) Na seção "{% data variables.product.prodname_GH_advanced_security %}", você pode ver o número de committers e committers únicos para cada organização. ![{% data variables.product.prodname_GH_advanced_security %} em configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise.png) 5. Opcionalmente, clique no nome de uma organização em que você é um proprietário para exibir as configurações de segurança e análise para a organização. ![Organização proprietária na seção de {% data variables.product.prodname_GH_advanced_security %} das configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. Na página de configurações "Análise de & segurança" desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}" para ver uma descrição detalhada do uso por repositório para esta organização. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". +6. Na página de configurações "Análise de & segurança" desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}" para ver uma descrição detalhada do uso por repositório para esta organização. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". 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 index 5c8fb356c7..c59027b168 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### Sobre o logon único SAML para contas corporativas -{% 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.dotcom-saml-explanation %} Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". {% data reusables.saml.about-saml-enterprise-accounts %} 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 43459ceac2..f93ff5a823 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 @@ -49,7 +49,7 @@ Os proprietários de empresas podem restringir o acesso a ativos pertencentes a {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -Você também pode configurar endereços IP permitidos para uma organização individual. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)". +Você também pode configurar endereços IP permitidos para uma organização individual. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)". #### Adicionar endereços IP permitidos diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md index 6097215750..0a9cebac30 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md @@ -15,7 +15,7 @@ topics: ### Aplicar política para discussões de equipe -Em todas as organizações pertencentes à conta corporativa, é possível habilitar ou desabilitar discussões de equipe ou permitir que os proprietários administrem a configuração no nível da organização. Para obter mais informações, consulte "[Sobre discussões de equipe](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)". +Em todas as organizações pertencentes à conta corporativa, é possível habilitar ou desabilitar discussões de equipe ou permitir que os proprietários administrem a configuração no nível da organização. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions/)". {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 3a98ae2494..99d5e67c61 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 @@ -39,7 +39,7 @@ Os proprietários da organização podem convidar novos integrantes para uma org Embora não seja necessário, recomendamos que os proprietários da organização enviem um convite para o mesmo endereço de e-mail usado para o Nome Principal do Usuário (UPN) do assinante de {% data variables.product.prodname_vs %}. Quando o endereço de e-mail em {% data variables.product.product_name %} corresponder ao UPN do assinante, você poderá garantir que outro integrante da organização não reivindique a licença do assinante. -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), "[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)". +Para obter mais informações, consulte "[Convidar usuários para participar da sua organização](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization), "[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)". ### 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 index a61c71cf04..c8a65acec5 100644 --- 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 @@ -19,7 +19,7 @@ Se você usar o Azure AD como seu IdP, você pode habilitar a sincronização de {% 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)". +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](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". ### Pré-requisitos diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md index bbf99cd660..88004fc439 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -11,7 +11,7 @@ topics: ### Sobre restrições de e-mail para a sua conta corporativa -Ao restringir notificações de e-mail para domínios verificados, os integrantes da empresa só poderão usar um endereço de e-mail associado a um domínio verificado para receber notificações de e-mail sobre a atividade em organizações pertencentes à sua conta corporativa. Os domínios podem ser herdados da conta corporativa ou configurados para a organização específica. Para obter mais informações sobre restrições de e-mail para organizações, consulte "[Restringir notificações de e-mail para um domínio aprovado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)". +Ao restringir notificações de e-mail para domínios verificados, os integrantes da empresa só poderão usar um endereço de e-mail associado a um domínio verificado para receber notificações de e-mail sobre a atividade em organizações pertencentes à sua conta corporativa. Os domínios podem ser herdados da conta corporativa ou configurados para a organização específica. Para obter mais informações sobre restrições de e-mail para organizações, consulte "[Restringir notificações de e-mail para um domínio aprovado](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)". Se restrições de e-mail estiverem habilitadas para uma conta corporativa, os proprietários da organização não poderão desabilitar restrições de e-mail para qualquer organização que pertence à conta corporativa. Se ocorrerem alterações que resultem em uma organização não ter domínios verificados, herdado de uma conta corporativa pertencente à organização ou para uma organização específica, as restrições de e-mail serão desabilitadas para a organização. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md index e2cde4adea..091b20b28a 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -14,7 +14,7 @@ topics: ### Sobre a verificação do domínio -Você pode confirmar que os sites e endereços de e-mail listados nos perfis de qualquer organização pertencente à sua conta corporativa são controlados pela sua empresa verificando os domínios. Os domínios verificados para uma conta corporativa aplicam-se a todas as organizações pertencentes à conta corporativa, e os proprietários da organização podem verificar domínios adicionais para suas organizações. Par obter mais informações, consulte "[Verificar o domínio da sua organização](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." +Você pode confirmar que os sites e endereços de e-mail listados nos perfis de qualquer organização pertencente à sua conta corporativa são controlados pela sua empresa verificando os domínios. Os domínios verificados para uma conta corporativa aplicam-se a todas as organizações pertencentes à conta corporativa, e os proprietários da organização podem verificar domínios adicionais para suas organizações. Par obter mais informações, consulte "[Verificar o domínio da sua organização](/organizations/managing-organization-settings/verifying-your-organizations-domain)." Depois de verificar a propriedade dos domínios da sua conta, será exibido um selo "Verificado" no perfil de cada organização com o domínio listado no seu perfil. {% data reusables.organizations.verified-domains-details %} @@ -22,7 +22,7 @@ Os proprietários da organização conseguirão de verificar a identidade dos in Após verificar domínios para a sua conta corporativa, você poderá restringir notificações de e-mail para domínios verificados para todas as organizações pertencentes à sua conta corporativa. Para obter mais informações, consulte "[Restringir notificações de e-mail da sua conta corporativa para domínios aprovados](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)". -Mesmo se você não restringir as notificações de e-mail para a conta corporativa, se o proprietário da organização tiver restringido as notificações de e-mail para a organização, os integrantes da organização poderão receber notificações de qualquer domínio verificado pela conta corporativa, além de qualquer domínio verificado para a organização. Para obter mais informações sobre restrição de notificações para uma organização, consulte "[Restringir notificações de e-mail para um domínio aprovado](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain). +Mesmo se você não restringir as notificações de e-mail para a conta corporativa, se o proprietário da organização tiver restringido as notificações de e-mail para a organização, os integrantes da organização poderão receber notificações de qualquer domínio verificado pela conta corporativa, além de qualquer domínio verificado para a organização. Para obter mais informações sobre restrição de notificações para uma organização, consulte "[Restringir notificações de e-mail para um domínio aprovado](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain). ### Verificar o domínio da conta corporativa 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 73b3b552f5..edb2e31e58 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 @@ -53,4 +53,4 @@ Ao ativar o logon único do SAML para a sua conta corporativa, cada integrante d ### Leia mais -- "[Visualizar e gerenciar acesso de SAML de um integrante à sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" +- "[Visualizar e gerenciar acesso de SAML de um integrante à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md index 6909153403..22e196b674 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -14,7 +14,7 @@ topics: Se desejar, você pode optar por adicionar uma descrição, um local, um site e um endereço de e-mail para sua organização, além de fixar repositórios importantes no topo da página. -{% if currentVersion == "free-pro-team@latest" %}Para confirmar a identidade da sua organização e exibir um selo "Verificado" na página de perfil da sua organização, você deve verificar os domínios da sua organização com {% data variables.product.product_name %}. Par obter mais informações, consulte "[Verificar o domínio da sua organização](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." +{% if currentVersion == "free-pro-team@latest" %}Para confirmar a identidade da sua organização e exibir um selo "Verificado" na página de perfil da sua organização, você deve verificar os domínios da sua organização com {% data variables.product.product_name %}. Par obter mais informações, consulte "[Verificar o domínio da sua organização](/organizations/managing-organization-settings/verifying-your-organizations-domain)." ![Exemplo de página de perfil verificada da organização](/assets/images/help/profile/org_profile_verified.png) {% else %} @@ -23,4 +23,4 @@ Se desejar, você pode optar por adicionar uma descrição, um local, um site e ### Leia mais -- "[Sobre organizações](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" +- "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md index b2ba70604a..71d4ffdff7 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/about-your-profile.md @@ -1,6 +1,6 @@ --- -title: About your profile -intro: 'Your profile page tells people the story of your work through the repositories you''re interested in, the contributions you''ve made, and the conversations you''ve had.' +title: Sobre seu perfil +intro: 'Sua página de perfil conta a história do seu trabalho por meio de repositórios nos quais você está interessado, das contribuições que fez e das conversas que teve.' redirect_from: - /articles/viewing-your-feeds/ - /articles/profile-pages/ @@ -9,31 +9,33 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - perfis --- -You can add personal information about yourself in your bio, like previous places you've worked, projects you've contributed to, or interests you have that other people may like to know about. For more information, see "[Adding a bio to your profile](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)." +Você pode adicionar informações pessoais sobre si mesmo na bio, como locais em que trabalhou anteriormente, os projetos com os quais contribuiu ou interesses que você tem que outras pessoas talvez gostem de saber. Para obter mais informações, consulte "[Adicionar uma bio ao seu perfil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)". {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} {% data reusables.profile.profile-readme %} -![Profile README file displayed on profile](/assets/images/help/repository/profile-with-readme.png) +![Arquivo README do perfil exibido no perfil](/assets/images/help/repository/profile-with-readme.png) {% endif %} -People who visit your profile see a timeline of your contribution activity, like issues and pull requests you've opened, commits you've made, and pull requests you've reviewed. You can choose to display only public contributions or to also include private, anonymized contributions. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" or "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." +As pessoas que visitam seu perfil veem uma linha do tempo da sua atividade de contribuição, como problemas e pull requests que abriu, commits que fez e pull requests que revisou. Você pode optar por exibir apenas contribuições públicas ou também incluir contribuições privadas e anônimas. Para obter mais informações, consulte "[Exibir contribuições na sua página de perfil](/articles/viewing-contributions-on-your-profile-page)" ou "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". -People who visit your profile can also see the following information. +As pessoas que visitam seu perfil também podem ver as informações a seguir. -- Repositories and gists you own or contribute to. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}You can showcase your best work by pinning repositories and gists to your profile. For more information, see "[Pinning items to your profile](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)."{% endif %} -- Repositories you've starred. For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)." -- An overview of your activity in organizations, repositories, and teams you're most active in. 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. For more information, see "[Personalizing your profile](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)."{% endif %} +- Repositórios e gists que você possui ou com os quais contribui. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contém currentVersion %}Você pode exibir o melhor trabalho fixando repositórios e gists no seu perfil. Para obter mais informações, consulte "[Fixar itens no seu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)".{% endif %} +- Repositórios que você salvou com estrela. Para obter mais informações, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)." +- Uma visão geral da sua atividade em organizações, repositórios e equipes nos quais você está mais ativo. Para obter mais informações, consulte "[Exibir uma visão geral da sua atividade no seu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% if currentVersion == "free-pro-team@latest" %} +- Selos que serão exibidos se você usar {% data variables.product.prodname_pro %} ou participar de programas como {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %} ou do programa de desenvolvedor de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Personalizar seu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)".{% endif %} -You can also set a status on your profile to provide information about your availability. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)." +Você também pode definir um status no seu perfil para fornecer informações sobre a sua disponibilidade. Para obter mais informações, consulte "[Configurar um status](/articles/personalizing-your-profile/#setting-a-status)". -### Further reading +### Leia mais -- "[How do I set up my profile picture?](/articles/how-do-i-set-up-my-profile-picture)" -- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" +- "[Como configurar minha foto de perfil?](/articles/how-do-i-set-up-my-profile-picture)" +- "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Exibir contribuições no perfil](/articles/viewing-contributions-on-your-profile)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index c3cc863659..a53caeead8 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- -title: Viewing contributions on your profile -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.' +title: Exibir contribuições no perfil +intro: 'Seu perfil de {% data variables.product.product_name %} exibe {% if currentVersion == "free-pro-team@latest" ou enterpriseServerVersions contém currentVersion %}os seus repositórios fixados, bem como{% endif %} um gráfico de contribuições de repositório ao longo do último ano.' redirect_from: - /articles/viewing-contributions/ - /articles/viewing-contributions-on-your-profile-page/ @@ -9,90 +9,95 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - perfis --- -{% 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. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Seu gráfico de contribuição mostra a atividade dos repositórios públicos. {% endif %}Você pode escolher mostrar a atividade dos {% if currentVersion == "free-pro-team@latest" ou enterpriseServerVersions contém currentVersion %}repositórios públicos e {% endif %}privados, com informações específicos da atividade em repositórios privados anonimizados. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". {% note %} -**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" +**Observação:** Os commits só aparecerão no seu gráfico de contribuições se o endereço de e-mail que você usou para criar das submissões estiver conectado à sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" {% endnote %} -### What counts as a contribution +### O que conta como contribuição -On your profile page, certain actions count as contributions: +Na sua página de perfil, determinadas ações contam como contribuições: -- Committing to a repository's default branch or `gh-pages` branch -- Opening an issue -- Proposing a pull request -- Submitting a pull request review{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %} +- Fazer commit no branch `gh-pages` ou no branch padrão de um repositório +- Abrir um problema +- Abrir uma discussão +- Responder a uma discussão +- Propor uma pull request +- Enviar uma revisão de pull request{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- Fazer coautoria de commits no branch `gh-pages` ou no branch padrão do repositório{% endif %} {% data reusables.pull_requests.pull_request_merges_and_contributions %} -### Popular repositories +### Repositórios populares -This section displays your repositories with the most watchers. {% 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 %} +Esta seção exibe os repositórios com a maioria dos inspetores. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contém currentVersion %}Após [fixar repositórios no seu perfil](/articles/pinning-repositories-to-your-profile), esta seção irá mudar para "Repositórios fixos".{% endif %} -![Popular repositories](/assets/images/help/profile/profile_popular_repositories.png) +![Repositórios populares](/assets/images/help/profile/profile_popular_repositories.png) {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -### Pinned repositories +### Repositórios fixos -This section displays up to six public repositories and can include your repositories as well as repositories you've contributed to. To easily see important details about the repositories you've chosen to feature, each repository in this section includes a summary of the work being done, the number of [stars](/articles/saving-repositories-with-stars/) the repository has received, and the main programming language used in the repository. For more information, see "[Pinning repositories to your profile](/articles/pinning-repositories-to-your-profile)." +Esta seção exibe até seis repositórios públicos e pode incluir tanto repositórios pertencentes a você como aqueles com os quais você contribuiu. Para ver detalhes importantes sobre os repositórios que você escolheu retratar, cada repositório nesta seção inclui um resumo do trabalho que está sendo feito, o número de [estrelas](/articles/saving-repositories-with-stars/) que ele recebeu e a principal linguagem de programação usada nele. Para obter mais informações, consulte "[Fixar repositórios no seu perfil](/articles/pinning-repositories-to-your-profile)". -![Pinned repositories](/assets/images/help/profile/profile_pinned_repositories.png) +![Repositórios fixos](/assets/images/help/profile/profile_pinned_repositories.png) {% endif %} -### Contributions calendar +### Calendário de contribuições -Your contributions calendar shows your contribution activity. +O calendário de contribuições mostra sua atividade de contribuição. -#### Viewing contributions from specific times +#### Exibir contribuições de horários específicos -- Click on a day's square to show the contributions made during that 24-hour period. -- Press *Shift* and click on another day's square to show contributions made during that timespan. +- Clique no quadrado de um dia para mostrar as contribuições feitas durante esse período de 24 horas. +- Pressione *Shift* e clique no quadrado de outro data para mostrar as contribuições feitas durante esse período. {% note %} -**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger timespan, we will only display one month of contributions. +**Observação:** só é possível selecionar um intervalo de até um mês no calendário de contribuições. Se você selecionar um período maior, será exibido apenas um mês de contribuições. {% endnote %} -![Your contributions graph](/assets/images/help/profile/contributions_graph.png) +![Gráfico de contribuição](/assets/images/help/profile/contributions_graph.png) -#### How contribution event times are calculated +#### Como são calculados os horários de evento de contribuição -Timestamps are calculated differently for commits and pull requests: -- **Commits** use the time zone information in the commit timestamp. For more information, see "[Troubleshooting commits on your timeline](/articles/troubleshooting-commits-on-your-timeline)." -- **Pull requests** and **issues** opened on {% data variables.product.product_name %} use your browser's time zone. Those opened via the API use the timestamp or time zone [specified in the API call](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). +Os registros de data e hora são calculados de forma diferente para commits e pull requests: +- Os **commits** usam as informações de fuso horário no registro de data e hora do commit. Para obter mais informações, consulte "[Solucionar problemas de commits na linha do tempo](/articles/troubleshooting-commits-on-your-timeline)". +- As **pull requests** e os **problemas** abertos no {% data variables.product.product_name %} usam o fuso horário do navegador. Os abertos pela API usam o registro de data e hora ou o fuso horário [especificado na chamada de API](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). -### Activity overview +### Visão geral de atividade -{% data reusables.profile.activity-overview-summary %} For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)." +{% data reusables.profile.activity-overview-summary %} Para obter mais informações, consulte "[Exibir a visão geral das atividades no perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)". -![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png) +![Seção Visão geral de atividade no perfil](/assets/images/help/profile/activity-overview-section.png) -The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see “[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." +As organizações retratadas na visão geral da atividade são priorizadas de acordo com a forma como você está ativo na organização. Se você for integrante de uma organização e @mencioná-la na bio do perfil, essa organização será priorizada na visão geral da atividade. Para obter mais informações, consulte “[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” ou "[Adicionar uma bio ao seu perfil](/articles/adding-a-bio-to-your-profile/)". -### Contribution activity +### Atividade de contribuição -The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened. You can see your contributions over time by either clicking **Show more activity** at the bottom of your contribution activity or by clicking the year you're interested in viewing on the right side of the page. Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity. If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened. +A seção de atividade de contribuição contém uma linha do tempo detalhada do seu trabalho, incluindo commits feitos exclusivamente por você ou em coautoria, solicitações de pull que você propôs e problemas que você abriu. Para ver suas contribuições ao longo do tempo, clique em **Mostrar mais atividade** na parte inferior da atividade de contribuição ou clique no ano em que você está interessado em visualizar, no lado direito da página. Momentos importantes, como a data em que você ingressou na organização, propôs sua primeira pull request ou abriu um problema relevante, são realçados na atividade de contribuição. Se você não conseguir ver determinados eventos na sua linha do tempo, verifique se ainda tem acesso à organização ou ao repositório em que o evento aconteceu -![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png) +![Filtro de hora de atividade de contribuição](/assets/images/help/profile/contributions_activity_time_filter.png) {% if currentVersion != "github-ae@latest" %} -### Viewing contributions from {% data variables.product.product_location_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} +### Exibir contribuições da {% data variables.product.product_location_enterprise %} no {% data variables.product.prodname_dotcom_the_website %} +Se o administrador do site habilitou -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. For more information, see "[Sending your {% data variables.product.prodname_ghe_server %} contributions to your {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)." +{% data variables.product.prodname_unified_contributions %}, você pode enviar contagens de contribuição de {% data variables.product.prodname_enterprise %} para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Enviar suas contribuições do {% data variables.product.prodname_ghe_server %} para o {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)". {% endif %} -### Further reading +### Leia mais -- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" -- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" -- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)" +- "[Visualizar contribuições na página de perfil](/articles/viewing-contributions-on-your-profile-page)" +- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" +- "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Exibir a visão geral das atividades no perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)" 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 0cd4560c5d..e9fc190a07 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 @@ -25,7 +25,7 @@ Os commits aparecerão no gráfico de contribuições se atenderem a **todas** e - No branch-padrão do repositório - No branch `gh-pages` (para repositórios com sites de projetos) -Para obter mais informações sobre sites de projeto, consulte "[Sobre {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)". +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Além disso, **pelo menos uma** das seguintes afirmativas devem ser verdadeiras: - Você é um colaborador no repositório ou um integrante da organização que possui o repositório. @@ -66,7 +66,7 @@ Não é possível adicionar endereços de e-mail genéricos, como `jane@computer #### O commit não foi criado no branch `gh-pages` ou padrão -Os commits só são contados se forem feitos no branch-padrão ou no branch `gh-pages` (para repositórios com sites de projeto). Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)". +Os commits só são contados se forem feitos no branch-padrão ou no branch `gh-pages` (para repositórios com sites de projeto). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Se os commits estiverem em um branch que não seja `gh-pages` ou o padrão e você quiser que eles sejam contabilizados para suas contribuições, precisará seguir um destes procedimentos: - [Abrir uma pull request](/articles/creating-a-pull-request) para que ocorra o merge das alterações no branch `gh-pages` ou padrão. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md index 56bc439f15..420b683689 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard.md @@ -1,56 +1,58 @@ --- -title: About your personal dashboard +title: Sobre seu painel pessoal 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: 'You can visit your personal dashboard to keep track of issues and pull requests you''re working on or following, navigate to your top repositories and team pages, stay updated on recent activities in organizations and repositories you''re subscribed to, and explore recommended repositories.' +intro: 'Você pode visitar seu painel pessoal para acompanhar problemas e pull requests nos quais está trabalhando ou seguindo, navegar para os repositórios principais e páginas de equipe, manter-se atualizado sobre atividades recentes nas organizações e nos repositórios em que está inscrito e explorar repositórios recomendados.' versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - contas --- -### Accessing your personal dashboard +### Acessar seu painel pessoal -Your personal dashboard is the first page you'll see when you sign in on {% data variables.product.product_name %}. +Seu quadro pessoal é a primeira página que você verá quando entrar no {% data variables.product.product_name %}. -To access your personal dashboard once you're signed in, click the {% octicon "mark-github" aria-label="The github octocat logo" %} in the upper-left corner of any page on {% data variables.product.product_name %}. +Para acessar seu quadro pessoal assim que se conectar, clique no {% octicon "mark-github" aria-label="The github octocat logo" %} no canto superior esquerdo de qualquer página em {% data variables.product.product_name %}. -### Finding your recent activity +### Encontrar sua atividade recente -In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests you're working on. Under "Recent activity", you can preview up to 12 recent updates made in the last two weeks. +Na seção "Recent activity" (Atividade recente) do feed de notícias, você pode encontrar e acompanhar problemas e pull requests recém-atualizados nos quais você está trabalhando, além de visualizar até 12 atualizações recentes feitas nas últimas duas semanas. {% data reusables.dashboard.recent-activity-qualifying-events %} -### Finding your top repositories and teams +### Encontrar equipes e repositórios principais -In the left sidebar of your dashboard, you can access the top repositories and teams you use. +Na barra lateral esquerda do painel, é possível acessar os repositórios e equipes principais que usa. -![list of repositories and teams from different organizations](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png) +![lista de repositórios e equipes de diferentes organizações](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png) -The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list 4 months after you last interacted with them. +A lista dos principais repositórios é gerada automaticamente e pode incluir qualquer repositório com o qual você interagiu, independentemente de pertencer diretamente à sua conta. As interações incluem criação commits, abrir ou comentar em problemas e pull requests. A lista dos principais repositórios não pode ser editada, mas os repositórios serão excluídos da lista 4 meses após a última vez que você interagir com eles. -You can also find a list of your recently visited repositories, teams, and project boards when you click into the search bar at the top of any page on {% data variables.product.product_name %}. +Também é possível encontrar uma lista de seus repositórios, equipes e quadros de projeto recentemente visitados quando você clica na barra de pesquisa no topo de qualquer página do {% data variables.product.product_name %}. -### Staying updated with activity from the community +### Permanecer atualizado com as atividades da comunidade -In the "All activity" section of your news feed, you can view updates from repositories you're subscribed to and people you follow. The "All activity" section shows updates from repositories you watch or have starred, and from users you follow. +Na seção "All activity" (Todas as atividades) do feed de notícias, você pode exibir atualizações de repositórios em que está inscrito e de pessoas que você segue. Essa seção mostra atualizações dos repositórios que você inspeciona ou marca com estrela e dos usuários que você segue. -You'll see updates in your news feed when a user you follow: -- Stars a repository. +Atualizações serão exibidas no feed de notícias quando um usuário que você segue: +- Marcar um repositório com estrelas. - Follows another user.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- Creates a public repository.{% endif %} -- Opens an issue or pull request with "help wanted" or "good first issue" label on a repository you're watching. -- Pushes commits to a repository you watch.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- Forks a public repository.{% endif %} +- Cria um repositório público.{% endif %} +- Abrir um problema ou uma pull request com a etiqueta "help wanted" ou "good first issue" em um repositório que você está inspecionando. +- Faz push de commits para um repositório que você inspeciona.{% if currentVersion == "free-pro-team@latest" ou enterpriseServerVersions contém currentVersion %} +- Bifurca um repositório público.{% endif %} -For more information about starring repositories and following people, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)" and "[Following people](/articles/following-people)." +Para obter mais informações sobre como atribuir estrelas a repositórios e seguir pessoas, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)" e "[Seguir pessoas](/articles/following-people)". -### Exploring recommended repositories +### Explorar repositórios recomendados -In the "Explore repositories" section on the right side of your dashboard, you can explore recommended repositories in your communities. 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 %} +Na seção "Explorar repositórios" no lado direito do painel, é possível explorar repositórios recomendados nas suas comunidades. As recomendações têm por base repositórios que você marcou com uma estrela ou visitou, as pessoas que você segue e a atividade nos repositórios aos quais você tem acesso.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Encontrar maneiras de contribuir com código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %} -### Further reading +### Leia mais -- "[About your organization dashboard](/articles/about-your-organization-dashboard)" +- "[Sobre o painel da sua organização](/articles/about-your-organization-dashboard)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md index a70167108e..186cc2be83 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -52,7 +52,7 @@ Você também pode converter sua conta de usuário pessoal diretamente em uma or {% tip %} -**Dica**: quando você converte uma conta de usuário em uma organização, os colaboradores nos repositórios que pertencem à conta são adicionados à nova organização como *colaboradores externos*. Você pode então convidar *colaboradores externos* para se tornarem integrantes da nova organização, se desejar. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)". +**Dica**: quando você converte uma conta de usuário em uma organização, os colaboradores nos repositórios que pertencem à conta são adicionados à nova organização como *colaboradores externos*. Você pode então convidar *colaboradores externos* para se tornarem integrantes da nova organização, se desejar. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)". {% endtip %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md index 352849bd57..3825934664 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -1,16 +1,18 @@ --- -title: Setting up and managing your GitHub user account -shortTitle: User accounts +title: Configurar e gerenciar sua conta de usuário do GitHub +shortTitle: Contas de usuário redirect_from: - /categories/setting-up-and-managing-your-github-user-account versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - contas --- -### Table of Contents +### Índice {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} @@ -23,7 +25,7 @@ versions: {% 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 /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 %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index dffcea9f35..2e34b6fd03 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -56,4 +56,4 @@ Os repositórios de propriedade de uma organização podem conceder mais acesso - "[Níveis de permissão para um repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)" - "[Remover um colaborador de um repositório pessoal](/articles/removing-a-collaborator-from-a-personal-repository)" - "[Remover a si mesmo de um repositório de colaborador](/articles/removing-yourself-from-a-collaborator-s-repository)" -- "[Organizar integrantes em equipes](/articles/organizing-members-into-teams)" +- "[Organizar integrantes em equipes](/organizations/organizing-members-into-teams)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md index 78144dcb96..68dc2acb82 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -25,4 +25,4 @@ Ao criar um novo repositório em {% data variables.product.product_location %}, ### Leia mais -- "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)" +- "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md index 5a1a59dd02..a07cfdc40d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -13,7 +13,7 @@ Os lembretes agendados são usados para garantir que os usuários se concentrem Para certos eventos, você também pode habilitar alertas em tempo real para agendamentos de lembretes. Os alertas em tempo real são enviados para o seu canal do Slack assim que ocorrer um evento importante, como, por exemplo, a atribuição de uma revisão, ocorre. -Você pode definir lembretes agendados para solicitações de revisão no nível da equipe para pull requests nas organizações das quais você é integrante. Antes de criar um lembrete agendado para você, um proprietário da organização deve autorizar o seu espaço de trabalho do Slack. Para obter mais informações, consulte "[Gerenciar lembretes agendados para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)". +Você pode definir lembretes agendados para solicitações de revisão no nível da equipe para pull requests nas organizações das quais você é integrante. Antes de criar um lembrete agendado para você, um proprietário da organização deve autorizar o seu espaço de trabalho do Slack. Para obter mais informações, consulte "[Gerenciar lembretes agendados para a sua organização](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)". {% data reusables.reminders.scheduled-reminders-limitations %} @@ -50,5 +50,5 @@ Você pode definir lembretes agendados para solicitações de revisão no nível ### Leia mais -- "[Gerenciar lembretes agendados para a sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" -- "[Gerenciar lembretes agendados para a sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" +- "[Gerenciar lembretes agendados para a sua organização](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- "[Gerenciar lembretes agendados para a sua equipe](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" 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 fd56d55423..0314902a9e 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 @@ -7,6 +7,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - contas --- ### Sobre os níveis de permissões para um repositório de conta de usuário @@ -25,33 +27,37 @@ Você também pode {% if currentVersion == "free-pro-team@latest" %}convidar{% e O proprietário do repositório tem controle total do repositório. Além das ações que qualquer colaborador pode executar, o proprietário do repositório pode executar as ações a seguir. -| Ação | Mais informações | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% 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 %} -| 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" %} -| Gerenciar configurações de segurança e análise para o repositório | "[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" %} -| Habilitar o gráfico de dependências para um repositório privado | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Excluir pacotes | "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)" |{% endif %} -| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| Receive | | -| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | -| Manage data use for a private repository | "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"|{% endif %} -| Definir os proprietários do código do repositório | "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | -| Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} -| Criar consultorias de segurança | "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Exibir um botão de patrocinador | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" | -| 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 %} +| Ação | Mais informações | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| {% 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 as interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)".|{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| Renomear um branch, incluindo o branch padrão | "[Renomear um 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" %} +| Gerenciar configurações de segurança e análise para o repositório | "[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)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Habilitar o gráfico de dependências para um repositório privado | "[Explorar as dependências de um repositório](/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" or currentVersion ver_gt "enterprise-server@3.0" %} +| Excluir e restaurar pacotes | "[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)"|{% endif %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +| Excluir pacotes | "[Excluir pacotes](/packages/learn-github-packages/deleting-a-package)" +{% endif %} +| Personalizar a visualização das mídias sociais do repositório | "[Personalizar a visualização das mídias sociais do seu repositório](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | +| Criar um modelo a partir do repositório | "[Criar um repositório a partir do modelo](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Receber | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} para dependências vulneráveis | "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| Ignorar {% data variables.product.prodname_dependabot_alerts %} no repositório | "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| Gerenciar o uso de dados para um repositório privado | "[Gerenciar as configurações de uso de dados para o seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)" +{% endif %} +| Definir os proprietários do código do repositório | "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| Arquivar o repositório | "[Sobre arquivar os repositórios](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} +| Criar consultorias de segurança | "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| Exibir um botão de patrocinador | "[Exibir um botão de patrocinador no seu repositório](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +| Permitir ou negar merge automático para pull requests | "[Gerenciar merge automático para pull requests no seu repositório](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)", {% endif %} -### Collaborator access for a repository owned by a user account +### Acesso de colaborador para um repositório pertencente a uma conta de usuário -Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository. +Os colaboradores em um repositório pessoal podem extrair (ler) os conteúdos do repositório e fazer push (gravação) das alterações no repositório. {% note %} @@ -59,26 +65,27 @@ Collaborators on a personal repository can pull (read) the contents of the repos {% endnote %} -Collaborators can also perform the following actions. +Os colaboradores também podem executar as seguintes ações. -| Ação | Mais informações | -|:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Bifurcar o repositório | "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)" | -| Create, edit, and delete comments on commits, pull requests, and issues in the repository |
  • "[About issues](/github/managing-your-work-on-github/about-issues)"
  • "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"
| -| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | -| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | -| Manage milestones for issues and pull requests in the repository | "[Criar e editar marcos para problemas e pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | -| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | -| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% 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 | "[Criar uma pull request de uma bifurcação](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | -| Submit a review on a pull request that affects the mergeability of the pull request | "[Revisando alterações propostas em uma pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | -| Create and edit a wiki for the repository | "[Sobre wikis](/github/building-a-strong-community/about-wikis)" | -| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" | -| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" %} -| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} -| Remover a si mesmos como colaboradores do repositório | "[Remover a si mesmo de um repositório de colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | +| Ação | Mais informações | +|:---------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Bifurcar o repositório | "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| Renomear um branch diferente do branch padrão | "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)" ➲{% endif %} +| Criar, editar e excluir comentários em commits, pull requests e problemas no repositório |
  • "[Sobre problemas](/github/managing-your-work-on-github/about-issues)"
  • "[Comentar em um pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
| +| Criar, atribuir, fechar e reabrir problemas no repositório | "[Gerenciar o seu trabalho com problemas](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| Gerenciar etiquetas para problemas e pull requests no repositório | "[Etiquetar problemas e pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| Gerenciar marcos para problemas e pull requests no repositório | "[Criar e editar marcos para problemas e pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| Marcar um problema ou pull request no repositório como duplicado | "[Sobre problemas e pull requests duplicados](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| Criar, mesclar e fechar pull requests no repositório | "[Propor alterações para o seu trabalho com pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| Habilitar e desabilitar o merge automático para um pull request | "[Fundir automaticamente um pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)"{% endif %} +| Aplicar alterações sugeridas aos pull requests no repositório | "[Incorporar feedback no seu pull request](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" | +| Criar um pull request a partir de uma bifurcação do repositório | "[Criar uma pull request de uma bifurcação](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| Enviar uma revisão em um pull request que afeta a capacidade de merge do pull request | "[Revisando alterações propostas em uma pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| Criar e editar uma wiki para o repositório | "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)" | +| Criar e editar versões para o repositório | "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)" | +| Agir como proprietário do código para o repositório | "[Sobre proprietários de código](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} +| Publicar, visualizar ou instalar pacotes | "[Publicar e gerenciar pacotes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)",{% endif %} +| Remover a si mesmos como colaboradores do repositório | "[Remover a si mesmo de um repositório de colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md index e43a3ba4e4..8420db5193 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address.md @@ -1,21 +1,23 @@ --- -title: Setting a backup email address -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 %}. +title: Configurar endereço de e-mail de backup +intro: 'Use um endereço de e-mail de backup como um destino adicional para notificações de conta relevantes para segurança{% if currentVersion != "github-ae@latest" %} e para redefinir sua senha de forma segura, se não puder mais acessar seu endereço de e-mail principal{% endif %}.' redirect_from: - /articles/setting-a-backup-email-address versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - contas + - notificações --- {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.emails %} -3. Under "Backup email address," select the address you want to set as your backup email address using the drop-down menu. -![Backup email address](/assets/images/help/settings/backup-email-address.png) -4. Click **Save**. +3. Em "Backup email address" (Endereço de e-mail de backup), selecione o endereço que deseja configurar como endereço de e-mail de backup usando o menu suspenso. ![Endereço de e-mail de backup](/assets/images/help/settings/backup-email-address.png) +4. Clique em **Salvar**. -### Further reading +### Leia mais -- "[Managing email preferences](/articles/managing-email-preferences/)" -- "[Updating your GitHub access credentials](/articles/updating-your-github-access-credentials/)" +- "[Gerenciar preferências de e-mail](/articles/managing-email-preferences/)" +- "[Atualizar credenciais de acesso do GitHub](/articles/updating-your-github-access-credentials/)" diff --git a/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md index f29bc2e1b7..f8db9e047d 100644 --- a/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/pt-BR/content/github/site-policy/github-corporate-terms-of-service.md @@ -125,7 +125,7 @@ O uso dos Produtos pelo Cliente não deve violar quaisquer leis aplicáveis, inc O uso do Serviço pelo Cliente deve estar em conformidade com a [Política de Uso Aceitável do GitHub](/articles/github-acceptable-use-policies) e as [Diretrizes da Comunidade do GitHub](/articles/github-community-guidelines). O Cliente não deve usar o Serviço em qualquer jurisdição para atividade ou Conteúdo ilegal, obsceno, ofensivo ou fraudulento, como defender ou causar danos, interferir ou violar a integridade ou a segurança de uma rede ou um sistema, enganar os filtros, enviar vírus ou código nocivo e mensagens não solicitadas, abusivas ou enganosas ou violar direitos de terceiros. #### 3. Privacidade -A [Declaração de Privacidade do GitHub](/articles/github-privacy-statement) e o [Adendo de Proteção de Dados do GitHub](/github/site-policy/github-data-protection-addendum) fornecem aviso detalhado das práticas de privacidade e uso de dados do GitHub, bem como do processamento e das obrigações de segurança do GitHub no que diz respeito aos Dados Pessoais do Cliente. Qualquer pessoa, entidade ou serviço que colete dados do Serviço deve estar em conformidade com a Declaração de Privacidade do GitHub, especialmente no que diz respeito à coleta de Informações Pessoais dos Usuários (conforme definido na Declaração de Privacidade do GitHub). Se o Cliente coletar qualquer Informação pessoal do usuário no GitHub, só a utilizará para a finalidade para a qual o Usuário externo o autorizou. O Cliente protegerá essas Informações pessoais, e o Cliente responderá prontamente a reclamações, solicitações de remoção e pedidos para "não contatar" do GitHub ou de Usuários externos. +The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Agreement](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Qualquer pessoa, entidade ou serviço que colete dados do Serviço deve estar em conformidade com a Declaração de Privacidade do GitHub, especialmente no que diz respeito à coleta de Informações Pessoais dos Usuários (conforme definido na Declaração de Privacidade do GitHub). Se o Cliente coletar qualquer Informação pessoal do usuário no GitHub, só a utilizará para a finalidade para a qual o Usuário externo o autorizou. O Cliente protegerá essas Informações pessoais, e o Cliente responderá prontamente a reclamações, solicitações de remoção e pedidos para "não contatar" do GitHub ou de Usuários externos. ### D. Responsabilidade pelo conteúdo; Propriedade; Direitos de licença diff --git a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md new file mode 100644 index 0000000000..8c94bfb559 --- /dev/null +++ b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md @@ -0,0 +1,348 @@ +--- +title: GitHub Data Protection Agreement (Non-Enterprise Customers) +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum +versions: + free-pro-team: '*' +--- + +_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._ + +## INTRODUÇÃO + +The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products. + +Na hipótese de qualquer conflito ou inconsistência entre o DPA e quaisquer outros termos nos acordos do Cliente com o GitHub, prevalecerá o DPA. As provisões do DPA substituem quaisquer disposições conflitantes da Declaração de Privacidade do GitHub que, de outra forma, possam aplicar-se ao processamento de Dados Pessoais do Cliente definidos no presente documento. Para clareza, consistente com a Cláusula 10 das Cláusulas Contratuais Padrão no Anexo 1, as Cláusulas Contratuais Padrão prevalecem sobre quaisquer outros termos no DPA. + + +## PROTEÇÃO DE DADOS DO GITHUB + +### 1. Definições. + +1.1 "**Leis de proteção de dados aplicáveis**" significa leis, regulamentações, marcos regulatórios ou outras legislações relacionadas a processamento e uso de Dados Pessoais Do Cliente, conforme aplicável ao uso do GitHub e do Serviço do GitHub pelo Cliente, incluindo: + + a. o Regulamento Geral sobre a Proteção de Dados 2016/679 da UE (**"GDPR"**), juntamente com quaisquer leis ou regulamentos nacionais equivalentes em implementação ou correspondentes, uma vez em vigor e se aplicáveis; e + + b. A Lei de Privacidade do Consumidor da Califórnia de 2018, Cal. Civ. Código §§1798.100 et seq. (**"CCPA"**); e + + c. A Lei de Proteção de Dados do Reino Unido de 2018 e a implementação do GDPR contida na mesma. + +1.2 Os termos "**Controlador**", "**Titular de dados**", "**Estado-membro**", "**Dados pessoais**", "**Violação de dados pessoais**", "**Processamento**", "**Processador**" e "**Autoridade de supervisão**" têm os significados que são atribuídos a eles nas Leis de Proteção de Dados aplicáveis. Em caso de conflito, os significados atribuídos no GDPR serão substituídos. + +1.3 O termo "**Dados pessoais do cliente**" significa quaisquer dados pessoais dos quais o Cliente seja Controlador, independentemente de serem fornecidos pelo Cliente para processamento pelo GitHub ou gerados pelo GitHub durante a execução de suas obrigações previstas no Contrato. Inclui dados como informações de cobrança, endereços IP, endereços de e-mail corporativos e quaisquer outros Dados pessoais dos quais o Cliente seja Controlador. + +1.4 O termo "**Dados de repositório do cliente**" significa quaisquer dados ou informações que sejam carregados ou criados pelo Cliente em um dos respectivos Repositórios privados. + +1.5 "**Violação de dados**" significa uma Violação de dados pessoais ou qualquer outra violação confirmada ou razoavelmente suspeita dos Dados Protegidos do Cliente. + +1.6 O termo "**Usuário final**" significa um Titular de dados individual que controla uma conta do GitHub, concordou com os Termos de serviço do GitHub e cujos Dados pessoais estão sendo transferidos, armazenados ou processados pelo GitHub. Por exemplo, cada contratado ou funcionário do Cliente que tenha uma conta do GitHub também é um Usuário final do GitHub. + +1.7 O termo "**Finalidades permitidas**" no processamento de dados significa as finalidades limitadas e específicas para fornecer o Serviço conforme estabelecido no Contrato, na Declaração de privacidade do GitHub e neste Anexo A ou as finalidades para as quais um Titular de dados autorizou o uso de Dados pessoais do cliente. + +1.8 O termo "**Dados protegidos**" inclui Dados pessoais do cliente e Dados de repositório do cliente processados pelo GitHub em nome do Cliente neste Contrato. + +1.9 O termo "**Dados confidenciais**" significa quaisquer Dados Pessoais de Clientes que revelem origem racial ou étnica; opiniões políticas, crenças religiosas ou filosóficas ou filiação sindical; processamento de dados genéticos ou biométricos para identificar uma pessoa física de forma inequívoca; dados relativos à saúde, à orientação ou à vida sexual de uma pessoa física e dados relativos a infrações, condenações penais ou medidas de segurança. + +### 2. Status e conformidade. + +#### 2.1 Processamento de dados. +O GitHub atua como um Processador com relação a Dados Pessoais do Cliente recebidos em conexão com o Contrato e os processará somente para as Finalidades Permitidas de acordo com as instruções do Cliente, conforme representado pelo Contrato e por outras comunicações escritas. Caso o GitHub não consiga cumprir as instruções do Cliente (por exemplo, devido a conflitos com as Leis de proteção de dados aplicáveis ou quando o processamento é exigido pelas Leis de proteção de dados aplicáveis ou outros requisitos legais), o GitHub notificará o Cliente desde que permitido. Embora o GitHub processe todos os Dados pessoais do cliente nos Estados Unidos ou na União Europeia, os subprocessadores do GitHub podem processar dados fora dos Estados Unidos ou da União Europeia. Além disso, o GitHub atua como Processador para Dados de repositório do cliente. + +#### 2.2 Controladores de dados. +O GitHub recebe Dados pessoais tanto do cliente como diretamente dos titulares de dados que criam contas de usuário final. O Cliente é Controlador apenas dos Dados pessoais do cliente que ele transfere diretamente para o GitHub. + +#### 2.3 Conformidade do GitHub; transferências de dados. +O GitHub cumprirá as leis de proteção de dados aplicáveis com relação ao processamento dos dados pessoais do cliente. + +Todas as transferências de dados pessoais do cliente para fora da União Europeia, Espaço Econômico Europeu, Reino Unido e a Suíça para fornecer o Serviço serão regidas pelas Cláusulas Contratuais Padrão no Anexo 1 (Cláusulas Contratuais Padrão). O GitHub cumprirá os requisitos do Espaço Econômico Europeu e da legislação suíça de proteção de dados referente à coleta, uso, transferência, retenção e outro tipo de processamento de Dados Pessoais do Cliente do Espaço Econômico Europeu, Reino Unido e Suíça. Todas as transferências de Dados Pessoais do Cliente para um país terceiro ou uma organização internacional estarão sujeitas às salvaguardas apropriadas, conforme descrito no Artigo 46 do RGPD e tais transferências e salvaguardas serão documentadas de acordo com o Artigo 30(2) do RGPD. + +Além disso, o GitHub é certificado na relação entre UE e EUA. e entre a Suíça e os EUA. In addition, GitHub is certified to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-U.S. Privacy Shield Framework as a legal basis for transfers of Personal Data in light of the judgment of the Court of Justice of the EU in Case C-311/18. O GitHub concorda em notificar o Cliente se determinar que não pode mais cumprir sua obrigação de fornecer o mesmo nível de proteção exigido pelos princípios do Escudo de Privacidade. + + +### 3. Proteção de dados. + +#### 3.1 Limitação de finalidade. +O GitHub processará e comunicará os Dados Protegidos apenas para as Finalidades Permitidas, a menos que as Partes concordem, por escrito, com uma finalidade expandida. + +#### 3.2 Qualidade de Dados e Proporcionalidade. +O GitHub manterá os dados pessoais do Cliente precisos e atualizados, ou habilitará o Cliente a fazê-lo. O GitHub tomará medidas comercialmente razoáveis para garantir que os Dados protegidos que ele colete em nome do Cliente sejam adequados, relevantes e não excessivos em relação às finalidades para as quais são transferidos e processados. Em nenhuma hipótese, o GitHub coletará intencionalmente Dados confidenciais em nome do Cliente. O Cliente concorda que o Serviço do GitHub não se destina ao armazenamento de Dados confidenciais. Se o Cliente optar por fazer upload de Dados confidenciais para o Serviço, deverá cumprir o Artigo 9 do GDPR ou disposições equivalentes nas Leis de proteção de dados aplicáveis. + +#### 3.3 Retenção e Exclusão de Dados. +Mediante solicitação razoável do Cliente, a menos que proibido por lei, o GitHub devolverá, destruirá ou desidentificará todos os Dados pessoais do cliente e dados relacionados em todos os locais onde estejam armazenados, depois que não forem mais necessários para as finalidades permitidas, no prazo de 30 (trinta dias) após a solicitação. O GitHub pode reter Dados pessoais do cliente e dados relacionados, apenas na medida exigida pelas Leis de proteção de dados aplicáveis e durante o período estipulado por elas, desde que assegure que os Dados pessoais do cliente serão processados somente conforme necessário para a finalidade especificada nas Leis de proteção de dados aplicáveis e que os Dados pessoais do cliente permaneçam protegidos pelas Leis de proteção de dados aplicáveis. + +#### 3.4 Processamento de dados. +No que diz respeito ao processamento de Dados Protegidos do Cliente, o GitHub fornece as informações a seguir, exigidas pelo artigo 28(3) do RGPD: + +a. *O assunto e a duração do processamento* de Dados pessoais do cliente estão definidos no Contrato e neste Adendo. + +b. *A natureza e a finalidade do processamento* de Dados pessoais do cliente estão descritos na Seção 3.1 deste Adendo. + +c. *Os tipos de Dados pessoais do cliente a serem processados* estão descritos na Declaração de privacidade do GitHub e incluem Dados pessoais do cliente, como nomes de usuário, senhas, endereços de e-mail e endereços IP. O GitHub também processa as informações necessárias para efetuar a cobrança na conta do Cliente, mas não processa nem armazena informações de cartão de crédito. O Cliente pode optar por fornecer ao GitHub outros Dados pessoais do cliente; por exemplo, nas configurações de perfil do Cliente ou ao fazer upload de Dados pessoais do cliente para os repositórios do GitHub. + +d. *As categorias de Titular de dados aos quais estão relacionados os Dados pessoais do cliente* são o próprio Cliente e seus Usuários finais. + +e. *As obrigações e os direitos do Cliente* estão previstos no Contrato e neste Adendo. + +### 4. Obrigações de auditoria e segurança. + +#### 4.1 medidas de segurança técnicas e organizacionais. +Levando em consideração o que há de mais moderno, os custos de implementação e a natureza, o escopo, o contexto e as finalidades do processamento, bem como o risco de probabilidade e gravidade variadas para direitos e liberdades fundamentais das pessoas físicas, o GitHub implementará medidas técnicas e organizacionais para garantir um nível de segurança adequado contra os riscos (como destruição acidental ou ilegal, perda, alteração, divulgação ou acesso não autorizado) que se apresentam ao processar Dados Protegidos. O GitHub monitorará regularmente o cumprimento dessas medidas e continuará a tomar as providências apropriadas ao longo da vigência do Contrato. + +#### 4.2 - Resposta de incidente e notificação de violação. +GitHub will comply with Applicable Data Protection Laws. + +#### 4.3 Equipe do GitHub. +O GitHub declara e garante que tomará medidas razoáveis para assegurar que todos os funcionários do GitHub que processam Dados protegidos tenham concordado em manter a confidencialidade dos Dados Protegidos e recebido treinamento adequado sobre o cumprimento deste Adendo e das Leis de Proteção de Dados aplicáveis. + +#### 4.4 Registros. +O GitHub manterá registros escritos completos, precisos e atualizados de todas as categorias de atividades de processamento realizadas em nome do Cliente que contenham as informações exigidas nas Leis de Proteção de Dados aplicáveis. Desde que a assistência não arrisque a segurança do GitHub ou os direitos de privacidade de Titulares de dados individuais, o GitHub disponibilizará esses registros ao Cliente mediante solicitação conforme a necessidade; por exemplo, para ajudar o cliente a demonstrar conformidade com as Leis de proteção de dados aplicáveis. + +#### 4.5 Assistência. +O GitHub fornecerá a assistência cabível ao Cliente com preocupações como avaliações de impacto na privacidade de dados, solicitações de direitos de Titular de Dados, consultas com Autoridades de Supervisão e outros assuntos semelhantes, em todos os casos exclusivamente em relação ao processamento de Dados Pessoais do Cliente e levando em consideração a natureza do processamento. + +### 5. Uso e divulgação de dados protegidos. + +#### 5.1 Sem uso no Marketing. +O GitHub não usará os Dados Protegidos para fins de publicidade de conteúdo de terceiros nem os venderá a terceiros, exceto como parte de uma fusão ou aquisição. + +#### 5.2 Declaração de Privacidade do GitHub. +A Declaração de Privacidade do GitHub, disponível publicamente em [https://help.github.com/articles/github-privacy-statement/](/articles/github-privacy-statement), fornece um aviso detalhado sobre as práticas de privacidade e uso de dados do GitHub, como o uso de cookies, o processo de resolução de disputas e mais informações sobre a conformidade do GitHub com a GDPR. + +### 6. Transferência progressiva e subprocessamento. + +#### 6.1 Proteção de Dados. +O GitHub é responsável por transferências progressivas de Dados Protegidos para seus subprocessadores, como o processador de pagamentos a terceiros. Na hipótese de o GitHub transferir os Dados Protegidos para um subprocessador de terceiros ou na hipótese de GitHub, usar, ou permitir que terceiros processem os Dados Protegidos em nome do GitHub, o GitHub garantirá que o subprocessador de terceiros seja vinculado pelo acordo escrito que exige que eles forneçam, pelo menos, o mesmo nível de confidencialidade, proteção de privacidade e segurança, conforme exigido por este DPA e pelas Leis de Proteção de Dados aplicáveis. + +#### 6.2 - Aceitação de Subprocessadores do GitHub. +O Cliente autoriza o GitHub a nomear (e a permitir que cada subprocessador nomeado de acordo com esta Seção 6 também nomeie) subprocessadores de acordo com a Seção 6 e quaisquer outras restrições no Contrato. O GitHub pode continuar a usar esses subprocessadores utilizados atualmente a partir do início da vigência deste Adendo. + +#### 6.3 Consentimento Geral para Subprocessamento progressivo. +O Cliente dá consentimento geral para que o GitHub utilize subprocessadores progressivos, condicionando à conformidade do GitHub com os seguintes requisitos: + +a. Qualquer subprocessador progressivo deve concordar por escrito em somente processar dados em países que a Comissão Europeia tenha declarado como tendo um nível "adequado" de proteção ou somente processar dados em termos equivalentes às Cláusulas Contratuais Padrão, de acordo com uma aprovação das Regras corporativas vinculativas concedidas pelas autoridades europeias competentes de proteção de dados ou de acordo com uma certificação vda álida do Escudo de Privacidade entre a UE e os EUA e entre a Suíça e os EUA. Certificações do Escudo de Privacidade; e + +b. b. O GitHub restringirá o acesso do subprocessador progressivo a Dados pessoais do cliente apenas ao estritamente necessário para executar os serviços e proibirá o subprocessador de processar os Dados pessoais do cliente para qualquer outra finalidade. + +#### 6.4 - Divulgação de Acordos de Subprocessador. +O GitHub mantém uma lista de subprocessadores progressivos que utilizou para processar Dados Pessoais do Cliente em [https://help.github.com/articles/github-subprocessors-and-cookies/](/articles/github-subprocessors-and-cookies), incluindo as categorias de Dados Pessoais do Cliente processados, uma descrição do tipo de processamento que o subprocessador executa e a localização do seu processamento. Mediante solicitação por escrito do Cliente, o GitHub fornecerá esta lista de subprocessadores e os termos em que eles processarão os Dados pessoais do cliente. De acordo com as restrições de confidencialidade de subprocessadores, o GitHub pode remover informações confidenciais ou comercialmente confidenciais antes de fornecer a lista e os termos ao Cliente. Caso o GitHub não possa divulgar informações confidenciais ao Cliente, as Partes concordam que o GitHub fornecerá todas as informações razoavelmente possíveis relacionadas aos contratos de subprocessamento. + +#### 6.5 Objeção para subprocessadores. +O GitHub fornecerá um aviso por escrito no prazo de 30 (trinta), além da remoção de qualquer subprocessador, incluindo as categorias listadas na Seção 6.4, anunciando mudanças no seu site . Se o Cliente tiver uma objeção razoável à utilização do GitHub em um novo subprocessador, deverá notificar o GitHub prontamente por escrito. Sempre que possível, o GitHub envidará esforços comercialmente razoáveis para fornecer uma solução alternativa ao Serviço afetado para evitar o processamento de dados pelo subprocessador questionável. Caso o GitHub não consiga oferecer uma solução alternativa e as Partes não resolvam o conflito em 90 (noventa) dias, o Cliente poderá rescindir o Contrato. + +### 7. Rescisão. + +#### 7.1 Suspensão. +Na hipótese de o GitHub violar suas obrigações de manter um nível adequado de proteção de segurança ou privacidade, o Cliente poderá suspender temporariamente a transferência de todos os Dados Pessoais ou proibir a coleta e o processamento dos seus Dados Pessoais em nome do Cliente até que a violação seja reparada ou o Contrato seja encerrado. + +#### 7.2 - Rescisão com motivo. +Além dos direitos de rescisão que o Cliente tem previsto no Contrato, o Cliente poderá rescindir o Contrato sem prejuízo de qualquer outra reivindicação na lei ou na justiça caso: + +a. o GitHub notifique o cliente de que não pode mais cumprir suas obrigações de privacidade; + +b. a transferência, a coleta ou o processamento de todos os Dados pessoais do cliente tenha sido temporariamente suspenso por mais de um mês, de acordo com a Seção 7.1; + +c. o GitHub esteja em violação substancial ou persistente de quaisquer garantias ou representações neste Adendo; + +d. o GitHub não esteja mais em atividade, seja dissolvido, entre em liquidação ou tenha uma ordem de liquidação feita em seu nome; ou + +e. o Cliente faça objeção a um subprocessador de acordo com a Seção 6.5, e o GitHub não tenha conseguido fornecer uma solução alternativa em até 90 (noventa) dias. + +#### 7.3 Violação. +A não observância das disposições materiais deste Adendo é considerada uma violação material ao disposto no Contrato. + +#### 7.4 Não cumprimento. +Na hipótese de mudanças na lei ou na regulamentação tornarem o cumprimento deste Adendo impossível ou comercialmente impraticável, as Partes poderão renegociar o Adendo de boa-fé. Se a renegociação não corrigir a impossibilidade ou se as Partes não conseguirem chegar a um acordo, elas poderão rescindir o Contrato após 30 (trinta) dias. + +#### 7.5 Notificação. +Caso o GitHub determine que não pode mais cumprir as obrigações de privacidade previstas neste Adendo, ele notificará o Cliente por escrito imediatamente. + +#### 7.6 Modificações. +O GitHub pode modificar este Adendo de tempos em tempos, conforme exigido pelas Leis de Proteção de Dados aplicáveis, com aviso prévio de 30 (trinta) dias ao Cliente. + +#### 7.7 Requisitos de rescisão. +Após a rescisão, o GitHub deverá: + +a. tomar medidas razoáveis e apropriadas para interromper o processamento dos Dados pessoais do cliente; + +b. dentro de 90 (noventa) dias após a rescisão, excluir ou desidentificar Dados pessoais do cliente que o GitHub armazene em nome do Cliente, de acordo com a Seção 3.3; e + +c. fornecer ao Cliente garantia razoável de que o GitHub cumpriu suas obrigações na Seção 7.7. + +### 8. Responsabilidade pelo processamento de dados. + +#### 8.1 Limitações. +Exceto quando limitado pelas Leis de Proteção de Dados aplicáveis, quaisquer reivindicações referentes a este Adendo estarão sujeitas aos termos do Contrato sobre Limitações de Responsabilidade. + +## Anexo 1 – Cláusulas Contratuais Padrão (Processadores) +A execução do contrato aplicável pelo cliente inclui a execução deste Anexo 1 referente ao Adendo de Proteção de Dados ratificado pelo GitHub, Inc. + +Em países onde a aprovação regulatória é necessária para o uso das Cláusulas Contratuais Padrão, estas não podem ser confiadas à Comissão Europeia 2010/87/UE (de fevereiro de 2010) para legitimar a exportação de dados do país, a menos que o Cliente tenha a aprovação regulatória necessária. + +Para efeitos do artigo 46(2) do Regulamento Geral sobre a Proteção de Dados (UE 2016/679) referente à transferência de dados pessoais para processadores estabelecidos em países terceiros que não garantem um nível adequado de proteção de dados, o Cliente (como exportador de dados) e o GitHub (como importador de dados, cuja assinatura aparece abaixo), cada "parte" ou, coletivamente "as partes", concordaram com as seguintes Cláusulas Contratuais (as “Cláusulas” ou “Cláusulas Contratuais Padrão”) a fim de adjudicar salvaguardas adequadas no que diz respeito à proteção da privacidade e dos direitos e liberdades fundamentais dos indivíduos para a transferência por parte exportador para o importador de dados dos dados pessoais especificados no Apêndice 1. + +#### Cláusula 1: Definições +(a) "dados pessoais", "categorias especiais de dados", "processo/processamento", "controlador", "processador", "titular dos dados" e "autoridade de supervisão" terão o mesmo significado do Regulamento Geral sobre a Proteção de Dados (UE 2016/679) referente à proteção dos indivíduos no que se refere ao tratamento de dados pessoais e à livre circulação desses dados; + +(b) "o exportador de dados" significa o controlador que transfere os dados pessoais; + +(c) "o importador de dados" significa o processador que aceita receber dos dados do exportador de dados pessoais destinados a processamento em seu nome após a transferência, de acordo com as suas instruções e os termos das Cláusulas e que não está sujeito a um sistema de um país terceiro, e garante uma proteção adequada no âmbito do artigo 45(2) do Regulamento Geral da Proteção de Dados (UE 2016/679); + +(d) "subprocessador" significa qualquer processador envolvido pelo importador de dados ou por qualquer outro subprocessador do importador de dados que concorde em receber dados do importador de dados ou de qualquer outro subprocessador dos dados pessoais do importador destinados exclusivamente a atividades de processamento a serem realizadas em nome do exportador de dados após a transferência, de acordo com suas instruções, termos das Cláusulas e termos do subcontrato escrito; + +(e) "A lei de proteção de dados aplicável" é a legislação que protege os direitos e liberdades fundamentais dos indivíduos, e, em particular, o direito à privacidade no que diz respeito ao processamento de dados pessoais aplicável a um controlador de dados do Estado-Membros onde o exportador de dados estiver estabelecido; + +(f) "medidas de segurança técnicas e organizacionais" são as medidas que visam proteger os dados pessoais contra a destruição ilegal ou acidental, perda, alteração, divulgação ou acesso não autorizado, em particular quando o processamento envolve a transmissão de dados através de uma rede, e contra todas as formas ilegais de processamento. + +#### Cláusula 2: Detalhes da transferência +Os detalhes da transferência e em particular as categorias especiais de dados pessoais quando aplicáveis estão especificadas no Apêndice 1 abaixo, que constitui parte integral das Cláusulas. + +#### Cláusula 3: Cláusula de beneficiário de terceiros +1. O titular dos dados pode impor contra o exportador de dados esta Cláusula, a Cláusula 4(b) para (i), Cláusula 5(a) para (e), e (g) para (j), a Cláusula 6(1) e (2), a Cláusula 7, Cláusula 8(2), e as Cláusulas 9 a 12 como beneficiário de terceiros. + +2. O titular dos dados pode aplicar contra o importador de dados esta Cláusula, a Cláusula 5(a) para (e) e (g), a Cláusula 6, a Cláusula 7, a Cláusula 8(2), e as Cláusulas 9 a 12, nos casos em que o exportador de dados desapareceu factualmente ou deixou de existir perante a lei, a menos que qualquer entidade sucessora tenha assumido todas as obrigações legais do exportador de dados por contrato ou por aplicação da lei. em resultado do qual assume os direitos e obrigações do exportador de dados. Nesse caso, a questão dos dados pode impô-los contra essa entidade. + +3. O titular dos dados pode impor contra o subprocessador esta Cláusula, a Cláusula 5(a) para (e) e (g), a Cláusula 6, a Cláusula 7, a Cláusula 8(2), e as Cláusulas 9 a 12, nos casos em que tanto o exportador como o importador de dados desapareceram ou deixaram de existir perante a lei ou tornaram-se insolventes, a menos que qualquer entidade sucessora tenha assumido todas as obrigações legais do exportador de dados por contrato ou pelo funcionamento da lei, assumindo, como resultado, os direitos e obrigações do exportador de dados, em cujo caso, o titular dos dados pode impô-los contra essa entidade. Essa responsabilidade de terceiros do subprocessador estará limitada às suas próprias operações de processamento nos termos das Cláusulas. + +4. As partes não se opõem, caso o titular dos dados seja representado por uma associação ou outro organismo se, expressamente, assim o desejar e a legislação nacional o permitir. + +#### Cláusula 4: Obrigações do exportador de dados +O exportador de dados concorda e garante: + +(a) que o processamento, incluindo a transferência em si, dos dados pessoais foi e continuará sendo executado de acordo com as provisões relevantes aplicáveis à lei de proteção de dados (e, quando aplicável, foi notificado às autoridades responsáveis do Estado-Membros onde o exportador de dados está estabelecido) e não viola as provisões relevantes deste Estado; + +(b) que instruiu e que durante a duração dos serviços de processamento de dados pessoais irá instruir o importador de dados sobre o processamento de dados pessoais transferidos apenas no nome do exportador e em concordância com a legislação aplicável e as Cláusulas; + +(c) que o importador de dados fornecerá garantias suficientes no que se refere às medidas de segurança técnicas e organizacionais especificadas no Anexo 2 abaixo; + +(d) que, após a avaliação dos requerimentos da legislação de proteção aos dados aplicável, as medidas de segurança estejam apropriadas para proteger os dados pessoais contra a destruição ilegal ou acidental, ou a perca acidental, alteração, divulgação ou acesso não autorizado, em particular onde o processamento envolve a transmissão de dados através de uma rede, e contra todas as outras formas ilegais de processamento, e que estas medidas garantam um nível adequado de segurança aos riscos apresentados pelo processamento e pela natureza dos dados a serem protegidos, tendo em conta a conjuntura da questão e o custo de implementação; + +(e) que garantirá o cumprimento das medidas de segurança; + +(f) que, se a transferência envolver categorias especiais de dados, o titular dos dados foi informado ou será informado antes, ou o mais depressa possível após a transferência, de que os seus dados poderão ser transmitidos para um terceiro país que não garante um nível de proteção adequado no âmbito do Regulamento Geral sobre a Proteção de Dados (EU 2016/679); + +(g) que encaminhará qualquer notificação recebida do importador de dados ou qualquer subprocessador em conformidade com a Cláusula 5(b) e a Cláusula 8(3) da proteção de dados para a autoridade de supervisão de proteção aos dados se o exportador de dados decidir continuar a transferência ou interromper a suspensão; + +(h) em disponibilizar aos titulares dos dados, se assim requisitado, uma cópia das Cláusulas, com exceção do Apêndice 2 e uma descrição resumida das medidas de segurança, bem como uma cópia de qualquer contrato de serviços de subprocessamento que precisam ser feitos de acordo com as Cláusulas; a menos que as Cláusulas ou o contrato contenham informações comerciais, onde neste caso é possível remover tais informações comerciais; + +(i) que, em caso de subprocessamento, a atividade de processamento seja realizada de acordo com a Cláusula 11 por um subprocessador, fornecendo, pelo menos, o mesmo nível de proteção dos dados pessoais e dos direitos do titular de dados como o importador de dados nos termos das Cláusulas; e + +(j) que garantirá o cumprimento da Cláusula 4(a) para (i). + +#### Cláusula 5: Obrigações do importador de dados +O importador de dados concorda e garante: + +(a) processar somente dados pessoais em nome do exportador de dados e em conformidade com as suas instruções e cláusulas; se não puder assegurar tal conformidade por qualquer razão, concorda em informar prontamente o exportador de dados a inaptidão no cumprimento, que nessas circunstâncias, o exportador é autorizado a suspender a transferência de dados e/ou rescindir o contrato; + +(b) que não tem qualquer razão para crer que a legislação que lhe é aplicável o impede de respeitar as instruções recebidas do exportador de dados e as obrigações que lhe incumbem por força do contrato e que, no caso de haver uma alteração nesta legislação que possa ter um efeito adverso substancial nas garantias e obrigações conferidas pelas cláusulas, notificará imediatamente essa alteração ao exportador de dados, assim que tiver conhecimento, tendo neste caso o exportador de dados o direito de suspender a transferência de dados e/ou de rescindir o contrato; + +(c) que implementou as medidas de segurança técnicas e organizacionais especificadas no Apêndice 2 antes de processar os dados pessoais transferidos; + +(d) que irá notificar rapidamente o exportador de dados sobre: + +(i) qualquer pedido juridicamente vinculativo de divulgação dos dados pessoais por parte de uma autoridade competente para a aplicação da lei, a não ser que exista uma proibição em contrário, como uma proibição prevista no código penal para preservar a confidencialidade de uma investigação policial, + +(ii) qualquer acesso acidental ou não autorizado; e + +(iii) qualquer pedido recebido diretamente dos titulares de dados, sem responder a esse pedido, a não ser que tenha sido autorizado a fazê-lo; + +(e) em lidar rápida e adequadamente com todos os inquéritos do exportador de dados em relação ao processamento dos dados pessoais na questão da transferência de dados, e em cumprir com o conselho da autoridade de supervisão em relação ao processamento dos dados transferidos; + +(f) em caso de pedido por parte do exportador de dados para a submissão das instalações de processamento de dados a uma auditoria das atividades de processamento, em conformidade com as Cláusulas, que deve ser conduzida pelo exportador de dados ou um órgão de inspeção composto por membros independentes e em posse das requeridas qualificações profissionais vinculadas ao dever de confidencialidade, selecionado pelo exportador de dados, onde aplicável, e em concordância com a autoridade de supervisão; + +(g) disponibilizar ao titular dos dados, mediante pedido, um exemplar das cláusulas ou de qualquer contrato existente de subprocessamento, a menos que as Cláusulas ou o contrato contenham informações comerciais, caso em que poderá suprimir as informações comerciais, com exceção do Apêndice 2, que deve ser substituído por uma descrição sumária das medidas de segurança, no caso de o titular dos dados não poder obter um exemplar do exportador de dados; + +(h) que, em caso de subprocessamento, informou previamente o exportador de dados e obteve o seu consentimento escrito prévio; + +(i) que os serviços de processamento pelo subprocessador serão realizados de acordo com a Cláusula 11; e + +(j) enviar prontamente uma cópia de qualquer acordo de subprocessador concluído sob as Cláusulas para o exportador de dados. + +#### Cláusula 6: Responsabilidade +1. As partes concordam que qualquer titular de dados que tenha sofrido danos em consequência de qualquer violação das obrigações referidas na Cláusula 3 ou na Cláusula 11 por qualquer parte ou subprocessador tem o direito de receber compensação do exportador de dados pelos danos sofridos. + +2. Se um titular de dados não puder apresentar um pedido de indenização em conformidade com o parágrafo 1 contra o exportador de dados, decorrente de uma violação do importador de dados ou do seu subprocessador de qualquer uma de suas obrigações referidas na Cláusula 3 ou 11, porque o exportador de dados desapareceu ou deixou de existir perante a lei ou tornou-se insolvente, o importador de dados concorda que o titular dos dados poderá interpor uma reivindicação contra o importador de dados como se fosse o exportador de dados, a não ser que qualquer entidade sucessora tenha assumido todas as obrigações legais do exportador de dados por contrato de aplicação da lei. Nesse caso, o titular dos dados pode impor seus direitos contra essa entidade. O importador de dados não pode apoiar-se no descumprimento por um subprocessador das suas obrigações para se eximir de suas próprias responsabilidades. + +3. Se um titular de dados não puder apresentar uma reivindicação contra o exportador ou o importador de dados referido nos parágrafos 1 e 2, decorrente de uma violação por parte do subprocessador de qualquer uma das suas obrigações referidas na Cláusula 3 ou 11, porque tanto o exportador como o importador de dados desapareceram ou deixaram de existir perante a lei ou tornaram-se insolventes, o subprocessador concorda que o titular dos dados poderá interpor uma reivindicação contra o subprocessador de dados no que diz respeito às suas próprias operações de processamento nos termos das Cláusulas como se fosse o exportador ou o importador de dados, salvo se qualquer entidade sucessora tenha assumido todas as obrigações legais do exportador ou do importador de dados por contrato ou por exercício da lei. Nesse caso, a o titular dos dados poderá impor seus direitos contra tal entidade. A responsabilidade do subprocessador é limitada às suas próprias atividades de processamento de dados nos termos previstas nas Cláusulas. + +#### Cláusula 7: Mediação e jurisdição +1. O importador de dados concorda que, se o titular dos dados pode invocar contra ele direitos de terceiros beneficiários e/ou reivindicar compensação por dados de acordo com as Cláusulas, o importador de dados irá aceitar a decisão do titular de dados: + +(a) a remeter o litígio à mediação, por uma pessoa independente ou, quando aplicável, pela autoridade supervisora; + +(b) a remeter o litígio aos tribunais do Estado-Membro onde o exportador de dados está estabelecido. + +2. As partes concordam que a escolha feita pelo titular dos dados não prejudicará os seus direitos substantivos ou processuais de procurar recursos de acordo com as disposições da lei nacional ou internacional. + +#### Cláusula 8: Cooperação com as autoridades de supervisão +1. O exportador de dados concorda em depositar um exemplar deste contrato junto da autoridade de controle se esta assim requerer ou se a legislação de proteção de dados aplicável exigir. + +2. As partes concordam que a autoridade de supervisão tem o direito de realizar auditorias no importador de dados ou a qualquer subprocessador, que tenha o mesmo escopo e as mesmas condições das auditorias executadas no exportador de dados, em conformidade com a legislação de proteção de dados aplicável. + +3. O importador de dados deve prontamente informar o exportador de dados sobre a existência de legislação aplicável sobre tal ato, e de qualquer subprocessador que previna a condução de uma auditoria ao importador de dados, ou qualquer subprocessador, em conformidade com o parágrafo 2. Neste caso, o exportador de dados terá o direito de tomar as medidas previstas na Cláusula 5(b). + +#### Cláusula 9: Lei regente. +As Cláusulas devem ser regidas pela lei do Estado-Membro onde o exportador de dados estiver estabelecido. + +#### Cláusula 10: Variação do contrato +As partes comprometem-se a não alterar as Cláusulas. Isso não impede que as partes adicionem cláusulas de caráter comercial sempre que necessário, desde que as mesmas não contrariem a Cláusula. + +#### Cláusula 11: Subprocessamento +1. O importador de dados não deve subcontratar nenhuma de suas operações de processamento em nome do exportador de dados sob as Cláusulas sem o consentimento prévio por escrito do exportador de dados. Quando o importador de dados subcontratar suas obrigações sob as Cláusulas, com o consentimento do exportador, ele deverá fazê-lo somente por meio de um contrato por escrito com o subprocessador, que imponha a este as mesmas obrigações impostas ao importador de dados nos termos das Cláusulas. Nos casos em que o subcontratante não cumprir as suas obrigações de proteção de dados nos termos de tal contrato por escrito, o importador de dados permanecerá totalmente responsável perante o exportador de dados pelo desempenho das obrigações do subprocessador nos termos desse contrato. + +2. O contrato prévio por escrito entre o importador de dados e o subprocessador prevê também uma cláusula de beneficiário de terceiros, conforme estabelecido na Cláusula 3, para os casos em que o titular de dados não for capaz de interpor a reivindicação para a compensação referida no parágrafo 1 da Cláusula 6 contra o exportador ou o importador de dados porque eles desapareceram factualmente ou deixaram de existir perante lei ou tornaram-se insolventes, e nenhuma entidade sucessora assumiu todas as obrigações legais do exportador de dados ou importador de dados por contrato ou por operação da lei. Essa responsabilidade de terceiros do subprocessador estará limitada às suas próprias operações de processamento nos termos das Cláusulas. + +3. As disposições relativas aos aspectos de proteção de dados para o subprocessamento do contrato referido no parágrafo 1 serão regidas pela lei do Estado-Membro onde o exportador de dados estiver estabelecido. + +4. O exportador de dados deve manter uma lista dos acordos de subprocessamento concluídos sob as Cláusulas e notificados pelo importador de dados em conformidade com a Cláusula 5 (j), que deve ser atualizada pelo menos uma vez por ano. A lista deve estar disponível para a autoridade responsável pela supervisão da proteção de dados do exportador. + +#### Cláusula 12: Obrigação após a rescisão dos serviços de processamento de dados pessoais +1. As partes estão de acordo quanto à rescisão da prestação de serviços de processamento de dados, o importador de dados e o subprocessador, mediante a escolha do exportador de dados, devolverão todos os dados pessoais transferidos e as suas cópias ao exportador de dados ou destruirão todos os dados pessoais, e informarão ao exportador de dados que o procedimento foi realizado, a menos que a legislação imposta ao importador de dados os impeça de devolver ou de destruir a totalidade ou parte dos dados pessoais transferidos. Nesse caso, o importador de dados irá garantir a confidencialidade dos dados pessoais transferidos e não processará mais ativamente os dados pessoais transferidos. + +2. O importador de dados e o subprocessador garantem que, mediante solicitação do exportador de dados e/ou da autoridade supervisora, submeterão as suas instalações de processamento de dados a uma auditoria das medidas referidas no parágrafo 1. + +### Apêndice 1 das Cláusulas Contratuais Padrão +Exportador de dados: Cliente é o exportador de dados. + +**Importador de dados:** O importador de dados é o GitHub, Inc., produtor global de software e serviços. + +**Titulares dos dados:** Os titulares de dados incluem os representantes e usuários finais do exportador, incluindo funcionários, contratados, colaboradores e clientes do exportador de dados. Os titulares de dados também podem incluir indivíduos que tentam comunicar-se ou transferir informações pessoais aos usuários dos serviços fornecidos pelo importador de dados. O GitHub reconhece que, dependendo do uso do Serviço pelo Cliente, este pode optar por incluir dados pessoais de qualquer um dos tipos a seguir de titulares de dados nos Dados Pessoais do Cliente: + +- Empregados, contratados e trabalhadores temporários (atual, anterior, potencial) do exportador de dados; +- Dependentes do acima; +- Os colaboradores/pontos de contato do exportador de dados (pessoas físicas) ou funcionários, contratados ou trabalhadores temporários de colaboradores de entidades legais colaboradores/contactar pessoas (atual, potencial, anterior); +- Usuários (p. ex.: consumidores, clientes, pacientes, visitantes, etc.) e outros titulares de dados que são usuários dos serviços do exportador de dados; +- Parceiros, partes interessadas ou indivíduos que colaboram ativamente, comunicam-se ou, de outra forma, interagem com os funcionários do exportador de dados e/ou usam ferramentas de comunicação como aplicativos e sites fornecidos pelo exportador de dados; +- Partes interessadas ou indivíduos que interagem passivamente com o exportador de dados (por exemplo, porque são objeto de investigação, investigação ou mencionada em documentos ou correspondência de ou para o exportador de dados); ou +- Profissionais com prestígio profissional (por exemplo, médicos, advogados, notários, trabalhadores religiosos, etc.). + +**Categorias de dados:** Os dados pessoais transferidos incluídos em e-mails, documentos e outros dados de forma eletrônica no âmbito do Serviço. O GitHub reconhece que, dependendo do uso do Serviço pelo Cliente, este pode optar por incluir dados pessoais de qualquer uma das seguintes categorias nos Dados Pessoais do Cliente: +- Dados de autenticação (por exemplo, nome de usuário, e-mail, senha); +- Informações de contato (por exemplo, e-mail); +- Números de identificação únicos e assinaturas (endereços IP, identificador único em cookies de rastreamento ou tecnologia similar). +- Outras informações únicas de identificação. Os titulares dos dados podem incluir mais informações, como, por exemplo, nomes reais, imagens de avatar e outras informações pessoais; + +**Categorias especiais de dados (se apropriado):** O importador de dados não coleta ou processa intencionalmente nenhuma categoria especial de dados ao realizar seus serviços para o exportador de dados. + +No entanto, uma vez que o importador de dados fornece serviços de armazenamento e não controla as categorias de dados que armazena, o exportador de dados pode optar por transferir as categorias especiais de dados. Consequentemente, o exportador de dados é o único responsável por assegurar que cumpre todas as obrigações impostas por leis e regulamentos aplicáveis relativos à coleta e processamento de quaisquer categorias especiais de dados, incluindo a obtenção do consentimento explícito dos dados sujeitos antes de processar dados pessoais confidenciais. + +**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontratados: de acordo com o DPA, o importador de dados pode contratar outras empresas para prestar serviços limitados em nome do importador de dados, tais como fornecer suporte ao cliente. Esses subcontratantes terão a permissão de obter Dados Pessoais do Cliente apenas para fornecer os serviços que o importador de dados os manteve para fornecer, e são proibidos de usar os Dados Pessoais do Cliente para qualquer outra finalidade. + +### Apêndice 2 das Cláusulas Contratuais Padrão +Descrição das medidas de segurança técnicas e organizacionais implementadas pelo importador de dados, de acordo com as Cláusulas 4(d) e 5(c): + +**1. Equipe.** A equipe do importador de dados não processará os Dados Pessoais do Cliente sem autorização. A equipe é obrigada a manter a confidencialidade de quaisquer Dados Pessoais do Cliente e essa obrigação permanece mesmo após o fim do compromisso. + +**2. Contato de Privacidade de Dados.** Você pode entrar em contato com o encarregado da privacidade de dados do importador de dados no endereço abaixo: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA + +**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction. + +A assinatura do GitHub, Inc. aparece abaixo. + +Assinatura das Cláusulas Contratuais Padrão, Apêndice 1 e Apêndice 2 em nome do importador de dados + +![Captura de tela 20/07/2020 às 14h20m29s](/assets/images/help/site-policy/docusign-signature.png) + +Lynn Hashimoto, Chefe da área de Produtos & Departamento jurídico regulatório + +GitHub, Inc. diff --git a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md index cd402808e3..bf8aecbb75 100644 --- a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md +++ b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md @@ -192,7 +192,7 @@ De modo semelhante, os projetos no GitHub podem incluir Informações Pessoais d #### Organizações -Por meio de suas ações no GitHub, você poderá indicar a sua disposição em compartilhar suas Informações Pessoais de Usuário. Se você colaborar com ou se tornar integrante de uma Organização, os proprietários da Conta poderão receber suas Informações Pessoais de Usuário. Ao aceitar um convite para uma Organização, você receberá uma notificação sobre os tipos de informações que os proprietários poderão ver (para mais informações, consulteorganização <[Sobre Associação à Organização](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Se você aceitar um convite para uma Organização com um [domínio verificado](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain), os proprietários da Organização poderão ver seu(s) endereço(s) de e-mail completo(s) no(s) domínio(s) verificado(s) da Organização. +Por meio de suas ações no GitHub, você poderá indicar a sua disposição em compartilhar suas Informações Pessoais de Usuário. Se você colaborar com ou se tornar integrante de uma Organização, os proprietários da Conta poderão receber suas Informações Pessoais de Usuário. Ao aceitar um convite para uma Organização, você receberá uma notificação sobre os tipos de informações que os proprietários poderão ver (para mais informações, consulteorganização <[Sobre Associação à Organização](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Se você aceitar um convite para uma Organização com um [domínio verificado](/organizations/managing-organization-settings/verifying-your-organizations-domain), os proprietários da Organização poderão ver seu(s) endereço(s) de e-mail completo(s) no(s) domínio(s) verificado(s) da Organização. Observe que o GitHub poderá compartilhar seu nome de usuário, suas [Informações de Uso](#usage-information) e as [Informações do Dispositivo](#device-information) com a organização da qual você é integrante na medida que as suas informações pessoais sejam fornecidas apenas para investigar ou responder a um incidente de segurança que afeta ou compromete a segurança dessa organização em particular. @@ -321,7 +321,7 @@ No caso improvável de conflito entre você e o GitHub sobre a manipulação das ### Mudanças nesta Declaração de Privacidade -Embora grande parte das alterações sejam secundárias, o GitHub pode alterar esta Declaração de Privacidade ocasionalmente. Publicaremos uma notificação para os usuários no site sobre mudanças concretas feitas nesta Declaração de Privacidade pelo menos 30 dias antes de sua entrada em vigor. A notificação será exibida em nossa página inicial ou enviada por e-mail para o endereço de e-mail principal especificado na sua conta do GitHub. Também atualizaremos nosso [repositório da Política do Site](https://github.com/github/site-policy/), que registra e monitora todas as alterações feitas a esta política. Para outras mudanças nesta Declaração de Privacidade, incentivamos os usuários a [observar](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) ou verificar o nosso repositório de Política de Site com frequência. +Embora grande parte das alterações sejam secundárias, o GitHub pode alterar esta Declaração de Privacidade ocasionalmente. Publicaremos uma notificação para os usuários no site sobre mudanças concretas feitas nesta Declaração de Privacidade pelo menos 30 dias antes de sua entrada em vigor. A notificação será exibida em nossa página inicial ou enviada por e-mail para o endereço de e-mail principal especificado na sua conta do GitHub. Também atualizaremos nosso [repositório da Política do Site](https://github.com/github/site-policy/), que registra e monitora todas as alterações feitas a esta política. Para outras mudanças nesta Declaração de Privacidade, incentivamos os usuários a [observar](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) ou verificar o nosso repositório de Política de Site com frequência. ### Licença diff --git a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md index d8d33ac510..2cecad5852 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 @@ -13,7 +13,7 @@ topics: - legal --- -Entrada em vigor: **29 de janeiro de 2021** +Effective date: **April 2, 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. Para essa finalidade, disponibilizamos esta página, que detalha os [nossos subprocessadores](#github-subprocessors) e como usamos [cookies](#cookies-on-github). @@ -33,7 +33,6 @@ Quando compartilhamos suas informações com terceiros subprocessadores, tais co | 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 | -| Monday.com | Colaboração da equipe e plataforma de gerenciamento de projetos | Estados Unidos | Israel | | Nexmo | Provedor de notificação de SMS | Estados Unidos | Estados Unidos | | Salesforce.com | Gerenciamento de relacionamento com clientes | Estados Unidos | Estados Unidos | | Sentry.io | Provedor de monitoramento de aplicativo | 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 f8a0c6385b..16270e24eb 100644 --- a/translations/pt-BR/content/github/site-policy/index.md +++ b/translations/pt-BR/content/github/site-policy/index.md @@ -16,6 +16,7 @@ topics: {% 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-agreement-non-enterprise-customers %} {% link_in_list /global-privacy-practices %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} {% link_in_list /github-sponsors-additional-terms %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 69ae8043c4..efd711126d 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -24,7 +24,9 @@ Você pode definir uma meta para seus patrocínios. Para obter mais informaçõe ### Níveis de patrocínio -{% data reusables.sponsors.tier-details %} Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_sponsors %} para a sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Configurando {% data variables.product.prodname_sponsors %} para sua organização](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization), e "[Alterando suas camadas de patrocínio](/articles/changing-your-sponsorship-tiers)". +{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)." + +It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. ### Pagamentos de patrocínios @@ -34,5 +36,9 @@ Você pode definir uma meta para seus patrocínios. Para obter mais informaçõe Para obter mais informações, consulte "[Gerenciando seus pagamentos com o {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)". +### Compartilhando feedback sobre o {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.feedback %} + ### Leia mais - "[Perguntas frequentes com a equipe do {% data variables.product.prodname_sponsors %}](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" no {% data variables.product.prodname_blog %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md index 0dc90fcc3c..114e09f3dc 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -37,7 +37,7 @@ Para ser elegível para o {% data variables.product.prodname_matching_fund %}, v ### Compartilhando feedback sobre o {% data variables.product.prodname_sponsors %} -Esse é apenas o começo – adoraríamos saber sua opinião para garantir que o {% data variables.product.prodname_sponsors %} atenda às suas necessidades no futuro. Por favor, envie-nos seu feedback ou sugestões, entrando em contato com [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). +{% data reusables.sponsors.feedback %} ### Leia mais - "[Patrocinando contribuidores de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md index 0e42303a1b..24e0088437 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -15,6 +15,8 @@ Seus patrocinadores podem escolher se querem receber atualizações sobre seu tr Para contas de desenvolvedor patrocinado, a atualização virá do endereço de e-mail principal da sua conta de usuário. Se você habilitou a privacidade do endereço de e-mail, em sua conta de usuário, a atualização virá de `noreply@github.com`. Para organizações patrocinadas, a atualização virá do endereço de e-mail `noreply@github.com` da organização. Para obter mais informações, consulte "[Setting your commit email address](/articles/setting-your-commit-email-address)." +You can also contact any one-time sponsors who contributed within the last 30 days and enabled updates. + ### Entrar em contato com os patrocinadores {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md index faa380c150..c0c2b68e0e 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/index.md @@ -25,7 +25,7 @@ topics: {% 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 /managing-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 %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md index 380e65facc..73958b0b2e 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -13,6 +13,12 @@ Você pode definir uma meta de financiamento para a sua conta patrocinada e comp Sua meta pode definir um objetivo para o número de patrocinadores que você deseja ter ou a quantidade de dinheiro que você quer ganhar a cada mês. Você só pode definir em uma meta de cada vez. Depois de atingir uma meta, você pode definir outra meta. +{% note %} + +**Note:** Goals are intended to help people track momentum so only monthly sponsors contribute toward your goal. + +{% endnote %} + ### Definir uma meta {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md new file mode 100644 index 0000000000..519f845c9d --- /dev/null +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md @@ -0,0 +1,45 @@ +--- +title: Managing your sponsorship tiers +intro: 'Você pode adicionar uma nova camada de patrocínio, ou editar ou retirar uma camada existente.' +redirect_from: + - /articles/changing-your-sponsorship-tiers + - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +topics: + - sponsors +--- + +### Sobre as camadas de patrocínio + +{% data reusables.sponsors.tier-details %} + +{% data reusables.sponsors.maximum-tier %} + +### Adicionar uma camada + +{% 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 %} + +### Editando ou retirar uma camada + +{% 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 %} + +### Enabling tiers with custom amounts + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.enable-custom-amounts %} + +### Disabling tiers with custom amounts + +You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired. diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 99031fe2ce..e33d343da3 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -48,6 +48,7 @@ Para se juntar ao {% data variables.product.prodname_sponsors %} como colaborado {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Enviando informações bancárias @@ -73,7 +74,7 @@ Para obter mais informações sobre como configurar o Stripe Connect usando o Op ### Habilitar a autenticação de dois fatores (2FA, two-factor authentication) na sua conta do {% data variables.product.prodname_dotcom %} -Antes de sua organização se tornar uma organização patrocinada, você deve habilitar a 2FA em sua conta do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)". +Antes da sua organização se tornar uma organização patrocinada, você deve habilitar a 2FA na sua conta do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)". ### Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index e0e957c0fd..ab67841368 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -48,6 +48,7 @@ Depois de {% data variables.product.prodname_dotcom %} avaliar sua solicitação {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Enviando informações bancárias diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 3cfb444cdd..37e7f899d8 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -1,6 +1,6 @@ --- title: Patrocinando um colaborador de código aberto -intro: 'Você pode fazer um pagamento recorrente mensal a um desenvolvedor ou uma organização que projeta, cria ou mantém projetos de código aberto dos quais você depende.' +intro: 'You can make a one-time or monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' redirect_from: - /articles/sponsoring-a-developer - /articles/sponsoring-an-open-source-contributor @@ -24,11 +24,11 @@ Você pode patrocinar uma conta em nome de sua conta de usuário para investir e - Desenvolver a conscientização da marca como uma organização que valoriza o código aberto - Agradecer aos desenvolvedores de código aberto para a criação de bibliotecas que complementam os produtos que a sua organização oferece -Você pode usar um cartão de crédito para patrocinar uma conta em {% data variables.product.product_name %}. Se sua organização desejar pagar por fatura, [entre em contato conosco](https://support.github.com/contact/org-sponsors-waitlist). +You use your normal payment method to sponsor an account on {% data variables.product.product_name %}. Se sua organização desejar pagar por fatura, [entre em contato conosco](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". -Ao patrocinar uma conta usando um cartão de crédito, a alteração entrará em vigor imediatamente. {% data reusables.sponsors.prorated-sponsorship %} +When you sponsor an account the change is effective immediately, unless you are sponsoring on behalf of an organization that pays by invoice. {% data reusables.sponsors.prorated-sponsorship %} Your sponsorship is included in the next scheduled payment to the sponsored account. {% data reusables.sponsors.manage-updates-for-orgs %} @@ -53,6 +53,7 @@ Antes de poder patrocinar uma conta, você deve ter um endereço de e-mail verif - Para patrocinar um desenvolvedor, sob o nome do desenvolvedor, clique em **Patrocinador**. ![Botão Sponsor (Patrocinar)](/assets/images/help/profile/sponsor-button.png) - Para patrocinar uma organização clique em **Patrocinador** à direita do nome da organização. ![Botão Sponsor (Patrocinar)](/assets/images/help/sponsors/sponsor-org-button.png) 1. Opcionalmente, no lado direito da página, para patrocinar a conta em nome da sua organização, use o menu suspenso **Patrocinar como** e clique na organização. ![Menu suspenso para escolher a conta que você irá patrocinar como](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index 1a66878f1a..0117fdc0e4 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -1,89 +1,94 @@ --- -title: About the dependency graph -intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' +title: Sobre o gráfico de dependências +intro: 'Informações detalhadas sobre o gráfico de dependência, os ecossistemas que apoia e como determina quais pacotes um repositório depende.' versions: - free-pro-team: '*' - enterprise-server: '*' + enterprise-server: '<=2.22' +topics: + - repositories --- -### Dependency graph availability +### Disponibilidade do gráfico de dependências -The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} +O gráfico de dependências está disponível para todos{% if currentVersion == "free-pro-team@latest" %} os repositórios públicos{% endif %} que definem dependências em um ecossistema de pacote suportado usando um formato de arquivo suportado. {% if currentVersion == "free-pro-team@latest" %} Os administradores do repositório também podem configurar o gráfico de dependências para repositórios privados.{% endif %} {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### Sobre o gráfico de dependências -The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: +O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Para cada repositório, é exibido{% if currentVersion == "free-pro-team@latest" %}: -- Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} +- As dependências, os ecossistemas e os pacotes do qual depende +- Dependentes, os repositórios e pacotes que dependem dele{% else %} dependências, isto é, os ecossistemas e pacotes de que ele depende. O {% data variables.product.prodname_ghe_server %} não calcula informações sobre dependentes, repositórios e pacotes que dependem de um repositório.{% endif %} -When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. +Ao fazer push de um commit para {% data variables.product.product_name %} que altera ou adiciona um manifesto compatível ou um arquivo de bloqueio para o branch-padrão, o gráfico de dependências é atualizado automaticamente.{% if currentVersion == "free-pro-team@latest" %} Além disso, o gráfico é atualizado quando alguém faz push de uma alteração no repositório de uma de suas dependências.{% endif %} Para informações sobre os ecossistemas compatíveis e arquivos de manifesto, consulte "[ecossistemas de pacote compatíveis](#supported-package-ecosystems)" abaixo. {% if currentVersion == "free-pro-team@latest" %} -When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. 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)." +Ao criar um pull request que contém alterações para dependências direcionadas ao branch padrão, +{% data variables.product.prodname_dotcom %} usa o gráfico de dependências para adicionar revisões de dependências para o pull request. Eles indicam se as dependências contêm vulnerabilidades e, em caso afirmativo, a versão da dependência na qual a vulnerabilidade foi corrigida. Para obter mais informações, consulte "[Revisar as mudanças de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". {% endif %} -### Dependencies included +### Dependências incluídas -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +O gráfico de dependências inclui todas as dependências de um repositório detalhadas nos arquivos de manifesto e de bloqueio ou seu equivalente para ecossistemas compatíveis. Isto inclui: -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio +- Dependências indiretas dessas dependências diretas, também conhecidas como dependências transitórias ou subdependências -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +O gráfico de dependências identifica dependências indiretas{% if currentVersion == "free-pro-team@latest" %} explicitamente a partir de um arquivo de bloqueio ou verificando as dependências de suas dependências diretas. Para o gráfico mais confiável, você deve usar os arquivos de bloqueio (ou o equivalente deles), pois definem exatamente quais versões das dependências diretas e indiretas você usa atualmente. Se você usar arquivos de bloqueio, você também terá certeza de que todos os contribuidores do repositório usarão as mesmas versões, o que facilitará para você testar e depurar o código{% else %} dos arquivos de bloqueio{% endif %}. {% if currentVersion == "free-pro-team@latest" %} -### Dependents included +### Dependentes incluídos -For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} +Para repositórios públicos, apenas repositórios públicos que dependem dele ou de pacotes que publica são relatados. Essas informações não foram relatadas para repositórios privados.{% endif %} -### Using the dependency graph +### Usar o gráfico de dependências -You can use the dependency graph to: +Você pode usar o gráfico de dependências para: -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} -- See information about vulnerable dependencies in pull requests. 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 %} +- Explore os repositórios dos quais o seu código depende {% if currentVersion == "free-pro-team@latest" %} e aqueles que dependem dele {% endif %}. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)". {% if currentVersion == "free-pro-team@latest" %} +- Visualizar um resumo das dependências usadas nos repositórios da sua organização em um único painel. Para obter mais informações, consulte "[Visualizar informações na organização](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %} +- Ver e atualizar dependências vulneráveis no seu repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% if currentVersion == "free-pro-team@latest" %} +- Veja as informações sobre dependências vulneráveis em pull requests. Para obter mais informações, consulte "[Revisar as alterações de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)".{% endif %} -### Enabling the dependency graph +### Habilitar o gráfico de dependências -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}Para gerar um gráfico dependente, {% data variables.product.product_name %} precisa de acesso somente-leitura ao manifesto dependência e aos arquivos de bloqueios de um repositório. O gráfico de dependências é gerado automaticamente para todos os repositórios públicos e você pode optar por habilitá-lo para repositórios privados. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if enterpriseServerVersions contém currentVersion and currentVersion ver_gt "enterprise-server@2. 1" %}Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server){% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} Se o gráfico de dependências não estiver disponível no seu sistema, o administrador do site poderá habilitar o gráfico de dependências e os alertas de segurança. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". {% endif %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +Quando o gráfico de dependências é ativado pela primeira vez, todos manifesto e arquivos de bloqueio para ecossistemas suportados são analisados imediatamente. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Uma vez habilitado, o gráfico é atualizado automaticamente a cada push para o repositório{% if currentVersion == "free-pro-team@latest" %} e cada push para outros repositórios no gráfico{% endif %}. -### Supported package ecosystems +### Ecossistemas de pacote compatíveis -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +Os formatos recomendados definem explicitamente quais versões são usadas para todas as dependências diretas e indiretas. Se você usar esses formatos, seu gráfico de dependências será mais preciso. Ele também reflete a configuração da criação atual e permite que o gráfico de dependências relate vulnerabilidades em dependências diretas e indiretas.{% if currentVersion == "free-pro-team@latest" %} As dependências indiretas que são inferidas a partir de um arquivo de manifesto (ou equivalente) são excluídas das verificações de dependências vulneráveis.{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +{% if currentVersion == "free-pro-team@latest" %}Os ecossistemas listados abaixo são suportados pelo gráfico de dependência, {% data variables.product.prodname_dependabot_alerts %} e {% data variables.product.prodname_dependabot_security_updates %}.{% endif %} +| +{% if currentVersion ver_gt "enterprise-server@2.21" %}Os ecossistemas listados abaixo são suportados pelo gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}.{% endif %} +| Gerenciador de pacotes | Idiomas | Formatos recomendados | Todos os formatos compatíveis | +| ---------------------- | -------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | +| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | +| Maven | Java, Scala | `pom.xml` | `pom.xml` | +| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json` | +| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**Observação:** se você listar suas dependências de Python em um arquivo `setup.py`, será provável que não possamos analisar e listar cada dependência no seu projeto. {% endnote %} -### Further reading +### Leia mais -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia -- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} +- "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia +- "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} +- "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" +- "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index 48d1ad6287..0f0cd23caa 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -68,7 +68,7 @@ Para repositórios públicos, a vista de dependentes mostra como o repositório Os administradores de repositórios podem habilitar ou desabilitar o gráfico de dependências em repositórios privados. -Você também pode habilitar ou desabilitar o gráfico de dependências 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)". +Você também pode habilitar ou desabilitar o gráfico de dependências 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](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -109,7 +109,7 @@ Se um arquivo de manifesto ou de bloqueio não for processado, suas dependência ### Leia mais - "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- "[Visualizar ideias para sua organização](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Visualizar informações da organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Entender como o {% data variables.product.product_name %} usa e protege seus dados](/github/understanding-how-github-uses-and-protects-your-data)" {% endif %} diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md index 2b091f4867..7f4725dbe3 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors.md @@ -1,6 +1,6 @@ --- -title: Viewing a project's contributors -intro: 'You can see who contributed commits to a repository{% if currentVersion == "free-pro-team@latest" %} and its dependencies{% endif %}.' +title: Exibir contribuidores do projeto +intro: 'Você pode ver quem contribuiu com commits em um repositório{% if currentVersion == "free-pro-team@latest" %} e suas dependências{% endif %}.' redirect_from: - /articles/i-don-t-see-myself-in-the-contributions-graph/ - /articles/viewing-contribution-activity-in-a-repository/ @@ -10,38 +10,38 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - repositories --- -### About contributors +### Sobre contribuidores -You can view the top 100 contributors to a repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph. +Você pode ver os 100 principais colaboradores de um repositório{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}, incluindo os coautores do commit,{% endif %} no gráfico de contribuidores. Commits de merge e commits vazios não são contabilizados como contribuições para este gráfico. {% if currentVersion == "free-pro-team@latest" %} -You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. +Você também pode ver uma lista de pessoas que contribuíram para as dependências Python do projeto. Para acessar essa lista de contribuidores da comunidade, visite `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. {% endif %} -### Accessing the contributors graph +### Acessar o gráfico de contribuidores {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} -3. In the left sidebar, click **Contributors**. - ![Contributors tab](/assets/images/help/graphs/contributors_tab.png) -4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. - ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) +3. Na barra lateral esquerda, clique em **Contributors** (Contribuiddores). ![Aba de colaboradores](/assets/images/help/graphs/contributors_tab.png) +4. Como alternativa, para exibir os contribuidores durante um determinado período, clique no período desejado e arraste-o até que seja selecionado. ![Intervalo de tempo selecionado no gráfico de contribuidores](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) -### Troubleshooting contributors +### Solucionar problemas com contribuidores -If you don't appear in a repository's contributors graph, it may be because: -- You aren't one of the top 100 contributors. -- Your commits haven't been merged into the default branch. -- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}. +Se você não aparecer no gráfico de contribuidores de um repositório, pode ser que: +- Você não seja um dos 100 principais contribuidores. +- Não tenha sido feito merge dos seus commits no branch padrão. +- O endereço de e-mail que você usou para criar os commits não está conectado à sua conta em {% data variables.product.product_name %}. {% tip %} -**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)." +**Dica:** para listar todos os contribuidores de commit em um repositório, consulte "[Repositórios](/rest/reference/repos#list-contributors)". {% endtip %} -If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/articles/about-pull-requests)." +Se todos os seus commits no repositório estiverem em branches não padrão, você não estará no gráfico de contribuidores. Por exemplo, os commits no branch `gh-pages` só serão incluídos no gráfico se `gh-pages` for o branch padrão do repositório. Para que seja feito merge dos seus commits no branch padrão, você precisa criar uma pull request. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests)". -If the email address you used to author the commits is not connected to your account on {% data variables.product.product_name %}, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address){% if currentVersion != "github-ae@latest" %}" and "[Adding an email address to your {% data variables.product.product_name %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}." +Se o endereço de e-mail que você usou para criar os commits não estiver conectado à sua conta em {% data variables.product.product_name %}, seus commits não serão vinculados à sua conta e você não aparecerá no gráfico de contribuidores. Para obter mais informações, consulte "[Definir o seu endereço de e-mail de commit](/articles/setting-your-commit-email-address){% if currentVersion != "github-ae@latest" %}" e "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.product_name %} ](/articles/adding-an-email-address-to-your-github-account){% endif %}." diff --git a/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md b/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md index 6157615856..48440344f6 100644 --- a/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md +++ b/translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md @@ -11,7 +11,7 @@ topics: Se a sua conta usa um produto {% data variables.product.prodname_dotcom %} pago, você pode entrar em contato diretamente com {% data variables.contact.github_support %}. Se a sua conta usa {% data variables.product.prodname_free_user %} para contas de usuários e organizações, você pode entrar em contato com {% data variables.contact.contact_support %} para relatar problemas com a conta, de segurança e abusos. Para obter mais informações, consulte "[Sobre GitHub Support](/github/working-with-github-support/about-github-support)". -Se você usar o {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %} ou o {% data variables.product.premium_support_plan %}, você deve enviar tíquetes usando o {% data variables.contact.enterprise_portal %}. +If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)." ### Enviando um tíquete usando o {% data variables.contact.support_portal %} 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 4c0e060889..371c699ba2 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 @@ -1,6 +1,6 @@ --- -title: Basic writing and formatting syntax -intro: Create sophisticated formatting for your prose and code on GitHub with simple syntax. +title: Sintaxe básica de escrita e formatação no GitHub +intro: Crie formatação sofisticada para narração e código no GitHub com sintaxe simples. redirect_from: - /articles/basic-writing-and-formatting-syntax versions: @@ -9,62 +9,62 @@ versions: github-ae: '*' --- -### Headings +### Títulos -To create a heading, add one to six `#` symbols before your heading text. The number of `#` you use will determine the size of the heading. +Para criar um título, adicione de um a seis símbolos `#` antes do texto do título. O número de `#` que você usa determinará o tamanho do título. -``` -# The largest heading -## The second largest heading -###### The smallest heading +```markdown +# O título maior +## O segundo maior título +###### O título menor ``` -![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png) +![Títulos H1, H2 e H6 renderizados](/assets/images/help/writing/headings-rendered.png) -### Styling text +### Estilizar texto -You can indicate emphasis with bold, italic, or strikethrough text. +Você pode dar ênfase usando texto em negrito, itálico ou tachado. -| Style | Syntax | Keyboard shortcut | Example | Output | -| --- | --- | --- | --- | --- | -| Bold | `** **` or `__ __` | command/control + b | `**This is bold text**` | **This is bold text** | -| Italic | `* *` or `_ _` | command/control + i | `*This text is italicized*` | *This text is italicized* | -| Strikethrough | `~~ ~~` | | `~~This was mistaken text~~` | ~~This was mistaken text~~ | -| Bold and nested italic | `** **` and `_ _` | | `**This text is _extremely_ important**` | **This text is _extremely_ important** | -| All bold and italic | `*** ***` | | `***All this text is important***` | ***All this text is important*** | +| Estilo | Sintaxe | Atalho | Exemplo | Resultado | +| -------------------------- | ------------------ | ------------------- | -------------------------------------------- | ------------------------------------------ | +| Negrito | `** **` ou `__ __` | command/control + b | `**Esse texto está em negrito**` | **Esse texto está em negrito** | +| Itálico | `* *` ou `_ _` | command/control + i | `*Esse texto está em itálico*` | *Esse texto está em itálico* | +| Tachado | `~~ ~~` | | `~~Esse texto estava errado~~` | ~~Esse texto estava errado~~ | +| Negrito e itálico aninhado | `** **` e `_ _` | | `**Esse texto é _extremamente_ importante**` | **Esse texto é _extremamente_ importante** | +| Todo em negrito e itálico | `*** ***` | | `***Todo esse texto é importante***` | ***Todo esse texto é importante*** | -### Quoting text +### Citar texto -You can quote text with a `>`. +Você pode citar texto com um `>`. -``` -In the words of Abraham Lincoln: +```markdown +Nas palavras de Abraham Lincoln: > Pardon my French ``` -![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png) +![Texto citado renderizado](/assets/images/help/writing/quoted-text-rendered.png) {% tip %} -**Tip:** When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing `r`. You can quote an entire comment by clicking {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Quote reply**. For more information about keyboard shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts/)." +**Dica:** ao exibir uma conversa, você pode citar textos automaticamente em um comentário destacando o texto e digitando `r`. É possível citar um comentário inteiro clicando em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Quote reply** (Resposta à citação). Para obter mais informações sobre atalhos de teclado, consulte "[Atalhos de teclado](/articles/keyboard-shortcuts/)". {% endtip %} -### Quoting code +### Citar código -You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted. +Você pode chamar código ou um comando em uma frase com aspas simples. O texto entre as aspas não será formatado. -``` -Use `git status` to list all new or modified files that haven't yet been committed. +```markdown +Use 'git status' para listar todos os arquivos novos ou modificados que ainda não receberam commit. ``` -![Rendered inline code block](/assets/images/help/writing/inline-code-rendered.png) +![Bloco de código inline renderizado](/assets/images/help/writing/inline-code-rendered.png) -To format code or text into its own distinct block, use triple backticks. +Para formatar código ou texto no próprio bloco distinto, use aspas triplas. 
-Some basic Git commands are:
+Alguns comandos Git básicos são:
 ```
 git status
 git add
@@ -72,168 +72,168 @@ git commit
 ```
-![Rendered code block](/assets/images/help/writing/code-block-rendered.png) +![Bloco de código renderizado](/assets/images/help/writing/code-block-rendered.png) -For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)." +Para obter mais informações, consulte "[Criar e destacar blocos de código](/articles/creating-and-highlighting-code-blocks)". ### Links -You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. You can also use the keyboard shortcut `command + k` to create a link. +Você pode criar um link inline colocando o texto do link entre colchetes `[ ]` e, em seguida, o URL entre parênteses `( )`. Também é possível usar o atalho de teclado `command + k` para criar um link. -`This site was built using [GitHub Pages](https://pages.github.com/).` +`Este site foi construído usando [GitHub Pages](https://pages.github.com/).` -![Rendered link](/assets/images/help/writing/link-rendered.png) +![Link renderizado](/assets/images/help/writing/link-rendered.png) {% tip %} -**Tip:** {% data variables.product.product_name %} automatically creates links when valid URLs are written in a comment. For more information, see "[Autolinked references and URLS](/articles/autolinked-references-and-urls)." +**Dica:** o {% data variables.product.product_name %} cria links automaticamente quando URLs válidos são escritos em um comentário. Para obter mais informações, consulte "[Referências e URLs vinculados automaticamente](/articles/autolinked-references-and-urls)". {% endtip %} -### Section links +### Links de seção {% data reusables.repositories.section-links %} -### Relative links +### Links relativos {% data reusables.repositories.relative-links %} -### Lists +### Listas -You can make an unordered list by preceding one or more lines of text with `-` or `*`. +Você pode criar uma lista não ordenada precedendo uma ou mais linhas de texto com `-` ou `*`. -``` +```markdown - George Washington - John Adams - Thomas Jefferson ``` -![Rendered unordered list](/assets/images/help/writing/unordered-list-rendered.png) +![Lista não ordenada renderizada](/assets/images/help/writing/unordered-list-rendered.png) -To order your list, precede each line with a number. +Para ordenar a lista, coloque um número na frente de cada linha. -``` +```markdown 1. James Madison 2. James Monroe 3. John Quincy Adams ``` -![Rendered ordered list](/assets/images/help/writing/ordered-list-rendered.png) +![Lista ordenada renderizada](/assets/images/help/writing/ordered-list-rendered.png) -#### Nested Lists +#### Listas aninhadas -You can create a nested list by indenting one or more list items below another item. +Você pode criar uma lista aninhada recuando um ou mais itens da lista abaixo de outro item. -To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [Atom](https://atom.io/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (`-` or `*`) lies directly below the first character of the text in the item above it. +Para criar uma lista aninhada usando o editor web do {% data variables.product.product_name %} ou um editor de texto que usa uma fonte monoespaçada, como o [Atom](https://atom.io/), você pode alinhar sua lista visualmente. Digite caracteres de espaço na fonte do item da lista aninhada, até que o caractere de marcador da lista (`-` ou `*`) fique diretamente abaixo do primeiro caractere do texto no item acima dele. -``` -1. First list item - - First nested list item - - Second nested list item +```markdown +1. Primeiro item da lista + - Primeiro item de lista aninhado + - Segundo item de lista aninhada ``` -![Nested list with alignment highlighted](/assets/images/help/writing/nested-list-alignment.png) +![Lista aninhada com alinhamento destacado](/assets/images/help/writing/nested-list-alignment.png) -![List with two levels of nested items](/assets/images/help/writing/nested-list-example-1.png) +![Lista com dois níveis de itens aninhados](/assets/images/help/writing/nested-list-example-1.png) -To create a nested list in the comment editor on {% data variables.product.product_name %}, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item. +Para criar uma lista aninhada no editor de comentários do {% data variables.product.product_name %}, que não usa uma fonte monoespaçada, você pode observar o item da lista logo acima da lista aninhada e contar o número de caracteres que aparecem antes do conteúdo do item. Em seguida, digite esse número de caracteres de espaço na fonte do item da linha aninhada. -In this example, you could add a nested list item under the list item `100. First list item` by indenting the nested list item a minimum of five spaces, since there are five characters (`100. `) before `First list item`. +Neste exemplo, você pode adicionar um item de lista aninhada abaixo do item de lista `100. Primeiro item da lista` recuando o item da lista aninhada com no mínimo cinco espaços, uma vez que há cinco caracteres (`100.`) antes de `Primeiro item da lista`. -``` -100. First list item - - First nested list item +```markdown +100. Primeiro item da lista + - Primeiro item da lista aninhada ``` -![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png) +![Lista com um item de lista aninhada](/assets/images/help/writing/nested-list-example-3.png) -You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven spaces (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. +Você pode criar vários níveis de listas aninhadas usando o mesmo método. Por exemplo, como o primeiro item da lista aninhada tem sete espaços (`␣␣␣␣␣-␣`) antes do conteúdo da lista aninhada `Primeiro item da lista aninhada`, você precisaria recuar o segundo item da lista aninhada com sete espaços. -``` -100. First list item - - First nested list item - - Second nested list item +```markdown +100. Primeiro item da lista + - Primeiro item da lista aninhada + - Segundo item da lista aninhada ``` -![List with two levels of nested items](/assets/images/help/writing/nested-list-example-2.png) +![Lista com dois níveis de itens aninhados](/assets/images/help/writing/nested-list-example-2.png) -For more examples, see the [GitHub Flavored Markdown Spec](https://github.github.com/gfm/#example-265). +Para obter mais exemplos, consulte a [Especificação de markdown em estilo GitHub](https://github.github.com/gfm/#example-265). -### Task lists +### Listas de tarefas {% data reusables.repositories.task-list-markdown %} -If a task list item description begins with a parenthesis, you'll need to escape it with `\`: +Se a descrição de um item da lista de tarefas começar com parênteses, você precisará usar `\` para escape: -`- [ ] \(Optional) Open a followup issue` +`- [ ] \(Optional) Abrir um problema de acompanhamento` -For more information, see "[About task lists](/articles/about-task-lists)." +Para obter mais informações, consulte "[Sobre listas de tarefas](/articles/about-task-lists)". -### Mentioning people and teams +### Mencionar pessoas e equipes -You can mention a person or [team](/articles/setting-up-teams/) on {% data variables.product.product_name %} by typing `@` plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando `@` mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. Para obter mais informações sobre notificações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." -`@github/support What do you think about these updates?` +`@github/suporte O que você acha dessas atualizações?` -![Rendered @mention](/assets/images/help/writing/mention-rendered.png) +![@menção renderizada](/assets/images/help/writing/mention-rendered.png) -When you mention a parent team, members of its child teams also receive notifications, simplifying communication with multiple groups of people. For more information, see "[About teams](/articles/about-teams)." +Quando você menciona uma equipe principal, os integrantes de suas equipes secundárias também recebem notificações, simplificando a comunicação com vários grupos de pessoas. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)". -Typing an `@` symbol will bring up a list of people or teams on a project. The list filters as you type, so once you find the name of the person or team you are looking for, you can use the arrow keys to select it and press either tab or enter to complete the name. For teams, enter the @organization/team-name and all members of that team will get subscribed to the conversation. +Digitar um símbolo `@` chamará uma lista de pessoas ou equipes em um projeto. A lista é filtrada à medida que você digita. Portanto, assim que você achar o nome da pessoa ou da equipe que está procurando, use as teclas de seta para selecioná-lo e pressione tab ou enter para completar o nome. Para equipes, digite nome da @organização/equipe e todos os integrantes dessa equipe serão inscritos na conversa. -The autocomplete results are restricted to repository collaborators and any other participants on the thread. +Os resultados do preenchimento automático são restritos aos colaboradores do repositório e qualquer outro participante no thread. -### Referencing issues and pull requests +### Fazer referências a problemas e pull requests -You can bring up a list of suggested issues and pull requests within the repository by typing `#`. Type the issue or pull request number or title to filter the list, and then press either tab or enter to complete the highlighted result. +Você pode trazer à tona uma lista de problemas e pull requests sugeridos no repositório digitando `#`. Digite o número ou o título do problema ou da pull request para filtrar a lista e, em seguida, pressione tab ou enter para completar o resultado destacado. -For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)." +Para obter mais informações, consulte "[Referências e URLs vinculados automaticamente](/articles/autolinked-references-and-urls)". -### Referencing external resources +### Fazer referência a recursos externos {% data reusables.repositories.autolink-references %} -### Content attachments +### Anexos de conteúdo -Some {% data variables.product.prodname_github_app %}s provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. {% data variables.product.product_name %} renders the information provided by the app under the URL in the body or comment of an issue or pull request. +Alguns {% data variables.product.prodname_github_app %}s fornecem informações no {% data variables.product.product_name %} para URLs que são vinculados aos respectivos domínios registrados. O {% data variables.product.product_name %} renderiza as informações fornecidas pelo app sob o URL no texto ou comentário de um problema ou uma pull request. -![Content attachment](/assets/images/help/writing/content-attachment.png) +![Anexo de conteúdo](/assets/images/github-apps/content_reference_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 %} +Para ver os anexos de conteúdo, é necessário ter um {% data variables.product.prodname_github_app %} que use a API de anexos de conteúdo instalada no repositório.{% if currentVersion == "free-pro-team@latest" %} Para mais informações, consulte "[Instalar um aplicativo na sua conta pessoal](/articles/installing-an-app-in-your-personal-account)" e "[Instalar um aplicativo na sua organização](/articles/installing-an-app-in-your-organization).{% endif %} -Content attachments will not be displayed for URLs that are part of a markdown link. +Os anexos de conteúdo não serão exibidos para URLs que fazem parte de um link markdown. -For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)." +Para obter mais informações sobre como compilar um {% data variables.product.prodname_github_app %} que use anexos de conteúdo, consulte "[Usar anexos de conteúdo](/apps/using-content-attachments)". -### Using emoji +### Usar emoji -You can add emoji to your writing by typing `:EMOJICODE:`. +Você pode adicionar emoji à sua escrita digitando `:EMOJICODE:`. -`@octocat :+1: This PR looks great - it's ready to merge! :shipit:` +`@octocat :+1: Este PR parece ótimo - está pronto para o merge! :shipit:` -![Rendered emoji](/assets/images/help/writing/emoji-rendered.png) +![Emoji renderizado](/assets/images/help/writing/emoji-rendered.png) -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. +Digitar `:` trará à tona uma lista de emojis sugeridos. A lista será filtrada à medida que você digita. Portanto, assim que encontrar o emoji que estava procurando, pressione **Tab** ou **Enter** para completar o resultado destacado. -For a full list of available emoji and codes, check out [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com). +Para obter uma lista completa dos emojis e códigos disponíveis, confira [a lista de emojis](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md). -### Paragraphs +### Parágrafos -You can create a new paragraph by leaving a blank line between lines of text. +Você pode criar um parágrafo deixando uma linha em branco entre as linhas de texto. -### Ignoring Markdown formatting +### Ignorar formatação markdown -You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character. +Para informar ao {% data variables.product.product_name %} que deve ignorar a formatação markdown (ou usar escape nela), anteceda o caractere markdown com `\`. -`Let's rename \*our-new-project\* to \*our-old-project\*.` +`Vamos renomear \*our-new-project\* para \*our-old-project\*.` -![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png) +![Caractere com escape renderizado](/assets/images/help/writing/escaped-character-rendered.png) -For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)." +Para obter mais informações, consulte "[Sintaxe markdown](https://daringfireball.net/projects/markdown/syntax#backslash)" de Daring Fireball. -### Further reading +### Leia mais -- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) -- "[About writing and formatting on GitHub](/articles/about-writing-and-formatting-on-github)" -- "[Working with advanced formatting](/articles/working-with-advanced-formatting)" -- "[Mastering Markdown](https://guides.github.com/features/mastering-markdown/)" +- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/) +- "[Sobre escrita e formatação no GitHub](/articles/about-writing-and-formatting-on-github)" +- "[Trabalhar com formatação avançada](/articles/working-with-advanced-formatting)" +- "[Dominar o markdown](https://guides.github.com/features/mastering-markdown/)" 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 df4494e932..be7ec5b31a 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: 'Você pode criar dois tipos de gists: {% if currentVersion == "github-ae@latest" %}internos{% else %}públicos{% endif %} e secretos. Crie um gist {% if currentVersion == "github-ae@latest" %}interno{% else %}um público{% endif %} se você estiver pronto para compartilhar suas ideias com {% if currentVersion == "github-ae@latest" %}os integrantes corporativos{% else %}o mundo{% endif %} ou um gist secreto se você não estiver pronto.' 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" %}Se você estiver conectado em {% data variables.product.product_name %} quando{% else %}Quando{% endif %} criar um gist, este será associado à sua conta e você irá vê-lo na sua lista de gists ao acessar o seu {% 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 %} +Os gists podem ser {% if currentVersion == "github-ae@latest" %}internos{% else %}públicos{% endif %} ou segredo. {% se a versão atual == "github-ae@latest" %} Os gists internos{% else %}Públicos{% endif %} aparecem em {% data variables.gists.discover_url %}, onde {% se a correnteVersion == "github-ae@latest" %}integrantes corporativos{% else %}pessoas{% endif %} podem pesquisar novos gistas à medida que 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. -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. Os grupos de segredos não são privados. Se você enviar a URL de um gist de segredo para {% if currentVersion == "github-ae@latest" %}outro integrante corporativo{% else %}um amigo {% endif %}, eles poderão vê-lo. No entanto, se {% if currentVersion == "github-ae@latest" %}qualquer outro integrante corporativo{% else %}alguém que você não conhece{% endif %} descobrir a URL, eles também poderão ver o 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). + +{% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} @@ -31,7 +33,7 @@ Se o administrador do site tiver desabilitado o modo privado, você também pode Você receberá uma notificação quando: - Você for o autor de um gist. - Alguém mencionar você em um gist. -- Você assinar um gist, clicando em **Subscribe** (Assinar) no topo de qualquer gist. +- You subscribe to a gist, by clicking **Subscribe** at the top of any gist. {% if currentVersion == "free-pro-team@latest" or 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). +Você pode descobrir gists {% if currentVersion == "github-ae@latest" %}internos{% else %}públicos{% endif %} que outros criaram, acessando {% data variables.gists.gist_homepage %} e clicando em **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). 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). @@ -53,13 +55,15 @@ O gist permite mapeamento de arquivos geoJSON. Esses mapas são exibidos em gist ### Criar um gist -Você também pode arrastar e soltar um arquivo de texto da sua área de trabalho diretamente no editor do gist. +Follow the steps below to create a gist. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% note %} Você também pode criar um gist usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`gh gist cria`](https://cli.github.com/manual/gh_gist_create)" na documentação do {% data variables.product.prodname_cli %}. +Alternatively, you can drag and drop a text file from your desktop directly into the editor. + {% endnote %} {% endif %} @@ -67,14 +71,8 @@ Você também pode criar um gist usando o {% data variables.product.prodname_cli 2. Navegue até sua {% data variables.gists.gist_homepage %}. 3. Digite uma descrição opcional e o nome do seu gist. ![Descrição do nome do gist](/assets/images/help/gist/gist_name_description.png) -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) +4. Type the text of your gist into the gist text box. ![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) +5. Opcionalmente, para criar {% se a correnteVersion == "github-ae@latest" %}um gist interno{% else %}um público{% endif %}, clique em {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, clique em **Criar gist {% se a correnteVersion == "github-ae@latest" %}interno{% else %}público{% endif %}**. ![Menu suspenso para selecionar a visibilidade do gist]{% 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 %} - {% note %} - - **Observação:** {% data reusables.gist.cannot-convert-public-gists-to-secret %} - - {% endnote %} +6. Clique em **Criar Gist secreto** ou **Criar gist{% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %}**. ![Botão para criar gist](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/pt-BR/content/index.md b/translations/pt-BR/content/index.md index 0eb88fb20a..c62b6ab036 100644 --- a/translations/pt-BR/content/index.md +++ b/translations/pt-BR/content/index.md @@ -13,5 +13,43 @@ featuredLinks: - /github/getting-started-with-github/managing-remote-repositories - /github/working-with-github-pages versions: '*' +children: + - github + - administrador + - organizations + - code-security + - ações + - pacotes + - developers + - rest + - graphql + - insights + - discussões + - comunidades + - Páginas + - educação + - desktop + - early-access +externalProducts: + cli: + id: cli + name: GitHub CLI + href: 'https://cli.github.com/manual' + external: true + atom: + id: atom + name: Atom + href: 'https://atom.io/docs' + external: true + electron: + id: electron + name: Electron + href: 'https://electronjs.org/docs' + external: true + codeql: + id: codeql + name: 'CodeQL' + href: 'https://codeql.github.com/docs' + external: true --- diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md new file mode 100644 index 0000000000..644177b4d3 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -0,0 +1,33 @@ +--- +title: Sobre organizações +intro: As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança. +redirect_from: + - /articles/about-organizations + - /github/setting-up-and-managing-organizations-and-teams/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} +### Organizações e contas corporativas + +As contas corporativas permitem que proprietários gerenciem centralmente a política e a cobrança para várias organizações do {% data variables.product.prodname_dotcom_the_website %}. + +Para organizações que pertencem a uma conta corporativa, a cobrança é gerenciada no nível da conta corporativa e as configurações de cobrança não estão disponíveis no nível da organização. Os proprietários de empresa podem definir a política para todas as organizações na conta corporativa ou permitir que os proprietários da organização definam a política no nível da organização. Os proprietários da organização não podem alterar as configurações aplicadas à sua organização no nível da conta corporativa. Se você tiver dúvidas sobre uma política ou configuração da sua organização, entre em contato com o proprietário da conta corporativa. + +{% data reusables.gated-features.enterprise-accounts %} + +{% data reusables.organizations.org-ownership-recommendation %} Para obter mais informações, consulte "[Manter a continuidade da propriedade para sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)". + +### Termos de serviços e proteção de dados para organizações + +Uma entidade, como uma empresa, não lucrativa, ou um grupo, pode concordar com os Termos de serviço padrão ou os Termos de serviço corporativos para a respectiva organização. Para obter mais informações, consulte "[Atualizar para os Termos de serviço corporativos](/articles/upgrading-to-the-corporate-terms-of-service)". + +{% endif %} diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md new file mode 100644 index 0000000000..b87e08e1b9 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -0,0 +1,49 @@ +--- +title: Sobre o painel da sua organização +intro: 'Como um integrante da organização, você pode visitar o painel da sua organização durante todo o dia para se manter atualizado sobre atividades recentes e acompanhar problemas e pull requests nos quais está trabalhando ou seguindo na organização.' +redirect_from: + - /articles/about-your-organization-dashboard + - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Acessar o painel da sua organização + +{% data reusables.dashboard.access-org-dashboard %} + +### Encontrar sua atividade recente + +Na seção "Recent activity" (Atividade recente) do feed de notícias, você pode encontrar e acompanhar problemas e pull requests recém-atualizados na organização. + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### Encontrar repositórios em sua organização + +Na barra lateral esquerda do painel, é possível acessar os principais repositórios da sua organização nos quais você está ativo. + +![Lista de repositórios em que você é mais ativo na sua organização](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) + +### Permanecer atualizado com a atividade da organização + +Na seção "All activity" (Todas as atividades) do seu feed de notícias, você pode ver atualizações de outras equipes e repositórios em sua organização. + +A seção "All activity" (Todas as atividades) mostra todas as últimas atividades na organização, inclusive atividades em repositórios que você não assina e de pessoas que você não está seguindo. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Inspecionar e não inspecionar repositórios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" e "[Seguindo pessoas](/articles/following-people)." + +Por exemplo, o feed de notícias da organização mostra atualizações quando alguém na organização: + - Cria um branch. + - Fazer comentários em um problema ou pull request. + - Envia um comentário de revisão de pull request. + - Bifurca um repositório. + - Cria uma página wiki. + - Faz push de commits.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contém currentVersion %} + - Cria um repositório público.{% endif %} + +### Outras informações + +- "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)" diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md new file mode 100644 index 0000000000..e6b8ba162c --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -0,0 +1,26 @@ +--- +title: Sobre o feed de notícias da sua organização +intro: Você pode usar o feed de notícias da sua organização para se manter atualizado com atividades recentes nos repositórios de propriedade da organização. +redirect_from: + - /articles/news-feed/ + - /articles/about-your-organization-s-news-feed + - /articles/about-your-organizations-news-feed + - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +O feed de notícias de uma organização mostra a atividade de outras pessoas nos repositórios que pertencem a essa organização. Você pode usar o feed de notícias da sua organização para ver quando alguém abre, fecha ou faz merge de um problema ou uma pull request, cria ou exclui um branch, cria uma tag ou versão, comenta sobre um problema, uma pull request, ou faz commit, ou faz push de novos commits no {% data variables.product.product_name %}. + +### Acessar o feed de notícias da sua organização + +1. {% data variables.product.signin_link %} na sua conta do {% data variables.product.product_name %}. +2. Abra o seu {% data reusables.user_settings.personal_dashboard %}. +3. Clique no alternador de contexto da conta no canto superior esquerdo da página. ![Botão do alternador de contexto no Enterprise](/assets/images/help/organizations/account_context_switcher.png) +4. Selecione uma organização no menu suspenso.{% 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/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md new file mode 100644 index 0000000000..29c52b3c3d --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -0,0 +1,34 @@ +--- +title: Acessar as configurações da organização +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 + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings +intro: 'A página de configurações da conta da organização fornece várias maneiras de gerenciar a conta, como cobrança, associação a equipes e configurações do repositório.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Dica:** somente proprietários da organização e gerentes de cobrança podem ver e alterar as informações de cobrança e configurações da conta para uma organização. {% 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/pt-BR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000..247a0aa931 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md @@ -0,0 +1,28 @@ +--- +title: Criar uma organização do início +intro: Crie uma organização para aplicar permissões de acesso refinadas aos repositórios. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /articles/creating-a-new-organization-from-scratch + - /admin/user-management/creating-organizations + - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch +topics: + - organizations + - teams +--- + +Quando você cria uma organização do zero, ela não tem repositórios associados a ela. Para obter mais informações sobre como adicionar repositórios à sua organização, consulte "[Criar um repositório](/articles/creating-a-new-repository)" e "[Transferir um repositório](/articles/transferring-a-repository)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Siga as instruções para criar sua organização. {% if currentVersion == "free-pro-team@latest" %}Para obter mais informações sobre os planos disponíveis para a sua equipe, consulte "[ produtos de {% data variables.product.prodname_dotcom %}](/articles/githubs-products)".{% endif %} + +### Leia mais + +{% if currentVersion == "free-pro-team@latest" %} +- "[Configurar seu e-mail de cobrança](/articles/setting-your-billing-email)"{% endif %} +- "[Sobre organizações](/articles/about-organizations)" diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md new file mode 100644 index 0000000000..4943c70c03 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md @@ -0,0 +1,22 @@ +--- +title: Colaborar com grupos e organizações +intro: Os grupos de pessoas podem colaborar em muitos projetos ao mesmo tempo nas contas da organização. +redirect_from: + - /articles/creating-a-new-organization-account/ + - /articles/collaborating-with-groups-in-organizations + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000..5efc918c62 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -0,0 +1,50 @@ +--- +title: Exibir informações da organização +intro: 'As informações da organização fornecem dados sobre a atividade, as contribuições e as dependências dela.' +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/viewing-insights-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Todos os integrantes de uma organização podem exibir informações da organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization)". + +Você pode usar informações de atividade da organização para entender melhor como os integrantes da sua organização estão usando o {% data variables.product.product_name %} para colaborar e trabalhar no código. As informações de dependência podem ajudar você a monitorar, reportar e agir de acordo com o uso de código aberto da organização. + +### Exibir informações de atividade da organização + +{% note %} + +**Observação:** As ideias da atividade da organização estão atualmente na versão beta pública e são sujeitas a alterações. + +{% endnote %} + +Com as informações de atividade da organização, é possível exibir visualizações de dados semanais, mensais e anuais de toda a organização ou de repositórios específicos, como atividade de pull requests e problemas, principais linguagens usadas e dados cumulativos sobre onde os integrantes da organização passam o tempo. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. No nome da organização, clique em {% octicon "graph" aria-label="The bar graph icon" %} **Insights** (Informações). ![Clique na guia Insights (Informações) da organização](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Como alternativa, no canto superior direito da página, opte por exibir dados do período de **1 semana**, **1 mês** ou **1 ano** mais recente. ![Escolha o período para visualizar informações da organização](/assets/images/help/organizations/org-insights-time-period.png) +5. Ou, no canto superior direito da página, opte por exibir dados de até três repositórios e clique em **Apply** (Aplicar). ![Escolha os repositórios para visualizar informações da organização](/assets/images/help/organizations/org-insights-repos.png) + +### Exibir informações de dependência da organização +Com as informações de dependência, é possível visualizar vulnerabilidades, licenças e outras informações importantes dos projetos de código aberto dos quais a sua organização depende. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. No nome da organização, clique em {% octicon "graph" aria-label="The bar graph icon" %} **Insights** (Informações). ![Guia Insights (Informações) na principal barra de navegação da organização](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Clique em **Dependencies** (Dependências) para exibir as que pertencem a esta organização. ![Guia Dependencies (Dependências) na principal barra de navegação da organização](/assets/images/help/organizations/org-insights-dependencies-tab.png) +5. Para exibir informações de dependência para todas as suas organizações do {% data variables.product.prodname_ghe_cloud %}, clique em **My organizations** (Minhas organizações). ![Botão My organizations (Minhas organizações) na guia Dependencies (Dependências)](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) +6. Você pode clicar nos resultados dos gráficos **Consultorias de segurança abertas** e **Licenças** para filtrar por um status de vulnerabilidade, uma licença ou uma combinação dos dois. ![Gráficos de "vulnerabilidades das minhas organizações"](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +7. Também pode clicar em {% octicon "package" aria-label="The package icon" %} **Dependents** (Dependentes) ao lado de cada vulnerabilidade para ver quais dependentes na organização estão usando cada biblioteca. ![Dependentes vulneráveis em My organizations (Minhas organizações)](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) + +### Leia mais + - "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)" + - "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" + - "[Alterar a visibilidade das informações de dependência da organização](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)" + - "[Aplicar uma política nas informações de dependência de sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)". diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md new file mode 100644 index 0000000000..952a61de23 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -0,0 +1,49 @@ +--- +title: Sobre discussões de equipe +intro: 'Sua equipe pode planejar em conjunto, atualizar uns aos outros ou falar sobre qualquer tópico que desejar em postagens de discussão na página de equipe em uma organização.' +redirect_from: + - /articles/about-team-discussions + - /github/building-a-strong-community/about-team-discussions + - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidade +--- + +{% data reusables.organizations.team-discussions-purpose %} + +Qualquer integrante da organização pode postar na página da equipe ou participar de uma discussão pública. {% data reusables.organizations.team-discussions-permissions %} + +![Guia Discussions (Discussões) da página de equipe com discussões públicas e privadas](/assets/images/help/organizations/team-page-discussions-tab.png) + +Você pode se vincular a qualquer discussão de equipe para fazer referência a ela em qualquer lugar. É possível fixar postagens importantes na página da equipe para referência rápida posterior. Para obter mais informações, consulte "[Fixar uma discussão de equipe](/organizations/collaborating-with-your-team/pinning-a-team-discussion)". + +![Guia de discussões fixada da página de equipe com discussão fixada](/assets/images/help/organizations/team-discussions-pinned.png) + +{% data reusables.organizations.team-discussions-default %} Os proprietários podem desabilitar as discussões de equipe para a organização inteira. Para obter mais informações, consulte "[Desabilitar discussões de equipe para sua organização](/articles/disabling-team-discussions-for-your-organization)". + +### Notificações para discussões de equipe + +Quando alguém posta ou responde a uma discussão pública na página de uma equipe, os integrantes da equipe e os integrantes de qualquer equipe secundária recebem notificações da web ou de e-mail. Quando alguém posta ou responde a uma discussão privada na página de uma equipe, somente os integrantes da equipe recebem notificações. + +{% tip %} + +**Dica:** dependendo das suas configurações de notificação, você receberá atualizações por e-mail, pela página de notificações da web no {% data variables.product.product_name %}, ou por ambos. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Sobre notificações de e-mail](/github/receiving-notifications-about-activity-on-github/about-email-notifications)e "[Sobre notificações da web](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." + +{% endtip %} + +Por padrão, se seu nome de usuário for mencionado em uma discussão de equipe, você receberá notificações para a postagem mencionando seu nome de usuário e todas as respostas a essa postagem. Além disso, por padrão, se você responder a uma postagem, notificações serão enviadas para outras respostas à postagem. + +Para desativar notificações de discussões de equipe, você pode cancelar a assinatura de uma postagem de discussão específica ou alterar as configurações de notificação para cancelar a inspeção ou ignorar completamente discussões de uma equipe específica. É possível assinar para receber notificações de uma postagem de discussão específica se você estiver cancelando a inspeção de discussões dessa equipe. + +Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 0" %}"[Visualizar suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Assinar e cancelar a assinatura das notificações](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" e "[Equipes aninhadas](/articles/about-teams/#nested-teams)". + +### Leia mais + +- "[Sobre conversas no {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)" +- "[Sobre equipes](/articles/about-teams)" +- "[Criar uma discussão de equipe](/organizations/collaborating-with-your-team/creating-a-team-discussion)" +- "[Editar ou excluir uma discussão de equipe](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md new file mode 100644 index 0000000000..b825d77c01 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md @@ -0,0 +1,30 @@ +--- +title: Criar uma discussão de equipe +intro: 'Qualquer integrante da organização pode criar uma postagem de discussão de equipe _pública_. Para criar uma postagem de discussão de equipe _privada_, você deve ser um integrante da equipe ou proprietário da organização.' +redirect_from: + - /articles/creating-a-team-discussion + - /github/building-a-strong-community/creating-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidade +--- + +{% data reusables.organizations.team-discussions-permissions %} Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/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. Digite um título para a discussão de equipe e um comentário para iniciar uma conversa. ![Novo comentário de discussão de equipe](/assets/images/help/projects/team-discussions-comment.png) +7. Se desejar, selecione se deseja que sua postagem seja privada ou pública usando o menu suspenso. ![Menu de configurações de privacidade das discussões de equipe](/assets/images/help/projects/team-discussions-privacy-menu.png) +8. Clique em **Comentário**. ![Botão Create new team discussions comment (Criar comentário de discussões de equipe)](/assets/images/help/projects/team-discussions-comment-button.png) + +### Leia mais + + - "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Editar ou excluir uma discussão de equipe](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" + - "[Fixar uma discussão de equipe](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000..9a043e2c9f --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,28 @@ +--- +title: Editar ou excluir uma discussão de equipe +intro: 'Os integrantes da organização podem editar ou excluir discussões na página de uma equipe. Caso seja integrante da organização, você poderá editar ou excluir a discussão.' +redirect_from: + - /articles/editing-or-deleting-a-team-discussion + - /github/building-a-strong-community/editing-or-deleting-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidade +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. Clique em {% octicon "kebab-horizontal" aria-label="The edit icon" %} ao lado da discussão de equipe que deseja editar ou excluir. +7. Clique em **Editar**. Ou clique em **Delete** (Excluir). ![Botão Edit team discussion (Editar discussão de equipe)](/assets/images/help/projects/edit-team-discussions-button.png) +8. Modifique o título e o comentário da discussão de equipe conforme necessário e clique em **Update comment** (Atualizar comentário). ![Botão Update comment (Atualizar comentário)](/assets/images/help/projects/update-comment-button.png) + +### Leia mais + + - "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Criar uma discussão de equipe](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Fixar uma discussão de equipe](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/index.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/index.md new file mode 100644 index 0000000000..ec6c23e708 --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/index.md @@ -0,0 +1,19 @@ +--- +title: Colaborar com a equipe +intro: 'Em uma organização, sua equipe pode trabalhar em conjunto em projetos usando discussões de equipe.' +redirect_from: + - /articles/collaborating-with-your-team + - /github/building-a-strong-community/collaborating-with-your-team + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidade +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md new file mode 100644 index 0000000000..50ad4290eb --- /dev/null +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +title: Fixar uma discussão de equipe +intro: 'Você pode fixar discussões importantes nas páginas da equipe da organização para facilitar a consulta e desafixar discussões que não são mais relevantes.' +redirect_from: + - /articles/pinning-a-team-discussion + - /github/building-a-strong-community/pinning-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - comunidade +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +5. Clique em {% octicon "pin" aria-label="The pin icon" %} ao lado da discussão de equipe que deseja fixar. Você também pode desafixar uma discussão ao clicar no ícone. ![Fixar uma discussão](/assets/images/help/projects/pin-discussion-button.png) + +### Leia mais + + - "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Criar uma discussão de equipe](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Editar ou excluir uma discussão de equipe](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000..0a0d213273 --- /dev/null +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,26 @@ +--- +title: Sobre a autenticação de dois fatores e o SAML de logon único +intro: Os administradores da organização podem habilitar o SAML de logon único e a autenticação de dois fatores para adicionar medidas extras de autenticação para os integrantes da organização. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-two-factor-authentication-and-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +A autenticação de dois fatores (2FA, Two-Factor Authentication) fornece autenticação básica para integrantes da organização. Ao habilitar a 2FA, os administradores da organização limitam a probabilidade de que a conta do {% data variables.product.product_name %} de um integrante possa ser comprometida. Para obter mais informações sobre a 2FA, consulte "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)". + +Para adicionar medidas extras de autenticação, os administradores da organização também podem [habilitar o SAML de logon único (SSO, Single Sign-On)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para que os integrantes da organização usem o logon único para acessar uma organização. Para obter mais informações sobre o SAML SSO, consulte "[Sobre o gerenciamento de identidade e acesso com SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)". + +Se a 2FA e o SAML SSO forem habilitados, os integrantes da organização deverão fazer o seguinte: +- Usar a 2FA para entrar na conta do {% data variables.product.product_name %} +- Usar o logon único para acessar a organização +- Usar um token autorizado para acesso por API ou Git e usar logon único para autorizar o token + +### Leia mais + +- "[Aplicar SAML de logon único para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md new file mode 100644 index 0000000000..063f890330 --- /dev/null +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -0,0 +1,16 @@ +--- +title: Conceder acesso à sua organização com logon único SAML +intro: 'Administradores de organizações podem conceder acesso à organização com logon único SAML. O acesso pode ser concedido a integrantes de organizações, bots e contas de serviço.' +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000..86d796ec35 --- /dev/null +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,25 @@ +--- +title: Gerenciar bots e contas de serviço com logon único SAML +intro: Organizações que habilitaram logon único SAML podem manter o acesso para bots e contas de serviço. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Para manter o acesso para bots e contas de serviço, os administradores da organização podem [habilitar](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), mas **não** [executar](/articles/enforcing-saml-single-sign-on-for-your-organization) o logon único SAML na organização. Se você precisa executar logon único SAML na organização, é possível criar uma identidade externa para o bot ou conta de serviço com seu provedor de identidade (IdP). + +{% warning %} + +**Observação:** se você aplicar logon único SAML na sua organização e **não** tiver configurado identidades externas para bots e contas de serviço com o IdP, eles serão removidos da organização. + +{% endwarning %} + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000..7b99fb4938 --- /dev/null +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,64 @@ +--- +title: Visualizar e gerenciar o acesso SAML de um integrante à sua organização +intro: 'Você pode visualizar e revogar a identidade vinculada de um integrante da organização, as sessões ativas e as credenciais autorizadas.' +permissions: Os proprietários da organização podem visualizar e gerenciar o acesso SAML de um integrante a uma organização. +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Sobre o acesso SAML à sua organização + +Ao ativar o logon único SAML para sua organização, cada integrante da organização poderá vincular sua identidade externa ao seu provedor de identidade (IdP) à sua conta {% data variables.product.product_name %} existente. Para acessar os recursos da sua organização no {% data variables.product.product_name %}, o integrante deverá ter uma sessão SAML ativa em seu navegador. Para acessar os recursos da sua organização usando a API ou o Git, o integrante deve usar um token de acesso pessoal ou chave SSH que o integrante autorizou a usar com a sua organização. + +Você pode visualizar e revogar a identidade vinculada de cada integrante, as sessões ativas e as credenciais autorizadas na mesma página. + +### Visualizar e revogar uma identidade 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 e revogar uma sessão ativa 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 e revogar credenciais 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 %} + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Visualizar e gerenciar acesso SAML de um usuário à conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)" diff --git a/translations/pt-BR/content/organizations/index.md b/translations/pt-BR/content/organizations/index.md new file mode 100644 index 0000000000..1e15ca90ed --- /dev/null +++ b/translations/pt-BR/content/organizations/index.md @@ -0,0 +1,32 @@ +--- +title: Organizações e equipes +shortTitle: Organizações +intro: Colabore em muitos projetos gerenciando o acesso a projetos e dados e personalizando as configurações de sua organização. +redirect_from: + - /articles/about-improved-organization-permissions/ + - /categories/setting-up-and-managing-organizations-and-teams + - /github/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_with_intro /collaborating-with-groups-in-organizations %} +{% link_with_intro /managing-membership-in-your-organization %} +{% link_with_intro /managing-peoples-access-to-your-organization-with-roles %} +{% link_with_intro /organizing-members-into-teams %} +{% link_with_intro /collaborating-with-your-team %} +{% link_with_intro /managing-access-to-your-organizations-repositories %} +{% link_with_intro /managing-access-to-your-organizations-project-boards %} +{% link_with_intro /managing-access-to-your-organizations-apps %} +{% link_with_intro /managing-organization-settings %} +{% link_with_intro /restricting-access-to-your-organizations-data %} +{% link_with_intro /keeping-your-organization-secure %} +{% link_with_intro /managing-saml-single-sign-on-for-your-organization %} +{% link_with_intro /granting-access-to-your-organization-with-saml-single-sign-on %} +{% link_with_intro /managing-git-access-to-your-organizations-repositories %} +{% link_with_intro /migrating-to-improved-organization-permissions %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md new file mode 100644 index 0000000000..0a32837a56 --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md @@ -0,0 +1,24 @@ +--- +title: Proteger sua organização +intro: 'Os proprietários de organizações têm vários recursos disponíveis para ajudá-los a proteger seus projetos e dados. Se você for o proprietário de uma organização, você deverá revisar regularmente o log de auditoria da sua organização{% if currentVersion != "github-ae@latest" %}, status de 2FA do integrante{% endif %} e as configurações do aplicativo para garantir que não ocorra nenhuma atividade não autorizada ou maliciosa.' +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure + - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000..0055b1ea76 --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Gerenciar endereços IP permitidos para sua organização +intro: Você pode restringir o acesso aos ativos da sua organização configurando uma lista de endereços IP autorizados a se conectar. +product: '{% data reusables.gated-features.allowed-ip-addresses %}' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Os proprietários da organização podem gerenciar endereços IP permitidos para uma organização. + +### Sobre endereços IP permitidos + +Você pode restringir o acesso a ativos da organização configurando uma lista de permissões para endereços IP específicos. {% 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 %} + +Você também pode configurar endereços IP permitidos para as organizações em uma conta corporativa. Para obter mais informações, consulte {% if currentVersion == "github-ae@latest" %}"[Restringir o tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)". {% else %}"[Aplicar configurações de segurança na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)."{% endif %} + +### Adicionar endereços IP permitidos + +{% 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 endereços IP permitidos + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +3. Em "IP allow list" (Lista de permissões IP), selecione **Enable IP allow list** (Habilitar lista de permissões IP). ![Caixa de seleção para permitir endereços IP](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) +4. Clique em **Salvar**. + +### Editar endereços IP permitidos + +{% 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. Clique em **Atualizar**. + +### Excluir endereços IP permitidos + +{% 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 %} + +### Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-actions.ip-allow-list-hosted-runners %} + +{% else %} + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +{% endif %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000..132ca09c69 --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,143 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +topics: + - organizations + - teams +--- + +### 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. {% if currentVersion == "free-pro-team@latest" %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, você também poderá gerenciar o acesso a essas funcionalidades. {% 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 %} + +### Exibir as configurações de segurança e análise + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security-and-analysis %} + +A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização. + +{% if currentVersion == "free-pro-team@latest" %}Se a sua organização pertence a uma empresa com uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %} + +{% if currentVersion == "github-ae@latest" %}A página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}.{% endif %} + +### Habilitar ou desabilitar um recurso para todos os repositórios existentes + +Você pode habilitar ou desabilitar funcionalidades para todos os repositórios. {% if currentVersion == "free-pro-team@latest" %}O impacto de suas alterações nos repositórios da organização é determinado pela visibilidade: + +- **Gráfico de dependências** - Suas alterações afetam apenas repositórios privados porque a funcionalidade está sempre habilitada para repositórios públicos. +- **{% data variables.product.prodname_dependabot_alerts %}** - As suas alterações afetam todos os repositórios. +- **{% data variables.product.prodname_dependabot_security_updates %}** - As suas alterações afetam todos os repositórios. +- **{% data variables.product.prodname_GH_advanced_security %}** - As suas alterações afetam apenas repositórios privados, porque {% data variables.product.prodname_GH_advanced_security %} e os as funcionalidades relacionadas estão sempre habilitadas para repositórios públicos. +- **{% data variables.product.prodname_secret_scanning_caps %}** - As suas alterações afetam apenas repositórios privados em que {% data variables.product.prodname_GH_advanced_security %} também está habilitado. {% data variables.product.prodname_secret_scanning_caps %} está sempre habilitado para repositórios públicos.{% 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)". +2. 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" or currentVersion ver_gt "enterprise-server@3. " %}O controle para "{% data variables.product.prodname_GH_advanced_security %}" fica desabilitado se você não tiver estações disponíveis na sua licença de {% data variables.product.prodname_GH_advanced_security %}{% endif %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% if currentVersion == "github-ae@latest" %} + ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +3. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} +4. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% endif %} + {% if currentVersion == "github-ae@latest" %} +3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Botão para habilitar o recurso para todos os repositórios elegíveis na organização](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} + + {% data reusables.security.displayed-information %} + +### Habilitar ou desabilitar uma funcionalidade automaticamente quando novos repositórios forem adicionados + +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)". +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% if currentVersion == "github-ae@latest" %} + ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Permitir que {% data variables.product.prodname_dependabot %} acesse dependências privadas + +{% 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 a todos os arquivos de dependência de destino. Normalmente, atualizações da versão irão falhar se uma ou mais dependências forem inacessíveis. Para obter mais informações, consulte "[Sobre atualizações da versão de {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)". + +Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências que estão localizadas em repositórios privados ou registros de pacotes 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. + +Se seu código depende de pacotes em um registro privado, você pode permitir que {% data variables.product.prodname_dependabot %} atualize as versões dessas dependências configurando isso no nível do repositório. Você faz isso adicionando detalhes de autenticação ao arquivo _dependabot.yml_ do repositório. Para obter mais informações, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". + +Para permitir que {% data variables.product.prodname_dependabot %} acesse um repositório privado de {% data variables.product.prodname_dotcom %}: + +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 "Acesso ao repositório privado de {% data variables.product.prodname_dependabot %}", clique em **Adicionar repositórios privados** ou **Adicionar repositórios internos e privados**. ![Botão para adicionar repositórios](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. Comece a digitar o nome do repositório que você deseja permitir. ![Botão para adicionar repositórios](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Clique no repositório que você deseja permitir. + +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. ![Botão "X" para remover um repositório](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### Remover acesso a {% data variables.product.prodname_GH_advanced_security %} de repositórios individuais em uma organização + +Você pode gerenciar o acesso a funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para um repositório na aba "Configurações". 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)". No entanto, você também pode desabilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para um repositório na aba "Configurações" da organização. + +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. Para ver uma lista de todos os repositórios na sua organização com {% data variables.product.prodname_GH_advanced_security %} habilitados, desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}". ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) A tabela lista o número de committers únicos para cada repositório. Este é o número de estações que você poderia liberar em sua licença, removendo acesso a {% data variables.product.prodname_GH_advanced_security %}. O tamanho da sua licença é mostrado para licenças no nível da organização. Para obter mais informações, consulte "[Sobre licenciamento para {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)". +1. Para remover acesso ao {% data variables.product.prodname_GH_advanced_security %} de um repositório e liberar estações usadas por todos os committers que são exclusivos do repositório, clique no {% octicon "x" aria-label="X symbol" %} adjacente. +1. Na caixa de diálogo de confirmação, clique em **Remover repositório** para remover acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %}. + +{% note %} + +**Observação:** Se você remover o acesso a {% data variables.product.prodname_GH_advanced_security %} para um repositório, você deverá comunicar-se com a equipe de desenvolvimento afetada para que saibam que a alteração foi planejada. Isso garante que eles não perderão tempo corrigindo execuções falhas de varredura de código. + +{% endnote %} + +{% endif %} + +### Leia mais + +- "[Sobre proteger seu repositório](/github/administering-a-repository/about-securing-your-repository)" +- "[Sobre a varredura de segredo](/github/administering-a-repository/about-secret-scanning)"{% if currentVersion == "free-pro-team@latest" %} +- "[Manter as suas dependências atualizadas automaticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}{% if currentVersion != "github-ae@latest" %} +- "[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)"{% endif %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..5f8b48737f --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Preparar para exigir autenticação de dois fatores na organização +intro: 'Antes de exigir autenticação de dois fatores (2FA), é possível notificar os usuários sobre as próximas mudanças e verificar quem já utiliza 2FA.' +redirect_from: + - /articles/preparing-to-require-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +Recomendamos que você notifique {% if currentVersion == "free-pro-team@latest" %}os integrantes da organização, colaboradores externos e os gerentes de cobrança{% else %}integrantes da organização e colaboradores externos{% endif %} a pelo menos uma semana antes de exigir 2FA na sua organização. + +Se você exigir o uso da autenticação de dois fatores na organização, os integrantes, colaboradores externos e gerentes de cobrança (inclusive contas bots) que não usam 2FA serão removidos da organização e perderão acesso aos repositórios dela. Eles também perderão acesso às bifurcações dos repositórios privados da organização. + +Antes de exigir 2FA na organização, recomendamos que você: + - [Habilite a 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) em sua conta pessoal + - Solicite às pessoas da organização para configurar 2FA na conta delas + - Verifique se [os usuários na organização têm a 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/) + - Alerte os usuários que assim que a 2FA estiver habilitada, aqueles que não a tiverem habilitado serão automaticamente removidos da organização diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..89d5bed545 --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,80 @@ +--- +title: Exigir autenticação de dois fatores em sua organização +intro: 'Os proprietários da organização podem exigir que os {% if currentVersion == "free-pro-team@latest" %}integrantes da organização, colaboradores externos e gerentes de cobrança{% else %}membros da organização e colaboradores externos{% endif %} habilitem a autenticação de dois fatores para suas contas pessoais, tornando mais difícil para atores maliciosos acessar os repositórios e configurações de uma organização.' +redirect_from: + - /articles/requiring-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +### Sobre a autenticação de dois fatores para organizações + +{% data reusables.two_fa.about-2fa %} Você pode exigir que todos os {% if currentVersion == "free-pro-team@latest" %}integrantes, colaboradores externos e gerentes de cobrança {% else %}integrantes e colaboradores externos na sua organização{% endif %} habilitem a autenticação de dois fatores em {% data variables.product.product_name %}. Para obter mais informações sobre a autenticação de dois fatores, consulte "[Proteger a sua conta com autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". + +{% if currentVersion == "free-pro-team@latest" %} + +Você também pode exigir autenticação de dois fatores para as organizações de uma empresa. 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#requiring-two-factor-authentication-for-organizations-in-your-enterprise-account)". + +{% endif %} + +{% warning %} + +**Avisos:** + +- Ao exigir o uso da autenticação de dois fatores para a sua organização, {% if currentVersion == "free-pro-team@latest" %}os integrantes, colaboradores externos e gerentes de cobrança{% else %}integrantes e colaboradores externos{% endif %} (incluindo contas bot) que não usarem a 2FA serão removidos da organização e perderão acesso aos seus repositórios. Eles também perderão acesso às bifurcações dos repositórios privados da organização. Se eles habilitarem a autenticação de dois fatores for habilitada na conta pessoal em até três meses após a remoção da organização, você poderá [restabelecer as configurações e os privilégios de acesso deles](/articles/reinstating-a-former-member-of-your-organization). +- Se um proprietário da organização, integrante{% if currentVersion == "free-pro-team@latest" %} gerente de cobrança,{% endif %} ou colaborador externo desabilitar a 2FA para sua conta pessoal depois que você habilitar a autenticação de dois fatores, eles serão automaticamente removidos da organização. +- Se você for o único proprietário de uma organização que exige autenticação de dois fatores, não poderá desabilitar a 2FA na sua conta pessoal sem desabilitar a autenticação de dois fatores obrigatória na organização. + +{% endwarning %} + +{% data reusables.two_fa.auth_methods_2fa %} + +### Pré-requisitos + +Antes de poder exigir que {% if currentVersion == "free-pro-team@latest" %}os integrantes da organização, colaboradores externos e gerentes de cobrança{% else %}integrantes da organização e colaboradores externos{% endif %} usem a autenticação de dois fatores, você deve habilitá-la para a sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Proteger sua conta com autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". + +Antes de exigir o uso da autenticação de dois fatores, recomendamos notificar os {% if currentVersion == "free-pro-team@latest" %}integrantes da organização, colaboradores externos e gerentes de cobrança {% else %}integrantes da organização e colaboradores externos{% endif %} e solicitar que configurem a 2FA para suas contas. Você pode ver se os integrantes e colaboradores externos já estão usando a 2FA. Para obter mais informações, consulte "[Ver se os usuários na organização têm a 2FA habilitada](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)". + +### Exigir autenticação de dois fatores em sua organização + +{% 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. Se algum integrante ou colaborador externo for removido da organização, recomendamos o envio de um convite para restabelecer os privilégios e o acesso à organização que ele tinha anteriormente. O usuário precisa habilitar a autenticação de dois fatores para poder aceitar o convite. +{% endif %} + +### Exibir pessoas removidas da organização + +Para exibir as pessoas que foram removidas automaticamente da organização por motivo de não conformidade quando você passou a exibir a autenticação de dois fatores, você pode [pesquisar o log de auditoria da organização](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log) para consultar as pessoas removidas da organização. O evento do log de auditoria mostrará se uma pessoa foi removida por motivo de não conformidade com a 2FA. + +![Evento do log de auditoria mostrando um usuário removido por motivo de não conformidade com a 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. Faça a pesquisa. Para pesquisar: + - Integrantes da organização removidos, use `action:org.remove_member` na pesquisa + - Colaboradores externos removidos, use `action:org.remove_outside_collaborator` na sua consulta de pesquisa{% if currentVersion == "free-pro-team@latest" %} + - Gerentes de cobrança removidos, use `action:org.remove_billing_manager`na pesquisa{% endif %} + + Você também pode exibir as pessoas que foram removidas da organização usando um [intervalo de tempo](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) na pesquisa. + +### Ajudar integrantes e colaboradores externos removidos a voltarem à organização + +Se algum integrante ou colaborador externo for removido da organização quando você habilitar o uso obrigatório da autenticação de dois fatores, o integrante/colaborador receberá um e-mail informando que foi removido. Para solicitar acesso à sua organização, o integrante/colaborador deverá ativar a 2FA na conta pessoal e entrar em contato com o proprietário da organização. + +### Leia mais + +- "[Ver se os usuários na organização têm a 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Proteger sua conta com autenticação de dois fatores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)" +- "[Restabelecer o acesso de um ex-colaborador externo à organização](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000..43b45cebc4 --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,31 @@ +--- +title: Restringir notificações de e-mail para um domínio aprovado +intro: 'Para evitar a divulgação de informações da organização para contas pessoais, os proprietários da organização podem restringir as notificações de e-mail sobre a atividade da organização a um domínio 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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Sobre restrições de e-mail + +Quando notificações de e-mail restritas são habilitadas em uma organização, os integrantes só podem usar um endereço de e-mail associado aos domínios verificados da organização para receber notificações de e-mail sobre a atividade da organização. Para obter mais informações, consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)". + +Os colaboradores externos não estão sujeitos a restrições de notificações por e-mail para domínios verificados. Para obter mais informações sobre colaboradores externos, consulte "[Níveis de permissão para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)". + +Se a sua organização pertencer a uma conta corporativa, os integrantes da organização poderão receber notificações sobre quaisquer domínios verificados para a conta corporativa, além de quaisquer domínios verificados para a organização. Para obter mais informações, consulte "[Verificar o domínio da sua conta corporativa](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)". + +### Restringir notificações de e-mail para um domínio aprovado + +{% 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. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000..22e11daab1 --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,643 @@ +--- +title: Revisar o log de auditoria da organização +intro: 'O log de auditoria permite que os administradores da organização revisem rapidamente as ações executadas pelos integrantes da organização. O painel detalha informações como o tipo de ação, o autor da ação e quando a ação foi executada.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-the-audit-log-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Acessar o log de auditoria + +O log de auditoria lista os eventos acionados por atividades que afetaram a sua organização nos últimos 90 dias. Somente proprietários conseguem acessar o log de auditoria da organização. + +{% 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 %} + +### Pesquisar no log de auditoria + +{% data reusables.audit_log.audit-log-search %} + +#### Pesquisar com base na ação + +Para pesquisar eventos específicos, use o qualificador `action` na consulta. As ações listadas no log de auditoria são agrupadas nas seguintes categorias: + +| Categoria | Descrição | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`conta`](#account-category-actions) | Contém todas as atividades relacionadas à conta da sua organização. | +| [`advisory_credit`](#advisory_credit-category-actions) | Contém todas as atividades relacionadas ao crédito de um colaborador de uma consultoria de segurança no {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Sobre consultoria de segurança de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | +| [`cobrança`](#billing-category-actions) | Contém todas as atividades relacionadas à cobrança da organização. | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contém atividades de configuração do nível de organização para alertas de {% data variables.product.prodname_dependabot %} em repositórios existentes. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" | +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contém atividades de configuração do nível de organização para alertas de {% data variables.product.prodname_dependabot %} em novos repositórios criados na organização. | +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contém atividades de configuração a nível da organização para {% data variables.product.prodname_dependabot_security_updates %} em repositórios existentes. Para obter mais informações, consulte "[Configurando {% 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) | Contém atividades de configuração do nível da organização em {% data variables.product.prodname_dependabot_security_updates %} para novos repositórios criados na organização. | +| [`dependency_graph`](#dependency_graph-category-actions) | Contém atividades de configuração a nível da organização para gráficos de dependências nos repositórios. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contém atividades de configuração no nível da organização para novos repositórios criados na organização:{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Contém todas as atividades relacionadas às discussões publicadas em uma página de equipe. | +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contém todas as atividades relacionadas às respostas de discussões publicadas em uma página de equipe. | +| [`hook`](#hook-category-actions) | Tem todas as atividades relacionadas a webhooks. | +| [`integration_installation_request`](#integration_installation_request-category-actions) | Contém todas as atividades relacionadas a solicitações de integrantes da organização para proprietários aprovarem integrações para uso na organização. | +| [`problema`](#issue-category-actions) | Contém atividades relacionadas à exclusão de um problema. |{% if currentVersion == "free-pro-team@latest" %} +| [`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 a listar aplicativos em {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contém todas as atividades relacionadas ao gerenciamento da publicação de sites do {% data variables.product.prodname_pages %} para repositórios na organização. Para obter mais informações, consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |{% endif %} +| [`org`](#org-category-actions) | Contém atividades relacionadas à associação da organização.{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contém todas as atividades relacionadas à autorização de credenciais para uso com SAML único de login.{% 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) | Contém todas as atividades relacionadas a etiquetas padrão na sua organização.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contém todas as atividades relacionadas aos aplicativos OAuth.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`pacotes`](#packages-category-actions) | Contém todas as atividades relacionadas a {% data variables.product.prodname_registry %}.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contém todas as atividades relacionadas a como sua organização paga pelo GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contém todas as atividades relacionadas à imagem de perfil da organização. | +| [`project`](#project-category-actions) | Contém todas as atividades relacionadas aos quadros de projeto. | +| [`protected_branch`](#protected_branch-category-actions) | Contém todas as atividades relacionadas aos branches protegidos. | +| [`repo`](#repo-category-actions) | Contém atividades relacionadas aos repositórios pertencentes à sua organização.{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contém atividades no nível do repositório relacionadas às consultorias de segurança no {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Sobre consultoria de segurança de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contém todas as atividades relacionadas a [habilitar ou desabilitar o uso de dados em um repositório privado](/articles/about-github-s-use-of-your-data).{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contém atividades do nível de repositório relacionadas a habilitar ou desabilitar o gráfico de dependências para um | +| repositório {% if currentVersion == "free-pro-team@latest" %}privado{% endif %}. Para obter mais informações, consulte "[Sobre o gráfico de dependências](/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" or currentVersion == "github-ae@latest" %} | | +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contém atividades no nível do repositório relacionadas ao escaneamento do segredo. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contém todas as atividades relacionadas a [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contém atividades de configuração do nível do repositório para alertas de {% data variables.product.prodname_dependabot %}. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| [`secret_scanning`](#secret_scanning-category-actions) | Contém atividades de configuração a nível da organização para varredura de segredo em repositórios existentes. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." | +| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contém atividades de configuração a nível da organização para varredura de segredo de novos repositórios criados na organização. |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | Contém todos os eventos relacionados a botões de patrocinadores (consulte "[Exibir um botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %} +| [`equipe`](#team-category-actions) | Tem todas as atividades relacionadas às equipes na organização. | +| [`team_discussions`](#team_discussions-category-actions) | Contém atividades relacionadas ao gerenciamento de discussões de equipe na organização. | + +Você pode pesquisar conjuntos específicos de ações usando esses termos. Por exemplo: + + * `action:team` localiza todos os eventos agrupados na categoria da equipe; + * `-action:hook` exclui todos os eventos na categoria de webhook. + +Cada categoria tem um conjunto de ações associadas que você pode filtrar. Por exemplo: + + * `action:team.create` localiza todos os eventos em que uma equipe foi criada; + * `-action:hook.events_changed` exclui todos os eventos nos quais os eventos em um webhook foram alterados. + +#### Pesquisar com base na hora da ação + +Use o qualificador `created` para filtrar eventos no log de auditoria com base na hora que elas ocorreram. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +Por exemplo: + + * `created:2014-07-08` localiza todos os eventos ocorridos em 8 de julho de 2014; + * `created:>=2014-07-08` localiza todos os eventos ocorridos em 8 de julho de 2014 ou depois dessa data; + * `created:<=2014-07-08` localiza todos os eventos ocorridos em 8 de julho de 2014 ou antes dessa data; + * `created:2014-07-01..2014-07-31` localiza todos os eventos ocorridos em julho de 2014. + +O log de auditoria contém dados dos últimos 90 dias, mas você pode usar o qualificador `created` para pesquisar eventos mais antigos. + +#### Pesquisar com base no local + +Ao usar o qualificador `país`, você pode filtrar eventos no log de auditoria com base no país de origem. Você pode usar o código de duas letras do país ou o nome completo. Lembre-se de que os país com espaços no nome devem ser colocados entre aspas. Por exemplo: + + * `country:de` localiza todos os eventos ocorridos na Alemanha; + * `country:Mexico` localiza todos os eventos ocorridos no México; + * `country:"United States"` localiza todos os eventos ocorridos nos Estados Unidos. + +{% if currentVersion == "free-pro-team@latest" %} +### Exportar o log de auditoria + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### Usando a API do log de auditoria + +Você pode interagir com o log de auditoria usando a API GraphQL{% if currentVersion == "free-pro-team@latest" %} ou a API REST{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Usando a API GraphQL + +{% endif %} + +{% note %} + +**Nota**: A API GraphQL de auditoria do log está disponível para organizações usando {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +Para garantir um IP seguro e manter conformidade para a sua organização, você pode usar a API GraphQL de auditoria para manter cópias dos seus dados de log de auditoria e do monitor: +{% data reusables.audit_log.audit-log-api-info %} + +{% if currentVersion == "free-pro-team@latest" %} +Observe que você não pode recuperar eventos Git usando a API GraphQL. Para recuperar eventos do Git, use a API REST. Para obter mais informações, consulte "[`git` ações de categoria](#git-category-actions)". +{% endif %} + +A resposta do GraphQL pode incluir dados por até 90 a 120 dias. + +Por exemplo, você pode fazer uma solicitação GraphQL para ver todos os novos integrantes adicionados à organização. Para obter mais informações, consulte o " "[Log de auditoria da API do GraphQL](/graphql/reference/interfaces#auditentry/)". + +{% if currentVersion == "free-pro-team@latest" %} + +#### Usando a API REST + +{% note %} + +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. + +{% endnote %} + +Para garantir um IP seguro e manter conformidade para a sua organização, você pode usar a API REST de auditoria para manter cópias dos seus dados de log de auditoria e monitorar: +{% data reusables.audit_log.audit-log-api-info %} +* Eventos do Git, como clonar, buscar e fazer push + +{% data reusables.audit_log.audit-log-git-events-retention %} + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endif %} + +### Ações do log de auditoria + +Uma visão geral de algumas das ações mais comuns registradas como eventos no log de auditoria. + +{% if currentVersion == "free-pro-team@latest" %} + +#### ações de categoria da `conta` + +| Ação | Descrição | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing_plan_change` | Acionada quando o [ciclo de cobrança](/articles/changing-the-duration-of-your-billing-cycle) da organização é alterado. | +| `plan_change` | Acionada quando a [assinatura](/articles/about-billing-for-github-accounts) da organização é alterada. | +| `pending_plan_change` | Acionada quando um gerente de cobrança ou proprietário da organização [cancela ou faz downgrade de uma assinatura paga](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). | +| `pending_subscription_change` | Acionada quando uma [avaliação gratuita do {% data variables.product.prodname_marketplace %} inicia ou expira](/articles/about-billing-for-github-marketplace/). | + +#### ações de categoria de `advisory_credit` + +| Ação | Descrição | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `aceitar` | Acionada quando alguém aceita crédito para uma consultoria de segurança. Para obter mais informações, consulte "[Editar um consultor de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory)". | +| `create` | Acionada quando o administrador da consultoria de segurança adiciona alguém à seção de crédito. | +| `recusar` | Acionada quando alguém rejeita crédito para uma consultoria de segurança. | +| `destroy` | Acionada quando o administrador da consultoria de segurança remove alguém da seção de crédito. | + +#### ações de categoria de `cobrança` + +| Ação | Descrição | +| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `change_billing_type` | Acionada quando a organização [altera o método de pagamento do {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). | +| `change_email` | Acionada quando o [endereço de e-mail de cobrança](/articles/setting-your-billing-email) da organização é alterado. | + +#### ações de categoria de `dependabot_alerts` + +| Ação | Descrição | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `desabilitar` | Acionada quando um proprietário da organização desabilita {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %} existentes. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | Acionada quando um proprietário da organização habilita {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %}. | + +#### ações de categoria de `dependabot_alerts_new_repos` + +| Ação | Descrição | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `desabilitar` | Acionada quando um proprietário da organização desabilita {% data variables.product.prodname_dependabot_alerts %} para todos os novos repositórios {% if currentVersion == "free-pro-team@latest" %}privados {% endif %}. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | Acionada quando um proprietário da organização habilita {% data variables.product.prodname_dependabot_alerts %} para todos os novos repositórios {% if currentVersion == "free-pro-team@latest" %}privados{% endif %}. | + +#### ações de categoria de `dependabot_security_updates` + +| Ação | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `desabilitar` | Acionada quando um proprietário da organização desabilita {% data variables.product.prodname_dependabot_security_updates %} em todos os repositórios existentes. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | Acionada quando um proprietário da organização habilita {% data variables.product.prodname_dependabot_security_updates %} em todos os repositórios existentes. | + +#### ações de categoria de `dependabot_security_updates_new_repos` + +| Ação | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `desabilitar` | Acionada quando um proprietário da organização desabilita {% data variables.product.prodname_dependabot_security_updates %} em todos os novos repositórios. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | Acionada quando um proprietário da organização habilita {% data variables.product.prodname_dependabot_security_updates %} em todos os novos repositórios. | + +#### ações de categoria de `dependency_graph` + +| Ação | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `desabilitar` | Acionada quando um proprietário da organização desabilita o gráfico de dependências em todos os repositórios existentes. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | Acionada quando um proprietário da organização habilita o gráfico de dependências para todos os repositórios existentes. | + +#### ações de categoria de `dependency_graph_new_repos` + +| Ação | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `desabilitar` | Acionada quando um proprietário da organização desabilita o gráfico de dependências em todos os novos repositórios. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". | +| `habilitar` | Acionada quando um proprietário da organização habilita o gráfico de dependências para todos os novos repositórios. | + +{% endif %} + +#### ações de categoria de `discussion_post` + +| Ação | Descrição | +| --------- | ----------------------------------------------------------------------------------------------------------------------------- | +| `update` | Acionada quando uma [postagem de discussão de equipe é editada](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Acionada quando uma [postagem de discussão de equipe é excluída](/articles/managing-disruptive-comments/#deleting-a-comment). | + +#### ações de categoria de `discussion_post_reply` + +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------- | +| `update` | Acionada quando a [resposta de uma postagem de discussão de equipe é editada](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Acionada quando a [resposta de uma postagem de discussão de equipe é excluída](/articles/managing-disruptive-comments/#deleting-a-comment). | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Ações da categoria `empresa` + +{% data reusables.actions.actions-audit-events-for-enterprise %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### ações da categoria `ambiente` + +| Ação | Descrição | +| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create_actions_secret` | Acionada quando um segredo é criado em um ambiente. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)". | +| `delete` | Acionada quando um ambiente é excluído. Para obter mais informações, consulte ["Excluir um ambiente](/actions/reference/environments#deleting-an-environment)". | +| `remove_actions_secret` | Acionada quando um segredo é removido de um ambiente. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)". | +| `update_actions_secret` | Acionada quando um segredo em um ambiente é atualizado. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)". | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### ações da categoria `git` + +{% note %} + +**Observação:** Para acessar eventos Git no log de auditoria, você deve usar a API REST do log de auditoria. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Ação | Descrição | +| ------- | ------------------------------------------------------------------------ | +| `clone` | Acionada quando um repositório é clonado. | +| `fetch` | Acionada quando alterações são obtidas de um repositório. | +| `push` | Acionada quando as alterações são enviadas por push para um repositório. | + +{% endif %} + +#### ações de categoria de `hook` + +| Ação | Descrição | +| ---------------- | --------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando [um novo hook é adicionado](/articles/creating-webhooks) a um repositório da organização. | +| `config_changed` | Acionada quando a configuração de um hook é alterada. | +| `destroy` | Acionada quando um hook é removido de um repositório. | +| `events_changed` | Acionada quando os eventos em um hook são alterados. | + +#### ações de categoria de `integration_installation_request` + +| Ação | Descrição | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando um integrante da organização pede para um proprietário da organização instalar uma integração para uso na organização. | +| `close` | Acionada quando uma solicitação de instalação de integração para uso na organização é aprovada ou negada pelo proprietário da organização ou cancelada pelo integrante que fez a solicitação. | + +#### ações de categoria de `problema` + +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `destroy` | Acionada quando um proprietário da organização ou um usuário com permissões de administrador em um repositório exclui um problema de um repositório pertencente à organização. | + +{% if currentVersion == "free-pro-team@latest" %} + +#### ações de categoria de `marketplace_agreement_signature` + +| Ação | Descrição | +| -------- | ------------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando você assina o Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}. | + +#### ações de categoria de `marketplace_listing` + +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------ | +| `aprovar` | Acionada quando sua lista é aprovada para inclusão no {% data variables.product.prodname_marketplace %}. | +| `create` | Acionada quando você cria uma lista para seu app no {% data variables.product.prodname_marketplace %}. | +| `delist` | Acionada quando sua lista é removida do {% data variables.product.prodname_marketplace %}. | +| `redraft` | Triggered when your listing is sent back to draft state. | +| `reject` | Acionada quando sua lista não é aprovada para inclusão no {% data variables.product.prodname_marketplace %}. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +#### ações de categoria de `members_can_create_pages` + +Para obter mais informações, consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". + +| Ação | Descrição | +|:------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `habilitar` | Acionada quando um proprietário da organização habilita a publicação de sites do {% data variables.product.prodname_pages %} nos repositórios da organização. | +| `desabilitar` | Acionada quando um proprietário da organização desabilita a publicação de sites do {% data variables.product.prodname_pages %} nos repositórios da organização. | + +{% endif %} + +#### ações de categoria de `org` + +| Ação | Descrição | +| ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `audit_log_export` | Acionada quando um administrador da organização [cria uma exportação do log de auditoria da organização](#exporting-the-audit-log). Se a exportação incluir uma consulta, o log relacionará a consulta usada e o número de entradas do log de auditoria que correspondem à consulta. | +| `block_user` | Acionada quando um proprietário da organização [bloqueia o acesso de um usuário aos repositórios da organização](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization). | +| `cancel_invitation` | Acionada quando um convite para ingressar na organização é revogado. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é criado na organização. Para obter mais informações, consulte "[Criar segredos criptografados para uma organização](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} |{% if currentVersion == "free-pro-team@latest"%} +| `disable_oauth_app_restrictions` | Acionada quando um proprietário [desabilita as restrições de acesso ao {% data variables.product.prodname_oauth_app %}](/articles/disabling-oauth-app-access-restrictions-for-your-organization) na organização. | +| `disable_saml` | Acionada quando um administrador da organização desabilita o logon único SAML para uma organização.{% endif %} +| `disable_member_team_creation_permission` | Acionada quando um proprietário da organização limita a criação de equipe a proprietários. Para obter mais informações, consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)". |{% if currentVersion != "github-ae@latest" %} +| `disable_two_factor_requirement` | Acionada quando um proprietário desabilita uma exigência de autenticação de dois fatores para todos os integrantes{% if currentVersion == "free-pro-team@latest" %}, gerentes de cobrança{% endif %} e colaboradores externos na organização.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable_oauth_app_restrictions` | Acionada quando um proprietário [habilita as restrições de acesso ao {% data variables.product.prodname_oauth_app %}](/articles/enabling-oauth-app-access-restrictions-for-your-organization) na organização. | +| `enable_saml` | Acionada quando um administrador da organização [habilita o logon único SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) na organização.{% endif %} +| `enable_member_team_creation_permission` | Acionada quando um proprietário da organização permite a criação de equipes pelos integrantes. Para obter mais informações, consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)". |{% if currentVersion != "github-ae@latest" %} +| `enable_two_factor_requirement` | Acionada quando um proprietário exige a autenticação de dois fatores para todos os integrantes{% if currentVersion == "free-pro-team@latest" %}, gerentes de cobrança,{% endif %} e colaboradores externos em uma organização.{% endif %} +| `invite_member` | Acionada quando [um novo usuário foi convidado a ingressar na organização](/articles/adding-organization-members-to-a-team).{% if currentVersion == "free-pro-team@latest" %} +| `oauth_app_access_approved` | Acionada quando um proprietário [concede acesso da organização a um {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). | +| `oauth_app_access_denied` | Acionada quando um proprietário [desabilita um acesso aprovado anteriormente ao {% data variables.product.prodname_oauth_app %}](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) na organização. | +| `oauth_app_access_requested` | Acionada quando um integrante da organização solicita que um proprietário conceda um acesso de {% data variables.product.prodname_oauth_app %} à sua organização.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma organização](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | +| `remove_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é removido.{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `remove_billing_manager` | Acionada quando um [proprietário remove um gerente de cobrança da organização](/articles/removing-a-billing-manager-from-your-organization/) ou quando [a autenticação de dois fatores é exigida na organização](/articles/requiring-two-factor-authentication-in-your-organization) e um gerente de cobrança não usa ou desabilita a 2FA. +{% endif %} +| `remove_member` | Acionada quando um proprietário [remove um integrante da organização](/articles/removing-a-member-from-your-organization/){% if currentVersion ! "github-ae@latest" %} ou quando [a autenticação de dois fatores é exigida em uma organização](/articles/requiring-two-factor-authentication-in-your-organization) e um membro da organização não usa a 2FA ou desabilita a 2FA{% endif %}. Também é acionada quando um [integrante da organização remove a si mesmo](/articles/removing-yourself-from-an-organization/) da organização. | +| `remove_outside_collaborator` | Acionada quando um proprietário remove um colaborador externo da organização{% if currentVersion ! "github-ae@latest" %} ou quando [a autenticação de dois fatores é necessária em uma organização](/articles/requiring-two-factor-authentication-in-your-organization) e um colaborador externo não usa 2FA ou desabilita a autenticação de dois fatores{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. Para obter mais informações, consulte "[Remover um executor de uma organização](/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` | Acionada quando o proprietário de uma organização revoga a identidade vinculada a um integrante. Para obter mais informações, consulte "[Visualizar e gerenciar o acesso SAML de um integrante à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". | +| `revoke_sso_session` | Acionada quando o proprietário de uma organização revoga a sessão SAML de um integrante. Para obter mais informações, consulte "[Visualizar e gerenciar o acesso SAML de um integrante à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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` | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Criar um grupo de executores auto-hospedados para uma organização](/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` | Acionada quando um grupo de executores auto-hospedados é removido. Para obter mais informações, consulte "[Remover um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | +| `runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores 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)". | +| `runner_group_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte [Transferir um executor auto-hospedado para um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | +| `runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. Para obter mais informações, consulte "[Remover um executor auto-hospedado de um grupo para uma organização](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | +| `runner_group_runners_updated` | Acionada quando a lista de integrantes do grupo de executor é atualizada. Para obter mais informações, consulte "[Definir executores auto-hospedados em um grupo para uma organização](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization).{% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Acionada quando o executor é atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `unblock_user` | Acionada quando um proprietário da organização [desbloqueia um usuário da organização](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Acionada quando um segredo de {% data variables.product.prodname_actions %} é atualizado.{% 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` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."{% endif %} +| `update_default_repository_permission` | Acionada quando um proprietário altera o nível de permissão padrão do repositório para integrantes da organização. | +| `update_member` | Acionada quando um proprietário altera a função de um usuário de proprietário para integrante ou de integrante para proprietário. | +| `update_member_repository_creation_permission` | Acionada quando um proprietário altera a permissão de criar repositório para integrantes da organização.{% if currentVersion == "free-pro-team@latest" %} +| `update_saml_provider_settings` | Acionada quando as configurações de um provedor de SAML da organização são atualizadas. | +| `update_terms_of_service` | Acionada quando uma organização alterna entre Termos de serviço padrão e Termos de serviço corporativos. Para obter mais informações, consulte "[Atualizar para os Termos de serviço corporativos](/articles/upgrading-to-the-corporate-terms-of-service)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### ações da categoria `org_credential_authorization` + +| Ação | Descrição | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `grant` | Acionada quando um integrante [autoriza credenciais para uso com logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `deauthorized` | Acionada quando um integrante [desautoriza credenciais para uso com logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `revogar` | Acionada quando um proprietário [revoga credenciais autorizadas](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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" %} +#### ações da categoria `organization_label` + +| Ação | Descrição | +| --------- | ----------------------------------------------- | +| `create` | Acionada quando uma etiqueta padrão é criada. | +| `update` | Acionada quando uma etiqueta padrão é editada. | +| `destroy` | Acionada quando uma etiqueta padrão é excluída. | + +{% endif %} + +#### ações da categoria `oauth_application` + +| Ação | Descrição | +| --------------- | ---------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando um {% data variables.product.prodname_oauth_app %} é criado. | +| `destroy` | Acionada quando um {% data variables.product.prodname_oauth_app %} é excluído. | +| `reset_secret` | Acionada quando um segredo do cliente de {% data variables.product.prodname_oauth_app %} é redefinido. | +| `revoke_tokens` | Acionada quando um token de usuário de {{% data variables.product.prodname_oauth_app %} é revogado. | +| `transferir` | Acionada quando um {% data variables.product.prodname_oauth_app %} é transferido para outra organização. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +#### Ações da categoria `pacotes` + +| Ação | Descrição | +| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `package_version_published` | Acionada quando uma versão do pacote é publicada. | +| `package_version_deleted` | Acionada quando uma versão específica do pacote é excluída. Para obter mais informações, consulte "[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)". | +| `package_deleted` | Acionada quando um pacote inteiro é excluído. Para obter mais informações, consulte "[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)". | +| `package_version_restored` | Acionada quando uma versão específica do pacote é excluída. Para obter mais informações, consulte "[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)". | +| `package_restored` | Acionada quando um pacote inteiro é restaurado. Para obter mais informações, consulte "[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)". | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### ações de categoria `payment_method` + +| Ação | Descrição | +| -------- | ---------------------------------------------------------------------------------------------------------- | +| `clear` | Acionada quando um método de pagamento registrado é [removido](/articles/removing-a-payment-method). | +| `create` | Acionada quando um novo método de pagamento, como um novo cartão de crédito ou conta PayPal, é adicionado. | +| `update` | Acionada quando um método de pagamento é atualizado. | + +{% endif %} + +#### ações de categoria `profile_picture` +| Ação | Descrição | +| ------ | ------------------------------------------------------------------------ | +| update | Acionada quando você define ou atualiza a foto de perfil da organização. | + +#### ações de categoria `project` + +| Ação | Descrição | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Acionada quando um quadro de projeto é criado. | +| `link` | Acionada quando um repositório é vinculado a um quadro de projeto. | +| `rename` | Acionada quando um quadro de projeto é renomeado. | +| `update` | Acionada quando um quadro de projeto é atualizado. | +| `delete` | Acionada quando um quadro de projeto é excluído. | +| `unlink` | Acionada quando um repositório é desvinculado de um quadro de projeto. | +| `update_org_permission` | Acionada quando a permissão no nível de base para todos os integrantes da organização é alterada ou removida. | +| `update_team_permission` | Acionada quando o nível de permissão do quadro de projeto de uma equipe é alterado ou quando uma equipe é adicionada ou removida de um quadro de projeto. | +| `update_user_permission` | Acionada quando um integrante ou colaborador externo da organização é adicionado ou removido de um quadro de projeto ou tem seu nível de permissão alterado. | + +#### ações da categoria `protected_branch` + +| Ação | Descrição | +| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando a proteção do branch é habilitada em um branch. | +| `destroy` | Acionada quando a proteção do branch é desabilitada em um branch. | +| `update_admin_enforced` | Acionada quando a proteção do branch é exigida para os administradores do repositório. | +| `update_require_code_owner_review` | Acionada quando a exigência da revisão do proprietário do código é atualizada em um branch. | +| `dismiss_stale_reviews` | Acionada quando a exigência de ignorar pull requests obsoletas é atualizada em um branch. | +| `update_signature_requirement_enforcement_level` | Acionada quando a exigência de assinatura de commit obrigatória é atualizada em um branch. | +| `update_pull_request_reviews_enforcement_level` | Acionada quando a exigência de revisão de pull requests é atualizada em um branch. | +| `update_required_status_checks_enforcement_level` | Acionada quando a exigência de verificações de status obrigatórias é atualizada em um branch. | +| `update_strict_required_status_checks_policy` | Acionada quando a exigência de um branch estar atualizado antes de o merge ser alterado. | +| `rejected_ref_update` | Acionada quando uma tentativa de atualização do branch é rejeitada. | +| `policy_override` | Acionada quando uma exigência de proteção de branch é substituída por um administrador do repositório.{% 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` | Acionada quando o push forçado é habilitado ou desabilitado para um branch protegido. | +| `update_allow_deletions_enforcement_level` | Acionada quando a exclusão do branch é habilitada ou desabilitada para um branch protegido. | +| `update_linear_history_requirement_enforcement_level` | Acionada quando o histórico de commit linear necessário está habilitado ou desabilitado em um branch protegido. | +{% endif %} + +#### ações de categoria `repo` + +| Ação | Descrição | +| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | Acionada quando um usuário [altera a visibilidade](/github/administering-a-repository/setting-repository-visibility) de um repositório na organização. | +| `actions_enabled` | Acionada quando {% data variables.product.prodname_actions %} está habilitado para um repositório. Pode ser visto usando a interface do usuário. Este evento não é incluído quando você acessar o log de auditoria usando a API REST. Para obter mais informações, consulte "[Usar a API REST](#using-the-rest-api)". | +| `add_member` | Acionada quando um usuário aceita um [convite para ter acesso de colaboração em um repositório](/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" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. 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)". | +| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for 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).".{% endif %} +| `archived` | Acionada quando um administrador do repositório [arquiva um repositório](/articles/about-archiving-repositories).{% if enterpriseServerVersions contains currentVersion %} +| `config.disable_anonymous_git_access` | Acionada quando um [acesso de leitura anônimo do Git é desabilitado](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) em um repositório público. | +| `config.enable_anonymous_git_access` | Acionada quando um [acesso de leitura anônimo do Git é habilitado](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) em um repositório público. | +| `config.lock_anonymous_git_access` | Acionada quando a [configuração de acesso de leitura anônimo do Git de um repositório é bloqueada](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | +| `config.unlock_anonymous_git_access` | Acionada quando a [configuração de acesso de leitura anônimo do Git de um repositório é desbloqueada](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `create` | Acionada quando [um novo repositório é criado](/articles/creating-a-new-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é criado em um repositório. Para obter mais informações, consulte "[Criar segredos criptografados para um repositório](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".{% endif %} +| `destroy` | Acionada quando [um repositório é excluído](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `desabilitar` | Acionada quando um repositório é desabilitado (por exemplo, por [recursos financeiros insuficientes](/articles/unlocking-a-locked-account)).{% endif %} +| `habilitar` | Acionada quando um repositório é reativado.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_actions_secret` | Acionada quando um segredo de {% data variables.product.prodname_actions %} é removido.{% endif %} +| `remove_member` | Acionada quando um usuário é [removido de um repositório como colaborador](/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` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a um repositório](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). ". | +| `remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. Para obter mais informações, consulte "[Remover um executor de um repositório](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". |{% endif %} +| `remove_topic` | Acionada quando um administrador do repositório remove um tópico de um repositório. | +| `rename` | Acionada quando [um repositório é renomeado](/articles/renaming-a-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Acionada quando o executor é atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `transferir` | Acionada quando [um repositório é transferido](/articles/how-to-transfer-a-repository). | +| `transfer_start` | Acionada quando uma transferência de repositório está prestes a ocorrer. | +| `unarchived` | Acionada quando um administrador do repositório desarquiva um repositório.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Acionada quando um segredo de {% data variables.product.prodname_actions %} é atualizado.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### Ações da categoria `repository_advisory` + +| Ação | Descrição | +| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `close` | Acionada quando alguém fecha uma consultoria de segurança. Para obter mais informações, consulte "[Sobre consultoria de segurança de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | +| `cve_request` | Acionada quando alguém solicita um número de CVE (Vulnerabilidades e Exposições Comuns) de {% data variables.product.prodname_dotcom %} para um rascunho da consultoria de segurança. | +| `github_broadcast` | Acionada quando {% data variables.product.prodname_dotcom %} torna uma consultoria de segurança pública em {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Acionada quando {% data variables.product.prodname_dotcom %} retira uma consultoria de segurança publicado com erro. | +| `aberto` | Acionada quando alguém abre uma consultoria de segurança. | +| `publish` | Acionada quando alguém publica uma consultoria de segurança. | +| `reabrir` | Acionada quando alguém reabre como um rascunho de consultoria de segurança. | +| `update` | Acionada quando alguém edita um rascunho ou uma consultoria de segurança publicada. | + +#### ações de categoria de `repository_content_analysis` + +| Ação | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `habilitar` | Acionada quando o proprietário de uma organização ou pessoa com acesso de administrador ao repositório [habilita as configurações de uso de dados para um repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | +| `desabilitar` | Acionada quando o proprietário de uma organização ou pessoa com acesso de administrador ao repositório [desabilita as configurações de uso de dados para um repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | + +{% endif %}{% if currentVersion != "github-ae@latest" %} + +#### ações de categoria de `repository_dependency_graph` + +| Ação | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `desabilitar` | Acionada quando um proprietário ou pessoa do repositório com acesso de administrador ao repositório desabilita o gráfico de dependências de um{% if currentVersion == "free-pro-team@latest" %}repositório {% endif %}privado. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | +| `habilitar` | Acionada quando um proprietário ou pessoa do repositório com acesso de administrador ao repositório habilita o gráfico de dependências de um{% if currentVersion == "free-pro-team@latest" %}repositório {% endif %}privado. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### ações de categoria de `repository_secret_scanning` + +| Ação | Descrição | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `desabilitar` | Acionada quando um proprietário ou pessoa com acesso de administrador ao repositório desabilita a varredura de segredo para um {% if currentVersion == "free-pro-team@latest" %}repositório {% endif %}privado. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." | +| `habilitar` | Acionada quando um proprietário ou pessoa com acesso de administrador ao repositório habilita a varredura de segredo secreta de um {% if currentVersion == "free-pro-team@latest" %}repositório {% endif %}privado. | + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### ações de categoria de `repository_vulnerability_alert` + +| Ação | Descrição | +| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Acionada quando {% data variables.product.product_name %} cria um {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}alerta de segurança{% endif %} para um repositório que usa uma dependência vulnerável. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" | +| `ignorar` | Acionada quando um proprietário ou pessoa com acesso de administrador ao repositório ignorar um alerta de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}segurança{% endif %} sobre uma dependência vulnerável. | +| `resolver` | Acionada quando alguém com acesso de gravação a um repositório, faz alterações para atualizar e resolver uma vulnerabilidade na dependência de um projeto. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### ações da categoria `repository_vulnerability_alerts` + +| Ação | Descrição | +| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `authorized_users_teams` | Acionada quando um proprietário da organização ou uma pessoa com permissões de administrador no repositório atualiza a lista de pessoas ou equipes autorizadas a receber {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis no repositório. 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)". | +| `desabilitar` | Acionada quando um proprietário ou pessoa do repositório com acesso de administrador ao repositório desabilita {% data variables.product.prodname_dependabot_alerts %}. | +| `habilitar` | Acionada quando um proprietário ou pessoa do repositório com acesso de administrador ao repositório habilita {% data variables.product.prodname_dependabot_alerts %}. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### ações da categoria `secret_scanning` + +| Ação | Descrição | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `desabilitar` | Acionada quando um proprietário da organização desabilita a varredura de segredo de todos os repositórios{% if currentVersion == "free-pro-team@latest" %} privados{% endif %} existentes. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." | +| `habilitar` | Acionada quando um proprietário da organização permite a varredura de segredo de todos os repositórios {% if currentVersion == "free-pro-team@latest" %} privados{% endif %} existentes. | + +#### ações da categoria `secret_scanning_new_repos` + +| Ação | Descrição | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `desabilitar` | Acionada quando um proprietário da organização desabilita a varredura de segredo para todos os repositórios {% if currentVersion == "free-pro-team@latest" %}novos e {% endif %}privados. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." | +| `habilitar` | Acionada quando um proprietário da organização permite a varredura secreta de todos os repositórios {% if currentVersion == "free-pro-team@latest" %}novos {% endif %}e privados. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### ações de categoria de `patrocinadores` + +| Ação | Descrição | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo_funding_link_button_toggle` | Acionada quando você habilita ou desabilita um botão de patrocinador no repositório (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create` | Acionada quando você patrocina uma conta (veja "[Patrocinar um contribuidor de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_preference_change` | Acionada quando você altera se recebe atualizações de e-mail de uma conta patrocinada (consulte "[Gerenciar seu patrocínio](/articles/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsored_developer_approve` | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para a sua organização](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_create` | Acionada quando sua conta em {% data variables.product.prodname_sponsors %} é criada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para a sua organização](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_profile_update` | Acionada quando você edita o seu perfil de organização patrocinado (consulte "[Editar as informações do seu perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval` | Acionada quando você envia o seu aplicativo para {% data variables.product.prodname_sponsors %} para aprovação (consulte "[Configurar {% data variables.product.prodname_sponsors %} para a sua organização](/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 "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| sponsored_developer_update_newsletter_send | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/articles/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer` | Acionada quando você é convidado a juntar-se a {% data variables.product.prodname_sponsors %} na lista de espera (consulte "[Configurar {% data variables.product.prodname_sponsors %} para a sua organização](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `waitlist_join` | Acionada quando você se junta à lista de espera para tornar-se uma organização patrocinada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para a sua organização](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +{% endif %} + +#### ações de categoria de `equipe` + +| Ação | Descrição | +| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `add_member` | Acionada quando um integrante de uma organização é [adicionado a uma equipe](/articles/adding-organization-members-to-a-team). | +| `add_repository` | Acionada quando uma equipe recebe o controle de um repositório. | +| `change_parent_team` | Acionada quando uma equipe secundária é criada ou [a equipe principal de uma equipe secundária é alterada](/articles/moving-a-team-in-your-organization-s-hierarchy). | +| `change_privacy` | Acionada quando nível de privacidade de uma equipe é alterado. | +| `create` | Acionada quando uma nova equipe é criada.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`demote_maintainer` | Acionada quando um usuário teve sua categoria rebaixada de mantenedor da equipe para integrante de equipe. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/managing-peoples-access-to-your-organization-with-roles/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` | Acionada quando um repositório não está mais sob o controle de uma equipe. + +#### ações de categoria de `team_discussions` + +| Ação | Descrição | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `desabilitar` | Acionada quando um proprietário da organização desabilita as discussões de equipe em uma organização. Para obter mais informações, consulte "[Desabilitar discussões de equipe para sua organização](/articles/disabling-team-discussions-for-your-organization)". | +| `habilitar` | Acionada quando um proprietário da organização habilita as discussões de equipe em uma organização. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +#### Ações da categoria `fluxos de trabalho` + +{% data reusables.actions.actions-audit-events-workflow %} + +{% endif %} + +### Leia mais + +- [Proteger sua organização](/articles/keeping-your-organization-secure) diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000..bfd9aa0e07 --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,25 @@ +--- +title: Revisar as integrações instaladas da organização +intro: Você pode revisar os níveis de permissão das integrações instaladas da organização e configurar o acesso de cada integração aos repositórios da organização. +redirect_from: + - /articles/reviewing-your-organization-s-installed-integrations + - /articles/reviewing-your-organizations-installed-integrations + - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Na barra lateral esquerda, clique em **Installed {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s instalados). ![Guia Installed {% data variables.product.prodname_github_app %}s ({% data variables.product.prodname_github_app %}s instalados) na barra lateral de configurações da organização](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. Próximo do {% data variables.product.prodname_github_app %} que deseja revisar, clique em **Configure** (Configurar). ![Botão Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png) +6. Revise o acesso ao repositório e as permissões de {% data variables.product.prodname_github_app %}. ![Opção para fornecer ao {% data variables.product.prodname_github_app %} acesso a todos os repositórios ou a repositórios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png) + - Para fornecer acesso ao {% data variables.product.prodname_github_app %} em todos os repositórios da organização, selecione **All repositories** (Todos os repositórios). + - Para selecionar repositórios específicos para fornecer acesso ao aplicativo, selecione **Only select repositories** (Somente os repositórios selecionados) e insira o nome do repositório. +7. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000..a34f0b7dbb --- /dev/null +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,30 @@ +--- +title: Ver se os usuários da organização habilitaram a 2FA +intro: 'Você pode ver quais proprietários da organização, integrantes e colaboradores externos habilitaram a autenticação de dois fatores.' +redirect_from: + - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled + - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% note %} + +**Observação:** Você pode exigir que todos os integrantes{% if currentVersion == "free-pro-team@latest" %}, incluindo proprietários, gerentes de cobrança e{% else %} e{% endif %} colaboradores externos na sua organização possuem autenticação de dois fatores habilitada. Para obter mais informações, consulte "[Exigir autenticação de dois fatores em sua organização](/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 exibir os integrantes da organização, inclusive proprietários da organização, que habilitaram ou desabilitaram a autenticação de dois fatores, clique em **2FA** à direita e selecione **Enabled** (Habilitado) ou **Disabled** (Desabilitado). ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png) +5. Clique em **Outside collaborators** (Colaboradores externos), na guia "People" (Pessoas), para exibir aqueles que pertencem à sua organização. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) +6. Para exibir quais colaboradores externos habilitaram ou desabilitaram a autenticação de dois fatores, clique em **2FA** à direita e selecione **Enabled** (Habilitado) ou **Disabled** (Desabilitado). ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) + +### Leia mais + +- "[Exibir as funções das pessoas em uma organização](/articles/viewing-people-s-roles-in-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000..95dbdbdbcf --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,40 @@ +--- +title: Adicionar gerentes do aplicativo GitHub em sua organização +intro: 'Os proprietários da organização podem conceder aos usuários a capacidade de gerenciar {% data variables.product.prodname_github_app %} específicos ou todos os {% data variables.product.prodname_github_app %}s da organização.' +redirect_from: + - /articles/adding-github-app-managers-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Para obter mais informações sobre as permissões de gerente do {% data variables.product.prodname_github_app %}, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization#github-app-managers)". + +### Dar a um indivíduo a capacidade de gerenciar todos os {% data variables.product.prodname_github_app %}s possuídos pela organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Em "Management" (Gerenciamento), digite o nome de usuário da pessoa que deseja designar como um gerente do {% data variables.product.prodname_github_app %} na organização e clique em **Grant** (Conceder). ![Adicionar um gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/add-github-app-manager.png) + +### Dar a um indivíduo a capacidade de gerenciar um {% 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. Em "{% data variables.product.prodname_github_app %}s", clique no avatar do app ao qual deseja adicionar um gerente do {% data variables.product.prodname_github_app %}. ![Selecione {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Em "App managers" (Gerentes de app), digite o nome de usuário da pessoa que deseja designar como gerente do aplicativo GitHub e clique em **Grant** (Conceder). ![Adicionar um gerente do {% data variables.product.prodname_github_app %} para um app específico](/assets/images/help/organizations/add-github-app-manager-for-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Leia mais + +- "[Sobre o {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md new file mode 100644 index 0000000000..83d5faacd9 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -0,0 +1,18 @@ +--- +title: Gerenciar acessos aos aplicativos da organização +intro: 'Como proprietário da organização, você pode permitir que integrantes individuais gerenciem {% data variables.product.prodname_github_app %}s em sua organização.' +redirect_from: + - /articles/managing-access-to-your-organization-s-apps + - /articles/managing-access-to-your-organizations-apps + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /adding-github-app-managers-in-your-organization %} +{% link_in_list /removing-github-app-managers-from-your-organization %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000..63c4faf076 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,40 @@ +--- +title: Remover gerentes do aplicativo GitHub da organização +intro: 'Os proprietários da organização podem revogar as permissões de gerente do {% data variables.product.prodname_github_app %} concedidas a um integrante da organização.' +redirect_from: + - /articles/removing-github-app-managers-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Para obter mais informações sobre as permissões de gerente do {% data variables.product.prodname_github_app %}, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization#github-app-managers)". + +### Remover as permissões de gerente do {% data variables.product.prodname_github_app %} em toda a organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Em "Management" (Gerenciamento), encontre o nome de usuário da pessoa da qual deseja remover as permissões de gerente do {% data variables.product.prodname_github_app %} e clique em **Revoke** (Revogar). ![Revogue as permissões de gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) + +### Remover as permissões de gerente do {% data variables.product.prodname_github_app %} de um {% 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. Em "{% data variables.product.prodname_github_app %}s", clique no avatar do app no qual deseja remover um gerente do {% data variables.product.prodname_github_app %}. ![Selecione {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Em "App managers" (Gerentes do app), encontre o nome de usuário da pessoa da qual deseja remover as permissões de gerente do {% data variables.product.prodname_github_app %} e clique em **Revoke** (Revogar). ![Revogue as permissões de gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Leia mais + +- "[Sobre o {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000..1a69089909 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Adicionar um colaborador externo a um quadro de projeto em sua organização +intro: 'Como um proprietário da organização ou administrador do quadro de projeto, você pode adicionar um colaborador externo e personalizar as permissões dele em um quadro de projeto.' +redirect_from: + - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Um colaborador externo é uma pessoa que não é explicitamente um integrante da sua organização, mas tem permissões para um quadro de projeto em sua organização. + +{% 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. Em "Search by username, full name or email address" (Pesquisar por nome de usuário, nome completo ou endereço de e-mail), digite o nome do colaborador externo, nome de usuário ou e-mail no {% data variables.product.prodname_dotcom %}. ![A seção Collaborators (Colaboradores) com o nome de usuário Octocat inserido no campo de pesquisa](/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/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/index.md new file mode 100644 index 0000000000..95f10f8cdf --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -0,0 +1,22 @@ +--- +title: Gerenciar acessos aos quadros de projetos da organização +intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode conceder a integrantes, equipes e colaboradores externos níveis diferentes de acesso a quadros de projetos de propriedade da organização.' +redirect_from: + - /articles/managing-access-to-your-organization-s-project-boards + - /articles/managing-access-to-your-organizations-project-boards + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000..3ff8f26d5f --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,39 @@ +--- +title: Gerenciar acesso de integrantes da organização a um quadro de projeto +intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode configurar um nível de permissão padrão para todos os integrantes da organização.' +redirect_from: + - /articles/managing-access-to-a-project-board-for-organization-members + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Por padrão, os integrantes de uma organização têm acesso de gravação nos quadros de projetos da organização, exceto se os proprietários da organização ou os administradores de quadro de projeto configurarem permissões diferentes para quadros de projetos específicos. + +### Configurar um nível referencial de permissão para todos os integrantes da organização + +{% tip %} + +**Dica:** você pode dar a um integrante da organização as permissões mais altas em um um quadro de projeto. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/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. Em "Organization member permission" (Permissão de integrante da organização), escolha um nível referencial de permissão para todos os integrantes da organização: **Read** (Leitura), **Write** (Gravação), **Admin** (Administrador) ou **None** (Nenhuma). ![Opções de permissões a quadro de projeto para todos os integrantes da organização](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. Clique em **Salvar**. + +### Leia mais + +- "[Gerenciar o acesso de um indivíduo a um quadro de projeto da organização](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Gerenciar o acesso da equipe a um quadro de projeto da organização](/articles/managing-team-access-to-an-organization-project-board)" +- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..1328aa7056 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,62 @@ +--- +title: Gerenciar o acesso de um indivíduo a um quadro de projeto da organização +intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode gerenciar o acesso de um integrante individual a um quadro de projeto pertencente à sua organização.' +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-project-board + - /articles/managing-an-individuals-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% note %} + +**Observação:** {% data reusables.project-management.cascading-permissions %} para obter mais informações, consulte "[Permissões do quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)". + +{% endnote %} + +### Conceder a um integrante da organização acesso a um quadro de projeto + +{% 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. Em "Search by username, full name or email address" (Pesquisar por nome de usuário, nome completo ou endereço de e-mail), digite o nome, o nome de usuário ou o e-mail do colaborador no {% data variables.product.prodname_dotcom %}. ![A seção Collaborators (Colaboradores) com o nome de usuário Octocat inserido no campo de pesquisa](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} + +### Alterar o acesso de um integrante da organização a um quadro de projeto + +{% 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 %} + +### Remover o acesso de um integrante da organização a um quadro de projeto + +Quando você remove um colaborador de um quadro de projeto, a pessoa ainda pode ter acesso ao quadro com base nas permisões que tem para outras funções. Para remover completamente o acesso ao quadro de projeto, você deve remover o acesso à cada função que a pessoa tem. Por exemplo, uma pessoa pode ter acesso ao quadro de projeto como integrante de uma organização ou equipe. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/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 %} + +### Leia mais + +- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..09603bd411 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,52 @@ +--- +title: Gerenciar o acesso da equipe em um quadro de projeto da organização +intro: 'Como proprietário da organização ou administrador de quadro de projeto, você pode conceder o acesso da equipe a um quadro de projeto pertencente à sua organização.' +redirect_from: + - /articles/managing-team-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% warning %} + +**Avisos:** +- Você pode alterar os níveis de permissões de uma equipe se a equipe tiver acesso direto a um quadro de projeto. Se o acesso da equipe ao quadro de projeto é herança de uma equipe principal, você deve alterar o acesso da equipe principal ao quadro de projeto. +- Se você adicionar ou remover acesso de uma equipe principal ao quadro de projeto, cada uma das equipes secundárias da equipe principal também receberá ou perderá o acesso ao quadro de projeto. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)". + +{% endwarning %} + +### Conceder a uma equipe acesso a um quadro de projeto + +Você pode dar a uma equipe inteira o mesmo nível de permissão em um quadro de projeto. + +{% note %} + +**Observação:** {% data reusables.project-management.cascading-permissions %} por exemplo, se um proprietário da organização deu a uma equipe permissões de leitura em um quadro de projeto e um administrador de quadro de projeto concede permissões de administrador a um integrante da equipe como um colaborador individual, essa pessoa teria permissões de administrador no quadro de projeto. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/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. Na barra lateral esquerda, clique em **Teams** (Equipes). +9. Para adicionar uma equipe, clique em **Add a team: Select team** (Adicionar uma equipe: Selecionar equipe). Depois, escolha uma equipe no menu suspenso ou pesquise a equipe que você deseja adicionar. ![Menu suspenso Add a team (Adicionar uma equipe) com lista de equipes na organização](/assets/images/help/projects/add-a-team.png) +10. Ao lado do nome da equipe, use o menu suspenso para selecionar o nível de permissão desejado: **Read** (Leitura), **Write** (Gravação) ou **Admin** (Administrador). ![Menu suspenso Team permissions (Permissões de equipe) com opções read, write e admin (leitura, gravação e administrador)](/assets/images/help/projects/org-project-team-choose-permissions.png) + +### Configurar o acesso de uma equipe a um quadro de projeto + +Se o acesso de uma equipe a um quadro de projeto for herdado de uma equipe principal, você deverá alterar o acesso da equipe principal ao quadro de projeto para atualizar o acesso das equipes secundárias. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. Acima das conversas da equipe, clique em {% octicon "project" aria-label="The Projects icon" %} **Projects** (Projetos). ![Aba repositórios da equipe](/assets/images/help/organizations/team-project-board-button.png) +5. Para alterar os níveis de permissão, à direita do quadro de projetos que deseja atualizar, use o menu suspenso. Para remover um quadro de projeto, clique em **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botão Trash (Lixeira) Remove a project board from your team (Remover um quadro de projeto de sua equipe)](/assets/images/help/organizations/trash-button.png) diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000..087f7eb3dc --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -0,0 +1,44 @@ +--- +title: Permissões do quadro de projeto da organização +intro: 'Proprietários da organização e pessoas com permissões de administradores de quadro de projeto podem personalizar quem tem permissões de leitura, gravação e de administrador nos quadros de projeto da organização.' +redirect_from: + - /articles/project-board-permissions-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Visão geral das permissões + +Existem três níveis de permissões em um quadro de projeto para pessoas e equipes: + +{% data reusables.project-management.project-board-permissions %} + +Os proprietários da organização e pessoas com permissões de administrador podem conceder acesso a alguém a um quadro de projeto da organização individualmente, como colaborador externo ou integrante da organização, ou ainda, por meio da associação dele a uma equipe ou organização. Um colaborador externo é uma pessoa que não é integrante da organização mas recebeu permissões para colaborar na organização. + +Proprietários da organização e pessoas com permissões de administrador em um quadro de projeto também podem: +- Definir permissões de quadro de projeto padrão para todos os integrantes da organização. +- Gerenciar o acesso de integrantes, equipes e colaboradores externos da organização ao quadro de projeto. Para obter mais informações, consulte "[Gerenciar o acesso da equipe a um quadro de projeto da organização](/articles/managing-team-access-to-an-organization-project-board)", "[Gerenciar o acesso de um indivíduo a um quadro de projeto da organização](/articles/managing-an-individual-s-access-to-an-organization-project-board)" ou "[Gerenciar o acesso de integrantes da organização a um quadro de projeto](/articles/managing-access-to-a-project-board-for-organization-members)". +- Gerenciar a visibilidade do quadro de projeto. Para obter mais informações, consulte "[Gerenciar o acesso de integrantes da organização a um quadro de projeto](/articles/managing-access-to-a-project-board-for-organization-members)". + +### Permissões de acesso em cascata para quadros de projeto + +{% data reusables.project-management.cascading-permissions %} + +Por exemplo, se um proprietário da organização concedeu a todos os integrantes de uma equipe permissões de leitura em um quadro de projeto e um administrador de quadro de projeto concede permissões de gravação a um integrante da equipe naquele quadro de projeto como um colaborador individual, essa pessoa teria permissões de gravação no quadro de projeto. + +### Visibilidade do quadro de projeto + +{% data reusables.project-management.project-board-visibility %} Você pode alterar a visibilidade do quadro de projeto de privado para {% if currentVersion == "github-ae@latest" %}interno{% else %}public{% endif %} e novamente para privado. Para obter mais informações, consulte "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)". + +### Leia mais + +- "[Alterar a visibilidade do quadro de projeto](/articles/changing-project-board-visibility)" +- "[Gerenciar o acesso de um indivíduo a um quadro de projeto da organização](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Gerenciar o acesso da equipe a um quadro de projeto da organização](/articles/managing-team-access-to-an-organization-project-board)" +- "[Gerenciar o acesso de integrantes da organização a um quadro de projeto](/articles/managing-access-to-a-project-board-for-organization-members)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000..ad20944f80 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,23 @@ +--- +title: Remover um colaborador externo do quadro de projeto da organização +intro: 'Como proprietário da organização ou administrador do quadro de projeto, você pode remover o acesso de um colaborador externo ao quadro de projeto.' +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000..9e0de2b171 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,42 @@ +--- +title: Adicionar colaboradores externos a repositórios em sua organização +intro: 'Um *colaborador externo* é uma pessoa que não é explicitamente um integrante da sua organização, mas que tem permissões de Gravação, Leitura ou de Administrador para um ou vários repositórios da organização.' +redirect_from: + - /articles/adding-outside-collaborators-to-repositories-in-your-organization + - github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +O {% data reusables.organizations.owners-and-admins-can %} adiciona colaboradores externos em um repositório, a menos que o proprietário da organização tenha restringido a possibilidade de convidar colaboradores. Para obter mais informações, consulte "[Configurar permissões para adicionar colaboradores externos](/articles/setting-permissions-for-adding-outside-collaborators)". + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% if currentVersion != "github-ae@latest" %} +Se sua organização [exigir que integrantes e colaboradores externos usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), eles deverão habilitar a autenticação de dois fatores antes de aceitar seu convite para colaborar no repositório de uma organização. +{% 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. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field.png) +6. Em "Escolher uma função", selecione as permissões a serem concedidas à pessoa e, em seguida, clique em **Adicionar NOME ao REPOSITÓRIO**. ![Selecionar permissões para a pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +{% else %} +5. Na barra lateral esquerda, clique em **Collaborators & teams** (Colaboradores e equipes). ![Barra lateral de configurações do repositório com destaque para Collaborators & teams (Colaboradores e equipes)](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. Em "Collaborators" (Colaboradores), digite o nome da pessoa à qual deseja conceder acesso ao repositório e clique em **Add collaborator** (Adicionar colaborador). ![A seção Collaborators (Colaboradores) com o nome de usuário Octocat inserido no campo de pesquisa](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. Ao lado do nome do novo colaborador, escolha o nível de permissão apropriado: *Gravação*, *Leitura* ou *Administrador*. ![O selecionador de permissões do repositório](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +{% endif %} + +### Leia mais + +- "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Remover um colaborador externo de um repositório da organização](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000..0dca7fe6ef --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,24 @@ +--- +title: Cancelar um convite para se tornar um colaborador externo na sua organização +intro: É possível cancelar todos os convites para que uma pessoa se torne um colaborador externo em repositórios que pertencem à sua organização. +permissions: Os proprietários da organização podem cancelar um convite para se tornarem colaboradores externos na organização. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Você pode visualizar uma lista de todas as pessoas com convites pendentes para se tornar um colaborador externo em qualquer repositório que pertence à sua organização. + +Para cada colaborador pendente, você pode cancelar todos os convites para juntar-se aos repositórios da organização ao mesmo tempo. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% 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) diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000..7ee3b44de5 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,44 @@ +--- +title: Converter um integrante da organização em colaborador externo +intro: 'Se um integrante atual da organização precisar de acesso apenas a determinados repositórios, como consultores ou funcionários temporários, você poderá convertê-lo em um *colaborador externo*.' +redirect_from: + - /articles/converting-an-organization-member-to-an-outside-collaborator + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} converter integrantes da organização em colaboradores externos. + +{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} + +Após conversão de um integrante da organização em um colaborador externo, ele só terá acesso aos repositórios que sua associação à equipe atual permitir. A pessoa não será mais um integrante explícito da organização e não poderá mais: + +- Criar equipes +- Ver todos os integrantes e equipes da organização +- @mencionar qualquer equipe visível +- Seja um mantenedor de equipe + +Para obter mais informações, consulte "[Níveis de permissão para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)". + +Recomendamos rever o acesso dos membros da organização aos repositórios para garantir que seu o acesso seja como você espera. Para obter mais informações, consulte "[Gerenciar o acesso de um indivíduo ao repositório de uma organização](/articles/managing-an-individual-s-access-to-an-organization-repository)". + +Ao converter um integrante da organização em um colaborador externo, seus privilégios como integrantes da organização serão salvos por três meses para que você possa restaurar seus privilégios de associação se você{% if currentVersion == "free-pro-team@latest" %} convidá-los a juntar-se novamente{% else %} adicione-os à{% endif %} sua organização nesse período de tempo. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)". + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Selecione a(s) pessoa(s) que deseja converter em colaborador(es) externo(s). ![Lista de integrantes com dois integrantes selecionados](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Acima da lista de integrantes, use o menu suspenso e clique em **Convert to outside collaborator** (Converter em colaborador externo). ![Menu suspenso com opção para converter integrantes em colaboradores externos](/assets/images/help/teams/user-bulk-management-options.png) +6. Leia as informações sobre como converter integrantes em colaboradores externos e clique em **Convert to outside collaborator** (Converter em colaborador externo). ![Informações sobre permissões de colaboradores externos e botão Convert to outside collaborators (Converter em colaboradores externos)](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) + +### Leia mais + +- "[Adicionar colaboradores externos a repositórios na sua organização](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Remover um colaborador externo de um repositório da organização](/articles/removing-an-outside-collaborator-from-an-organization-repository)" +- "[Converter um colaborador externo em um integrante da organização](/articles/converting-an-outside-collaborator-to-an-organization-member)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000..b4b908846a --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,41 @@ +--- +title: Remover um colaborador externo em integrante da organização +intro: 'Se você quiser conceder a um colaborador externo permissões mais amplas nos repositórios da sua organização dentro de sua organização, você pode {% if currentVersion == "free-pro-team@latest" %} convidá-los a tornar-se um integrante de{% else %}torná-los um integrante da{% endif %} organização.' +redirect_from: + - /articles/converting-an-outside-collaborator-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 'Proprietários da organização podem {% if currentVersion == "free-pro-team@latest" %}convidar usuários para juntar-se a{% else %}adicionar usuários a{% endif %} uma organização.' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %}{% endif %} + +{% if currentVersion != "github-ae@latest" %} +Se a sua organização [exigir que os integrantes usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), os usuários {% if currentVersion == "free-pro-team@latest" %}que você convidar devem [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes que possam aceitar o convite.{% else %}devem [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de adicioná-la à organização.{% endif %} +{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +{% if currentVersion == "free-pro-team@latest" %} +5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.![Convidar colaboradores externos para a organização](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) +{% else %} +5. À direita do nome do colaborador externo que você deseja que se torne integrante, clique em **Invite to organization** (Convidar para a organização).![Convidar colaboradores externos para a organização](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png) +{% endif %} +{% data reusables.organizations.choose-to-restore-privileges %} +{% data reusables.organizations.choose-user-role-send-invitation %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Leia mais + +- "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..e66d89f4a3 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md @@ -0,0 +1,28 @@ +--- +title: Gerenciar acessos aos repositórios da organização +intro: Proprietários da organização podem gerenciar acessos individuais e de equipes aos repositórios da organização. Mantenedores de equipes também podem gerenciar o acesso ao repositório da equipe. +redirect_from: + - /articles/permission-levels-for-an-organization-repository/ + - /articles/managing-access-to-your-organization-s-repositories + - /articles/managing-access-to-your-organizations-repositories + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000..bd04c79297 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,39 @@ +--- +title: Gerenciar o acesso de um indivíduo a um repositório da organização +intro: Você pode gerenciar o acesso de uma pessoa ao repositório de sua organização. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Pessoas com permissões de administrador podem gerenciar o acesso de integrantes da organização e colaboradores externos a um repositório da organização. + +### Remover acesso a repositórios + +Ao remover um colaborador de um repositório de sua organização, o colaborador perde os acessos de leitura e gravação no repositório. Caso o repositório seja privado e o colaborador o tenha bifurcado, a bifurcação também é excluída, mas o colaborador ainda manterá quaisquer clones locais de seu repositório. + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +### Gerenciar o acesso de um indivíduo a um repositório da organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Cloque em **Members** (Integrantes) ou **Outside collaborators** (Colaboradores externos) para gerenciar pessoas com tipos diferentes de acessos. ![Botão para invite (convidar) members (colaboradores) ou outside collaborators (colaboradores externos) para uma organização](/assets/images/help/organizations/select-outside-collaborators.png) +5. À direita do nome do colaborador que deseja remover, use o menu suspenso {% octicon "gear" aria-label="The Settings gear" %} e clique em **Manage** (Gerenciar). ![Link para manage access (gerenciar acesso)](/assets/images/help/organizations/member-manage-access.png) +6. Na página "Manage access" (Gerenciar acesso), ao lado do repositório clique em **Manage access** (Gerenciar acesso). ![Botão Manage access (Gerenciar acesso) em um repositório](/assets/images/help/organizations/repository-manage-access.png) +7. Revise o acesso da pessoa em determinado repositório, por exemplo, se a pessoa é um colaborador ou tem acesso ao repositório como integrante de equipe. ![Matriz de acesso a repositório para o usuário](/assets/images/help/organizations/repository-access-matrix-for-user.png) + +### Leia mais + +{% if currentVersion == "free-pro-team@latest" %}- "[Limitar interações com o seu repositório](/articles/limiting-interactions-with-your-repository)"{% endif %} +- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000..12968700aa --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +title: Gerenciar o acesso da equipe em um repositório da organização +intro: 'Você pode conceder e remover o acesso da equipe a um repositório ou mudar o nível de permissão dela no repositório.' +redirect_from: + - /articles/managing-team-access-to-an-organization-repository-early-access-program/ + - /articles/managing-team-access-to-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Pessoas com acesso de administrador a um repositório podem gerenciar o acesso de equipes ao repositório. Mantenedores de equipes podem remover o acesso de uma equipe a um repositório. + +{% warning %} + +**Avisos:** +- Você pode alterar os níveis de permissões de uma equipe se a equipe tiver acesso direto a um repositório. Se o acesso da equipe ao repositório é herança de uma equipe principal, você deve alterar o acesso da equipe principal ao repositório. +- Se você adicionar ou remover acesso de uma equipe principal ao repositório, cada uma das equipes secundárias da equipe principal também receberá ou perderá o acesso ao repositório. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)". + +{% endwarning %} + +### Conceder a uma equipe acesso a um repositório + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. Acima da lista de repositórios, clique em **Add repository** (Adicionar repositório). ![Botão Add repository (Adicionar repositório)](/assets/images/help/organizations/add-repositories-button.png) +6. Digite o nome de um repositório e clique em **Add repository to team** (Adicionar repositório a uma equipe). ![Campo de pesquisa Repository (Repositório)](/assets/images/help/organizations/team-repositories-add.png) +7. Como opção, use o menu suspenso à direita do nome do repositório e escolha um nível de permissão diferente para a equipe. ![Menu suspenso Repository access level (Nível de acesso ao repositório)](/assets/images/help/organizations/team-repositories-change-permission-level.png) + +### Remover acesso de uma equipe a um repositório + +Você pode remover o acesso de uma equipe a um repositório se a equipe tiver acesso direto a ele. Se o acesso da equipe ao repositório é herdado de uma equipe principal, você deve remover o repositório da equipe principal para remover o repositório das equipes secundárias. + +{% 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. Selecione o repositório ou repositórios que deseja remover da equipe. ![Lista de repositórios de equipes com as caixas de seleção para alguns repositórios selecionadas](/assets/images/help/teams/select-team-repositories-bulk.png) +6. Acesse o menu suspenso acima da lista de repositórios e clique em **Remove from team** (Remover da equipe). ![Menu suspenso com a opção para Remove a repository from a team (Remover um repositório de uma equipe)](/assets/images/help/teams/remove-team-repo-dropdown.png) +7. Verifique o repositório ou repositórios que serão removidos da equipe e clique em **Remove repositories** (Remover repositórios). ![Caixa modal com uma lista de repositórios que a equipe não terá mais acesso](/assets/images/help/teams/confirm-remove-team-repos.png) + +### Leia mais + +- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000..bc7ab6123c --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Restabelecer o acesso de um ex-colaborador externo à organização +intro: 'É possível restabelecer as permissões de acesso de um ex-colaborador externo para repositórios, forks e configurações da organização.' +redirect_from: + - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization + - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Quando o acesso de um colaborador externo aos repositórios privados da sua organização é removido, os privilégios e configurações de acesso do usuário são salvos por três meses. Você pode restaurar os privilégios do usuário se você {% if currentVersion == "free-pro-team@latest" %}convidá-los{% else %}add{% endif %} para a organização nesse período de tempo. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +Ao restabelecer um ex-colaborador externo, você pode restaurar: + - O acesso anterior do usuário aos repositórios da organização + - As bifurcações privadas de repositórios de propriedade da organização + - A associação nas equipes da organização + - Os acessos e permissões anteriores nos repositórios da organização + - As estrelas dos repositórios da organização + - As atribuições de problemas na organização + - As assinaturas do repositório (configurações de notificação para inspecionar, não inspecionar ou ignorar as atividades de um repositório) + +{% tip %} + +**Dicas**: + - Somente proprietários da organização podem restabelecer o acesso de um colaborador externo à organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization)". + - O restabelecimento de um fluxo de integrante em {% data variables.product.product_location %} pode usar o termo "integrante" para descrever o restabelecimento de um colaborador externo. No entanto, se você restabelecer esta pessoa e mantiver seus privilégios anteriores, ela terá apenas suas [permissões de colaborador externo](/articles/permission-levels-for-an-organization/#outside-collaborators). {% if currentVersion == "free-pro-team@latest" %} + - Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)."{% endif %} + +{% endtip %} + +{% 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. Escolha restaurar os privilégios anteriores do colaborador externo na organização clicando em **Invite and reinstate** (Convidar e restabelecer) ou escolha apagar os privilégios anteriores e definir novas permissões de acesso clicando em **Invite and start fresh** (Convidar e começar do zero). + + {% warning %} + + **Aviso:** se quiser converter um colaborador externo em um integrante da organização, selecione **Invite and start fresh** (Convidar e começar do zero) e escolha uma nova função para a pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para converter o ex-colaborador externo em um integrante da organização *e* manter as bifurcações privadas dele, selecione **Invite and reinstate** (Convidar e restabelecer). Quando a pessoa aceitar o convite, você poderá fazer a conversão [convidando a pessoa para participar da organização como um integrante](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Escolher se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Escolha restaurar os privilégios anteriores do colaborador externo na organização clicando em **Add and reinstate** (Adicionar e restabelecer) ou escolha apagar os privilégios anteriores e definir novas permissões de acesso clicando em **Add and start fresh** (Adicionar e começar do zero). + + {% warning %} + + **Aviso:** se quiser converter um colaborador externo em um integrante da organização, selecione **Add and start fresh** (Adicionar e começar do zero) e escolha uma nova função para a pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para converter o ex-colaborador externo em um integrante da organização *e* manter as bifurcações privadas dele, selecione **Add and reinstate** (Adicionar e restabelecer). Em seguida, converta-o em integrante da organização [adicionando ele à organização como um integrante](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Escolher se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. Se você apagou os privilégios anteriores de um ex-colaborador externo, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Send invitation** (Enviar convite). ![Opções Role and team (Função e equipe) e botão send invitation (enviar convite)](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. Se você apagou os privilégios anteriores de um ex-colaborador externo, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Add member** (Adicionar integrante). ![Opções Role and team (Função e equipe) e botão add member (adicionar integrante)](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +8. A pessoa convidada receberá um e-mail com um convite para participar da organização. Ela precisará aceitar o convite antes de se tornar um colaborador externo na organização. {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Leia mais + +- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000..e4d1109cd2 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,57 @@ +--- +title: Remover um colaborador externo do repositório da organização +intro: Os proprietários e administradores do repositório podem remover o acesso de um colaborador externo a um repositório. +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Aviso:** +- Ao remover um colaborador externo de um repositório privado, a contagem de licenças pagas não faz o downgrade automaticamente. Para pagar menos licenças depois de remover os usuários da sua organização, siga as etapas em "[Fazer o downgrade das estações pagas da sua organização](/articles/downgrading-your-organization-s-paid-seats)". + +- Você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual. + +{% endwarning %} + +{% endif %} + +Apesar de as bifurcações de repositórios privados serem excluídas quando um colaborador é removido, o colaborador mantém todos os clones locais do seu repositório. + +### Remover colaboradores externos de todos os repositórios da organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Selecione um ou mais colaboradores externos que deseja remover da organização. ![Lista de colaboradores externos com dois colaboradores selecionados](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) +6. Use o menu suspenso acima da lista de colaboradores externos e clique em **Remove from all repositories** (Remover de todos os repositórios). ![Menu suspenso com opção para remover colaboradores externos ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) +7. Revise os colaboradores externos que serão removidos da organização e clique em **Remove outside collaborators** (Remover colaboradores externos). ![Lista de colaboradores externos que serão removidos e botão Remove outside collaborators (Remover colaboradores externos)](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) + +### Remover um colaborador externo de um repositório específico na organização + +Se você desejar remover um colaborador externo de repositórios específicos na organização, poderá remover o acesso desse usuário a um determinado repositório por vez. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. À direita do nome de usuário do colaborador que deseja remover, use o menu suspenso {% octicon "gear" aria-label="The Settings gear" %} e clique em **Manage** (Gerenciar). ![Botão Manage access (Gerenciar acesso)](/assets/images/help/organizations/member-manage-access.png) +6. À direita do repositório do qual deseja remover o colaborador externo, clique em **Manage access** (Gerenciar acesso). ![Selecione o botão Manage access (Gerenciar acesso) ao lado do repositório ao qual o colaborador externo tem acesso](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) +7. Para remover completamente o acesso do colaborador externo ao repositório, clique em **Remove access to this repository** (Remover acesso a este repositório) no canto superior direito. ![Botão Remove access to this repository (Remover acesso a este repositório)](/assets/images/help/organizations/remove-access-to-this-repository.png) +8. Para confirmar, clique em **Remove access** (Remover acesso). ![Confirme o colaborador externo que será removido do repositório](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) + +### Leia mais + +- "[Adicionar colaboradores externos a repositórios na sua organização](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000..9b465aa499 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -0,0 +1,181 @@ +--- +title: Níveis de permissão do repositório da organização +intro: 'Você pode personalizar o acesso a cada repositório da organização com níveis granulares de permissão, fornecendo aos usuários o acesso aos recursos e às tarefas que eles precisam.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Usuários com permissões de administrador podem gerenciar acessos individuais e da equipe a um repositório de propriedade da organização. + +### Níveis de permissão para repositórios de propriedade de uma organização + +Você pode atribuir diferentes níveis de acesso aos repositórios de propriedade de uma organização a integrantes, colaboradores externos e equipes da organização. Cada nível de permissão aumenta progressivamente o acesso ao conteúdo e às configurações de um repositório. Escolha o nível mais adequado para a função de cada pessoa ou equipe do projeto, sem dar aos usuários um acesso mais abrangente do que o necessário. + +Do acesso mais restritivo ao acesso mais abrangente, estes são os níveis de permissão de um repositório da organização: +- **Read** (Leitura): recomendado para contribuidores que não escrevem códigos e desejam visualizar ou discutir o projeto +- **Triage** (Triagem): recomendado para contribuidores que precisam gerenciar proativamente problemas e pull requests sem acesso de gravação +- **Write** (Gravação): recomendado para contribuidores que proativamente fazem push no projeto +- **Maintain** (Manutenção): recomendado para gerentes de projeto que precisam gerenciar o repositório, mas não devem ter acesso a ações destrutivas ou confidenciais +- **Admin** (Administrador): recomendado para usuários que precisam ter acesso completo ao projeto, incluindo ações confidenciais e destrutivas, como gerenciar a segurança e excluir um repositório + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +Para obter mais informações sobre como atribuir acesso aos repositórios para usuários e equipes, consulte "[Gerenciar acessos aos repositórios da organização](/articles/managing-access-to-your-organizations-repositories)". + +Os proprietários da organização podem definir permissões básicas que se aplicam a todos os integrantes da organização ao acessar qualquer um dos repositórios da organização. Para obter mais informações, consulte "[Configurar permissões básicas para uma organização](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)". + +Os proprietários da organização também podem optar por limitar ainda mais o acesso a configurações e ações específicas na organização. Para obter mais informações sobre as opções para configurações específicas, consulte "[Gerenciar as configurações da organização](/articles/managing-organization-settings)". + +Além de gerenciar as configurações da organização, os proprietários da organização têm permissões de administrador em todos os repositórios de propriedade da organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization)". + +{% warning %} + +**Aviso:** quando alguém adiciona uma chave de implantação a um repositório, qualquer usuário com a chave privada pode ler e gravar no repositório (dependendo das configurações da chave), mesmo que ele seja removido posteriormente da organização. + +{% endwarning %} + +### Acesso ao repositório de cada nível de permissão +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Observação:** As permissões de repositório necessárias para usar funcionalidades de segurança estão listadas em "[Requisitos de permissões para recursos de segurança](#permission-requirements-for-security-features)" abaixo. + +{% endnote %} + +{% endif %} +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:| +| Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | +| Bifurcar os repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | +| Editar e excluir seus próprios comentários | **X** | **X** | **X** | **X** | **X** | +| Criar problemas | **X** | **X** | **X** | **X** | **X** | +| Fechar os problemas que eles criaram | **X** | **X** | **X** | **X** | **X** | +| Reabrir problemas que eles fecharam | **X** | **X** | **X** | **X** | **X** | +| Ter um problema atribuído a eles | **X** | **X** | **X** | **X** | **X** | +| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **X** | **X** | **X** | **X** | **X** | +| Enviar revisões em pull requests | **X** | **X** | **X** | **X** | **X** | +| Exibir as versões publicadas | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Editar wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Denunciar conteúdo abusivo ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +{% endif %} +| Aplicar/ignorar etiquetas | | **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" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [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 %} +| Aplicar marcos | | **X** | **X** | **X** | **X** | +| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Solicitar [revisões de pull requests](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe | | | **X** | **X** | **X** | +| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas | | | **X** | **X** | **X** | +| [Ocultar comentários de qualquer usuário](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **X** | **X** | **X** | +| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Marcar uma pull request de rascunho como pronta para revisão](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| [Converter um pull request em rascunho](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** +{% endif %} +| Enviar revisões que afetam a capacidade de merge de uma pull request | | | **X** | **X** | **X** | +| [Aplicar alterações sugeridas](/articles/incorporating-feedback-in-your-pull-request) a pull requests | | | **X** | **X** | **X** | +| Criar [verificações de status](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +{% endif %} +| Criar e editar versões | | | **X** | **X** | **X** | +| Exibir versões de rascunho | | | **X** | **X** | **X** | +| Editar a descrição de um repositório | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} +| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar pacoes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir pacotes](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Habilitar wikis e restringir editores de wiki | | | | **X** | **X** | +| Habilitar quadros de projeto | | | | **X** | **X** | +| Configurar [merges de pull request](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **X** | **X** | +| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Limitar [interações em um repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +{% endif %} +| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **X** | +| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **X** | +| [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **X** | +| Adicionar um repositório a uma equipe (consulte "[Gerenciar o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obter informações) | | | | | **X** | +| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **X** | +| Alterar as configurações do repositório | | | | | **X** | +| Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **X** | +| Editar o branch padrão do repositório | | | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| Renomeie o branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Renomeie um branch diferente do branch padrão do repositório (veja "[Renomear um 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" %} +| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +{% endif %} +| [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" %} +| [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** | +| [Transferir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) para um novo repositório | | | **X** | **X** | **X** | +| [Gerenciar discussões fixadas](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [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** | +| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +#### Requisitos de permissão para funcionalidades de segurança + +Nesta seção, você pode encontrar os níveis de permissão de repositório necessários para as funcionalidades de segurança, como os funcionalidades de {% data variables.product.prodname_advanced_security %}. + +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:| +| {% if currentVersion == "free-pro-team@latest" %} | | | | | | +| 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#granting-access-to-security-alerts) para as dependências vulneráveis | | | | | **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.22" or currentVersion == "github-ae@latest" %} +| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Habilitar o gráfico de dependências](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) em um repositório privado | | | | | **X** | +| [Visualizar as revisões de dependências](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| [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" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | +| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% if currentVersion == "enterprise-server@3.0" %} +| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [Designar outras pessoas ou equipes para receber alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) em repositórios | | | | | **X** +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +[1] Os autores e mantenedores do repositório só podem ver informações de alertas sobre seus próprios commits. +{% endif %} +{% endif %} + +### Leia mais + +- "[Gerenciar acessos aos repositórios da organização](/articles/managing-access-to-your-organization-s-repositories)" +- "[Adicionar colaboradores externos a repositórios na sua organização](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000..7b0698936f --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -0,0 +1,36 @@ +--- +title: Definir permissões básicas para uma organização +intro: Você pode definir permissões básicas para repositórios que uma organização possui. +permissions: Os proprietários da organização podem definir permissões básicas para uma organização. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Sobre as permissões básicas para uma organização + +É possível definir as permissões básicas que se aplicam a todos os integrantes da organização ao acessar qualquer um dos repositórios da organização. As permissões básicas não se aplicam a colaboradores externos. + +{% if currentVersion == "free-pro-team@latest" %}Por padrão, os integrantes de uma organização terão permissões de **Leitura** nos repositórios da organização.{% endif %} + +Se alguém com permissão de administrador no repositório de uma organização conceder a um membro um nível de permissão mais alto para o repositório, o nível mais alto de permissão irá substituir a permissão básica. + +### Definir permissões básicas + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Em "Permissões básicas", use o menu suspenso para selecionar novas permissões básicas. ![Selecionar novo nível de permissão a partir do menu suspenso de permissões básicas](/assets/images/help/organizations/base-permissions-drop-down.png) +6. Revise as alterações. Para confirmar, clique em **Alterar permissão-padrão para PERMISSÃO**. ![Revisar e confirmar a alteração das permissões básicas](/assets/images/help/organizations/base-permissions-confirm.png) + +### Leia mais + +- "[Níveis de permissão do repositório da organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" +- "[Adicionar colaboradores externos a repositórios na sua organização](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000..f9ac6f5ee6 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,41 @@ +--- +title: Exibir pessoas com acesso ao seu repositório +intro: 'Os proprietários da organização podem ver o acesso das pessoas a um repositório dentro de uma organização. Os proprietários de organizações que usam o {% data variables.product.prodname_ghe_cloud %} ou o {% data variables.product.prodname_ghe_server %} também podem exportar uma lista CSV de pessoas que têm acesso a um repositório.' +redirect_from: + - /articles/viewing-people-with-access-to-your-repository + - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Os administradores podem usar essas informações para ajudar pessoas fora do quadro, coletar dados para conformidade e outras verificações gerais de segurança. + +![Lista de permissões para pessoas no repositório](/assets/images/help/repository/repository-permissions-list.png) + +### Exibir pessoas com acesso ao seu repositório + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Observação**: Você também pode ver uma visão geral combinada das equipes e pessoas com acesso ao seu repositório. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/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 uma lista de pessoas com acesso a um repositório + +Os proprietários de organizações no {% data variables.product.prodname_ghe_cloud %} ou no {% data variables.product.prodname_ghe_server %} podem exportar uma lista CSV de pessoas que têm acesso a um repositório. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} +4. Clique em **Export CSV** (Exportar CSV). ![Guia People (Pessoas) na barra lateral do repositório](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000..6ca1cc6761 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -0,0 +1,47 @@ +--- +title: Sobre autoridades certificadas de SSH +intro: 'Com uma autoridade certificada SSH, a organização ou conta corporativa pode oferecer certificados SSH para os integrantes usarem ao acessar seus recursos com o Git.' +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/about-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Um certificado SSH é um mecanismo utilizado para uma chave SSH assinar outra chave SSH. Se você usa uma autoridade certificada (CA) SSH para fornecer certificados SSH aos integrantes da organização, você pode adicionar a CA em sua conta corporativa ou organização para permitir que integrantes da organização usem os certificados deles para acessar os recursos da organização. Para obter mais informações, consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)". + +Depois de adicionar uma CA SSH à sua organização ou conta corporativa, você pode usar a CA para assinar certificados SSH de cliente para integrantes da organização. Integrantes da organização podem usar os certificados assinados para acessar os repositórios da sua organização (e somente os repositórios da sua organização) no Git. Você pode exigir que os integrantes usem certificados SSH para acessar os recursos da organização.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Aplicar configurações de segurança na sua conta corporativa](/articles/enforcing-security-settings-in-your-enterprise-account#managing-your-enterprise-accounts-ssh-certificate-authorities)".{% endif %} + +Por exemplo, você pode desenvolver um sistema interno que emite um novo certificado para seus desenvolvedores todas as manhãs. Cada desenvolvedor pode usar o certificado diário para trabalhar nos repositórios da organização no {% data variables.product.product_name %}. No final do dia, o certificado pode expirar automaticamente, protegendo seus repositórios caso o certificado seja adulterado mais tarde. + +A cada emissão de certificado, você deve incluir uma extensão especificando para qual usuário do {% data variables.product.product_name %} é o certificado. Por exemplo, você pode usar o comando do OpenSSH `ssh-keygen` substituindo _KEY-IDENTITY_ por sua identidade chave e _USERNAME_ por um nome de usuário do {% data variables.product.product_name %}. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +Para emitir um certificado para alguém que utiliza SSH para acessar vários produtos de {% data variables.product.company_short %}, você pode incluir duas extensões de login para especificar o nome de usuário para cada produto. Por exemplo, o comando a seguir emitiria um certificado para _USERNAME-1_ para a conta do usuário para {% data variables.product.prodname_ghe_cloud %}, e _USERNAME-2_ para a conta do usuário em {% data variables.product.prodname_ghe_managed %} ou {% data variables.product.prodname_ghe_server %} em _HOSTNAME_. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +``` + +É possível restringir os endereços IP dos quais um integrante da organização pode acessar os recursos da sua organização usando uma extensão `source-address`. A extensão aceita um endereço IP específico ou um intervalo de endereços IP usando a notação CIDR. É possível especificar vários endereços ou intervalos separando os valores com vírgulas. Para obter mais informações, consulte "[Roteamento interdomínio sem classes](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" na Wikipedia. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +{% if currentVersion == "free-pro-team@latest" %} + +Integrantes da organização podem usar os certificados assinados para autenticação mesmo que você tenha aplicado o logon único SAML. A menos que você exija certificados SSH, os integrantes podem continuar a usar outros meios de autenticação para acessar os recursos da organização no Git, como o nome de usuário e senha deles, tokens de acesso pessoais e outras chaves SSH próprias. + +{% endif %} + +Para evitar erros de autenticação, os integrantes da organização devem usar uma URL especial que inclua o ID da organização para clonar repositórios usando certificados assinados. Qualquer pessoa com acesso de leitura no repositório pode localizar essa URL na página do repositório. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)". diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..0b93952342 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -0,0 +1,19 @@ +--- +title: Gerenciar acesso do Git aos repositórios da organização +intro: Você pode adicionar uma autoridade certificada (CA, certificate authority) SSH em sua organização e permitir que os integrantes acessem os repositórios da organização no Git usando as chaves assinadas pela CA SSH. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /about-ssh-certificate-authorities %} +{% link_in_list /managing-your-organizations-ssh-certificate-authorities %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000..52fe272346 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,38 @@ +--- +title: Gerenciar autoridades certificadas de SSH da organização +intro: Você pode adicionar ou excluir autoridades certificadas de SSH da organização. +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-your-organizations-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Proprietários da organização podem gerenciar as autoridades certificadas (CA, certificate authorities) de SSH da organização. + +Você pode permitir que os integrantes acessem os repositórios da organização com certificados SSH fornecidos por você, adicionando um CA SSH à organização. {% data reusables.organizations.can-require-ssh-cert %} Para obter mais informações, consulte "[Sobre autoridades certificadas de SSH](/articles/about-ssh-certificate-authorities)". + +### Adicionar uma autoridade certificada 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 %} + +### Excluir uma autoridade certificada 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/pt-BR/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md new file mode 100644 index 0000000000..2fb365033a --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -0,0 +1,29 @@ +--- +title: Adicionar pessoas à organização +intro: 'Você pode tornar qualquer pessoa um integrante da sua organização usando o respectivo nome de usuário no {% data variables.product.product_name %} ou o endereço de e-mail dela.' +redirect_from: + - Adding people to your organization + - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization +versions: + enterprise-server: '*' + github-ae: '*' +permissions: 'Os proprietários da organização podem adicionar pessoas a uma organização.' +--- + +{% if currentVersion != "github-ae@latest" %} +Se sua organização [exige que os integrantes usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), os usuários deverão [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) para que você possa adicioná-los à organização. +{% 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 %} + +### Leia mais +- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000..51d8c2a149 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,21 @@ +--- +title: Posso criar contas para as pessoas na minha organização? +intro: 'Embora você possa adicionar usuários a uma organização que criou, não é possível criar contas de usuário pessoais em nome de outra pessoa.' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization + - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Como você acessa uma organização entrando em uma conta pessoal, cada um dos integrantes da equipe precisa de uma conta pessoal. Uma vez que você tem nomes de usuário para cada pessoa que deseja adicionar à sua organização, você pode adicioná-las às equipes. + +### Adicionar usuários à organização + +1. Forneça a cada pessoa instruções para [criar uma conta pessoal](/articles/signing-up-for-a-new-github-account). +2. Peça o nome de usuário de cada pessoa a quem deseja conceder associação à organização. +3. [Convide as novas contas pessoais para ingressar](/articles/inviting-users-to-join-your-organization) na sua organização. Use as [funções da organização](/articles/permission-levels-for-an-organization) e [permissões de repositório](/articles/repository-permission-levels-for-an-organization) para limitar o acesso de cada conta. diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000..f8a023677a --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Cancelar ou editar um convite para ingressar na organização +intro: Os proprietários da organização podem editar ou cancelar um convite para se tornar um integrante da sua organização a qualquer momento antes da aceitação do usuário. +redirect_from: + - /articles/canceling-or-editing-an-invitation-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Na guia People (Pessoas), clique em **Pending invitation** (Convite pendente). ![Link de convite pendente](/assets/images/help/organizations/pending-invitation-link.png) +5. Ao lado do nome de usuário ou do endereço de e-mail da pessoa cujo convite você deseja editar ou cancelar, clique em **Edit invitation** (Editar convite). ![Botão Edit invitation (Editar convite)](/assets/images/help/organizations/edit-invitation-button.png) + + Talvez seja necessário clicar em **View all invitations** (Exibir todos os convites) na parte inferior da janela para encontrar a pessoa que está procurando. +6. Você pode optar por editar ou cancelar o convite do usuário para ingressar na organização. ![Botões Update invitation (Atualizar convite) e cancel invitation (Cancelar convite)](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) + - Para editar o convite do usuário, selecione uma função ou equipe diferente e clique em **Update invitation** (Atualizar convite). + - Para cancelar o convite do usuário para ingressar na organização, clique em **Cancel invitation** (Cancelar convite). + +### Leia mais + +{% if currentVersion == "free-pro-team@latest" %} +- "[Convidar usuários para ingressar na organização](/articles/inviting-users-to-join-your-organization)" +{% endif %} +- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md new file mode 100644 index 0000000000..5a3f5c0bea --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md @@ -0,0 +1,23 @@ +--- +title: Gerenciar associação na organização +intro: 'Depois de criar a sua organização, você pode {% if currentVersion == "free-pro-team@latest" %}convide pessoas para se tornar {% else %}adicionar pessoas como{% endif %} integrantes da organização. Você também pode remover integrantes da organização e restabelecer ex-integrantes.' +redirect_from: + - /articles/removing-a-user-from-your-organization/ + - /articles/managing-membership-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000..04c75fe31e --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Convidar usuários para sua organização +intro: 'É possível convidar qualquer pessoa para integrar sua organização usando o nome de usuário {% data variables.product.product_name %} ou endereço de e-mail dela.' +permissions: Os proprietários da organização podem convidar usuários para participar de uma organização. +redirect_from: + - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ + - /articles/inviting-users-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Dicas**: +- Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %} +- Se a sua organização exige que os integrantes usem a autenticação de dois fatores, os usuários que você convidar deverão ativar a autenticação de dois fatores antes de aceitar o convite. Para mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" e[Proteger a sua conta com a autenticação de dois fatores (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 %} + +### Leia mais +- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000..fca1bf02fa --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,63 @@ +--- +title: Restabelecer ex-integrantes da organização +intro: 'Os proprietários da organização podem {% if currentVersion == "free-pro-team@latest" %}convidar os antigos integrantes da organização para juntar-se novamente a{% else %}adicionar ex-integrantes à{% endif%} sua organização e escolher se desejam restaurar as funções anteriores da pessoa, acessar as permissões, bifurcações e configurações.' +redirect_from: + - /articles/reinstating-a-former-member-of-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: Os proprietários da organização podem restabelecer um antigo integrante de uma organização. +topics: + - organizations + - teams +--- + +### Sobre a reintegração de integrantes + +Se você [remover um usuário da sua organização](/articles/removing-a-member-from-your-organization){% if currentVersion == "github-ae@latest" %} ou{% else %},{% endif %} [converter um integrante da organização em um colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator){% if currentVersion != "github-ae@latest" %}, ou um usuário foi removido da sua organização porque você [exigiu que os integrantes e colaboradores externos habilitassem a autenticação de dois fatores (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, os privilégios e configurações do usuário ficarão salvos por três meses. Você pode restaurar os privilégios do usuário se você {% if currentVersion =="free-pro-team@latest" %}convidá-los{% else %}adicioná-los{% endif %} à organização nesse período de tempo. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +Ao restabelecer um ex-integrante da organização, você pode restaurar: + - A função do usuário na organização + - As bifurcações privadas de repositórios de propriedade da organização + - A associação nas equipes da organização + - Os acessos e permissões anteriores nos repositórios da organização + - As estrelas dos repositórios da organização + - As atribuições de problemas na organização + - As assinaturas do repositório (configurações de notificação para inspecionar, não inspecionar ou ignorar as atividades de um repositório) + +{% if enterpriseServerVersions contains currentVersion %} +Se um integrante foi removido da organização por não usar a autenticação de dois fatores e a organização ainda exigir essa autenticação, o ex-integrante precisará habilitar a autenticação de dois fatores antes de você restabelecer a associação. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Se a sua organização tem uma assinatura paga por usuário, uma licença não utilizada deve estar disponível antes de você poder restabelecer um antigo integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %} +{% endif %} + +### Restabelecer ex-integrantes da organização + +{% 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. Escolha se deseja restaurar os privilégios anteriores da pessoa na organização ou apagar os privilégios anteriores e definir novas permissões de acesso, depois clique em **Invite and reinstate** (Convidar e restabelecer) ou em **Invite and start fresh** (Convidar e começar do zero). ![Escolher restaurar as informações ou não](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Escolha se deseja restaurar os privilégios anteriores da pessoa na organização ou apagar os privilégios anteriores e definir novas permissões de acesso, depois clique em **Add and reinstate** (Adicionar e restabelecer) ou em **Add and start fresh** (Adicionar e começar do zero). ![Escolher se deseja restaurar os privilégios](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. Se você apagou os privilégios anteriores de um ex-integrante da organização, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Send invitation** (Enviar convite). ![Opções Role and team (Função e equipe) e botão send invitation (enviar convite)](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. Se você apagou os privilégios anteriores de um ex-integrante da organização, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Add member** (Adicionar integrante). ![Opções Role and team (Função e equipe) e botão add member (adicionar integrante)](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Leia mais + +- "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000..d93ee6d9a3 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -0,0 +1,60 @@ +--- +title: Remover um integrante da organização +intro: 'Se integrantes não precisarem mais acessar os repositórios pertencentes à organização, você poderá removê-los da organização.' +redirect_from: + - /articles/removing-a-member-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Somente proprietários da organização podem remover integrantes da organização. + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Aviso:** Ao remover integrantes de uma organização: +- O número de licenças pagas não faz o downgrade automaticamente. Para pagar menos licenças depois de remover os usuários da sua organização, siga as etapas em "[Fazer o downgrade das estações pagas da sua organização](/articles/downgrading-your-organization-s-paid-seats)". +- Os integrantes removidos perderão o acesso às bifurcações privadas dos repositórios privados da sua organização, mas ainda poderão ter cópias locais. No entanto, eles não conseguem sincronizar as cópias locais com os repositórios da organização. As bifurcações privadas poderão ser restauradas se o usuário for [restabelecido como um integrante da organização](/articles/reinstating-a-former-member-of-your-organization) em até três meses após sua remoção da organização. Em última análise, você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual. +- Quaisquer convites para organizações enviados por um integrante removido que não foram aceitos, serão cancelados e não serão acessíveis. + +{% endwarning %} + +{% else %} + +{% warning %} + +**Aviso:** Ao remover integrantes de uma organização: + - Os integrantes removidos perderão o acesso às bifurcações privadas dos repositórios privados da sua organização, mas ainda poderão ter cópias locais. No entanto, eles não conseguem sincronizar as cópias locais com os repositórios da organização. As bifurcações privadas poderão ser restauradas se o usuário for [restabelecido como um integrante da organização](/articles/reinstating-a-former-member-of-your-organization) em até três meses após sua remoção da organização. Em última análise, você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual. + - Quaisquer convites para organizações enviados pelo usuário removido, que não foram aceitos, serão cancelados e não serão acessíveis. + +{% endwarning %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +Para auxiliar a transição e garantir a exclusão das informações confidenciais ou de propriedade intelectual, recomendamos o compartilhamento de uma lista de práticas recomendadas ao sair da organização com o usuário que está sendo removido. Consulte um exemplo em "[Práticas recomendadas para sair da empresa](/articles/best-practices-for-leaving-your-company/)". + +{% endif %} + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} + +### Revogar a associação do usuário + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Selecione um ou mais integrantes que deseja remover da organização. ![Lista de integrantes com dois integrantes selecionados](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Acima da lista de integrantes, use o menu suspenso e clique **Remove from organization** (Remover da organização). ![Menu suspenso com opção de remover integrantes](/assets/images/help/teams/user-bulk-management-options.png) +6. Revise os integrantes que serão removidos da organização e clique em **Remove members** (Remover integrantes). ![Lista de integrantes que serão removidos e botão Remove members (Remover integrantes)](/assets/images/help/teams/confirm-remove-members-bulk.png) + +### Leia mais + +- "[Remover integrantes da organização de uma equipe](/articles/removing-organization-members-from-a-team)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000..6a232b4a35 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Permitir que as pessoas excluam problemas em sua organização +intro: Os proprietários da organização podem permitir que determinadas pessoas excluam problemas em repositórios que pertencem à sua organização. +redirect_from: + - /articles/allowing-people-to-delete-issues-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Por padrão, os problemas não podem ser excluídos dos repositórios de uma organização. Um proprietário da organização deve habilitar esse recurso primeiro para todos os repositórios da organização. + +Uma vez habilitado, os proprietários da organização e as pessoas com permissões de administrador em um repositório pertencente à organização podem excluir os problemas. As pessoas com permissões de administrador em um repositório incluem integrantes da organização e colaboradores externos com privilégios administrativos. Para obter mais informações, consulte "[ Níveis de permissão do repositório da organização](/articles/repository-permission-levels-for-an-organization/)" e "[Excluir um problema](/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. Em "Issue deletion" (Exclusão do problema), selecione **Allow members to delete issues for this organization** (Permitir que integrantes excluam problemas dessa organização). ![Caixa de seleção para permitir que as pessoas excluam problemas](/assets/images/help/settings/issue-deletion.png) +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000..422fd8c4e3 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,24 @@ +--- +title: Alterar a visibilidade de informações de dependência da organização +intro: Você pode permitir que todos os integrantes da organização exibam informações de dependência da sua organização ou limitar a exibição aos proprietários da organização. +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/changing-the-visibility-of-your-organizations-dependency-insights + - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Os proprietários da organização podem definir limitações para exibir informações de dependência da organização. Todos os integrantes de uma organização podem exibir informações de dependência da organização por padrão. + +Os proprietários corporativos podem definir limitações para exibir informações de dependência da organização em todas as organizações da sua conta corporativa. Para obter mais informações, consulte "[Aplicar uma política nas informações de dependência de sua conta corporativa](/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. Em "Member organization permissions" (Permissões da organização do integrante), marque ou desmarque **Allow members to view dependency insights** (Permitir que integrantes exibam informações de dependência). ![Caixa de seleção para permitir que integrantes exibam informações](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000..d2fd5fbb06 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,22 @@ +--- +title: Configurar o período de retenção para artefatos e registros do GitHub Actions na sua organização +intro: 'Você pode configurar o período de retenção para artefatos e registros de {% data variables.product.prodname_actions %} da sua organização.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.actions.about-artifact-log-retention %} + +## Definir o período de retenção para uma organização + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +{% data reusables.github-actions.change-retention-period-for-artifacts-logs %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000..43b37580a7 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -0,0 +1,33 @@ +--- +title: Converter uma organização em usuário +intro: 'Não é possível converter uma organização em uma conta de usuário pessoal, mas você pode criar uma conta de usuário e transferir para ela os repositórios da organização.' +redirect_from: + - /articles/converting-an-organization-into-a-user + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +1. [Inscreva-se](/articles/signing-up-for-a-new-github-account) para uma nova conta de usuário do GitHub. +2. [Altere a função do usuário para um proprietário](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} na nova conta de usuário. +4. [Transfira cada repositório da organização](/articles/how-to-transfer-a-repository) para a nova conta de usuário. +5. [Exclua a organização](/articles/deleting-an-organization-account). +6. [Renomeie o usuário](/articles/changing-your-github-username) para o nome da organização. + +{% else %} + +1. Inscreva-se para uma nova conta de usuário do GitHub Enterprise GitHub Enterprise. +2. [Altere a função do usuário para um proprietário](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} na nova conta de usuário. +4. [Transfira cada repositório da organização](/articles/how-to-transfer-a-repository) para a nova conta de usuário. +5. [Exclua a organização](/articles/deleting-an-organization-account). +6. [Renomeie o usuário](/articles/changing-your-github-username) para o nome da organização. + +{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md new file mode 100644 index 0000000000..9e04d7c307 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -0,0 +1,34 @@ +--- +title: Excluir uma conta de organização +intro: 'Quando você exclui uma organização, todos os repositórios, bifurcações de repositórios privados, wikis, problemas, pull requests e páginas de projeto ou de organização são excluídos também. {% if currentVersion == "free-pro-team@latest" %}O nome da organização fica disponível para uso em uma nova conta de usuário ou organização, e a cobrança será encerrada{% endif %}' +redirect_from: + - /articles/deleting-an-organization-account + - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**Dica**: caso queira cancelar sua assinatura paga, [faça downgrade da sua organização para {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) em vez de excluir a organização e o conteúdo dela. + +{% endtip %} + +{% endif %} + +### 1. Fazer backup do conteúdo da organização + +Depois que você exclui uma organização, o GitHub **não pode restaurar o conteúdo que você tem lá**. Portanto, antes de excluir sua organização, certifique-se de ter uma cópia de todos os repositórios, wikis, problemas e quadros de projetos da conta. + +### 2. Excluir a organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Próximo à parte inferior da página de configurações da organização, clique em **Delete this Organization** (Excluir esta organização). ![Botão Delete this organization (Excluir esta organização)](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000..aaeb86ba07 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,85 @@ +--- +title: Desabilitar ou limitar o GitHub Actions para sua organização +intro: 'Os proprietários da organização podem desabilitar, habilitar e limitar o GitHub Actions para uma organização.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### Sobre as permissões de {% data variables.product.prodname_actions %} para a sua organização + +{% data reusables.github-actions.disabling-github-actions %} Para mais informações sobre {% data variables.product.prodname_actions %}, consulte "[Sobre {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." + +Você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.enabled-actions-description %} Você pode desabilitar {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.disabled-actions-description %} + +Como alternativa, você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios na sua organização e limitar as ações que um fluxo de trabalho pode executar. {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Em **Ações locais e de terceiros**, selecione uma opção. ![Habilitar, desabilitar ou limitar ações para esta organização](/assets/images/help/repository/enable-org-actions.png) +1. Clique em **Salvar**. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua organização + +Você pode desabilitar todos os fluxos de trabalho para uma organização ou definir uma política que configura quais ações podem ser usadas em uma organização. + +{% data reusables.actions.actions-use-policy-settings %} + +{% note %} + +**Observação:** Talvez você não consiga gerenciar essas configurações se a sua organização for gerenciada por uma empresa que tem uma política de substituição. Para obter mais informações, {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account).{% else %}"[Aplicar políticas de {% data variables.product.prodname_actions %} para a sua empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise).{% endif %} + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Em **Políticas**, selecione uma opção. ![Definir política de ações para esta organização](/assets/images/help/organizations/actions-policy.png) +1. Clique em **Salvar**. + +### Permitir a execução de ações 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. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Clique em **Salvar**. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Habilitar fluxos de trabalho para bifurcações privadas do repositório + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configurar a política de bifurcação privada para uma organização + +{% 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/pt-BR/content/organizations/managing-organization-settings/index.md b/translations/pt-BR/content/organizations/managing-organization-settings/index.md new file mode 100644 index 0000000000..ceba932561 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/index.md @@ -0,0 +1,39 @@ +--- +title: Gerenciar as configurações da organização +intro: 'Administradores da organização podem alterar várias configurações, inclusive o nome dos repositórios pertencentes à organização e a associação de proprietários de equipes. Além disso, os administradores da organização podem excluir a organização e todos os repositórios dela.' +redirect_from: + - /articles/managing-organization-settings + - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 /managing-the-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 %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000..d20b893d89 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,26 @@ +--- +title: Integrar o Jira com o quadro de projetos da organização +intro: 'É possível integrar o Jira Cloud à conta de sua organização para analisar commits e pull requests, criando metadados e hyperlinks relevantes em qualquer problema mencionado no Jira.' +redirect_from: + - /articles/integrating-jira-with-your-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. Na barra lateral esquerda, em **Organization settings** (Configurações da organização) clique no nome de sua organização. ![Barra lateral organization name (nome da organização)](/assets/images/help/settings/organization-settings-from-sidebar.png) +3. Na barra lateral esquerda, em **Developer settings** (Configurações do desenvolvedor), clique em **OAuth applications** (Aplicativos OAuth) ![Aba OAuth applications (aplicativos OAuth) na barra lateral esquerda](/assets/images/help/organizations/org-oauth-applications-ghe.png) +4. Clique em **Register a new application** (Registrar novo aplicativo). +5. Em **Application name** (Nome do aplicativo), digite "Jira". +6. Em **Homepage URL** (URL da página inicial), digite a URL completa da sua instância do JIRA. +7. Em **Authorization callback URL** (URL de revogação de autorização), digite a URL completa da sua instância do JIRA. +8. Clique em **Register application** (Registrar aplicativo). ![Botão Register application (registrar aplicativo)](/assets/images/help/oauth/register-application-button.png) +9. Em **Organization owned applications** (Aplicativos de propriedade da organização), anote os valores "Client ID" (ID do cliente) e "Client Secret" (Chave secreta do cliente). ![Client ID (ID do cliente) e Client Secret (Chave secreta do cliente)](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### Leia mais + +- ["Integrar o Jira com seus projetos pessoais"](/articles/integrating-jira-with-your-personal-projects) +- Conectar o Jira Cloud ao GitHub (documentação Atlassian) diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..1c74cc82fb --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,67 @@ +--- +title: Gerenciar etiquetas padrão para repositórios na organização +intro: É possível personalizar as etiquetas que são incluídas em cada repositório novo na organização. +redirect_from: + - /articles/managing-default-labels-for-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +Os proprietários da organização podem gerenciar as etiquetas padrão para repositórios na organização. + +As etiquetas padrão são incluídas em cada repositório novo na organização, mas qualquer pessoa com acesso de gravação ao repositório pode editá-las ou excluí-las nesse repositório mais tarde. Adicionar, editar ou excluir uma etiqueta padrão não adiciona, edita ou exclui essa etiqueta dos repositórios existentes. + +### Criar etiquetas padrão + +{% 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. Em "Repository labels" (Etiquetas de repositório), clique em **New label** (Nova etiqueta). ![Botão New label (Nova etiqueta)](/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 etiquetas padrão + +{% 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 %} + +### Excluir etiquetas padrão + +{% 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 %} + +### Leia mais + +- "[Sobre etiquetas](/articles/about-labels)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..218717b30f --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Gerenciar criação de discussões para repositórios na sua organização +intro: Você pode escolher os níveis de permissão exigidos pelos integrantes para criar discussões em repositórios pertencentes à sua organização. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization +permissions: Os proprietários da organização podem gerenciar a criação de discussões para repositórios pertencentes à organização. +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.discussions.beta %} + +### Permitir ou impedir usuários com acesso de leitura para criar discussões + +Por padrão, integrantes da organização com acesso de leitura podem criar discussões se um administrador ou proprietário da organização habilitar discussões para um repositório pertencente à organização. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Em "Discussões do repositório, selecione ou desmarque **Permitir que os usuários com acesso de leitura criem discussões**. ![Caixa de seleção para permitir que pessoas com acesso de leitura criem discussões](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. Clique em **Salvar**. ![Botão "Salvar" para configurações de discussões](/assets/images/help/discussions/click-save.png) + +### Leia mais + +- "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Gerenciar discussões para a sua comunidade](/discussions/managing-discussions-for-your-community)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000..4dbff0ed8a --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,66 @@ +--- +title: Gerenciar lembretes agendados para a sua organização +intro: Você pode obter lembretes no Slack para todos os pull requests que as equipes em sua organização foram solicitadas para revisar. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Sobre lembretes agendados para pull requests + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Os proprietários da organização podem agendar um lembrete para uma ou mais equipes na sua organização, para todos os pull requests que a equipe ou equipes foram solicitadas revisar. + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Criar um lembrete agendado para uma organização +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botão de lembretes agendados](/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. Em "Filtrar por equipe atribuída ao código de revisão", clique no menu suspenso **Adicionar uma equipe** e escolha uma ou mais equipes. Você pode adicionar até 100 equipes. Se a equipe selecionada não tiver acesso aos "repositórios rastreados" selecionados acima, você não será conseguirá criar o lembrete agendado. ![Menu suspenso para Adicionar equipe](/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 %} + +### Gerenciar um lembrete agendado para uma organização +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botão de lembretes agendados](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Excluir um lembrete agendado para uma organização +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Botão de lembretes agendados](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.delete %} + +### Leia mais + +- "[Gerenciar seus lembretes agendados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" +- "[Gerenciar lembretes agendados para a sua equipe](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..b6ff702f37 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Gerenciar o nome de branch-padrão para repositórios na sua organização +intro: 'Você pode definir o nome do branch-padrão para repositórios que os integrantes criam na sua organização em {% data variables.product.product_location %}.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +permissions: Os proprietários da organização podem gerenciar o nome do branch-padrão para novos repositórios na organização. +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Sobre o gerenciamento do nome do brancc-padrão + +Quando um integrante da sua organização cria um novo repositório na sua organização, o repositório contém um branch, que é o branch-padrão. Você pode alterar o nome que {% data variables.product.product_name %} usa para o branch-padrão em novos repositórios que os integrantes da sua organização criam. Para obter mais informações sobre o branch padrão, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". + +{% data reusables.branches.change-default-branch %} + +Se um proprietário da empresa tiver aplicado uma política para o nome do branch padrão para sua empresa, você não poderá definir um nome do branch padrão para sua organização. Em vez disso, você pode alterar o branch padrão para repositórios individuais. Para mais informações, consulte {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de gerenciamento do repositório na sua empresa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)"{% else %}[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)"{% endif %} e "[Alterar o branch padrão](/github/administering-a-repository/changing-the-default-branch)". + +### Definir o nome do branch-padrão + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. Em "Branch padrão do repositório", clique em **Alterar o nome do branch-padrão agora**. ![Botão de sobrescrever](/assets/images/help/organizations/repo-default-name-button.png) +4. Digite o nome-padrão que você gostaria de usar para novos branches. ![Caixa de texto para digitar o nome-padrão](/assets/images/help/organizations/repo-default-name-text.png) +5. Clique em **Atualizar**. ![Botão de atualizar](/assets/images/help/organizations/repo-default-name-update.png) + +### Leia mais + +- "[Gerenciar o nome do branch-padrão para seus repositórios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000..751785a911 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,28 @@ +--- +title: Gerenciar a exibição dos nomes de integrantes na organização +intro: Você pode permitir que integrantes da organização vejam o nome de perfil do autor de um comentário nos repositórios privados da organização. +product: '{% data reusables.gated-features.display-names %}' +redirect_from: + - /articles/managing-the-display-of-member-names-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Proprietários de organização podem gerenciar a exibição do nome de integrantes na organização. + +![Nome de perfil do autor do comentário exibido no comentário](/assets/images/help/issues/commenter-full-name.png) + +Cada integrante da organização escolhe o próprio nome de perfil nas configurações. Para obter mais informações, consulte "[Personalizar seu 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. Em "Admin repository permissions" (Permissões do administrador do repositório), marque ou desmarque **Allow members to see comment author's profile name in private repositories** (Permitir que integrantes vejam nome de perfil do autor nos repositórios privados). ![Caixa de seleção para permitir que integrantes vejam o nome completo do autor do comentário nos repositórios privados](/assets/images/help/organizations/allow-members-to-view-full-names.png) +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000..586f2109e8 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Gerenciar a política de bifurcação da sua organização +intro: 'Você pode permitir ou impedir a bifurcação de qualquer repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} ou interno{% endif %} pertencentes à sua organização.' +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization +permissions: Os proprietários da organização podem gerenciar a política de bifurcação de uma organização. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Por padrão, as novas organizações são configuradas para impedir a bifurcação dos repositórios privados {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} e internos{% endif %}. + +Se você permite a bifurcação do repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} e interno{% endif %} no nível da organização você também pode configurar a capacidade de bifurcar um repositório privado específico{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou interno{% endif %}. Para obter mais informações, consulte "[Gerenciar a política de bifurcação do seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". + +{% 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. Em "Bifurcação do repositório", selecione **Permitir bifurcação de repositórios privados** ou **Permitir bifurcação de repositórios internos e privados**. ![Caixa de seleção para permitir ou proibir a bifurcação na organização](/assets/images/help/repository/allow-disable-forking-organization.png) +6. Clique em **Salvar**. + +### Leia mais + +- "[Sobre bifurcações](/articles/about-forks)" +- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..bb1f354068 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Gerenciar a publicação dos sites do GitHub Pages para a sua organização +intro: 'Você pode controlar se os integrantes da organização podem publicar sites de {% data variables.product.prodname_pages %} a partir de repositórios na organização{% if currentVersion == "free-pro-team@latest" %} e restringir as visibilidades que os integrantes podem escolher para os sites{% endif %}.' +permissions: 'Os proprietários da organização podem gerenciar a publicação de sites de {% data variables.product.prodname_pages %} a partir de repositórios na organização.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Caso contrário, você pode optar por permitir ou negar a publicação pública. Para obter mais informações sobre controle de acesso para sites de {% data variables.product.prodname_pages %}, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". +{% endif %} + +Se você não permitir a publicação de sites de {% data variables.product.prodname_pages %}, todos os sites publicados permanecerão publicados. Você pode remover manualmente a publicação do site. Para obter mais informações, consulte "[Cancelar a publicação de um site do {% data variables.product.prodname_pages %}](/pages/getting-started-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 %}{% if currentVersion == "free-pro-team@latest" %} +1. Em "Criação de páginas", selecione as visibilidades que você deseja permitir e desmarque as visibilidades que você não deseja permitir. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Em "Criação de páginas", marque ou desmarque **Permitir que os integrantes publiquem sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Clique em **Salvar**. + +### Leia mais + +- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..947e7f22a8 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,28 @@ +--- +title: Gerenciar atualizações de contas que a sua organização patrocina +intro: Você pode gerenciar o endereço de e-mail que recebe atualizações de contas patrocinadas pela sua organização. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors +versions: + free-pro-team: '*' +permissions: Os proprietários da organização podem gerenciar atualizações a partir de contas que a organização patrocina. +topics: + - organizations + - teams +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +Os desenvolvedores e as organizações que sua organização patrocina podem enviar atualizações sobre o seu trabalho para você. Você pode gerenciar o endereço de e-mail que recebe essas atualizações. + +Você também pode desabilitar atualizações de contas que a sua organização patrocina. Para obter mais informações, consulte "[Gerenciar o patrocínio](/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. Em "E-mail de atualização de patrocínios (Privado)", digite o endereço de e-mail em que deseja receber atualizações de contas patrocinadas pela sua organização. ![Caixa de texto para inserir o endereço de email para receber atualizações de contas patrocinadas](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. Clique em **Update profile** (Atualizar perfil). ![Botão Update profile (Atualizar perfil)](/assets/images/help/organizations/update-profile-button.png) + +### Leia mais + +- "[Apoiar a comunidade de código aberto com {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md new file mode 100644 index 0000000000..08a84b12a3 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -0,0 +1,50 @@ +--- +title: Renomear uma organização +intro: 'Se seu projeto ou sua empresa mudarem de nome, atualize o nome da organização.' +redirect_from: + - /articles/what-happens-when-i-change-my-organization-s-name/ + - /articles/renaming-an-organization + - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Dica:** somente proprietários da organização podem renomear a organização. {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +### O que acontece quando eu altero o nome da organização? + +Depois que você altera o nome da organização, o nome antigo da organização fica disponível para ser usado por outra pessoa. Quando você altera o nome da organização, a maioria das referências ao repositórios no nome antigo da organização é alterada automaticamente para o novo nome. No entanto, alguns links para seu perfil não são redirecionados automaticamente. + +#### Alterações que ocorrem automaticamente + +- O {% data variables.product.prodname_dotcom %} redireciona automaticamente as referências aos seus repositórios. Os links da web para os **repositórios** da organização continuarão a funcionar. Esse processo pode demorar alguns minutos após a alteração. +- Você pode continuar a fazer push dos repositórios locais para a URL de controle do remote antigo sem atualizá-lo. No entanto, recomendamos que você atualize todas as URLs do repositório remoto depois de alterar o nome da organização. Como o nome antigo da organização ficou disponível para uso por qualquer pessoa após a alteração, o proprietário da nova organização pode criar repositórios que sobrescrevem as entradas de redirecionamento para o seu repositório. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +- Os Git commits anteriores também serão atribuídos corretamente ao usuários na sua organização. + +#### Alterações que não são automáticas + +Depois de alterar o nome da organização: +- Os links para a página de perfil da organização anterior, como `https://{% data variables.command_line.backticks %}/previousorgname`, retornarão um erro 404. Recomendamos que você atualize os links para a sua organização a partir de outros sites{% if currentVersion == "free-pro-team@latest" %}, como, por exemplo, os seus perfis do LinkedIn ou do Twitter{% endif %}. +- As solicitações de API que usam o nome antigo da organização retornarão um erro 404. Recomendamos que você atualize o nome da organização nas solicitações de API. +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} + +### Alterar o nome da organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Perto da parte inferior da página de configuração, em "Rename organization" (Renomear organização), clique em **Rename Organization** (Renomear organização). ![Botão Rename organization (Renomear organização)](/assets/images/help/settings/settings-rename-organization.png) + +### Leia mais + +* "[Por que meus commits estão vinculados ao usuário errado?](/articles/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000..fb39403845 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,35 @@ +--- +title: Restringir a criação de repositórios na organização +intro: 'Para proteger os dados da organização, você pode configurar as permissões de criação de repositórios na organização.' +redirect_from: + - /articles/restricting-repository-creation-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Você pode escolher se os integrantes podem criar repositórios na sua organização. Se você permitir que os integrantes criem repositórios, você poderá escolher quais tipos de repositórios os integrantes poderão criar.{% if currentVersion == "free-pro-team@latest" %} Para permitir que os integrantes criem apenas repositórios privados, a sua organização deve usar {% data variables.product.prodname_ghe_cloud %}.{% endif %} Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +Os proprietários da organização sempre podem criar qualquer tipo de repositório. + +{% if currentVersion == "free-pro-team@latest" %}Os proprietários da empresa{% else %}administradores do site{% endif %} podem restringir as opções disponíveis para você para a política de criação de repositório da sua organização. Para obter mais informações, consulte {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de gerenciamento do repositório na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account).{% else %}"[Restringir a criação do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %} + +{% warning %} + +**Aviso**: Essa configuração restringe apenas as opções de visibilidade disponíveis quando os repositórios são criados e não restringe a capacidade de alterar a visibilidade do repositório mais tarde. Para obter mais informações sobre restringir alterações em visibilidades de repositórios existentes, consulte "[Restringindo alterações da visibilidade do repositório na sua organização](/organizations/managing-organization-settings/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. Em "Criação do repositório", selecione uma ou mais opções. ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..c265785a60 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Restringir as alterações de visibilidade de repositório na organização +intro: 'Para proteger os dados da organização, você pode configurar as permissões de alteração da visibilidade do repositório na organização.' +redirect_from: + - /articles/restricting-repository-visibility-changes-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Você pode restringir a capacidade de alterar a visibilidade do repositório apenas para os proprietários da organização, ou permitir que os integrantes com privilégios de administrador de um repositório também alterem a visibilidade. + +{% warning %} + +**Aviso**: Se habilitada, esta configuração permite que pessoas com permissões de administrador alterem um repositório existente para qualquer visibilidade, mesmo que você não permita que esse tipo de repositório seja criado. Para obter mais informações sobre restringir a visibilidade de repositórios existentes durante a criação, consulte "[Restringindo a criação do repositório na sua organização](/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. Em "Repository visibility change" (Alteração da visibilidade do repositório), desmarque a opção **Allow members to change repository visibilities for this organization** (Permitir que os integrantes alterem a visibilidade dos repositórios nesta organização). ![Caixa de seleção para permitir que os integrantes alterem a visibilidade dos repositórios](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) +6. Clique em **Salvar**. + +### Leia mais + +- "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000..4d0b81bfda --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,28 @@ +--- +title: Configurar permissões para adicionar colaboradores externos +intro: 'Para proteger os dados da organização e o o número de licenças pagas usadas, você pode permitir que somente proprietários convidem colaboradores externos para os repositórios da organização.' +product: '{% data reusables.gated-features.restict-add-collaborator %}' +redirect_from: + - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories/ + - /articles/setting-permissions-for-adding-outside-collaborators + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Os proprietários da organização e integrantes com privilégios de administrador para um repositório podem convidar colaboradores externos para trabalhar no repositório. Você também pode restringir as permissões de convites de colaboradores externos para apenas proprietários de organizações. + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Em "Convites para o repositório", selecione **Permitir que os integrantes convidem colaboradores externos para repositórios desta organização**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %} +![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %} +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000..afe1142378 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,24 @@ +--- +title: Definir permissões para excluir ou transferir repositórios +intro: 'Você pode permitir que integrantes da organização com permissões de administrador no repositório excluam ou transfiram o repositório, ou limitem a capacidade de excluir ou transferir repositórios aos proprietários da organização.' +redirect_from: + - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ + - /articles/setting-permissions-for-deleting-or-transferring-repositories + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Proprietários podem definir permissões para excluir ou transferir repositórios na organização. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Em "Repository deletion and transfer" (Exclusão e transferência de repositório), marque ou desmarque a opção **Allow members to delete or transfer repositories for this organization** (Permitir que os integrantes excluam ou transfiram repositórios na organização). ![Caixa de seleção para permitir que os integrantes excluam repositórios](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000..5c0bb44933 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Configurar permissões de criação de equipes na organização +intro: Você pode permitir que os integrantes da organização criem equipes ou limitar a criação de equipes aos proprietários da organização. +redirect_from: + - /articles/setting-team-creation-permissions-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Os proprietários da organização podem configurar permissões de criação de equipes. + +Se você não configurar as permissões de criação de equipes, todos os integrantes da organização poderão criar equipes por padrão. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Em "Team creation rules" (Regras de criação de equipes), marque ou desmarque a opção **Allow members to create teams** (Permitir que integrantes criem equipes). ![Caixa de seleção para permitir que integrantes criem equipes](/assets/images/help/organizations/allow-members-to-create-teams.png) +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md new file mode 100644 index 0000000000..3867e8c442 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -0,0 +1,29 @@ +--- +title: Transferir a propriedade da organização +intro: 'Para tornar outra pessoa proprietária de uma conta de organização, você deve adicionar um novo proprietário{% if currentVersion == "free-pro-team@latest" %}, certifique-se de que as informações de cobrança estejam atualizadas,{% endif %} e, em seguida, remova o usuário da conta.' +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership + - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +1. Caso você seja o único integrante com privilégios de *proprietário*, atribua a função de proprietário a outro integrante da organização. Para obter mais informações, consulte "[Designar um proprietário da organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)". +2. Entre em contato com o novo proprietário e verifique se ele consegue [acessar as configurações da organização](/articles/accessing-your-organization-s-settings). +{% if currentVersion == "free-pro-team@latest" %} +3. Se você é o atual responsável pelo pagamento do GitHub na organização, também precisará pedir ao novo proprietário ou a um [gerente de cobrança](/articles/adding-a-billing-manager-to-your-organization/) que atualize as informações de pagamento da organização. Para obter mais informações, consulte "[Adicionar ou editar forma de pagamento](/articles/adding-or-editing-a-payment-method)". + + {% warning %} + + **Aviso**: remover a si mesmo da organização **não** atualiza as informações de cobrança no arquivo referentes à conta da organização. O novo proprietário ou um gerente de cobrança deve atualizar as informações de cobrança no arquivo para apagar suas informações de cartão de crédito ou PayPal. + + {% endwarning %} + +{% endif %} +4. [Remova a si mesmo](/articles/removing-yourself-from-an-organization) da organização. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/pt-BR/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000..4a843c3055 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,24 @@ +--- +title: Atualizar para os Termos de serviço corporativos +intro: As organizações podem atualizar dos Termos de serviço padrão para os Termos de serviço corporativos. +redirect_from: + - /articles/upgrading-to-the-corporate-terms-of-service + - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Os Termos de serviço padrão são um acordo entre o {% data variables.product.prodname_dotcom %} e você como indivíduo. Para fazer um acordo com o {% data variables.product.prodname_dotcom %} em nome de uma entidade, como uma empresa, um grupo ou uma organização sem fins lucrativos, os proprietários da organização podem atualizar para os Termos de serviço corporativos. + +1. Entre em contato com o {% data variables.contact.contact_support %} para solicitar uma atualização para os Termos de serviço corporativos. Será habilitado um banner no painel da organização que permitirá que você aceite os Termos de serviço corporativos. +{% data reusables.dashboard.access-org-dashboard %} +3. Na parte superior da página, à direita do banner dos Termos de serviço, clique em **Sign now** (Assinar agora). ![Botão Sign now (Assinar agora)](/assets/images/help/organizations/sign-now-button.png) +4. Leia as informações sobre os Termos de serviço corporativos e selecione **Yes, I want to sign these terms on behalf of my business** (Sim, quero assinar estes termos em nome da minha empresa). ![Caixa de seleção para assinar em nome da empresa](/assets/images/help/organizations/sign-on-behalf-business.png) +5. Digite o nome da empresa, do grupo ou da organização sem fins lucrativos a quem pertence a conta da organização. É essa entidade que fará o acordo com o {% data variables.product.prodname_dotcom %}. ![Campo Business name (Nome da empresa)](/assets/images/help/organizations/business-name-field.png) +6. Para concordar com os Termos de serviço corporativos em nome da entidade, clique em **Accept terms** (Aceitar termos). ![Botão Accept terms (Aceitar termos)](/assets/images/help/organizations/accept-terms-button.png) + +### Leia mais +- "[Termos de serviço corporativos do GitHub](/articles/github-corporate-terms-of-service/)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md b/translations/pt-BR/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md new file mode 100644 index 0000000000..88f407d8ea --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md @@ -0,0 +1,42 @@ +--- +title: Verificar o domínio da organização +intro: 'Você pode verificar os domínios controlados pela sua organização para confirmar a identidade dela no {% data variables.product.product_name %}.' +redirect_from: + - /articles/verifying-your-organization-s-domain + - /articles/verifying-your-organizations-domain + - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Sobre a verificação do domínio + +Para verificar domínios no {% data variables.product.product_name %}, você deve ter permissões de proprietário na organização. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/articles/permission-levels-for-an-organization)". Você também precisará de acesso para modificar registros de domínio com o serviço de hospedagem de domínio. + +Após a verificação da propriedade dos domínios da sua organização, é exibido um selo "Verified" (Verificado) no perfil da organização. Se ela estiver no {% data variables.product.prodname_ghe_cloud %} e tiver concordado com os Termos de serviço corporativos, os proprietários da organização poderão verificar a identidade dos integrantes dela exibindo o endereço de e-mail de cada um deles no domínio verificado. Para obter mais informações, consulte "[Sobre a página de perfil da sua organização](/articles/about-your-organization-s-profile/)" e "[Atualizar para os Termos de serviço corporativos](/articles/upgrading-to-the-corporate-terms-of-service)". + +Se sua organização pertence a uma conta corporativa, será exibido um selo "Verificado" no perfil da sua organização para quaisquer domínios verificados para a conta corporativa, além de quaisquer domínios verificados para a organização. Para obter mais informações, consulte "[Verificar o domínio da sua conta corporativa](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)". + +{% data reusables.organizations.verified-domains-details %} + +No {% data variables.product.prodname_ghe_cloud %}, após a verificação da propriedade do domínio da sua organização, você pode restringir as notificações de email para a organização a esse domínio. Para obter mais informações, consulte "[Restringir notificações de e-mail a um domínio aprovado](/articles/restricting-email-notifications-to-an-approved-domain)." + +### Verificar o domínio da organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +5. Clique em **Add a domain** (Adicionar um domínio). ![Botão Add a domain (Adicionar um domínio)](/assets/images/help/organizations/add-a-domain-button.png) +{% data reusables.organizations.add-domain %} +{% data reusables.organizations.add-dns-txt-record %} +1. Aguarde a alteração da configuração de DNS, que pode demorar até 72 horas. Você pode confirmar que a configuração do DNS foi alterada executando o comando `dig` na linha de comando, substituindo `ORGANIZATION` pelo nome da sua organização e `example.com` pelo o domínio que você gostaria de verificar. Você deverá ver o novo registro TXT listado na saída do comando. + ```shell + $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT + ``` +8. Depois de confirmar que o registro TXT foi adicionado ao DNS, navegue até a guia Verified domain (Domínios verificados) nas configurações da organização. Siga as etapas 1 a 4 acima para localizar a guia Verified domains (Domínios verificados). ![Página de configurações de domínios verificados com domínio pendente](/assets/images/help/organizations/pending-domain-verification.png) +{% data reusables.organizations.continue-verifying-domain %} +11. Depois que o selo "Verified" (Verificado) estiver visível na página de perfil da sua organização, a entrada TXT poderá ser excluída do registro DNS no serviço de hospedagem de domínio. ![Selo Verified (Verificado)](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000..ca1bf4b19c --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,57 @@ +--- +title: Adicionar um gerente de cobrança à sua organização +intro: 'Um *gerente de cobrança* é um usuário que gerencia as configurações de cobrança para sua organização, como atualizar informações de pagamento. Essa será uma excelente opção se integrantes regulares da sua organização normalmente não tiverem acesso aos recursos de cobrança.' +redirect_from: + - /articles/adding-a-billing-manager-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - cobrança +--- + +Os integrantes da equipe Proprietários da organização podem conceder permissões de *gerente de cobrança* para as pessoas. Depois que uma pessoa aceita o convite deles para se tornar um gerente de cobrança da sua organização, ela poderá convidar mais pessoas para serem gerentes de cobrança. + +{% note %} + +**Observação:** Os gerentes de cobrança não usam licenças pagas na assinatura da sua organização. + +{% endnote %} + +### Permissões para gerentes de cobrança + +Os gerentes de cobrança podem: + +- Atualizar ou fazer downgrade da conta +- Adicionar, atualizar ou remover formas de pagamento +- Exibir o histórico de pagamentos +- Baixar recibos +- Exibir, convidar e remover gerentes de cobrança + +Além disso, todos os gerentes de cobrança receberão recibos de cobrança por e-mail na data de cobrança da organização. + +Os gerentes de cobrança **não** podem: + +- Criar ou acessar repositórios nas suas organizações +- Ver integrantes privados da sua organização +- Ser vistos na lista de integrantes da organização +- Comprar, editar ou cancelar assinaturas para aplicativos do {% data variables.product.prodname_marketplace %} + +{% tip %} + +**Dica:** se sua organização [exigir que integrantes, gerentes de cobrança e colaboradores externos usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), o usuário deverá habilitar a autenticação de dois fatores antes de aceitar o convite para se tornar um gerente de cobrança da organização. + +{% endtip %} + +### Convidar um gerente de cobrança + +A pessoa convidada receberá um e-mail de convite solicitando que ela se torne um gerente de cobrança da sua organização. Assim que a pessoa convidada clicar no link de aceitação no e-mail de convite, ela será adicionada automaticamente à organização como um gerente de cobrança. Se ela ainda não tiver uma conta do GitHub, ela será direcionada para se inscrever em uma, e será adicionada automaticamente à organização como um gerente de cobrança depois que ela criar uma conta. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Ao lado de Billing managers (Gerentes de cobrança), clique em **Add a billing manager** (Adicionar um gerente de cobrança). ![Convidar gerente de cobrança](/assets/images/help/billing/settings_billing_managers_list.png) +6. Digite o nome de usuário ou endereço de e-mail da pessoa que deseja adicionar e clique em **Send invitation** (Enviar convite). ![Página para convidar gerente de cobrança](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000..ba653e6296 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,29 @@ +--- +title: Dar permissões de "mantenedor de equipe" a um integrante de uma organização +intro: 'Um proprietário da organização pode promover qualquer integrante a *mantenedor de equipe*, oferecendo a ele um subconjunto de privilégios existentes para proprietários de organizações.' +redirect_from: + - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ + - /articles/giving-team-maintainer-permissions-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team_maintainers_can %} + +### Promover um integrante de organização a mantenedor de equipe + +Antes de promover um integrante de organização a mantenedor de equipe, a pessoa já deve ser um integrante da equipe. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +4. Selecione a pessoa que você gostaria de promover a mantenedor de equipe. ![Caixa de seleção ao lado de integrante de organização](/assets/images/help/teams/team-member-check-box.png) +5. Acesse o menu suspenso que está acima da lista de integrantes da equipe e clique em **Change role...** (Alterar função). ![Menu suspenso com opção change role (alterar função)](/assets/images/help/teams/bulk-edit-drop-down.png) +6. Selecione uma nova função e clique em **Change role** (Alterar função). ![Botão de rádio para funções de Mantendor ou Integrante](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md new file mode 100644 index 0000000000..23c746454c --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -0,0 +1,21 @@ +--- +title: Gerenciar o acesso de pessoas à organização com funções +intro: 'A função de uma pessoa na organização define o nível de acesso dela à sua organização, às configurações da organização e aos seus dados. Você pode tornar as pessoas proprietárias, integrantes ou gerentes de cobrança da organização, ou dar a elas permissões de mantenedores de equipes.' +redirect_from: + - /articles/managing-people-s-access-to-your-organization-with-roles + - /articles/managing-peoples-access-to-your-organization-with-roles + - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000..baa4e952fa --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Manter a continuidade da propriedade para sua organização +intro: As organizações podem ter mais de um proprietário para evitar intermitências de propriedade. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization +permissions: Os proprietários da organização podem promover qualquer integrante de uma organização a um proprietário da organização. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Sobre a manutenção da continuidade da propriedade da sua organização + +{% data reusables.organizations.org-ownership-recommendation %} + +Os proprietários da organização têm pleno acesso administrativo à organização. {% data reusables.organizations.new-org-permissions-more-info %} + +### Designar um proprietário da organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Selecione a(s) pessoa(s) que deseja promover a proprietário. ![Lista de integrantes com dois integrantes selecionados](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Acesse o menu suspenso que está acima da lista de integrantes e clique em **Change role** (Alterar função). ![Menu suspenso com opção de remover integrantes](/assets/images/help/teams/user-bulk-management-options.png) +6. Selecione uma nova função para a(s) pessoa(s) e clique em **Change role** (Alterar função). ![Botões de opção com funções de proprietário e integrante e botão Change role (Alterar função)](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md new file mode 100644 index 0000000000..bcb3c28ad9 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -0,0 +1,147 @@ +--- +title: Níveis de permissão da organização +intro: 'Depois de [criar uma organização](/articles/creating-a-new-organization-account), você deverá conceder permissões de proprietários a um pequeno grupo de pessoas que gerenciará a conta da organização.' +redirect_from: + - /articles/permission-levels-for-an-organization-early-access-program/ + - /articles/permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Níveis de permissão da organização + +Os integrantes da organização podem ter funções de *proprietário*{% if currentVersion == "free-pro-team@latest" %}, *gerente de cobrança*,{% endif %} ou *integrante*: + +- **Proprietários** têm acesso administrativo total à sua organização. Essa função deve ser limitada a não menos que duas pessoas na sua organização. Para obter mais informações, consulte "[Manter a continuidade da propriedade para a sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)". +{% if currentVersion == "free-pro-team@latest" %} +- **Gerentes de cobrança** podem gerenciar as configurações de cobrança. Para obter mais informações, consulte "[Adicionar um gerente de cobrança à sua organização](/articles/adding-a-billing-manager-to-your-organization)". +{% endif %} +- **Integrante** é a função padrão para todas as outras pessoas. + +{% if currentVersion == "free-pro-team@latest" %} + + +| Ação da organização | Proprietários | Integrantes | Gerentes de cobrança | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:-----------:|:--------------------:| +| Criar repositórios (consulte "[Restringir a criação de repositórios na organização](/articles/restricting-repository-creation-in-your-organization)" para detalhes) | **X** | **X** | | +| Visualizar e editar informações de cobrança | **X** | | **X** | +| Convidar pessoas para integrar a organização | **X** | | | +| Editar e cancelar convites para integrar a organização | **X** | | | +| Remover integrantes da organização | **X** | | | +| Restabelecer ex-integrantes da organização | **X** | | | +| Adicionar e remover pessoas de **todas as equipes** | **X** | | | +| Promover integrantes da organização a *mantenedor de equipe* | **X** | | | +| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Definir lembretes agendados (consulte "[Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | +| Adicionar colaboradores em **todos os repositórios** | **X** | | | +| Acessar o log de auditoria da organização | **X** | | | +| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/articles/about-your-organization-s-profile)" para detalhes) | **X** | | | +| Verificar os domínios da organização (consulte "[Verificar o domínio da sua organização](/articles/verifying-your-organization-s-domain)" para detalhes) | **X** | | | +| Restringir notificações de e-mail a domínios verificados (consulte "[Restringir notificações de e-mail para um domínio aprovado](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" para obter informações) | **X** | | | +| Excluir **todas as equipes** | **X** | | | +| Excluir a conta da organização, inclusive todos os repositórios | **X** | | | +| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | | +| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | +| Ver todos os integrantes e equipes da organização | **X** | **X** | | +| @mencionar qualquer equipe visível | **X** | **X** | | +| Poder se tornar um *mantenedor de equipe* | **X** | **X** | | +| Visualizar as informações da organização (consulte "[Visualizar informações da organização](/articles/viewing-insights-for-your-organization)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | | | +| Editar e excluir discussões de equipe em **todas as equipes** (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" para detalhes) | **X** | | | +| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | | +| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | +| Gerenciar a visualização de informações de dependência da organização (consulte "[Alterar a visibilidade das informações de dependência da organização](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para detalhes) | **X** | | | +| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | | +| Patrocinar contas e gerenciar os patrocínios da organização (Consulte "[Patrocinar contribuidoresde código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" para mais detalhes) | **X** | **X** | | +| Gerenciar atualizações de e-mail de contas patrocinadas (consulte "[Gerenciar atualizações de contas que a sua organização patrocina](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)" para obter detalhes) | **X** | | | +| Atribuir seus patrocínios a outra organização (consulte "[Atribuir de patrocínios à sua organização](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" para obter mais detalhes) | **X** | | | +| Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) | **X** | | | +| Gerenciar as configurações de segurança e análise (consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" para obter mais informações) | **X** | | | +| Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | +| [Gerenciar o acesso de SAML de um usuário à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | | +| Transferir repósitórios | **X** | | | +| Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %} | **X** | | | +| Listar aplicativos no {% data variables.product.prodname_marketplace %} | **X** | | | +| Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização | **X** | | | +| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | +| [Gerenciar a política de bifurcação](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limitar a atividade em repositórios públicos na organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | +| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | | +| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | +| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Gerenciar o nome do branch-padrão (consulte "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Habilitar sincronização de equipes (consulte "[Gerenciar sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" para obter informações) | **X** | | | + +{% else %} + + +| Ação da organização | Proprietários | Integrantes | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:------------------------------------------------------------------------------------------------:| +| Convidar pessoas para integrar a organização | **X** | | +| Editar e cancelar convites para integrar a organização | **X** | | +| Remover integrantes da organização | **X** | | | +| Restabelecer ex-integrantes da organização | **X** | | | +| Adicionar e remover pessoas de **todas as equipes** | **X** | | +| Promover integrantes da organização a *mantenedor de equipe* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Adicionar colaboradores em **todos os repositórios** | **X** | | +| Acessar o log de auditoria da organização | **X** | | +| Editar a página de perfil da organização (consulte "[Sobre o perfil da sua organização](/articles/about-your-organization-s-profile)" para detalhes) | **X** | | | +| Excluir **todas as equipes** | **X** | | +| Excluir a conta da organização, inclusive todos os repositórios | **X** | | +| Criar equipes (consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)" para detalhes) | **X** | **X** | +| Ver todos os integrantes e equipes da organização | **X** | **X** | +| @mencionar qualquer equipe visível | **X** | **X** | +| Poder se tornar um *mantenedor de equipe* | **X** | **X** | +| Transferir repósitórios | **X** | | +| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes) | **X** | | +| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | **X** | | +| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes) | **X** | | | +| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes) | **X** | **X** | **X** | +| Desabilitar discussões de equipe na organização (consulte "[Desabilitar discussões de equipe em sua organização](/articles/disabling-team-discussions-for-your-organization)" para detalhes) | **X** | | | +| Definir uma foto de perfil da equipe para **todas as equipes** (consulte "[Definir uma foto de perfil de sua equipe](/articles/setting-your-team-s-profile-picture)" para detalhes) | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| Gerencie a publicação dos sites de {% data variables.product.prodname_pages %} a partir dos repositórios na organização (consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)para obter mais informações) | **X** | +{% endif %} +| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização | **X** | | +| Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | +| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Exportar uma lista das pessoas com acesso a um repositório da organização](/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" %} +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | +{% endif %} +{% if currentVersion == "github-ae@latest" %}| Gerenciar listas de permissão de IP (consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} + +{% endif %} + +### Gerentes de {% data variables.product.prodname_github_app %} + +Por padrão, somente proprietários da organização podem gerenciar as configurações dos {% data variables.product.prodname_github_app %}s pertencentes a uma organização. Para permitir que outros usuários gerenciem os {% data variables.product.prodname_github_app %}s pertencentes a uma organização, um proprietário pode conceder a eles permissões de gerente de {% data variables.product.prodname_github_app %}. + +Ao designar um usuário como gerente de {% data variables.product.prodname_github_app %} na organização, você pode conceder a ele acesso para gerenciar as configurações de alguns {% data variables.product.prodname_github_app %}s ou para gerenciar todos os {% data variables.product.prodname_github_app %}s da organização. Para obter mais informações, consulte: + +- "[Adicionar gerentes de aplicativos GitHub na organização](/articles/adding-github-app-managers-in-your-organization)" +- "[Remover gerentes de aplicativos GitHub de sua organização](/articles/removing-github-app-managers-from-your-organization)" + +### Colaboradores externos + +Para manter os dados da sua organização seguros, permitindo o acesso aos repositórios, é possível adicionar *colaboradores externos*. {% data reusables.organizations.outside_collaborators_description %} + +### Leia mais + +- "[Níveis de permissão do repositório para uma organização](/articles/repository-permission-levels-for-an-organization)" +- "[Sobre equipes](/articles/about-teams)" +- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000..6a54b30aa4 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Remover um gerente de cobrança da organização +intro: 'Se um usuário com a função *gerente de cobrança* não precisar mais visualizar ou alterar as informações de cobrança da organização, remova seu acesso à organização.' +redirect_from: + - /articles/removing-a-billing-manager-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - cobrança +--- + +{% warning %} + +**Observação:** {% 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. Na lista Billing managers (Gerentes de cobrança), clique em {% octicon "x" aria-label="X symbol" %} ao lado do nome do usuário que deseja remover. ![Remover gerente de cobrança](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000..9645dfdbde --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,62 @@ +--- +title: Sobre o gerenciamento de identidade e acesso com o SAML de logon único +intro: 'Se você gerencia centralmente as identidades e aplicativos dos seus usuários com um provedor de identidade (IdP), você pode configurar o Logon Único (SSO) da Linguagem de Markup de Declaração de Segurança (SAML) para proteger os recursos da sua organização em {% 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 + - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Sobre o SAML SSO + +{% data reusables.saml.dotcom-saml-explanation %} + +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 da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. 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 %} + +Antes de ativar o SAML SSO para sua organização, é necessário conectar seu IdP à sua organização. Para obter mais informações, consulte "[Conectar o provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)". + +Para uma organização, o SAML SSO pode ser desabilitado, habilitado, mas não aplicado, ou habilitado e aplicado. Depois de ativar o SSO SAML para a sua organização e os integrantes da sua organização efetuarem a autenticação com sucesso com o seu IdP, você poderá aplicar a configuração SAML SSO. Para obter mais informações sobre a aplicação de SAML SSO para a sua organização do {% data variables.product.prodname_dotcom %}, consulte "[Aplicando logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". + +Os integrantes devem efetuar a autenticação periodicamente com seu IdP para efetuar a autenticação e obter acesso aos recursos da sua organização. A duração desse período de login é especificado pelo seu IdP e geralmente é de 24 horas. Esse requisito de login periódico limita a duração do acesso e exige que os usuários identifiquem-se novamente para continuar. + +Para acessar os recursos protegidos da organização que usam a API e o Git na linha de comando, os integrantes devem autorizar e efetuar a autenticação com um token de acesso pessoal ou chave SSH. Para mais informações consulte "[Autorizar um token de acesso pessoal para usar com o logon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" e "[Autorizar uma chave SSH para uso com o logon único SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." + +A primeira vez que um membro usar o SAML SSO para acessar sua organização, o {% data variables.product.prodname_dotcom %} criará automaticamente um registro que irá vincular a sua organização, a conta do {% data variables.product.prodname_dotcom %} do integrante e a conta do integrante no seu IdP. Você pode visualizar e revogar a identidade de SAML vinculada, as sessões ativas e credenciais autorizadas para integrantes da sua empresa ou conta corporativa. Para obter mais informações consulte "[Visualizar e gerenciar o acesso de SAML de um integrante da sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" e "[Visualizar e gerenciar o acesso de SAML de um usuário à conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". + +Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um novo repositório, a visibilidade-padrão desse repositório será privada. Caso contrário, a visibilidade-padrão será pública. Para obter mais informações sobre a visibilidade de repositório, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". + +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 %} + +Alguns IdPs suportam acesso de provisionamento a uma organização do {% data variables.product.prodname_dotcom %} via SCIM. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + +### Adicionar integrantes a uma organização usando SAML SSO + +Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adicionar novos integrantes à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, consulte "[Convidar usuários para juntar-se à sua organização](/articles/inviting-users-to-join-your-organization)" e "[Integrantes](/rest/reference/orgs#add-or-update-organization-membership)". + +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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### Leia mais + +- "[Sobre a autenticação de dois fatores e o SAML de logon único](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md new file mode 100644 index 0000000000..d62e5033e3 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -0,0 +1,31 @@ +--- +title: Sobre o SCIM +intro: 'Com o Sistema para gerenciamento de identidades entre domínios (SCIM, System for Cross-domain Identity Management), os administradores podem automatizar a troca de informações de identidade do usuário entre sistemas.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-scim + - /github/setting-up-and-managing-organizations-and-teams/about-scim +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Se você usa [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) em sua organização, é possível implementar o SCIM pra adicionar, gerenciar e remover o acesso dos integrantes da organização ao {% data variables.product.product_name %}. Por exemplo, um administrador pode desprovisionar um integrante da organização usando SCIM e remover automaticamente o integrante da organização. + +Se o SAML SSO for usado sem implementação do SCIM, você não terá desprovisionamento automático. Quando as sessões dos integrantes da organização expiram depois que o acesso deles é removido do IdP, eles não podem ser removidos automaticamente da organização. Os tokens autorizados concedem acesso à organização mesmo depois que as respectivas sessões expiram. Para remover o acesso, os administradores da organização podem remover o token autorizado manualmente da organização ou automatizar a remoção com o SCIM. + +Estes provedores de identidade são compatíveis com a API de SCIM de {% data variables.product.product_name %} para organizações. Para obter mais informações, consulte [SCIM](/rest/reference/scim) na documentação de API do {% data variables.product.product_name %}. +- Azure AD +- Okta +- OneLogin + +{% data reusables.scim.enterprise-account-scim %} Para obter mais informações, consulte "[Sobre o provisionamento do usuário para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)". + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Conectar o provedor de identidade à sua organização](/articles/connecting-your-identity-provider-to-your-organization)" +- "[Habilitar e testar SAML de logon único para sua organização](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" +- "[Visualizar e gerenciar acesso de SAML de um integrante à sua organização](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000..d947953153 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,31 @@ +--- +title: Acessar sua organização se o provedor de identidade não estiver disponível +intro: 'Os administradores da organização podem entrar no {% data variables.product.product_name %} mesmo se o provedor de identidade deles estiver indisponível, ignorando o logon único e usando os respectivos códigos de recuperação.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Os administradores da organização podem usar [um de seus códigos de recuperação baixados ou salvos](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) para ignorar o logon único. Você pode ter salvado eles em um gerenciador de senhas, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/) ou [Keeper](https://keepersecurity.com/). + +{% note %} + +**Observação:** você pode usar os códigos de recuperação apenas uma vez e deve usá-los em ordem consecutiva. Os códigos de recuperação concedem acesso por 24 horas. + +{% endnote %} + +1. Na parte inferior da caixa de diálogo de logon único, clique em **Use a recovery code** (Usar um código de recuperação) para ignorar o logon único. ![Link para inserir código de recuperação](/assets/images/help/saml/saml_use_recovery_code.png) +2. No campo "Recovery Code" (Código de Recuperação), digite seu código de recuperação. ![Campo para inserir código de recuperação](/assets/images/help/saml/saml_recovery_code_entry.png) +3. Clique em **Verificar**. ![Botão para verificar código de recuperação](/assets/images/help/saml/saml_verify_recovery_codes.png) + +Depois de ter usado um código de recuperação, certifique-se de anotar que ele não é mais válido. Você não poderá reutilizar o código de recuperação. + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000..5b866a2d73 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,81 @@ +--- +title: Configurar SCIM e o logon único SAML usando o Okta +intro: 'Você pode usar o logon único (SSO) da Linguagem de Markup da Declaração de Segurança (SAML) e o Sistema de Gerenciamento de Identidades de Domínio Cruzado (SCIM) com o Okta para gerenciar automaticamente o acesso à sua organização em {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta +product: '{% data reusables.gated-features.saml-sso %}' +permissions: Os proprietários da organização podem configurar o SAML SSO e os SCIM usando o Okta para uma organização. +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Sobre SAML e SCIM com Okta + +Você pode controlar o acesso à organização do {% data variables.product.prodname_dotcom %} e outros aplicativos da web a partir de uma interface central, configurando a organização para usar SAML SSO e SCIM com Okta, um provedor de identidade (IdP). + +O SAML SSO controla e protege o acesso a recursos da organização, como repositórios, problemas e pull requests. O SCIM adiciona, gerencia e remove automaticamente o acesso dos integrantes à sua organização do {% data variables.product.prodname_dotcom %} quando você fizer alterações no Okta. Para obter mais informações, consulte "[Sobre a identidade e gerenciamento de acesso com logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" e "[Sobre SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + +Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponíveis para qualquer usuário ao qual você atribuir seu aplicativo do {% data variables.product.prodname_ghe_cloud %} no Okta. + +| Funcionalidade | Descrição | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Fazer push de novos usuários | Ao criar um novo usuário no Okta, ele receberá um e-mail para juntar-se à sua organização do {% data variables.product.prodname_dotcom %}. | +| Fazer push de desativações de usuário | Ao desativar um usuário no Okta, este removerá o usuário da sua organização de {% data variables.product.prodname_dotcom %}. | +| Fazer push das atualização de perfil | Ao atualizar o perfil de um usuário no Okta, este atualizará os metadados para a associação do usuário na sua organização de {% data variables.product.prodname_dotcom %}. | +| Reativar usuários | Ao reativar um usuário no Okta, este enviará um convite por e-mail para o usuário juntar-se novamente à sua organização de {% data variables.product.prodname_dotcom %}. | + +### Pré-requisitos + +{% data reusables.saml.use-classic-ui %} + +### Adicionar o aplicativo {% data variables.product.prodname_ghe_cloud %} no Okta + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +4. À direita do "Github Enterprise Cloud - Organização", clique em **Adicionar**. ![Clicar em "Adicionar" para o aplicativo {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/saml/okta-add-ghec-application.png) + +5. No campo **Organização do GitHub**, digite o nome da sua organização de {% data variables.product.prodname_dotcom %}. Por exemplo, se a URL da sua organização for https://github.com/octo-org, o nome da organização será `octo-org`. ![Digite o nome da organização do GitHub](/assets/images/help/saml/okta-github-organization-name.png) + +6. Clique em **Cpncluído**. + +### Habilitar e e testar o SAML SSO + +{% 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. Habilitar e testar o SAML SSO no {% data variables.product.prodname_dotcom %} usando a URL de logon, a URL do emissor e os certificados públicos da aba "Como configurar o SAML 2.0". Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)". + +### Configurar provisionamento de acesso com SCIM em 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. Clique em **Efetuar a autenticação com Github Enterprise Cloud - Organização**. ![Botão "Efetuar a autenticação com Github Enterprise Cloud - Organização" para o aplicativo Okta](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) + +7. À direita do nome da sua organização, clique em **Conceder**. ![Botão "Conceder" para autorizar a integração do SCIM do Okta para acessar a organização](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) + + {% note %} + + **Observação**: Se você não vir a sua organização na lista, acesse `https://github.com/orgs/ORGANIZATION-NAME/sso` no seu navegador e efetue a autenticação com sua organização por meio do SAML SSO usando sua conta de administrador no IdP. Por exemplo, se o nome da sua organização for `octo-org`, a URL seria `https://github.com/orgs/octo-org/sso`. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". + + {% endnote %} +1. Clique em **Autorizar o OktaOAN**. ![Botão "Autorizar o OktaOAN" para autorizar a integração do SCIM do Okta para acessar a organização](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} + +### Leia mais + +- "[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 equipe para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" +- [Compreender o SAML](https://developer.okta.com/docs/concepts/saml/) na documentação do Okta +- [Entender o SCIM](https://developer.okta.com/docs/concepts/scim/) na documentação do Okta diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000..f49557ede6 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Conectar o provedor de identidade à organização +intro: 'Para usar o logon único SAML e o SCIM, é preciso conectar o provedor de identidade à organização do {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/connecting-your-identity-provider-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Antes de [habilitar o SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) na organização do {% data variables.product.product_name %}, você precisará conectar o provedor de identidade (IdP) à sua organização. + +Você pode encontrar os detalhes de implementação do SAML e SCIM para seu IdP na respectiva documentação: +- [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) do Active Directory Federation Services (AD FS) +- [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) e [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) do Azure Active Directory (Azure AD) +- [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) e [SCIM](http://developer.okta.com/standards/SCIM/) do Okta +- [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) e [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e) do OneLogin +- [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) do PingOne +- [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home) do Shibboleth + +{% note %} + +**Observação:** os provedores de identidade aceitos pelo {% data variables.product.product_name %} para SCIM são Azure AD, Okta e OneLogin. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/articles/about-scim)." + +{% endnote %} + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Aplicar SAML de logon único para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000..523be4884d --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,36 @@ +--- +title: Baixar os códigos de recuperação de logon único de SAML da organização +intro: 'Os administradores da organização devem baixar os códigos de recuperação de logon único de SAML dela para garantir que possam acessar o {% data variables.product.product_name %} mesmo se o provedor de identidade da organização não estiver disponível.' +redirect_from: + - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes + - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes + - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Os códigos de recuperação não devem ser compartilhados ou distribuídos. É recomendável salvá-los com um gerenciador de senha como [LastPass](https://lastpass.com/), [1Password](https://1password.com/) ou [Keeper](https://keepersecurity.com/). + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. Em "SAML single sign-on" (Logon único de SAML), na observação sobre código de recuperação, clique em **Save your recovery codes** (Salvar os códigos de recuperação). ![Link para exibir e salvar os códigos de recuperação](/assets/images/help/saml/saml_recovery_codes.png) +6. Salve seus códigos de recuperação clicando em **Download** (Baixar), **Print** (Imprimir) ou **Copy** (Copiar). ![Botões para baixar, imprimir ou copiar os códigos de recuperação](/assets/images/help/saml/saml_recovery_code_options.png) + + {% note %} + + **Observação:** os códigos de recuperação ajudam você a retornar para o {% data variables.product.product_name %} caso seu IdP fique indisponível. Se você gerar novos códigos de recuperação, os exibidos na página "Códigos de recuperação de logon único" serão atualizados automaticamente. + + {% endnote %} + +7. Cada código de recuperação só pode ser usado uma vez para recuperar o acesso ao {% data variables.product.product_name %}. O acesso ao {% data variables.product.product_name %} só ficará disponível 24 horas antes de você fazer login usando o login único. + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Acessar a organização se o provedor de identidade estiver indisponível](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..e425285e4c --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,51 @@ +--- +title: Habilitar e testar logon único de SAML para sua organização +intro: Os administradores e proprietários da organização podem habilitar o logon único (SSO, Single Sign-On) de SAML para adicionar uma camada extra de segurança à organização. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Você pode habilitar o SAML SSO na sua organização sem exigir que todos os integrantes o utilizem. A habilitação (em vez da aplicação) do SAML SSO facilitará a adoção dele pela organização. Depois que a maioria dos integrantes da sua organização já estiver usando o SAML SSO, você poderá aplicá-lo a toda a organização. + +Se você habilitar em vez de aplicar o SAML SSO, os integrantes da organização que preferem não usá-lo poderão continuar sendo integrantes da organização. Para obter mais informações sobre a aplicação do SAML SSO, consulte "[Aplicar logon único de SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". + +{% data reusables.saml.outside-collaborators-exemption %} + +Antes de aplicar o SAML SSO à sua organização, verifique se você configurou o provedor de identidade (IdP, Identity Provider). Para obter mais informações, consulte "[Preparar para aplicar logon único de SAML na organização](/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. 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/saml/saml_enable.png) + + {% note %} + + **Observação:** depois de habilitar o SAML SSO, baixe os seus códigos de recuperação de logon único para poder acessar sua organização mesmo que o IdP esteja indisponível. Para obter mais informações, consulte "[Baixar códigos de recuperação de logon único de SAML da organização](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)". + + {% endnote %} + +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.png) +7. Como alternativa, no campo "Issuer" (Emissor), digite o nome do emissor do 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. Clique em {% octicon "pencil" aria-label="The edit icon" %} e, 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 para verificar a integridade das solicitações. ![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 organização, 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) + + {% tip %} + + **Dica:** {% data reusables.saml.testing-saml-sso %} + + {% endtip %} +11. Para aplicar o SAML SSO e remover todos os integrantes da organização que não foram autenticados via IdP, selecione **Require SAML SSO authentication for all members of the _organization name_ organization** (Requer autenticação do SAML SSO para todos os integrantes da organização *nome da organização*). Para obter mais informações sobre a aplicação do SAML SSO, consulte "[Aplicar logon único de SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". ![Caixa de seleção para exigir SAML SSO para sua organização ](/assets/images/help/saml/saml_require_saml_sso.png) +12. Clique em **Salvar**. ![Botão para salvar as configurações do SAML SSO](/assets/images/help/saml/saml_save.png) + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..6bd2ed20ac --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Aplicar logon único de SAML para sua organização +intro: Administradores e proprietários da organização podem aplicar logon único (SSO, Single Sign-On) de SAML para que todos os integrantes da organização precisem se autenticar por meio de um provedor de identidade. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enforcing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Se você aplicar SAML SSO na sua organização, todos os integrantes, inclusive administradores que não tenham sido autenticados pelo seu provedor de identidade (IdP, Identity Provider) de SAML, serão removidos da organização e receberão um e-mail notificando-os sobre a remoção. Bots e contas de serviço que não tenham identidades externas configuradas no IdP da organização também serão removidos. Para obter mais informações sobre bots e contas de serviço, consulte "[Gerenciar bots e contas de serviço com logon único de SAML](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)". Você poderá restaurar integrantes da organização depois que eles tiverem concluído o logon único com êxito. + +Se a organização pertence a uma conta corporativa, habilitar o SAML para a conta corporativa substituirá a configuração do SAML 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)". + +{% tip %} + +**Dica:** {% data reusables.saml.testing-saml-sso %} + +{% endtip %} + +1. Habilite e teste o SAML SSO para sua organização. Para obter mais informações sobre esse processo, consulte "[Habilitar e testar logon único de SAML para sua organização](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)". +2. Depois que você selecionar **Require SAML SSO authentication for all members of the SAML SSO Org organization** (Exigir autenticação SAML SSO para todos os integrantes da organização SAML SSO Org), serão mostrados os integrantes da organização que não foram autenticados via IdP. Se você aplicar o SAML SSO, esses integrantes serão removidos da organização. +3. Clique em **Enforce SAML SSO** (Aplicar SAML SSO) e remova os integrantes da organização listados. + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md new file mode 100644 index 0000000000..e4ec1ad6cf --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -0,0 +1,24 @@ +--- +title: Gerenciar o logon único SAML para sua organização +intro: Administradores da organização podem gerenciar as identidades e acessos dos integrantes à organização com logon único SAML (SSO). +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000..9950238f82 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,79 @@ +--- +title: Gerenciar a sincronização de equipe para a sua organização +intro: 'Você pode habilitar e desabilitar a sincronização de equipes entre o seu provedor de identidade (IdP) e a sua organização em {% 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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization +permissions: Os proprietários da organização podem gerenciar a sincronização de equipes para uma organização. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Sobre a sincronização de equipes + +É possível habilitar a sincronização de equipes entre seu IdP e o {% data variables.product.product_name %} para permitir que os proprietários da organização e mantenedores da equipe conectem equipes na sua organização com 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 %} + +Também é possível habilitar a sincronização de equipes para organizações que pertencem a 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)". + +### Habilitar a sincronização de equipes + +As etapas para habilitar a sincronização de equipe dependem do IdP que você deseja usar. Existem pré-requisitos para habilitar a sincronização de equipes que se aplicam a cada IdP. Cada IdP individual tem pré-requisitos adicionais. + +#### Pré-requisitos + +{% data reusables.identity-and-permissions.team-sync-required-permissions %} + +Você deve habilitar o logon único SAML para sua organização e seu IdP compatível. 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)". + +Você deve efetuar a autenticação para a sua organização usando 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)". + +#### Habilitar a sincronização de equipe para o 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. Reveja as informações do encarregado do provedor de identidade que você deseja conectar à organização e clique em **Approve** (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) + +#### Habilitar a sincronização de equipe para o 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. No nome da sua organização, digite um token SSWS válido e a URL para sua instância do Okta. ![Formulário da organização do Okta para habilitar a sincronização de equipes](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) +6. Revise as informações do locatário do provedor de identidade que você deseja conectar à sua organização e clique em **Criar**. ![Botão de criar em habilitar a sincronização de equipes](/assets/images/help/teams/confirm-team-synchronization-okta.png) + +### Desabilitar a sincronização de equipes + +{% 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. Em "Team synchronization" (Sincronização de equipes), clique em **Disable team synchronization** (Desabilitar sincronização de equipes). ![Desabilitar a sincronização de equipes](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000..fddc7d9376 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Preparar para exigir o logon único SAML na organização +intro: 'Antes de exigir o logon único SAML na organização, você deve verificar a associação da organização e configurar as definições de conexão para seu provedor de identidade.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Ao [exigir logon único SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) na sua organização, os integrantes que não tenham sido autenticados por meio de seu provedor de identidade (IdP) serão removidos da organização e receberão um e-mail notificando-os sobre a remoção. + +Antes de exigir o SAML SSO na organização, você deve: + +- [Adicionar](/articles/inviting-users-to-join-your-organization) ou [remover](/articles/removing-a-member-from-your-organization) integrantes da organização, se necessário. +- Se ainda não o fez, conecte seu IdP à organização. Para obter mais informações, consulte "[Conectar o provedor de identidade à sua organização](/articles/connecting-your-identity-provider-to-your-organization)". +- Certifique-se de que os integrantes da organização registraram e vincularam suas contas ao IdP. + +{% data reusables.saml.outside-collaborators-exemption %} + +### Leia mais + +- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..f2902de001 --- /dev/null +++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,32 @@ +--- +title: Migrar uma equipe de administradores para permissões de organização aprimoradas +intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões aprimoradas. Integrantes de equipes de administradores legadas mantêm automaticamente a capacidade de criar repositórios até que as equipes sejam migradas para o modelo de permissões de organização aprimoradas.' +redirect_from: + - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ + - /articles/converting-an-admin-team-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +Você pode impedir os integrantes das equipes de administradores legadas de criar repositórios criando uma equipe para esses integrantes, garantindo que a equipe tenha acesso necessário aos repositórios da organização e, em seguida, excluindo a equipe de administradores legada. + +Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/articles/repository-permission-levels-for-an-organization/)". + +{% warning %} + +**Avisos:** +- Se houver integrantes da equipe de administradores legada que não sejam integrantes de outras equipes, excluir a equipe removerá esses integrantes da organização. Antes de excluir a equipe, certifique-se de que os integrantes já sejam integrantes diretos da organização ou que tenham acesso de colaborador aos repositórios necessários. +- Para evitar a perda de bifurcações privadas feitas pelos integrantes da equipe de administradores legada, você deve seguir as etapas de 1 a 3 abaixo antes de excluir a equipe de administradores legada. +- Como "administrador" é um termo para integrantes da organização com [acesso específico a determinados repositórios](/articles/repository-permission-levels-for-an-organization) na organização, é recomendável evitar esse termo em nomes de equipe sobre os quais você decide. + +{% endwarning %} + +1. [Crie uma equipe](/articles/creating-a-team). +2. [Adicione cada um dos integrantes](/articles/adding-organization-members-to-a-team) da sua equipe de administradores legada à nova equipe. +3. [Dê à nova equipe acesso equivalente](/articles/managing-team-access-to-an-organization-repository) a cada um dos repositórios que a equipe legada podia acessar. +4. [Exclua a equipe de administradores legada](/articles/deleting-a-team). diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..6169f9bc01 --- /dev/null +++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,52 @@ +--- +title: Migrar uma equipe de proprietários para permissões de organização aprimoradas +intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões aprimoradas. O "proprietário" é agora uma função administrativa fornecida a integrantes individuais da sua organização. Os integrantes da equipe de proprietários legada recebem automaticamente privilégios de proprietário.' +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +Você tem algumas opções para converter sua equipe de proprietários legada: + +- Dê à organização um novo nome que denote que os integrantes têm um status especial na organização. +- Exclua a equipe após garantir que todos os integrantes foram adicionados às equipes que concedem acesso necessário aos repositórios da organização. + +### Dar à equipe de proprietários um novo nome + +{% tip %} + + **Observação:** como "administrador" é um termo para integrantes da organização com [acesso específico a determinados repositórios](/articles/repository-permission-levels-for-an-organization) na organização, é recomendável evitar esse termo em nomes de equipe sobre os quais você decide. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. No campo de nome da equipe, escolha um novo nome para a equipe de proprietários. Por exemplo: + - Se apenas alguns integrantes da organização forem integrantes da equipe de proprietários, você poderá dar à equipe o nome de "Principal". + - Se todos os integrantes da organização forem integrantes da equipe de proprietários, de modo que eles podem [@mencionar equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), você pode dar à equipe o nome de "Funcionários". ![O campo de nome da equipe, com a equipe de proprietários renomeada para Principal](/assets/images/help/teams/owners-team-new-name.png) +6. Abaixo da descrição da equipe, clique em **Save and continue** (Salvar e continuar). ![O botão Save and continue (Salvar e continuar)](/assets/images/help/teams/owners-team-save-and-continue.png) +7. Como opção, [torne a equipe *pública*](/articles/changing-team-visibility). + +### Excluir a equipe de proprietários legada + +{% warning %} + +**Aviso:** se houver integrantes da equipe de proprietários que não sejam integrantes de outras equipes, excluir a equipe removerá esses integrantes da organização. Antes de excluir a equipe, certifique-se de que os integrantes já sejam integrantes diretos da organização ou que tenham acesso de colaborador aos repositórios necessários. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. Na parte inferior da página, revise o aviso e clique em **Delete the Owners team** (Excluir a equipe de proprietários). ![Link para excluir a equipe de proprietários](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md new file mode 100644 index 0000000000..7e83cef4e1 --- /dev/null +++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md @@ -0,0 +1,20 @@ +--- +title: Migrar para permissões de organização aprimoradas +intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões de organização aprimoradas.' +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000..b0c0c50fd9 --- /dev/null +++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,44 @@ +--- +title: Migrar uma equipe de administradores para permissões de organização aprimoradas +intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões aprimoradas. Integrantes de equipes de administradores legadas mantêm automaticamente a capacidade de criar repositórios até que as equipes sejam migradas para o modelo de permissões de organização aprimoradas.' +redirect_from: + - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ + - /articles/migrating-admin-teams-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +Por padrão, todos os integrantes da organização podem criar repositórios. Se você restringir [as permissões de criação de repositórios](/articles/restricting-repository-creation-in-your-organization) para proprietários de organizações e sua organização foi criada sob a estrutura de permissões de organização legadas, os integrantes das equipes de administradores legadas ainda conseguirão criar repositórios. + +Equipes de administradores legadas são equipes que foram criadas com o nível de permissão de administrador na estrutura de permissões de organização legadas. Integrantes dessas equipes conseguiam criar repositórios para a organização, e essa capacidade foi preservada na estrutura de permissões de organização aprimoradas. + +Você pode remover essa capacidade migrando suas equipes de administradores legadas para as permissões de organização aprimoradas. + +Para obter mais informações, consulte "[Níveis de permissão do repositório para organizações](/articles/repository-permission-levels-for-an-organization)". + +{% warning %} + +**Aviso:** se sua organização desabilitou [as permissões de criação de repositórios](/articles/restricting-repository-creation-in-your-organization) para todos os integrantes, alguns integrantes de equipes de administradores legadas podem perder as permissões de criação de repositórios. Se a organização habilitou a criação de repositórios pelos integrantes, migrar as equipes de administradores legadas para permissões de organização aprimoradas não afetará a capacidade de criação de repositórios pelos integrantes de equipes. + +{% endwarning %} + +### Migrar todas as equipes de administradores legadas da organização + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +1. Revise as equipes de administradores legadas da organização e clique em **Migrate all teams** (Migrar todas as equipes). ![Botão Migrate all teams (Migrar todas as equipes)](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) +1. Leia as informações sobre possíveis alterações de permissões para integrantes dessas equipes e clique em **Migrate all teams** (Migrar todas as equipes). ![Botão Confirm migration (Confirmar migração)](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) + +### Migrar uma única equipe de administradores + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +1. Na caixa de descrição de equipe, clique em **Migrate team** (Migrar equipe). ![Botão Migrate team (Migrar equipe)](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md new file mode 100644 index 0000000000..ba67c67e9b --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md @@ -0,0 +1,79 @@ +--- +title: Sobre equipes +intro: As equipes são grupos de integrantes da organização que refletem sua empresa ou a estrutura do grupo com permissões de acesso em cascata e menções. +redirect_from: + - /articles/about-teams + - /github/setting-up-and-managing-organizations-and-teams/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +![Lista de equipes em uma organização](/assets/images/help/teams/org-list-of-teams.png) + +Os proprietários da organização e os mantenedores de equipe podem dar às equipes acesso de administrador, leitura ou gravação aos repositórios da organização. Os integrantes da organização podem enviar uma notificação a uma equipe inteira mencionando o nome da equipe. Os integrantes da organização também podem enviar uma notificação a uma equipe inteira solicitando uma revisão dessa equipe. Os integrantes da organização podem solicitar revisões de equipes específicas com acesso de leitura ao repositório onde a pull request está aberta. As equipes podem ser designadas como proprietários de determinados tipos de área de código em um arquivo CODEOWNERS. + +Para obter mais informações, consulte: +- "[Gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)" +- "[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" +- "[Sobre proprietários do código](/articles/about-code-owners/)" + +![Imagem de uma menção de equipe](/assets/images/help/teams/team-mention.png) + +{% if enterpriseServerVersions contains currentVersion %} + +Você também pode usar a sincronização LDAP para sincronizar os integrantes e funções da equipe da {% data variables.product.product_location %} com os grupos LDAP estabelecidos. Isso permite estabelecer o controle de acesso baseado em função para usuários do servidor LDAP em vez de manualmente na {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar a Sincronização LDAP](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". + +{% endif %} + +{% data reusables.organizations.team-synchronization %} + +### Visibilidade da equipe + +{% data reusables.organizations.types-of-team-visibility %} + +### Páginas da equipe + +Cada equipe tem sua própria página em uma organização. Na página de uma equipe, é possível exibir integrantes da equipe, equipes secundárias e os repositórios da equipe. Os proprietários da organização e os mantenedores de equipe podem acessar as configurações da equipe, bem como atualizar a descrição e a foto de perfil da equipe na página da equipe. + +Os integrantes da organização podem criar e participar de discussões com a equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)". + +![Página da equipe listando integrantes e discussões da equipe](/assets/images/help/organizations/team-page-discussions-tab.png) + +### Equipes aninhadas + +Você pode refletir seu grupo ou a hierarquia da empresa na sua organização do {% data variables.product.product_name %} com vários níveis de equipes aninhadas. Uma equipe principal pode ter várias equipes secundárias, enquanto cada equipe secundária tem apenas uma equipe principal. Não é possível aninhar equipes secretas. + +As equipes secundárias herdam as permissões de acesso da principal, simplificando o gerenciamento de permissões para grandes grupos. Os integrantes das equipes secundárias também recebem notificações quando a equipe principal é @mencionada, simplificando a comunicação com vários grupos de pessoas. + +Por exemplo, se a estrutura da sua equipe for Funcionários > Engenharia > Engenharia de aplicativos > Identidade, conceder à Engenharia acesso de gravação a um repositório significa que a Engenharia de aplicativos e a Identidade também obterão esse acesso. Se você @mencionar a Equipe Identidade ou qualquer equipe na parte inferior da hierarquia da organização, elas serão as únicas que receberão uma notificação. + +![Página das equipes com uma equipe principal e equipes secundárias](/assets/images/help/teams/nested-teams-eng-example.png) + +Para entender facilmente quem compartilha permissões da equipe principal e faz menção, você pode ver todos os integrantes das equipes secundárias de uma equipe principal na guia Members (Integrantes) da página da equipe principal. Os integrantes de uma equipe secundária não são integrantes diretos da equipe principal. + +![Página da equipe principal com todos os integrantes das equipes secundárias](/assets/images/help/teams/team-and-subteam-members.png) + +Você pode escolher uma principal quando criar a equipe ou pode mover uma equipe na hierarquia da organização posteriormente. Para obter mais informações, consulte "[Mover uma equipe na hierarquia da sua organização](/articles/moving-a-team-in-your-organization-s-hierarchy)". + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +### Preparar para aninhar equipes em sua organização + +Se a sua organização já tiver equipes, você deverá auditar as permissões de acesso ao repositório de cada equipe antes de aninhar equipes acima ou abaixo dela. Também é preciso considerar a nova estrutura que deseja implementar para a organização. + +No topo da hierarquia da equipe, você deve fornecer às equipes principais permissões de acesso ao repositório que sejam seguras para cada integrante da equipe principal e suas equipes secundárias. À medida que desce pela hierarquia, você pode conceder às equipes secundárias adicionais, acesso mais granular a repositórios mais confidenciais. + +1. Remova todos os integrantes das equipes existentes +2. Audite e ajuste as permissões de acesso ao repositório de cada equipe e forneça a cada equipe uma equipe principal +3. Crie qualquer equipe nova que desejar, escolha uma principal para cada equipe nova e forneça a ela acesso ao repositório +4. Adicione pessoas diretamente às equipes + +### Leia mais + +- "[Criar uma equipe](/articles/creating-a-team)" +- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000..d96249139f --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,32 @@ +--- +title: Adicionar integrantes da organização a uma equipe +intro: 'As pessoas com permissões de proprietário ou mantenedor de equipe podem adicionar integrantes da organização às equipes. Pessoas com permissões de proprietário também podem {% if currentVersion == "free-pro-team@latest" %}convidar os não integrantes a juntar-se a {% else %}adicionar não integrantes a {% endif %} uma equipe e à organização.' +redirect_from: + - /articles/adding-organization-members-to-a-team-early-access-program/ + - /articles/adding-organization-members-to-a-team + - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. Acima da lista de integrantes da equipe, clique em **Adicionar um integrante**. ![Botão Add member (Adicionar integrante)](/assets/images/help/teams/add-member-button.png) +{% data reusables.organizations.invite_to_team %} +{% data reusables.organizations.review-team-repository-access %} + +{% if currentVersion == "free-pro-team@latest" %}{% data reusables.organizations.cancel_org_invite %}{% endif %} + +### Leia mais + +- "[Sobre equipes](/articles/about-teams)" +- "[Gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/changing-team-visibility.md new file mode 100644 index 0000000000..119c1fc7a9 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/changing-team-visibility.md @@ -0,0 +1,29 @@ +--- +title: Alterar a visibilidade da equipe +intro: Os mantenedores de equipe e os proprietários da organização podem determinar se uma equipe ficará *visível* ou *secreta*. +redirect_from: + - /articles/changing-team-visibility + - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.types-of-team-visibility %} + +{% tip %} + +**Dica:** se uma equipe tiver [equipes principais ou secundárias](/articles/about-teams), não será possível torná-la secreta. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +3. Selecione a(s) equipe(s) cuja visibilidade deseja alterar. ![Lista de equipes com duas equipes selecionadas](/assets/images/help/teams/list-of-teams-selected.png) +4. Acima da lista de equipes, use o menu suspenso e clique em **Change visibility** (Alterar visibilidade). ![Menu suspenso com opção para alterar visibilidade da equipe](/assets/images/help/teams/team-bulk-management-options.png) +5. Escolha se deseja tornar a(s) equipe(s) visível(is) ou secreta(s) e clique em **Change visibility** (Alterar visibilidade). ![Botões de opção para tornar uma equipe visível ou secreta e botão Change visibility (Alterar visibilidade)](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md new file mode 100644 index 0000000000..7786dfd1ec --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -0,0 +1,38 @@ +--- +title: Criar equipes +intro: Você pode criar equipes independentes ou aninhadas para gerenciar permissões de repositório e menções para grupos de pessoas. +redirect_from: + - /articles/creating-a-team-early-access-program/ + - /articles/creating-a-team + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Apenas os proprietários e mantenedores de uma equipe principal podem criar uma nova equipe secundária sob a principal. Os proprietários também podem restringir as permissões de criação para todas as equipes em uma organização. Para obter mais informações, consulte "[Configurar permissões de criação de equipes na organização](/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. Opcionalmente, se sua conta de organização ou empresa usar a sincronização de equipes, para conectar um grupo de provedor de identidade à sua equipe, use o menu suspenso "Grupos de provedores de identidade" e selecione até 5 grupos de provedores de identidade. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Menu suspenso para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png) +{% endif %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} +9. Se desejar, [forneça à equipe acesso aos repositórios da organização](/articles/managing-team-access-to-an-organization-repository). + +### Leia mais + +- "[Sobre equipes](/articles/about-teams)" +- "[Alterar a visibilidade da equipe](/articles/changing-team-visibility)" +- "[Mover uma equipe na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/deleting-a-team.md new file mode 100644 index 0000000000..76f69f0ec6 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/deleting-a-team.md @@ -0,0 +1,27 @@ +--- +title: Excluir uma equipe +intro: Os proprietários da organização podem excluir equipes a qualquer momento da página de configurações da equipe. +redirect_from: + - /articles/deleting-a-team + - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Dica:** somente proprietários da organização podem excluir equipes principais. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)". + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Selecione as equipes que deseja excluir. ![Lista de equipes com duas equipes selecionadas](/assets/images/help/teams/list-of-teams-selected.png) +5. Acima da lista de equipes, use o menu suspenso e clique em **Delete** (Excluir). ![Menu suspenso com opção para alterar visibilidade da equipe](/assets/images/help/teams/team-bulk-management-options.png) +6. Revise as equipes que serão excluídas e clique em **I understand, delete teams** (Entendi; exclua as equipes). ![Lista de equipes que serão excluídas e o botão Delete teams (Excluir equipes)](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000..3c28612531 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Desabilitar discussões de equipe da sua organização +intro: Os proprietários da organização podem optar por desabilitar ou habilitar discussões de equipe na organização. +redirect_from: + - /articles/disabling-team-discussions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team-discussions-default %} Consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para obter mais informações sobre esse assunto. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +5. Em "Team discussions" (Discussões de equipe), desmarque **Enable team discussions for this organization** (Habilitar discussões de equipe desta organização). ![Caixa de seleção para habilitar ou desabilitar discussões de equipe de uma organização](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) +6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/index.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/index.md new file mode 100644 index 0000000000..1e7ee06a9f --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/index.md @@ -0,0 +1,38 @@ +--- +title: Organizar integrantes em equipes +intro: Você pode agrupar os integrantes da organização em equipes que reflitam sua empresa ou a estrutura do grupo, com permissões de acesso em cascata e menções. +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 + - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000..dbe3f19cc5 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,51 @@ +--- +title: Gerenciar a atribuição de revisão de código para a sua equipe +intro: As atividades de revisão do código indicam claramente quais membros de uma equipe devem enviar uma revisão para um pull request. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +Os mantenedores de equipe e os proprietários da organização podem configurar atribuições de revisão de código. + +### Sobre as atribuições de revisão de código + +Ao usar atribuições de revisão de código, a qualquer momento em que for solicitado que a sua equipe revise um pull request, a equipe será removida como revisora e um subconjunto específico de integrantes da equipe será atribuído em seu lugar. As atribuições de revisão de código permitem que você decida se toda a equipe ou apenas um subconjunto dos seus integrantes serão notificados quando for solicitado que uma equipe faça a revisão. + +Quando se solicita automaticamente que os proprietários de códigos façam uma revisão, a equipe será removida e substituída por indivíduos. As aprovações individuais não satisfazem o requisito para aprovação do proprietário do código em um branch protegido. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)". + +### Encaminhar algoritmos + +Escolha as atribuições de revisão de código e atribua os revisores automaticamente com base em um dos dois algoritmos possíveis. + +O algoritmo round robin (rotativo) escolhe os revisores com base em quem recebeu a solicitação de revisão menos recente e tem o foco em alternar entre todos os integrantes da equipe, independentemente do número de avaliações pendentes que possuem atualmente. + +O algoritmo do balanço de carga escolhe os revisores com base no número total de solicitações de revisão recentes de cada integrante e considera o número de revisões pendentes para cada integrante. O algoritmo do balanço de carga tenta garantir que cada integrante da equipe revise um número igual de pull requests em qualquer período de 30 dias. + +### Configurar a atribuição da revisão de código +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Na barra lateral esquerda, clique em **Atribuição de revisão de código** ![Botão da atribuição da revisão de código](/assets/images/help/teams/review-assignment-button.png) +6. Selecione **Habilitar atribuição automática**. ![Botão da atribuição da revisão de código](/assets/images/help/teams/review-assignment-enable.png) +7. Em "Quantos membros da equipe devem ser atribuídos para a revisão?, use o menu suspenso e escolha um número de revisores a serem atribuídos a cada pull request. ![Menu suspenso do número de revisores](/assets/images/help/teams/review-assignment-number.png) +8. Em "Algoritmo de encaminhamento", use o menu suspenso e escolha qual algoritmo você gostaria de usar. Para obter mais informações, consulte "[Algoritmos de encaminhamento](#routing-algorithms)". ![Menu suspenso do algoritmo de encaminhamento](/assets/images/help/teams/review-assignment-algorithm.png) +9. Opcionalmente, para sempre ignorar determinados membros da equipe, selecione **Nunca atribuir certos integrantes da equipe**. Em seguida, selecione um ou mais integrantes da equipe que você gostaria de ignorar sempre. ![Menu suspenso e caixa de seleção "Nunca atribuir certos integrantes da equipe"](/assets/images/help/teams/review-assignment-skip-members.png) +10. Opcionalmente, para notificar apenas os integrantes da equipe escolhidos pela atribuição de revisão de código para cada solicitação de revisão de pull request, em "Notificações", selecione **Ao atribuir integrantes da equipe, não notifique toda a equipe.** ![Notificações de atribuições de revisão de código](/assets/images/help/teams/review-assignment-notifications.png) +11. Clique em **Save changes** (Salvar alterações). + +### Desabilitar atribuição de revisão de código +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Selecione **Habilitar atribuição automática** para remover a marca. ![Botão da atribuição da revisão de código](/assets/images/help/teams/review-assignment-enable.png) +6. Clique em **Save changes** (Salvar alterações). diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000..7b0f98c185 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,69 @@ +--- +title: Gerenciar lembretes agendados para a sua equipe +intro: Você pode receber lembretes no Slack quando sua equipe tiver pull requests à espera de revisão. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### Sobre os lembretes agendados para as equipes + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Os mantenedores de equipe e os proprietários da organização podem definir lembretes agendados para quaisquer pull requests que se solicite que uma equipe revise. Antes de criar um lembrete agendado para sua equipe, um proprietário da organização deve autorizar o seu espaço de trabalho do Slack. Para obter mais informações, consulte "[Gerenciar lembretes agendados para a sua organização](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)". + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Criar um lembrete agendado para uma equipe +{% 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ão de lembretes agendados](/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 %} + +### Gerenciar um lembrete agendado para uma equipe +{% 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ão de lembretes agendados](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Excluir um lembrete agendado para uma equipe +{% 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ão de lembretes agendados](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.delete %} + +### Leia mais + +- "[Gerenciar lembretes agendados para a sua organização](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- "[Gerenciar seus lembretes agendados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000..f18574310f --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,42 @@ +--- +title: Movendo uma equipe na hierarquia da organização +intro: 'Mantenedores de equipes e proprietários de organizações podem encaixar uma equipe abaixo de uma equipe principal, ou ainda, alterar ou remover uma principal da equipe aninhada.' +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 + - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Proprietários de organizações podem mudar a principal de qualquer equipe. Mantenedores de equipes podem alterar a principal de uma equipe se forem mantenedores da equipe secundária e da equipe principal. Mantenedores de equipe sem permissões de mantenedor na equipe secundária podem solicitar para adicionar uma equipe principal ou secundária. Para obter mais informações, consulte "[Solicitar adição ou alteraração de uma equipe principal](/articles/requesting-to-add-or-change-a-parent-team)" e "[Solicitar adição de uma equipe secundária](/articles/requesting-to-add-a-child-team)". + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% tip %} + +**Dicas:** +- Você não pode alterar uma equipe principal para equipe secreta. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)". +- Você não pode encaixar uma equipe principal sob uma de suas equipes secundárias. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Na lista de equipes, clique no nome da equipe cuja principal você deseja alterar. ![Lista das equipes da organização](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Use o menu suspenso para escolher uma equipe principal ou para remover uma principal existente e selecione **Clear selected value** (Limpar valor selecionado). ![Menu suspenso listando as equipes da organização](/assets/images/help/teams/choose-parent-team.png) +7. Clique em **Atualizar**. +{% data reusables.repositories.changed-repository-access-permissions %} +9. Clique em **Confirm new parent team** (Confirmar nova equipe principal). ![Caixa de diálogo modal com informações sobre as alterações nas permissões de acesso ao repositório](/assets/images/help/teams/confirm-new-parent-team.png) + +### Leia mais + +- "[Sobre equipes](/articles/about-teams)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000..8bbd6c3bec --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,23 @@ +--- +title: Remover integrantes da organização de uma equipe +intro: 'Os usuários com permissões de *proprietário* ou *mantenedor de equipe* podem remover integrantes de uma equipe. Isso pode ser necessário se um usuário não precisar mais acessar um repositório ao qual a equipe tem acesso ou se um usuário deixar de participar dos projetos de uma equipe.' +redirect_from: + - /articles/removing-organization-members-from-a-team-early-access-program/ + - /articles/removing-organization-members-from-a-team + - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. Selecione um ou mais integrantes que deseja remover. ![Caixa de seleção ao lado de integrante de organização](/assets/images/help/teams/team-member-check-box.png) +5. Use o menu suspenso acima da lista de integrantes da equipe e clique em **Remove from team** (Remover da equipe). ![Menu suspenso com opção change role (alterar função)](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/renaming-a-team.md new file mode 100644 index 0000000000..20d1c8dae4 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/renaming-a-team.md @@ -0,0 +1,21 @@ +--- +title: Renomear uma equipe +intro: Mantenedores de equipe e proprietários da organização podem editar o nome e a descrição da equipe. +redirect_from: + - /articles/renaming-a-team + - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Insira um novo nome ou descrição para a equipe. ![Campos de nome e descrição da equipe](/assets/images/help/teams/team-name-description.png) +6. Clique em **Atualizar**. diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000..b8ebb3ace8 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,36 @@ +--- +title: Solicitar a adição de uma equipe secundária +intro: 'Se você tiver permissões de mantenedor em uma equipe, poderá solicitar o aninhamento de uma equipe abaixo da sua equipe na hierarquia da organização.' +redirect_from: + - /articles/requesting-to-add-a-child-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Quando você solicita a adição de uma equipe como uma equipe secundária, uma solicitação é enviada aos mantenedores da equipe secundária. Quando um mantenedor da equipe secundária aprova a solicitação, a equipe secundária é aninhada abaixo da equipe principal na hierarquia da organização. + +Se você for proprietário da organização ou tiver permissões de mantenedor de equipe na equipe secundária e na equipe principal, poderá adicionar a equipe secundária sem solicitar aprovação ou alterar a equipe principal da equipe secundária na página de configurações da equipe secundária. Para obter mais informações, consulte "[Mover uma equipe na hierarquia da sua organização](/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. Na lista de equipes, clique no nome da equipe na qual deseja adicionar a equipe secundária. ![Lista das equipes da organização](/assets/images/help/teams/click-team-name.png) +5. Na parte superior da página da equipe, clique em {% octicon "people" aria-label="The people icon" %} **Teams** (Equipes). ![Guia Teams (Equipes) na página de uma equipe](/assets/images/help/teams/team-teams-tab.png) +6. Clique em **Add a team** (Adicionar uma equipe). ![Botão Add a team (Adicionar uma equipe) na página de uma equipe](/assets/images/help/teams/add-a-team.png) +7. Insira o nome da equipe que deseja adicionar como equipe secundária e selecione-a na lista suspensa.![Caixa de texto para digitar e menu suspenso para selecionar o nome da equipe secundária](/assets/images/help/teams/type-child-team-name.png) +{% data reusables.repositories.changed-repository-access-permissions %} +9. Clique em **Confirm changes** (Confirmar alterações) para enviar uma solicitação de adição da equipe secundária. ![Caixa de diálogo modal com informações sobre as alterações nas permissões de acesso ao repositório](/assets/images/help/teams/confirm-new-parent-team.png) + +### Leia mais + +- "[Sobre equipes](/articles/about-teams)" +- "[Mover uma equipe na hierarquia da sua organização](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Solicitar a adição ou alteração de uma equipe principal](/articles/requesting-to-add-or-change-a-parent-team)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000..8cc9079ab9 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,36 @@ +--- +title: Solicitar a adição ou alteração de uma equipe principal +intro: 'Se você tiver permissões de mantenedor em uma equipe, poderá solicitar o aninhamento da sua equipe abaixo de uma equipe principal na hierarquia da organização.' +redirect_from: + - /articles/requesting-to-add-or-change-a-parent-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Quando você solicita a adição ou alteração da equipe principal, uma solicitação é enviada aos mantenedores da equipe principal. Quando um mantenedor da nova equipe principal aprova a solicitação, sua equipe é aninhada como uma equipe secundária abaixo da equipe principal na hierarquia da organização. + +Se você for proprietário da organização ou tiver permissões de mantenedor de equipe na equipe secundária e na equipe principal, poderá adicionar a equipe principal sem solicitar aprovação ou alterar a equipe principal na página de configurações da equipe. Para obter mais informações, consulte "[Mover uma equipe na hierarquia da sua organização](/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. Na lista de equipes, clique no nome da equipe que deseja aninhar abaixo de uma equipe principal. ![Lista das equipes da organização](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Em "Parent team" (Equipe principal), use o menu suspenso "Select parent team" (Selecionar equipe principal) e clique no nome da nova equipe principal. ![Menu suspenso listando as equipes da organização](/assets/images/help/teams/choose-parent-team.png) +7. Clique em **Save changes** (Salvar alterações). +{% data reusables.repositories.changed-repository-access-permissions %} +9. Clique em **Confirm changes** (Confirmar alterações) para enviar uma solicitação de adição ou alteração da equipe principal. ![Caixa de diálogo modal com informações sobre as alterações nas permissões de acesso ao repositório](/assets/images/help/teams/confirm-new-parent-team.png) + +### Leia mais + +- "[Sobre equipes](/articles/about-teams)" +- "[Mover uma equipe na hierarquia da sua organização](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Solicitar a adição de uma equipe secundária](/articles/requesting-to-add-a-child-team)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000..15d0028895 --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,24 @@ +--- +title: Configurar a foto de perfil da sua equipe +intro: 'Os mantenedores da equipe e os proprietários da organização podem configurar a foto de perfil de uma equipe, que é exibida na página da equipe.' +redirect_from: + - /articles/setting-your-team-s-profile-picture + - /articles/setting-your-teams-profile-picture + - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Se você não configurar a foto de perfil da equipe, a foto da equipe será a foto de perfil da organização. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Clique em **Upload new picture** (Fazer upload de uma nova imagem) e selecione a foto de perfil desejada. ![Upload new picture (Fazer upload de uma nova imagem)](/assets/images/help/teams/org-team-profile-picture-upload.png) +6. Clique e arraste para cortar a imagem conforme necessário, depois clique em **Set new team avatar** (Configurar novo avatar da equipe). ![Set new team avatar (Configurar novo avatar da equipe)](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000..36a300f5ea --- /dev/null +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,99 @@ +--- +title: Sincronizar uma equipe com um grupo de provedor de identidade +intro: 'Você pode sincronizar uma equipe do {% data variables.product.product_name %} com um grupo de provedor de identidade (IdP) para adicionar e remover automaticamente os integrantes da equipe.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group +product: '{% data reusables.gated-features.team-synchronization %}' +permissions: 'Os proprietários da organização e mantenedores da equipe podem sincronizar uma equipe do {% data variables.product.prodname_dotcom %} com um grupo de IdP.' +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### Sobre a sincronização de equipes + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% if currentVersion == "free-pro-team@latest" %}Você pode conectar até cinco grupos de IdP a uma equipe de {% data variables.product.product_name %}.{% elsif currentVersion == "github-ae@latest" %}Você pode conectar uma equipe em {% data variables.product.product_name %} a um grupo de IdP. Todos os usuários do grupo são automaticamente adicionados à equipe e também adicionados à organização principal como integrantes. Ao desconectar um grupo de uma equipe, os usuários que se tornaram integrantes da organização por meio da associação da equipe serão removidos da organização.{% endif %} Você pode atribuir um grupo de IdP a várias equipes de {% data variables.product.product_name %}. + +{% if currentVersion == "free-pro-team@latest" %}A sincronização de equipes não é compatível com grupos de IdP com mais de 5000 integrantes.{% endif %} + +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 da equipe em {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} ou usando a API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} +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)". +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Qualquer solicitação que altere a equipe de {% data variables.product.prodname_dotcom %} equipe ou associação da organização será registrada no log de auditoria como alterações feitas pela conta usada para configurar provisionamento do usuário. Para obter mais informações sobre essa conta, consulte "[Configurar o provisionamento de usuários para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obter mais informações sobre o agendamento de pedidos do SCIM, consulte "[Verificar o status do provisionamento do usuário](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" na documentação da Microsoft. +{% endif %} + +As equipes principais não podem sincronizar com grupos de IdP. Se a equipe que você deseja conectar a um grupo IdP for uma equipe principal, recomendamos criar uma equipe nova ou remover as relações aninhadas que fazem da sua equipe uma equipe principal. Para obter mais informações, consulte "[Sobre as equipes](/articles/about-teams#nested-teams)"[Criar uma equipe](/organizations/organizing-members-into-teams/creating-a-team), e "[Mover uma equipe para a hierarquia da sua organização](/articles/moving-a-team-in-your-organizations-hierarchy) + +Para gerenciar o acesso ao repositório de qualquer equipe do {% data variables.product.prodname_dotcom %} incluindo equipes conectadas a um grupo de IdP, você deve fazer alterações com o {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)" e "[Gerenciar o acesso da equipe ao repositório de uma organização](/articles/managing-team-access-to-an-organization-repository)". + +{% if currentVersion == "free-pro-team@latest" %}Você também pode gerenciar a sincronização de equipes com a API. Para obter mais informações, consulte "[Sincronização de equipe](/rest/reference/teams#team-sync)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Requisitos para integrantes de equipes sincronizadas + +Após conectar uma equipe a um grupo de IdP, a sincronização da equipe adicionará cada integrante do grupo IdP à equipe correspondente em {% data variables.product.product_name %} apenas se: +- A pessoa for integrante da organização em {% data variables.product.product_name %}. +- A pessoa já efetuou o login com sua conta de usuário em {% data variables.product.product_name %} e efetuou a autenticação na conta corporativa ou corporativa via logon único SAML pelo menos uma vez. +- A identidade SSO da pessoa é um integrante do grupo IdP. + +As equipes ou integrantes de grupo que não atenderem a esses critérios serão automaticamente removidos da equipe em {% data variables.product.product_name %} e perderão o acesso aos repositórios. Revogar a identidade vinculada a um usuário também removerá o usuário de quaisquer equipes mapeadas com os grupos de IdP. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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 mais informações, consulte "[Aplicar logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" e "[Habilitar o logon único SAML para organizações na sua conta corporativa](/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 "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". + +{% endif %} + +### Pré-requisitos + +{% if currentVersion == "free-pro-team@latest" %} +Before you can connect a {% data variables.product.product_name %} 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](/organizations/managing-saml-single-sign-on-for-your-organization/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. + +Você deve efetuar a autenticação usando SAML SSO. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)". + +{% elsif currentVersion == "github-ae@latest" %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". + +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. Para obter mais informações, consulte [Configurar o provisionamento automático do usuário no GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) na documentação da Microsoft. +{% endif %} + +### Conectar um grupo de IdP a uma equipe + +Ao conectar um grupo de IdP a uma equipe de {% data variables.product.product_name %}, todos os usuários do grupo serão automaticamente adicionados à equipe. {% if currentVersion == "github-ae@latest" %}Todos os usuários que não eram integrantes dos da organização principal também serão adicionados à organização.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Em "Grupos de provedores de identidade", use o menu suspenso e selecione até 5 grupos de provedores de identidade. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. No "Grupo de Provedores de Identidade", use o menu suspenso e selecione um grupo de provedores de identidade na lista. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. Clique em **Save changes** (Salvar alterações). + +### Desconectar um grupo de IdP de uma equipe + +Se desconectar um grupo de IdP de uma equipe do {% data variables.product.prodname_dotcom %}, os integrantes da equipe atribuídos à equipe do {% data variables.product.prodname_dotcom %} por meio do grupo de IdP serão removidos da equipe. {% if currentVersion == "github-ae@latest" %} Todos os usuários que eram integrantes da organização principal apenas por causa da conexão com a equipe também serão removidos da organização.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Em "Grupos de provedores de identidade", à direita do grupo de IdP que você deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Em "Grupo de Provedores de Identidade", à direita do grupo de IdP que você deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Clique em **Save changes** (Salvar alterações). diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000..e667a92e8a --- /dev/null +++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -0,0 +1,60 @@ +--- +title: Sobre restrições de acesso do aplicativo OAuth +intro: 'As organizações podem escolher quais {% data variables.product.prodname_oauth_app %}s terão acesso a seus repositórios e outros recursos habilitando as restrições de acesso do {% data variables.product.prodname_oauth_app %}.' +redirect_from: + - /articles/about-third-party-application-restrictions/ + - /articles/about-oauth-app-access-restrictions + - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Quando as restrições de acesso do {% data variables.product.prodname_oauth_app %} são habilitadas, os integrantes da organização não podem autorizar o acesso do {% data variables.product.prodname_oauth_app %} aos recursos da organização. Os integrantes da organização podem solicitar aprovação do proprietário para os {% data variables.product.prodname_oauth_app %}s que gostariam de usar, e os proprietários da organização recebem uma notificação de solicitações pendentes. + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% tip %} + +**Dica**: quando uma organização não configura as restrições de acesso do {% data variables.product.prodname_oauth_app %}, qualquer {% data variables.product.prodname_oauth_app %} autorizado por um integrante da organização também pode acessar os recursos privados da organização. + +{% endtip %} + +### Configurar as restrições de acesso do {% data variables.product.prodname_oauth_app %} + +Quando um proprietário da organização configura as restrições de acesso do {% data variables.product.prodname_oauth_app %} pela primeira vez: + +- Os **aplicativos que a organização possui** recebem acesso automaticamente aos recursos da organização. +- Os **{% data variables.product.prodname_oauth_app %}s** perdem imediatamente o acesso aos recursos da organização. +- As **chaves SSH criadas antes de fevereiro de 2014** perdem imediatamente o acesso aos recursos da organização (isso inclui chaves de implantação e usuário). +- As **chaves SSH criadas pelos {% data variables.product.prodname_oauth_app %} durante ou após fevereiro de 2014** perdem acesso imediatamente aos recursos da organização. +- As **entregas de hook de repositórios da organização privada** não serão mais enviadas a {% data variables.product.prodname_oauth_app %}s não aprovados. +- O **acesso de API** aos recursos da organização privada não é disponibilizado para {% data variables.product.prodname_oauth_app %}s não aprovados. Além disso, não há ações de criação, atualização ou exclusão com privilégios em recursos de organização pública. +- Os **hooks criados pelos usuários e antes de maio de 2014** não serão afetados. +- As **bifurcações privadas dos repositórios de propriedade da organização** estão sujeitas às restrições de acesso da organização. + +### Resolver falhas de acesso de SSH + +Quando uma chave SSH criada antes de fevereiro de 2014 perde acesso a uma organização com restrições de acesso do {% data variables.product.prodname_oauth_app %} habilitadas, as tentativas de acesso subsequentes do SSH falharão. Os usuários encontrarão uma mensagem de erro direcionando-as a uma URL onde podem aprovar a chave ou fazer upload de uma chave confiável. + +### Webhooks + +Quando um {% data variables.product.prodname_oauth_app %} receber acesso à organização depois que as restrições forem habilitadas, os webhooks preexistentes criados por esse {% data variables.product.prodname_oauth_app %} retomarão o envio. + +Quando uma organização remover o acesso de um {% data variables.product.prodname_oauth_app %} anteriormente aprovado, todos os webhooks preexistentes criados por esse aplicativo não serão mais enviados (esses hooks serão desabilitados, mas não excluídos). + +### Reabilitando restrições de acesso + +Se uma organização desabilitar as restrições de acesso do {% data variables.product.prodname_oauth_app %} e, posteriormente, reabilitá-las, os {% data variables.product.prodname_oauth_app %}s anteriormente aprovados receberão acesso automaticamente aos recursos da organização. + +### Leia mais + +- "[Habilitar restrições de acesso do {% data variables.product.prodname_oauth_app %} para sua organização](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" +- "[Aprovar {% data variables.product.prodname_oauth_app %} para sua organização](/articles/approving-oauth-apps-for-your-organization)" +- "[Revisar integrações instaladas da sua organização](/articles/reviewing-your-organization-s-installed-integrations)" +- "[Negar acesso ao {% data variables.product.prodname_oauth_app %} anteriormente aprovado para sua organização](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" +- "[Desabilitar restrições de acesso do {% data variables.product.prodname_oauth_app %} para sua organização](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" +- "[Solicitar aprovação da organização para os {% data variables.product.prodname_oauth_app %}s](/articles/requesting-organization-approval-for-oauth-apps)" +- "[Autorizar {% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps)" diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000..178060d41b --- /dev/null +++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Aprovar aplicativos OAuth na organização +intro: 'Quando uma integrante da organização solicita acesso do {% data variables.product.prodname_oauth_app %} aos recursos da organização, os proprietários da organização podem aprová-la ou negá-la.' +redirect_from: + - /articles/approving-third-party-applications-for-your-organization/ + - /articles/approving-oauth-apps-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Quando as restrições de acesso do {% data variables.product.prodname_oauth_app %} são habilitadas, os integrantes da organização devem [solicitar aprovação](/articles/requesting-organization-approval-for-oauth-apps) de um proprietário da organização para que eles possam autorizar um {% data variables.product.prodname_oauth_app %} que tenha acesso aos recursos da organização. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Ao lado do aplicativo que deseja aprovar, clique em **Review** (Revisar). ![Link de solicitação de revisão](/assets/images/help/settings/settings-third-party-approve-review.png) +6. Depois que revisar as informações sobre o aplicativo solicitado, clique em **Grant access** (Conceder acesso). ![Botão Grant access (Conceder acesso)](/assets/images/help/settings/settings-third-party-approve-grant.png) + +### Leia mais + +- "[Sobre restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000..1a450cfaa3 --- /dev/null +++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,20 @@ +--- +title: Negar acesso a um aplicativo OAuth previamente aprovado para a organização +intro: 'Se uma organização não requer mais um {% data variables.product.prodname_oauth_app %} previamente autorizado, os proprietários podem remover o acesso do aplicativo aos recursos da organização.' +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 + - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Ao lado do aplicativo que deseja desabilitar, clique em {% octicon "pencil" aria-label="The edit icon" %}. ![Ícone Edit (Editar)](/assets/images/help/settings/settings-third-party-deny-edit.png) +6. Clique em **Deny access** (Negar). ![Botão Deny confirmation (Negar confirmação)](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..83932c8c3b --- /dev/null +++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Desabilitar restrições de acesso do aplicativo OAuth da sua organização +intro: 'Os proprietários da organização podem desabilitar restrições nos {% data variables.product.prodname_oauth_app %}s que têm acesso aos recursos da organização.' +redirect_from: + - /articles/disabling-third-party-application-restrictions-for-your-organization/ + - /articles/disabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% danger %} + +**Aviso**: com a desabilitação das restrições de acesso do {% data variables.product.prodname_oauth_app %} da sua organização, qualquer integrante da organização autorizará automaticamente o acesso do {% data variables.product.prodname_oauth_app %} aos recursos privados da organização ao aprovar um aplicativo para ser usado nas configurações de conta pessoal dele. + +{% enddanger %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Clique em **Remove restrictions** (Remover restrições). ![Botão Remove restrictions (Remover restrições)](/assets/images/help/settings/settings-third-party-remove-restrictions.png) +6. Depois de revisar as informações sobre desabilitação de restrições de aplicativos de terceiros, clique em **Yes, remove application restrictions** (Sim, remover restrições de aplicativos). ![Botão de remover confirmação](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..db6c2bba00 --- /dev/null +++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Habilitar restrições de acesso do aplicativo OAuth da sua organização +intro: 'Os proprietários da organização podem habilitar restrições de acesso do {% data variables.product.prodname_oauth_app %} para impedir que aplicativos não confiáveis acessem recursos da organização ao permitir que integrantes da organização usem {% data variables.product.prodname_oauth_app %}s para suas contas pessoais.' +redirect_from: + - /articles/enabling-third-party-application-restrictions-for-your-organization/ + - /articles/enabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% warning %} + +**Avisos**: +- A habilitação de restrições de acesso do {% data variables.product.prodname_oauth_app %} revogará o acesso da organização para todos os {% data variables.product.prodname_oauth_app %}s e chaves SSH previamente autorizados. Para obter mais informações, consulte "[Sobre restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)". +- Depois de configurar as restrições de acesso do {% data variables.product.prodname_oauth_app %}, lembre-se de tornar a autorizar qualquer {% data variables.product.prodname_oauth_app %} que requeira acesso aos dados privados da organização continuamente. Todos os integrantes da organização precisarão criar chaves SSH, e a organização precisará criar chaves de implantação conforme necessário. +- Quando as restrições de acesso do {% data variables.product.prodname_oauth_app %} estiverem habilitadas, os aplicativos poderão usar um token OAuth para acessar informações sobre transações do {% 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. Em "Third-party application access policy" (Política de acesso a aplicativos de terceiros), clique em **Setup application access restrictions** (Configurar restrições de acesso a aplicativos). ![Botão Set up restrictions (Configurar restrições)](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) +6. Depois de revisar as informações sobre restrições de acesso a terceiros, clique em **Restrict third-party application access** (Restringir acesso a aplicativos de terceiros). ![Botão Restriction confirmation (Confirmação de restrição)](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md new file mode 100644 index 0000000000..a1e5a03f6a --- /dev/null +++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -0,0 +1,19 @@ +--- +title: Restringir o acesso aos dados da organização +intro: 'As restrições de acesso ao {% data variables.product.prodname_oauth_app %} permitem que os proprietários da organização restrinjam o acesso de um app não confiável aos dados da organização. Os integrantes da organização podem então usar o {% data variables.product.prodname_oauth_app %} para as contas de usuário pessoais, mantendo os dados da organização seguros.' +redirect_from: + - /articles/restricting-access-to-your-organization-s-data + - /articles/restricting-access-to-your-organizations-data + - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file 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 4c70530c6f..15ff056c22 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 @@ -11,9 +11,11 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} **Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. @@ -30,10 +32,10 @@ Para efetuar a autenticação em {% data variables.product.prodname_registry %} Você deve substituir: - `USUÁRIO` pelo o nome da sua conta de usuário em {% data variables.product.prodname_dotcom %}. - `TOKEN` pelo seu token de acesso pessoal. -- `PROPRIETÁRIO` com o nome da conta do usuário ou da organização que é proprietário do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %} -- `HOSTNAME` com o nome de host para sua instância de {% data variables.product.prodname_ghe_server %}. +- `PROPRIETÁRIO` com o nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto.{%if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- `HOSTNAME` com o nome do host para {% data variables.product.product_location %}.{% endif %} -Se sua instância tem o isolamento de subdomínio habilitado: +{%if enterpriseServerVersions contains currentVersion %}Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} ```xml @@ -78,10 +80,40 @@ 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. +Você pode publicar um pacote em {% data variables.product.prodname_registry %} autenticando com um arquivo *nuget.config*{% se a correnteVersion == "free-pro-team@latest" ou currentVersion ver_gt "enterprise-server@2.22" ou currentVersion == "github-ae@latest"%}, ou usando a opção de linha de comando `--api-key com seu token de acesso pessoal (PAT) de {% data variables.product.prodname_dotcom %}{% endif %}.

+ +

{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}

+ +

Publicar um pacote usando um o PAT do GitHub como sua chave da API

+ +

Se você ainda não tem um PAT para usar na sua conta do {% data variables.product.prodname_dotcom %}, consulte "Criar um token de acesso pessoal".

+ +
    +

  1. Criar um novo projeto +

      dotnet new console --name OctocatApp
+`
    2. +2 +Empacotar o projeto. + ```shell + dotnet pack --configuration Release + ``` + +3 + +Publique o pacote usando o seu PAT como a chave da API. + ```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 %} + +#### Publicar um pacote usando um arquivo *nuget.config* + +Ao fazer a publicação, você precisa usar o mesmo valor para `PROPRIETÁRIO` no seu arquivo *csproj* que você usa no seu arquivo de autenticação *nuget.config*. Especifique ou incremente o número da versão no seu *.csproj* e, em seguida, utilize o comando `dotnet pack` para criar um arquivo *.nuspec* para essa versão. Para obter mais informações sobre como criar seu pacote, consulte "[Criar e publicar um pacote](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" na documentação da Microsoft. + {% data reusables.package_registry.authenticate-step %} 2. Criar um novo projeto ```shell @@ -90,8 +122,8 @@ Você pode publicar um pacote no {% data variables.product.prodname_registry %}, 3. Adicione informações específicas do seu projeto ao arquivo do seu projeto, que termina em *.csproj*. Você deve substituir: - `PROPRIETÁRIO` com o nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto. - `REPOSITÓRIO` pelo nome do repositório que contém o pacote que você deseja publicar. - - `1.0.0` com o número da versão do pacote.{% if enterpriseServerVersions contains currentVersion %} - - `HOSTNAME` com o nome de host para sua instância de {% data variables.product.prodname_ghe_server %} .{% endif %} + - `1.0.0` com o número de versão do pacote.{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} + - `HOSTNAME` com o nome do host para {% data variables.product.product_location %}.{% endif %} ``` xml @@ -118,6 +150,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. @@ -193,4 +227,4 @@ Usar pacotes do {% data variables.product.prodname_dotcom %} no seu projeto é s ### Leia mais -- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" +- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}" diff --git a/translations/pt-BR/content/packages/index.md b/translations/pt-BR/content/packages/index.md index 7f30b9ab5e..4345fc08cb 100644 --- a/translations/pt-BR/content/packages/index.md +++ b/translations/pt-BR/content/packages/index.md @@ -20,8 +20,8 @@ featuredLinks: - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - label: 'packages' - prefix: 'Packages: ' + label: 'pacotes' + prefix: 'Pacotes:' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..e92d961a52 --- /dev/null +++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -0,0 +1,68 @@ +--- +title: Sobre domínios personalizados e GitHub Pages +intro: 'O {% data variables.product.prodname_pages %} permite o uso de domínios personalizados, ou a alteração da raiz do URL do seu site do padrão, como ''octocat.github.io'', para qualquer domínio que você possua.' +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 + - /github/working-with-github-pages/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Páginas +--- + +### Domínios personalizados compatíveis + +O {% data variables.product.prodname_pages %} trabalha com dois tipos de domínio: subdomínios e domínios apex. Para obter uma lista de domínios personalizados não compatíveis, consulte "[Solução de problemas de domínios personalizados e {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)". + +| Tipo de domínio personalizado compatível | Exemplo | +| ---------------------------------------- | ------------------ | +| Subdomínio `www` | `www.example.com` | +| Subdomínio personalizado | `blog.example.com` | +| Domínio apex | `example.com` | + +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." + +É recomendável sempre usar um subdomínio `www`, mesmo se você também usar um domínio apex. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +Depois que você configurar um domínio personalizado para um site de usuário ou organização, o domínio personalizado substituirá a parte `.github.io` ou `.github.io` da URL para qualquer site de projeto de propriedade da conta que não tenha um domínio personalizado configurado. Por exemplo, se o domínio personalizado para o site de usuário for `www.octocat.com` e você tiver um site de projeto sem domínio personalizado configurado que seja publicado de um repositório chamado `octo-project`, o site do {% data variables.product.prodname_pages %} para esse repositório estará disponível em `www.octocat.com/octo-project`. + +### Usar um subdomínio para seu site do {% data variables.product.prodname_pages %} + +Um subdomínio é a parte de um URL antes do domínio raiz. Você pode configurar seu subdomínio como `www` ou como uma seção distinta do seu site, como `blog.example.com.`. + +Os subdomínios são configurados com um registro `CNAME` por meio do provedor DNS. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)". + +#### Subdomínios `www` + +Um subdomínio `www` é o tipo de subdomínio usado com mais frequência. Por exemplo, `www.example.com` inclui um subdomínio `www`. + +Os subdomínios `www` são o tipo mais estável de domínio personalizado, pois os subdomínios `www` não são afetados pelas alterações nos endereços IP dos servidores do {% data variables.product.product_name %}. + +#### Subdomínios personalizados + +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Os subdomínios personalizados são usados mais frequentemente quando você deseja duas seções distintas do site. Por exemplo, você pode criar um site chamado `blog.example.com.` e personalizar essa seção independentemente de `www.example.com`. + +### Usar um domínio apex para seu site do {% data variables.product.prodname_pages %} + +Um domínio apex é um domínio personalizado que não contém um subdomínio, como `example.com`. Os domínios apex também são conhecidos como domínios base, bare, naked, apex raiz ou apex de zona. + +Um domínio apex é configurado com um registro `A`, `ALIAS` ou `ANAME` por meio do provedor DNS. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)". + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." + +### Atualizar domínios personalizados quando seu site do {% data variables.product.prodname_pages %} é desabilitado + +Se seu site do {% data variables.product.prodname_pages %} estiver desabilitado, mas tiver um domínio personalizado configurado, você deverá atualizar ou remover imediatamente seus registros DNS com o provedor DNS a fim de evitar o risco de tomada de controle do domínio. Ter um domínio personalizado configurado com o provedor DNS enquanto o site está desabilitado pode fazer com que outra pessoa acabe hospedando um site em um de seus subdomínios. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +Há alguns motivos para que seu site possa ser desabilitado automaticamente. + +- Se você fizer downgrade do {% data variables.product.prodname_pro %} para o {% data variables.product.prodname_free_user %}, qualquer site do {% data variables.product.prodname_pages %} que esteja publicado no momento usando repositórios privados em sua conta terão a publicação cancelada. Para obter mais informações, consulte "[Fazer downgrade do plano de cobrança do {% data variables.product.prodname_dotcom %}](/articles/downgrading-your-github-billing-plan)". +- Se você transferir um repositório privado para uma conta pessoal que esteja usando o {% data variables.product.prodname_free_user %}, o repositório perderá o acesso ao recurso {% data variables.product.prodname_pages %} e o site do {% data variables.product.prodname_pages %} atualmente publicado terá a publicação cancelada. Para obter mais informações, consulte "[Transferir um repositório](/articles/transferring-a-repository)". + +### Leia mais + +- "[Solucionar problemas de domínios personalizados e do {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md new file mode 100644 index 0000000000..dfe12e48ec --- /dev/null +++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -0,0 +1,23 @@ +--- +title: Configurar um domínio personalizado para o site do GitHub Pages +intro: 'É possível personalizar o nome de domínio do site do {% 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 + - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Páginas +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000..0d2f7b2937 --- /dev/null +++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,121 @@ +--- +title: Gerenciar um domínio personalizado do seu site do GitHub Pages +intro: 'É possível definir ou atualizar determinados registros DNS e as configurações de repositório para apontar o domínio padrão do seu site do {% data variables.product.prodname_pages %} para um domínio 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 + - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Páginas +--- + +Pessoas com permissões de administrador para um repositório podem configurar um domínio personalizado de um site do {% data variables.product.prodname_pages %}. + +### Sobre a configuração de domínio personalizado + +Lembre-se de adicionar o domínio personalizado ao seu site do {% data variables.product.prodname_pages %} antes de configurar o domínio personalizado com o provedor DNS. Se você configurar o domínio personalizado com o provedor DNS sem adicioná-lo ao {% data variables.product.product_name %}, outra pessoa conseguirá hospedar um site em um dos seus subdomínios. + +{% windows %} + +O comando `dig`, que pode ser usado para verificar a configuração correta dos registros DNS, não está incluído no Windows. Antes de verificar se os registros DNS estão configurados corretamente, você deve instalar [BIND](https://www.isc.org/bind/). + +{% endwindows %} + +{% note %} + +**Observação:** as alterações no DNS podem levar até 24 horas para serem propagadas. + +{% endnote %} + +### Configurando um subdomínio + +Para configurar um `www` ou um subdomínio personalizado como, por exemplo, `www.example.com` ou `blog.example.com`, você deve adicionar seu domínio nas configurações do repositório, o que criará um arquivo CNAME no repositório do seu site. Em seguida, configure um registro CNAME com seu provedor DNS. + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Em "Domínio personalizado,", digite o seu domínio personalizado e clique em **Salvar**. Isso criará um commit que adiciona um arquivo _CNAME_ à raiz da sua fonte de publicação. ![Botão Salvar domínio personalizado](/assets/images/help/pages/save-custom-subdomain.png) +5. Navegue até o provedor DNS e crie um registro `CNAME` que aponte seu subdomínio para o domínio padrão do seu site. Por exemplo, se você quiser usar o subdomínio `www.example.com` para seu site de usuário, crie um registro `CNAME` que aponte `www.example.com` para `.github.io`. Se você desejar usar o subdomínio `www.anotherexample.com` no seu site da organização, crie um registro `CNAME` que aponte `www. notherexample.com` para `.github.io`. O registro `CNAME` sempre deve apontar para `.github.io` ou `.github.io`, excluindo o nome do repositório. {% 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 o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _WW.EXAMPLE.COM_ pelo seu subdomínio. +```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 %} + +### Configurando um domínio apex + +To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider. + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)." + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Em "Domínio personalizado,", digite o seu domínio personalizado e clique em **Salvar**. Isso criará um commit que adiciona um arquivo _CNAME_ à raiz da sua fonte de publicação. ![Botão Salvar domínio personalizado](/assets/images/help/pages/save-custom-apex-domain.png) +5. Navegue até o provedor DNS e crie um registro `ALIAS`, `ANAME` ou `A`. {% data reusables.pages.contact-dns-provider %} + - Para criar um registro `ALIAS` ou `ANAME`, aponte o domínio apex para o domínio padrão do seu site. {% data reusables.pages.default-domain-information %} + - To create `A` records, point your apex domain to the IP addresses for {% 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 o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _WW.EXAMPLE.COM_ pelo domínio apex. Confirme que os resultados correspondem aos endereços IP do {% data variables.product.prodname_pages %} acima. + ```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 %} + +### Configuring an apex domain and the `www` subdomain variant + +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. + +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." + +After you configure the apex domain, you must to configure a CNAME record with your DNS provider. + +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. +```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 +``` +### Removing a custom domain + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain," click **Remove**. ![Botão Salvar domínio personalizado](/assets/images/help/pages/remove-custom-domain.png) + +### Leia mais + +- "[Solucionar problemas de domínios personalizados e do {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..1fa90e0c7e --- /dev/null +++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,65 @@ +--- +title: Solucionar problemas de domínios personalizados e do GitHub Pages +intro: 'Você pode verificar os erros comuns para resolver problemas com domínios personalizados ou HTTPS no seu site do {% 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 + - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Páginas +--- + +### Erros _CNAME_ + +Os domínios personalizados são armazenados em um arquivo _CNAME_ na raiz da fonte de publicação que pode ser adicionado ou atualizado manualmente ou por meio das configurações do repositório. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +Para que o site seja renderizado no domínio correto, verifique se o arquivo _CNAME_ ainda existe no repositório. Por exemplo, muitos geradores de site estáticos fazem push forçado para o repositório, o que pode substituir o arquivo _CNAME_ que foi adicionado ao repositório quando você configurou o domínio personalizado. Se você criar o site localmente e fizer push dos arquivos gerados para o {% data variables.product.product_name %}, primeiro insira o commit que adicionou o arquivo _CNAME_ ao repositório local, para que o arquivo seja incluído na criação. + +Em seguida, verifique se o arquivo _CNAME_ está formatado corretamente. + +- O nome de arquivo _CNAME_ deve estar todo em letras maiúsculas. +- O arquivo _CNAME_ só pode conter um domínio. Para apontar vários domínios para o site, é preciso configurar um redirecionamento por meio do provedor DNS. +- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`. +- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. Por exemplo, se o arquivo _CNAME_ de outro repositório contiver `example.com`, você não poderá usar `example.com` no arquivo _CNAME_ para o repositório. + +### Configuração incorreta do DNS + +Se você tiver problemas para apontar o domínio padrão do site para o domínio personalizado, entre em contato com seu provedor DNS. + +Você também pode testar se os registros DNS do domínio personalizado estão configurados corretamente. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +### Nomes de domínios personalizados que não são compatíveis + +Se o seu domínio personalizado não for compatível, talvez você precise alterá-lo para um que tenha suporte. Você também pode entrar em contato com seu provedor DNS para ver se ele oferece serviços de encaminhamento para nomes de domínio. + +Verifique se o seu site não: +- Usa mais de um domínio apex. Por exemplo, `example.com` e `anotherexample.com`. +- Usa mais de um subdomínio `www`. Por exemplo, `www.example.com` e `www.anotherexample.com`. +- Usa um domínio apex e um subdomínio personalizado. Por exemplo, `example.com` e `docs.example.com`. + + The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)". + +{% data reusables.pages.wildcard-dns-warning %} + +Para obter uma lista de domínios personalizados compatíveis, consulte "[Sobre domínios personalizados e o {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)". + +### Erros de HTTPS + +É possível acessar por HTTPS os sites do {% data variables.product.prodname_pages %} que usem domínios personalizados e estejam corretamente configurados com registros DNS _CNAME_, `ALIAS`, `ANAME` ou `A`. Para obter mais informações, consulte "[Proteger seu site do {% data variables.product.prodname_pages %} com HTTPS](/articles/securing-your-github-pages-site-with-https)". + +Depois que você configurar seu domínio personalizado, pode levar até uma hora para o seu site ser disponibilizado por HTTPS. Após a atualização das configurações DNS existentes, talvez seja necessário remover o domínio personalizado e tornar a adicioná-lo ao repositório do site para acionar o processo de habilitação do HTTPS. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". + +Se você estiver usando registros CAA (Certification Authority Authorization, Autorização da autoridade de certificação), pelo menos um deles deverá ter o valor `letsencrypt.org` para que o seu site possa ser acessado por HTTPS. Para obter mais informações, consulte "[Autorização da autoridade de certificação (CAA)](https://letsencrypt.org/docs/caa/)" na documentação de Let's Encrypt. + +### Formatação de URL no Linux + +Se a URL para o seu site incluir um nome de usuário ou de organização que começa ou termina com um traço ou contiver traços consecutivos, as pessoas que navegam com Linux receberão um erro de servidor quando tentarem visitar o site. Para corrigir isso, remova caracteres não alfanuméricos do seu nome de usuário do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Alterar seu nome de usuário do {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username/)". + +### Cache do navegador + +Se você tiver alterado ou removido recentemente seu domínio personalizado e não conseguir acessar a nova URL no navegador, talvez precise limpar o cache do navegador para alcançar a nova URL. Para obter mais informações sobre limpeza do cache, consulte a documentação do navegador. diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000..259d7e8a7e --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -0,0 +1,150 @@ +--- +title: Sobre o GitHub Pages +intro: 'Você pode usar o {% data variables.product.prodname_pages %} para hospedar um site sobre si mesmo, sua organização ou seu projeto diretamente de um repositório do {% 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 + - /github/working-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +### Sobre o {% data variables.product.prodname_pages %} + +O {% data variables.product.prodname_pages %} é um serviço de hospedagem de site estático que usa arquivos HTML, CSS e JavaScript diretamente de um repositório no {% data variables.product.product_name %} e, como opção, executa os arquivos por meio de um processo e publica um site. Você pode ver exemplos de sites do {% data variables.product.prodname_pages %} na [coleção de exemplos do {% data variables.product.prodname_pages %}](https://github.com/collections/github-pages-examples). + +{% if currentVersion == "free-pro-team@latest" %} +É possível hospedar seu site no domínio `github.io` do {% data variables.product.prodname_dotcom %} ou no seu próprio domínio personalizado. Para obter mais informações, consulte "[Usar um domínio personalizado com o {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)". +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} Para obter mais informações, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +Para começar, consulte "[Criar um site do {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)". + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +Os proprietários da organização podem desabilitar a publicação de sites do {% data variables.product.prodname_pages %} nos repositórios da organização. Para obter mais informações, consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". +{% endif %} + +### Tipos de site do {% data variables.product.prodname_pages %} + +Há três tipos de site do {% data variables.product.prodname_pages %}: projeto, usuário e organização. Os sites de projeto são conectados a um projeto específico hospedado no {% data variables.product.product_name %}, como uma biblioteca do JavaScript ou um conjunto de receitas. Os sites de usuário e organização são conectados a uma conta específica do {% data variables.product.product_name %}. + +Para publicar um site de usuário, você deve criar um repositório pertencente à sua conta de usuário denominada {% if currentVersion == "free-pro-team@latest" %}`. ithub.io`{% else %}`.`{% endif %}. Para publicar um site da organização, você deve criar um repositório pertencente a uma organização denominada {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}A menos que você esteja usando um domínio personalizado, os sites de usuário e organização estarão disponíveis em `http(s)://.github.io` ou `http(s)://.github.io`.{% elsif currentVersion == "github-ae@latest" %}Sites de usuário e organização estão disponíveis em `http(s)://pages./` ou `http(s)://pages./`.{% endif %} + +Os arquivos de origem de um site de projeto são armazenados no mesmo repositório que o respectivo projeto. {% if currentVersion == "free-pro-team@latest" %}A menos que você esteja usando um domínio personalizado, os sites de projeto estão disponíveis em `http(s)://.github.io/` ou `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Os sites de projeto estão disponíveis em `http(s)://pages.///` ou `http(s)://pages.///`.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Se você publicar seu site em particularmente, a URL do seu site será diferente. Para obter mais informações, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +Para obter mais informações sobre como os domínios personalizados afetam o URL do seu site, consulte "[Sobre domínios personalizados e {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". +{% endif %} + +Você só pode criar um site de usuário ou organização para cada conta em {% data variables.product.product_name %}. Os sites de projeto, sejam eles de uma conta de organização ou de usuário, são ilimitados. + +{% if enterpriseServerVersions contains currentVersion %} +O URL onde o site estará disponível depende da habilitação do isolamento do subdomínio para o {% data variables.product.product_location %}. + +| Tipo de site | Isolamento de subdomínio habilitado | Isolamento de subdomínio desabilitado | +| ------------ | ----------------------------------- | ------------------------------------- | +| | | | + Usuário | + +`http(s)://pages./` | `http(s):///pages/` | Organization | `http(s)://pages./` | `http(s):///pages/` | Site do projeto pertencente a uma conta do usuário | `http(s)://pages.///` | `http(s):///pages///` Site do projeto pertencente a uma conta da organização | `http(s)://pages.///` | `http(s):///pages///` + +Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" ou entre em contato com o administrador do site. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Observação:** os repositórios que usam o esquema de nomenclatura `.github.com` herdado ainda são publicados, mas os visitantes serão redirecionados de `http(s)://.github.com` para `http(s)://.github.io`. Se ambos os repositórios, `.github.com` e `.github.io` existirem, somente o repositório `.github.io` será publicado. + +{% endnote %} +{% endif %} + +### Publicar fontes para sites do {% data variables.product.prodname_pages %} + +A fonte de publicação do seu site de {% data variables.product.prodname_pages %} é o branch e a pasta onde os arquivos de origem do seu site são armazenados. + +{% 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" %} + +Se existir uma fonte de publicação padrão no repositório, o {% data variables.product.prodname_pages %} publicará automaticamente um site a partir dessa fonte. A fonte de publicação padrão para sites de usuário e organização é a raiz do branch-padrão do repositório. A fonte de publicação padrão para sites de projeto é a raiz do branch `gh-pages`. + +Se você desejar manter os arquivos de origem do seu site em outro local, você poderá alterar a fonte de publicação do seu site. É possível publicar o site a partir de qualquer branch no repositório, a partir da raiz do repositório nesse branch, `/` ou a partir da pasta `/docs` nesse branch. Para obter mais informações, consulte "[Configurar uma fonte de publicação para seu site do {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". + +Se você escolher a pasta `/docs` de qualquer branch como fonte de publicação, {% data variables.product.prodname_pages %} lerá tudo para publicar o seu site{% if currentVersion == "free-pro-team@latest" %}, incluindo o arquivo _CNAME_ ,{% endif %} da pasta `/docs` .{% if currentVersion == "free-pro-team@latest" %} Por exemplo, quando você editar o seu domínio personalizado através das configurações {% data variables.product.prodname_pages %}, o domínio personalizado escreverá em `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} + +{% else %} + +A fonte de publicação padrão para sites de usuário e organização é o branch `master`. Se o repositório para o site de usuário ou organização tiver um branch `master`, seu site será publicado automaticamente a partir desse branch. Não é possível escolher uma fonte de publicação diferente para sites de usuário ou organização. + +A fonte de publicação padrão para um site de projeto é o branch `gh-pages`. Se o repositório para seu site de projeto tiver um branch `gh-pages`, seu site será publicado automaticamente a partir desse branch. + +Os sites de projeto também podem ser publicados do branch `master` ou de uma pasta `/docs` no branch `master`. Para publicar o site de uma dessas fontes, é preciso configurar uma fonte de publicação diferente. Para obter mais informações, consulte "[Configurar uma fonte de publicação para seu site do {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". + +Se você escolher a pasta `/docs` do branch `master` como fonte de publicação, {% data variables.product.prodname_pages %} lerá tudo para publicar o seu site{% if currentVersion == "free-pro-team@latest" %}, incluindo o arquivo _CNAME_ {% endif %} da pasta `/docs`.{% if currentVersion == "free-pro-team@latest" %} Por exemplo, ao editar o seu domínio personalizado através das configurações de {% data variables.product.prodname_pages %}, o domínio personalizado escreverá a `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} + +Você não pode publicar seu site de projeto de qualquer outro branch, mesmo que o branch padrão não seja `master` ou `gh-pages`. + +{% endif %} + +### Geradores de site estáticos + +O {% data variables.product.prodname_pages %} publica qualquer arquivo estático do qual você faz push no repositório. É possível criar seus próprios arquivos estáticos ou usar um gerador de site estático para que ele crie o site para você. Também pode personalizar seu próprio processo de criação localmente ou em outro servidor. É recomendável usar o Jekyll, um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %} e um processo de compilação simplificado. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_pages %} e o JJekyll](/articles/about-github-pages-and-jekyll)". + +O {% data variables.product.prodname_pages %} usará o Jekyll para criar seu site por padrão. Se quiser usar um gerador de site estático diferente do Jekyll, desabilite o processo de compilação do Jekyll criando um arquivo vazio chamado `.nojekyll` na raiz da fonte de publicação e siga as instruções do gerador de site estático para criar seu site localmente. + +O {% data variables.product.prodname_pages %} não aceita linguagens de servidor como PHP, Ruby ou Python. + +### Diretrizes para usar o {% data variables.product.prodname_pages %} + +{% if currentVersion == "free-pro-team@latest" %} +- Os sites do {% data variables.product.prodname_pages %} criados após 15 de junho e que usam domínios do `github.io` são disponibilizados por HTTPS. Se você criou seu site ante de 15 de junho de 2016, é possível habilitar o suporte ao HTTPS para tráfego no seu site. Para obter mais informações, consulte "[Proteger seu {% data variables.product.prodname_pages %} com HTTPS](/articles/securing-your-github-pages-site-with-https)". +- {% data reusables.pages.no_sensitive_data_pages %} +- O uso que você faz do {% data variables.product.prodname_pages %} está sujeito aos [Termos de serviço do GitHub](/articles/github-terms-of-service/), inclusive a proibição de revenda. + +#### Limites de uso +{% endif %} +Os sites do {% data variables.product.prodname_pages %} estão sujeitos ao seguintes limites de uso: + + - Repositórios de origem de {% data variables.product.prodname_pages %} têm um limite recomendado de 1 GB.{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Qual é a minha cota de disco?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} + - Os sites do {% data variables.product.prodname_pages %} publicados não podem ter mais de 1 GB. +{% if currentVersion == "free-pro-team@latest" %} + - Sites de {% data variables.product.prodname_pages %} têm um limite de banda larga *flexível* de 100 GB por mês. + - Os sites do {% data variables.product.prodname_pages %} têm um limite *flexível* de 10 compilações por hora. + +Se o seu site exceder essas cotas de uso, talvez não possamos atender a ele ou você receba um e-mail formal do {% data variables.contact.contact_support %} sugerindo estratégias para reduzir o impacto do site em nossos servidores, como colocar uma rede de distribuição de conteúdo (CDN, Content Distribution Network) de terceiros na frente do site, usar outros recursos do {% data variables.product.prodname_dotcom %}, como versões, ou migrar para outro serviço de hospedagem que possa atender melhor às suas necessidades. + +#### Usos proibidos + +O {% data variables.product.prodname_pages %} não foi projetado e nem tem permissão para ser usado como um serviço de hospedagem gratuita na web, capaz de administrar sua empresa online, seu site de comércio eletrônico ou qualquer outro site desenvolvido principalmente para facilitar transações comerciais ou fornecer software comercial como um serviço (SaaS). + +In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. Para uma lista de usos proibidos, consulte "[Termos Adicionais do Produto de {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)". +{% endif %} + +### Tipos de MIME no {% data variables.product.prodname_pages %} + +Um tipo de MIME é um header que um servidor envia a um navegador, fornecendo informações sobre a natureza e o formato dos arquivos que o navegador solicitou. O {% data variables.product.prodname_pages %} aceita mais de 750 tipos de MIME entre milhares de extensões de arquivo. A lista de tipos de MIME compatíveis é gerada do [projeto mime-db](https://github.com/jshttp/mime-db). + +Embora não seja possível especificar tipos de MIME personalizados por arquivo ou repositório, você pode adicionar ou modificar tipos de MIME para uso no {% data variables.product.prodname_pages %}. Para obter mais informações, consulte [as diretrizes de contribuição do mime-db](https://github.com/jshttp/mime-db#adding-custom-media-types). + +### Leia mais + +- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) em {% data variables.product.prodname_learning %} +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000..d613a49c90 --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,46 @@ +--- +title: Adicionar um tema ao site do GitHub Pages com o seletor de temas +intro: 'É possível adicionar um tema ao site do {% data variables.product.prodname_pages %} para personalizar a aparência dele.' +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Páginas +--- + +Pessoas com permissões de administrador para um repositório podem usar o seletor de temas para adicionar um tema a um site do {% data variables.product.prodname_pages %}. + +### Sobre o seletor de temas + +O seletor de temas adiciona um tema do Jekyll ao repositório. Para obter mais informações sobre o Jekyll, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll)". + +O funcionamento do seletor de temas depende de o repositório ser público ou privado. + - Se o {% data variables.product.prodname_pages %} já estiver habilitado para o repositório, o seletor de temas adicionará o tema à fonte de publicação atual. + - Se o repositório for público e o {% data variables.product.prodname_pages %} estiver desabilitado para ele, o uso do seletor de temas habilitará o {% data variables.product.prodname_pages %} e definirá o branch-padrão como fonte de publicação. + - Se o repositório for privado e o {% data variables.product.prodname_pages %} estiver desabilitado para ele, será preciso habilitar o {% data variables.product.prodname_pages %} definindo uma fonte de publicação para poder usar o seletor de temas. + +Para obter mais informações sobre fontes de publicação, consulte "[Sobre o {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". + +Caso você tenha adicionado manualmente um tema do Jekyll ao repositório no passado, esses arquivos poderão ser aplicados mesmo depois que você usar o seletor de temas. Para evitar conflitos, remova todas as pastas e arquivos de temas adicionados manualmente antes de usar o seletor de temas. 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)". + +### Adicionar um tema com o seletor de temas + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. No "{% data variables.product.prodname_pages %}", clique em **Escolher um tema** ou **Alterar tema**. ![Botão Choose a theme (Escolher um tema)](/assets/images/help/pages/choose-a-theme.png) +4. No topo da página, clique no tema desejado e depois em **Selecionar tema**. ![Opções de tema e botão Select theme (Selecionar tema)](/assets/images/help/pages/select-theme.png) +5. Talvez seja necessário editar o arquivo *README.md* do site. + - Para editá-lo mais tarde, clique em **Cancelar**. ![Link Cancel (Cancelar) ao editar um arquivo](/assets/images/help/pages/cancel-edit.png) + - Para editá-lo agora, consulte "[Editar arquivos no repositório](/articles/editing-files-in-your-repository/)". + +O tema escolhido será aplicado automaticamente aos arquivos markdown no repositório. Para aplicar o tema a arquivos HTML no repositório, é preciso adicionar a página inicial YAML que especifica um layout para cada arquivo. Para obter mais informações, consulte "[Página inicial](https://jekyllrb.com/docs/front-matter/)" no site do Jekyll. + +### Leia mais + +- [Temas](https://jekyllrb.com/docs/themes/) no site do Jekyll diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..17dbdc50aa --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: Alterar a visibilidade do site do GitHub Pages +intro: 'Você pode gerenciar o controle de acesso no seu site de projeto publicando o site publicamente ou privadamente.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: As pessoas com permissões de administrador em um repositório podem alterar a visibilidade de um site de {% data variables.product.prodname_pages %} +redirect_from: + - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site +--- + +### Sobre controle de acesso para sites de {% data variables.product.prodname_pages %} + +Se o seu site de projeto for publicado de um repositório privado ou interno, pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, você poderá gerenciar o controle de acesso para o site. Com controle de acesso, você pode optar por publicar o site publicamente para qualquer pessoa na internet ou em particular para pessoas com acesso de leitura ao seu repositório. Um site publicado de forma privada pode ser usado para compartilhar sua documentação interna ou base de conhecimento com integrantes da sua empresa. Você não pode gerenciar o controle de acesso para um site da organização. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Os sites publicados em particular estão disponíveis em um subdomínio diferente dos sites publicados em modo público. Isso garante que seu site do {% data variables.product.prodname_pages %} esteja seguro a partir do momento em que for publicado: + +- Protegemos automaticamente todos os subdomínios de `*.pages.github.io` com um certificado TLS e aplicamos HSTS para garantir que os navegadores sempre servem a página por meio de HTTPS. +- Usamos um subdomínio único para a página privada para garantir que outros repositórios na organização não possam publicar conteúdo na mesma origem da página privada. Isto protege sua página privada contra "[cookie tossing"](https://github.blog/2013-04-09-yummy-cookies-across-domains/). É por isso que também não hospedamos sites de {% data variables.product.prodname_pages %} no domínio do `github.com`. + +Você pode visualizar o subdomínio único do site na aba páginas das configurações do seu repositório. Se você estiver usando um gerador de site estático configurado para criar o site com o nome do repositório como um caminho, talvez seja necessário atualizar as configurações para o gerador do site estático ao alterar o site para privado. Para obter mais informações, consulte "[Configurar o Jekyll no seu site de {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" ou a documentação para o gerador do seu site estático. + +Para usar um domínio mais curto e mais memorável no seu site privado de {% data variables.product.prodname_pages %}, você pode configurar um domínio personalizado. Para obter mais informações, consulte "[Configurar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site)"" + +### Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Em "{% data variables.product.prodname_pages %}", selecione o ** visibilidade de {% data variables.product.prodname_pages %}** no menu suspenso e, em seguida, clique em uma visibilidade. ![Menu suspenso para escolher uma visibilidade para o seu site](/assets/images/help/pages/public-or-private-visibility.png) +4. Para ver seu site publicado, em "{% data variables.product.prodname_pages %}", clique na URL do seu site. ![URL do seu site publicado em modo particular](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000..32c8773f5f --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,38 @@ +--- +title: Configurar uma fonte de publicação para o site do GitHub Pages +intro: 'Se você usar a fonte de publicação padrão do site do {% data variables.product.prodname_pages %}, seu site será publicado automaticamente. Você também pode optar por publicar o seu{% if currentVersion ver_lt "enterprise-server@3.0" %} site do projeto{% endif %} a partir de um branch ou pasta diferente.' +redirect_from: + - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-your-github-pages-site + - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'Pessoas com permissões de administrador ou mantenedor para um repositório podem configurar uma fonte de publicação para um site do {% data variables.product.prodname_pages %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +Para obter mais informações sobre fontes de publicação, consulte "[Sobre o {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". + +### Escolher uma fonte de publicação + +Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} 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 %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +3. Em "{% data variables.product.prodname_pages %}", use o menu suspenso **Nenhum** ou **Branch** e selecione uma fonte de publicação. ![Menu suspenso para selecionar uma fonte de publicação](/assets/images/help/pages/publishing-source-drop-down.png) +4. Opcionalmente, use o menu suspenso para selecionar uma pasta para sua fonte de publicação. ![Menu suspenso para selecionar uma pasta para a fonte de publicação](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. Clique em **Salvar**. ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %} +3. No "{% data variables.product.prodname_pages %}", use o menu suspenso **Source** (Fonte) e selecione uma fonte de publicação. ![Menu suspenso para selecionar uma fonte de publicação](/assets/images/help/pages/publishing-source-drop-down.png) +{% endif %} + +### Solucionar problemas de publicação com o site do {% data variables.product.prodname_pages %} + +{% data reusables.pages.admin-must-push %} + +Se você escolher a pasta `docs` em {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}qualquer branch{% else %}ou `branch mestre`{% endif %} como fonte de publicação e eliminar a pasta `/docs` do branch do repositório, seu site não será criado e você receberá uma mensagem de erro de criação de página referente a uma pasta `/docs` ausente. Para obter informações, consulte [Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)". diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000..0f231307b7 --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Criar uma página 404 personalizada para o site do GitHub Pages +intro: Você pode exibir uma página de erro 404 personalizada quando as pessoas tentam acessar páginas não existentes no seu site. +redirect_from: + - /articles/custom-404-pages/ + - /articles/creating-a-custom-404-page-for-your-github-pages-site + - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +{% data reusables.files.add-file %} +3. No campo de nome de arquivo, digite `404.html` ou `404.md`. ![Campo de nome de arquivo](/assets/images/help/pages/404-file-name.png) +4. Se você nomeou seu arquivo como `404.md`, adicione a seguinte página inicial YAML no começo do arquivo: + ```yaml + --- + permalink: /404.html + --- + ``` +5. Abaixo da página inicial YAML, se houver, adicione o conteúdo que deseja exibir na 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 %} + +### Leia mais + +- [Página inicial](http://jekyllrb.com/docs/frontmatter) na documentação do Jekyll diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000..ffc6876078 --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,63 @@ +--- +title: Criar um site do GitHub Pages +intro: 'É possível criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou 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 + - /github/working-with-github-pages/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Criar um repositório para seu site + +{% data reusables.pages.new-or-existing-repo %} + +{% 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 %} + +### Criar seu site + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.decide-publishing-source %} +3. Se a fonte de publicação que você escolheu já existe, navegue até ela. Caso contrário, crie a fonte de publicação. +4. Na raiz da fonte de publicação, crie um novo arquivo chamado `index.md` com o conteúdo que você deseja exibir na página principal do seu site. +{% data reusables.pages.configure-publishing-source %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Próximas etapas + +Você pode adicionar mais páginas ao seu site criando novos arquivos. Cada arquivo ficará disponível no site na mesma estrutura de diretórios que a fonte de publicação. Por exemplo, se a fonte de publicação para o seu site de projeto for o branch `gh-pages`, e você criar um novo arquivo chamado `/about/contact-us.md` no branch `gh-pages`, o arquivo estará disponível em {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. + +Também é possível adicionar um tema para personalizar a aparência do site. Para mais informações consulte {% if currentVersion == "free-pro-team@latest" %}"[Adicionar um tema ao site de {% data variables.product.prodname_pages %} com o seletor de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adicionar um tema ao site de {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." + +Para personalizar seu site ainda mais, você pode usar o Jekyll, um gerador de site estático com suporte integrado para o {% data variables.product.prodname_pages %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_pages %} e o JJekyll](/articles/about-github-pages-and-jekyll)". + +### Leia mais + +- "[Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" +- "[Criar e excluir branches no repositório](/articles/creating-and-deleting-branches-within-your-repository)" +- "[Criar arquivos](/articles/creating-new-files)" diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md new file mode 100644 index 0000000000..f79aba446f --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md @@ -0,0 +1,26 @@ +--- +title: Indrodução ao GitHub Pages +intro: 'Você pode configurar um site básico do {% data variables.product.prodname_pages %} para você mesmo, sua organização ou seu projeto.' +redirect_from: + - /categories/github-pages-basics + - /articles/additional-customizations-for-github-pages/ + - /articles/getting-started-with-github-pages + - /github/working-with-github-pages/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +{% 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 /changing-the-visibility-of-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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000..ba7ff527c2 --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,55 @@ +--- +title: Proteger o site GitHub Pages com HTTPS +intro: 'O HTTPS adiciona uma camada de criptografia que impede outras pessoas de interceptar ou adulterar o tráfego do seu site. Você pode exigir HTTPS para seu site do {% data variables.product.prodname_pages %} para redirecionar de forma transparente todas as solicitações HTTP para HTTPS.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/securing-your-github-pages-site-with-https + - /github/working-with-github-pages/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +topics: + - Páginas +--- + +Pessoas com permissões de administrador para um repositório podem exigir HTTPS para um site do {% data variables.product.prodname_pages %}. + +### Sobre HTTPS e o {% data variables.product.prodname_pages %} + +Todos os sites do {% data variables.product.prodname_pages %}, incluindo os sites corretamente configurados com um domínio personalizado, permitem exigir HTTPS e HTTPS. Para obter mais informações sobre domínios personalizados, consulte "[Sobre domínios personalizados e o {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" e "[Solucionar problemas de domínios personalizados e do {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)". + +{% data reusables.pages.no_sensitive_data_pages %} + +{% data reusables.pages.private_pages_are_public_warning %} + +### Exigir HTTPS para o site do {% data variables.product.prodname_pages %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. No "{% data variables.product.prodname_pages %}," selecione **Enforce HTTPS** (Exigir HTTPS). ![Caixa de seleção Enforce HTTPS (Exigir HTTPS)](/assets/images/help/pages/enforce-https-checkbox.png) + +### Resolver problemas com conteúdo misto + +Se você habilitar HTTPS para seu site do {% data variables.product.prodname_pages %}, mas o HTML do site ainda fizer referência a imagens, CSS ou JavaScript por HTTP, significa que seu site está fornecendo *conteúdo misto*. O fornecimento de conteúdo misto pode tornar o site menos seguro e causar problemas no carregamento de arquivos. + +Para remover conteúdo misto do site, verifique se todos os arquivos são entregues via HTTPS alterando `http://` para `https://` no HTML do site. + +Os ativos geralmente são encontrados nos seguintes locais: +- Caso seu site utilize o Jekyll, provavelmente os arquivos HTML estarão na pasta *_layouts*. +- O CSS fica na seção `` do arquivo HTML. +- O JavaScript geralmente está na seção `` ou um pouco antes da tag de encerramento ``. +- As imagens geralmente estão na seção ``. + +{% tip %} + +**Dica:** se você não conseguir encontrar seus ativos nos arquivos de origem do site, tente pesquisar neles por `http` no editor de texto ou no {% data variables.product.product_name %}. + +{% endtip %} + +#### Exemplos de ativos referenciados em um arquivo HTML + +| Tipo de ativo | HTTP | HTTPS | +|:-------------:|:--------------------------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------:| +| CSS | `` | `` | +| JavaScript | `` | `` | +| Imagem | `Logotipo` | `Logotipo` | diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000..0c7aec1d2d --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Cancelar a publicação de um site do GitHub Pages +intro: 'Você pode cancelar a publicação do seu site de {% data variables.product.prodname_pages %} para que não fique mais disponível.' +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 + - /github/working-with-github-pages/unpublishing-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'As pessoas com permissões de administrador para um repositório podem cancelar a publicação de um site do {% data variables.product.prodname_pages %}.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +### Cancelar a publicação de um site de projeto + +{% data reusables.repositories.navigate-to-repo %} +2. Se existir um branch `gh-pages` no repositório, exclua o branch `gh-pages`. Para obter mais informações, consulte "[Criar e excluir branches em seu repositório](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)". +3. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. No "{% data variables.product.prodname_pages %}", use o menu suspenso **Source** (Fonte) e selecione **None** (Nenhuma). ![Menu suspenso para selecionar uma fonte de publicação](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} + +### Cancelar a publicação de um site de usuário ou organização + +{% data reusables.repositories.navigate-to-repo %} +2. Exclua o branch que você está usando como fonte de publicação ou exclua todo o repositório. Para obter mais informações, consulte "[Criar e excluir branches no repositório](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" e "[Excluir um repositório](/articles/deleting-a-repository)". +{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000..8722942e34 --- /dev/null +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,24 @@ +--- +title: Usar submódulos com o GitHub Pages +intro: 'Você pode usar submódulos com o {% data variables.product.prodname_pages %} para incluir outros projetos no código do seu site.' +redirect_from: + - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-github-pages + - /github/working-with-github-pages/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - Páginas +--- + +Se o repositório do seu site do {% data variables.product.prodname_pages %} contiver submódulos, o conteúdo dele será inserido automaticamente quando o site for criado. + +Só é possível usar submódulos que apontem para repositórios públicos, porque o servidor do {% data variables.product.prodname_pages %} não pode acessar repositórios privados. + +Use a URL somente leitura `https://` para os submódulos, inclusive os aninhados. Essa alteração pode ser feita no arquivo _.gitmodules_. + +### Leia mais + +- "[Ferramentas Git - Submódulos](https://git-scm.com/book/en/Git-Tools-Submodules)" no livro _Pro Git_ +- "[Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/pt-BR/content/pages/index.md b/translations/pt-BR/content/pages/index.md new file mode 100644 index 0000000000..188bfab3b2 --- /dev/null +++ b/translations/pt-BR/content/pages/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages Documentation +shortTitle: GitHub Pages +intro: 'Você pode criar um site diretamente de um repositório do {% 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 + - /github/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +{% link_with_intro /getting-started-with-github-pages %} +{% link_with_intro /setting-up-a-github-pages-site-with-jekyll %} +{% link_with_intro /configuring-a-custom-domain-for-your-github-pages-site %} \ No newline at end of file diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000..d049d204dd --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -0,0 +1,131 @@ +--- +title: Sobre o GitHub Pages e Jekyll +intro: 'Jekyll é um gerador de site estático com suporte 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 + - /github/working-with-github-pages/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +### Sobre o Jekyll + +O Jekyll é um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %} e um processo de compilação simplificado. O Jekyll usa arquivos Markdown e HTML, além de criar um site estático completo com base na sua escolha de layouts. O Jekyll aceita Markdown e Liquid, uma linguagem de modelagem que carrega conteúdo dinâmico no site. Para obter mais informações, consulte [Jekyll](https://jekyllrb.com/). + +O Jekyll não é oficialmente compatível com o Windows. Para obter mais informações, consulte "[Jekyll no Windows](http://jekyllrb.com/docs/windows/#installation)" na documentação do Jekyll. + +É recomendável usar o Jekyll com o {% data variables.product.prodname_pages %}. Se preferir, você pode usar outros geradores de site estáticos ou personalizar seu próprio processo de compilação localmente ou em outro servidor. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)". + +### Configurar o Jekyll em seu site do {% data variables.product.prodname_pages %} + +É possível configurar a maioria das definições do Jekyll, como o tema e os plugins do seu site, editando o arquivo *_config.yml*. Para obter mais informações, consulte "[Configuração](https://jekyllrb.com/docs/configuration/)" na documentação do Jekyll. + +Algumas definições de configuração não podem ser alteradas para sites do {% data variables.product.prodname_pages %}. + +```yaml +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 +``` + +Por padrão, o Jekyll não cria arquivos nem pastas que: +- estão localizadas em uma pasta chamada `/node_modules` ou `/vendor` +- start with `_`, `.`, or `#` +- terminam com `~` +- são excluídos pela configuração `exclude` em seu arquivo de configuração + +Se quiser que o Jekyll processe algum desses arquivos, você poderá usar a configuração `includes` no arquivo de configuração. + +### Material inicial + +{% data reusables.pages.about-front-matter %} + +Você pode adicionar `site.github` a uma publicação ou página para incluir metadados de referências de repositório ao seu site. Para obter mais informações, consulte "[Usar `site.github`](https://jekyll.github.io/github-metadata/site.github/)" na documentação de metadados do Jekyll. + +### Temas + +{% data reusables.pages.add-jekyll-theme %} Para obter mais informações, consulte "[Temas](https://jekyllrb.com/docs/themes/)" na documentação do Jekyll. + +{% if currentVersion == "free-pro-team@latest" %} +É possível adicionar um tema compatível ao seu site no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Temas compatíveis](https://pages.github.com/themes/)" no site do {% data variables.product.prodname_pages %} e "[Adicionar um tema ao seu site do {% data variables.product.prodname_pages %} com o seletor de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)". + +Para usar qualquer outro tema de código aberto do Jekyll hospedado em {% data variables.product.prodname_dotcom %}, você pode adicionar o tema manualmente.{% else %} Você pode adicionar um tema ao seu site manualmente.{% endif %} Para mais informações, consulte {% if currentVersion == "free-pro-team@latest" %} [temas hospedados em {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) e{% else %} "[Temas compatíveis](https://pages.github.com/themes/)no site de {% data variables.product.prodname_pages %} e{% endif %} "[Adicionar um tema ao seu site de {% data variables.product.prodname_pages %} usando Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". + +Você pode substituir qualquer um dos padrões do seu tema editando os arquivos do tema. Para obter mais informações, consulte a documentação do seu tema e "[Substituir padrões do tema](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" na documentação do Jekyll. + +### Plugins + +Você pode baixar ou criar plugins do Jekyll para ampliar a funcionalidade do Jekyll em seu site. Por exemplo, o plugin [jemoji](https://github.com/jekyll/jemoji) permite usar emoji em estilo do {% data variables.product.prodname_dotcom %} em qualquer página do seu site da mesma forma que você faria no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Plugins](https://jekyllrb.com/docs/plugins/)" na documentação do Jekyll. + +O {% data variables.product.prodname_pages %} usa plugins que são habilitados por padrão e não podem ser desabilitados: +- [`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) + +Você pode habilitar plugins adicionais incluindo a gem do plugin à configuração `plugins` em seu arquivo *_config.yml*. Para obter mais informações, consulte "[Configuração](https://jekyllrb.com/docs/configuration/)" na documentação do Jekyll. + +Para obter uma lista de plugins compatíveis, consulte "[Versões de dependência](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}. Para obter informações de uso para um plugin específico, consulte a documentação do plugin. + +{% tip %} + +**Dica:** você pode ter certeza de que está usando a versão mais recente de todos os plugins mantendo o gem do {% data variables.product.prodname_pages %} atualizado. Para obter mais informações, consulte "[Testar o site do GitHub Pages localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" e "[Versões de dependência](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}. + +{% endtip %} + +O {% data variables.product.prodname_pages %} não pode criar sites usando plugins incompatíveis. Se quiser usar plugins incompatíveis, gere seu site localmente e faça push dos arquivos estáticos do site no {% data variables.product.product_name %}. + +### Realce de sintaxe + +Para facilitar a leitura do seu site, trechos de código são destacados nos sites do {% data variables.product.prodname_pages %} da mesma maneira que são destacados no {% data variables.product.product_name %}. Para mais informações sobre destaque de sintaxe em {% data variables.product.product_name %}, consulte "[Criar e realçar blocos de código](/articles/creating-and-highlighting-code-blocks)". + +Por padrão, blocos de código no seu site serão destacados pelo Jekyll. O Jekyll usa o realçador [Rouge](https://github.com/jneen/rouge), que é compatível com [Pygments](http://pygments.org/). Se você especificar Pygments no arquivo *_config.yml*, Rouge será usado no lugar. O Jekyll não pode usar qualquer outro realçador de sintaxe, e você receberá um aviso de criação de página se especificar outro realçador de sintaxe no arquivo *_config.yml*. Para obter mais informações, consulte "[Sobre erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". + +Se quiser usar outro realçador, como `highlight.js`, você deverá desabilitar o realce da sintaxe do Jekyll atualizando o arquivo *_config.yml* do projeto. + +```yaml +kramdown: + syntax_highlighter_opts: + disable : true +``` + +Se o seu tema não incluir CSS para realce da sintaxe, você poderá gerar CSS de realce de sintaxe do {% data variables.product.prodname_dotcom %} e adicioná-lo ao arquivo `style.css` do projeto. + +```shell +$ rougify style github > style.css +``` + +### Criar site localmente + +{% data reusables.pages.test-locally %} diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..8020354352 --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,62 @@ +--- +title: Sobre erros de criação do Jekyll para sites do GitHub Pages +intro: 'Se o Jekyll encontrar um erro ao criar seu site do {% data variables.product.prodname_pages %} localmente ou no {% data variables.product.product_name %}, você receberá uma mensagem de erro com mais informações.' +redirect_from: + - /articles/viewing-jekyll-build-error-messages/ + - /articles/generic-jekyll-build-failures/ + - /articles/about-jekyll-build-errors-for-github-pages-sites + - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +### Sobre erros de criação do Jekyll + +Às vezes, {% data variables.product.prodname_pages %} não tentará criar seu site depois que você fizer push das alterações na fonte de publicação do site.{% if currentVersion == "free-pro-team@latest" %} +- A pessoa que fez push das alterações não verificou o endereço de e-mail dela. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)".{% endif %} +- Você está fazendo push com uma chave de implantação. Se desejar automatizar pushes para o repositório do seu site, você poderá configurar um usuário de máquina. Para obter mais informações, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys#machine-users)". +- Você está usando um serviço de CI que não está configurado para criar sua fonte de publicação. Por exemplo, Travis CI não criará o branch `gh-pages`, a menos que você adicione o branch a uma lista segura. Para obter mais informações, consulte "[Personalizar a criação](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" em Travis CI ou na documentação do seu serviço de CI. + +{% note %} + +**Observação:** podem ser necessários até 20 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}. + +{% endnote %} + +Se o Jekyll não tentar criar seu site e encontrar um erro, você receberá uma mensagem de erro de criação. Existem dois tipos principais de mensagens de erro de compilação do Jekyll. +- Uma mensagem "Page build warning" significa que sua criação foi concluída com êxito, mas talvez você precise fazer alterações para evitar problemas futuros. +- Uma mensagem "Page build failed" significa que sua criação falhou ao ser concluída. Se for possível para o Jekyll detectar um motivo para a falha, você verá uma mensagem de erro descritiva. + +Para obter informações sobre como solucionar problemas de erros de criação, consulte [Solução de problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)". + +### Exibir mensagens de erro de compilação do Jekyll + +É recomendável testar o site no local, o que permite ver mensagens de erro de criação na linha de comando e solucionar qualquer falha de criação antes de fazer push das alterações no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Testar seu site do {% data variables.product.prodname_pages %} localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". + +Quando você cria uma pull request para atualizar a fonte de publicação no {% data variables.product.product_name %}, é possível ver mensagens de erro de criação na guia **Checks** (Verificações) da pull request. Para obter mais informações, consulte "[Sobre verificações de status](/articles/about-status-checks)". + +Quando você fizer push das alterações na fonte de publicação no {% data variables.product.product_name %}, o {% data variables.product.prodname_pages %} tentará criar seu site. Se a criação falhar, você receberá um e-mail no seu endereço de e-mail principal. Você também receberá e-mails para avisos de criação. {% data reusables.pages.build-failure-email-server %} + +É possível ver falhas de criação (mas não os avisos de criação) para seu site no {% data variables.product.product_name %}, na guia **Settings** (Configurações) do repositório do site. + +Você pode configurar um serviço de terceiros, como o [Travis CI](https://travis-ci.org/), para exibir mensagens de erro após cada commit. + +1. Se você ainda não tiver, adicione um arquivo chamado _Gemfile_ na raiz da sua fonte de publicação, com o seguinte conteúdo: + ```ruby + source `https://rubygems.org` + gem `github-pages` + ``` + +2. Configure o repositório do site para o serviço de teste de sua escolha. Por exemplo, para usar [Travis CI](https://travis-ci.org/), adicione um arquivo chamado _.travis.yml_ na raiz da fonte de publicação, com o seguinte conteúdo: + ```yaml + language: ruby + rvm: + - 2.3 + script: "bundle exec jekyll build" + ``` +3. Talvez você precise ativar o repositório com o serviço de teste de terceiros. Para obter mais informações, consulte a documentação do seu serviço de teste. diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..eb4f7cab1b --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,71 @@ +--- +title: Adicionar um tema ao site do GitHub Pages usando Jekyll +intro: É possível personalizar o site do Jekyll adicionando e personalizando um 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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +Pessoas com permissões de gravação para um repositório podem adicionar um tema a um site do {% data variables.product.prodname_pages %} usando Jekyll. + +{% data reusables.pages.test-locally %} + +### Adicionar um tema + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +2. Navegue até *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Adicione uma nova linha ao arquivo para o nome do tema. + - Para usar um tema compatível, digite `theme: THEME-NAME`, substituindo _THEME-NAME_ pelo nome do tema, conforme mostrado no README do repositório do tema. Para obter uma lista de temas compatíveis, consulte "[Temas compatíveis](https://pages.github.com/themes/)" no site do {% data variables.product.prodname_pages %}. ![Tema compatível no arquivo de configuração](/assets/images/help/pages/add-theme-to-config-file.png) + - Para usar qualquer outro tema do Jekyll hospedado em {% data variables.product.prodname_dotcom %}, digite `remote_theme: THEME-NAME`, substituindo THEME-NAME pelo nome do tema, como mostrado no README do repositório do tema. ![Tema não compatível no arquivo de configuração](/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 o CSS do 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. Crie um novo arquivo chamado _/assets/css/style.scss_. +2. Adicione o seguinte conteúdo ao topo do arquivo: + ```scss + --- + --- + + @import "{{ site.theme }}"; + ``` +3. Adicione o CSS ou Sass personalizado (incluindo importações) que deseja imediatamente após a linha `@import`. + +### Personalizar o layout HTML do tema + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +1. No {% data variables.product.prodname_dotcom %}, navegue até o repositório de origem do tema. Por exemplo, o repositório de origem do Minima é https://github.com/jekyll/minima. +2. Na pasta *_layouts*, navegue até o arquivo _default.html_ do tema. +3. Copie o conteúdo do arquivo. +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +6. Crie um arquivo chamado *_layouts/default.html*. +7. Cole o conteúdo do layout padrão que você copiou anteriormente. +8. Personalize o layout como desejado. + +### Leia mais + +- "[Criar arquivos](/articles/creating-new-files)" diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..ffe279dcd5 --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,72 @@ +--- +title: Adicionar conteúdo ao site do GitHub Pages usando o Jekyll +intro: 'É possível adicionar uma nova página ou postagem ao site do Jekyll no {% data variables.product.prodname_pages %}.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/adding-content-to-your-github-pages-site-using-jekyll + - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +Pessoas com permissões de gravação para um repositório podem adicionar conteúdo a um site do {% data variables.product.prodname_pages %} usando o Jekyll. + +### Sobre conteúdo em sites do Jekyll + +Para poder adicionar conteúdo a um site do Jekyll no {% data variables.product.prodname_pages %}, você precisa criar o site do Jekyll. Para obter mais informações, consulte "[Criar um site do {% data variables.product.prodname_pages %} com o Jekyll](/articles/creating-a-github-pages-site-with-jekyll)". + +Os principais tipos de conteúdo para sites do Jekyll são páginas e postagens. As páginas se destinam a conteúdo autônomo que não está associado a uma data específica, como uma página "Sobre". O site padrão do Jekyll contém um arquivo chamado `about.md` que é renderizado como uma página no seu site em `YOUR-SITE-URL/about`. Você pode editar o conteúdo desse arquivo para personalizar a página "Sobre" e usá-la como um modelo para criar novas páginas. Para obter mais informações, consulte "[Páginas](https://jekyllrb.com/docs/pages/)" na documentação do Jekyll. + +As postagens são uma postagem de blog. O site padrão do Jekyll contém um diretório chamado `_posts` que contém um arquivo de postagem padrão. Você pode editar o conteúdo dessa postagem e usá-la como modelo para criar novas postagens. Para obter mais informações, consulte "[Postagens](https://jekyllrb.com/docs/posts/)" na documentação do Jekyll. + +O tema engloba layouts, inclusões e folhas de estilo padrão que serão aplicados automaticamente a novas páginas e postagens no site, mas é possível substituir qualquer um desses padrões. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll#themes)". + +{% data reusables.pages.about-front-matter %} + +{% data reusables.pages.test-locally %} + +### Adicionar uma nova página ao site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. Na raiz da fonte de publicação, crie um novo arquivo para a página chamado _PAGE-NAME.md_, substituindo _PAGE-NAME_ por um nome de arquivo significativo. +4. Adicione a página inicial YAML a seguir ao topo do arquivo, substituindo _PAGE TITLE_ pelo título da página e _URL-PATH_ por um caminho para a URL da página. Por exemplo, se a URL base do site for `https://octocat.github.io` e _URL-PATH_ for `/about/contact/`, a página estará localizada em `https://octocat.github.io/about/contact`. + ```shell + layout: page + title: "PAGE TITLE" + permalink: /URL-PATH/ + ``` +5. Abaixo da página inicial, adicione conteúdo para a 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 %} + +### Adicionar uma nova postagem ao site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. Navegue até o diretório `_posts`. +4. Crie um novo arquivo chamado _YYYY-MM-DD-NAME-OF-POST.md_, substituindo _YYY-MM-DD_ pela data da postagem e _NAME-OF-POST_ pelo nome dela. +4. Adicione a página inicial YAML a seguir ao topo do arquivo, substituindo _POST TITLE_ pelo título da postagem, _YYYY-MM-DD hh:mm:ss -0000_ pela data e hora da postagem e _CATEGORY-1_ e _CATEGORY-2_ por quantas categorias que você quiser que a postagem tenha. + ```shell + layout: post + title: "POST TITLE" + date: YYYY-MM-DD hh:mm:ss -0000 + categories: CATEGORY-1 CATEGORY-2 + ``` +5. Abaixo da página inicial, adicione conteúdo para a postagem. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +Seu post já deve estar no seu site! Se a URL de base do seu site for `https://octocat.github.io`, o seu novo post estará localizado em `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/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000..9daf5dd370 --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,116 @@ +--- +title: Criar um site do GitHub Pages com o Jekyll +intro: 'É possível usar o Jekyll para criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou existente.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/creating-a-github-pages-site-with-jekyll + - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll +permissions: 'Pessoas com permissões de administrador para um repositório podem criar um site do {% data variables.product.prodname_pages %} com o Jekyll.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Pré-requisitos + +Antes de poder usar o Jekyll para criar um site do {% data variables.product.prodname_pages %}, você precisa instalar o Jekyll e o Git. Para obter mais informações, consulte [Instalação](https://jekyllrb.com/docs/installation/) na documentação do Jekyll e "[Configurar o Git](/articles/set-up-git)". + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Criar um repositório para seu site + +{% data reusables.pages.new-or-existing-repo %} + +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} + +### Criar seu site + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Se você ainda não tem uma cópia do seu repositório, navegue até o local onde deseja armazenar os arquivos de origem do seu site, substituindo _PARENT-FOLDER_ pela pasta que deverá conter a pasta do repositório. + ```shell + $ cd PARENT-FOLDER + ``` +3. Caso você ainda não o tenha feito, inicialize um repositório Git local, substituindo _REPOSITORY-NAME_ pelo nome do seu repositório. + ```shell + $ git init REPOSITORY-NAME + > Initialized empty Git repository in /Users/octocat/my-site/.git/ + # Cria uma nova pasta no seu computador, inicializada como um repositório Git + ``` + 4. Altere os diretórios no repositório. + ```shell + $ cd REPOSITORY-NAME + # Altera o diretório de trabalho + ``` +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + Por exemplo, se você escolheu publicar o seu site a partir da pasta `documentação` no branch-padrão, crie e altere os diretórios na pasta `documentação`. + ```shell + $ mkdir docs + # Cria uma nova pasta chamada docs + $ cd docs + ``` + Se você optou por publicar seu site a partir do branch `gh-pages`, crie e faça checkout do branch `gh-pages`. + ```shell + $ git checkout --orphan gh-pages + # Cria um novo branch, sem histórico ou conteúdo, chamado gh-pages e alterna para o branch gh-pages + ``` +7. Para criar um novo site do Jekyll, use o comando `jekyll new`: + ```shell + $ jekyll new . + # Cria um site do Jekyll no diretório atual + ``` +8. Abra o Gemfile que o Jekyll criou. +1. Adicione "#" ao início da linha que começa com `gem "jekyll"` para comentar nesta linha. +1. Adicione o gem `github-pages` editando a linha que começa com `# gem "github-pages"`. Mudar esta linha para: + + ```shell + gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins + ``` + + Substitua _GITHUB-PAGES-VERSÃO_ pela última versão compatível do gem de `github-pages`. Você pode encontrar esta versão aqui: "[Versões de dependência](https://pages.github.com/versions/)". + + A versão correta do Jekyll será instalada como uma dependência do gem de `github-pages`. +10. Salve e feche o Gemfile. +11. Na linha de comando, execute `atualização do pacote`. +11. Como alternativa, teste seu site localmente. Para obter mais informações, consulte "[Testar seu site do {% data variables.product.prodname_pages %} localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". +12. Adicione seu repositório {% data variables.product.product_name %} como um remoto, substituindo {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ pelo nome de host da sua empresa,{% endif %} _USUÁRIO_ pela conta proprietária do repositório{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} e _REPOSITÓRIO_ pelo nome do repositório. +```shell +{% if currentVersion == "free-pro-team@latest" %} +$ git remote add origin https://github.com/USER/REPOSITORY.git +{% else %} +$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git +{% endif %} +``` +13. Faça push no repositório para o {% data variables.product.product_name %}, substituindo _BRANCH_ pelo nome do branch em que você está trabalhando. + ```shell + $ git push -u origin BRANCH + ``` +{% data reusables.pages.configure-publishing-source %} +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Próximas etapas + +Para adicionar uma nova página ou postagem ao seu site, consulte "[Adicionar conteúdo ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)". + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md new file mode 100644 index 0000000000..3f97b639ff --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md @@ -0,0 +1,25 @@ +--- +title: Configurar um site do GitHub Pages com o Jekyll +intro: 'Você pode usar o Jekyll, um popular gerador de site estático, para personalizar ainda mais o site do {% 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 + - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..c41b3d87d7 --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,36 @@ +--- +title: Definir um processador markdown para seu site do GitHub Pages usando o Jekyll +intro: 'Você pode escolher um processador markdown para determinar como o markdown é renderizado no site do {% 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 + - /github/working-with-github-pages/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: '*' +topics: + - Páginas +--- + +Pessoas com permissões de gravação para um repositório podem definir um processador markdown para um site do {% data variables.product.prodname_pages %}. + +O {% data variables.product.prodname_pages %} é compatível com dois processadores markdown: [kramdown](http://kramdown.gettalong.org/) e o próprio processador [CommonMark](https://commonmark.org/) estendido do {% data variables.product.prodname_dotcom %}, que é usado para renderizar markdown em estilo {% data variables.product.prodname_dotcom %} em todo o {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)". + +Você pode usar o markdown em estilo {% data variables.product.prodname_dotcom %} com qualquer um dos processadores, mas apenas o processador CommonMark é que sempre corresponderá aos resultados que você vê no {% data variables.product.product_name %}. + +{% data reusables.pages.navigate-site-repo %} +2. No repositório, navegue até o arquivo *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Localize a linha que começa com `markdown:` e altere o valor para `kramdown` ou `GFM`. ![Configuração do markdown em 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 %} + +### Leia mais + +- [Documentação do kramdown](https://kramdown.gettalong.org/documentation.html) +- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/) diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000..3884a41920 --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,62 @@ +--- +title: Testar o site do GitHub Pages localmente com o Jekyll +intro: 'Você pode criar o site do {% data variables.product.prodname_pages %} localmente para visualizar e testar as alterações nele.' +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 + - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +Qualquer pessoa com permissões de leitura para um repositório pode testar um site do {% data variables.product.prodname_pages %} localmente. + +### Pré-requisitos + +Antes de usar o Jekyll para testar um site, você deve: + - Instalar o [Jekyll](https://jekyllrb.com/docs/installation/). + - Criar um site do Jekyll. Para obter mais informações, consulte "[Criar um site do {% data variables.product.prodname_pages %} com o Jekyll](/articles/creating-a-github-pages-site-with-jekyll)". + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Criar site localmente + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.pages.navigate-publishing-source %} +3. Run `bundle install`. +3. Execute o site do Jekyll localmente. + ```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 visualizar o site, navegue para `http://localhost:4000` no navegador da web. + +### Atualizar o gem do {% data variables.product.prodname_pages %} + +O Jekyll é um projeto ativo de código aberto que é atualizado com frequência. Se o gem `github-pages` no seu computador estiver desatualizado em relação ao gem `github-pages` no servidor do {% data variables.product.prodname_pages %}, seu site poderá ter uma aparência diferente da criada localmente quando for publicado no {% data variables.product.product_name %}. Para evitar isso, atualize regularmente o gem `github-pages` no seu computador. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Atualize o gem `github-pages`. + - Se você instalou o bundler, execute `bundle update github-pages`. + - Se não tiver o bundler instalado, execute `gem update github-pages`. + +### Leia mais + +- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) na documentação do Jekyll diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..237651d8f9 --- /dev/null +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,191 @@ +--- +title: Solucionar problemas de erros de criação do Jekyll para sites do GitHub Pages +intro: 'Você pode usar mensagens de erro de criação do Jekyll para solucionar problemas com seu site do {% 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 + - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - Páginas +--- + +### Solucionar problemas de erros de criação + +Se o Jekyll encontrar um erro ao criar seu site do {% data variables.product.prodname_pages %} localmente ou no {% data variables.product.product_name %}, você poderá usar mensagens de erro para solucionar problemas. Para obter mais informações sobre mensagens de erro e como visualizá-las, consulte "[Sobre erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". + +Se você recebeu uma mensagem de erro genérica, verifique os problemas comuns. +- Você está usando plugins incompatíveis. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% if currentVersion == "free-pro-team@latest" %} +- Seu repositório excedeu os limites de tamanho. Para obter mais informações, consulte "[Qual é a minha quota de disco?](/articles/what-is-my-disk-quota)"{% endif %} +- Você alterou a configuração `source` no arquivo *_config.yml*. {% data variables.product.prodname_pages %} substitui essa configuração durante o processo de criação. +- Um nome de arquivo na fonte de publicação contém dois pontos (`:`), o que não é permitido. + +Se você recebeu uma mensagem de erro específica, revise abaixo as informações de solução de problemas relativas à mensagem de erro. + +Depois que tiver corrigido os possíveis erros, faça push das alterações para a fonte de publicação do seu site para ativar outra criação no {% data variables.product.product_name %}. + +### Erro no arquivo de configuração + +Este erro significa que ocorreu falha na criação do seu site porque o arquivo *_config.yml* contém erros de sintaxe. + +Para solucionar problemas, verifique se o arquivo *_config.yml* segue estas regras: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +### Esta é uma data/hora inválida + +Este erro significa que uma das páginas do seu site inclui uma data/hora inválida. + +Para solucionar problemas, pesquise o arquivo na mensagem de erro e os layouts do arquivo para as exigências de qualquer filtro de data do Liquid. Verifique se alguma variável passada em filtros de data do Liquid tem valores em todos os casos e nunca passa `nil` ou `""`. Para obter mais informações, consulte "[Filtros do Liquid](https://help.shopify.com/en/themes/liquid/filters)" na documentação do Liquid. + +### O arquivo não existe no diretório includes + +Este erro significa que o código faz referência a um arquivo que não existe no diretório *_includes*. + +{% data reusables.pages.search-for-includes %} Se algum dos arquivos a que você fez referência não estiver no diretório *_includes*, copie ou mova os arquivos para o diretório *_includes*. + +### O arquivo é um link simbólico + +Este erro significa que o código faz referência a um arquivo com link simbólico que não existe na fonte de publicação do seu site. + +{% data reusables.pages.search-for-includes %} Se algum dos arquivos a que você fez referência for com link simbólico, copie ou mova os arquivos para o diretório *_includes*. + +### Arquivo codificado por UTF-8 incorretamente + +Este erro significa que você usou caracteres não latinos, como `日本語`, sem avisar ao computador que esperava esses símbolos. + +Para solucionar problemas, force a codificação UTF-8 adicionando a seguinte linha ao arquivo *_config.yml*: +```yaml +encoding: UTF-8 +``` + +### Linguagem inválida do realçador + +Este erro significa que você especificou algum realçador de sintaxe diferente de [Rouge](https://github.com/jneen/rouge) ou [Pygments](http://pygments.org/) no arquivo de configuração. + +Para solucionar problemas, atualize o arquivo *_config.yml* para especificar [Rouge](https://github.com/jneen/rouge) ou [Pigmentos](http://pygments.org/). Para obter mais informações, consulte "[Sobre o {% data variables.product.product_name %} e o Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)". + +### Data de postagem inválida + +Este erro significa que uma postagem no seu site contém uma data inválida no nome de arquivo ou na página inicial YAML. + +Para solucionar problemas, verifique se todas as datas estão no formato YYYY-MM-DD HH:MM:SS para UTC e se são datas reais do calendário. Para especificar um fuso horário com um intervalo de tempo UTC, use o formato YYYY-MM-DD HH:MM:SS +/-TTTT (ano-mês-dia horas:minutos:segundos +/-TTTT), como `2014-04-18 11:30:00 +0800`. + +Se você especificar um formato de data no arquivo *_config.yml*, verifique se o formato está correto. + +### SCSS ou Sass inválido + +Este erro significa que seu repositório contém um arquivo Sass ou SCSS com conteúdo inválido. + +Para solucionar problemas, revise o número de linha incluído na mensagem de erro referente a Sass ou SCSS inválido. Para ajudar a prevenir erros no futuro, instale um linter Sass ou SCSS para seu editor de texto favorito. + +### Submódulo inválido + +Este erro significa que seu repositório inclui um submódulo que não foi inicializado corretamente. + +{% data reusables.pages.remove-submodule %} + +Caso queira utilizar o submódulo, lembre-se de usar `https://` quando fizer referência ao submódulo (a não `http://`) e de que o submódulo está em um repositório público. + +### YAML inválido no arquivo de dados + +Este erro significa que um ou mais arquivos na pasta *_data* contém YAML inválido. + +Para solucionar problemas, verifique se os arquivos YAML na pasta *_data* seguem estas regras: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +Para obter mais informações sobre arquivos de dados do Jekyll, consulte ""[Arquivos de dados](https://jekyllrb.com/docs/datafiles/)" na documentação do Jekyll. + +### Erros de markdown + +Este erro significa que seu repositório contém erros de markdown. + +Para solucionar problemas, verifique se você está usando um processador markdown compatível. Para obter mais informações, consulte "[Definir um processador markdown para seu site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)". + +Em seguida, verifique se o arquivo na mensagem de erro usa uma sintaxe markdown válida. Para obter mais informações, consulte "[Markdown: sintaxe](https://daringfireball.net/projects/markdown/syntax)" no Daring Fireball. + +### Pasta docs ausente + +Este erro significa que você escolheu a pasta `docs` em um branch como a sua fonte de publicação, mas não há nenhuma pasta de `docs` na raiz do seu repositório naquele branch. + +Para solucionar esse problema, se a pasta `documentação` foi movida acidentalmente, tente mover a pasta `docs` de volta para a raiz do repositório no branch que você escolheu para a sua fonte de publicação. Se a pasta `docs` tiver sido excluída acidentalmente, siga um destes procedimentos: +- Use o Git para reverter ou desfazer a exclusão. Para obter mais informações, consulte "[git-revert](https://git-scm.com/docs/git-revert.html)" na documentação do Git. +- Crie uma nova pasta de `documentação` na raiz do repositório no branch que você escolheu para a sua fonte de publicação e adicione os arquivos de origem do site à pasta. Para obter mais informações, consulte "[Criar arquivos](/articles/creating-new-files)". +- Altere a fonte de publicação. Para obter mais informações, consulte "[Configurar uma fonte de publicação do {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)". + +### Submódulo ausente + +Este erro significa que seu repositório inclui um submódulo que não existe ou não foi inicializado corretamente. + +{% data reusables.pages.remove-submodule %} + +Se você quiser usar um submódulo, inicialize-o. Para obter mais informações, consulte "[Ferramentas Git - Submódulos](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" no livro _Pro Git_. + +### Permalinks relativos configurados + +Este erro significa que você tem permalinks relativos, que não são compatíveis com o {% data variables.product.prodname_pages %} no arquivo *_config.yml*. + +Permalinks são URLs permanentes que fazem referência a uma determinada página no seu site. Os permalinks absolutos iniciam com a raiz do site, enquanto os permalinks relativos iniciam com a pasta que contém a página referenciada. O {% data variables.product.prodname_pages %} e o Jekyll não são mais compatíveis com permalinks relativos. Para obter mais informações sobre permalinks, consulte "[Permalinks](https://jekyllrb.com/docs/permalinks/)" na documentação do Jekyll. + +Para solucionar problemas, remova a linha `relative_permalinks` do arquivo *_config.yml* e reformate os permalinks relativos no site com permalinks absolutos. Para obter mais informações, consulte "[Editar arquivos no repositório](/articles/editing-files-in-your-repository)". + +### O link simbólico não existe no repositório do site + +Este erro significa que seu site inclui um link simbólico que não existe na fonte de publicação do site. Para obter mais informações sobre links simbólicos, consulte "[Link simbólico](https://en.wikipedia.org/wiki/Symbolic_link)" na Wikipédia. + +Para solucionar problemas, determine se o arquivo na mensagem de erro é usado para criar o site. Se ele não for ou se você não quiser que o arquivo seja um link simbólico, exclua o arquivo. Se o arquivo de link simbólico for necessário para criar seu site, verifique se o arquivo ou o diretório a que ele faz referência está na fonte de publicação do site. Para incluir ativos externos, considere usar {% if currentVersion == "free-pro-team@latest" %}`submódulo do git` ou {% endif %}um gerenciador de pacotes de terceiros como o [Bower](https://bower.io/).{% if currentVersion == "free-pro-team@latest" %} Para obter mais informações, consulte "[Usar submódulos com {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %} + +### Erro de sintaxe no loop 'for' + +Este erro significa que o código inclui sintaxe inválida em uma declaração de loop `for` do Liquid. + +Para solucionar problemas, verifique se todos os loops `for` no arquivo da mensagem de erro têm sintaxe adequada. Para obter mais informações sobre a sintaxe adequada para loops `for`, consulte "[Tags de Iteração](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" na documentação do Liquid. + +### Tag fechada incorretamente + +Esta mensagem de erro significa que o código inclui uma tag lógica que foi fechada incorretamente. Por exemplo, {% raw %}`{% capture example_variable %}` deve ser fechada por `{% endcapture %}`{% endraw %}. + +Para solucionar problemas, verifique se todas as tags lógicas no arquivo da mensagem de erro estão fechadas corretamente. Para obter mais informações, consulte "[Tags do Liquid](https://help.shopify.com/en/themes/liquid/tags)" na documentação do Liquid. + +### Tag terminada incorretamente + +Este erro significa que o código inclui uma tag de saída que não foi terminada corretamente. Por exemplo, {% raw %}`{{ page.title }` em vez de `{{ page.title }}`{% endraw %}. + +Para solucionar problemas, verifique se todas as tags de saída no arquivo da mensagem de erro estão terminadas com `}}`. Para obter mais informações, consulte "[Objetos do Liquid](https://help.shopify.com/en/themes/liquid/objects)" na documentação do Liquid. + +### Erro de tag desconhecida + +Este erro significa que o código contém uma tag do Liquid não reconhecida. + +Para solucionar problemas, verifique se todas as tags do Liquid no arquivo da mensagem de erro correspondem a variáveis padrão do Jekyll e se não há erros de digitação nos nomes das tags. Para obter uma lista de variáveis padrão, consulte "[Variáveis](https://jekyllrb.com/docs/variables/)" na documentação do Jekyll. + +Plugins incompatíveis são uma fonte comum de tags não reconhecidas. Se você usar um plugin incompatível ao gerar seu site localmente e fazer push dos arquivos estáticos para o {% data variables.product.product_name %}, verifique se o plugin não está inserindo tags que não estão nas variáveis padrão do Jekyll. Para obter uma lista de plugins compatíveis, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll#plugins)". diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md index c6b8adaa7f..b2cb7bca82 100644 --- a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md @@ -170,7 +170,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap Da mesma forma, podemos [visualizar repositórios para o usuário autenticado][user repos api]: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -207,7 +207,7 @@ API de {% data variables.product.product_name %} também é compatível com a cr precisamos `POST` alguns JSON que contém informações e opções de configuração. ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -242,7 +242,7 @@ A interface de usuário para problemas no {% data variables.product.product_name Assim como o github.com, a API fornece alguns métodos para exibir problemas para o usuário autenticado. Para [ver todos os seus problemas][get issues api], chame `GET /issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -250,7 +250,7 @@ Para obter apenas os [problemas sob uma das suas organizações de {% data varia /orgs//issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -283,7 +283,7 @@ Agora que vimos como paginar listas de problemas, vamos [criar um problema][crea Para criar um problema, precisamos estar autenticados. Portanto, passaremos um token do OAuth no cabeçalho. Além disso, passaremos o título, texto, e as etiquetas no texto do JSON para o caminho `/issues` abaixo do repositório em que queremos criar o problema: ```shell -$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ +$ curl -i -H 'Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md index da5c8969e1..e0d429a8e3 100644 --- a/translations/pt-BR/content/rest/reference/enterprise-admin.md +++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md @@ -8,6 +8,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints to administer your enterprise account. @@ -16,7 +18,7 @@ You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints {% note %} -**Observação:** Este artigo aplica-se a {% data variables.product.prodname_ghe_cloud %}. Para ver a versão do {% data variables.product.prodname_ghe_server %}, use o menu suspenso **{% data ui.pages.article_version %}**. +**Observação:** Este artigo aplica-se a {% data variables.product.prodname_ghe_cloud %}. Para visualizar a versão de {% data variables.product.prodname_ghe_managed %} ou de {% data variables.product.prodname_ghe_server %}, use o menu suspenso **{% data ui.pages.article_version %}**. {% endnote %} @@ -24,10 +26,10 @@ You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints ### URLs do ponto de extremidade -REST API endpoints{% if enterpriseServerVersions contains currentVersion %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: +Pontos de extremidade da API REST{% if enterpriseServerVersions contains currentVersion %}—exceto os pontos de extremidades da API REST do [Console de gerenciamento](#management-console) -{% endif %} são prefixados com a seguinte URL: ```shell -http(s)://hostname/api/v3/ +{% data variables.product.api_url_pre %} ``` {% if enterpriseServerVersions contains currentVersion %} @@ -40,16 +42,16 @@ http(s)://hostname/ {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} ### Autenticação -Os endpoints de API da sua instalação do {% data variables.product.product_name %} aceitam [os mesmos métodos de autenticação](/rest/overview/resources-in-the-rest-api#authentication) da API do GitHub.com. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% if enterpriseServerVersions contains currentVersion %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} Os tokens OAuth devem ter o `site_admin` [escopo OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) quando usados com endpoints específicos da Enterprise.{% endif %} +Os endpoints de API da sua instalação do {% data variables.product.product_name %} aceitam [os mesmos métodos de autenticação](/rest/overview/resources-in-the-rest-api#authentication) da API do GitHub.com. Você pode efetuar a autenticação com **[tokens do OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% if enterpriseServerVersions contains currentVersion %}(que podem ser criado usando a [API de Autorizações](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}ou **[autenticação básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} Os tokens OAuth devem ter o `site_admin` [escopo OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) quando usados com endpoints específicos da Enterprise.{% endif %} -Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% if enterpriseServerVersions contains currentVersion %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. +Os pontos de extremidade da API da administração da empresa podem ser acessados por administradores do site de {% data variables.product.product_name %}autenticados{% if enterpriseServerVersions contains currentVersion %}, exceto a API do [Console de Gerenciamento](#management-console), que exige a [senha do console de gerenciamento](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. {% endif %} {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} ### Informações da versão -The current version of your enterprise is returned in the response header of every API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` You can also read the current version by calling the [meta endpoint](/rest/reference/meta/). +A versão atual da sua empresa é retornada no cabeçalho de resposta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` Você também pode ler a versão atual chamando o [ponto de extremidade de meta](/rest/reference/meta/). {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} @@ -76,9 +78,11 @@ The current version of your enterprise is returned in the response header of eve {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ## GitHub Actions +{% data reusables.actions.ae-beta %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} {% endfor %} @@ -96,7 +100,7 @@ O IdP deve usar `{% data variables.product.api_url_code %}/scim/v2/enterprises/{ {% note %} -**Nota:** A API corporativa SCIM está disponível apenas para empresas em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Nota:** A API corporativa SCIM está disponível apenas para empresas em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% endnote %} @@ -150,9 +154,9 @@ GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} {% if currentVersion == "github-ae@latest" %} -## Encryption at rest +## Criptografia em repouso -You can use the encryption at rest API to manage the key that encrypts your data on {% data variables.product.product_name %}. For more information, see "[Configuring data encryption for your enterprise](/admin/configuration/configuring-data-encryption-for-your-enterprise)." +Você pode usar a criptografia em API REST para gerenciar a chave que criptografa seus dados em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Configurar a criptografia de dados para sua empresa](/admin/configuration/configuring-data-encryption-for-your-enterprise)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'encryption-at-rest' %}{% include rest_operation %}{% endif %} @@ -173,9 +177,9 @@ A API de Estatísticas Administrativas fornece uma variedade de métricas sobre {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -## Announcements +## Anúncios -The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." +A API de anúncios permite que você gerencie o banner de anúncio global na sua empresa. Para obter mais informações, consulte "[Personalizar mensagens de usuários para a sua empresa](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'announcement' %}{% include rest_operation %}{% endif %} @@ -187,7 +191,7 @@ The Announcements API allows you to manage the global announcement banner in you ## Webhooks globais -Global webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise. Webhooks globais podem se inscrever para os tipos de eventos [organização](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuário](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositório](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipe](/developers/webhooks-and-events/webhook-events-and-payloads#team), [integrante](/developers/webhooks-and-events/webhook-events-and-payloads#member), [filiação](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifurcação](/developers/webhooks-and-events/webhook-events-and-payloads#fork)e [ping](/developers/webhooks-and-events/about-webhooks#ping-event). +Webhooks globais são instalados na sua empresa. Você pode usar webhooks globais para monitorar, responder ou aplicar regras automaticamente para usuários, organizações, equipes e repositórios na sua empresa. Webhooks globais podem se inscrever para os tipos de eventos [organização](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuário](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositório](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipe](/developers/webhooks-and-events/webhook-events-and-payloads#team), [integrante](/developers/webhooks-and-events/webhook-events-and-payloads#member), [filiação](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifurcação](/developers/webhooks-and-events/webhook-events-and-payloads#fork)e [ping](/developers/webhooks-and-events/about-webhooks#ping-event). *Esta API está disponível somente para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la. Para aprender como configurar webhooks globais, consulte [Sobre webhooks globais](/enterprise/admin/user-management/about-global-webhooks). @@ -203,7 +207,7 @@ Global webhooks are installed on your enterprise. You can use global webhooks to Você pode usar a API LDAP para atualizar as relações de conta entre um usuário ou equipe {% data variables.product.product_name %} e sua entrada LDAP vinculada ou enfileirar uma nova sincronização. -Com os endpoints de mapeamento LDAP, você é capaz de atualizar o Nome Distinto (DN) para o qual um usuário ou uma equipe mapeia. Note que os endpoints LDAP são geralmente eficazes apenas se o seu appliance {% data variables.product.product_name %} tiver [Sincronização LDAP habilitada](/enterprise/admin/authentication/using-ldap). O endpoint [mapeamento LDAP de atualização para um usuário](#update-ldap-mapping-for-a-user) pode ser usado quando o LDAP é habilitado, mesmo que a sincronização LDAP esteja desativada. +Com os endpoints de mapeamento LDAP, você é capaz de atualizar o Nome Distinto (DN) para o qual um usuário ou uma equipe mapeia. Note que os endpoints LDAP são geralmente eficazes apenas se o seu aplicativo de {% data variables.product.product_name %} tiver [Sincronização LDAP habilitada](/enterprise/admin/authentication/using-ldap). O endpoint [mapeamento LDAP de atualização para um usuário](#update-ldap-mapping-for-a-user) pode ser usado quando o LDAP é habilitado, mesmo que a sincronização LDAP esteja desativada. {% for operation in currentRestOperations %} {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %} @@ -231,7 +235,7 @@ A API do Console de Gerenciamento ajuda você a gerenciar sua instalação do {% {% tip %} -Você deve definir explicitamente o número da porta ao fazer chamadas de API para o Console de Gerenciamento. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`. +Você deve definir explicitamente o número da porta ao fazer chamadas de API para o Console de Gerenciamento. Se o TLS estiver habilitado na sua empresa, o número da porta será `8443`; caso contrário, o número da porta será `8080`. Se não quiser fornecer um número da porta, você precisará configurar sua ferramenta para seguir os redirecionamentos automaticamente. @@ -264,7 +268,7 @@ $ curl -L 'https://api_key:your-amazing-password@hostname: {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} ## Organizações -The Organization Administration API allows you to create organizations on your enterprise. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la. +A API de administração da organização permite a criação de organizações na sua empresa. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `404` se tentarem acessá-la. {% for operation in currentRestOperations %} {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} @@ -384,7 +388,7 @@ Os valores possíveis para *aplicação* são `habilitado`, `desabilitado` e`tes {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} ## Usuários -The User Administration API allows you to suspend{% if enterpriseServerVersions contains currentVersion %}, unsuspend, promote, and demote{% endif %}{% if currentVersion == "github-ae@latest" %} and unsuspend{% endif %} users on your enterprise. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `403` se tentarem acessá-la. +A API de Administração do Usuário permite que você suspenda{% if enterpriseServerVersions contains currentVersion %}, cancele a suspensão, promova e rebaixe{% endif %}{% if currentVersion == "github-ae@latest" %} e cancele o suspensão{% endif %} dos usuários da sua empresa. *Só está disponível para [administradores do site](/rest/overview/resources-in-the-rest-api#authentication) autenticados.* Usuários normais receberão uma mensagem `403` se tentarem acessá-la. {% for operation in currentRestOperations %} {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/rest/reference/gists.md b/translations/pt-BR/content/rest/reference/gists.md index 1ff371cc24..428ddf75ee 100644 --- a/translations/pt-BR/content/rest/reference/gists.md +++ b/translations/pt-BR/content/rest/reference/gists.md @@ -6,45 +6,47 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- -### Authentication +### Autenticação -You can read public gists {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %}and create them for anonymous users without a token.{% else %} anonymously, but you must be signed into GitHub to create gists.{% endif %} To read or write gists on a user's behalf, you need the gist OAuth scope and a token. For more information, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps)." +Você pode ler gists públicos {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contém currentVersion %}e criá-los para usuários anônimos sem um token{% else %} de forma anônima, mas você precisa entrar no GitHub para criar gists.{% endif %} Para ler ou escrever gists em nome do usuário, você precisa do escopo OAuth para gists e um token. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)." -### Truncation +### Truncamento -The Gist API provides up to one megabyte of content for each file in the gist. Each file returned for a gist through the API has a key called `truncated`. If `truncated` is `true`, the file is too large and only a portion of the contents were returned in `content`. +A API de Gist fornece até um megabyte de conteúdo para cada arquivo no gist. Cada arquivo retornado por um gist através da API tem uma chave denominada `truncada`. Se `truncado` for `verdadeiro`, significa que arquivo é muito grande e apenas uma parte do conteúdo foi retornado em `conteúdo`. -If you need the full contents of the file, you can make a `GET` request to the URL specified by `raw_url`. Be aware that for files larger than ten megabytes, you'll need to clone the gist via the URL provided by `git_pull_url`. +Se você precisar do conteúdo completo do arquivo, você pode fazer uma solicitação `GET` para a URL especificada por `raw_url`. Tenha em mente que, para arquivos maiores que dez megabytes, você deverá clonar o gist através da URL fornecida por `git_pull_url`. -In addition to a specific file's contents being truncated, the entire files list may be truncated if the total number exceeds 300 files. If the top level `truncated` key is `true`, only the first 300 files have been returned in the files list. If you need to fetch all of the gist's files, you'll need to clone the gist via the URL provided by `git_pull_url`. +Além do conteúdo de um arquivo específico ser truncado, toda a lista de arquivos pode ser truncada se o número total exceder 300 arquivos. Se a chave de nível superior `truncado` é `verdadeira`, apenas os primeiros 300 arquivos foram retornados na lista de arquivos. Se você precisar buscar todos os arquivos do gist, você deverá clonar o gist através da URL fornecida por `git_pull_url`. -### Custom media types for gists +### Tipos de mídia personalizados para gists -These are the supported media types for fetching gist contents. +Estes são os tipos de mídia compatíveis para buscar conteúdo geral. application/vnd.github.VERSION.raw application/vnd.github.VERSION.base64 -For more information, see "[Media types](/rest/overview/media-types)." +Para obter mais informações, consulte "[Tipos de mídia](/rest/overview/media-types)". {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Comments +## Comentários -### Custom media types for Gist comments +### Tipos de mídia personalizados para comentários do Gist -These are the supported media types for gist comments. +Estes são os tipos de mídia compatíveis para comentários de gist. application/vnd.github.VERSION.raw application/vnd.github.VERSION.base64 -For more information about media types, see "[Custom media types](/rest/overview/media-types)." +Para obter mais informações sobre os tipos de mídia, consulte "[Tipos de mídia personalizados](/rest/overview/media-types)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/rest/reference/migrations.md b/translations/pt-BR/content/rest/reference/migrations.md index 2933a4c8c4..7dc1c49677 100644 --- a/translations/pt-BR/content/rest/reference/migrations.md +++ b/translations/pt-BR/content/rest/reference/migrations.md @@ -16,7 +16,7 @@ topics: ## organização -A API de migrações só está disponível para os proprietários de organizações autenticadas. Para obter mais informações, consulte "[Níveis de permissão para uma organização](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)" e "[Outros métodos de autenticação](/rest/overview/other-authentication-methods)". +A API de migrações só está disponível para os proprietários de organizações autenticadas. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/pt-BR/content/rest/reference/repos.md b/translations/pt-BR/content/rest/reference/repos.md index 67a2f1ffa6..d32a5b49db 100644 --- a/translations/pt-BR/content/rest/reference/repos.md +++ b/translations/pt-BR/content/rest/reference/repos.md @@ -1,5 +1,5 @@ --- -title: Repositories +title: Repositórios allowTitleToDifferFromFilename: true redirect_from: - /v3/repos @@ -7,6 +7,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- {% for operation in currentRestOperations %} @@ -19,25 +21,24 @@ versions: {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %} {% endfor %} -## Collaborators +## Colaboradores {% for operation in currentRestOperations %} {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %} {% endfor %} -## Comments +## Comentários -### Custom media types for commit comments +### Tipos de mídia personalizados para comentários de commit -These are the supported media types for commit comments. You can read more -about the use of media types in the API [here](/rest/overview/media-types). +Estes são os tipos de mídia compatíveis com os comentários do commit. Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types). application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json application/vnd.github-commitcomment.html+json application/vnd.github-commitcomment.full+json -For more information, see "[Custom media types](/rest/overview/media-types)." +Para obter mais informações, consulte "[tipos de mídia personalizados](/rest/overview/media-types)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} @@ -45,14 +46,14 @@ For more information, see "[Custom media types](/rest/overview/media-types)." ## Commits -The Repo Commits API supports listing, viewing, and comparing commits in a repository. +A API de Commits do repositório é compatível com a listagem, visualização e comparação de commits em um repositório. {% for operation in currentRestOperations %} {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} {% endfor %} {% if currentVersion == "free-pro-team@latest" %} -## Community +## Comunidade {% for operation in currentRestOperations %} {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %} @@ -60,56 +61,54 @@ The Repo Commits API supports listing, viewing, and comparing commits in a repos {% endif %} -## Contents +## Conteúdo -These API endpoints let you create, modify, and delete Base64 encoded content in a repository. To request the raw format or rendered HTML (when supported), use custom media types for repository contents. +Estes pontos de extremidade da API permitem criar, modificar e excluir conteúdo codificado em Base64 em um repositório. Para solicitar o formato sem processar ou HTML interpretado (quando compatível), use os tipos de mídia personalizados para o conteúdo do repositório. -### Custom media types for repository contents +### Tipos de mídia personalizados para conteúdo do repositório -[READMEs](/rest/reference/repos#get-a-repository-readme), [files](/rest/reference/repos#get-repository-content), and [symlinks](/rest/reference/repos#get-repository-content) support the following custom media types: +Os [READMEs](/rest/reference/repos#get-a-repository-readme), [arquivos](/rest/reference/repos#get-repository-content) e [links simbólicos](/rest/reference/repos#get-repository-content) são compatíveis com os seguintes tipos de mídia personalizados: application/vnd.github.VERSION.raw application/vnd.github.VERSION.html -Use the `.raw` media type to retrieve the contents of the file. +Use o tipo de mídia `.raw` para recuperar o conteúdo do arquivo. -For markup files such as Markdown or AsciiDoc, you can retrieve the rendered HTML using the `.html` media type. Markup languages are rendered to HTML using our open-source [Markup library](https://github.com/github/markup). +Para arquivos de markup, como Markdown ou AsciiDoc, você pode recuperar o HTML interpretado usando o tipo de mídia `.html`. As linguagens de markup são processadas em HTML usando nossa [biblioteca de markup](https://github.com/github/markup) de código aberto. -[All objects](/rest/reference/repos#get-repository-content) support the following custom media type: +[Todos os objetos](/rest/reference/repos#get-repository-content) são compatíveis com o seguinte tipo de mídia personalizado: application/vnd.github.VERSION.object -Use the `object` media type parameter to retrieve the contents in a consistent object format regardless of the content type. For example, instead of an array of objects -for a directory, the response will be an object with an `entries` attribute containing the array of objects. +Use o parâmetro do tipo de mídia do `objeto` para recuperar o conteúdo em um formato de objeto consistente independentemente do tipo de conteúdo. Por exemplo, em vez de um array de objetos para um diretório, a resposta será um objeto com um atributo de `entrada` contendo o array de objetos. -You can read more about the use of media types in the API [here](/rest/overview/media-types). +Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types). {% for operation in currentRestOperations %} {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %} {% endfor %} -## Deploy keys +## Chaves de implantação {% data reusables.repositories.deploy-keys %} -Deploy keys can either be setup using the following API endpoints, or by using GitHub. To learn how to set deploy keys up in GitHub, see "[Managing deploy keys](/developers/overview/managing-deploy-keys)." +Chaves de implantação podem ser configuradas usando os seguintes pontos de extremidades da API ou usando o GitHub. Para saber como configurar as chaves de implantação no GitHub, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %} {% endfor %} -## Deployments +## Implantações -Deployments are requests to deploy a specific ref (branch, SHA, tag). GitHub dispatches a [`deployment` event](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) that external services can listen for and act on when new deployments are created. Deployments enable developers and organizations to build loosely coupled tooling around deployments, without having to worry about the implementation details of delivering different types of applications (e.g., web, native). +As implantações são solicitações para implantar um ref específico (branch, SHA, tag). O GitHub envia um [ evento de `implantação`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) pelo qual os serviços externos podem ouvir e atuar quando novas implantações são criadas. As implantações permitem que os desenvolvedores e as organizações construam ferramentas associadas em torno de implantações sem ter que se preocupar com os detalhes de implementação da entrega de diferentes tipos de aplicativos (p. ex., web, nativo). -Deployment statuses allow external services to mark deployments with an `error`, `failure`, `pending`, `in_progress`, `queued`, or `success` state that systems listening to [`deployment_status` events](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) can consume. +Os status de implantação externos permitem marcar implantações com `error`, `failure`, `pending`, `in_progress`, `queued` ou `success` afirmar que os sistemas que estão escutando os eventos [`deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) podem consumir. -Deployment statuses can also include an optional `description` and `log_url`, which are highly recommended because they make deployment statuses more useful. The `log_url` is the full URL to the deployment output, and -the `description` is a high-level summary of what happened with the deployment. +Os status de implantação também podem incluir uma `descrição` opcional e `log_url`, que são altamente recomendados porque tornam o status de implantação mais útil. O `log_url` é a URL completa para a saída de implantação e a `descrição` é um resumo de alto nível do que aconteceu com a implantação. -GitHub dispatches `deployment` and `deployment_status` events when new deployments and deployment statuses are created. These events allows third-party integrations to receive respond to deployment requests and update the status of a deployment as progress is made. +O GitHub envia os eventos de `implantação` e `deployment_status` quando novas implantações de status de implantação são criadas. Esses eventos permitem que as integrações de terceiros recebam resposta para solicitações de implantação e atualizem o status de implantação conforme o progresso é feito. -Below is a simple sequence diagram for how these interactions would work. +Abaixo está um diagrama de sequência sobre para como essas interações funcionariam. ``` +---------+ +--------+ +-----------+ +-------------+ @@ -138,49 +137,55 @@ Below is a simple sequence diagram for how these interactions would work. | | | | ``` -Keep in mind that GitHub is never actually accessing your servers. It's up to your third-party integration to interact with deployment events. Multiple systems can listen for deployment events, and it's up to each of those systems to decide whether they're responsible for pushing the code out to your servers, building native code, etc. +Tenha em mente que o GitHub nunca terá acesso aos seus servidores. Cabe à sua integração de terceiros interagir com os eventos de implantação. Vários sistemas podem ouvir eventos de implantação, e cabe a cada um desses sistemas decidir se serão responsáveis por retirar o código dos seus servidores, criar código nativo, etc. -Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the `public_repo` and `repo` scopes grant permission to code as well. +Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% if currentVersion != "github-ae@latest" %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well. -### Inactive deployments -When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. +### Implantações inativas -You can communicate that a transient environment no longer exists by setting its `state` to `inactive`. Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it. +Ao definir o estado de uma implantação como `sucesso`, todas as implantações de ambiente de não produção e não transitórios anteriores no mesmo nome do ambiente irão tornar-se `inativas`. Para evitar isso, você pode definir `auto_inactive` como `falso` ao criar o status de implantação. + +Você pode informar que um ambiente transitório não existe mais definindo seu `estado` como `inativo`. Definir o `estado` como `inativo` mostra a implantação como `destruída` em {% data variables.product.prodname_dotcom %} e remove o acesso a ela. {% for operation in currentRestOperations %} {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %} {% endfor %} -## Forks +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} +## Ambientes + +The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} +{% endfor %} +{% endif %} + +## Bifurcações {% for operation in currentRestOperations %} {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %} {% endfor %} -## Invitations +## Convites -The Repository Invitations API allows users or external services to invite other users to collaborate on a repo. The invited users (or external services on behalf of invited users) can choose to accept or decline the invitations. +A API de Convites do Repositório permite que usuários ou serviços externos convidem outros usuários para colaborar em um repositório. Os usuários convidados (ou serviços externos em nome dos usuários convidados) podem optar por aceitar ou recusar os convites. -Note that the `repo:invite` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted -access to invitations **without** also granting access to repository code, while the -`repo` scope grants permission to code as well as invitations. +Observe que o [Escopo OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` concede acesso direcionado aos convites **sem** conceder também acesso ao código do repositório. enquanto o escopo `repo` concede permissão ao código e aos convites convites. -### Invite a user to a repository +### Convidar um usuário para um repositório -Use the API endpoint for adding a collaborator. For more information, see "[Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator)." +Use o ponto de extremidade da API para adicionar um colaborador. Para obter mais informações, consulte "[Adicionar um colaborador de repositório](/rest/reference/repos#add-a-repository-collaborator)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %} {% endfor %} -## Merging +## Mesclar -The Repo Merging API supports merging branches in a repository. This accomplishes -essentially the same thing as merging one branch into another in a local repository -and then pushing to {% data variables.product.product_name %}. The benefit is that the merge is done on the server side and a local repository is not needed. This makes it more appropriate for automation and other tools where maintaining local repositories would be cumbersome and inefficient. +A API de merge do repositório é compatível com o merge de branches em um repositório. Isso realiza, essencialmente, a mesma coisa que mesclar um branch em outro em um repositório local e, em seguida, fazer push para {% data variables.product.product_name %}. O benefício é que o merge é realizado no lado do servidor e não é necessário um repositório local. Isso o torna mais apropriado para automação e outras ferramentas em que a manutenção de repositórios locais seria pesada e ineficiente. -The authenticated user will be the author of any merges done through this endpoint. +O usuário autenticado será o autor de qualquer merge feito por meio deste ponto de extremidade. {% for operation in currentRestOperations %} {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %} @@ -188,30 +193,30 @@ The authenticated user will be the author of any merges done through this endpoi ## Pages -The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners, even though the websites are public. For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." +A API de {% data variables.product.prodname_pages %} recupera informações sobre a sua configuração do {% data variables.product.prodname_pages %} e os status das suas criações. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". -In {% data variables.product.prodname_pages %} API endpoints with a `status` key in their response, the value can be one of: -* `null`: The site has yet to be built. -* `queued`: The build has been requested but not yet begun. -* `building`:The build is in progress. -* `built`: The site has been built. -* `errored`: Indicates an error occurred during the build. +Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} com uma chave de `status` na sua resposta, o valor pode ser: +* `null`: O site ainda não foi criado. +* `queued`: A criação foi solicitada, mas ainda não começou. +* `building`:A criaçãoestá em andamento. +* `built`: O site foi criado. +* `errored`: Indica que ocorreu um erro durante a criação. -In {% data variables.product.prodname_pages %} API endpoints that return GitHub Pages site information, the JSON responses include these fields: -* `html_url`: The absolute URL (including scheme) of the rendered Pages site. For example, `https://username.github.io`. -* `source`: An object that contains the source branch and directory for the rendered Pages site. This includes: - - `branch`: The repository branch used to publish your [site's source files](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. - - `path`: The repository directory from which the site publishes. Will be either `/` or `/docs`. +Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} que devolvem as informações do site do GitHub Pages, as respostas do JSON incluem esses campos: +* `html_url`: A URL absoluta (incluindo o esquema) do site de páginas interpretadas. Por exemplo, `https://username.github.io`. +* `source`: Um objeto que contém o branch de origem e o diretório do site de páginas interpretadas. Isto inclui: + - `branch`: O branch do repositório utilizado para publicar os [arquivos de origem do site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por exemplo, _principal_ ou _gh-pages_. + - `path`: O diretório do repositório a partir do qual o site é publicado. Será `/` ou `/docs`. {% for operation in currentRestOperations %} {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %} {% endfor %} -## Releases +## Versões {% note %} -**Note:** The Releases API replaces the Downloads API. You can retrieve the download count and browser download URL from the endpoints in this API that return releases and release assets. +**Observação:** A API de versões substitui a API de Downloads. Você pode recuperar a contagem de download e a URL de download do navegador a partir dos pontos de extremidades nesta API que retornam versões e liberam ativos. {% endnote %} @@ -219,68 +224,50 @@ In {% data variables.product.prodname_pages %} API endpoints that return GitHub {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %} {% endfor %} -## Statistics +## Estatísticas -The Repository Statistics API allows you to fetch the data that {% data variables.product.product_name %} uses for visualizing different -types of repository activity. +A API de Estatísticas do Repositório permite que você recupere os dados que o {% data variables.product.product_name %} usa para visualizar diferentes tipos de atividade do repositório. -### A word about caching +### Umas palavras sobre o armazenamento em cache -Computing repository statistics is an expensive operation, so we try to return cached -data whenever possible. If the data hasn't been cached when you query a repository's -statistics, you'll receive a `202` response; a background job is also fired to -start compiling these statistics. Give the job a few moments to complete, and -then submit the request again. If the job has completed, that request will receive a -`200` response with the statistics in the response body. +Computar as estatísticas do repositório é uma operação cara. Por esse motivo, tentamos retornar dados armazenados em cache sempre que possível. Se os dados não forem armazenados em cache nas estatísticas de um repositório, você receberá uma resposta de `202`; um trabalho em segundo plano também é acionado para começar a compilar estas estatísticas. Dê ao trabalho alguns instantes para que seja concluído e, em seguida, envie a solicitação novamente. Se o trabalho foi concluído, essa solicitação receberá uma resposta de `200` com as estatísticas no texto da resposta. -Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache. +As estatísticas do repositório são armazenadas em cache pelo SHA do branch-padrão do repositório; fazer push para o branch-padrão redefine o armazenamento em cache de estatísticas. -### Statistics exclude some types of commits +### As estatísticas excluem alguns tipos de commits -The statistics exposed by the API match the statistics shown by [different repository graphs](/github/visualizing-repository-data-with-graphs/about-repository-graphs). +As estatísticas expostas pela API correspondem às estatísticas mostradas pelos [diferentes gráficos de repositórios](/github/visualizing-repository-data-with-graphs/about-repository-graphs). -To summarize: -- All statistics exclude merge commits. -- Contributor statistics also exclude empty commits. +Resumo: +- Todas as estatísticas excluem commits de merge. +- As estatísticas do contribuidor também excluem commits vazios. {% for operation in currentRestOperations %} {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %} {% endfor %} -## Statuses +## Status -The status API allows external services to mark commits with an `error`, -`failure`, `pending`, or `success` state, which is then reflected in pull requests -involving those commits. +A API de status permite que serviços externos marquem commits com status de `erro`, `falha`, `pendente` ou `sucesso`, o que é refletido em pull requests que envolvem esses commits. -Statuses can also include an optional `description` and `target_url`, and -we highly recommend providing them as they make statuses much more -useful in the GitHub UI. +Os status também podem incluir uma `descrição` opcional e `target_url`, e é altamente recomendável fornecê-los, pois tornam o status muito mais útil na interface de usuário do GitHub. -As an example, one common use is for continuous integration -services to mark commits as passing or failing builds using status. The -`target_url` would be the full URL to the build output, and the -`description` would be the high level summary of what happened with the -build. +Como exemplo, um uso comum é para serviços de integração contínua para marcar commits como criações que passam ou que falham usando o status. O `target_url` seria a URL completa para a saída da criação, e a `descrição` seria o resumo de alto nível do que aconteceu com a criação. -Statuses can include a `context` to indicate what service is providing that status. -For example, you may have your continuous integration service push statuses with a context of `ci`, and a security audit tool push statuses with a context of `security`. You can -then use the [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) to retrieve the whole status for a commit. +Os status podem incluir um `contexto` para indicar qual serviço está fornecendo esse status. Por exemplo, você pode fazer com que o seu serviço de integração contínua faça push status com um contexto de `ci`, e uma ferramenta de auditoria de segurança faça push dos status com um contexto de `segurança`. Você pode usar [Obter o status combinado para uma referência específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) para recuperar todo o status de um commit. -Note that the `repo:status` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to statuses **without** also granting access to repository code, while the -`repo` scope grants permission to code as well as statuses. +Observe que o `escopo do OAuth` [repo:status](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a status **sem** conceder acesso ao código do repositório, enquanto o escopo `repo` concede permissão para o código e para status. -If you are developing a GitHub App and want to provide more detailed information about an external service, you may want to use the [Checks API](/rest/reference/checks). +Se você está desenvolvendo um aplicativo GitHub e deseja fornecer informações mais detalhadas sobre um serviço externo, você deverá usar a [API de verificação](/rest/reference/checks). {% for operation in currentRestOperations %} {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %} {% endfor %} {% if currentVersion == "free-pro-team@latest" %} -## Traffic +## Tráfego -For repositories that you have push access to, the traffic API provides access -to the information provided in your repository graph. For more information, see "Viewing traffic to a repository." +Para repositórios aos quais você tem acesso de push, a API de tráfego fornece acesso às informações fornecidas no seu gráfico de repositório. Para obter mais informações, consulte "Visualizar tráfego para um repositório. " {% for operation in currentRestOperations %} {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %} @@ -289,41 +276,41 @@ to the information provided in your repository graph. For more information, see ## Webhooks -The Repository Webhooks API allows repository admins to manage the post-receive hooks for a repository. Webhooks can be managed using the JSON HTTP API, or the [PubSubHubbub](#PubSubHubbub) API. +A API de Webhooks do Repositório permite que os administradores do repositório gerenciem os hooks post-receive de um repositório. Os webhooks podem ser gerenciados usando a API de HTTP do JSON ou a API de [SubHubbub](#PubSubHubbub). -If you would like to set up a single webhook to receive events from all of your organization's repositories, see our API documentation for [Organization Webhooks](/rest/reference/orgs#webhooks). +Se você deseja configurar um único webhook para receber eventos de todos os repositórios da organização, consulte nossa documentação de API para [Webhooks de organização](/rest/reference/orgs#webhooks). {% for operation in currentRestOperations %} {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} -### Receiving Webhooks +### Receber Webhooks -In order for {% data variables.product.product_name %} to send webhook payloads, your server needs to be accessible from the Internet. We also highly suggest using SSL so that we can send encrypted payloads over HTTPS. +Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por HTTPS. -#### Webhook headers +#### Cabeçalhos de webhook -{% data variables.product.product_name %} will send along several HTTP headers to differentiate between event types and payload identifiers. See [webhook headers](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) for details. +{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para obter informações. ### PubSubHubbub -GitHub can also serve as a [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) hub for all repositories. PSHB is a simple publish/subscribe protocol that lets servers register to receive updates when a topic is updated. The updates are sent with an HTTP POST request to a callback URL. -Topic URLs for a GitHub repository's pushes are in this format: +O GitHub também pode servir como um centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos os repositórios. O PSHB é um simples protocolo de publicação/assinatura que permite o registro de servidores para receber atualizações quando um tópico é atualizado. As atualizações são enviadas com uma solicitação HTTP do tipo POST para uma URL de chamada de retorno. As URLs dos tópicos dos pushes de um repositório do GitHub estão neste formato: `https://github.com/{owner}/{repo}/events/{event}` -The event can be any available webhook event. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." +O evento pode ser qualquer evento de webhook disponível. Para obter mais informações, consulte "[Eventos e cargas de Webhook](/developers/webhooks-and-events/webhook-events-and-payloads)". -#### Response format +#### Formato de resposta -The default format is what [existing post-receive hooks should expect](/post-receive-hooks/): A JSON body sent as the `payload` parameter in a POST. You can also specify to receive the raw JSON body with either an `Accept` header, or a `.json` extension. +O formato padrão é o que [os hooks post-receive existentes devem esperar](/post-receive-hooks/): Um texto JSON enviado como parâmetro `payload` em um POST. Você também pode especificar para receber o texto do JSON sem processar com um cabeçalho `Aceitar` ou uma extensão `.json`. Accept: application/json https://github.com/{owner}/{repo}/events/push.json -#### Callback URLs +#### URLs de chamada de retorno +As URLs de chamada de retorno podem usar o protocolo `http://`. -Callback URLs can use the `http://` protocol. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %}You can also `github://` callbacks to specify a GitHub service. +{% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2.20" %}Você também pode fazer chamada de retorno `github://` para especificar um serviço do GitHub. {% data reusables.apps.deprecating_github_services_ghe %} {% endif %} @@ -331,13 +318,12 @@ Callback URLs can use the `http://` protocol. {% if enterpriseServerVersions con 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 + # Send updates to Campfire github://campfire?subdomain=github&room=Commits&token=abc123 {% endif %} -#### Subscribing +#### Assinar -The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like: +O ponto de extremidade do GitHub PubSubHubbub é: `{% data variables.product.api_url_code %}/hub`. Uma solicitação bem-sucedida com o curl parece como: ``` shell curl -u "user" -i \ @@ -347,13 +333,13 @@ curl -u "user" -i \ -F "hub.callback=http://postbin.org/123" ``` -PubSubHubbub requests can be sent multiple times. If the hook already exists, it will be modified according to the request. +Solicitações do PubSubHubbub podem ser enviadas várias vezes. Se o hook já existe, ele será modificado de acordo com a solicitação. -##### Parameters +##### Parâmetros -Name | Type | Description ------|------|-------------- -``hub.mode``|`string` | **Required**. Either `subscribe` or `unsubscribe`. -``hub.topic``|`string` |**Required**. The URI of the GitHub repository to subscribe to. The path must be in the format of `/{owner}/{repo}/events/{event}`. -``hub.callback``|`string` | The URI to receive the updates to the topic. -``hub.secret``|`string` | A shared secret key that generates a SHA1 HMAC of the outgoing body content. You can verify a push came from GitHub by comparing the raw request body with the contents of the `X-Hub-Signature` header. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details. +| Nome | Tipo | Descrição | +| -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `hub.mode` | `string` | **Obrigatório**. `Assine` ou `cancele a assinatura`. | +| `hub.topic` | `string` | **Obrigatório**. A URI do repositório do GitHub a ser assinada. O caminho deve estar no formato `/{owner}/{repo}/events/{event}`. | +| `hub.callback` | `string` | A URI para receber as atualizações do tópico. | +| `hub.secret` | `string` | Uma chave secreta compartilhada que gera um HMAC de SHA1 do conteúdo do texto de saída. Você pode verificar se um push veio do GitHub, comparando o texto da solicitação sem processamento com o conteúdo do cabeçalho `X-Hub-Signature`. Você pode ver [a documentação do PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obter mais informações. | diff --git a/translations/pt-BR/content/rest/reference/scim.md b/translations/pt-BR/content/rest/reference/scim.md index d2524878f8..f8888bf566 100644 --- a/translations/pt-BR/content/rest/reference/scim.md +++ b/translations/pt-BR/content/rest/reference/scim.md @@ -14,7 +14,7 @@ A API do SCIM é usada pelos provedores de identidade (IdPs) habilitados pelo SC {% note %} -**Observação:** A API do SCIM está disponível apenas para organizações em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Observação:** A API do SCIM está disponível apenas para organizações em [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) com [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% endnote %} diff --git a/translations/pt-BR/content/rest/reference/teams.md b/translations/pt-BR/content/rest/reference/teams.md index e7a1251af7..ec1ea1b740 100644 --- a/translations/pt-BR/content/rest/reference/teams.md +++ b/translations/pt-BR/content/rest/reference/teams.md @@ -18,7 +18,7 @@ Esta API só está disponível para os integrantes autenticados da [organizaçã ## Discussões -A API de discussões de equipe permite que você obtenha, crie, edite e exclua postagens de discussão na página de uma equipe. Você pode usar discussões da equipe para ter conversas que não são específicas para um repositório ou projeto. Qualquer integrante da [organização](/rest/reference/orgs) da equipe pode criar e ler posts de discussão públicos. Para obter mais informações, consulte "[Sobre discussões de equipe](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)". Para aprender mais sobre comentários em uma publicação de discussão, consulte [a API de comentários de discussão em equipe](/rest/reference/teams#discussion-comments). Esta API só está disponível para os integrantes autenticados da organização da equipe. +A API de discussões de equipe permite que você obtenha, crie, edite e exclua postagens de discussão na página de uma equipe. Você pode usar discussões da equipe para ter conversas que não são específicas para um repositório ou projeto. Qualquer integrante da [organização](/rest/reference/orgs) da equipe pode criar e ler posts de discussão públicos. Para obter mais informações, consulte "[Sobre discussões de equipe](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender mais sobre comentários em uma publicação de discussão, consulte [a API de comentários de discussão em equipe](/rest/reference/teams#discussion-comments). Esta API só está disponível para os integrantes autenticados da organização da equipe. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -26,7 +26,7 @@ A API de discussões de equipe permite que você obtenha, crie, edite e exclua p ## Comentários da discussão -A API de comentários de discussão em equipe permite que você obtenha, crie, edite e exclua comentários de discussão em um post de [discussão de equipe](/rest/reference/teams#discussions). Qualquer integrante da organização da [organização](/rest/reference/orgs) da equipe pode criar e ler comentários em uma discussão pública. Para obter mais informações, consulte "[Sobre discussões de equipe](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)". Esta API só está disponível para os integrantes autenticados da organização da equipe. +A API de comentários de discussão em equipe permite que você obtenha, crie, edite e exclua comentários de discussão em um post de [discussão de equipe](/rest/reference/teams#discussions). Qualquer integrante da organização da [organização](/rest/reference/orgs) da equipe pode criar e ler comentários em uma discussão pública. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API só está disponível para os integrantes autenticados da organização da equipe. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -39,7 +39,7 @@ Esta API só está disponível para os integrantes autenticados da organização {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Observação:** Quando você tiver configurado a sincronização da equipe para uma equipe com o provedor de identidade (IdP) da sua organização, você receberá uma mensagem de erro se tentar usar a API para fazer alterações na associação da equipe. Se você tiver acesso para administrar a associação do grupo em seu IdP, você pode administrar a associação da equipe do GitHub através do seu provedor de identidade, que adiciona e remove automaticamente os integrantes da equipe em uma organização. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub". +**Observação:** Quando você tiver configurado a sincronização da equipe para uma equipe com o provedor de identidade (IdP) da sua organização, você receberá uma mensagem de erro se tentar usar a API para fazer alterações na associação da equipe. Se você tiver acesso para administrar a associação do grupo em seu IdP, você pode administrar a associação da equipe do GitHub através do seu provedor de identidade, que adiciona e remove automaticamente os integrantes da equipe em uma organização. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub". {% endnote %} @@ -54,7 +54,7 @@ Esta API só está disponível para os integrantes autenticados da organização A API de Sincronização da Equipe permite que você gerencie as conexões entre equipes de {% data variables.product.product_name %} e grupos de provedor de identidade externo (IdP). Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe. O token que você usa para efetuar a autenticação também deverá ser autorizado para uso com o provedor de IdP (SSO). Para obter mais informações, consulte "Autorizando um token de acesso pessoal para uso com uma organização de logon único SAML". -Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com a sincronização de equipe. A sincronização de equipe deve estar habilitada para usar a API de sincronização de equipe. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub". +Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com a sincronização de equipe. A sincronização de equipe deve estar habilitada para usar a API de sincronização de equipe. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub". {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/data/release-notes/2-20/0.yml b/translations/pt-BR/data/release-notes/2-20/0.yml index c7d94eed08..6b41ffc522 100644 --- a/translations/pt-BR/data/release-notes/2-20/0.yml +++ b/translations/pt-BR/data/release-notes/2-20/0.yml @@ -1,4 +1,5 @@ -date: '2020-02-11' +--- +date: '11-02-2020' sections: features: - 'Em um branch de repositório, os administradores do repositório podem rejeitar qualquer push que contenha um commit de merge, habilitando "Exigir histórico linear" ao usar [regras de proteção de branch](https://help.github. om/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' @@ -10,9 +11,9 @@ sections: - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - 'Quando um integrante de uma organização tentou visualizar um repositório público nessa organização, um prompt SSO poderia corromper a exibição da página. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' - - 'Ao visualizar o perfil de usuários, os links para as equipes dos usuários poderiam estar corrompidos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}' + - "Ao visualizar o perfil de usuários, os links para as equipes dos usuários poderiam estar corrompidos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" - 'Usuários com a função "manter" não conseguiram editar os tópicos do repositório. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' - - 'Um usuário que não é um administrador em uma organização receberá um erro 500 ao tentar acessar a página de inscrição. {% comment %} https://github. om/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}' + - "Um usuário que não é um administrador em uma organização receberá um erro 500 ao tentar acessar a página de inscrição. {% comment %} https://github. om/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" - 'O pop-up de histórico de edição não apareceria nos comentários do gist. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' - 'Foi possível registrar uma nova conta com um e-mail que já foi registrado. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' - 'Um serviço de armazenamento estava atingindo um limite de descritor de arquivos e deixando o kernel pendurado e outros serviços de log de erros. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/1.yml b/translations/pt-BR/data/release-notes/2-20/1.yml index 57f15491b1..997436f15e 100644 --- a/translations/pt-BR/data/release-notes/2-20/1.yml +++ b/translations/pt-BR/data/release-notes/2-20/1.yml @@ -1,4 +1,5 @@ -date: '2020-02-27' +--- +date: '27-02-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/10.yml b/translations/pt-BR/data/release-notes/2-20/10.yml index 32f502bf50..6639466791 100644 --- a/translations/pt-BR/data/release-notes/2-20/10.yml +++ b/translations/pt-BR/data/release-notes/2-20/10.yml @@ -1,14 +1,15 @@ -date: '2020-06-23' +--- +date: '23-06-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' bugs: - 'Eventos de registro excessivamente grandes podem gerar instabilidade no encaminhamento do registro quando UDP foi usado como o mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - 'A suspensão automática de um usuário através de SSO não foi concluída se o atributo de chaves SSH já tinha chaves associadas à conta do usuário. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}' + - "A suspensão automática de um usuário através de SSO não foi concluída se o atributo de chaves SSH já tinha chaves associadas à conta do usuário. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" - 'O hash de permissão do repositório da API REST não indicou acesso para membros de negócios que têm acesso a repositórios internos. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' - 'A visualização de uma descrição do aplicativo GitHub escrita em markdown não foi processada corretamente. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' - 'O log de auditoria não incluiu eventos de alteração de proteção de branch. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' - - 'Tentar atribuir a revisão de código a um integrante de uma equipe vazia geraria "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}' + - "Tentar atribuir a revisão de código a um integrante de uma equipe vazia geraria \"500 Internal Server Error\". {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" - 'A atribuição da revisão do código que usa o algoritmo de balanceamento de carga pode ser atribuída repetidamente ao mesmo integrante da equipe. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' known_issues: - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/11.yml b/translations/pt-BR/data/release-notes/2-20/11.yml index df5d0cc5c6..614faa3e9f 100644 --- a/translations/pt-BR/data/release-notes/2-20/11.yml +++ b/translations/pt-BR/data/release-notes/2-20/11.yml @@ -1,4 +1,5 @@ -date: '2020-07-09' +--- +date: '09-07-2020' sections: security_fixes: - '**MEDIUM:** foi atualizado para a versão 1.16.1 e dirigiu o CVE-2019-20372. (atualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/12.yml b/translations/pt-BR/data/release-notes/2-20/12.yml index 5d6a8d8270..a8cba0ded9 100644 --- a/translations/pt-BR/data/release-notes/2-20/12.yml +++ b/translations/pt-BR/data/release-notes/2-20/12.yml @@ -1,4 +1,5 @@ -date: '2020-07-21' +--- +date: '21-07-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/13.yml b/translations/pt-BR/data/release-notes/2-20/13.yml index 1c384fd554..b2b4624855 100644 --- a/translations/pt-BR/data/release-notes/2-20/13.yml +++ b/translations/pt-BR/data/release-notes/2-20/13.yml @@ -1,4 +1,5 @@ -date: '2020-08-11' +--- +date: '11-08-2020' sections: security_fixes: - '**CRÍTICO:** Uma vulnerabilidade de execução de código remoto foi identificada no GitHub Pages e permite que um invasor execute comandos como parte de criação de um site do GitHub Pages. Esse problema deve-se a uma dependência desatualizada e vulnerável usada no processo de criação de páginas. Para explorar essa vulnerabilidade, um invasor precisará de permissão para criar e construir um site do GitHub Pages na instância do GitHub Enterprise Server. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server. Para mitigar essa vulnerabilidade, a Kramdown foi atualizada para abordar o CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' @@ -8,7 +9,7 @@ sections: - 'Um erro de configuração do Cônsul impediu que algumas tarefas de segundo plano fossem processadas em instâncias autônomas. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' - 'O cálculo de alocação de memória de serviço poderia determinar uma alocação de memória incorreta ou ilimitada para um serviço resultando em desempenho de sistema pobre. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' - 'A plataforma de virtualização para sistemas oVirt KVM não foi detectada corretamente, gerando problemas durante as atualizações. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - 'A mensagem de erro para autenticação inválida com uma senha via linha de comando Git não preencheu a URL vinculada à adição do token apropriado ou chave SSH. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}' + - "A mensagem de erro para autenticação inválida com uma senha via linha de comando Git não preencheu a URL vinculada à adição do token apropriado ou chave SSH. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" - 'O GitHub Connect estava usando um ponto obsoleto da API do GitHub.com. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' - 'Os problemas não puderam ser classificados por *Atualizações recentes* nos repositórios migrados para uma nova instância. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/github/pull/149330 {% endcomment %}' - 'A página 404 continha links de contato e links status do GitHub.com na nota de rodapé. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/14.yml b/translations/pt-BR/data/release-notes/2-20/14.yml index 2e3e9d011a..1632366f38 100644 --- a/translations/pt-BR/data/release-notes/2-20/14.yml +++ b/translations/pt-BR/data/release-notes/2-20/14.yml @@ -1,4 +1,5 @@ -date: '2020-08-12' +--- +date: '12-08-2020' sections: bugs: - 'Resolveu um problema que poderia gerar alto uso da CPU ao gerar modelos de configuração do sistema. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/15.yml b/translations/pt-BR/data/release-notes/2-20/15.yml index aa3c664487..4c22ac4713 100644 Binary files a/translations/pt-BR/data/release-notes/2-20/15.yml and b/translations/pt-BR/data/release-notes/2-20/15.yml differ diff --git a/translations/pt-BR/data/release-notes/2-20/16.yml b/translations/pt-BR/data/release-notes/2-20/16.yml index 0d3b497e48..c580b0753f 100644 --- a/translations/pt-BR/data/release-notes/2-20/16.yml +++ b/translations/pt-BR/data/release-notes/2-20/16.yml @@ -1,8 +1,9 @@ -date: '2020-09-08' +--- +date: '08-09-2020' sections: bugs: - 'Uma verificação de saúde do serviço causou o crescimento da sessão, o que gerou um esgotamento do sistema de arquivos. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - 'A atualização que usa um hotpatch pode falhar com um erro: `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' + - "A atualização que usa um hotpatch pode falhar com um erro: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" known_issues: - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/17.yml b/translations/pt-BR/data/release-notes/2-20/17.yml index b6c66a9dc2..c6f9f2d6bb 100644 --- a/translations/pt-BR/data/release-notes/2-20/17.yml +++ b/translations/pt-BR/data/release-notes/2-20/17.yml @@ -1,4 +1,5 @@ -date: '2020-09-23' +--- +date: '23-09-2020' sections: security_fixes: - '**MÉDIO**: ImageMagick foi atualizado para o endereço [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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/18.yml b/translations/pt-BR/data/release-notes/2-20/18.yml index eabe2c16e2..bacfddb0c0 100644 --- a/translations/pt-BR/data/release-notes/2-20/18.yml +++ b/translations/pt-BR/data/release-notes/2-20/18.yml @@ -1,4 +1,5 @@ -date: '2020-10-09' +--- +date: '09-10-2020' sections: security_fixes: - 'Um usuário cujo nome de usuário de diretório de LDAP padronizado em um login da conta GHES existente pode efetuar a autenticação na conta existente. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/19.yml b/translations/pt-BR/data/release-notes/2-20/19.yml index a84929c005..544072c47b 100644 --- a/translations/pt-BR/data/release-notes/2-20/19.yml +++ b/translations/pt-BR/data/release-notes/2-20/19.yml @@ -1,4 +1,5 @@ -date: '2020-10-20' +--- +date: '20-10-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/2.yml b/translations/pt-BR/data/release-notes/2-20/2.yml index 17e5bd727b..073a9d978b 100644 --- a/translations/pt-BR/data/release-notes/2-20/2.yml +++ b/translations/pt-BR/data/release-notes/2-20/2.yml @@ -1,4 +1,5 @@ -date: '2020-03-10' +--- +date: '10-03-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/20.yml b/translations/pt-BR/data/release-notes/2-20/20.yml index 0d04588902..7561596a86 100644 --- a/translations/pt-BR/data/release-notes/2-20/20.yml +++ b/translations/pt-BR/data/release-notes/2-20/20.yml @@ -1,8 +1,9 @@ -date: '2020-11-03' +--- +date: '03-11-2020' sections: security_fixes: - '**MÉDIO:** Alto uso de CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN resultando em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - '**BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}' + - "**BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" - 'Os pacotes foram atualizados para as últimas versões de segurança. {% 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: - 'Os usuários suspensos foram incluídos na lista de usuários sugeridos, ocultando potencialmente usuários não suspensos. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/21.yml b/translations/pt-BR/data/release-notes/2-20/21.yml index b73520361e..a714c41751 100644 --- a/translations/pt-BR/data/release-notes/2-20/21.yml +++ b/translations/pt-BR/data/release-notes/2-20/21.yml @@ -1,4 +1,5 @@ -date: '2020-11-17' +--- +date: '17-11-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/22.yml b/translations/pt-BR/data/release-notes/2-20/22.yml index ba494ad034..02d9462e44 100644 --- a/translations/pt-BR/data/release-notes/2-20/22.yml +++ b/translations/pt-BR/data/release-notes/2-20/22.yml @@ -1,4 +1,5 @@ -date: '2020-12-03' +--- +date: '03-12-2020' sections: bugs: - 'O serviço de autorização foi detectado como não saudável devido a uma condição de raça no bootstrap que gerou a reinicialização do serviço. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/23.yml b/translations/pt-BR/data/release-notes/2-20/23.yml index efd84f457e..0e64bf454c 100644 --- a/translations/pt-BR/data/release-notes/2-20/23.yml +++ b/translations/pt-BR/data/release-notes/2-20/23.yml @@ -1,4 +1,5 @@ -date: '2020-12-17' +--- +date: '17-12-2020' sections: security_fixes: - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/3.yml b/translations/pt-BR/data/release-notes/2-20/3.yml index c777efa565..7799117d09 100644 --- a/translations/pt-BR/data/release-notes/2-20/3.yml +++ b/translations/pt-BR/data/release-notes/2-20/3.yml @@ -1,4 +1,5 @@ -date: '2020-03-12' +--- +date: '12-03-2020' sections: bugs: - 'As atualizações e as atualizações de configurações poderiam falhar se as configurações em segundo plano do trabalhador tivessem sido personalizadas. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/4.yml b/translations/pt-BR/data/release-notes/2-20/4.yml index 4722d8ab26..1ef5b13261 100644 --- a/translations/pt-BR/data/release-notes/2-20/4.yml +++ b/translations/pt-BR/data/release-notes/2-20/4.yml @@ -1,4 +1,5 @@ -date: '2020-03-25' +--- +date: '25-03-2020' sections: bugs: - 'As solicitações de autenticação do SAML e Metadados não foram estritamente codificadas, o que fez com que alguns provedores de identidade não processem corretamente as solicitações de autenticação iniciadas pelo provedor de serviços. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/5.yml b/translations/pt-BR/data/release-notes/2-20/5.yml index ee855bc2c7..384a951894 100644 --- a/translations/pt-BR/data/release-notes/2-20/5.yml +++ b/translations/pt-BR/data/release-notes/2-20/5.yml @@ -1,4 +1,5 @@ -date: '2020-04-07' +--- +date: '07-04-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/6.yml b/translations/pt-BR/data/release-notes/2-20/6.yml index 46d74deacc..1cba614c8a 100644 --- a/translations/pt-BR/data/release-notes/2-20/6.yml +++ b/translations/pt-BR/data/release-notes/2-20/6.yml @@ -1,4 +1,5 @@ -date: '2020-04-23' +--- +date: '23-04-2020' sections: security_fixes: - '**ALTO**: O OpenSSL foi atualizado para o endereço [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 %}' @@ -9,12 +10,12 @@ sections: - 'O usuário do git não tinha permissões para invocar os processos necessários para converter repositórios existentes usando Subversion, do formato da v4 ao LRS da v3. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' - 'Uma incompatibilidade nas configurações do MySQL pode fazer com que os backups falhem em grandes instalações. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' - 'Ao atualizar de versões anteriores, trabalhadores em segundo plano às vezes não seriam gerados, o que impediu as funcionalidades essenciais como mesclar pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' - - 'Quando uma licença do GitHub Enterprise Server continha caracteres diferentes dos da ASCII, as solicitações do tipo "GET" para o ponto de extremidade `/setup/api/settings` da API do console de gerenciamento resultaria em um erro de servidor interno. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}' + - "Quando uma licença do GitHub Enterprise Server continha caracteres diferentes dos da ASCII, as solicitações do tipo \"GET\" para o ponto de extremidade `/setup/api/settings` da API do console de gerenciamento resultaria em um erro de servidor interno. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" - 'O console de recuperação solicitaria uma senha de raiz, mesmo que a conta raiz tenha sido bloqueada. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' - 'Um arquivo de CODEOWNERS com uma marca de ordem inicial UTF-8 fez com que todas as regras de todos os códigos fossem ignoradas. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' changes: - 'Quando o trabalho do cron do orchestrator-cliente falhou, vários e-mails foram enviados para a conta raiz. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - - 'Quando um provedor de identidade externo controlou o status de administrador do site do usuário, os usuários não puderem ser rebaixados por meio do utilitário da linha de comando. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}' + - "Quando um provedor de identidade externo controlou o status de administrador do site do usuário, os usuários não puderem ser rebaixados por meio do utilitário da linha de comando. {% 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: - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/7.yml b/translations/pt-BR/data/release-notes/2-20/7.yml index 6623676cc2..8b5afc19ff 100644 --- a/translations/pt-BR/data/release-notes/2-20/7.yml +++ b/translations/pt-BR/data/release-notes/2-20/7.yml @@ -1,4 +1,5 @@ -date: '2020-05-05' +--- +date: '05-05-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/8.yml b/translations/pt-BR/data/release-notes/2-20/8.yml index 3788df27e8..4b9ec32b92 100644 --- a/translations/pt-BR/data/release-notes/2-20/8.yml +++ b/translations/pt-BR/data/release-notes/2-20/8.yml @@ -1,4 +1,5 @@ -date: '2020-05-19' +--- +date: '19-05-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/9.yml b/translations/pt-BR/data/release-notes/2-20/9.yml index e96c186e4d..b88da63dd3 100644 --- a/translations/pt-BR/data/release-notes/2-20/9.yml +++ b/translations/pt-BR/data/release-notes/2-20/9.yml @@ -1,4 +1,5 @@ -date: '2020-06-02' +--- +date: '02-06-2020' sections: security_fixes: - '**ALTO:** Uma vulnerabilidade de controle de acesso imprópria foi identificada na API do GitHub Enterprise Server que permitiu que um integrante da organização aumentasse as permissões e recebesse acesso a repositórios não autorizados dentro de uma organização. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server anteriores à versão 2.21. Emitimos [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) em resposta a este problema. A vulnerabilidade foi relatada por meio do [programa Bug Bounty do GitHub](https://bounty. ithub.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/0.yml b/translations/pt-BR/data/release-notes/2-21/0.yml index 90c55c2f21..3479ae8f78 100644 --- a/translations/pt-BR/data/release-notes/2-21/0.yml +++ b/translations/pt-BR/data/release-notes/2-21/0.yml @@ -1,4 +1,5 @@ -date: '2020-06-09' +--- +date: '09-06-2020' sections: features: - 'Os usuários podem [gerenciar notificações](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) em problemas, pull requests e outros assuntos ao navegar a partir de uma notificação na web. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' @@ -13,13 +14,13 @@ sections: security_fixes: - 'Uma vulnerabilidade de controle de acesso imprópria foi identificada na API do GitHub Enterprise Server que permitiu que um integrante da organização aumentasse as permissões e recebesse acesso a repositórios não autorizados dentro de uma organização. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server anteriores à versão 2.21. Emitimos [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) em resposta a este problema. A vulnerabilidade foi relatada por meio do [programa Bug Bounty do GitHub](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' bugs: - - 'Se um usuário com acesso push minimizou o comentário de outro usuário, o autor do comentário poderia minimizá-lo mesmo se não tivesse privilégios suficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}' + - "Se um usuário com acesso push minimizou o comentário de outro usuário, o autor do comentário poderia minimizá-lo mesmo se não tivesse privilégios suficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" - 'Os usuários podem acidentalmente fazer merge para mestre a partir do editor de modelos de problemas e blob. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - 'Quando um usuário exclui uma conta do GitHub, os registros do log de auditoria não mostraram corretamente os registros de remoção da organização. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - 'O avatar do gist para o usuário atual faria um link para uma URL inexistente. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - 'A aba de contagem de repositórios da organização não incluiu repositórios internos. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - 'Ao transferir um repositório, clicar no botão "Mostrar Todas as Equipes" gerou um erro 500. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - 'Os nomes de arquivos longos podem gerar um excesso de fluxo de problemas ao mostrar a etiqueta "Alterado desde a última vista" ou a alternância de diff de "Mostrar enriquecido" na vista dos arquivos diff. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}' + - "Os nomes de arquivos longos podem gerar um excesso de fluxo de problemas ao mostrar a etiqueta \"Alterado desde a última vista\" ou a alternância de diff de \"Mostrar enriquecido\" na vista dos arquivos diff. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" - 'Os cartões de vista virtual para equipes da organização relataram mal o tamanho do integrante. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - 'A janela pop-up de comentário do pull request teve um problema de deslocamento. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - 'Haproxy pode saturar-se, gerando lentidão nas operações do git. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' @@ -69,4 +70,4 @@ sections: - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - Ocorre uma falha na configuração da permissão de um repositório para "Triagem" ou "Manter" com uma mensagem de erro. + - "Ocorre uma falha na configuração da permissão de um repositório para \"Triagem\" ou \"Manter\" com uma mensagem de erro." diff --git a/translations/pt-BR/data/release-notes/2-21/1.yml b/translations/pt-BR/data/release-notes/2-21/1.yml index 0f2837e40e..c357b1b49e 100644 --- a/translations/pt-BR/data/release-notes/2-21/1.yml +++ b/translations/pt-BR/data/release-notes/2-21/1.yml @@ -1,11 +1,12 @@ -date: '2020-06-23' +--- +date: '23-06-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' bugs: - 'Eventos de registro excessivamente grandes podem gerar instabilidade no encaminhamento do registro quando UDP foi usado como o mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - 'O serviço de comunicação interno usado para acessar o MySQL pode ser reiniciado com mais frequência do que o necessário, incluindo parte do processo de atualização, que pode fazer com que a atualização falhe parcialmente. Reduzimos a taxa de reinicialização e tornamos o código mais robusto. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' - - 'A suspensão automática de um usuário através de SSO não foi concluída se o atributo de chaves SSH já tinha chaves associadas à conta do usuário. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}' + - "A suspensão automática de um usuário através de SSO não foi concluída se o atributo de chaves SSH já tinha chaves associadas à conta do usuário. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" - 'O hash de permissão do repositório da API REST não indicou acesso para membros de negócios que têm acesso a repositórios internos. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' - 'A política da conta corporativa "Exclusão de problema do repositório" não refletiu a configuração salva no momento. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - 'O log de auditoria não incluiu eventos de alteração de proteção de branch. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' @@ -17,4 +18,4 @@ sections: - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - Ocorre uma falha na configuração da permissão de um repositório para "Triagem" ou "Manter" com uma mensagem de erro. + - "Ocorre uma falha na configuração da permissão de um repositório para \"Triagem\" ou \"Manter\" com uma mensagem de erro." diff --git a/translations/pt-BR/data/release-notes/2-21/10.yml b/translations/pt-BR/data/release-notes/2-21/10.yml index 913683d235..1cd72dc0ee 100644 --- a/translations/pt-BR/data/release-notes/2-21/10.yml +++ b/translations/pt-BR/data/release-notes/2-21/10.yml @@ -1,4 +1,5 @@ -date: '2020-10-20' +--- +date: '20-10-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/11.yml b/translations/pt-BR/data/release-notes/2-21/11.yml index 2e0e4a0f46..fd8d06c1a2 100644 --- a/translations/pt-BR/data/release-notes/2-21/11.yml +++ b/translations/pt-BR/data/release-notes/2-21/11.yml @@ -1,8 +1,9 @@ -date: '2020-11-03' +--- +date: '03-11-2020' sections: security_fixes: - '**MÉDIO:** Alto uso de CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN resultando em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - '**BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}' + - "**BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" - 'Os pacotes foram atualizados para as últimas versões de segurança. {% 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: - 'Editar templates de problemas com nomes de arquivos que contenham caracteres diferentes de ASCII gerariam uma falha com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/12.yml b/translations/pt-BR/data/release-notes/2-21/12.yml index ac64ac8c15..621a6b7142 100644 --- a/translations/pt-BR/data/release-notes/2-21/12.yml +++ b/translations/pt-BR/data/release-notes/2-21/12.yml @@ -1,4 +1,5 @@ -date: '2020-11-17' +--- +date: '17-11-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/13.yml b/translations/pt-BR/data/release-notes/2-21/13.yml index 991a21b794..b04c44d73d 100644 --- a/translations/pt-BR/data/release-notes/2-21/13.yml +++ b/translations/pt-BR/data/release-notes/2-21/13.yml @@ -1,4 +1,5 @@ -date: '2020-12-03' +--- +date: '03-12-2020' sections: bugs: - 'O serviço de autorização foi detectado como não saudável devido a uma condição de raça no bootstrap que gerou a reinicialização do serviço. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/14.yml b/translations/pt-BR/data/release-notes/2-21/14.yml index d62558dbb0..8a17c6d7c5 100644 --- a/translations/pt-BR/data/release-notes/2-21/14.yml +++ b/translations/pt-BR/data/release-notes/2-21/14.yml @@ -1,4 +1,5 @@ -date: '2020-12-17' +--- +date: '17-12-2020' sections: security_fixes: - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/16.yml b/translations/pt-BR/data/release-notes/2-21/16.yml index 3dca24b7d2..8a7f9726b2 100644 --- a/translations/pt-BR/data/release-notes/2-21/16.yml +++ b/translations/pt-BR/data/release-notes/2-21/16.yml @@ -1,13 +1,14 @@ -date: '2021-03-16' +--- +date: '16-03-2021' sections: security_fixes: - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.' + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. - As regras personalizadas de firewall não são mantidas durante uma atualização. - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.' + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. - - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.' + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. - Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. diff --git a/translations/pt-BR/data/release-notes/2-21/18.yml b/translations/pt-BR/data/release-notes/2-21/18.yml new file mode 100644 index 0000000000..f05f605186 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/18.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - As regras personalizadas de firewall não são mantidas durante uma atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - Os alertas de segurança não são relatados ao fazer push em um repositório na linha de comando. diff --git a/translations/pt-BR/data/release-notes/2-21/2.yml b/translations/pt-BR/data/release-notes/2-21/2.yml index 0c98556011..77b3f79887 100644 --- a/translations/pt-BR/data/release-notes/2-21/2.yml +++ b/translations/pt-BR/data/release-notes/2-21/2.yml @@ -1,4 +1,5 @@ -date: '2020-07-09' +--- +date: '09-07-2020' sections: security_fixes: - '**MEDIUM:** foi atualizado para a versão 1.16.1 e dirigiu o CVE-2019-20372. (atualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' @@ -17,4 +18,4 @@ sections: - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - Ocorre uma falha na configuração da permissão de um repositório para "Triagem" ou "Manter" com uma mensagem de erro. + - "Ocorre uma falha na configuração da permissão de um repositório para \"Triagem\" ou \"Manter\" com uma mensagem de erro." diff --git a/translations/pt-BR/data/release-notes/2-21/3.yml b/translations/pt-BR/data/release-notes/2-21/3.yml index 3caf7cb599..3ac8740709 100644 --- a/translations/pt-BR/data/release-notes/2-21/3.yml +++ b/translations/pt-BR/data/release-notes/2-21/3.yml @@ -1,11 +1,12 @@ -date: '2020-07-21' +--- +date: '21-07-2020' sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% 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: - 'Os gráficos do monitor do console de gerenciamento às vezes não seriam exibidos corretamente em telas maiores. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - 'Não era possível usar o fluxo de criação do manifesto do aplicativo GitHub em alguns cenários quando uma política de Cookie do SameSite foi aplicada. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - 'Em algumas circunstâncias, o acesso à página de "Explorar" geraria um erro no aplicativo. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}' + - "Em algumas circunstâncias, o acesso à página de \"Explorar\" geraria um erro no aplicativo. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" known_issues: - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' @@ -14,4 +15,4 @@ sections: - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - Ocorre uma falha na configuração da permissão de um repositório para "Triagem" ou "Manter" com uma mensagem de erro. + - "Ocorre uma falha na configuração da permissão de um repositório para \"Triagem\" ou \"Manter\" com uma mensagem de erro." diff --git a/translations/pt-BR/data/release-notes/2-21/4.yml b/translations/pt-BR/data/release-notes/2-21/4.yml index 2563e00f2a..47e459fbb8 100644 --- a/translations/pt-BR/data/release-notes/2-21/4.yml +++ b/translations/pt-BR/data/release-notes/2-21/4.yml @@ -1,4 +1,5 @@ -date: '2020-08-11' +--- +date: '11-08-2020' sections: security_fixes: - '**CRÍTICO:** Uma vulnerabilidade de execução de código remoto foi identificada no GitHub Pages e permite que um invasor execute comandos como parte de criação de um site do GitHub Pages. Esse problema deve-se a uma dependência desatualizada e vulnerável usada no processo de criação de páginas. Para explorar essa vulnerabilidade, um invasor precisará de permissão para criar e construir um site do GitHub Pages na instância do GitHub Enterprise Server. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server. Para mitigar essa vulnerabilidade, a Kramdown foi atualizada para abordar o CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' @@ -8,7 +9,7 @@ sections: - 'Um erro de configuração do Cônsul impediu que algumas tarefas de segundo plano fossem processadas em instâncias autônomas. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' - 'O cálculo de alocação de memória de serviço poderia determinar uma alocação de memória incorreta ou ilimitada para um serviço resultando em desempenho de sistema pobre. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' - 'A plataforma de virtualização para sistemas oVirt KVM não foi detectada corretamente, gerando problemas durante as atualizações. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - 'A mensagem de erro para autenticação inválida com uma senha via linha de comando do Git não preencheu a URL vinculada à adição do token apropriado ou chave SSH. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}' + - "A mensagem de erro para autenticação inválida com uma senha via linha de comando do Git não preencheu a URL vinculada à adição do token apropriado ou chave SSH. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" - 'Criar um problema em um repositório de usuário que usa o recurso de modelo do problema pode falhar com um erro de servidor interno. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - 'Ocorreu uma falha ao acessar a seção *Explorar* com um erro de servidor interno de 500. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - 'Os problemas não puderam ser classificados por *Atualizações recentes* nos repositórios migrados para uma nova instância. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/github/pull/149330 {% endcomment %}' @@ -24,4 +25,4 @@ sections: - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - Ocorre uma falha na configuração da permissão de um repositório para "Triagem" ou "Manter" com uma mensagem de erro. + - "Ocorre uma falha na configuração da permissão de um repositório para \"Triagem\" ou \"Manter\" com uma mensagem de erro." diff --git a/translations/pt-BR/data/release-notes/2-21/5.yml b/translations/pt-BR/data/release-notes/2-21/5.yml index b27347abed..997e7d7350 100644 --- a/translations/pt-BR/data/release-notes/2-21/5.yml +++ b/translations/pt-BR/data/release-notes/2-21/5.yml @@ -1,4 +1,5 @@ -date: '2020-08-12' +--- +date: '12-08-2020' sections: bugs: - 'Resolveu um problema que poderia gerar alto uso da CPU ao gerar modelos de configuração do sistema. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' @@ -12,4 +13,4 @@ sections: - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - Ocorre uma falha na configuração da permissão de um repositório para "Triagem" ou "Manter" com uma mensagem de erro. + - "Ocorre uma falha na configuração da permissão de um repositório para \"Triagem\" ou \"Manter\" com uma mensagem de erro." diff --git a/translations/pt-BR/data/release-notes/2-21/6.yml b/translations/pt-BR/data/release-notes/2-21/6.yml index 8638d1d9cd..d534c83a6a 100644 Binary files a/translations/pt-BR/data/release-notes/2-21/6.yml and b/translations/pt-BR/data/release-notes/2-21/6.yml differ diff --git a/translations/pt-BR/data/release-notes/2-21/7.yml b/translations/pt-BR/data/release-notes/2-21/7.yml index ddb00ff76d..2ecf01159e 100644 --- a/translations/pt-BR/data/release-notes/2-21/7.yml +++ b/translations/pt-BR/data/release-notes/2-21/7.yml @@ -1,9 +1,10 @@ -date: '2020-09-08' +--- +date: '08-09-2020' sections: bugs: - 'Uma verificação de saúde do serviço causou o crescimento da sessão, o que gerou um esgotamento do sistema de arquivos. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - 'A atualização que usa um hotpatch pode falhar com um erro: `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' - - Configurar a permissão de um repositório para "Triagem" ou "Manter" não irá mais falhar. + - "A atualização que usa um hotpatch pode falhar com um erro: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + - "Configurar a permissão de um repositório para \"Triagem\" ou \"Manter\" não irá mais falhar." known_issues: - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/8.yml b/translations/pt-BR/data/release-notes/2-21/8.yml index 13afccece3..5a824b8232 100644 --- a/translations/pt-BR/data/release-notes/2-21/8.yml +++ b/translations/pt-BR/data/release-notes/2-21/8.yml @@ -1,4 +1,5 @@ -date: '2020-09-23' +--- +date: '23-09-2020' sections: security_fixes: - '**MÉDIO**: ImageMagick foi atualizado para o endereço [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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/9.yml b/translations/pt-BR/data/release-notes/2-21/9.yml index f909cb0399..fd7020fff4 100644 --- a/translations/pt-BR/data/release-notes/2-21/9.yml +++ b/translations/pt-BR/data/release-notes/2-21/9.yml @@ -1,4 +1,5 @@ -date: '2020-10-09' +--- +date: '09-10-2020' sections: security_fixes: - 'Um usuário cujo nome de usuário de diretório de **LDAP** padronizado em um login da conta GHES existente pode efetuar a autenticação na conta existente. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' 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 55e200422f..bd060cff90 100644 --- a/translations/pt-BR/data/release-notes/2-22/0.yml +++ b/translations/pt-BR/data/release-notes/2-22/0.yml @@ -1,71 +1,84 @@ +--- intro: O GitHub está animado para apresentar o GitHub Enterprise Server 2.2.0. -date: '2020-09-23' +date: '23-09-2020' sections: features: - - heading: GitHub Actions Beta + - + heading: GitHub Actions Beta notes: - | [GitHub Actions](https://github.com/features/actions) é uma solução poderosa e flexível para CI/CD e automação de fluxo de trabalho. O GitHub Actions no Enterprise Server inclui ferramentas que ajudam você a gerenciar o serviço incluindo métricas chave no Console de Gerenciamento, logs de auditoria e controles de acesso para ajudar você a controlar a implementação. Você precisará fornecer seu próprio [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) e executores para o GitHub Actions. AWS S3, Azure Blob Storage e MinIO são compatíveis. Revise os [requisitos mínimos atualizados para sua plataforma](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de ativar o GitHub Actions. Para saber mais, entre em contato com a equipe do GitHub Sales ou [inscreva-se para o beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - - heading: GitHub Packages Beta + - + heading: GitHub Packages Beta notes: - | [GitHub Packages](https://github.com/features/packages) é um serviço de hospedagem de pacotes, integrado nativamente com as APIs, ações e webhooks do GitHub. Crie um [fluxo de trabalho de ponta a ponta para o DevOps](https://docs.github.com/en/enterprise/2. 2/admin/pacotes/configuring-packages-support-for-your-enterpris) que inclui seu código, integração contínua e soluções de implantação. Os backends de armazenamento compatíveis incluem AWS S3 e MinIO com suporte para o Azure blob em uma versão futura. Observe que o suporte atual ao Docker será substituído por uma versão beta do novo Registro de Contêiner do GitHub na próxima versão. Revise os [requisitos mínimos atualizados para sua plataforma](https://docs.github.com/en/enterprise/2. 2/admin/installation/setting-up-a-github-enterprise-server-instance) antes de ativar o GitHub Packages. Para saber mais, entre em contato com a equipe do GitHub Sales ou [inscreva-se no beta](https://resources. ithub.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - - heading: Varredura avançada de segurança de código beta + - + heading: Varredura avançada de segurança de código beta notes: - | [Varredura avançada de código de segurança do GitHub](https://github.com/features/security) é um ambiente de teste de segurança para aplicativos estáticos nativos do GitHub nativo (SAST). Encontre facilmente vulnerabilidades de segurança antes que atinjam a produção, tudo desenvolvido pelo mais poderoso motor de análise de código do mundo: CodeQL. Os administradores que usam a Segurança Avançada do GitHub podem [inscrever-se em](https://resources.github.com/beta-signup/) e [enable](https://docs.github. om/pt/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) o Beta de varredura avançada de código de segurança GitHub. Revise os [requisitos mínimos atualizados para sua plataforma](https://docs.github. om/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de ativar a varredura avançada de código código de segurança GitHub. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - - heading: Redirecionamento de pull request + - + heading: Redirecionamento de pull request notes: - | Quando um [branch do cabeçalho do pull request](https://docs.github.com/en/enterprise/2. 2/usuário/github/colaboração-with-issues-and-pull-requests/about-branches#working-with-branches) é mesclado e excluído, todos os outros pull requests no mesmo repositório que apontam para este branch agora são redirecionados para o branch de base do pull request mesclado. Anteriormente, esses pull requests eram fechados. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} - - heading: Suspender e cancelar a suspensão da instalação de aplicativos + - + heading: Suspender e cancelar a suspensão da instalação de aplicativos notes: - | Os administradores e usuários podem [suspender o acesso de qualquer aplicativo do GitHub](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) durante o tempo necessário e [cancelar a suspensão do aplicativo](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) no comando por meio das das Configurações e da API. Os aplicativos suspensos não podem acessar a API do GitHub ou eventos de webhook. Você pode fazer isso em vez de desinstalar um aplicativo, que cancela a autorização de todos os usuários. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' - - heading: Desempenho aprimorado em grande escala + - + heading: Desempenho aprimorado em grande escala notes: - | Nós revisamos a abordagem que adotamos para agendar a manutenção da rede para repositórios, garantindo que os grandes monorrepositórios sejam capazes de evitar os estados de falha. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github. om/github/git-protocols/issues/94 {% endcomment %}'' As réplicas passivas agora são [compatíveis e configuráveis nas implantações de cluster do GitHub Enterprise Server](https://docs.github.com/en/enterprise/2. 2/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). Essas alterações permitirão falhas mais rápidas, reduzindo RTO e RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - - heading: Visualizar todos os seus usuários + - + heading: Visualizar todos os seus usuários notes: - | Para equipes excepcionalmente grandes, os administradores podem [ajustar o padrão máximo de 1.500 para as listas de usuários](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: Alterações na administração + - + heading: Alterações na administração notes: - - 'Os trabalhadores compartilhados foram habilitados para tornar as atualizações ao vivo mais resilientes, compartilhando conexões entre as abas. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %}' - - 'O link "Suporte ao Contato" na página de erro `50x` agora vincula ao e-mail de suporte ou link configurado no Console de Gerenciamento. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %}' + - Os trabalhadores compartilhados foram habilitados para tornar as atualizações ao vivo mais resilientes, compartilhando conexões entre as abas. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - O link "Suporte ao Contato" na página de erro `50x` agora vincula ao e-mail de suporte ou link configurado no Console de Gerenciamento. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} - 'Agora é possível [gerenciar anúncios e datas de expiração globais pelas configurações da conta corporativa](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/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %}' - - 'Agora você pode [isentar certos usuários do limite de taxa da API padrão configurado no console de gerenciamento](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), se necessário. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %}' - - 'Agora os administradores do repositório podem [definir seus repositórios como qualquer opção de visibilidade disponível](https://docs.github.com/en/enterprise/2.22/user/administering-a-repository/setting-repository-visibility) a partir de um único diálogo nas configurações do repositório. Anteriormente, você tinha de navegar por seções, botões e caixas de diálogo separadas para alternar entre público e privado e entre privado e interno. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %}' - - 'Um novo link de configurações corporativasno menu suspenso do usuário facilita a navegação nas Configurações da Conta Corporativa. {% 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 %}' - - 'O antigo link "Central de Adminstraão" na página de /stafftools foi removido. O link "Empresa" agora é a melhor maneira de acessar a Conta Corporativa a partir da página /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %}' - - 'O item do submenu de Opções nas configurações da Conta Corporativa foi transferido da seção de Configurações para a seção de Políticas. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %}' + - Agora você pode [isentar certos usuários do limite de taxa da API padrão configurado no console de gerenciamento](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), se necessário. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Agora os administradores do repositório podem [definir seus repositórios como qualquer opção de visibilidade disponível](https://docs.github.com/en/enterprise/2.22/user/administering-a-repository/setting-repository-visibility) a partir de um único diálogo nas configurações do repositório. Anteriormente, você tinha de navegar por seções, botões e caixas de diálogo separadas para alternar entre público e privado e entre privado e interno. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - Um novo link de configurações corporativasno menu suspenso do usuário facilita a navegação nas Configurações da Conta Corporativa. {% 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 %} + - O antigo link "Central de Adminstraão" na página de /stafftools foi removido. O link "Empresa" agora é a melhor maneira de acessar a Conta Corporativa a partir da página /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - O item do submenu de Opções nas configurações da Conta Corporativa foi transferido da seção de Configurações para a seção de Políticas. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} - '[Acessar recursos usando um token de acesso pessoal ou chave SSH agora conta como atividade de usuário](https://docs.github.com/en/enterprise/2.22/admin/user-management/management/managing-dormant-users). Isso alivia os administradores do trabalho de filtrar determinados usuários dos relatórios de dormência do usuário e torna mais seguro usar o botão "Suspender todos" sem suspender, acidentalmente, usuários que acessaram o GitHub de forma apenas leitura através das APIs com um Token de Acesso Pessoal (PAT) ou chave 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: Alterações de segurança + - + heading: Alterações de segurança notes: - - 'Os códigos de recuperação de dois fatores não podem mais ser usados durante o processo de autenticação de dois fatores. As senhas de uso único são os únicos valores aceitáveis. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %}' - - 'Quando um usuário é conectado ao GitHub Enterprise Server através de um único logon, a [seleção de visibilidade padrão do repositório é 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 %}' - - 'Agora os proprietários dos aplicativos GitHub podem escolher que os seus [tokens de acesso do usuário para servidor expirem após 8 horas](https://developer.github. om/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), para ajudar a aplicar rotação regular do token e reduzir o impacto de um token comprometido. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %}' - - heading: Alterações de desenvolvedor + - Os códigos de recuperação de dois fatores não podem mais ser usados durante o processo de autenticação de dois fatores. As senhas de uso único são os únicos valores aceitáveis. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - Quando um usuário é conectado ao GitHub Enterprise Server através de um único logon, a [seleção de visibilidade padrão do repositório é 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 %} + - Agora os proprietários dos aplicativos GitHub podem escolher que os seus [tokens de acesso do usuário para servidor expirem após 8 horas](https://developer.github. om/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), para ajudar a aplicar rotação regular do token e reduzir o impacto de um token comprometido. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Alterações de desenvolvedor notes: - '[A interface de usuário do GitHub passou por uma atualização de design](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), e a página inicial dos repositórios foi reprojetada, incluindo um layout responsivo e uma melhor experiência de web móvel. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - 'No menu suspenso do repositório "Clonar com SSH", os usuários agora serão notificados se não tiverem nenhuma configuração de chaves. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %}' + - No menu suspenso do repositório "Clonar com SSH", os usuários agora serão notificados se não tiverem nenhuma configuração de chaves. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} - 'Agora, os commits são ordenados cronologicamente na linha do tempo do pull request e na aba commits. Esta nova ordem também é refletida na API REST de ["Lista de commits em um pull request"](https://docs.github.com/en/enterprise/2. 2/user/rest/reference/pulls#list-commits-on-a-pull-request) e no [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 %}' - - 'Agora os usuários podem [definir o padrão do tom de tema padrão para resultados de preenchimento automático de emojis](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) nas áreas de texto de comentário. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %}' + - Agora os usuários podem [definir o padrão do tom de tema padrão para resultados de preenchimento automático de emojis](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) nas áreas de texto de comentário. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) melhora o destaque da sintaxe e agora é a biblioteca padrão usada para análise de linguagens. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - heading: Os usuários e as organizações podem adicionar nomes de usuários do Twitter aos seus perfis do GitHub + - + heading: Os usuários e as organizações podem adicionar nomes de usuários do Twitter aos seus perfis do GitHub notes: - '[Os desenvolvedores e organizações agora podem adicionar seu nome de usuário do Twitter ao seu perfil](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: Alterações de API + - + heading: Alterações de API notes: - | #### Pré-visualizações graduadas @@ -77,7 +90,8 @@ sections: #### Alterações no esquema do GraphQL * [As mudanças de esquema do GraphQL](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) incluem alterações retrocompatíveis, pré-visualizações do esquema e futuras alterações significativas. - - heading: Alterações do controlador de VMware Network + - + heading: Alterações do controlador de VMware Network notes: - | O tipo adaptador de rede padrão do GitHub Enterprise Server para clientes do VMware foi alterado de E1000 para VMXNET3, começando com a versão 2.22.0. Ao fazer a atualização de uma versão anterior para 2.22.0 ou mais recente, se um adaptador de rede E1000 for detectado durante a verificação de pré-atualização, a seguinte mensagem será exibida na linha de comando: @@ -90,36 +104,40 @@ sections: O administrador pode optar por atualizar o tipo de adaptador de rede para VMXNET3 antes ou após a atualização do GitHub Enterprise Server. O aplicativo virtual terá de ser encerrado para realizar esta alteração. Os clientes devem seguir as etapas recomendadas do VMware para [alterar a configuração do adaptador de rede da máquina virtual](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin. oc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) para VMXNET3. Observe que o `VMXNET3` não será uma opção se a versão do sistema operacional do aplicativo virtual estiver definida como `Other Linux (64-bit)`. Nesse caso, a versão do OS deve ser alterada primeiro `Other Linux (64-bit)` para `Other 2.6.x Linux (64-bit)` ou, se disponível, `Debian GNU/Linux 9`. Recomendamos testar essas alterações em uma [instância de preparação](https://docs.github. om/pt/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) antes de ser executada em uma produção do GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - - 'A página de stafftools de equipe para visualizar o colaborador pendente mostrou um `500 Internal Server Error` quando houve um convite de e-mail pendente. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %}' - - 'A verificação de integridade do repositório na stafftools pode gerar resultados incorretos em repositórios ocupados. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %}' - - 'Um usuário conectado que tenta aceitar um convite de e-mail poderia obter um erro `404 Not Found`. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %}' - - 'Se um usuário acessar um repositório cujo nome foi iniciado com "repositórios", ele será direcionado a aba "Repositórios" do proprietário em vez de chegar à página de visão geral do repositório. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %}' - - 'As etiquetas na linha do tempo do painel não têm contraste suficiente. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %}' + - A página de stafftools de equipe para visualizar o colaborador pendente mostrou um `500 Internal Server Error` quando houve um convite de e-mail pendente. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - A verificação de integridade do repositório na stafftools pode gerar resultados incorretos em repositórios ocupados. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - Um usuário conectado que tenta aceitar um convite de e-mail poderia obter um erro `404 Not Found`. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - Se um usuário acessar um repositório cujo nome foi iniciado com "repositórios", ele será direcionado a aba "Repositórios" do proprietário em vez de chegar à página de visão geral do repositório. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - As etiquetas na linha do tempo do painel não têm contraste suficiente. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} deprecations: - - heading: Próxima obsolescência do GitHub Enterprise Server 2.19 + - + heading: Próxima obsolescência do GitHub Enterprise Server 2.19 notes: - '**GitHub Enterprise Server 2.19 irá tornar-se obsoleto a partir do dia 12 de novembro 2020**, o que significa que não serão feitas versões de patch, ainda que para problemas críticos de segurança, após esta data. Para obter um melhor desempenho, melhoria na segurança e novas funcionalidades, [atualize para a versão mais recente do GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) assim que possível.' - - heading: Obsolescência de Eventos de Webhook de legado do aplicativo GitHub + - + heading: Obsolescência de Eventos de Webhook de legado do aplicativo GitHub notes: - 'A partir da versão GitHub Enterprise Server 2.21.0 dois eventos legados de webhook relacionados aos aplicativos GitHub tornaram-se obsoletos e serão removidos do GitHub Enterprise Server 2.25.0. Os eventos obsoletos `integration_installation` e `integration_installation_repositories` têm eventos equivalentes que serão compatíveis. Mais informações estão disponíveis no [post do blogue do anúncio de obsolescência](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: Obsolescência do ponto de extremidade de legado dos aplicativos GitHub + - + heading: Obsolescência do ponto de extremidade de legado dos aplicativos GitHub notes: - 'Começando com o GitHub Enterprise Server 2.21.0, o ponto de extremidade de legado dos aplicativos GitHub para criar os tokens de acesso de instalação tornou-se obsoleto e será removido no GitHub Enterprise Server 2.25.0. Mais informações estão disponíveis no [post do blogue do anúncio de obsolescência](https://developer. ithub.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' - - heading: Obsolescência da API do aplicativo OAuth + - + heading: Obsolescência da API do aplicativo OAuth notes: - - 'O GitHub não é mais compatível com pontos de extremidade do aplicativo OAuth que contêm `access_token` como um parâmetro de caminho. Nós introduzimos novos pontos de extremidade que permitem gerenciar com segurança tokens para aplicativos OAuth, movendo `access_token` para o texto da solicitação. Embora obsoletos, os pontos de extremidade ainda podem ser acessados nesta versão. Temos o objetivo de remover esses pontos de extremidades no GitHub Enterprise Server 3.4. Para obter mais informações, consulte [post do blogue de anúncio de obscolescência](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).' + - O GitHub não é mais compatível com pontos de extremidade do aplicativo OAuth que contêm `access_token` como um parâmetro de caminho. Nós introduzimos novos pontos de extremidade que permitem gerenciar com segurança tokens para aplicativos OAuth, movendo `access_token` para o texto da solicitação. Embora obsoletos, os pontos de extremidade ainda podem ser acessados nesta versão. Temos o objetivo de remover esses pontos de extremidades no GitHub Enterprise Server 3.4. Para obter mais informações, consulte [post do blogue de anúncio de obscolescência](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). backups: - - 'O GitHub Enterprise Server 2.22 exige, pelo menos, [Utilitários de Backup do GitHub Enterprise](https://github.com/github/backup-utils) 2.22.0 para [Backups e Recuperação de Desastre](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/).' + - O GitHub Enterprise Server 2.22 exige, pelo menos, [Utilitários de Backup do GitHub Enterprise](https://github.com/github/backup-utils) 2.22.0 para [Backups e Recuperação de Desastre](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). known_issues: - - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'O menu suspenso Formato do ID do nome no Console de Gerenciamento redefine como "não especificado" depois de definir a instância como "persistente". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'A página de configurações do repositório de um repositório para um usuário ou organização de sites do GitHub Pages irá falhar com a mensagem "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %}' - - 'Os usuários podem experimentar um desempenho mais lento de recuperação em uma instância com réplicas de alta disponibilidade devido às leituras serem encaminhadas para um nó diferente. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %}' + - Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - O menu suspenso Formato do ID do nome no Console de Gerenciamento redefine como "não especificado" depois de definir a instância como "persistente". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - A página de configurações do repositório de um repositório para um usuário ou organização de sites do GitHub Pages irá falhar com a mensagem "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - Os usuários podem experimentar um desempenho mais lento de recuperação em uma instância com réplicas de alta disponibilidade devido às leituras serem encaminhadas para um nó diferente. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} - 'O [Criar um aplicativo GitHub a partir de um manifesto](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) falha. Para contornar esse problema, os usuários podem seguir as instruções manuais para [criar um aplicativo GitHub](https://docs. ithub.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}' - - 'Os nomes de usuário do GitHub podem alterar involuntariamente ao usar a autenticação de SAML, se o nome de usuário do GitHub não corresponder ao valor do atributo mapeado com o campo `username` no Console de gerenciamento. (atualizado 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %}' - - 'Em uma instância nova com a configuração 2.22.0 ou após a atualização para 2.22.0, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' - - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - Os nomes de usuário do GitHub podem alterar involuntariamente ao usar a autenticação de SAML, se o nome de usuário do GitHub não corresponder ao valor do atributo mapeado com o campo `username` no Console de gerenciamento. (atualizado 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - Em uma instância nova com a configuração 2.22.0 ou após a atualização para 2.22.0, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/pt-BR/data/release-notes/2-22/1.yml b/translations/pt-BR/data/release-notes/2-22/1.yml index 2027104a6f..198ef80c47 100644 --- a/translations/pt-BR/data/release-notes/2-22/1.yml +++ b/translations/pt-BR/data/release-notes/2-22/1.yml @@ -1,4 +1,5 @@ -date: '2020-10-09' +--- +date: '09-10-2020' sections: security_fixes: - '**MÉDIO**: ImageMagick foi atualizado para o endereço [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 %}' @@ -55,16 +56,16 @@ sections: - | O nomes de usuário do GitHub foram alterados involuntariamente ao usar a autenticação do SAML, quando o nome de usuário do GitHub não correspondeu ao valor do atributo mapeado com o campo `username` no Console. {% 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: - - 'O suporte é adicionado ao tipo de instância do AWS EC2 `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'Os manifestos do aplicativo GitHub agora incluem o 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 %}' + - O suporte é adicionado ao tipo de instância do AWS EC2 `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - Os manifestos do aplicativo GitHub agora incluem o 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: - - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'As atualizações de configuração irão falhar ao restaurar os dados para uma instância habilitada pelo GitHub Actions se a fonte original de backup não tiver o recurso habilitado. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %}' - - 'O GitHub Actions pode falhar ao iniciar com sucesso se estiver previamente habilitado em uma instância com versão 2.22.0 e for atualizado para 2.22.1. (atualizado 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' - - 'Em uma instância nova com a configuração 2.22.1 ou após a atualização para 2.22.1, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' - - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - As atualizações de configuração irão falhar ao restaurar os dados para uma instância habilitada pelo GitHub Actions se a fonte original de backup não tiver o recurso habilitado. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - O GitHub Actions pode falhar ao iniciar com sucesso se estiver previamente habilitado em uma instância com versão 2.22.0 e for atualizado para 2.22.1. (atualizado 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Em uma instância nova com a configuração 2.22.1 ou após a atualização para 2.22.1, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/pt-BR/data/release-notes/2-22/10.yml b/translations/pt-BR/data/release-notes/2-22/10.yml new file mode 100644 index 0000000000..ddc43e9e02 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-22/10.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - As regras personalizadas de firewall não são mantidas durante uma atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. diff --git a/translations/pt-BR/data/release-notes/2-22/2.yml b/translations/pt-BR/data/release-notes/2-22/2.yml index 54eebb54c5..3f261222d5 100644 --- a/translations/pt-BR/data/release-notes/2-22/2.yml +++ b/translations/pt-BR/data/release-notes/2-22/2.yml @@ -1,7 +1,8 @@ -date: '2020-10-20' +--- +date: '20-10-2020' sections: security_fixes: - - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + - Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} bugs: - | Se as configurações da conta de armazenamento não conseguiram validar ao configurar as ações do GitHub, a execução de `ghe-actions-teardown` foi necessária antes de fazer uma nova tentativa. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} @@ -18,11 +19,11 @@ sections: - | Em certas solicitações acima de 100 MB, o buffer de Kafka pode ser sobre-alocado. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} known_issues: - - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'O GitHub Actions pode falhar ao iniciar com sucesso se estiver previamente habilitado em uma instância com versão 2.22.0 e for atualizado para 2.22.2. (atualizado 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' - - 'Em uma instância nova com a configuração 2.22.2 ou após a atualização para 2.22.2, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' - - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - O GitHub Actions pode falhar ao iniciar com sucesso se estiver previamente habilitado em uma instância com versão 2.22.0 e for atualizado para 2.22.2. (atualizado 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Em uma instância nova com a configuração 2.22.2 ou após a atualização para 2.22.2, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/pt-BR/data/release-notes/2-22/3.yml b/translations/pt-BR/data/release-notes/2-22/3.yml index d6edd0056a..8911d6e8ad 100644 --- a/translations/pt-BR/data/release-notes/2-22/3.yml +++ b/translations/pt-BR/data/release-notes/2-22/3.yml @@ -1,4 +1,5 @@ -date: '2020-11-03' +--- +date: '03-11-2020' sections: security_fixes: - | @@ -8,15 +9,15 @@ sections: - | Os pacotes foram atualizados para as últimas versões de segurança. {% 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: - - 'O GitHub Actions pode falhar ao iniciar com êxito caso tenha sido habilitado previamente em uma instância com execução 2.22.0 e caso tenha sido atualizado para a 2.22.1 ou 2.22.2 {% comment %} https://github. om/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' - - 'Os arquivos de configuração para o GitHub Actions não foram copiados para a réplica ao configurar as réplicas de alta disponibilidade, gerando, potencialmente erros durante `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %}' - - 'Em uma nova instância com a configuração 2.22.1 ou 2.22.2 ou após a atualização para 2.22.1 ou 2.22.2, o feed de atividades no painel de uma organização não seria atualizado. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %}' - - 'Editar templates de problemas com nomes de arquivos que contenham caracteres diferentes de ASCII gerariam uma falha com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %}' - - 'Um método métrico de coleta em segundo plano para aumentar a utilização da CPU. (atualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + - O GitHub Actions pode falhar ao iniciar com êxito caso tenha sido habilitado previamente em uma instância com execução 2.22.0 e caso tenha sido atualizado para a 2.22.1 ou 2.22.2 {% comment %} https://github. om/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Os arquivos de configuração para o GitHub Actions não foram copiados para a réplica ao configurar as réplicas de alta disponibilidade, gerando, potencialmente erros durante `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - Em uma nova instância com a configuração 2.22.1 ou 2.22.2 ou após a atualização para 2.22.1 ou 2.22.2, o feed de atividades no painel de uma organização não seria atualizado. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - Editar templates de problemas com nomes de arquivos que contenham caracteres diferentes de ASCII gerariam uma falha com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - Um método métrico de coleta em segundo plano para aumentar a utilização da CPU. (atualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} known_issues: - - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP da fonte real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP da fonte real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/pt-BR/data/release-notes/2-22/4.yml b/translations/pt-BR/data/release-notes/2-22/4.yml index 3458c0e073..fdc35be19f 100644 --- a/translations/pt-BR/data/release-notes/2-22/4.yml +++ b/translations/pt-BR/data/release-notes/2-22/4.yml @@ -1,15 +1,16 @@ -date: '2020-11-17' +--- +date: '17-11-2020' sections: security_fixes: - - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + - Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} bugs: - - 'Os logs de babeld não tinham um separador entre segundos e microssegundos. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'Após atualizar o GHES com um hotpatch, os comandos `ghe-actions-precheck` e `ghe-packages-precheck` falhariam com o erro `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %}' - - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %}' - - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 em vez do endereço IP da fonte real. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %}' + - Os logs de babeld não tinham um separador entre segundos e microssegundos. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - Após atualizar o GHES com um hotpatch, os comandos `ghe-actions-precheck` e `ghe-packages-precheck` falhariam com o erro `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Os logs de auditoria podem ser atribuídos a 127.0.0.1 em vez do endereço IP da fonte real. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} known_issues: - - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/pt-BR/data/release-notes/2-22/5.yml b/translations/pt-BR/data/release-notes/2-22/5.yml index e3c61202be..78e7cc4145 100644 --- a/translations/pt-BR/data/release-notes/2-22/5.yml +++ b/translations/pt-BR/data/release-notes/2-22/5.yml @@ -1,4 +1,5 @@ -date: '2020-12-03' +--- +date: '03-12-2020' sections: bugs: - 'O serviço de autorização foi detectado como não saudável devido a uma condição de raça no bootstrap que gerou a reinicialização do serviço. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/6.yml b/translations/pt-BR/data/release-notes/2-22/6.yml index fa62449e96..514dcab76c 100644 --- a/translations/pt-BR/data/release-notes/2-22/6.yml +++ b/translations/pt-BR/data/release-notes/2-22/6.yml @@ -1,4 +1,5 @@ -date: '2020-12-17' +--- +date: '17-12-2020' sections: security_fixes: - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/8.yml b/translations/pt-BR/data/release-notes/2-22/8.yml index 074e3600e6..a95151fd52 100644 --- a/translations/pt-BR/data/release-notes/2-22/8.yml +++ b/translations/pt-BR/data/release-notes/2-22/8.yml @@ -1,4 +1,5 @@ -date: '2021-03-16' +--- +date: '16-03-2021' sections: security_fixes: - Os pacotes foram atualizados para as últimas versões de segurança. @@ -7,11 +8,11 @@ sections: - Um administrador do site poderia obter uma página de com a mensagem "500 error" ao tentar visualizar problemas referenciados em repositórios privados. - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.' + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. - As regras personalizadas de firewall não são mantidas durante uma atualização. - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.' + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. - - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.' + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. - | Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: diff --git a/translations/pt-BR/data/release-notes/3-0/0.yml b/translations/pt-BR/data/release-notes/3-0/0.yml index 93c736f550..8fc414546a 100644 --- a/translations/pt-BR/data/release-notes/3-0/0.yml +++ b/translations/pt-BR/data/release-notes/3-0/0.yml @@ -1,10 +1,12 @@ -date: '2021-02-16' +--- +date: '16-02-2021' intro: 'Os requisitos mínimos de infraestrutura aumentaram para {% data variables.product.prodname_ghe_server %} 3.0+. Para obter mais informações, consulte "[Sobre requisitos mínimos para o GitHub Enterprise Server 3.0 e posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."' sections: security_fixes: - '**HIGH:** A remote code execution vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration of the underlying parsers used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to execute commands on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' features: - - heading: GitHub Actions + - + heading: GitHub Actions notes: - | [{% data variables.product.prodname_actions %}] (https://github.com/features/actions) está disponível em {% data variables.product.prodname_ghe_server %} 3,0+. Crie, teste e implante seu código a partir de {% data variables.product.prodname_dotcom %}. Envie revisões de código, gerenciamento de branches e triagem de problemas da maneira que você desejar. @@ -25,7 +27,8 @@ sections: - [Modelos de fluxo de trabalho para uma organização](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) simplifica e promove as práticas recomendadas e a consistência em toda a sua organização. {% data variables.product.prodname_actions %} não é atualmente compatível para empresas que usam configurações de cluster. - - heading: GitHub Package Registry + - + heading: GitHub Package Registry notes: - | [{% data variables.product.prodname_registry %}](https://github.com/features/packages) é um serviço de hospedagem de pacotes, integrado nativamente às APIs, ações e webhooks do GitHub. Crie um [fluxo de trabalho de DevOps de ponta a ponta](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterpris-enterprise) que inclui o seu código, integração contínua e soluções de implantação. @@ -35,45 +38,53 @@ sections: Ao publicar pacotes no NuGet, os usuários agora podem usar a opção `--api-key` para passar seu token de autenticação em vez de escrevê-lo em um arquivo. Para obter mais informações, consulte [Configurar CLI do dotnet para uso com o GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) {% data variables.product.prodname_registry %} não é atualmente compatível para empresas que usam configurações de cluster. - - heading: GitHub Mobile beta + - + heading: GitHub Mobile beta notes: - | O beta de [{% data variables.product.prodname_mobile %}](https://github.com/features/) permite que você faça triagem de notificações e gerencie problemas e pull requests a partir do seu dispositivo. Você pode estar conectado simultaneamente ao celular com uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %} e uma conta de usuário em {% data variables.product.prodname_ghe_server %}. O beta de {% data variables.product.prodname_mobile %} agora está disponível para {% data variables.product.prodname_ghe_server %}. Efetue o login com os nossos aplicativos [Android](https://play.google.com/store/apps/details?id=com.github.android) e [iOS](https://apps.apple.com/app/github/id1477376905) para monitorar notificações e gerenciar problemas e pull requests em qualquer lugar. Os administradores podem desabilitar o suporte móvel para a sua Empresa usando o console de gerenciamento ou executando o comando `ghe-config app.mobile.enabled false`. - - heading: Beta de varredura de segredo de segurança avançada + - + heading: Beta de varredura de segredo de segurança avançada notes: - | [Varredura de segredo beta](https://github. um/recursos/segurança) faz a varredura de repositórios públicos e privados com relação a credenciais comprometidas, encontra segredos, e notifica o provedor do segredo ou administrador no momento em que são autorizados em um repositório. Os administradores que usam {% data variables.product.prodname_GH_advanced_security %} podem [habilitar e configurar](/enterprise-server@3. /admin/configuration/configuring-secret-scanning-for-your-appliance) a varredura de segredo de {% data variables.product.prodname_GH_advanced_security %}. Você pode revisar os [requisitos mínimos atualizados para sua plataforma](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) antes de habilitar a varredura de segredo de {% data variables.product.prodname_GH_advanced_security %}. - - heading: Varredura Avançada de Código de Segurança + - + heading: Varredura Avançada de Código de Segurança notes: - | [A Varredura Avançada de Código de Segurança do GitHub](https://github.com/features/security) agora está geralmente disponível no GitHub Enterprise Server. As organizações que adquiriram Segurança Avançada podem usar este recurso para fazer testes de segurança de análise estática com seu código e evitar que vulnerabilidades cheguem ao código de produção usando CodeQL, o nosso mecanismo de análise semântica. Para obter mais informações, consulte "[Configurar a varredura de código no seu aplicativo](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" changes: - - heading: Alterações na administração + - + heading: Alterações na administração notes: - - 'O sistema de entrega de eventos de webhook foi rearquitetado para rendimentos mais altos, entregas mais rápidas e menor atraso nas mensagens de erro.. Além disso, ele usa menos CPU e memória em {% data variables.product.prodname_ghe_server %} 3.0+.' - - 'Os proprietários da organização e da empresa agora podem ver quando um integrante da equipe foi promovido ou rebaixado de ser um mantenedor de equipe no log de auditoria por meio os novos eventos de log de auditoria `team.promote_maintainer` e `team.demote_maintainer`. Para obter mais informações, consulte "[Ações auditadas](/enterprise-server@3.0/admin/user-management/audited-actions)."' + - O sistema de entrega de eventos de webhook foi rearquitetado para rendimentos mais altos, entregas mais rápidas e menor atraso nas mensagens de erro.. Além disso, ele usa menos CPU e memória em {% data variables.product.prodname_ghe_server %} 3.0+. + - Os proprietários da organização e da empresa agora podem ver quando um integrante da equipe foi promovido ou rebaixado de ser um mantenedor de equipe no log de auditoria por meio os novos eventos de log de auditoria `team.promote_maintainer` e `team.demote_maintainer`. Para obter mais informações, consulte "[Ações auditadas](/enterprise-server@3.0/admin/user-management/audited-actions)." - 'Os mantenedores do repositório com os sites de {% data variables.product.prodname_pages %} existentes podem [atualizar facilmente o nome padrão anterior do branch](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' - - 'São necessários recursos adicionais de hardware para executar {% data variables.product.prodname_ghe_server %} com qualquer uma das Ações, Pacotes ou Segurança Avançada habilitadas. Para obter mais informações sobre os recursos mínimos necessários para cada plataforma compatível, consulte "[Configurar uma instância de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)."' - - 'Agora os administradores podem [publicar uma mensagem](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), que todos os usuários devem aceitar. Isso pode ajudar a integrar novos usuários e supervisionar outras informações e políticas específicas da organização.' - - heading: Alterações de segurança + - São necessários recursos adicionais de hardware para executar {% data variables.product.prodname_ghe_server %} com qualquer uma das Ações, Pacotes ou Segurança Avançada habilitadas. Para obter mais informações sobre os recursos mínimos necessários para cada plataforma compatível, consulte "[Configurar uma instância de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Agora os administradores podem [publicar uma mensagem](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), que todos os usuários devem aceitar. Isso pode ajudar a integrar novos usuários e supervisionar outras informações e políticas específicas da organização. + - + heading: Alterações de segurança notes: - - 'Os proprietários da organização agora podem desabilitar a publicação de sites de {% data variables.product.prodname_pages %} dos repositórios na organização. Desabilitar {% data variables.product.prodname_pages %} para a organização impedirá que os integrantes criem novos sites de páginas, mas não irá cancelar a publicação de sites existentes. Para obter mais informações, consulte "[Desabilitar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)."' + - Os proprietários da organização agora podem desabilitar a publicação de sites de {% data variables.product.prodname_pages %} dos repositórios na organização. Desabilitar {% data variables.product.prodname_pages %} para a organização impedirá que os integrantes criem novos sites de páginas, mas não irá cancelar a publicação de sites existentes. Para obter mais informações, consulte "[Desabilitar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." - Um centro de dados deve ser definido explicitamente em todos os nós antes de habilitar uma réplica ativa. - - 'Todo o uso de impressões digitais de SSH foi alterado para usar as impressões digitais de SHA256, pois são usadas com o OpenSSH desde a versão 6.8. Isto se aplica à interface web e também à API em que as impressões digitais são retornadas, como no GraphQL. As impressões digitais seguem o formato OpenSSH.' + - Todo o uso de impressões digitais de SSH foi alterado para usar as impressões digitais de SHA256, pois são usadas com o OpenSSH desde a versão 6.8. Isto se aplica à interface web e também à API em que as impressões digitais são retornadas, como no GraphQL. As impressões digitais seguem o formato OpenSSH. - Os cabeçalhos de assinatura SHA-1 e SHA-256 (dois cabeçalhos) são enviados em webhooks. - - heading: Alterações de desenvolvedor + - + heading: Alterações de desenvolvedor notes: - - 'A maioria dos serviços em execução em {% data variables.product.prodname_ghe_server %} 3.0 + estão agora nos contêineres, o que permite que o GitHub itere internamente e envie rapidamente versões de qualidade' - - 'O sistema de entrega de eventos webhook foi rearquivado para melhor rendimento, entregas mais rápidas e menor atraso nas mensagens.' - - heading: Alterações de API + - A maioria dos serviços em execução em {% data variables.product.prodname_ghe_server %} 3.0 + estão agora nos contêineres, o que permite que o GitHub itere internamente e envie rapidamente versões de qualidade + - O sistema de entrega de eventos webhook foi rearquivado para melhor rendimento, entregas mais rápidas e menor atraso nas mensagens. + - + heading: Alterações de API notes: - 'Os administradores agora podem configurar e gerenciar o anúncio do banner para todo o site através da API REST. Para obter mais informações, consulte os pontos de extremidade para "[Administração do GitHub Enterprise](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' - 'Um novo ponto de extremidade da API permite o intercâmbio de um usuário para um token de servidor para um token de servidor com escopo definido para repositórios específicos. Para obter mais informações, consulte "[Apps](/enterprise-server@3.0/rest/reference/apps#create-a-scoped-access-token)" na documentação da API REST de {% data variables.product.prodname_dotcom %}' - - heading: Renomeação do branch padrão + - + heading: Renomeação do branch padrão notes: - | Os administradores da empresa e da organização agora podem definir o nome do branch padrão para novos repositórios. Os administradores das empresas também podem aplicar a sua escolha do nome do branch padrão em todas as organizações ou permitir que as organizações individuais escolham suas próprias. @@ -88,10 +99,12 @@ sections: Esta alteração é uma das muitas mudanças que o GitHub está realizando para ser compatível com projetos e mantenedores que desejam renomear seu branch padrão. Para saber mais sobre as mudanças que estamos criando, consulte [github/renaming](https://github.com/github/renaming). bugs: - - heading: Fixes for known issues from Release Candidates + - + heading: Fixes for known issues from Release Candidates notes: - - 'All known issues from Release Candidate 1 and Release Candidate 2 have been fixed, except those listed in the Known Issues section below.' - - heading: Correções para outros problemas + - All known issues from Release Candidate 1 and Release Candidate 2 have been fixed, except those listed in the Known Issues section below. + - + heading: Correções para outros problemas notes: - Foram corrigidos os problemas com migrações e melhorias para a versão 3.0.0. - O versionamento do Backup de Utilitários agora funciona para versões de candidato de versões. @@ -100,44 +113,50 @@ sections: - A caixa de seleção para habilitar o GitHub Actions no Console de Gerenciamento agora é visível com qualquer método de autenticação. - GitHub Actions could be enabled if the required storage was also configured. - '`ghe-repl-status` could silently fail if MSSQL replication was not configured.' - - 'O formato de vários arquivos de registro foram alterados, incluindo a adição de um PID para diferentes tipos de registro. Isso não afeta como o Suporte GitHub Enterprise usa pacotes de suporte para solucionar problemas.' + - O formato de vários arquivos de registro foram alterados, incluindo a adição de um PID para diferentes tipos de registro. Isso não afeta como o Suporte GitHub Enterprise usa pacotes de suporte para solucionar problemas. - Uma solicitação de PATCH para a API de configuração de webhook não apaga mais o segredo do webhook. - Certain types of pre-receive hooks were failing. - 'The Packages NuGet service now normalizes semantic versions on publish. An invalid semantic version (for example: v1.0.0.0.0.0) is not downloadable by NuGet clients and therefore a NuGet service is expected to normalize those versions (for example: v1.0.0.0.0.0 --> v1.0.0). Any original, non-normalized, version will be available in the `verbatimVersion` field. No changes to client configurations are required.' known_issues: - - 'Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador.' + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. - As regras personalizadas de firewall não são mantidas durante uma atualização. - - 'Arquivos rastreados pelo LFS do Git [carregados por meio da interface web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) foram adicionados incorreta e diretamente ao repositório.' - - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.' - - 'Quando o modo de manutenção está habilitado, alguns serviços continuam listados como "processos ativos". Espera-se que os serviços identificados sejam executados durante o modo de manutenção. Se você tiver este problema e não estiver seguro, entre em contato com {% data variables.contact.contact_ent_support %}.' - - 'Quando o GitHub Actions estiver habilitado, use ''`ghe-maintenance -u`'' para cancelar a definição do modo de manutenção.' + - Arquivos rastreados pelo LFS do Git [carregados por meio da interface web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) foram adicionados incorreta e diretamente ao repositório. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - Quando o modo de manutenção está habilitado, alguns serviços continuam listados como "processos ativos". Espera-se que os serviços identificados sejam executados durante o modo de manutenção. Se você tiver este problema e não estiver seguro, entre em contato com {% data variables.contact.contact_ent_support %}. + - Quando o GitHub Actions estiver habilitado, use '`ghe-maintenance -u`' para cancelar a definição do modo de manutenção. - 'Duplicated logging to `/var/log/messages`, `/var/log/syslog`, and `/var/log/user.log` results in increased root volume utilization.' - Os usuários podem ignorar uma mensagem obrigatória sem marcar todas as caixas de seleção. - '[Pre-receive hook scripts](/admin/policies/enforcing-policy-with-pre-receive-hooks) cannot write temporary files, which may cause script execution to fail. Users who use pre-receive hooks should test in a staging environment to see if scripts require write access.' - - 'Repository [deploy keys](/developers/overview/managing-deploy-keys) are unable to be used with repositories containing LFS objects.' + - Repository [deploy keys](/developers/overview/managing-deploy-keys) are unable to be used with repositories containing LFS objects. - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text. - - 'Dependency graph fails to parse `setup.py` Python manifest files, resulting in HTTP 500 errors in logs. This, combined with the duplicated logging issue, results in increased root volume utilization.' + - Dependency graph fails to parse `setup.py` Python manifest files, resulting in HTTP 500 errors in logs. This, combined with the duplicated logging issue, results in increased root volume utilization. - A race condition can cause dependency graph database migrations to appear to fail. - Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI. - - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).' + - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). deprecations: - - heading: Depreciação do GitHub Enterprise Server 2.19 + - + heading: Depreciação do GitHub Enterprise Server 2.19 notes: - '**{% data variables.product.prodname_ghe_server %} 2.19 estará obsoleto a partir de 12 de novembro de 2020**. Isso significa que não serão feitas versões de patch, mesmo para questões críticas de segurança, após esta data. Para obter um melhor desempenho, melhoria na segurança e novas funcionalidades, [atualize para a versão mais recente de {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) assim que possível.' - - heading: Obsolescência de Eventos de Webhook de legado do aplicativo GitHub + - + heading: Obsolescência de Eventos de Webhook de legado do aplicativo GitHub notes: - - 'Começando com {% data variables.product.prodname_ghe_server %} 2.21.0, dois eventos legados de webhook relacionados a aplicativos GitHub foram descontinuados e serão removidos em {% data variables.product.prodname_ghe_server %} 3.2.0. Os eventos obsoletos `integration_installation` e `integration_installation_repositories` têm eventos equivalentes que serão compatíveis. Mais informações estão disponíveis no [post do blogue de anúncio de obsolescência](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).' - - heading: Obsolescência do ponto de extremidade de legado dos aplicativos GitHub + - Começando com {% data variables.product.prodname_ghe_server %} 2.21.0, dois eventos legados de webhook relacionados a aplicativos GitHub foram descontinuados e serão removidos em {% data variables.product.prodname_ghe_server %} 3.2.0. Os eventos obsoletos `integration_installation` e `integration_installation_repositories` têm eventos equivalentes que serão compatíveis. Mais informações estão disponíveis no [post do blogue de anúncio de obsolescência](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). + - + heading: Obsolescência do ponto de extremidade de legado dos aplicativos GitHub notes: - - 'Começando com {% data variables.product.prodname_ghe_server %} 2.21, o ponto de extremidade do legado dos aplicativos GitHub para a criação de tokens de acesso de instalação foi suspenso e será removido em {% data variables.product.prodname_ghe_server %} 3.2.0. Mais informações estão disponíveis no [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/).' - - heading: Obsolescência da API do aplicativo OAuth + - Começando com {% data variables.product.prodname_ghe_server %} 2.21, o ponto de extremidade do legado dos aplicativos GitHub para a criação de tokens de acesso de instalação foi suspenso e será removido em {% data variables.product.prodname_ghe_server %} 3.2.0. Mais informações estão disponíveis no [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). + - + heading: Obsolescência da API do aplicativo OAuth notes: - - 'O GitHub não é compatível mais com os pontos de extremidade do aplicativo OAuth que contêm `access_token` como um parâmetro de caminho. Nós introduzimos novos pontos de extremidade que permitem que você gerencie, com segurança, tokens para aplicativos OAuth movendo `access_token` para o texto da solicitação. Embora obsoleto, os pontos de extremidade ainda podem ser acessados nesta versão. Queremos remover esses pontos de extremidade em {% data variables.product.prodname_ghe_server %} 3.4. Para obter mais informações, consulte [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).' - - heading: Depreciação de compatibilidade com o Semiotic + - O GitHub não é compatível mais com os pontos de extremidade do aplicativo OAuth que contêm `access_token` como um parâmetro de caminho. Nós introduzimos novos pontos de extremidade que permitem que você gerencie, com segurança, tokens para aplicativos OAuth movendo `access_token` para o texto da solicitação. Embora obsoleto, os pontos de extremidade ainda podem ser acessados nesta versão. Queremos remover esses pontos de extremidade em {% data variables.product.prodname_ghe_server %} 3.4. Para obter mais informações, consulte [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - + heading: Depreciação de compatibilidade com o Semiotic notes: - O serviço era compatível com uma experiência de "Encontrar por Símbolo" na vista de pull request que não era amplamente utilizada. - - heading: Obsolescência de comandos de fluxo de trabalh + - + heading: Obsolescência de comandos de fluxo de trabalh notes: - 'Os comandos do fluxo de trabalho `set-env` and `add-path` de {% data variables.product.prodname_actions %} tornaram-se obsoletos. Para obter mais informações, consulte o [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' backups: diff --git a/translations/pt-BR/data/release-notes/3-0/2.yml b/translations/pt-BR/data/release-notes/3-0/2.yml index 98c723e739..e38d7b2624 100644 --- a/translations/pt-BR/data/release-notes/3-0/2.yml +++ b/translations/pt-BR/data/release-notes/3-0/2.yml @@ -1,35 +1,36 @@ -date: '2021-03-16' +--- +date: '16-03-2021' intro: 'Os requisitos mínimos de infraestrutura aumentaram para {% data variables.product.prodname_ghe_server %} 3.0+. Para obter mais informações, consulte "[Sobre requisitos mínimos para o GitHub Enterprise Server 3.0 e posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."' sections: security_fixes: - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - During a backup an error "Warning: One or more storage objects were not found on the source appliance." was occurring when attempting to clean up purgeable storage objects. - - 'Ocorreu uma falha no gráfico de dependência ao analisar os arquivos de manifesto de JavaScript `yarn.lock`, gerando erros HTTP 500 nos registros.' + - 'During a backup an error "Warning: One or more storage objects were not found on the source appliance." was occurring when attempting to clean up purgeable storage objects.' + - Ocorreu uma falha no gráfico de dependência ao analisar os arquivos de manifesto de JavaScript `yarn.lock`, gerando erros HTTP 500 nos registros. - Desabilitar o GitHub Actions às vezes gera falhas. - - 'Hooks pre-receive personalizados não foram autorizados a gravar em `/tmp`, impedindo que alguns scripts sejam executados corretamente.' + - Hooks pre-receive personalizados não foram autorizados a gravar em `/tmp`, impedindo que alguns scripts sejam executados corretamente. - Registros de jornais do Systemd foram duplicados em vários lugares. - - 'Um fuso horário definido no GitHub Enterprise 11.10.x ou anterior foi redefinido como fuso horário UTC depois de atualizar para 3.0, o que fez com que os carimbos de data fossem alterados em algumas instâncias.' + - Um fuso horário definido no GitHub Enterprise 11.10.x ou anterior foi redefinido como fuso horário UTC depois de atualizar para 3.0, o que fez com que os carimbos de data fossem alterados em algumas instâncias. - Clicar em "Publicar seu primeiro pacote" na barra lateral de pacotes no repositório leva a uma página vazia. - Um administrador do site poderia obter uma página de com a mensagem "500 error" ao tentar visualizar problemas referenciados em repositórios privados. - - 'Após desabilitar os pacotes do GitHub, algumas páginas da organização retornariam uma resposta de HTTP 500 error.' + - Após desabilitar os pacotes do GitHub, algumas páginas da organização retornariam uma resposta de HTTP 500 error. - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - - 'Repository [deploy keys](/developers/overview/managing-deploy-keys) were unable to be used with repositories containing LFS objects.' - - 'Na barra lateral de pacotes de um repositório, o ícone Docker era cinza e a dica da ferramenta exibia "This service is deprecated".' + - Repository [deploy keys](/developers/overview/managing-deploy-keys) were unable to be used with repositories containing LFS objects. + - Na barra lateral de pacotes de um repositório, o ícone Docker era cinza e a dica da ferramenta exibia "This service is deprecated". - Os webhooks configurados com um tipo de conteúdo de `application/x-www-form-urlencoded` não receberam parâmetros de consulta no texto da solicitação POST. - Os usuários podem descartar uma mensagem obrigatória sem marcar todas as caixas de seleção. - - 'Em alguns casos, após a atualização de uma instância 2.22.X, os ativos de interface web estavam faltando e a página não seria renderizada corretamente.' + - Em alguns casos, após a atualização de uma instância 2.22.X, os ativos de interface web estavam faltando e a página não seria renderizada corretamente. - Running `ghe-config-apply` could time out with `Failure waiting for nomad jobs to apply` due to `'job' stanza not found`. known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.' + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. - As regras personalizadas de firewall não são mantidas durante uma atualização. - - 'Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta.' + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. - - 'Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com.' - - 'When maintenance mode is enabled, some services continue to be listed as "active processes". The services identified are expected to run during maintenance mode. If you experience this issue and are unsure, contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/).' + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - When maintenance mode is enabled, some services continue to be listed as "active processes". The services identified are expected to run during maintenance mode. If you experience this issue and are unsure, contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/). - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text. - - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).' + - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). - | Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: diff --git a/translations/pt-BR/data/release-notes/3-0/4.yml b/translations/pt-BR/data/release-notes/3-0/4.yml new file mode 100644 index 0000000000..577ca023dc --- /dev/null +++ b/translations/pt-BR/data/release-notes/3-0/4.yml @@ -0,0 +1,25 @@ +--- +date: '2021-04-01' +intro: 'Os requisitos mínimos de infraestrutura aumentaram para {% data variables.product.prodname_ghe_server %} 3.0+. Para obter mais informações, consulte "[Sobre requisitos mínimos para o GitHub Enterprise Server 3.0 e posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - When maintenance mode was enabled, some services continued to be listed as "active processes" even though they were expected to be running, and should not have been listed. + - After upgrading from 2.22.x to 3.0.x with GitHub Actions enabled, the self-hosted runner version was not updated and no self-hosted updates were made. + - Old GitHub Pages builds were not cleaned up leading to increased disk usage. + - '`memcached` was not running on active replicas.' + - Upgrade failed when updating file permissions when GitHub Actions was enabled. + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The `ghe-saml-mapping-csv` command-line utility produced a warning message. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - As regras personalizadas de firewall não são mantidas durante uma atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text. diff --git a/translations/pt-BR/data/reusables/actions/actions-audit-events-workflow.md b/translations/pt-BR/data/reusables/actions/actions-audit-events-workflow.md index 5e2c944e63..80201c9711 100644 --- a/translations/pt-BR/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/pt-BR/data/reusables/actions/actions-audit-events-workflow.md @@ -4,5 +4,7 @@ | `completed_workflow_run` | Acionada quando um status de fluxo de trabalho é alterado para `concluído`. Só pode ser visto usando a API REST; não visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)". | | `created_workflow_run` | Acionada quando uma execução do fluxo de trabalho é criada. Só pode ser visto usando a API REST; não visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Criar um exemplo de fluxo de trabalho](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)". | | `delete_workflow_run` | Acionada quando a execução do fluxo de trabalho é excluída. Para obter mais informações, consulte "[Excluir uma execução de fluxo de trabalho](/actions/managing-workflow-runs/deleting-a-workflow-run)". | +| `disable_workflow` | Triggered when a workflow is disabled. | +| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`. | | `rerun_workflow_run` | Acionada quando uma execução do fluxo de trabalho é executada novamente. Para obter mais informações, consulte "[Executar novamente um fluxo de trabalho](/actions/managing-workflow-runs/re-running-a-workflow)". | | `prepared_workflow_job` | Acionada quando um trabalho no fluxo de trabalho é iniciado. Inclui a lista de segredos que foram fornecidos ao trabalho. Só pode ser visto usando a API REST; não visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". | diff --git a/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md index baa32fddac..b6abfe68c7 100644 --- a/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md +++ b/translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md @@ -2,4 +2,4 @@ You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose. -Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_advanced_security %} features, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." diff --git a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md index 26ea19355f..437c1acc2f 100644 --- a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,9 +1,9 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). +**Aviso de método obsoleto:** {% data variables.product.prodname_dotcom %} irá descontinuar a autenticação para a API usando parâmetros de consulta. A autenticação para a API deve ser feita com a [autenticação básica HTTP](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Usar parâmetros de consulta para efetuar a autenticação na API não funcionará mais a partir de 5 de maio de 2021. {% endif %} Para mais informações, incluindo brownouts agendadas, veja [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} +{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %} Autenticação na API usando parâmetros de consulta enquanto disponível não é mais compatível devido a questões de segurança. Em vez disso, recomendamos que integradores movam seu token de acesso, `client_id`, or `client_secret` no cabeçalho. {% data variables.product.prodname_dotcom %} anunciará a remoção da autenticação por parâmetros de consulta com aviso prévio. {% endif %} {% endwarning %} {% endif %} diff --git a/translations/pt-BR/data/reusables/branches/set-default-branch.md b/translations/pt-BR/data/reusables/branches/set-default-branch.md index f080eecba0..b6277df907 100644 --- a/translations/pt-BR/data/reusables/branches/set-default-branch.md +++ b/translations/pt-BR/data/reusables/branches/set-default-branch.md @@ -1 +1 @@ -Você pode definir o nome do branch-padrão para novos repositórios. Para obter mais informações, consulte "[Gerenciar a branch padrão para seus repositórios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories), "[Gerenciar o nome do branch padrão para repositórios na sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)" e {% if currentVersion == "free-pro-team@latest" %}"[Aplicar políticas de gerenciamento do repositório na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name).{% else %}"[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)".{% endif %} +Você pode definir o nome do branch-padrão para novos repositórios. For more information, see "[Managing the default branch for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)," "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/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 %} diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md index d0209122fe..7b242efbbd 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ Os repositórios de uma atividade podem ser públicos ou privados. Se você usar repositórios privados, apenas o aluno ou a equipe poderá ver o feedback que você fornecer. -Você também pode decidir se deseja conceder permissões de administrador para os alunos no repositório de uma atividade. Conceda permissões de administrador se o aluno puder executar tarefas administrativas para o repositório da atividade. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" e "[níveis de permissão do repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". +Você também pode decidir se deseja conceder permissões de administrador para os alunos no repositório de uma atividade. Conceda permissões de administrador se o aluno puder executar tarefas administrativas para o repositório da atividade. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" e "[níveis de permissão do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". Em "Visibilidade do repositório", selecione uma visibilidade. Opcionalmente, selecione **Conceder acesso de administrador aos seus repositórios**. diff --git a/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md b/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md index 7208b75c08..166df7f4fa 100644 --- a/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. Na lista de organizações, clique na organização que você gostaria de usar para a sua sala de aula. Opcionalmente, você pode criar uma nova organização. Para obter mais informações, consulte "[Criar uma nova organização do zero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". ![Organização na lista de organizações para criar uma nova sala de aula](/assets/images/help/classroom/click-organization.png) +1. Na lista de organizações, clique na organização que você gostaria de usar para a sua sala de aula. Opcionalmente, você pode criar uma nova organização. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". ![Organização na lista de organizações para criar uma nova sala de aula](/assets/images/help/classroom/click-organization.png) 1. Digite o nome para sua sala de aula. ![Campo de texto para digitar o nome da sala de aula](/assets/images/help/classroom/type-classroom-name.png) 1. Clique em **Criar sala de aula**. ![Campo de texto para digitar o nome da sala de aula](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/pt-BR/data/reusables/code-scanning/click-alert-in-list.md b/translations/pt-BR/data/reusables/code-scanning/click-alert-in-list.md index 9b7d49682e..8a32211d45 100644 --- a/translations/pt-BR/data/reusables/code-scanning/click-alert-in-list.md +++ b/translations/pt-BR/data/reusables/code-scanning/click-alert-in-list.md @@ -1 +1,6 @@ -1. Em "Varredura do código, clique no alerta que você deseja explorar. ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +1. Em "Varredura do código, clique no alerta que você deseja explorar. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% 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 71d41c3e06..664e15dce8 100644 --- a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -Ao executar atualizações de segurança ou versão, alguns ecossistemas devem ser capazes de resolver todas as dependências de sua fonte para verificar se as atualizações foram bem-sucedidas. Se o seu manifesto ou arquivos de bloqueio contiverem dependências privadas, {% data variables.product.prodname_dependabot %} deverá ser capaz de acessar o local em que essas dependências estão hospedadas. Os proprietários da organização podem conceder a {% data variables.product.prodname_dependabot %} acesso a repositórios privados que contêm dependências para um projeto dentro da mesma organização. 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-dependencies)". You can configure access to private registries in a repository's _dependabot.yml_ configuration file. Para obter mais informações, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". +Ao executar atualizações de segurança ou versão, alguns ecossistemas devem ser capazes de resolver todas as dependências de sua fonte para verificar se as atualizações foram bem-sucedidas. Se o seu manifesto ou arquivos de bloqueio contiverem dependências privadas, {% data variables.product.prodname_dependabot %} deverá ser capaz de acessar o local em que essas dependências estão hospedadas. Os proprietários da organização podem conceder a {% data variables.product.prodname_dependabot %} acesso a repositórios privados que contêm dependências para um projeto dentro da mesma organização. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". You can configure access to private registries in a repository's _dependabot.yml_ configuration file. Para obter mais informações, consulte "[Opções de configuração para atualizações de dependências](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". diff --git a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md index e6445f350f..485b246864 100644 --- a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md @@ -6,7 +6,7 @@ A tabela a seguir mostra, para cada gerenciador de pacotes: | Gerenciador de pacotes | Valor do YAML | Versões compatíveis | Repositórios privados | Private registries | Delegação | | ---------------------- | ---------------- | ------------------------------ |:---------------------:|:------------------:|:---------:| -| bundler | `bundler` | v1 | | **✓** | **✓** | +| bundler | `bundler` | v1, v2 | | **✓** | **✓** | | Cargo | `cargo` | v1 | **✓** | **✓** | | | Composer | `composer` | v1, v2 | **✓** | **✓** | | | Docker | `docker` | v1 | **✓** | **✓** | | diff --git a/translations/pt-BR/data/reusables/dotcom_billing/coupon-expires.md b/translations/pt-BR/data/reusables/dotcom_billing/coupon-expires.md new file mode 100644 index 0000000000..71beb790aa --- /dev/null +++ b/translations/pt-BR/data/reusables/dotcom_billing/coupon-expires.md @@ -0,0 +1 @@ +If you use a coupon to pay for a subscription, when the coupon expires, your payment method will be charged the full cost of your subscription. If you do not have a saved payment method, your account will be downgraded to {% data variables.product.prodname_free_user %} for user accounts or {% data variables.product.prodname_free_team %} for organizations. diff --git a/translations/pt-BR/data/reusables/education/about-github-education-link.md b/translations/pt-BR/data/reusables/education/about-github-education-link.md index 9f5fe24818..c14fac975b 100644 --- a/translations/pt-BR/data/reusables/education/about-github-education-link.md +++ b/translations/pt-BR/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Antes de solicitar um desconto individual, verifique se sua comunidade de estudos já não é nossa parceira como uma escola {% data variables.product.prodname_education %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)". +Antes de solicitar um desconto individual, verifique se sua comunidade de estudos já não é nossa parceira como uma escola {% data variables.product.prodname_campus_program %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)". diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md index 83944acdce..727552ef5d 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/business.md @@ -1,2 +1 @@ -1. In the left sidebar, click **Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %}**. - ![Enterprise{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} overview{% endif %} tab in the Site admin settings](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) +1. Na barra lateral esquerda, clique em **Empresa{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} visão geral{% endif %}**. ![Aba de {% if currentVersion ver_gt "enterprise-server@2.21" ou currentVersion == "github-ae@latest" %} visão geral da empresa{% endif %} nas configurações de administrador do site.](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) diff --git a/translations/pt-BR/data/reusables/github-actions/actions-github-connect-requirement.md b/translations/pt-BR/data/reusables/github-actions/actions-github-connect-requirement.md new file mode 100644 index 0000000000..8b36658e05 --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/actions-github-connect-requirement.md @@ -0,0 +1 @@ +To allow {% data variables.product.prodname_ghe_server %} to use actions directly from {% data variables.product.prodname_dotcom_the_website %}, you can use {% data variables.product.prodname_github_connect %}. You will need to enable the setting for "Server can use actions from {% data variables.product.prodname_dotcom_the_website %} in workflows runs," as described in "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." diff --git a/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md b/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md index 222a659fb1..e89eb779f1 100644 --- a/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md @@ -2,16 +2,17 @@ O modelo de fluxo de trabalho inicial configura o `PATH` para conter OpenJDK 8 para a plataforma x64. Se você quiser usar uma versão diferente do Java, ou escolher uma arquitetura diferente (`x64` or `x86`), você pode usar a ação `setup-java` para escolher um ambiente de execução Java diferente. -Por exemplo, para usar a versão 9.0. do JDK para a plataforma x64, você pode usar os parâmetros `setup-java` e configurar os de `java-version` e `architecture` para `'9.0.4'` e `x64`. +For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'adopt'` and `x64`. {% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 + - name: Set up JDK 11 for x64 + uses: actions/setup-java@v2 with: - java-version: '9.0.4' + java-version: '11' + distribution: 'adopt' architecture: x64 ``` {% endraw %} diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md index 9ddc7c7b5c..6b88ca8b5b 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md @@ -1,9 +1,9 @@ -A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added: -- **User repository**: You must be the repository owner. -- **Organization**: You must be an organization owner. -- **Organization repository**: You must be an organization owner, or have admin access to the repository. +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" or currentVersion == "github-ae@latest" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. Para gerenciar um executor auto-hospedado, você deve ter as seguintes permissões, dependendo de onde o executor auto-hospedado foi adicionado: +- **Repositório de Usuário**: Você deve ser o proprietário do repositório. +- **Organização**: Você deve ser um proprietário da organização. +- **Repositório da organização**: Você deve ser o proprietário da organização ou ter acesso de administrador ao repositório. {% if currentVersion == "free-pro-team@latest" %} -- **Enterprise account**: You must be an enterprise owner. -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} -- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator. +- **Conta corporativa**: Você deve ser proprietário de uma empresa. +{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- **Empresa**: Você deve ser um administrador do site de {% data variables.product.prodname_enterprise %} {% endif %} diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 12756c93a0..d6fcc551bf 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -1,12 +1,12 @@ -1. Navigate to where your self-hosted runner is registered: - * **In an organization or repository**: navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. - * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**: - - 1. In the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}. - 1. In the left sidebar, click **Enterprise overview**. - 1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**. -1. Navigate to the {% data variables.product.prodname_actions %} settings: - * **In an organization or repository**: click **Actions** in the left sidebar. - - ![Actions setting](/assets/images/help/settings/settings-sidebar-actions.png) - * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies". +1. Navegue por onde seu runner auto-hospedado está registrado: + * **Em uma organização ou repositório**: navegue até a página principal e clique em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**. + * {% 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" or currentVersion == "github-ae@latest" %}**If using an enterprise-level runner**: + + 1. No canto superior direito de qualquer página, clique em {% octicon "rocket" aria-label="The rocket ship" %}. + 1. Na barra lateral esquerda, clique em **Visão geral da empresa**. + 1. {% endif %} Na barra lateral da empresa, {% octicon "law" aria-label="The law icon" %} **Políticas**. +1. Navegue até as configurações {% data variables.product.prodname_actions %}: + * **Em uma organização ou um repositório**: clique em **Ações** na barra lateral esquerda. + + ![Configuração de ações](/assets/images/help/settings/settings-sidebar-actions.png) + * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies". diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/pt-BR/data/reusables/identity-and-permissions/revoking-identity-team-sync.md index 55754b26ee..64f4d84bde 100644 --- 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 @@ -1,5 +1,5 @@ {% warning %} -**Aviso:** Se a sua organização usar a sincronização de equipe, revogar a identidade SSO de uma pessoa irá remover essa pessoa de todas as equipes mapeadas para grupos de IdP. Para obter mais informações, consulte "[Sincronizar uma equipe com um provedor de identidade](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". +**Aviso:** Se a sua organização usar a sincronização de equipe, revogar a identidade SSO de uma pessoa irá remover essa pessoa de todas as equipes mapeadas para grupos de IdP. Para obter mais informações, consulte "[Sincronizar uma equipe com um provedor de identidade](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". {% endwarning %} diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 2abfe22fcf..1dca35c96d 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -Depois que você ativar a sincronização de equipe, os mantenedores de equipe e os proprietários da organização poderão conectar uma equipe a um grupo de IdP no {% data variables.product.prodname_dotcom %} ou através da API. Para obter mais informações, consulte "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" e "[Team synchronization](/rest/reference/teams#team-sync)." +Depois que você ativar a sincronização de equipe, os mantenedores de equipe e os proprietários da organização poderão conectar uma equipe a um grupo de IdP no {% data variables.product.prodname_dotcom %} ou através da API. Para obter mais informações, consulte "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)" e "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md index 22629137e0..1a3ac20eed 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-confirm-saml.md @@ -1 +1 @@ -3. Confirme que o SAML SSO está habilitado. For more information, see "[Gerenciar logon único de SAML para sua organização](/articles/managing-saml-single-sign-on-for-your-organization)". +3. Confirme que o SAML SSO está habilitado. For more information, see "[Gerenciar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/)". diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md index 3c48c2cec4..7b2b739d40 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md @@ -1,5 +1,5 @@ Para ativar a sincronização da equipe para a Okta, você ou seu administrador de IdP devem: -- Ativar SAML SSO e SCIM para sua organização usando o Okta. Para obter mais informações, consulte "[Configuring SAML single sign-on and SCIM using Okta](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)" (Configurar SAML logon único e SCIM usando Okta) +- Ativar SAML SSO e SCIM para sua organização usando o Okta. Para obter mais informações, consulte "[Configuring SAML single sign-on and SCIM using Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)" (Configurar SAML logon único e SCIM usando Okta) - Forneça o URL do inquilino para sua instância Okta. - Gere um token SSWS válido com permissões de administrador somente leitura para a sua instalação do Okta como usuário do serviço. Para obter mais informações, consulte [Criar o token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) e [Usuários de serviços](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) na documentação de Okta. diff --git a/translations/pt-BR/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/pt-BR/data/reusables/organizations/team-discussions-are-for-orgs.md index bb98de0715..be6994cc2a 100644 --- a/translations/pt-BR/data/reusables/organizations/team-discussions-are-for-orgs.md +++ b/translations/pt-BR/data/reusables/organizations/team-discussions-are-for-orgs.md @@ -1 +1 @@ -Discussões de equipes só estão disponíveis em páginas de equipe em organizações. Para obter mais informações, consulte "[Sobre discussões de equipe](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)". +Discussões de equipes só estão disponíveis em páginas de equipe em organizações. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)". diff --git a/translations/pt-BR/data/reusables/organizations/team-synchronization.md b/translations/pt-BR/data/reusables/organizations/team-synchronization.md index 9c42cf20cd..02f6364118 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" or currentVersion == "github-ae@latest" %} -Você pode usar a sincronização de equipe para adicionar e remover automaticamente integrantes da organização às equipes 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)." +Você pode usar a sincronização de equipe para adicionar e remover automaticamente integrantes da organização às equipes por meio de um provedor de identidade. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md index 727ddc9db2..d3f7861c09 100644 --- a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md +++ b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md @@ -11,5 +11,5 @@ Os membros com permissões de mantenedor da equipe podem: - [Remover membros da organização da equipe](/articles/removing-organization-members-from-a-team) - [Promover um membro da equipe existente para um mantenedor de equipe](/articles/giving-team-maintainer-permissions-to-an-organization-member) - Remover o acesso da equipe aos repositórios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -- [Gerencie a atribuição de código de revisão para a equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} +- [Gerencie a atribuição de código de revisão para a equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md index e485cdec2c..40d0c22824 100644 --- a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. Crie um novo token de acesso pessoal (PAT) com os escopos apropriados para as tarefas que você deseja realizar. Se sua organização exigir SSO, você deverá habilitar o SSO para seu novo token. {% warning %} - **Observação:** Se você selecionar o escopo `write:packages`, desmarque o escopo `repositório` ao criar o PAT. Adicionar um PAT com o escopo de `repositório` como um segredo no repositório permite que a credencial seja acessível a todos os colaboradores do repositório. Isso fornece um acesso adicional desnecessário quando um PAT com o escopo do `repositório` é usado em uma ação. Para obter mais informações sobre as práticas de segurança recomendadas para ações, consulte "[Fortalecimento de segurança para o GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". + **Note:** By default, when you select the `write:packages` scope for your personal access token (PAT) in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for GitHub Actions workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://github.com/settings/tokens/new?scopes=write:packages`. {% endwarning %} diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index 4f95f7feb5..b660b74b1a 100644 --- a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,5 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} +Os PATs podem conceder amplo acesso à sua conta. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}. + To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)." diff --git a/translations/pt-BR/data/reusables/pages/choose-visibility.md b/translations/pt-BR/data/reusables/pages/choose-visibility.md index 310f66e173..c897cf7b66 100644 --- a/translations/pt-BR/data/reusables/pages/choose-visibility.md +++ b/translations/pt-BR/data/reusables/pages/choose-visibility.md @@ -1 +1 @@ -1. Opcionalmente, se você estiver publicando um site de projeto de um repositório privado ou interno pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, escolha a visibilidade do seu site. Em "{% data variables.product.prodname_pages %}", selecione o ** visibilidade de {% data variables.product.prodname_pages %}** no menu suspenso e, em seguida, clique em uma visibilidade. Para obter mais informações, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Menu suspenso para selecionar visibilidade para o seu site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file +1. Opcionalmente, se você estiver publicando um site de projeto de um repositório privado ou interno pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, escolha a visibilidade do seu site. Em "{% data variables.product.prodname_pages %}", selecione o ** visibilidade de {% data variables.product.prodname_pages %}** no menu suspenso e, em seguida, clique em uma visibilidade. Para obter mais informações, consulte "[Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Menu suspenso para selecionar visibilidade para o seu site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/decide-publishing-source.md b/translations/pt-BR/data/reusables/pages/decide-publishing-source.md index 59211352bc..bde5e1718d 100644 --- a/translations/pt-BR/data/reusables/pages/decide-publishing-source.md +++ b/translations/pt-BR/data/reusables/pages/decide-publishing-source.md @@ -1 +1 @@ -1. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}Decide{% else %}If you're creating a project site, decide{% endif %} which publishing source you want to use. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're creating a user or organization site, you must store your site's source code on the `master` branch.{% endif %} For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." +1. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" ou currentVersion == "github-ae@latest" %}Decida{% else %}Se você estiver criando um site de projeto, decida{% endif %} qual fonte de publicação você deseja usar. {% if currentVersion ver_lt "enterprise-server@2. 3" %}Se você estiver criando um site de usuário ou organização, você deverá armazenar o código-fonte do seu site no branch `mestre`.{% endif %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". diff --git a/translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md index 92e34d5128..0b225c6a28 100644 --- a/translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md +++ b/translations/pt-BR/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Observação:** Os proprietários da organização podem restringir a publicação de sites de {% data variables.product.prodname_pages %} de repositórios pertencentes à organização. Para obter mais informações, consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %}](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)". +**Observação:** Os proprietários da organização podem restringir a publicação de sites de {% data variables.product.prodname_pages %} de repositórios pertencentes à organização. Para obter mais informações, consulte "[Gerenciar a publicação de sites de {% data variables.product.prodname_pages %}](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md b/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md index a6af500463..bd057a379a 100644 --- a/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ {% warning %} -**Aviso**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Se o administrador do site tiver ativado páginas públicas, {% endif %}{% data variables.product.prodname_pages %} sites estão disponíveis publicamente na internet{% if currentVersion == "free-pro-team@latest" %} por padrão{% endif %}, Mesmo que o repositório para o site seja privado ou interno. {% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Caso contrário, se{% else %} Se{% endif %} tiver dados confidenciais no repositório do seu site, poderá remover os dados antes de publicar. Para mais informações, consulte{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}[Configurando {% data variables.product.prodname_pages %} para a sua empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" e{% endif %} "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" e "[Alterando a visibilidade do seu site {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site).{% else %}."{% endif %} +**Aviso**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Se o administrador do site tiver ativado páginas públicas, {% endif %}{% data variables.product.prodname_pages %} sites estão disponíveis publicamente na internet{% if currentVersion == "free-pro-team@latest" %} por padrão{% endif %}, Mesmo que o repositório para o site seja privado ou interno. {% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Caso contrário, se{% else %} Se{% endif %} tiver dados confidenciais no repositório do seu site, poderá remover os dados antes de publicar. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} {% endwarning %} diff --git a/translations/pt-BR/data/reusables/pages/sidebar-pages.md b/translations/pt-BR/data/reusables/pages/sidebar-pages.md new file mode 100644 index 0000000000..1e942a4a40 --- /dev/null +++ b/translations/pt-BR/data/reusables/pages/sidebar-pages.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png) +{% endif %} diff --git a/translations/pt-BR/data/reusables/pages/update_your_dns_settings.md b/translations/pt-BR/data/reusables/pages/update_your_dns_settings.md index c9856a7aff..ff3c1dd211 100644 --- a/translations/pt-BR/data/reusables/pages/update_your_dns_settings.md +++ b/translations/pt-BR/data/reusables/pages/update_your_dns_settings.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" %}1. Se houver um domínio personalizado habilitado para o seu site, para evitar que outra pessoa o tome, atualize suas configurações de DNS. Para obter mais informações, consulte "[Configurar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/configuring-a-custom-domain-for-your-github-pages-site)""{% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. Se houver um domínio personalizado habilitado para o seu site, para evitar que outra pessoa o tome, atualize suas configurações de DNS. Para obter mais informações, consulte "[Configurar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site)""{% endif %} diff --git a/translations/pt-BR/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/pt-BR/data/reusables/pages/www-and-apex-domain-recommendation.md index 35275b680e..e985a1c1c7 100644 --- a/translations/pt-BR/data/reusables/pages/www-and-apex-domain-recommendation.md +++ b/translations/pt-BR/data/reusables/pages/www-and-apex-domain-recommendation.md @@ -1 +1 @@ -Se você estiver usando um domínio apex como seu domínio personalizado, recomendamos também configurar um subdomínio `www`. Se você configurar os registros corretos para cada tipo de domínio através do seu provedor DNS, {% data variables.product.prodname_pages %} irá automaticamente criar redirecionamentos entre os domínios. Por exemplo, se você configurar `www.example.com` como seu domínio personalizado para o seu site, e você tem os registros `ALIAS` e `CNAME` configurados para os domínios apex e `www`. Logo, `example.com` irá redirecionar para `www.exemplo.com`. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)". +Se você estiver usando um domínio apex como seu domínio personalizado, recomendamos também configurar um subdomínio `www`. Se você configurar os registros corretos para cada tipo de domínio através do seu provedor DNS, {% data variables.product.prodname_pages %} irá automaticamente criar redirecionamentos entre os domínios. For example, if you configure `www.example.com` as the custom domain for your site, and you have {% data variables.product.prodname_pages %} DNS records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. Note that automatic redirects only apply to the `www` subdomain. Automatic redirects do not apply to any other subdomains, such as `blog`. diff --git a/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md index 041d949ef2..789bda84b5 100644 --- a/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -You can link a pull request to an issue to{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} show that a fix is in progress and to{% endif %} automatically close the issue when someone merges the pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." +Você pode vincular um pull request a um problema para{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %} mostrar que uma correção está em andamento e{% endif %} fechar automaticamente o problema quando alguém faz o merge do pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." diff --git a/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md index bab06a961b..a4c93243c3 100644 --- a/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md +++ b/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md @@ -1,7 +1,7 @@ {% note %} -**Notes:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -- To appear on your profile contributions graph, co-authored commits must meet the same criteria as commits with one author.{% endif %} -- When rebasing commits, the original authors of the commit and the person who rebased the commits, whether on the command line or on {% data variables.product.product_location %}, receive contribution credit. +**Observação:**{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +- Para aparecer no gráfico de contribuições do seu perfil, os commits de criação conjunta devem atender aos mesmos critérios que os commits com um autor.{% endif %} +- Ao fazer rebase dos commits, os autores originais do commit e a pessoa que fez o rebase dos commits, seja na linha de comando ou em {% data variables.product.product_location %}, receberá o crédito de contribuição. {% endnote %} diff --git a/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index f67f87dda3..c60f7b57d0 100644 --- a/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/pt-BR/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -6,6 +6,6 @@ - When [LDAP Sync is enabled](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync), if you remove a person from a repository, they will lose access but their forks will not be deleted. Se a pessoa for adicionada a uma equipe com acesso ao repositório original da organização dentro de três meses, seu acesso às bifurcações será automaticamente restaurado na próxima sincronização.{% endif %} - Você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual. -- As pessoas com permissões de administrador para um repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou interno{% endif %} podem impedir a bifurcação desse repositório, e os proprietários da organização podem impedir a bifurcação de qualquer repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou interno{% endif %} em uma organização. Para mais informações, consulte "[Gerenciar a política de bifurcação da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" e "[Gerenciar a política de bifurcação do seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". +- As pessoas com permissões de administrador para um repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou interno{% endif %} podem impedir a bifurcação desse repositório, e os proprietários da organização podem impedir a bifurcação de qualquer repositório privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" or currentVersion == "github-ae@latest" %} ou interno{% endif %} em uma organização. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} diff --git a/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md b/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md index 7230ee9994..4069452d97 100644 --- a/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md +++ b/translations/pt-BR/data/reusables/repositories/security-alerts-x-github-severity.md @@ -1 +1 @@ -Email notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} that affect one or more repositories include the `X-GitHub-Severity` header field. You can use the value of the `X-GitHub-Severity` header field to filter email notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}. +Notificações de e-mail para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %} que afetam um ou mais repositórios incluem o campo do cabeçalho `X-GitHub-Severity`. Você pode usar o valor do campo de cabeçalho `X-GitHub-Severity` para filtrar notificações de e-mail para {% if currentVersion == "free-pro-team@latest" ou currentVersion ver_gt "enterprise-server@2. 1" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de segurança{% endif %}. diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/pt-BR/data/reusables/repositories/sidebar-code-scanning-alerts.md index c59dc7d169..ed13c1776d 100644 --- a/translations/pt-BR/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ b/translations/pt-BR/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -1 +1 @@ -1. Na barra lateral esquerda, clique em **alertas de varredura de código**. Opcionalmente, selecione a ferramenta de varredura de código que você usou. ![Aba de "Alertas de varredura de código"](/assets/images/help/repository/sidebar-code-scanning-alerts.png) +1. Na barra lateral esquerda, clique em **alertas de varredura de código**. ![Aba de "Alertas de varredura de código"](/assets/images/help/repository/sidebar-code-scanning-alerts.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 b74d5905b1..e46622acd1 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. 9" ou currentVersion == "github-ae@latest" %}Se houver uma regra de branch protegido no repositório que exija um histórico de commit linear. você deve permitir merge de combinação por squash, merge de rebase ou ambos. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/suggest-changes.md b/translations/pt-BR/data/reusables/repositories/suggest-changes.md index 4e7a49c9ed..7405d386dd 100644 --- a/translations/pt-BR/data/reusables/repositories/suggest-changes.md +++ b/translations/pt-BR/data/reusables/repositories/suggest-changes.md @@ -1,2 +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. -![Suggestion block](/assets/images/help/pull_requests/suggestion-block.png) +1. Opcionalmente, para sugerir uma alteração específica à linha{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %} ou linhas{% endif %}, clique em {% octicon "diff" aria-label="The diff symbol" %} e, em seguida, edite o texto dentro do bloco de sugestão. ![Bloco de sugestão](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/pt-BR/data/reusables/saml/about-linked-identities.md b/translations/pt-BR/data/reusables/saml/about-linked-identities.md index a9be0672ab..51556686f5 100644 --- a/translations/pt-BR/data/reusables/saml/about-linked-identities.md +++ b/translations/pt-BR/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -Você pode visualizar a identidade de logon único que um integrante vinculou à sua conta de {% data variables.product.product_name %} Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre o SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". +Você pode visualizar a identidade de logon único que um integrante vinculou à sua conta de {% data variables.product.product_name %} Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". Se um integrante vincular a identidade incorreta à sua conta de {% data variables.product.product_name %}, você poderá revogar a identidade vinculada para permitir que o integrante tente novamente. diff --git a/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md b/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md index 7d2af0b17d..4a82dc7f6e 100644 --- a/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,5 @@ {% note %} -**Observação:** Os colaboradores externos não são obrigados a efetuar a autenticação com um IdP para acessar os recursos de uma organização com SSO do SAML. Para obter mais informações sobre colaboradores externos, consulte "[Níveis de permissão para uma organização](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)". +**Observação:** Os colaboradores externos não são obrigados a efetuar a autenticação com um IdP para acessar os recursos de uma organização com SSO do SAML. Para obter mais informações sobre colaboradores externos, consulte "[Níveis de permissão para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)". {% endnote %} 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 index 4ae5f2add3..cfad6356b5 100644 --- 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 @@ -7,6 +7,7 @@ | Alibaba Cloud | Segredo da chave de acesso à nuvem do Alibaba | alibaba_cloud_access_key_secret | | Amazon Web Services (AWS) | ID da Chave de Acesso do AWS da Amazon | aws_access_key_id | | Amazon Web Services (AWS) | Chave de acesso secreta do AWS da Amazon | aws_secret_access_key | +| Asana | Asana Personal Access Token | asana_personal_access_token | | Atlassian | Token da API de Atlassian | atlassian_api_token | | Atlassian | Token web de JSON de Atlassian | atlassian_jwt | | Azure | Token de acesso pessoal do Azure DevOps | azure_devops_personal_access_token | @@ -37,8 +38,12 @@ | GoCardless | Token de acesso de GoCardless Sandbox | gocardless_sandbox_access_token | | Google Cloud | Chave da API do GOogle | google_api_key | | Google Cloud | ID da chave privada do Google Cloud | google_cloud_private_key_id | +| Grafana | Grafana API Key | grafana_api_key | | Hashicorp Terraform | Token da API de Terraform Cloud / Enterprise | terraform_api_token | | Hubspot | Chave da API de Hubspot | hubspot_api_key | +| Intercom | Intercom Access Token | intercom_access_token | +| Lob | Lob Live API Key | lob_live_api_key | +| Lob | Lob Test API Key | lob_test_api_key | | Mailchimp | Chave da API de Mailchimp | mailchimp_api_key | | Mailgun | Chave da API de Mailgun | mailgun_api_key | | npm | Token de acesso de npm | npm_access_token | @@ -51,6 +56,7 @@ | Proctorio | Chave de segredo de Proctorio | proctorio_secret_key | | Pulumi | Token de acesso de Pulumi | pulumi_access_token | | PyPI | PyPI API Token | pypi_api_token | +| RubyGems | RubyGems API Key | rubygems_api_key | | Samsara | Token de API de Samsara | samsara_api_token | | Samsara | Token de acesso de OAuth de Samsara | samsara_oauth_access_token | | SendGrid | SendGrid API Key | sendgrid_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 index a297f39ed5..cae8ca1247 100644 --- 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 @@ -50,6 +50,7 @@ | Proctorio | Chave de segredo de Proctorio | | Pulumi | Token de acesso de Pulumi | | PyPI | PyPI API Token | +| RubyGems | RubyGems API Key | | Samsara | Token de API de Samsara | | Samsara | Token de acesso de OAuth de Samsara | | Shopify | Segredo compartilhado do aplicativo Shopify | diff --git a/translations/pt-BR/data/reusables/sponsors/choose-updates.md b/translations/pt-BR/data/reusables/sponsors/choose-updates.md index 269182cf45..8f3036275b 100644 --- a/translations/pt-BR/data/reusables/sponsors/choose-updates.md +++ b/translations/pt-BR/data/reusables/sponsors/choose-updates.md @@ -1 +1 @@ -4. Decida se deseja receber atualizações de e-mail da conta patrocinada e, em seguida, selecione ou desmarque "Receber atualizações da _CONTA_." ![Caixa de seleção para receber atualizações da conta patrocinada](/assets/images/help/sponsors/updates-checkbox-manage.png) +4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![Caixa de seleção para receber atualizações da conta patrocinada](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/pt-BR/data/reusables/sponsors/click-add-tier.md b/translations/pt-BR/data/reusables/sponsors/click-add-tier.md index 5be8d9c927..69f514d823 100644 --- a/translations/pt-BR/data/reusables/sponsors/click-add-tier.md +++ b/translations/pt-BR/data/reusables/sponsors/click-add-tier.md @@ -1 +1 @@ -1. Na parte inferior da página, clique em **Adicionar uma camada**. ![Botão adicionar camada](/assets/images/help/sponsors/add-a-tier-button.png) +1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![Botão adicionar camada](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/pt-BR/data/reusables/sponsors/enable-custom-amounts.md b/translations/pt-BR/data/reusables/sponsors/enable-custom-amounts.md new file mode 100644 index 0000000000..1889367cb9 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/enable-custom-amounts.md @@ -0,0 +1,2 @@ +1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png) +1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png) diff --git a/translations/pt-BR/data/reusables/sponsors/feedback.md b/translations/pt-BR/data/reusables/sponsors/feedback.md new file mode 100644 index 0000000000..9bcf7d3f00 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/feedback.md @@ -0,0 +1 @@ +Você pode compartilhar seus comentários sobre {% data variables.product.prodname_sponsors %} com {% data variables.product.company_short %}. To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)." diff --git a/translations/pt-BR/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/pt-BR/data/reusables/sponsors/manage-updates-for-orgs.md index 45f3e66482..006ec1052a 100644 --- a/translations/pt-BR/data/reusables/sponsors/manage-updates-for-orgs.md +++ b/translations/pt-BR/data/reusables/sponsors/manage-updates-for-orgs.md @@ -1 +1 @@ -Você pode designar qual endereço de e-mail recebe atualizações das contas que a sua organização patrocina. Para obter mais informações, consulte "[Gerenciar atualizações de contas que a sua organização patrocina](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)". +Você pode designar qual endereço de e-mail recebe atualizações das contas que a sua organização patrocina. Para obter mais informações, consulte "[Gerenciar atualizações de contas que a sua organização patrocina](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)". diff --git a/translations/pt-BR/data/reusables/sponsors/pay-prorated-amount.md b/translations/pt-BR/data/reusables/sponsors/pay-prorated-amount.md index 7929488b19..26d02bd740 100644 --- a/translations/pt-BR/data/reusables/sponsors/pay-prorated-amount.md +++ b/translations/pt-BR/data/reusables/sponsors/pay-prorated-amount.md @@ -1 +1 @@ -1. Como alternativa, se você estiver patrocinando como organização, para pagar um valor proporcional em vez de efetuar o pagamento mensal completo, em "Vence hoje", clique em **Pagar $X.XX proporcional hoje**. ![Link para valor proporcional de pagamento](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file +1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![Link para valor proporcional de pagamento](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md b/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md index fee14045a9..80d9ee7439 100644 --- a/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +1 @@ -Se você estiver patrocinando em nome da sua conta de usuário, você será cobrado imediatamente um valor proporcional ao tempo até sua próxima data normal de cobrança. Se estiver patrocinando em nome de uma organização, você poderá optar por pagar o valor rateado ou fazer o pagamento mensal completo. +If you're starting a monthly sponsorship on behalf of your user account, you'll immediately be charged a prorated amount for the time until your next regular billing date. Se estiver patrocinando em nome de uma organização, você poderá optar por pagar o valor rateado ou fazer o pagamento mensal completo. diff --git a/translations/pt-BR/data/reusables/sponsors/review-and-publish-tier.md b/translations/pt-BR/data/reusables/sponsors/review-and-publish-tier.md index cc7f62fd69..a84fd2930a 100644 --- a/translations/pt-BR/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/pt-BR/data/reusables/sponsors/review-and-publish-tier.md @@ -1 +1 @@ -1. Revise a sua camada e, em seguida, clique em **Publicar camada**. ![Botão Publicar camada](/assets/images/help/sponsors/publish-tier-button.png) +1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/pt-BR/data/reusables/sponsors/review-tiers-to-select.md b/translations/pt-BR/data/reusables/sponsors/review-tiers-to-select.md new file mode 100644 index 0000000000..49f840d7a5 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/review-tiers-to-select.md @@ -0,0 +1 @@ +1. No lado direito da página, em "Selecione uma camada", reveja as camadas de patrocínio disponíveis. If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png) diff --git a/translations/pt-BR/data/reusables/sponsors/select-a-tier.md b/translations/pt-BR/data/reusables/sponsors/select-a-tier.md index 4755b2ee80..8bd182284a 100644 --- a/translations/pt-BR/data/reusables/sponsors/select-a-tier.md +++ b/translations/pt-BR/data/reusables/sponsors/select-a-tier.md @@ -1 +1 @@ -1. No lado direito da página, em "Selecione uma camada", reveja as camadas de patrocínio disponíveis. Em seguida, à direita da camada que você quer, clique em **Selecionar**. ![Selecione uma caixa de camada](/assets/images/help/sponsors/select-a-tier-box.png) +1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![Selecione uma caixa de camada](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md b/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md index cfacc27a36..dfedaa160a 100644 --- a/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md +++ b/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -Você pode patrocinar qualquer pessoa com um perfil de desenvolvedor patrocinado ou perfil de organização patrocinado em nome de sua conta de usuário ou uma organização. Você pode escolher entre várias camadas de patrocínio, com montantes e benefícios mensais definidos pela conta patrocinada. O seu patrocínio compartilhará a data de cobrança existente da sua conta, o método de pagamento e o recibo. +Você pode patrocinar qualquer pessoa com um perfil de desenvolvedor patrocinado ou perfil de organização patrocinado em nome de sua conta de usuário ou uma organização. You can choose from multiple sponsorship tiers, with one-time or monthly payment amounts and benefits that are set by the sponsored account. O seu patrocínio compartilhará a data de cobrança existente da sua conta, o método de pagamento e o recibo. diff --git a/translations/pt-BR/data/reusables/sponsors/tier-details.md b/translations/pt-BR/data/reusables/sponsors/tier-details.md index 120569cec1..2135637279 100644 --- a/translations/pt-BR/data/reusables/sponsors/tier-details.md +++ b/translations/pt-BR/data/reusables/sponsors/tier-details.md @@ -1,3 +1,3 @@ -Você pode criar até dez camadas de patrocínio para escolher. Cada camada tem seu próprio montante de pagamento mensal em dólares e benefícios nos EUA, como receber acesso antecipado a novas versões ou ser destacado no README do projeto. +Você pode criar até dez camadas de patrocínio para escolher. Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). -Após publicar uma camada, você não pode editar o preço dessa camada. Em vez disso, você deve se retirar a camada e criar uma nova. Os patrocinadores existentes permanecerão na camada aposentada até mudar a sua camada de patrocínio ou cancelarem seu patrocínio. +Após publicar uma camada, você não pode editar o preço dessa camada. Em vez disso, você deve se retirar a camada e criar uma nova. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/pt-BR/data/reusables/support/accessing-premium-content.md b/translations/pt-BR/data/reusables/support/accessing-premium-content.md index c19782ddbb..eaca45a25e 100644 --- a/translations/pt-BR/data/reusables/support/accessing-premium-content.md +++ b/translations/pt-BR/data/reusables/support/accessing-premium-content.md @@ -1,4 +1,4 @@ ### Acessar conteúdo premium -Você pode acessar o conteúdo premium fazendo o login em {% data variables.contact.contact_enterprise_portal %}. +Você pode acessar o conteúdo premium fazendo o login em {% data variables.contact.contact_landing_page_portal %}. diff --git a/translations/pt-BR/data/reusables/support/contacting-premium-support.md b/translations/pt-BR/data/reusables/support/contacting-premium-support.md index f17558ba90..e1402d6fa9 100644 --- a/translations/pt-BR/data/reusables/support/contacting-premium-support.md +++ b/translations/pt-BR/data/reusables/support/contacting-premium-support.md @@ -1,4 +1,4 @@ ### Entrar em contato com o {% data variables.contact.premium_support %} -Os clientes de {% data variables.contact.premium_support %} podem utilizar o {% data variables.contact.contact_enterprise_portal %} para relatar problemas por escrito, em inglês. Você também pode receber suporte em inglês por telefone. Para obter o número de telefone de {% data variables.contact.premium_support %}, consulte "[Suporte por telefone 24 horas por dia](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)" em {% data variables.contact.enterprise_portal %}. +Os clientes de {% data variables.contact.premium_support %} podem utilizar o {% data variables.contact.contact_landing_page_portal %} para relatar problemas por escrito, em inglês. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md b/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md index c1d07e7683..4aa11c15f2 100644 --- a/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md +++ b/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md @@ -1 +1 @@ -For more information on commit email addresses,{% if currentVersion == "free-pro-team@latest" %} including your {% data variables.product.product_name %}-provided `noreply` email address,{% endif %} see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +Para obter mais informações sobre endereços de e-mail de commit,{% if currentVersion == "free-pro-team@latest" %} incluindo seu endereço de e-mail `noreply` fornecido por{% data variables.product.product_name %},{% endif %} consulte "[Configurar seu endereço de e-mail do commit](/articles/setting-your-commit-email-address)." diff --git a/translations/pt-BR/data/reusables/user_settings/billing_plans.md b/translations/pt-BR/data/reusables/user_settings/billing_plans.md new file mode 100644 index 0000000000..8d26ab1479 --- /dev/null +++ b/translations/pt-BR/data/reusables/user_settings/billing_plans.md @@ -0,0 +1 @@ +1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png) diff --git a/translations/pt-BR/data/variables/contact.yml b/translations/pt-BR/data/variables/contact.yml index 2e31eead2e..d845290b02 100644 --- a/translations/pt-BR/data/variables/contact.yml +++ b/translations/pt-BR/data/variables/contact.yml @@ -24,9 +24,12 @@ contact_enterprise_portal: '[Portal de suporte do Enterprise GitHub](https://ent #Azure support (GitHub AE) portal ae_azure_portal: 'Portal de suporte do Azure' contact_ae_portal: '[Portal de suporte do Azure](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)' -#GitHub Support portal (for dotcom) +#GitHub Support portal (for dotcom - this sends users to a contact form) support_portal: 'Portal de suporte do GitHub' contact_support_portal: '[Portal de suporte do GitHub](https://support.github.com/contact)' +#GitHub Support portal (this sends users to the Support landing page) +landing_page_portal: 'Portal de suporte do GitHub' +contact_landing_page_portal: '[Portal de suporte do GitHub](https://support.github.com/)' #The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) community_support: 'Suporte à Comunidade GitHub' #The GitHub Community forum 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 7e7f73a7f7..e2373929a2 100644 --- a/translations/ru-RU/content/actions/creating-actions/about-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/about-actions.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' topics: - - Action development - - Fundamentals + - 'Action development' + - 'Fundamentals' --- {% 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 0b55e2a358..ef9ab2d468 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Action development + - 'Action development' --- {% 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 4cb3ded29f..2240afb12d 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 @@ -1,6 +1,6 @@ --- title: Creating a Docker container action -intro: This guide shows you the minimal steps required to build a Docker container action. +intro: 'This guide shows you the minimal steps required to build a Docker container action.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Action development - - Докер + - 'Action development' + - 'Докер' --- {% 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 45ab3945f7..5b8697f208 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 @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Action development - - JavaScript + - 'Action development' + - 'JavaScript' --- {% 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 53b7356530..766bb16e0d 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 @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'ссылка' --- {% data reusables.actions.enterprise-beta %} 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 520e3ee6db..7229f06ede 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 @@ -12,7 +12,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: 'ссылка' --- {% data reusables.actions.enterprise-beta %} @@ -58,7 +58,7 @@ inputs: When you specify an input to an action in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters. -For example, if a workflow defined the numOctocats and octocatEyeColor inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables. +For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables. #### `inputs.` @@ -76,6 +76,10 @@ For example, if a workflow defined the numOctocats and octocatEyeColor inputs, t **Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file. +#### `inputs..deprecationMessage` + +**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives. + ### `outputs` **Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions. For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input. 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 cd2f166950..529379dd52 100644 --- a/translations/ru-RU/content/actions/guides/about-continuous-integration.md +++ b/translations/ru-RU/content/actions/guides/about-continuous-integration.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' topics: - - CI - - CD + - 'CI' + - 'CD' --- {% 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 fb57ef4b4d..7c4ffdb960 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 @@ -9,9 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' topics: - - Упаковка + - 'Упаковка' --- {% 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 aa6344348e..a132ed19d1 100644 --- a/translations/ru-RU/content/actions/guides/about-service-containers.md +++ b/translations/ru-RU/content/actions/guides/about-service-containers.md @@ -9,10 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' topics: - - Containers - - Докер + - 'Containers' + - 'Докер' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md b/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md index cf4673d1e3..fd903ea744 100644 --- a/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md +++ b/translations/ru-RU/content/actions/guides/adding-labels-to-issues.md @@ -1,15 +1,15 @@ --- title: Adding labels to issues -intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.' +intro: You can use {% data variables.product.prodname_actions %} to automatically label issues. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% 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 3190b9a22d..043104f83e 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CI - - Java - - Ant + - 'CI' + - 'Java' + - 'Ant' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Ant run: ant -noinput -buildfile build.xml ``` @@ -70,7 +71,7 @@ jobs: This workflow performs the following steps: 1. The `checkout` step downloads a copy of your repository on the runner. -2. The `setup-java` step configures the Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. The "Build with Ant" step runs the default target in your `build.xml` in non-interactive mode. The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs. @@ -91,9 +92,10 @@ If you use different commands to build your project, or you want to run a differ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Ant jar target run: ant -noinput -buildfile build-ci.xml jar ``` @@ -109,7 +111,11 @@ Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ant -noinput -buildfile build.xml - uses: actions/upload-artifact@v2 with: 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 ce1764d9aa..b502deafa4 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CI - - Java - - Gradle + - 'CI' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Gradle run: ./gradlew build ``` @@ -70,7 +71,7 @@ jobs: This workflow performs the following steps: 1. The `checkout` step downloads a copy of your repository on the runner. -2. The `setup-java` step configures the Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. The "Build with Gradle" step runs the `gradlew` wrapper script to ensure that your code builds, tests pass, and a package can be created. The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs. @@ -91,9 +92,10 @@ If you use different commands to build your project, or you want to use a differ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Gradle package task run: ./gradlew -b ci.gradle package ``` @@ -107,10 +109,11 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Gradle packages uses: actions/cache@v2 with: @@ -143,7 +146,11 @@ Gradle will usually create output files like JARs, EARs, or WARs in the `build/l ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ./gradlew build - uses: actions/upload-artifact@v2 with: 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 764393b859..322eba6139 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CI - - Java - - Maven + - 'CI' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Maven run: mvn --batch-mode --update-snapshots verify ``` @@ -70,7 +71,7 @@ jobs: This workflow performs the following steps: 1. The `checkout` step downloads a copy of your repository on the runner. -2. The `setup-java` step configures the Java 1.8 JDK. +2. The `setup-java` step configures the Java 11 JDK by Adoptium. 3. The "Build with Maven" step runs the Maven `package` target in non-interactive mode to ensure that your code builds, tests pass, and a package can be created. The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs. @@ -91,9 +92,10 @@ If you use different commands to build your project, or you want to use a differ ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Maven verify phase run: mvn --batch-mode --update-snapshots verify ``` @@ -107,10 +109,11 @@ When using {% data variables.product.prodname_dotcom %}-hosted runners, you can ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Maven packages uses: actions/cache@v2 with: @@ -134,7 +137,10 @@ Maven will usually create output files like JARs, EARs, or WARs in the `target` ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 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 index 80db671516..5cdbb65242 100644 --- a/translations/ru-RU/content/actions/guides/building-and-testing-net.md +++ b/translations/ru-RU/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: ['3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -81,7 +81,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet: [ '2.2.103', '3.0', '3.1.x' ] + dotnet: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -201,7 +201,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 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 a18f0da38d..f3a97bfde8 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 @@ -9,11 +9,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CI - - Node - - JavaScript + - 'CI' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} 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 2a5ee5e15d..cf26262e18 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 @@ -8,10 +8,10 @@ versions: github-ae: '*' authors: - potatoqualitee -type: tutorial +type: 'руководство' topics: - - CI - - Powershell + - 'CI' + - 'Powershell' --- {% 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 4fe13263b0..9366fd3d89 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 @@ -8,10 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CI - - Python + - 'CI' + - 'Python' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md b/translations/ru-RU/content/actions/guides/building-and-testing-ruby.md index 71ff62efbf..47423e7399 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 @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CI - - Ruby + - 'CI' + - 'Ruby' --- {% 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 a16b3c3fdf..7164aea511 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,9 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: tutorial +type: 'руководство' topics: - - Workflows + - 'Workflows' --- {% data reusables.actions.ae-beta %} diff --git a/translations/ru-RU/content/actions/guides/closing-inactive-issues.md b/translations/ru-RU/content/actions/guides/closing-inactive-issues.md index 3c90e164ff..e9389e1e83 100644 --- a/translations/ru-RU/content/actions/guides/closing-inactive-issues.md +++ b/translations/ru-RU/content/actions/guides/closing-inactive-issues.md @@ -1,15 +1,15 @@ --- title: Closing inactive issues -intro: 'You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time.' +intro: You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md index 0b508458db..f792bb8a6a 100644 --- a/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/ru-RU/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md @@ -1,15 +1,15 @@ --- title: Commenting on an issue when a label is added -intro: 'You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied.' +intro: You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 665165453f..e295853eae 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Containers - - Докер + - 'Containers' + - 'Докер' --- {% 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 e03f61c62b..9d2106d368 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Containers - - Докер + - 'Containers' + - 'Докер' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md index 5a2dd5ada0..6afda4cd7f 100644 --- a/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/ru-RU/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CD - - Containers - - Amazon ECS + - 'CD' + - 'Containers' + - 'Amazon ECS' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md b/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md index 7fcc6ad3b4..41da11d34f 100644 --- a/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/ru-RU/content/actions/guides/deploying-to-azure-app-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CD - - Containers - - Azure App Service + - 'CD' + - 'Containers' + - 'Azure App Service' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md index 72477b8c64..3645c7e402 100644 --- a/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/ru-RU/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CD - - Containers - - Google Kubernetes Engine + - 'CD' + - 'Containers' + - 'Google Kubernetes Engine' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/ru-RU/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 1fe04624a8..3e4d6891e1 100644 --- a/translations/ru-RU/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/ru-RU/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CI - - Xcode + - 'CI' + - 'Xcode' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/moving-assigned-issues-on-project-boards.md b/translations/ru-RU/content/actions/guides/moving-assigned-issues-on-project-boards.md index 340c0bb992..4740430167 100644 --- a/translations/ru-RU/content/actions/guides/moving-assigned-issues-on-project-boards.md +++ b/translations/ru-RU/content/actions/guides/moving-assigned-issues-on-project-boards.md @@ -1,15 +1,15 @@ --- title: Moving assigned issues on project boards -intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.' +intro: You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} 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 cb520caf7b..adc17dfa11 100644 --- a/translations/ru-RU/content/actions/guides/publishing-docker-images.md +++ b/translations/ru-RU/content/actions/guides/publishing-docker-images.md @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Упаковка - - Publishing - - Докер + - 'Упаковка' + - 'Publishing' + - 'Докер' --- {% 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 05504bd51f..67555b5e3d 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Упаковка - - Publishing - - Java - - Gradle + - 'Упаковка' + - 'Publishing' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -143,9 +144,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -209,9 +211,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to the Maven Central Repository run: gradle publish env: 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 210aedf884..7c1bec70c8 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Упаковка - - Publishing - - Java - - Maven + - 'Упаковка' + - 'Publishing' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -147,9 +148,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: mvn --batch-mode deploy env: @@ -183,9 +185,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java for publishing to Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -195,9 +198,10 @@ jobs: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to GitHub Packages run: mvn --batch-mode deploy env: 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 9ee28a5dd2..265d8f6b8a 100644 --- a/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md @@ -9,12 +9,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Упаковка - - Publishing - - Node - - JavaScript + - 'Упаковка' + - 'Publishing' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index 07aea71cd8..dcf96df5f2 100644 --- a/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/ru-RU/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -1,15 +1,15 @@ --- title: Removing a label when a card is added to a project board column -intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board.' +intro: You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md b/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md index af72f9fd58..205bef1450 100644 --- a/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md +++ b/translations/ru-RU/content/actions/guides/scheduling-issue-creation.md @@ -1,15 +1,15 @@ --- title: Scheduling issue creation -intro: 'You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews.' +intro: You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows - - Project management + - 'Workflows' + - 'Project management' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index b9100c2834..2520341f09 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 @@ -12,10 +12,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows - - CI + - 'Workflows' + - 'CI' --- {% 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 ec42acbf6d..a038188dce 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 @@ -12,9 +12,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Workflows + - 'Workflows' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/using-github-actions-for-project-management.md b/translations/ru-RU/content/actions/guides/using-github-actions-for-project-management.md index d1b1191979..1b8ab1b015 100644 --- a/translations/ru-RU/content/actions/guides/using-github-actions-for-project-management.md +++ b/translations/ru-RU/content/actions/guides/using-github-actions-for-project-management.md @@ -1,14 +1,14 @@ --- title: Using GitHub Actions for project management -intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.' +intro: You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks. product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' topics: - - Project management + - 'Project management' --- You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board. 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 8a3b96d95c..d78af529c7 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -125,7 +125,7 @@ You must ensure that the self-hosted runner has appropriate network access to co For example, if your instance name is `octoghae`, then you will need to allow the self-hosted runner to access `octoghae.github.com`. If you use an IP address allow list for your -{% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)." +{% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)." {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -145,7 +145,7 @@ pkg-containers.githubusercontent.com pkg-containers-az.githubusercontent.com ``` -If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". +If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". {% else %} 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 697a86c796..ffb29ba520 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 cbfa198d10..1f38152c85 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +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 2c09058474..300f0dc1e3 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 7a553a77e7..96b388edb4 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 @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +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 d56c4d03b4..523f02182e 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 bfda487925..d59a358c79 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 afe0afc78a..128114fbe2 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 @@ -5,7 +5,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 e67d3b62d6..2467189275 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' --- {% data reusables.actions.ae-self-hosted-runners-notice %} diff --git a/translations/ru-RU/content/actions/index.md b/translations/ru-RU/content/actions/index.md index d32dfec985..0f1b4b9341 100644 --- a/translations/ru-RU/content/actions/index.md +++ b/translations/ru-RU/content/actions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /actions/reference/encrypted-secrets changelog: label: 'actions' - prefix: 'GitHub Actions: ' + prefix: 'GitHub Actions:' product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ 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 8c81c8ded6..cc5397d51f 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' topics: - - Fundamentals + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} 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 65bd6f61c8..c577411fe0 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 @@ -10,9 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: 'обзор' topics: - - Fundamentals + - 'Fundamentals' --- {% data reusables.actions.enterprise-beta %} 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 27e5288030..dbb8eaa939 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Azure Pipelines - - Migration - - CI - - CD + - 'Azure Pipelines' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 7c87a322a0..8d35afad02 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - CircleCI - - Migration - - CI - - CD + - 'CircleCI' + - 'Migration' + - 'CI' + - 'CD' --- {% 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 0013d4bf65..ed87381117 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 @@ -5,12 +5,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - GitLab - - Migration - - CI - - CD + - 'GitLab' + - 'Migration' + - 'CI' + - 'CD' --- {% 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 29977e4b77..3757777bd5 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Jenkins - - Migration - - CI - - CD + - 'Jenkins' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 5269453b5b..c0e3c64534 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: 'руководство' topics: - - Travis CI - - Migration - - CI - - CD + - 'Travis CI' + - 'Migration' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 2d561318f7..1d2700c713 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,13 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: overview + github-ae: '*' +type: 'обзор' topics: - - Безопасность + - 'Безопасность' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### Обзор @@ -22,9 +24,9 @@ This guide explains how to configure security hardening for certain {% data vari ### Using secrets -Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}. +Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}. -Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps the minimize risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime. +Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps minimize the risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime. To help prevent accidental disclosure, {% data variables.product.product_name %} uses a mechanism that attempts to redact any secrets that appear in run logs. This redaction looks for exact matches of any configured secrets, as well as common encodings of the values, such as Base64. However, because there are multiple ways a secret value can be transformed, this redaction is not guaranteed. As a result, there are certain proactive steps and good practices you should follow to help ensure secrets are redacted, and to limit other risks associated with secrets: @@ -41,7 +43,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %} - **Audit and rotate registered secrets** - Periodically review the registered secrets to confirm they are still required. Remove those that are no longer needed. - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - **Consider requiring review for access to secrets** - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)." {% endif %} @@ -75,7 +77,7 @@ This means that a compromise of a single action within a workflow can be very si ### Considering cross-repository access -{% data variables.product.product_name %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so having the `GITHUB_TOKEN` for one repository grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators. +{% data variables.product.prodname_actions %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so allowing the `GITHUB_TOKEN` for one repository to grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators. We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended. @@ -115,33 +117,68 @@ Some customers might attempt to partially mitigate these risks by implementing s You can use the audit log to monitor administrative tasks in an organization. The audit log records the type of action, when it was run, and which user account performed the action. -For example, you can use the audit log to track the `action:org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png) +For example, you can use the audit log to track the `org.update_actions_secret` event, which tracks changes to organization secrets: ![Audit log entries](/assets/images/help/repository/audit-log-entries.png) -The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." + +{% if currentVersion == "free-pro-team@latest" %} +#### Events for environments + +| Действие | Description | +| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `environment.remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `environment.update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### Events for configuration changes +| Действие | Description | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +{% endif %} #### Events for secret management -| Действие | Description | -| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `action:org.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). | -| `action:org.remove_actions_secret` | Triggered when a organization admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:org.update_actions_secret` | Triggered when a organization admin updates a {% data variables.product.prodname_actions %} secret. | -| `action:repo.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). | -| `action:repo.remove_actions_secret` | Triggered when a repository admin removes a {% data variables.product.prodname_actions %} secret. | -| `action:repo.update_actions_secret` | Triggered when a repository admin updates a {% data variables.product.prodname_actions %} secret. | +| Действие | Description | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `org.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)." | +| `org.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed. | +| `org.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated. | +| `repo.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." | +| `repo.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed. | +| `repo.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated. | #### Events for self-hosted runners -| Действие | Description | -| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.register_self_hosted_runner` | Triggered when an organization owner [registers a new self-hosted runner](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization). | -| `action:org.remove_self_hosted_runner` | Triggered when an organization owner [removes a self-hosted runner](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | -| `action:repo.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). | -| `action:repo.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). | +| Действие | Description | +| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% else %} | | +| `enterprise.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an enterprise](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)." | +| `enterprise.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. | +| `enterprise.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." | +| `enterprise.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI. This event is not included when you export the audit log as JSON data or a CSV file. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" and "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."{% endif %} +| `org.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." | +| `org.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see [Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | +| `org.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." | +| `org.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `org.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | +| `repo.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `repo.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." | +| `repo.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | #### Events for self-hosted runner groups -| Действие | Description | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.runner_group_created` | Triggered when an organization admin [creates a self-hosted runner group](/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` | Triggered when an organization admin removes a self-hosted runner group. | -| `action:org.runner_group_renamed` | Triggered when an organization admin renames a self-hosted runner group. | -| `action:org.runner_group_runners_added` | Triggered when an organization admin [adds a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | -| `action:org.runner_group_runners_removed` | Triggered when an organization admin removes a self-hosted runner from a group. | +| Действие | Description | +| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `enterprise.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an enterprise](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)." | +| `enterprise.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `enterprise.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. | +| `enterprise.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." | +| `enterprise.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `org.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." | +| `org.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `org.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." | +| `org.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | + +#### Events for workflow activities + +{% data reusables.actions.actions-audit-events-workflow %} diff --git a/translations/ru-RU/content/actions/quickstart.md b/translations/ru-RU/content/actions/quickstart.md index deb724657e..bd3a0189cc 100644 --- a/translations/ru-RU/content/actions/quickstart.md +++ b/translations/ru-RU/content/actions/quickstart.md @@ -1,6 +1,6 @@ --- title: Quickstart for GitHub Actions -intro: 'Add a {% data variables.product.prodname_actions %} workflow to an existing repository in 5 minutes or less.' +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates @@ -19,57 +19,58 @@ topics: ### Introduction -You only need an existing {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that lints multiple coding languages using the [{% data variables.product.prodname_dotcom %} Super-Linter action](https://github.com/github/super-linter). The workflow uses Super-Linter to validate your source code every time a new commit is pushed to your repository. +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. + +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. ### Creating your first workflow -1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `superlinter.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." -2. Copy the following YAML contents into the `superlinter.yml` file. **Note:** If your default branch is not `main`, update the value of `DEFAULT_BRANCH` to match your repository's default branch name. +1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." +2. Copy the following YAML contents into the `github-actions-demo.yml` file: {% raw %} ```yaml{:copy} - name: Super-Linter - - # Run this workflow every time a new commit pushed to your repository - on: push - + name: GitHub Actions Demo + 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 + Explore-GitHub-Actions: runs-on: ubuntu-latest - steps: - # Checks out a copy of your repository on the ubuntu-latest machine - - name: Checkout code + - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event." + - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!" + - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}." + - name: Check out repository code uses: actions/checkout@v2 + - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner." + - run: echo "🖥️ The workflow is now ready to test your code on the runner." + - name: List files in the repository + run: | + ls ${{ github.workspace }} + - run: echo "🍏 This job's status is ${{ job.status }}." - # 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. To run your workflow, scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. ![Commit workflow file](/assets/images/commit-workflow-file.png) +3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**. ![Commit workflow file](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -Committing the workflow file in your repository triggers the `push` event and runs your workflow. +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. ### Viewing your workflow results {% 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" or currentVersion == "github-ae@latest" %} -1. Under **Jobs** or in the visualization graph, click the **Lint code base** job. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) -{% else %} -1. In the left sidebar, click the **Lint code base** job. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) -{% endif %} -{% data reusables.repositories.view-failed-job-results-superlinter %} +1. In the left sidebar, click the workflow you want to see. + + ![Workflow list in left sidebar](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +1. From the list of workflow runs, click the name of the run you want to see. + + ![Name of workflow run](/assets/images/help/repository/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. + + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. + + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) ### More workflow templates @@ -77,74 +78,12 @@ Committing the workflow file in your repository triggers the `push` event and ru ### Дальнейшие шаги -The super-linter workflow you just added runs each time code is pushed to your repository to help you spot errors and inconsistencies in your code. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}: +The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}: -- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial -- "[Guides](/actions/guides)" for specific uses cases and examples -- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action +- Your repository can contain multiple workflows that trigger different jobs based on different events. +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. - +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial. +- "[Guides](/actions/guides)" for specific uses cases and examples. diff --git a/translations/ru-RU/content/actions/reference/environment-variables.md b/translations/ru-RU/content/actions/reference/environment-variables.md index ee04934f98..9248fb40e8 100644 --- a/translations/ru-RU/content/actions/reference/environment-variables.md +++ b/translations/ru-RU/content/actions/reference/environment-variables.md @@ -22,6 +22,7 @@ versions: To set custom environment variables, you need to specify the variables in the workflow file. 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. For more information, see "[Workflow syntax for {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)." +{% raw %} ```yaml jobs: weekday_job: @@ -30,13 +31,14 @@ jobs: DAY_OF_WEEK: Mon steps: - name: "Hello world when it's Monday" - if: env.DAY_OF_WEEK == 'Mon' + if: ${{ env.DAY_OF_WEEK == 'Mon' }} run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" env: FIRST_NAME: Mona middle_name: The Last_Name: Octocat ``` +{% endraw %} To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables. diff --git a/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md b/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md index 1464d1ea1d..7ec159acee 100644 --- a/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/ru-RU/content/actions/reference/usage-limits-billing-and-administration.md @@ -70,7 +70,7 @@ You can configure the artifact and log retention period for your repository, org Дополнительные сведения см. в: - [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your repository](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) -- [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) - [Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your enterprise](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) {% endif %} @@ -80,7 +80,7 @@ You can configure the artifact and log retention period for your repository, org Дополнительные сведения см. в: - "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)" -- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} +- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" for {% data variables.product.prodname_ghe_cloud %}{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} diff --git a/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 710772579c..ef7aa33326 100644 --- a/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/ru-RU/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -21,7 +21,7 @@ After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_ma * Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization. * Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}. -For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, 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)." +For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ### Требования diff --git a/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index e0a5883b98..83e21731b4 100644 --- a/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/ru-RU/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -28,7 +28,7 @@ The provisioning application on your IdP communicates with {% data variables.pro {% data reusables.scim.supported-idps %} -When you set up user provisioning with a supported IdP, you can also assign or unassign the application for {% data variables.product.product_name %} to groups of users. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. 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)." +When you set up user provisioning with a supported IdP, you can also assign or unassign the application for {% data variables.product.product_name %} to groups of users. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ### Требования diff --git a/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index 0fd0e9dcd6..98e7414d45 100644 --- a/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/ru-RU/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -13,7 +13,7 @@ By default, authorized users can access your enterprise from any IP address. Ent {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance. diff --git a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md index fca9bcced4..4c80cbedcc 100644 --- a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md +++ b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md @@ -37,7 +37,7 @@ In addition to all of the benefits of {% data variables.contact.enterprise_suppo {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} For more information, see "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)." +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md index 546c0ea912..d15418ab56 100644 --- a/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md +++ b/translations/ru-RU/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md @@ -35,7 +35,7 @@ In addition to all of the benefits of {% data variables.contact.enterprise_suppo {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} For more information, see "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)." +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/ru-RU/content/admin/github-actions/index.md b/translations/ru-RU/content/admin/github-actions/index.md index 7663491ab0..c40cf33b05 100644 --- a/translations/ru-RU/content/admin/github-actions/index.md +++ b/translations/ru-RU/content/admin/github-actions/index.md @@ -32,6 +32,7 @@ topics: {% 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 /using-the-latest-version-of-the-official-bundled-actions %} {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} {% topic_link_in_list /advanced-configuration-and-troubleshooting %} 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 76b312a056..fb00052b33 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 @@ -28,8 +28,21 @@ The `actions-sync` tool can only download actions from {% data variables.product ### Требования -* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." * You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. + + {% note %} + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + + {% endnote %} + + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." + + ```shell + ghe-org-admin-promote -u USERNAME -o actions + ``` ### Example: Using the `actions-sync` tool diff --git a/translations/ru-RU/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ru-RU/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md new file mode 100644 index 0000000000..ac100a941d --- /dev/null +++ b/translations/ru-RU/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md @@ -0,0 +1,45 @@ +--- +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' +versions: + enterprise-server: '>=2.22' +topics: + - корпоративный +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server). + +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}. + +Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}: + +- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}. +- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions. + +These options are described in more detail in the following sections. + +### Using actions-sync to update a bundled action + +To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." + +### Using actions from {% data variables.product.prodname_dotcom_the_website %} + +{% data reusables.github-actions.actions-github-connect-requirement %} + +Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file. + +### Using the latest version by removing the specific action's tag + +{% data reusables.github-actions.actions-github-connect-requirement %} + +If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)." + +For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}: + +1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository. +1. Create a workflow that uses `actions/setup-python` with the `v2` tag. + +When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}. 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 03dda2885a..189afb3189 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 @@ -1,6 +1,6 @@ --- title: Installing GitHub Enterprise Server on Hyper-V -intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2016.' +intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2019.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v @@ -13,7 +13,7 @@ topics: ### Требования - {% data reusables.enterprise_installation.software-license %} -- You must have Windows Server 2008 through Windows Server 2016, which support Hyper-V. +- You must have Windows Server 2008 through Windows Server 2019, which support Hyper-V. - Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). However, we recommend using the Windows PowerShell command-line shell for initial setup. Examples using PowerShell are included below. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)." ### Hardware considerations diff --git a/translations/ru-RU/content/admin/overview/github-ae-release-notes.md b/translations/ru-RU/content/admin/overview/github-ae-release-notes.md index 23940b2332..c82d226f05 100644 --- a/translations/ru-RU/content/admin/overview/github-ae-release-notes.md +++ b/translations/ru-RU/content/admin/overview/github-ae-release-notes.md @@ -29,7 +29,7 @@ During this beta, {% data variables.product.prodname_advanced_security %} featur #### Manage teams from your identity provider (IdP) -Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group. 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)." +Customers using SCIM (System for Cross-domain Identity Management) can now sync security groups in Azure Active Directory with {% data variables.product.company_short %} teams. Once a team has been linked to a security group, membership will be automatically updated in {% data variables.product.product_name %} when a user is added or removed from their assigned security group. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." #### IP allow lists beta @@ -37,7 +37,7 @@ Enterprise and organization owners can now use IP allow lists to restrict traffi This functionality is provided in addition to the ability to request network security group changes that filter traffic to the entirety of the {% data variables.product.product_name %} tenant. -For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." #### Pull request auto-merge @@ -47,8 +47,8 @@ With auto-merge, pull requests can be set to merge automatically when all merge #### Developer changes -- [Organization owners can now disable publication](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites. -- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). +- [Organization owners can now disable publication](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites. +- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - When writing an issue or pull request, the list syntax for bullets, numbers, and tasks will now be autocompleted after you press `return` or `enter`. - You can now delete a directory in a repository from the repository page. When navigating to a directory, a new kebab button next to the "Add file" button gives the option to delete the directory. - It’s now easier and faster to [reference issues or pull requests](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), with search across multiple words after the "#". @@ -65,7 +65,7 @@ With auto-merge, pull requests can be set to merge automatically when all merge ##### Default branch renaming -Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[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)." +Enterprise and organization owners can now set the default branch name for new repositories. Enterprise owners can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)" and "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." Existing repositories are unaffected by these settings, and their default branch name will not be changed. 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 d7cff857e3..7877f3f2fc 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 @@ -66,17 +66,16 @@ Mandatory messages have a variety of uses. - 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 %} -{% note %} - -**Note:** After you configure a mandatory message for {% data variables.product.product_location %}, you cannot change or remove the message. - -{% endnote %} - - 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)." +{% note %} + +**Note:** If you change the mandatory message for {% data variables.product.product_location %}, users who have already acknowledged the message will not see the new message. + +{% endnote %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} diff --git a/translations/ru-RU/content/code-security/secret-security/about-secret-scanning.md b/translations/ru-RU/content/code-security/secret-security/about-secret-scanning.md index e84961e5ed..0d1328cefc 100644 --- a/translations/ru-RU/content/code-security/secret-security/about-secret-scanning.md +++ b/translations/ru-RU/content/code-security/secret-security/about-secret-scanning.md @@ -45,7 +45,7 @@ When {% data variables.product.prodname_secret_scanning %} detects a set of cred {% 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)." +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](/organizations/keeping-your-organization-secure/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. diff --git a/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md index a692742bf4..d70acd2b01 100644 --- a/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md +++ b/translations/ru-RU/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md @@ -70,4 +70,4 @@ You can also ignore individual alerts from {% data variables.product.prodname_se ### Дополнительная литература -- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/ru-RU/content/code-security/secure-coding/index.md b/translations/ru-RU/content/code-security/secure-coding/index.md index db87c61bb8..33377f0fe3 100644 --- a/translations/ru-RU/content/code-security/secure-coding/index.md +++ b/translations/ru-RU/content/code-security/secure-coding/index.md @@ -1,7 +1,7 @@ --- title: Finding security vulnerabilities and errors in your code shortTitle: Secure coding -intro: 'Keep your code secure by using secret scanning to identify and fix potential security vulnerabilities and other errors in your code.' +intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code diff --git a/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md index 831282a2ec..5ba158d53b 100644 --- a/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ru-RU/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md @@ -45,7 +45,14 @@ You need write permission to view a summary of all the alerts for a repository o {% 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) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} +1. Optionally, use the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) @@ -57,7 +64,11 @@ If you have write permission for a repository, you can view fixed alerts by view 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +{% else %} +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} @@ -110,11 +121,19 @@ To dismiss or delete alerts: 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) +{% else %} + ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) +{% endif %} 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) diff --git a/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md index 2909125701..0900e69c32 100644 --- a/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md +++ b/translations/ru-RU/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md @@ -32,7 +32,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -72,7 +72,11 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re 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. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} {% endnote %} @@ -98,7 +102,11 @@ There are other situations where there may be no analysis for the latest commit To the right of "Code scanning", click **Set up code scanning**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% else %} + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) +{% endif %} The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. diff --git a/translations/ru-RU/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/ru-RU/content/code-security/security-advisories/editing-a-security-advisory.md index ab573b7f4e..fa50e87dc1 100644 --- a/translations/ru-RU/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/ru-RU/content/code-security/security-advisories/editing-a-security-advisory.md @@ -17,6 +17,8 @@ You can credit people who helped discover, report, or fix a security vulnerabili If someone accepts credit, the person's username appears in the "Credits" section of the security advisory. Anyone with read access to the repository can see the advisory and the people who accepted credit for it. +If you believe you should be credited for a security advisory, please contact the person who created the advisory and ask them to edit the advisory to include your credit. Only the creator of the advisory can credit you, so please don't contact GitHub Support about credits for security advisories. + ### Editing a security advisory {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/ru-RU/content/code-security/security-overview/exploring-security-alerts.md b/translations/ru-RU/content/code-security/security-overview/exploring-security-alerts.md index 32222253bf..4f5a26c9ec 100644 --- a/translations/ru-RU/content/code-security/security-overview/exploring-security-alerts.md +++ b/translations/ru-RU/content/code-security/security-overview/exploring-security-alerts.md @@ -11,7 +11,7 @@ versions: ### About the security overview -You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository)." +You can use the security overview for a high-level view of the security status of your organization or to identify problematic repositories that require intervention. At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." The security overview indicates whether {% data variables.product.prodname_GH_advanced_security %} features are enabled for repositories owned by your organization and consolidates alerts from {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} alerts, {% data variables.product.prodname_dependabot_alerts %}, and {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[About securing your repository](/code-security/getting-started/about-securing-your-repository)." diff --git a/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md index 8cf4e80954..ba9f1046fd 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md @@ -49,9 +49,9 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} diff --git a/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md index c6775c87fe..d831bca031 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/about-dependabot-version-updates.md @@ -12,8 +12,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot_version_updates %} {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. diff --git a/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md index 4f2a680635..e2311f076f 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/about-the-dependency-graph.md @@ -90,6 +90,6 @@ The recommended formats explicitly define which versions are used for all direct - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md index 9fcbfca3ea..0f38badc3f 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md @@ -11,8 +11,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About the *dependabot.yml* file The {% data variables.product.prodname_dependabot %} configuration file, *dependabot.yml*, uses YAML syntax. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." @@ -323,7 +321,7 @@ updates: {% note %} -**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. 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-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." +**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)." {% endnote %} diff --git a/translations/ru-RU/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md index 30a3a87790..e2834bc3d3 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md @@ -49,7 +49,7 @@ If security updates are not enabled for your repository and you don't know why, 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)." +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](/organizations/keeping-your-organization-secure/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)." diff --git a/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md index e339b81a3c..8c044bd77e 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md @@ -16,7 +16,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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" %} diff --git a/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md index 7ca4077ba2..f058194f72 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/customizing-dependency-updates.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About customizing dependency updates After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could: diff --git a/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md index 86e61e527a..784a8ccb2f 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md @@ -12,8 +12,6 @@ topics: -{% data reusables.dependabot.beta-note-no-link %} - ### About version updates for dependencies You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a *dependabot.yml* configuration file in to your repository's `.github` directory. {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. For each package manager's dependencies that you want to update, you must specify the location of the package manifest files and how often to check for updates to the dependencies listed in those files. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -117,7 +115,7 @@ updates: interval: "daily" # Overwrite any ignores created using `@dependabot ignore` commands ignore: - # Ignore updates to packages that start 'aws' + # Ignore updates to packages that start with 'aws' # Wildcards match zero or more arbitrary characters - dependency-name: "aws*" # Ignore some updates to the 'express' package diff --git a/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md index 6f48471c27..6919d3a67a 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md @@ -74,7 +74,7 @@ For public repositories, the dependents view shows how the repository is used by Repository administrators can enable or disable the dependency graph for private repositories. -You can also enable or disable the dependency graph 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)." +You can also enable or disable the dependency graph 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -114,7 +114,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ### Дополнительная литература - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)" {% endif %} diff --git a/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md index 35f33635bd..b2e9906953 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md @@ -10,8 +10,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot_version_updates %} for actions Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md index 0f1e222c63..b58accff31 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### Viewing dependencies monitored by {% data variables.product.prodname_dependabot %} After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." diff --git a/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md index 899d763033..53a261fe7d 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md @@ -9,8 +9,6 @@ topics: - repositories --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot %} pull requests {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md index e95181c704..7477851617 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md @@ -11,8 +11,6 @@ topics: - безопасность --- -{% data reusables.dependabot.beta-note %} - ### About {% data variables.product.prodname_dependabot %} errors {% data reusables.dependabot.pull-request-introduction %} 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 967ec9849c..6e11fa7b58 100644 --- a/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/authorizing-oauth-apps.md @@ -86,18 +86,18 @@ Exchange this `code` for an access token: By default, the response takes the following form: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer You can also receive the content in different formats depending on the Accept header: Accept: application/json - {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} + {"access_token":"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} Accept: application/xml bearer repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} #### 3. Use the access token to access the API @@ -207,7 +207,7 @@ Once the user has authorized, the app will receive an access token that can be u ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "user" } @@ -304,3 +304,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} * "[Device flow errors](#errors-for-the-device-flow)" {% endif %} + +### Дополнительная литература + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md index 23531bffd6..ef35a5be54 100644 --- a/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/ru-RU/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -54,16 +54,18 @@ The person creating the app will be redirected to a GitHub page with an input fi ##### GitHub App Manifest parameters - | Name | Тип | Description | - | --------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `строка` | The name of the GitHub App. | - | `url` | `строка` | **Required.** The homepage of your GitHub App. | - | `hook_attributes` | `объект` | The configuration of the GitHub App's webhook. | - | `redirect_url` | `строка` | The full URL to redirect to after the person installs the GitHub App. | - | `описание` | `строка` | A description of the GitHub App. | - | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | - | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | - | `default_permissions` | `объект` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | + | Name | Тип | Description | + | --------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `строка` | The name of the GitHub App. | + | `url` | `строка` | **Required.** The homepage of your GitHub App. | + | `hook_attributes` | `объект` | The configuration of the GitHub App's webhook. | + | `redirect_url` | `строка` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs.{% else %} + | `callback_url` | `строка` | A full URL to redirect to after someone authorizes an installation.{% endif %} + | `описание` | `строка` | A description of the GitHub App. | + | `public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app. | + | `default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to. | + | `default_permissions` | `объект` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. The format of the object uses the permission name for the key (for example, `issues`) and the access type for the value (for example, `write`). | The `hook_attributes` object has the following key: @@ -96,7 +98,10 @@ This example uses a form on a web page with a button that triggers the `POST` re "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -111,10 +116,11 @@ This example uses a form on a web page with a button that triggers the `POST` re }) ``` + This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app. ```html -
+ Create a GitHub App Manifest:
@@ -127,7 +133,10 @@ This example uses a form on a web page with a button that triggers the `POST` re "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -147,11 +156,11 @@ This example uses a form on a web page with a button that triggers the `POST` re When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. Например: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. Например: - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 #### 3. You exchange the temporary code to retrieve the app configuration diff --git a/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md index e6b2cc69e6..35b52acb79 100644 --- a/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/ru-RU/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -22,9 +22,15 @@ The person creating the app can edit the preselected values from the {% data var The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: - ``` - {% 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 - ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} +``` +{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite +``` +{% else %} +``` +{% 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 +``` +{% endif %} The complete list of available query parameters, permissions, and events is listed in the sections below. @@ -34,8 +40,9 @@ The complete list of available query parameters, permissions, and events is list | -------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | `строка` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. | | `описание` | `строка` | A description of the {% data variables.product.prodname_github_app %}. | - | `url` | `строка` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage. | - | `callback_url` | `строка` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. | + | `url` | `строка` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.{% else %} + | `callback_url` | `строка` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %} | `request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. | | `setup_url` | `строка` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation. | | `setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed. | 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 34bfdd1f94..5a691658bd 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 @@ -845,7 +845,7 @@ Here are a few common problems and some suggested solutions. If you run into any **A:** If you see the following error, you haven't deleted the checkout of the repository in one or both of the `initiate_check_run` or `take_requested_action` methods: ```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.: + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: ``` Compare your code to the `server.rb` file to ensure you have the same code in your `initiate_check_run` and `take_requested_action` methods. diff --git a/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index 293328fb88..533b3ec942 100644 --- a/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ru-RU/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -94,9 +94,9 @@ By default, the response takes the following form. The response parameters `expi ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -106,7 +106,7 @@ By default, the response takes the following form. The response parameters `expi By default, the response takes the following form: - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer {% endif %} @@ -934,3 +934,11 @@ While most of your API interaction should occur using your server-to-server inst * [Get a workflow](/rest/reference/actions#get-a-workflow) * [Get workflow usage](/rest/reference/actions#get-workflow-usage) {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Дополнительная литература + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md index 65eb1138d0..3edca8cef1 100644 --- a/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,9 +42,9 @@ This callback request will send you a new access token and a new refresh token. ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" @@ -73,3 +73,11 @@ If you want your app to use non-expiring user-to-server access tokens, you can d Existing {% data variables.product.prodname_github_app %}s using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app. Enabling expiring user tokens for existing {% data variables.product.prodname_github_app %}s requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### Дополнительная литература + +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)" + +{% endif %} diff --git a/translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md b/translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md index cb527f39f6..05f9449eb8 100644 --- a/translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md +++ b/translations/ru-RU/content/developers/github-marketplace/about-marketplace-badges.md @@ -13,7 +13,7 @@ Certain apps on the {% data variables.product.prodname_marketplace %} have the { - Verified ownership of their domain and has a verified badge on their profile - Confirmed their email address so {% data variables.product.prodname_dotcom %} Support can reach the organization -- Required two-factor authentication for their organization. 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)." +- Required two-factor authentication for their organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)." ![Marketplace badge for GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png) diff --git a/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md index c9f8610152..7fbaa69082 100644 --- a/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md +++ b/translations/ru-RU/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -22,8 +22,8 @@ To offer paid plans for your app, the app must be owned by an organization and y 1. Under "Developer settings", click **Publisher Verification**. ![Publisher verification option in the organization settings sidebar](/assets/images/marketplace/publisher-verification-settings-option.png) 1. Under "Publisher Verification", complete the information in the checklist: - Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}. - - Ensure that Two-factor authentication is enabled for your organization. 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)." - - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." + - Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)." + - Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." ![Publisher Verification checklist](/assets/images/marketplace/publisher-verification-checklist.png) diff --git a/translations/ru-RU/content/developers/overview/managing-deploy-keys.md b/translations/ru-RU/content/developers/overview/managing-deploy-keys.md index 4d8bc47df2..ee112d1de1 100644 --- a/translations/ru-RU/content/developers/overview/managing-deploy-keys.md +++ b/translations/ru-RU/content/developers/overview/managing-deploy-keys.md @@ -112,6 +112,36 @@ You can then use the hostname's alias to interact with the repository using SSH, $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` +### Server-to-server tokens + +If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents. + +Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for Github Apps](/developers/apps/rate-limits-for-github-apps). + +##### Pros + +- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API). +- Dedicated rate limits that grow with your organization. +- Decoupled from GitHub user identities, so they do not consume any licensed seats. +- Never granted a password, so cannot be directly signed in to. + +##### Cons + +- Additional setup is needed to create the GitHub App. +- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code. + +##### Setup + +1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private. +1. Determine the permissions your GitHub App requires, such as read-only access to repository contents. +1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app). +1. Note your GitHub App `id`. +1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key). +1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization. +1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app). +1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation). +1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client. + ### Machine users If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). diff --git a/translations/ru-RU/content/developers/overview/secret-scanning.md b/translations/ru-RU/content/developers/overview/secret-scanning.md index a6e755ac9c..6df6574480 100644 --- a/translations/ru-RU/content/developers/overview/secret-scanning.md +++ b/translations/ru-RU/content/developers/overview/secret-scanning.md @@ -17,12 +17,6 @@ When a match of your secret format is found in a public repository, a payload is When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -{% note %} - -**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta. - -{% endnote %} - This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} program. ### The {% data variables.product.prodname_secret_scanning %} process diff --git a/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md b/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md index 2b39d2a345..e5cb1bc607 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/github-event-types.md @@ -183,6 +183,20 @@ This event returns an empty `payload` object. {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} +### PullRequestReviewEvent + +{% data reusables.webhooks.pull_request_review_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### Event `payload` object + +| Клавиша | Тип | Description | +| -------------- | -------- | ------------------------------------------------ | +| `действие` | `строка` | The action that was performed. Can be `created`. | +| `pull_request` | `объект` | The pull request the review pertains to. | +| `проверка` | `объект` | The review that was affected. | + ### PullRequestReviewCommentEvent {% data reusables.webhooks.pull_request_review_comment_short_desc %} @@ -200,6 +214,8 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} +#### Event `payload` object + | Клавиша | Тип | Description | | -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `push_id` | `integer` | Unique identifier for the push. | diff --git a/translations/ru-RU/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/ru-RU/content/developers/webhooks-and-events/securing-your-webhooks.md index fe4df63c64..fd8cb2f8ba 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/securing-your-webhooks.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -93,4 +93,4 @@ Your language and server implementations may differ from this example code. Howe * Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 5ac9e8d988..b7629954f0 100644 --- a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -19,7 +19,7 @@ With {% data variables.product.prodname_discussions %}, the community for your p You don't need to close a discussion like you close an issue or a pull request. -If a repository administrator or project maintainer enables discussions for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +If a repository administrator or project maintainer enables discussions for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." For more information about management of discussions for your repository, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." diff --git a/translations/ru-RU/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/ru-RU/content/discussions/guides/best-practices-for-community-conversations-on-github.md index 90a9a0f431..01aab4cefb 100644 --- a/translations/ru-RU/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/ru-RU/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -29,7 +29,7 @@ You can use {% data variables.product.prodname_discussions %} to discuss big pic Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see "[About issues](/articles/about-issues)." Pull requests allow you to comment directly on proposed changes. For more information, see "[About pull requests](/articles/about-pull-requests)" and "[Commenting on a pull request](/articles/commenting-on-a-pull-request)." -{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." ### Following contributing guidelines diff --git a/translations/ru-RU/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/ru-RU/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 8ded0aaa3a..6c12ee38c7 100644 --- a/translations/ru-RU/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/ru-RU/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -21,7 +21,7 @@ The most helpful contributors for the past 30 days are highlighted on the {% dat People with triage permissions for a repository can help moderate a project's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." -For more information about repository permission levels and {% data variables.product.prodname_discussions %}, see "[Repository permissions levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +For more information about repository permission levels and {% data variables.product.prodname_discussions %}, see "[Repository permissions levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." ### Step 3: Change permissions levels for top contributors diff --git a/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index 329e42f94f..7e4f19c8e1 100644 --- a/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -12,7 +12,7 @@ versions: {% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." -Organization owners can choose the permissions required to create a discussion for repositories owned by the organization. For more information, see "[Managing discussion creation for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization)." +Organization owners can choose the permissions required to create a discussion for repositories owned by the organization. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)." As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating a code of conduct or contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md index 72f6d0950d..eb1f42f298 100644 --- a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -16,3 +16,7 @@ Professors, teachers and mentors can use the Campus Advisors online training to **Note:** As an instructor, you can't create {% data variables.product.prodname_dotcom %} accounts for your students. Students must create their own {% data variables.product.prodname_dotcom %} accounts. {% endnote %} + +Teachers can manage a course on software development with {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} allows you to distribute code, provide feedback, and manage coursework using {% data variables.product.product_name %}. For more information, see "[Manage coursework with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)." + +If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" or "[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/)." diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md index 1dad791c70..fb124ca41c 100644 --- a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -9,4 +9,6 @@ versions: free-pro-team: '*' --- -Learn public speaking skills, technical writing, community leadership, and software development skills as a {% data variables.product.prodname_dotcom %} Campus Expert. For more information, see "[Campus Experts](https://education.github.com/students/experts)." +Learn public speaking skills, technical writing, community leadership, and software development skills as a {% data variables.product.prodname_dotcom %} Campus Expert. + +To learn more about training programs for student leaders and teachers, see "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)" and "[Campus Advisors](https://education.github.com/teachers/advisors)." diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md new file mode 100644 index 0000000000..207dcedc5d --- /dev/null +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md @@ -0,0 +1,24 @@ +--- +title: About GitHub Campus Program +intro: '{% data variables.product.prodname_campus_program %} offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} free-of-charge for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community.' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_campus_program %} is a package of premium {% data variables.product.prodname_dotcom %} access for teaching-focused institutions that grant degrees, diplomas, or certificates. {% data variables.product.prodname_campus_program %} includes: + +- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments +- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our Campus Advisor program +- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners +- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} + +Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join. + +For more information, see the [official {% data variables.product.prodname_campus_program %}](https://education.github.com/schools) page. + +If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" or "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)." diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md index 9dda1a2a4f..46f1c88ab4 100644 --- a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -13,7 +13,7 @@ versions: ### Table of Contents {% topic_link_in_list /use-github-at-your-educational-institution %} - {% link_in_list /about-github-education %} + {% link_in_list /about-github-campus-program %} {% link_in_list /about-campus-experts %} {% link_in_list /about-campus-advisors %} {% topic_link_in_list /use-github-for-your-schoolwork %} diff --git a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index 2dfd74a141..dc45d944de 100644 --- a/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/ru-RU/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -59,11 +59,11 @@ If you have more than one personal user account, you must merge your accounts. T ### Ineligible student status You're ineligible for a {% data variables.product.prodname_student_pack %} if: -- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. +- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study. - You're pursuing a degree which will be terminated in the current academic session. - You're under 13 years old. -Your instructor may still apply for a {% data variables.product.prodname_education %} discount for classroom use. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_dotcom %} Campus Program](https://education.github.com/schools). +Your instructor may still apply for a {% data variables.product.prodname_education %} discount for classroom use. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools). ### Дополнительная литература diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 902630834b..b6eda7f6ea 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -17,7 +17,7 @@ When a student accepts a group assignment, the student can create a new team or {% 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 %}. For more information, see "[About teams](/github/setting-up-and-managing-organizations-and-teams/about-teams)." +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 %}. For more information, see "[About teams](/organizations/organizing-members-into-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)." 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 6e98f01a9c..4078150f7e 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 @@ -20,7 +20,7 @@ redirect_from: After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}. -Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)" and "[Inviting users to join your organization](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)." +Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom. @@ -34,7 +34,7 @@ When you first share the URL for an assignment with a student, the student must ### Требования -You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." +You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." diff --git a/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index 1d77d71a7e..36eef2ec21 100644 --- a/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -26,7 +26,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} in y {% note %} -**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -47,7 +47,7 @@ You can disable all workflows for a repository or set a policy that configures w {% note %} -**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." +**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." {% endif %} diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index cfdbd3bb6d..708fb360ee 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -11,7 +11,11 @@ topics: - repositories --- -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)." +### About auto-merge + +If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." + +### Managing auto-merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 3702198186..4bb0c534c2 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 @@ -47,6 +47,9 @@ You can choose whether 6. Type a title and description for your release. ![Releases description](/assets/images/help/releases/releases_description.png) 7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) 8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) +{%- if currentVersion == "free-pro-team@latest" %} +1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} 9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**. ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png) You can also automatically create a release from the command line or in a script. For more information, see "[Releases](/rest/reference/repos/#create-a-release)." 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 185c007706..82c1c527d1 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 @@ -106,4 +106,4 @@ Organization owners and repository administrators can only grant access to view ### Дополнительная литература - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)" -- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" +- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md index 710e7a15b0..e8dd0629a8 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -16,7 +16,7 @@ For each repository that you administer on {% data variables.product.prodname_do This overview can help you audit access to your repository, onboard or off-board contractors or employees, and effectively respond to security incidents. -For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." ![Access management overview](/assets/images/help/repository/manage-access-overview.png) @@ -53,4 +53,4 @@ For more information about repository permission levels, see "[Permission levels ### Дополнительная литература - "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" -- "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" +- "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)" diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index dcf9f0e79e..91144e68d6 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -13,7 +13,7 @@ topics: - repositories --- -An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)." +An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)." {% data reusables.organizations.internal-repos-enterprise %} 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 index 72604410c9..190210ca02 100644 --- 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 @@ -4,7 +4,7 @@ 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: '*' - enterprise-server: '>=3.1' + enterprise-server: '>=3.2' topics: - repositories --- @@ -13,7 +13,9 @@ topics: 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. +When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. + +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. ### Renaming a branch diff --git a/translations/ru-RU/content/github/administering-a-repository/renaming-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/renaming-a-repository.md index 87b247bf99..51d8eb004b 100644 --- a/translations/ru-RU/content/github/administering-a-repository/renaming-a-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/renaming-a-repository.md @@ -18,7 +18,7 @@ When you rename a repository, all existing information, with the exception of pr * Stars * Followers -For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git push` operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line: @@ -30,7 +30,7 @@ For more information, see "[Managing remote repositories](/github/getting-starte {% if currentVersion == "free-pro-team@latest" %} -If you plan to rename a repository that has a {% data variables.product.prodname_pages %} site, we recommend using a custom domain for your site. This ensures that the site's URL isn't impacted by renaming the repository. For more information, see "[About custom domains and {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/about-custom-domains-and-github-pages)." +If you plan to rename a repository that has a {% data variables.product.prodname_pages %} site, we recommend using a custom domain for your site. This ensures that the site's URL isn't impacted by renaming the repository. For more information, see "[About custom domains and {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)." {% endif %} 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 04bfa285ad..e7db2e2c23 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 @@ -16,7 +16,7 @@ topics: ### About repository visibility changes -Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)." +Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." We recommend reviewing the following caveats before you change the visibility of a repository. diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/ru-RU/content/github/authenticating-to-github/about-authentication-to-github.md index 23b8b2c79d..ee5f1547c0 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/ru-RU/content/github/authenticating-to-github/about-authentication-to-github.md @@ -55,3 +55,19 @@ You can access repositories on {% data variables.product.product_name %} from th * You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxys might refuse to allow SSH connections. Using SSH requires you to generate an SSH public/private keypair on your local machine and add the public key to your {% data variables.product.product_name %} account. Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." {% if currentVersion == "free-pro-team@latest" %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### {% data variables.product.company_short %}'s token formats + +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. + +| Token type | Prefix | More information | +|:------------------------------------------------------------------------------- |:------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Personal access token | `ghp_` | "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | + +{% endif %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index 6cbaf7a251..1f50063bee 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/ru-RU/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -51,5 +51,5 @@ After an enterprise or organization owner enables or enforces SAML SSO for an or ### Дополнительная литература -{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} {% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md index fad736bceb..05885816e0 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/ru-RU/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -36,8 +36,15 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} 7. Click **Generate token**. ![Generate token button](/assets/images/help/settings/generate_token.png) -8. Click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again.{% 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 %} +8. Click +{% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again. + {% if currentVersion == "free-pro-team@latest" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) + {% endif %} {% warning %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/ru-RU/content/github/authenticating-to-github/creating-a-strong-password.md index 10c8d20f33..9e8772fc8c 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/creating-a-strong-password.md +++ b/translations/ru-RU/content/github/authenticating-to-github/creating-a-strong-password.md @@ -20,7 +20,7 @@ To keep your account secure, we recommend you follow these best practices: - Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters. - Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your {% data variables.product.product_name %} account. - Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)." -- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/articles/collaborating-with-groups-in-organizations/)." +- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)." {% data reusables.repositories.blocked-passwords %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md b/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md index cce6bb4038..0f172a9230 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md +++ b/translations/ru-RU/content/github/authenticating-to-github/error-permission-denied-publickey.md @@ -7,6 +7,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - ssh --- ### Should the `sudo` command be used with Git? @@ -38,7 +40,7 @@ All connections, including those for remote URLs, must be made as the "git" user $ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %} > Permission denied (publickey). ``` -If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/articles/changing-a-remote-s-url/). +If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/github/getting-started-with-github/managing-remote-repositories). You should verify your connection by typing: 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 5d82d9952c..efde052510 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 @@ -193,7 +193,7 @@ An overview of some of the most common actions that are recorded as events in th | `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | | `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | | `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)") | | `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | | `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index 5fe4884dde..7d665c73e2 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -18,7 +18,7 @@ You can create and participate in issues, pull requests, and team discussions, d Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see "[About issues](/articles/about-issues)." Pull requests allow you to comment directly on proposed changes. For more information, see "[About pull requests](/articles/about-pull-requests)" and "[Commenting on a pull request](/articles/commenting-on-a-pull-request)." -{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." ### Reacting to ideas in comments 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 8a277f6d83..92db9072ca 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 @@ -15,7 +15,7 @@ topics: After a pull request is opened, anyone with *read* access can review and comment on the changes it proposes. You can also suggest specific changes to lines of code, which the author can apply directly from the pull request. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)." -Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review)." {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. 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 %} +Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review)." {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} Reviews allow for discussion of proposed changes and help ensure that the changes meet the repository's contributing guidelines and other quality standards. You can define which individuals or teams own certain types or areas of code in a CODEOWNERS file. When a pull request modifies code that has a defined owner, that individual or team will automatically be requested as a reviewer. For more information, see "[About code owners](/articles/about-code-owners/)." diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index be5d8366dc..063b7b8993 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -14,7 +14,9 @@ topics: If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks. -Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)." +Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} + +After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %} You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback). diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index 7bacb04a39..de4098c42a 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -13,7 +13,7 @@ topics: Owners and collaborators on a repository owned by a user account can assign pull request reviews. Organization members with triage permissions to a repository can assign a pull request review. -Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. 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 %} +Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %} {% note %} diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index be8cc1d914..1c742feddf 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -79,5 +79,5 @@ If you change the visibility of an internal repository and then delete the repos - "[Setting repository visibility](/articles/setting-repository-visibility)" - "[About forks](/articles/about-forks)" - "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" -- "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" - "{% if currentVersion == "free-pro-team@latest" %}[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}" diff --git a/translations/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 f24d24957b..b9cacf2463 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 @@ -23,7 +23,7 @@ Code owners are automatically requested for review when someone opens a pull req 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 %} +{% 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](/organizations/organizing-members-into-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.22" %} If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md index e62878b22f..edc0500dfe 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -19,7 +19,7 @@ topics: {% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch. -Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist#troubleshooting) for help. +Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help. ### Markup languages diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index 1a74ecee14..dabd0a63d6 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -22,7 +22,7 @@ Private repositories are only accessible to you, people you explicitly share acc Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." {% endif %} -Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md index 69243b563c..d0990e60e8 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -23,13 +23,13 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of ``` 3. Mirror-push to the new repository. ```shell - $ cd old-repository.git + $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` 4. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects @@ -41,7 +41,7 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of ``` 3. Navigate to the repository you just cloned. ```shell - $ cd old-repository.git + $ cd old-repository ``` 4. Pull in the repository's {% data variables.large_files.product_name_long %} objects. ```shell @@ -58,7 +58,7 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of 7. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### Mirroring a repository in another location @@ -72,7 +72,7 @@ If you want to mirror a repository in another location, including getting update ``` 3. Set the push location to your mirror. ```shell - $ cd repository-to-mirror.git + $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index 9a4250ad60..c7a0d6029d 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > provide shell access. ``` -If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "About OAuth App access restrictions." +If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "About OAuth App access restrictions." For more information, see [Adding a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account). diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md b/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md index fef7d78dad..fb1cb2e462 100644 --- a/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio.md @@ -1,6 +1,6 @@ --- title: Using Codespaces in Visual Studio -intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vs %} by connecting with your account on {% data variables.product.product_name %}.' +intro: 'This preview has concluded and will no longer be accepting signups.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,50 +10,10 @@ topics: {% note %} -**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. During the beta period, {% data variables.product.prodname_dotcom %} does not make any guarantees about the availability of {% data variables.product.prodname_codespaces %}. [Sign up for the limited public beta](https://github.com/features/codespaces/signup-vs). For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." +**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. During the beta period, {% data variables.product.prodname_dotcom %} does not make any guarantees about the availability of {% data variables.product.prodname_codespaces %}. {% endnote %} ### About codespaces in {% data variables.product.prodname_vs %} -You can create a codespace in {% data variables.product.prodname_vs %} to develop applications in a Windows environment. When you use a codespace in {% data variables.product.prodname_vs %}, you can browse source code, build solutions, and commit changes to your repository. - -You must create a codespace in {% data variables.product.prodname_vs %} to use it with the application. Codespaces created outside of {% data variables.product.prodname_vs %} can not currently be used with {% data variables.product.prodname_vs %}. - -### Требования - -Before you configure a codespace in {% data variables.product.prodname_vs %}, you must download the latest version of [{% data variables.product.prodname_vs %} Preview](https://aka.ms/vspreview). - -#### Enabling the connection between {% data variables.product.prodname_vs %} and {% data variables.product.prodname_github_codespaces %} - -Connecting to {% data variables.product.prodname_github_codespaces %} with the {% data variables.product.prodname_vs %} Preview is not enabled by default, so you will first need to enable the Preview Features option. - -1. In {% data variables.product.prodname_vs %} Preview, use the Tools drop-down menu, then click **Options**. -2. Under **Environment**, select **Preview Features** and check the **Connect to {% data variables.product.prodname_github_codespaces %}** preview feature. ![Check the Connect to {% data variables.product.prodname_github_codespaces %} preview feature](/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png) -3. You will need to restart {% data variables.product.prodname_vs %} for the feature to be available. - -### Creating a codespace in {% data variables.product.prodname_vs %} - -1. When you launch {% data variables.product.prodname_vs %}, the Start Window will show a **Connect to a codespace** button under "Get started". ![Visual Studio Start window with Connect to a codespace](/assets/images/help/codespaces/visual-studio-start-window.png) -2. Click **Connect to a codespace**. -3. Click **Sign in to {% data variables.product.prodname_dotcom %}** and follow the prompts, or click **Create one!** to create a new {% data variables.product.prodname_dotcom %} account and sign into the account. ![Visual Studio sign in to {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/visual-studio-sign-in-to-github.png) -4. Under "Codespace details", type the repository's URL you want {% data variables.product.prodname_github_codespaces %} to clone into your codespace. -5. Optionally, use the Instance type and Suspend after drop-down menus to configure more codespace details. ![Visual Studio codespace details](/assets/images/help/codespaces/visual-studio-codespace-details.png) -6. Click **Create and Connect**. {% data variables.product.prodname_github_codespaces %} will begin preparing the codespace and open {% data variables.product.prodname_vs %} after the codespace is ready. The codespace name will appear in the remote indicator in the menu. ![Visual Studio connected to eShopOnWeb repository codespace](/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png) - -### Opening a codespace in {% data variables.product.prodname_vs %} - -1. Use the File drop-down menu, and click **Connect to a Codespace**. ![Visual Studio File Connect to a codespace menu item](/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png) -2. Under "{% data variables.product.prodname_github_codespaces %}", click the codespace you want to connect to, then click **Connect**. ![Visual Studio displaying available codespaces and details](/assets/images/help/codespaces/visual-studio-connect-codespace.png) - -### Configuring a codespace for {% data variables.product.prodname_vs %} - -A codespace, created with {% data variables.product.prodname_vs %}, can be customized through a new tool called devinit, a command line tool included with {% data variables.product.prodname_vs %}. - -#### devinit - -[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) lets you install additional frameworks and tools into your Windows development codespaces, modify environment variables, and more. - -devinit supports a configuration file called [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). You can add this file to your project if you want to create a customized and repeatable development environment. When you use devinit with a [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) file, your codespaces will be automatically configured on creation. - -For more information about Windows codespace configuration and devinit, see [Customize a codespace](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces) in the {% data variables.product.prodname_vs %} documentation. For more information about devinit, see [Getting started with devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit). +The private preview for GitHub Codespaces in Visual Studio 2019 has concluded. For more information, see the [Visual Studio 2019 documentation](https://docs.microsoft.com/visualstudio/ide/codespaces/codespaces-overview?view=vs-2019). diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 7b6bd3dc17..96167850d7 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -37,7 +37,7 @@ You need write permission to view a summary of all the alerts for a repository o {% 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. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. ![Summary of alerts](/assets/images/enterprise/3.1/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) @@ -49,7 +49,7 @@ If you have write permission for a repository, you can view fixed alerts by view 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. -![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) +![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} @@ -102,11 +102,11 @@ To dismiss or delete alerts: 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. - ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![Filter alerts by rule](/assets/images/enterprise/3.1/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. - ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) + ![Open an alert from the summary list](/assets/images/enterprise/3.1/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) diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md index 1c7acce7ec..3b02432d96 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -25,7 +25,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -65,7 +65,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re 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. - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endnote %} @@ -91,7 +91,7 @@ There are other situations where there may be no analysis for the latest commit To the right of "Code scanning", click **Set up code scanning**. - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. 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 index 7f4f4bffa3..0312252f8d 100644 --- 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 @@ -38,7 +38,7 @@ 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)." {% endif %} -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)." +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](/organizations/keeping-your-organization-secure/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)." {% endif %} @@ -47,7 +47,7 @@ Once your system is set up, you can enable and disable these features at the org For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. -For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}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)."{% endif %} +For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)."{% endif %} {% endif %} 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 f029413c30..169522276a 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 @@ -92,7 +92,7 @@ In addition to the features available with {% data variables.product.prodname_te - {% data variables.contact.enterprise_support %}. For more information, see "{% data variables.product.prodname_ghe_cloud %} support" and "{% data variables.product.prodname_ghe_cloud %} Addendum." - 50,000 {% data variables.product.prodname_actions %} minutes - 50GB {% data variables.product.prodname_registry %} storage -- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" +- Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime - The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "About enterprise accounts." 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 36f9e7bcf1..6d602192ba 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 @@ -52,6 +52,7 @@ Below is a list of some of the available keyboard shortcuts. | control z or command z | Undo | | control y or command y | Redo | | cmd + shift + p | Toggles between the **Edit file** and **Preview changes** tabs | +| control s or command s | Write a commit message | For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands). diff --git a/translations/ru-RU/content/github/index.md b/translations/ru-RU/content/github/index.md index a5c31865b4..d97b60cc5d 100644 --- a/translations/ru-RU/content/github/index.md +++ b/translations/ru-RU/content/github/index.md @@ -23,7 +23,7 @@ versions: {% link_in_list /managing-subscriptions-and-notifications-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 %} @@ -57,7 +57,6 @@ versions: {% 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 %} diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 88e90af0e5..7ac3506e69 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -42,9 +42,9 @@ For a list of the ecosystems that {% data variables.product.product_name %} can {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." -For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} 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 100266fa1d..abc58480fd 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 @@ -13,7 +13,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. {% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/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" %} 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 3069d19d1b..c5fa5d2693 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 @@ -66,7 +66,7 @@ Email notifications also allow flexibility with the types of notifications you r ### About participating and watching notifications -When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on 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" %} @@ -78,7 +78,7 @@ You can configure notifications for a repository on the repository page, or on y #### About custom notifications {% data reusables.notifications-v2.custom-notifications-beta %} You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository. -{% endif %} For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)." +{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. #### 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. @@ -248,16 +248,15 @@ You can also schedule when {% data variables.product.prodname_mobile %} will sen 1. In the bottom menu, tap **Profile**. 2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}. -3. To update your notification settings, tap **Notifications** and then use the toggles to enable or disable your preferred types of push notifications. -4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Receive Notifications**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications. +3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications. +4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications. ### Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %} You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% if currentVersion == "free-pro-team@latest" %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository. -1. On {% data variables.product.prodname_mobile %}, navigate to main page of the repository. +1. On {% data variables.product.prodname_mobile %}, navigate to the main page of the repository. 2. Tap **Watch**. ![The watch button on {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-button.png) 3. To choose what activities you receive notifications for, tap your preferred watch settings. ![Watch settings dropdown menu in {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-settings.png) -{% data reusables.notifications-v2.custom-notifications-beta %} {% endif %} diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index 207c959f06..1022d71aaf 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -38,7 +38,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. +**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." {% endtip %} {% endif %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md index 4dc71ecc77..d117c30e18 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship.md @@ -19,14 +19,14 @@ When you downgrade or cancel a sponsorship, the change will become effective on {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Canceling a sponsorship {% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} +{% data reusables.user_settings.billing_plans %} {% data reusables.sponsors.billing-switcher %} -{% data reusables.user_settings.subscriptions-tab %} 3. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored open source contributor, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your sponsored amount, then click **Cancel sponsorship**. ![Cancel sponsorship button](/assets/images/help/billing/edit-sponsor-billing.png) 4. Review the information about canceling your sponsorship, then click **OK**. ![Cancellation confirmation box](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md index e6464bebef..2950db4002 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md @@ -14,6 +14,8 @@ topics: {% data variables.product.product_name %} can't issue a refund if you pay for an account before applying a coupon. We also can't transfer a redeemed coupon or give you a new coupon if you apply it to the wrong account. Confirm that you're applying the coupon to the correct account before you redeem a coupon. +{% data reusables.dotcom_billing.coupon-expires %} + You cannot apply coupons to paid plans for {% data variables.product.prodname_marketplace %} apps. ### Redeeming a coupon for your personal account diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md index ef7667f1c5..fc07401650 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md @@ -15,6 +15,8 @@ topics: If you're paying for your {% data variables.product.product_name %} subscription with a coupon, and you aren't using your payment method for any [other paid features or products](/articles/about-billing-on-github) on {% data variables.product.product_name %}, you can remove your credit card or PayPal information. +{% data reusables.dotcom_billing.coupon-expires %} + {% tip %} **Tip:** If you [downgrade your account to a free product](/articles/downgrading-your-github-subscription) and you don't have subscriptions for any other paid features or products, we'll automatically remove your payment information. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md index 5cb6ca4ffc..cd0aabf52a 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship.md @@ -19,5 +19,6 @@ When you upgrade your sponsorship tier, the change will become effective immedia {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md index 186eb3b759..37d89f2bce 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription.md @@ -59,7 +59,7 @@ You can upgrade your organization from {% data variables.product.prodname_free_t #### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %} -If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/articles/managing-saml-single-sign-on-for-your-organization)." +If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)." If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/articles/about-enterprise-accounts)." diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md index 0aa338416e..2a55ae7412 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md @@ -20,5 +20,5 @@ You can check how many seats your license includes and how many of them are curr The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red. You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %} enterprise license](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)." ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise.png) 5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization. ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 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)." +6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." 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 index 12a62fc4a7..524218c512 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### 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.dotcom-saml-explanation %} For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} 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 38ef295f55..ae7d0f8db3 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 @@ -49,7 +49,7 @@ Enterprise owners can restrict access to assets owned by organizations in an ent {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)." +You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." #### Adding an allowed IP address diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md index e0294ec0eb..63c8dbe2e9 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md @@ -15,7 +15,7 @@ topics: ### Enforcing a policy for team discussions -Across all organizations owned by your enterprise account, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." +Across all organizations owned by your enterprise account, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 0de872d33a..b0c58913ac 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 @@ -39,7 +39,7 @@ Organization owners can invite new members to an organization by email address. While not required, we recommend that organization owners send an invitation to the same email address used for the {% data variables.product.prodname_vs %} subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_name %} matches the subscriber's UPN, you can ensure that another member of the organization does not claim the subscriber's license. -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)." +For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/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 index 55681d08c2..921e5405ac 100644 --- 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 @@ -19,7 +19,7 @@ If you use Azure AD as your IdP, you can enable team synchronization for your en {% 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 can also configure and manage team synchronization for an individual organization. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." ### Требования diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md index b5ee192d8e..1320ba583f 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -11,7 +11,7 @@ topics: ### About email restrictions for your enterprise account -When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md index 6f71d80202..7692bba7ca 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain.md @@ -14,7 +14,7 @@ topics: ### 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. For more information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." +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. For more information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %} @@ -22,7 +22,7 @@ Organization owners will be able to verify the identity of organization members After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account to approved domains](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)." -Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)." +Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, 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 about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)." ### Verifying your enterprise account's domain 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 4381eba0b0..beb04191c5 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 @@ -53,4 +53,4 @@ When you enable SAML single sign-on for your enterprise account, each enterprise ### Дополнительная литература -- "[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 managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md index a4eca8f16d..e0032e4f17 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/about-your-organizations-profile.md @@ -14,7 +14,7 @@ topics: You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories to the top of the page. -{% 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 %}. For more information, see "[Verifying your organization's domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." +{% 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 %}. For more information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)." ![Sample verified organization profile page](/assets/images/help/profile/org_profile_verified.png) {% else %} @@ -23,4 +23,4 @@ You can optionally choose to add a description, location, website, and email add ### Дополнительная литература -- "[About organizations](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" +- "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" 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 4930400bc3..dee911246b 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 @@ -25,7 +25,7 @@ Commits will appear on your contributions graph if they meet **all** of the foll - In the repository's default branch - In the `gh-pages` branch (for repositories with project sites) -For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." In addition, **at least one** of the following must be true: - You are a collaborator on the repository or are a member of the organization that owns the repository. @@ -66,7 +66,7 @@ Generic email addresses--such as `jane@computer.local`--cannot be added to {% da #### Commit was not made in the default or `gh-pages` branch -Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)." +Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following: - [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md index 388b1277b0..a590dd84b4 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization.md @@ -52,7 +52,7 @@ You can also convert your personal user account directly into an organization. C {% tip %} -**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." +**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)." {% endtip %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md index 6f160235aa..247abe10d3 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository.md @@ -56,4 +56,4 @@ Repositories owned by an organization can grant more granular access. For more i - "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)" - "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)" - "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)" -- "[Organizing members into teams](/articles/organizing-members-into-teams)" +- "[Organizing members into teams](/organizations/organizing-members-into-teams)" diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md index 79e624e48e..5d5d524769 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories.md @@ -25,4 +25,4 @@ When you create a new repository on {% data variables.product.product_location % ### Дополнительная литература -- "[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)" +- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md index 809617b559..eb4f475a16 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -13,7 +13,7 @@ Scheduled reminders are used to make sure that users focus on the most important For certain events, you can also enable real-time alerts for scheduled reminders. Real-time alerts get sent to your Slack channel as soon as an important event, such as when you are assigned a review, takes place. -You can set scheduled reminders for personal or team-level review requests for pull requests in organizations you are a member of. Before you can create a scheduled reminder for yourself, an organization owner must authorize your Slack workspace. For more information, see "[Managing scheduled reminders for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)." +You can set scheduled reminders for personal or team-level review requests for pull requests in organizations you are a member of. Before you can create a scheduled reminder for yourself, an organization owner must authorize your Slack workspace. For more information, see "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)." {% data reusables.reminders.scheduled-reminders-limitations %} @@ -50,5 +50,5 @@ You can set scheduled reminders for personal or team-level review requests for p ### Дополнительная литература -- "[Managing scheduled reminders for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" -- "[Managing scheduled reminders for your team](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" +- "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- "[Managing scheduled reminders for your team](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md b/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md index 4a6b1e4c07..edbbfbd905 100644 --- a/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md +++ b/translations/ru-RU/content/github/site-policy/github-corporate-terms-of-service.md @@ -125,7 +125,7 @@ Customer’s use of the Products must not violate any applicable laws, including Customer’s use of the Service must comply with [GitHub's Acceptable Use Policies](/articles/github-acceptable-use-policies) and [GitHub’s Community Guidelines](/articles/github-community-guidelines). Customer must not use the Service in any jurisdiction for unlawful, obscene, offensive or fraudulent Content or activity, such as advocating or causing harm, interfering with or violating the integrity or security of a network or system, evading filters, sending unsolicited, abusive, or deceptive messages, viruses or harmful code, or violating third party rights. #### 3. Конфиденциальность -The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Addendum](/github/site-policy/github-data-protection-addendum) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the GitHub Privacy Statement, particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. +The [GitHub Privacy Statement](/articles/github-privacy-statement) and the [GitHub Data Protection Agreement](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) provide detailed notice of GitHub's privacy and data use practices as well as GitHub's processing and security obligations with respect to Customer Personal Data. Any person, entity, or service collecting data from the Service must comply with the GitHub Privacy Statement, particularly in regards to the collection of Users' Personal Information (as defined in the GitHub Privacy Statement). If Customer collects any User Personal Information from GitHub, Customer will only use it for the purpose for which the External User has authorized it. Customer will reasonably secure any such Personal Information, and Customer will respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or External Users. ### D. Content Responsibility; Ownership; License Rights diff --git a/translations/ru-RU/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/ru-RU/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md new file mode 100644 index 0000000000..7b2d47002d --- /dev/null +++ b/translations/ru-RU/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md @@ -0,0 +1,348 @@ +--- +title: GitHub Data Protection Agreement (Non-Enterprise Customers) +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum +versions: + free-pro-team: '*' +--- + +_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._ + +## INTRODUCTION + +The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products. + +In the event of any conflict or inconsistency between the DPA and any other terms in Customer’s agreements with GitHub, the DPA shall prevail. The provisions of the DPA supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Customer Personal Data as defined herein. For clarity, consistent with Clause 10 of the Standard Contractual Clauses in Attachment 1, the Standard Contractual Clauses prevail over any other terms in the DPA. + + +## GITHUB DATA PROTECTION + +### 1. Определения. + +1.1 The "**Applicable Data Protection Laws**" means certain laws, regulations, regulatory frameworks, or other legislations relating to the processing and use of Customer Personal Data, as applicable to Customer's use of GitHub and the GitHub Service, including: + + a. The EU General Data Protection Regulation 2016/679 (**"GDPR"**), along with any implementing or corresponding equivalent national laws or regulations, once in effect and applicable; and + + b. The California Consumer Privacy Act of 2018, Cal. Civ. Code §§1798.100 et seq. (**"CCPA"**); and + + c. The UK Data Protection Act 2018 and implementation of GDPR contained therein. + +1.2 "**Controller**," "**Data Subject**," "**Member State**," "**Personal Data**," "**Personal Data Breach**," "**Processing**," "**Processor**," and "**Supervisory Authority**" have the meanings given to them in the Applicable Data Protection Laws. In the event of a conflict, the meanings given in the GDPR will supersede. + +1.3 "**Customer Personal Data**" means any Personal Data for which Customer is a Controller, whether supplied by Customer for processing by GitHub or generated by GitHub in the course of performing its obligations under the Agreement. It includes data such as billing information, IP addresses, corporate email addresses, and any other Personal Data for which Customer is a Controller. + +1.4 "**Customer Repository Data**" means any data or information that is uploaded or created by Customer into any of its Private Repositories. + +1.5 A "**Data Breach**" means a Personal Data Breach or any other confirmed or reasonably suspected breach of Customer's Protected Data. + +1.6 "**End User**" means an individual Data Subject who controls a GitHub account and has agreed to the GitHub Terms of Service, and whose Personal Data is being transferred, stored, or processed by GitHub. For example, each Customer employee or contractor who has a GitHub account is also a GitHub End User. + +1.7 "**Permitted Purposes**" for data processing are those limited and specific purposes of providing the Service as set forth in the Agreement, the GitHub Privacy Statement, and this Exhibit A, or the purposes for which a Data Subject has authorized the use of Customer Personal Data. + +1.8 "**Protected Data**" includes any Customer Personal Data and any Customer Repository Data processed by GitHub on behalf of Customer under the Agreement. + +1.9 "**Sensitive Data**" means any Customer Personal Data revealing racial or ethnic origin; political opinions, religious or philosophical beliefs or trade union membership; processing of genetic data or biometric data for the purposes of uniquely identifying a natural person; data concerning health, a natural person's sex life or sexual orientation; and data relating to offences, criminal convictions, or security measures. + +### 2. Status and Compliance. + +#### 2.1 Data Processing. +GitHub acts as a Processor in regard to any Customer Personal Data it receives in connection with the Agreement, and GitHub will process Customer Personal Data only for Permitted Purposes in accordance with Customer's instructions as represented by the Agreement and other written communications. In the event that GitHub is unable to comply with Customer's instructions, such as due to conflicts with the Applicable Data Protection Laws, or where processing is required by the Applicable Data Protection Laws or other legal requirements, GitHub will notify Customer to the extent permissible. GitHub processes all Customer Personal Data in the United States or in the European Union; however, GitHub's subprocessors may process data outside of the United States or the European Union. Additionally, GitHub acts as a Processor for any Customer Repository Data. + +#### 2.2 Data Controllers. +GitHub receives Customer Personal Data both from Customer and directly from Data Subjects who create End User accounts. Customer is a Controller only for the Customer Personal Data it transfers directly to GitHub. + +#### 2.3 GitHub Compliance; Data Transfers. +GitHub will comply with Applicable Data Protection Laws in relation to the processing of Customer Personal Data. + +All transfers of Customer Personal Data out of the European Union, European Economic Area, United Kingdom, and Switzerland to provide the Service shall be governed by the Standard Contractual Clauses in Attachment 1 (Standard Contractual Clauses). GitHub will abide by the requirements of European Economic Area and Swiss data protection law regarding the collection, use, transfer, retention, and other processing of Customer Personal Data from the European Economic Area, United Kingdom, and Switzerland. All transfers of Customer Personal Data to a third country or an international organization will be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +In addition, GitHub is certified to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on them as a legal basis for transfers of Personal Data. GitHub agrees to notify Customer if it makes a determination that it can no longer meet its obligation to provide the same level of protection as is required by the Privacy Shield principles. + + +### 3. Data Protection. + +#### 3.1 Purpose Limitation. +GitHub will process and communicate the Protected Data only for Permitted Purposes, unless the Parties agree in writing to an expanded purpose. + +#### 3.2 Data Quality and Proportionality. +GitHub will keep the Customer Personal Data accurate and up to date, or enable Customer to do so. GitHub will take commercially reasonable steps to ensure that any Protected Data it collects on Customer's behalf is adequate, relevant, and not excessive in relation to the purposes for which it is transferred and processed. In no event will GitHub intentionally collect Sensitive Data on Customer's behalf. Customer agrees that the GitHub Service is not intended for the storage of Sensitive Data; if Customer chooses to upload Sensitive Data to the Service, Customer must comply with Article 9 of the GDPR, or equivalent provisions in the Applicable Data Protection Laws. + +#### 3.3 Data Retention and Deletion. +Upon Customer's reasonable request, unless prohibited by law, GitHub will return, destroy, or deidentify all Customer Personal Data and related data at all locations where it is stored after it is no longer needed for the Permitted Purposes within thirty days of request. GitHub may retain Customer Personal Data and related data to the extent required by the Applicable Data Protection Laws, and only to the extent and for such period as required by the Applicable Data Protection Laws, provided that GitHub will ensure that Customer Personal Data is processed only as necessary for the purpose specified in the Applicable Data Protection Laws and no other purpose, and Customer Personal Data remains protected by the Applicable Data Protection Laws. + +#### 3.4 Data Processing. +GitHub provides the following information, required by Article 28(3) of the GDPR, regarding its processing of Customer's Protected Data: + +a. *The subject matter and duration of the processing* of Customer Personal Data are set out in the Agreement and this Addendum. + +b. *The nature and purpose of the processing* of Customer Personal Data is described in Section 3.1 of this Addendum. + +c. *The types of Customer Personal Data to be processed* are described in the GitHub Privacy Statement, and include Customer Personal Data such as user names, passwords, email addresses, and IP addresses. GitHub also processes information necessary for billing Customer's account, but does not process or store credit card information. Customer may choose to supply GitHub with additional Customer Personal Data, such as in Customer's profile settings or by uploading Customer Personal Data to its GitHub repositories. + +d. *The categories of Data Subject to whom the Customer Personal Data relates* are the Customer itself and its End Users. + +e. *The obligations and rights of Customer* are set out in the Agreement and this Addendum. + +### 4. Security and Audit Obligations. + +#### 4.1 Technical and Organizational Security Measures. +Taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, GitHub will implement appropriate technical and organizational measures to ensure a level of security appropriate to the risks, such as against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure or access, presented by processing the Protected Data. GitHub will regularly monitor compliance with these measures and will continue to take appropriate safeguards throughout the duration of the Agreement. + +#### 4.2 Incident Response and Breach Notification. +GitHub will comply with Applicable Data Protection Laws. + +#### 4.3 GitHub Personnel. +GitHub represents and warrants that it will take reasonable steps to ensure that all GitHub personnel processing Protected Data have agreed to keep the Protected Data confidential and have received adequate training on compliance with this Addendum and the Applicable Data Protection Laws. + +#### 4.4 Records. +GitHub will maintain complete, accurate, and up to date written records of all categories of processing activities carried out on behalf of Customer containing the information required under the Applicable Data Protection Laws. To the extent that assistance does not risk the security of GitHub or the privacy rights of individual Data Subjects, GitHub will make these records available to Customer on request as reasonably required, such as to help Customer demonstrate its compliance under the Applicable Data Protection Laws. + +#### 4.5 Assistance. +GitHub will provide reasonable assistance to Customer with concerns such as data privacy impact assessments, Data Subject rights requests, consultations with Supervisory Authorities, and other similar matters, in each case solely in relation to the processing of Customer Personal Data and taking into account the nature of processing. + +### 5. Use and Disclosure of Protected Data. + +#### 5.1 No Use in Marketing. +GitHub will not use the Protected Data for the purposes of advertising third-party content, and will not sell the Protected Data to any third party except as part of a merger or acquisition. + +#### 5.2 GitHub Privacy Statement. +The GitHub Privacy Statement, publicly available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), provides detailed notice of GitHub's privacy and data use practices, including its use of cookies, its dispute resolution process, and further details about GitHub's GDPR compliance. + +### 6. Subprocessing and Onward Transfer. + +#### 6.1 Protection of Data. +GitHub is liable for onward transfers of Protected Data to its subprocessors, such as its third-party payment processor. In the event that GitHub does transfer the Protected Data to a third-party subprocessor, or GitHub installs, uses, or enables a third party or third-party services to process the Protected Data on GitHub's behalf, GitHub will ensure that the third-party subprocessor is bound by written agreement that requires them to provide at least the same level of confidentiality, security, and privacy protection as is required of GitHub by this DPA and the Applicable Data Protection Laws. + +#### 6.2 Acceptance of GitHub Subprocessors. +Customer authorizes GitHub to appoint (and permit each subprocessor appointed in accordance with this Section 6 to appoint) subprocessors in accordance with Section 6 and any other restrictions in the Agreement. GitHub may continue to use those subprocessors currently engaged as of the Effective Date of this Addendum. + +#### 6.3 General Consent for Onward Subprocessing. +Customer provides a general consent for GitHub to engage onward subprocessors, conditional on GitHub's compliance with the following requirements: + +a. Any onward subprocessor must agree in writing to only process data in a country that the European Commission has declared to have an "adequate" level of protection; or to only process data on terms equivalent to the Standard Contractual Clauses, or pursuant to a Binding Corporate Rules approval granted by competent European data protection authorities, or pursuant to compliant and valid EU-US Privacy Shield and Swiss-U.S. Privacy Shield certifications; and + +b. GitHub will restrict the onward subprocessor's access to Customer Personal Data only to what is strictly necessary to perform its services, and GitHub will prohibit the subprocessor from processing the Customer Personal Data for any other purpose. + +#### 6.4 Disclosure of Subprocessor Agreements. +GitHub maintains a list of onward subprocessors it has engaged to process Customer Personal Data at [https://docs.github.com/articles/github-subprocessors-and-cookies](/articles/github-subprocessors-and-cookies), including the categories of Customer Personal Data processed, a description of the type of processing the subprocessor performs, and the location of its processing. GitHub will, upon Customer's written request, provide Customer with this list of subprocessors and the terms under which they process the Customer Personal Data. Pursuant to subprocessor confidentiality restrictions, GitHub may remove any confidential or commercially sensitive information before providing the list and the terms to Customer. In the event that GitHub cannot disclose confidential or sensitive information to Customer, the Parties agree that GitHub will provide all information it reasonably can in connection with its subprocessing agreements. + +#### 6.5 Objection to Subprocessors. +GitHub will provide thirty (30) days' prior written notice of the addition or removal of any subprocessor, including the categories listed in Section 6.4, by announcing changes on its site. If Customer has a reasonable objection to GitHub's engagement of a new subprocessor, Customer must notify GitHub promptly in writing. Where possible, GitHub will use commercially reasonable efforts to provide an alternative solution to the affected Service to avoid processing of data by the objectionable subprocessor. In the event that GitHub is unable to provide an alternative solution and the Parties cannot resolve the conflict within ninety days, Customer may terminate the Agreement. + +### 7. Termination. + +#### 7.1 Suspension. +In the event that GitHub is in breach of its obligations to maintain an adequate level of security or privacy protection, Customer may temporarily suspend the transfer of all Customer Personal Data or prohibit collection and processing of Customer Personal Data on Customer's behalf until the breach is repaired or the Agreement is terminated. + +#### 7.2 Termination with Cause. +In addition to any termination rights Customer has under the Agreement, Customer may terminate the Agreement without prejudice to any other claims at law or in equity in the event that: + +a. GitHub notifies Customer that it can no longer meet its privacy obligations; + +b. the transfer, collection, or processing of all Customer Personal Data has been temporarily suspended for longer than one month pursuant to Section 7.1; + +c. GitHub is in substantial or persistent breach of any warranties or representations under this Addendum; + +d. GitHub is no longer carrying on business, is dissolved, enters receivership, or a winding up order is made on behalf of GitHub; or + +e. Customer objects to a subprocessor pursuant to Section 6.5, and GitHub has not been able to provide an alternative solution within ninety days. + +#### 7.3 Breach. +Failure to comply with the material provisions of this Addendum is considered a material breach under the Agreement. + +#### 7.4 Failure to perform. +In the event that changes in law or regulation render performance of this Addendum impossible or commercially unreasonable, the Parties may renegotiate the Addendum in good faith. If renegotiation would not cure the impossibility, or if the Parties cannot reach an agreement, the Parties may terminate the Agreement after thirty days. + +#### 7.5 Notification. +In the event that GitHub determines that it can no longer meet its privacy obligations under this Addendum, GitHub will notify Customer in writing immediately. + +#### 7.6 Modifications. +GitHub may modify this Addendum from time to time as required by the Applicable Data Protection Laws, with thirty days' notice to Customer. + +#### 7.7 Termination Requirements. +Upon Termination, GitHub must: + +a. take reasonable and appropriate steps to stop processing the Customer Personal Data; + +b. within ninety days of termination, delete or deidentify any Customer Personal Data GitHub stores on Customer's behalf pursuant to Section 3.3; and + +c. provide Customer with reasonable assurance that GitHub has complied with its obligations in Section 7.7. + +### 8. Liability for Data Processing. + +#### 8.1 Limitations. +Except as limited by the Applicable Data Protection Laws, any claims brought under this Addendum will be subject to the terms of the Agreement regarding Limitations of Liability. + +## Attachment 1 – The Standard Contractual Clauses (Processors) +Execution of the applicable agreement by Customer includes execution of this Attachment 1 to the GitHub Data Protection Addendum, which is countersigned by GitHub, Inc. + +In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. + +For the purposes of Article 46(2) of the General Data Protection Regulation (EU 2016/679) for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +#### Clause 1: Definitions +(a) 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in the General Data Protection Regulation (EU 2016/679) on the protection of individuals with regard to the processing of personal data and on the free movement of such data; + +(b) 'the data exporter' means the controller who transfers the personal data; + +(c) 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 45(2) of the General Data Protection Regulation (EU 2016/679); + +(d) 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract; + +(e) 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established; + +(f) 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing. + +#### Clause 2: Details of the transfer +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +#### Clause 3: Third-party beneficiary clause +1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary. + +2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. + +3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law. + +#### Clause 4: Obligations of the data exporter +The data exporter agrees and warrants: + +(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State; + +(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses; + +(c) that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below; + +(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation; + +(e) that it will ensure compliance with the security measures; + +(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of the General Data Protection Regulation (EU 2016/679); + +(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension; + +(h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information; + +(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and + +(j) that it will ensure compliance with Clause 4(a) to (i). + +#### Clause 5: Obligations of the data importer +The data importer agrees and warrants: + +(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; + +(c) that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred; + +(d) that it will promptly notify the data exporter about: + +(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation, + +(ii) any accidental or unauthorised access, and + +(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so; + +(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + +(f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; + +(g) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter; + +(h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent; + +(i) that the processing services by the subprocessor will be carried out in accordance with Clause 11; and + +(j) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter. + +#### Clause 6: Liability +1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered. + +2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity. The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities. + +3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +#### Clause 7: Mediation and jurisdiction +1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: + +(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; + +(b) to refer the dispute to the courts in the Member State in which the data exporter is established. + +2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. + +#### Clause 8: Cooperation with supervisory authorities +1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law. + +2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law. + +3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5(b). + +#### Clause 9: Governing Law. +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +#### Clause 10: Variation of the contract +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +#### Clause 11: Subprocessing +1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement. + +2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. + +3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established. + +4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority. + +#### Clause 12: Obligation after the termination of personal data processing services +1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore. + +2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1. + +### Appendix 1 to the Standard Contractual Clauses +Data exporter: Customer is the data exporter. + +**Data importer:** The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects:** Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal information to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following types of data subjects in the Customer Personal Data: + +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Dependents of the above; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users (e.g., customers, clients, patients, visitors, etc.) and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter; +- Stakeholders or individuals who passively interact with data exporter (e.g., because they are the subject of an investigation, research or mentioned in documents or correspondence from or to the data exporter); or +- Professionals with professional privilege (e.g., doctors, lawyers, notaries, religious workers, etc.). + +**Categories of data:** The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Service. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following categories in the Customer Personal Data: +- Authentication data (for example, username, email, password); +- Contact information (for example, email); +- Unique identification numbers and signatures (IP addresses, unique identifier in tracking cookies or similar technology). +- Other unique identifying information. Data subjects may include more data such as real names, avatar images, and other personal information; + +**Special categories of data (if appropriate):** The data importer does not intentionally collect or process any special categories of data in carrying out its services to the data exporter. + +However, because the data importer provides storage services and does not control the categories of data it stores, the data exporter may choose to transfer special categories of data. Consequently, the data exporter is solely responsible for ensuring that it complies with all obligations imposed by applicable laws and regulations relating to the collection and processing of any special categories of data, including obtaining the explicit consent of the data subject prior to processing sensitive personal data. + +**Processing operations:** The personal data transferred will be subject to the following basic processing activities: GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. Subcontractors: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain Customer Personal Data only to deliver the services the data importer has retained them to provide, and they are prohibited from using Customer Personal Data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +**1. Personnel.** Data importer’s personnel will not process Customer Personal Data without authorization. Personnel are obligated to maintain the confidentiality of any Customer Personal Data and this obligation continues even after their engagement ends. + +**2. Data Privacy Contact.** The data privacy officer of the data importer can be reached at the following address: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA + +**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction. + +Signature of GitHub, Inc. appears below. + +Signing the Standard Contractual Clauses, Appendix 1 and Appendix 2 on behalf of the data importer + +![Screen Shot 2020-07-20 at 2 20 29 PM](/assets/images/help/site-policy/docusign-signature.png) + +Lynn Hashimoto, Head of Product & Regulatory Legal + +GitHub, Inc. diff --git a/translations/ru-RU/content/github/site-policy/github-privacy-statement.md b/translations/ru-RU/content/github/site-policy/github-privacy-statement.md index ebae7a470b..2824ecdf61 100644 --- a/translations/ru-RU/content/github/site-policy/github-privacy-statement.md +++ b/translations/ru-RU/content/github/site-policy/github-privacy-statement.md @@ -192,7 +192,7 @@ Similarly, projects on GitHub may include publicly available User Personal Infor #### Organizations -You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s). +You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/organizations/managing-organization-settings/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s). Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization. @@ -321,7 +321,7 @@ In the unlikely event that a dispute arises between you and GitHub regarding our ### Changes to our Privacy Statement -Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For 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. +Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently. ### Лицензия diff --git a/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ru-RU/content/github/site-policy/github-subprocessors-and-cookies.md index 26f2e200ee..0aefdca22c 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 @@ -13,7 +13,7 @@ topics: - legal --- -Effective date: **January 29, 2021** +Effective date: **April 2, 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). @@ -33,7 +33,6 @@ When we share your information with third party subprocessors, such as our vendo | 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 | -| Monday.com | Team collaboration and project management platform | United States | Israel | | Nexmo | SMS notification provider | United States | United States | | Salesforce.com | Customer relations management | United States | United States | | Sentry.io | Application monitoring provider | 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 9d4e8b3ef8..72c9182c43 100644 --- a/translations/ru-RU/content/github/site-policy/index.md +++ b/translations/ru-RU/content/github/site-policy/index.md @@ -16,6 +16,7 @@ topics: {% 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-agreement-non-enterprise-customers %} {% link_in_list /global-privacy-practices %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} {% link_in_list /github-sponsors-additional-terms %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md index df20ace9af..745d4faf50 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -24,7 +24,9 @@ You can set a goal for your sponsorships. For more information, see "[Managing y ### Sponsorship tiers -{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)." +{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)." + +It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. ### Sponsorship payouts @@ -34,5 +36,9 @@ You can set a goal for your sponsorships. For more information, see "[Managing y For more information, see "[Managing your payouts from {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)." +### Sharing feedback about {% data variables.product.prodname_sponsors %} + +{% data reusables.sponsors.feedback %} + ### Дополнительная литература - "[FAQ with the {% data variables.product.prodname_sponsors %} team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" on {% data variables.product.prodname_blog %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md index 68663bdb8c..7614e92f48 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors.md @@ -37,7 +37,7 @@ To be eligible for the {% data variables.product.prodname_matching_fund %}, you ### Sharing feedback about {% data variables.product.prodname_sponsors %} -This is just the beginning — we'd love your input to make sure {% data variables.product.prodname_sponsors %} serves your needs into the future. Please send us your feedback or suggestions by contacting [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). +{% data reusables.sponsors.feedback %} ### Дополнительная литература - "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md index 5b8efe069c..de523d754e 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -15,6 +15,8 @@ Your sponsors can choose whether they receive email updates about your work. For For sponsored developer accounts, the update will come from your user account's primary email address. If you've enabled email address privacy on your user account, the update will come from `noreply@github.com` instead. For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +You can also contact any one-time sponsors who contributed within the last 30 days and enabled updates. + ### Contacting your sponsors {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/index.md index 6623eceb6b..39d60b8feb 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/index.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/index.md @@ -25,7 +25,7 @@ topics: {% 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 /managing-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 %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md index 1d9a6e18e3..9991858a58 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -13,6 +13,12 @@ You can set a funding goal for your sponsored account and share the goal with yo Your goal can set a target for the number of sponsors you want to have or the amount of money you want to earn each month. You can only set one goal up at a time. After you reach a goal, you can set another goal. +{% note %} + +**Note:** Goals are intended to help people track momentum so only monthly sponsors contribute toward your goal. + +{% endnote %} + ### Setting a goal {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md new file mode 100644 index 0000000000..efb3ada4b5 --- /dev/null +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md @@ -0,0 +1,45 @@ +--- +title: Managing your sponsorship tiers +intro: 'You can add a new sponsorship tier, or edit or retire an existing tier.' +redirect_from: + - /articles/changing-your-sponsorship-tiers + - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +topics: + - sponsors +--- + +### About sponsorship tiers + +{% data reusables.sponsors.tier-details %} + +{% data reusables.sponsors.maximum-tier %} + +### Adding a 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 %} + +### Editing or retiring a tier + +{% 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 %} + +### Enabling tiers with custom amounts + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.enable-custom-amounts %} + +### Disabling tiers with custom amounts + +You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired. diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 29578a5ec6..e3bd9271e3 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -48,6 +48,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Submitting your bank information diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index bfa5351d6f..cd2178f54c 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -48,6 +48,7 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### Submitting your bank information diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md index 5367e8b27e..b2d7b7755b 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -1,6 +1,6 @@ --- title: Sponsoring an open source contributor -intro: 'You can make a monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' +intro: 'You can make a one-time or monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' redirect_from: - /articles/sponsoring-a-developer - /articles/sponsoring-an-open-source-contributor @@ -24,11 +24,11 @@ You can sponsor an account on behalf of your user account to invest in projects - 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 pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). +You use your normal payment method to sponsor an account on {% data variables.product.product_name %}. If your organization wants to pay by invoice, [contact us](https://support.github.com/contact/org-sponsors-waitlist). {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% 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 %} +When you sponsor an account the change is effective immediately, unless you are sponsoring on behalf of an organization that pays by invoice. {% data reusables.sponsors.prorated-sponsorship %} Your sponsorship is included in the next scheduled payment to the sponsored account. {% data reusables.sponsors.manage-updates-for-orgs %} @@ -53,6 +53,7 @@ Before you can sponsor an account, you must have a verified email address. For m - To sponsor a developer, under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png) - To sponsor an organization, to the right of the organization's name, click **Sponsor**. ![Sponsor button](/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) +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index bdb91c9c64..09a7a9273c 100644 --- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -89,6 +89,6 @@ The recommended formats explicitly define which versions are used for all direct - "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md index d93abc3e5d..cca941cf13 100644 --- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md +++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository.md @@ -68,7 +68,7 @@ For public repositories, the dependents view shows how the repository is used by Repository administrators can enable or disable the dependency graph for private repositories. -You can also enable or disable the dependency graph 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)." +You can also enable or disable the dependency graph 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](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -109,7 +109,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ### Дополнительная литература - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" +- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Understanding how {% data variables.product.product_name %} uses and protects your data](/github/understanding-how-github-uses-and-protects-your-data)" {% endif %} diff --git a/translations/ru-RU/content/github/working-with-github-support/submitting-a-ticket.md b/translations/ru-RU/content/github/working-with-github-support/submitting-a-ticket.md index dd2c3e3c92..971cb6126f 100644 --- a/translations/ru-RU/content/github/working-with-github-support/submitting-a-ticket.md +++ b/translations/ru-RU/content/github/working-with-github-support/submitting-a-ticket.md @@ -11,7 +11,7 @@ topics: If your account uses a paid {% data variables.product.prodname_dotcom %} product, you can directly contact {% data variables.contact.github_support %}. If your account uses {% data variables.product.prodname_free_user %} for user accounts and organizations, you can contact {% data variables.contact.contact_support %} to report account, security, and abuse issues. For more information, see "[About GitHub Support](/github/working-with-github-support/about-github-support)." -If you use {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %}, or the {% data variables.product.premium_support_plan %} you must submit tickets using the {% data variables.contact.enterprise_portal %}. +If you do not have an enterprise account, please use the {% data variables.contact.enterprise_portal %} to submit tickets. For more information about enterprise accounts, see "[About enterprise accounts](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)." ### Submitting a ticket using the {% data variables.contact.support_portal %} 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 eaa67a64c2..a33cd2a88a 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 @@ -33,7 +33,7 @@ If your site administrator has disabled private mode, you can also use anonymous 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. +- You subscribe to a gist, by clicking **Subscribe** at the top of any gist. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} @@ -55,13 +55,15 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, ### Creating a gist -You can also drag and drop a text file from your desktop directly into the gist editor. +Follow the steps below to create a gist. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% note %} 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. +Alternatively, you can drag and drop a text file from your desktop directly into the editor. + {% endnote %} {% endif %} diff --git a/translations/ru-RU/content/index.md b/translations/ru-RU/content/index.md index 8a144eecbf..11671b8ca4 100644 --- a/translations/ru-RU/content/index.md +++ b/translations/ru-RU/content/index.md @@ -13,5 +13,43 @@ featuredLinks: - /github/getting-started-with-github/managing-remote-repositories - /github/working-with-github-pages versions: '*' +children: + - github + - admin + - organizations + - code-security + - actions + - пакеты + - developers + - rest + - graphql + - insights + - discussions + - сообщества + - pages + - education + - desktop + - early-access +externalProducts: + cli: + id: cli + name: GitHub CLI + href: 'https://cli.github.com/manual' + external: true + atom: + id: atom + name: Atom + href: 'https://atom.io/docs' + external: true + electron: + id: electron + name: Electron + href: 'https://electronjs.org/docs' + external: true + codeql: + id: codeql + name: 'CodeQL' + href: 'https://codeql.github.com/docs' + external: true --- diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md new file mode 100644 index 0000000000..f2dda89e95 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -0,0 +1,33 @@ +--- +title: About organizations +intro: Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. +redirect_from: + - /articles/about-organizations + - /github/setting-up-and-managing-organizations-and-teams/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} +### Organizations and enterprise accounts + +Enterprise accounts allow owners to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations. + +For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account. + +{% data reusables.gated-features.enterprise-accounts %} + +{% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." + +### Terms of service and data protection for organizations + +An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)." + +{% endif %} diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md new file mode 100644 index 0000000000..6b42ae2b62 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -0,0 +1,49 @@ +--- +title: About your organization dashboard +intro: 'As an organization member, you can visit your organization''s dashboard throughout the day to stay updated on recent activity and keep track of issues and pull requests you''re working on or following in the organization.' +redirect_from: + - /articles/about-your-organization-dashboard + - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Accessing your organization dashboard + +{% data reusables.dashboard.access-org-dashboard %} + +### Finding your recent activity + +In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests in your organization. + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### Finding repositories in your organization + +In the left sidebar of your dashboard, you can access your organization's top repositories you're active in. + +![List of repositories you're most active in from your organization](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) + +### Staying updated with activity from the organization + +In the "All activity" section of your news feed, you can view updates from other teams and repositories in your organization. + +The "All activity" section shows all recent activity in the organization, including activity in repositories you're not subscribed to and of people you're not following. 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)." + +For instance, the organization news feed shows updates when someone in the organization: + - Creates a new branch. + - Comments on an issue or pull request. + - Submits a pull request review comment. + - Forks a repository. + - Creates a wiki page. + - Pushes commits.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - Creates a public repository.{% endif %} + +### Further information + +- "[About your personal dashboard](/articles/about-your-personal-dashboard)" diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md new file mode 100644 index 0000000000..728b1ac690 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -0,0 +1,26 @@ +--- +title: About your organization’s news feed +intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization. +redirect_from: + - /articles/news-feed/ + - /articles/about-your-organization-s-news-feed + - /articles/about-your-organizations-news-feed + - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}. + +### Accessing your organization's news feed + +1. {% data variables.product.signin_link %} to your {% data variables.product.product_name %} account. +2. Open your {% data reusables.user_settings.personal_dashboard %}. +3. Click the account context switcher in the upper-left corner of the page. ![Context switcher button in 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 %} +![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md new file mode 100644 index 0000000000..eab2e56131 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -0,0 +1,34 @@ +--- +title: Accessing your organization's settings +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 + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings +intro: 'The organization account settings page provides several ways to manage the account, such as billing, team membership, and repository settings.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**Tip:** Only organization owners and billing managers can see and change the billing information and account settings for an organization. {% 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/ru-RU/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000..610d54a82c --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md @@ -0,0 +1,28 @@ +--- +title: Creating a new organization from scratch +intro: Create an organization to apply fine-grained access permissions to repositories. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /articles/creating-a-new-organization-from-scratch + - /admin/user-management/creating-organizations + - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch +topics: + - organizations + - teams +--- + +When you create a new organization from scratch, it doesn't have any repositories associated with it. For more information on adding repositories to your organization, see "[Creating a new repository](/articles/creating-a-new-repository)" and "[Transferring a repository](/articles/transferring-a-repository)." + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create your organization. {% 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 %} + +### Дополнительная литература + +{% if currentVersion == "free-pro-team@latest" %} +- "[Setting your billing email](/articles/setting-your-billing-email)"{% endif %} +- "[About organizations](/articles/about-organizations)" diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/index.md new file mode 100644 index 0000000000..1cff1af763 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/index.md @@ -0,0 +1,22 @@ +--- +title: Collaborating with groups in organizations +intro: Groups of people can collaborate across many projects at the same time in organization accounts. +redirect_from: + - /articles/creating-a-new-organization-account/ + - /articles/collaborating-with-groups-in-organizations + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000..ec192757c6 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -0,0 +1,50 @@ +--- +title: Viewing insights for your organization +intro: 'Organization insights provide data about your organization''s activity, contributions, and dependencies.' +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/viewing-insights-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +All members of an organization can view organization insights. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." + +You can use organization activity insights to help you better understand how members of your organization are using {% data variables.product.product_name %} to collaborate and work on code. Dependency insights can help you track, report, and act on your organization's open source usage. + +### Viewing organization activity insights + +{% note %} + +**Note:** Organization activity insights are currently in public beta and subject to change. + +{% endnote %} + +With organization activity insights you can view weekly, monthly, and yearly data visualizations of your entire organization or specific repositories, including issue and pull request activity, top languages used, and cumulative information about where your organization members spend their time. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**. ![Click the organization insights tab](/assets/images/help/organizations/org-nav-insights-tab.png) +4. Optionally, in the upper-right corner of the page, choose to view data for the last **1 week**, **1 month**, or **1 year**. ![Choose time period to view org insights](/assets/images/help/organizations/org-insights-time-period.png) +5. Optionally, in the upper-right corner of the page, choose to view data for up to three repositories and click **Apply**. ![Choose repositories to view org insights](/assets/images/help/organizations/org-insights-repos.png) + +### Viewing organization dependency insights +With dependency insights you can view vulnerabilities, licenses, and other important information for the open source projects your organization depends on. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**. ![Insights tab in the main organization navigation bar](/assets/images/help/organizations/org-nav-insights-tab.png) +4. To view dependencies for this organization, click **Dependencies**. ![Dependencies tab under the main organization navigation bar](/assets/images/help/organizations/org-insights-dependencies-tab.png) +5. To view dependency insights for all your {% data variables.product.prodname_ghe_cloud %} organizations, click **My organizations**. ![My organizations button under dependencies tab](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) +6. You can click the results in the **Open security advisories** and **Licenses** graphs to filter by a vulnerability status, a license, or a combination of the two. ![My organizations vulnerabilities and licenses graphs](/assets/images/help/organizations/org-insights-dependencies-graphs.png) +7. You can click on {% octicon "package" aria-label="The package icon" %} **dependents** next to each vulnerability to see which dependents in your organization are using each library. ![My organizations vulnerable dependents](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) + +### Дополнительная литература + - "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" + - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" + - "[Changing the visibility of your organization's dependency insights](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)" + - "[Enforcing a policy on dependency insights in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)" diff --git a/translations/ru-RU/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/ru-RU/content/organizations/collaborating-with-your-team/about-team-discussions.md new file mode 100644 index 0000000000..c19be1bd3a --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -0,0 +1,49 @@ +--- +title: About team discussions +intro: 'Your team can plan together, update one another, or talk about any topic you''d like in discussion posts on your team''s page in an organization.' +redirect_from: + - /articles/about-team-discussions + - /github/building-a-strong-community/about-team-discussions + - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - сообщество +--- + +{% data reusables.organizations.team-discussions-purpose %} + +Any organization member can post on your team's page or participate in a public discussion. {% data reusables.organizations.team-discussions-permissions %} + +![Discussions tab of team page with public and private discussions](/assets/images/help/organizations/team-page-discussions-tab.png) + +You can link to any team discussion to reference it elsewhere. You can pin important posts to your team's page for quick reference later. For more information, see "[Pinning a team discussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion)." + +![Pinned discussions tab of team page with pinned discussion](/assets/images/help/organizations/team-discussions-pinned.png) + +{% data reusables.organizations.team-discussions-default %} Owners can disable team discussions for the entire organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." + +### Notifications for team discussions + +When someone posts or replies to a public discussion on a team's page, members of the team and members of any child teams receive email or web notifications. When someone posts or replies to a private discussion on a team's page, only members of the team receive notifications. + +{% tip %} + +**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." + +{% endtip %} + +By default, if your username is mentioned in a team discussion, you'll receive notifications for the post mentioning your username and any replies to that post. Also, by default, if you reply to a post, you will receive notifications for other replies to the post. + +To turn off notifications for team discussions, you can unsubscribe to a specific discussion post or change your notification settings to unwatch or completely ignore a specific team's discussions. You can subscribe to notifications for a specific discussion post even if you're unwatching that team's discussions. + +For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)." + +### Дополнительная литература + +- "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)" +- "[About teams](/articles/about-teams)" +- "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)" +- "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/ru-RU/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/ru-RU/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md new file mode 100644 index 0000000000..3232ce0845 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md @@ -0,0 +1,30 @@ +--- +title: Creating a team discussion +intro: 'Any organization member can create a _public_ team discussion post. To create a _private_ team discussion post, you must be a member of the team or an organization owner.' +redirect_from: + - /articles/creating-a-team-discussion + - /github/building-a-strong-community/creating-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - сообщество +--- + +{% data reusables.organizations.team-discussions-permissions %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/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. Type a team discussion title and a comment to start a conversation. ![New team discussions comment](/assets/images/help/projects/team-discussions-comment.png) +7. Optionally, select whether you want your post to be private or public using the drop-down menu. ![Team discussions privacy settings menu](/assets/images/help/projects/team-discussions-privacy-menu.png) +8. Click **Comment**. ![Create new team discussions comment button](/assets/images/help/projects/team-discussions-comment-button.png) + +### Дополнительная литература + + - "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" + - "[Pinning a team discussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/ru-RU/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/ru-RU/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000..315e25af14 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,28 @@ +--- +title: Editing or deleting a team discussion +intro: 'Organization members can edit or delete discussions on a team''s page. If you''re an organization member, you can edit or delete the discussion.' +redirect_from: + - /articles/editing-or-deleting-a-team-discussion + - /github/building-a-strong-community/editing-or-deleting-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - сообщество +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. Click {% octicon "kebab-horizontal" aria-label="The edit icon" %} next to the team discussion you want to edit or delete. +7. Click **Edit**. Optionally, click **Delete**. ![Edit team discussion button](/assets/images/help/projects/edit-team-discussions-button.png) +8. Modify the team discussion title and comment as needed, and click **Update comment**. ![Update comment button](/assets/images/help/projects/update-comment-button.png) + +### Дополнительная литература + + - "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Pinning a team discussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/ru-RU/content/organizations/collaborating-with-your-team/index.md b/translations/ru-RU/content/organizations/collaborating-with-your-team/index.md new file mode 100644 index 0000000000..1d9ee74b49 --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-your-team/index.md @@ -0,0 +1,19 @@ +--- +title: Collaborating with your team +intro: 'Within an organization, your team can work together across projects using team discussions.' +redirect_from: + - /articles/collaborating-with-your-team + - /github/building-a-strong-community/collaborating-with-your-team + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - сообщество +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/ru-RU/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md new file mode 100644 index 0000000000..6cbfe0821a --- /dev/null +++ b/translations/ru-RU/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +title: Pinning a team discussion +intro: 'You can pin important discussions to your organization''s team pages for easy reference, and unpin discussions that are no longer relevant.' +redirect_from: + - /articles/pinning-a-team-discussion + - /github/building-a-strong-community/pinning-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - сообщество +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +5. Click {% octicon "pin" aria-label="The pin icon" %} next to the team discussion you want to pin. You can also unpin a discussion by clicking the icon. ![Pin a discussion](/assets/images/help/projects/pin-discussion-button.png) + +### Дополнительная литература + + - "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[Creating a team discussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[Editing or deleting a team discussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000..df69784843 --- /dev/null +++ b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,26 @@ +--- +title: About two-factor authentication and SAML single sign-on +intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-two-factor-authentication-and-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's {% data variables.product.product_name %} account could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)." + +To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)." + +If both 2FA and SAML SSO are enabled, organization members must do the following: +- Use 2FA to log in to their {% data variables.product.product_name %} account +- Use single sign-on to access the organization +- Use an authorized token for API or Git access and use single sign-on to authorize the token + +### Дополнительная литература + +- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md new file mode 100644 index 0000000000..9406a2c559 --- /dev/null +++ b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -0,0 +1,16 @@ +--- +title: Granting access to your organization with SAML single sign-on +intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.' +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000..cecf38ab43 --- /dev/null +++ b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,25 @@ +--- +title: Managing bots and service accounts with SAML single sign-on +intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP). + +{% warning %} + +**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization. + +{% endwarning %} + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000..7c6579e867 --- /dev/null +++ b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,64 @@ +--- +title: Viewing and managing a member's SAML access to your organization +intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.' +permissions: Organization owners can view and manage a member's SAML access to an organization. +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About SAML access to your organization + +When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing {% data variables.product.product_name %} account. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a personal access token or SSH key that the member has authorized for use with your organization. + +You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page. + +### Viewing and revoking a linked identity + +{% 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 %} + +### Viewing and revoking an active SAML session + +{% 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 %} + +### Viewing and revoking authorized credentials + +{% 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 %} + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[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)" diff --git a/translations/ru-RU/content/organizations/index.md b/translations/ru-RU/content/organizations/index.md new file mode 100644 index 0000000000..0cfd817912 --- /dev/null +++ b/translations/ru-RU/content/organizations/index.md @@ -0,0 +1,32 @@ +--- +title: Organizations and teams +shortTitle: Organizations +intro: Collaborate across many projects while managing access to projects and data and customizing settings for your organization. +redirect_from: + - /articles/about-improved-organization-permissions/ + - /categories/setting-up-and-managing-organizations-and-teams + - /github/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_with_intro /collaborating-with-groups-in-organizations %} +{% link_with_intro /managing-membership-in-your-organization %} +{% link_with_intro /managing-peoples-access-to-your-organization-with-roles %} +{% link_with_intro /organizing-members-into-teams %} +{% link_with_intro /collaborating-with-your-team %} +{% link_with_intro /managing-access-to-your-organizations-repositories %} +{% link_with_intro /managing-access-to-your-organizations-project-boards %} +{% link_with_intro /managing-access-to-your-organizations-apps %} +{% link_with_intro /managing-organization-settings %} +{% link_with_intro /restricting-access-to-your-organizations-data %} +{% link_with_intro /keeping-your-organization-secure %} +{% link_with_intro /managing-saml-single-sign-on-for-your-organization %} +{% link_with_intro /granting-access-to-your-organization-with-saml-single-sign-on %} +{% link_with_intro /managing-git-access-to-your-organizations-repositories %} +{% link_with_intro /migrating-to-improved-organization-permissions %} diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/index.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/index.md new file mode 100644 index 0000000000..f3cdc109bd --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/index.md @@ -0,0 +1,24 @@ +--- +title: Keeping your organization secure +intro: 'Organization owners have several features to help them keep their projects and data secure. 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.' +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure + - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000..e89cbfb4a9 --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Managing allowed IP addresses for your organization +intro: You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect. +product: '{% data reusables.gated-features.allowed-ip-addresses %}' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage allowed IP addresses for an organization. + +### About allowed IP addresses + +You can restrict access to organization assets by configuring an allow list for specific IP addresses. {% 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 %} + +You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see {% if currentVersion == "github-ae@latest" %}"[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." {% else %}"[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)."{% endif %} + +### Adding an allowed IP address + +{% 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 %} + +### Enabling allowed IP addresses + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +3. Under "IP allow list", select **Enable IP allow list**. ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) +4. Click **Save**. + +### Editing an allowed IP address + +{% 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. Click **Update**. + +### Deleting an allowed IP address + +{% 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 %} + +### Using {% data variables.product.prodname_actions %} with an IP allow list + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-actions.ip-allow-list-hosted-runners %} + +{% else %} + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +{% endif %} diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000..15cfec9a94 --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,143 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +topics: + - organizations + - teams +--- + +### 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. {% 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 %} + +### 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 all security and analysis features for the repositories in your organization. + +{% if currentVersion == "free-pro-team@latest" %}If your organization belongs to an enterprise with 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. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %}If you have 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. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} + +{% if currentVersion == "github-ae@latest" %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features.{% 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)." +2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + !["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 %} + {% if currentVersion == "github-ae@latest" %} + !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +3. Optionally, enable the feature by default for new repositories in your organization. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + !["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 %} +4. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% endif %} + {% if currentVersion == "github-ae@latest" %} +3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} + + {% data reusables.security.displayed-information %} + +### 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)." +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![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 %} + {% if currentVersion == "github-ae@latest" %} + ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### Allowing {% data variables.product.prodname_dependabot %} to access private dependencies + +{% 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. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. 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. + +If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." + +To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository: + +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 "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**. ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. Start typing the name of the repository you want to allow. ![Add repositories button](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Click the repository you want to allow. + +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. !["X" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization + +You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization. + +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. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. The size of your license is shown for organization-level licenses. For more information, see "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)." +1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}. +1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}. + +{% note %} + +**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning. + +{% endnote %} + +{% 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 %}{% if currentVersion != "github-ae@latest" %} +- "[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)"{% endif %} diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..a23a4647fe --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Preparing to require two-factor authentication in your organization +intro: 'Before requiring two-factor authentication (2FA), you can notify users about the upcoming change and verify who already uses 2FA.' +redirect_from: + - /articles/preparing-to-require-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +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. + +When you require use of two-factor authentication for your organization, members, outside collaborators, and billing managers (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. + +Before requiring 2FA in your organization, we recommend that you: + - [Enable 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) on your personal account + - Ask the people in your organization to set up 2FA for their accounts + - See whether [users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/) + - Warn users that once 2FA is enabled, those without 2FA are automatically removed from the organization diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..f82001d799 --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,80 @@ +--- +title: Requiring two-factor authentication in your organization +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.' +redirect_from: + - /articles/requiring-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +### 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)." + +{% if currentVersion == "free-pro-team@latest" %} + +You can also require two-factor authentication for organizations in an enterprise. 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#requiring-two-factor-authentication-for-organizations-in-your-enterprise-account)." + +{% endif %} + +{% warning %} + +**Warnings:** + +- 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. They will also lose access to their forks of the organization's private repositories. You can [reinstate their access privileges and settings](/articles/reinstating-a-former-member-of-your-organization) if they enable two-factor authentication for their personal account within three months of their removal from 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. +- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization. + +{% endwarning %} + +{% data reusables.two_fa.auth_methods_2fa %} + +### Требования + +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 %}. For more information, see "[Securing your account with two-factor authentication (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. For more information, see "[Viewing whether users in your organization have 2FA enabled](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)." + +### Requiring two-factor authentication in your organization + +{% 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. If any members or outside collaborators are removed from the organization, we recommend sending them an invitation that can reinstate their former privileges and access to your organization. They must enable two-factor authentication before they can accept your invitation. +{% endif %} + +### Viewing people who were removed from your organization + +To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search your organization's audit log](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log) for people removed from your organization. The audit log event will show if a person was removed for 2FA non-compliance. + +![Audit log event showing a user removed for 2FA non-compliance](/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. Enter your search query. To search for: + - Organization members removed, use `action:org.remove_member` in your search query + - Outside collaborators removed, use `action:org.remove_outside_collaborator` in your search query{% if currentVersion == "free-pro-team@latest" %} + - Billing managers removed, use `action:org.remove_billing_manager`in your search query{% endif %} + + You can also view people who were removed from your organization by using a [time frame](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) in your search. + +### Helping removed members and outside collaborators rejoin your organization + +If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization. + +### Дополнительная литература + +- "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)" +- "[Reinstating a former outside collaborator's access to your organization](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000..d4e2d5c231 --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,31 @@ +--- +title: Restricting email notifications to an approved domain +intro: 'To prevent organization information from leaking into personal accounts, organization owners can restrict email notifications about organization activity to a verified domain.' +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### 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. For more information, see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)." + +Outside collaborators are not subject to restrictions on email notifications for verified domains. For more information on outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/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)." + +### Restricting email notifications to an approved domain + +{% 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. Click **Save**. diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000..ea91887cff --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,643 @@ +--- +title: Reviewing the audit log for your organization +intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-the-audit-log-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Accessing the audit log + +The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.audit_log.audit_log_sidebar_for_org_admins %} + +### Searching the audit log + +{% data reusables.audit_log.audit-log-search %} + +#### Search based on the action performed + +To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories: + +| Category name | Description | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`учетная запись`](#account-category-actions) | Contains all activities related to your organization account. | +| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| [`выставление счетов`](#billing-category-actions) | Contains all activities related to your organization's billing. | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization. | +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." | +| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. | +| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page. | +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page. | +| [`перехватчик`](#hook-category-actions) | Contains all activities related to webhooks. | +| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | +| [`проблема`](#issue-category-actions) | Contains activities related to deleting an issue. |{% if currentVersion == "free-pro-team@latest" %} +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. | +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |{% endif %} +| [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`пакеты`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. | +| [`проект`](#project-category-actions) | Contains all activities related to project boards. | +| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. | +| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a | +| {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} | | +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| [`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 %} +| [`команда`](#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. Например: + + * `action:team` finds all events grouped within the team category. + * `-action:hook` excludes all events in the webhook category. + +Each category has a set of associated actions that you can filter on. Например: + + * `action:team.create` finds all events where a team was created. + * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered. + +#### Search based on time of action + +Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +Например: + + * `created:2014-07-08` finds all events that occurred on July 8th, 2014. + * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. + * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. + * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. + +The audit log contains data for the past 90 days, but you can use the `created` qualifier to search for events earlier than that. + +#### Search based on location + +Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. Например: + + * `country:de` finds all events that occurred in Germany. + * `country:Mexico` finds all events that occurred in Mexico. + * `country:"United States"` all finds events that occurred in the United States. + +{% if currentVersion == "free-pro-team@latest" %} +### Exporting the audit log + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### Using the audit log API + +You can interact with the audit log using the GraphQL API{% if currentVersion == "free-pro-team@latest" %} or the REST API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} + +#### Using the GraphQL API + +{% endif %} + +{% note %} + +**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +To ensure a secure IP and maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audit-log-api-info %} + +{% if currentVersion == "free-pro-team@latest" %} +Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)." +{% endif %} + +The GraphQL response can include data for up to 90 to 120 days. + +For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/v4/interface/auditentry/)." + +{% if currentVersion == "free-pro-team@latest" %} + +#### Using the REST API + +{% note %} + +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. + +{% endnote %} + +To ensure a secure IP and maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audit-log-api-info %} +* Git events, such as cloning, fetching, and pushing + +{% data reusables.audit_log.audit-log-git-events-retention %} + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endif %} + +### Audit log actions + +An overview of some of the most common actions that are recorded as events in the audit log. + +{% if currentVersion == "free-pro-team@latest" %} + +#### `account` category actions + +| Действие | Description | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes. | +| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes. | +| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). | +| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/). | + +#### `advisory_credit` category actions + +| Действие | Description | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." | +| `create` | Triggered when the administrator of a security advisory adds someone to the credit section. | +| `decline` | Triggered when someone declines credit for a security advisory. | +| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. | + +#### `billing` category actions + +| Действие | Description | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). | +| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes. | + +#### `dependabot_alerts` category actions + +| Действие | Description | +| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `включить` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +#### `dependabot_alerts_new_repos` category actions + +| Действие | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `включить` | 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 + +| Действие | Description | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `отключить` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `включить` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. | + +#### `dependabot_security_updates_new_repos` category actions + +| Действие | Description | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `включить` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. | + +#### `dependency_graph` category actions + +| Действие | Description | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `включить` | Triggered when an organization owner enables the dependency graph for all existing repositories. | + +#### `dependency_graph_new_repos` category actions + +| Действие | Description | +| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | +| `включить` | Triggered when an organization owner enables the dependency graph for all new repositories. | + +{% endif %} + +#### `discussion_post` category actions + +| Действие | Description | +| ------------ | --------------------------------------------------------------------------------------------------------------- | +| `обновление` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). | + +#### `discussion_post_reply` category actions + +| Действие | Description | +| ------------ | -------------------------------------------------------------------------------------------------------------------------- | +| `обновление` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | +| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### `enterprise` category actions + +{% data reusables.actions.actions-audit-events-for-enterprise %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `environment` category actions + +| Действие | Description | +| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `delete - Удалить` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." | +| `remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `git` category actions + +{% note %} + +**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Действие | Description | +| ---------- | ----------------------------------------------------- | +| `клон` | Triggered when a repository is cloned. | +| `выбрать` | Triggered when changes are fetched from a repository. | +| `отправка` | Triggered when changes are pushed to a repository. | + +{% endif %} + +#### `hook` category actions + +| Действие | Description | +| ---------------- | -------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization. | +| `config_changed` | Triggered when an existing hook has its configuration altered. | +| `destroy` | Triggered when an existing hook was removed from a repository. | +| `events_changed` | Triggered when the events on a hook have been altered. | + +#### `integration_installation_request` category actions + +| Действие | Description | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. | +| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. | + +#### `issue` category actions + +| Действие | Description | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `destroy` | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository. | + +{% if currentVersion == "free-pro-team@latest" %} + +#### `marketplace_agreement_signature` category actions + +| Действие | Description | +| -------- | -------------------------------------------------------------------------------------------------- | +| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. | + +#### `marketplace_listing` category actions + +| Действие | Description | +| ----------- | --------------------------------------------------------------------------------------------------------------- | +| `утвердить` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. | +| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. | +| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. | +| `redraft` | Triggered when your listing is sent back to draft state. | +| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +#### `members_can_create_pages` category actions + +For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." + +| Действие | Description | +|:----------- |:---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `включить` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | +| `отключить` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | + +{% endif %} + +#### `org` category actions + +| Действие | Description | +| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `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](/communities/maintaining-your-safety-on-github/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 {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/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" %} +| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization. | +| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %} +| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% if currentVersion != "github-ae@latest" %} +| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %} +| `invite_member` | Triggered when [a new user was invited to join your organization](/articles/adding-organization-members-to-a-team).{% if currentVersion == "free-pro-team@latest" %} +| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). | +| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization. | +| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." | +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. +{% endif %} +| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization. | +| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% if currentVersion != "github-ae@latest" %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/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` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." | +| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/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` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." | +| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | +| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | +| `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." | +| `runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% endif %}{% if currentVersion == "free-pro-team@latest"%}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% 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` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."{% endif %} +| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members. | +| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner. | +| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% if currentVersion == "free-pro-team@latest" %} +| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated. | +| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `org_credential_authorization` category actions + +| Действие | Description | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). | +| `revoke` | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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" %} +#### `organization_label` category actions + +| Действие | Description | +| ------------ | ------------------------------------------ | +| `create` | Triggered when a default label is created. | +| `обновление` | Triggered when a default label is edited. | +| `destroy` | Triggered when a default label is deleted. | + +{% endif %} + +#### `oauth_application` category actions + +| Действие | Description | +| --------------- | ------------------------------------------------------------------------------------------------------------------ | +| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. | +| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. | +| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. | +| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. | +| `передача` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +#### `packages` category actions + +| Действие | Description | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `package_version_published` | Triggered when a package version is published. | +| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | +| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `payment_method` category actions + +| Действие | Description | +| ------------ | ------------------------------------------------------------------------------------------ | +| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method). | +| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account. | +| `обновление` | Triggered when an existing payment method is updated. | + +{% endif %} + +#### `profile_picture` category actions +| Действие | Description | +| ---------- | --------------------------------------------------------------------- | +| обновление | Triggered when you set or update your organization's profile picture. | + +#### `project` category actions + +| Действие | Description | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Triggered when a project board is created. | +| `link` | Triggered when a repository is linked to a project board. | +| `rename` | Triggered when a project board is renamed. | +| `обновление` | Triggered when a project board is updated. | +| `delete - Удалить` | Triggered when a project board is deleted. | +| `unlink` | Triggered when a repository is unlinked from a project board. | +| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. | +| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. | +| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed. | + +#### `protected_branch` category actions + +| Действие | Description | +| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when branch protection is enabled on a branch. | +| `destroy` | Triggered when branch protection is disabled on a branch. | +| `update_admin_enforced` | Triggered when branch protection is enforced for repository administrators. | +| `update_require_code_owner_review` | Triggered when enforcement of required Code Owner review is updated on a branch. | +| `dismiss_stale_reviews` | Triggered when enforcement of dismissing stale pull requests is updated on a branch. | +| `update_signature_requirement_enforcement_level` | Triggered when enforcement of required commit signing is updated on a branch. | +| `update_pull_request_reviews_enforcement_level` | Triggered when enforcement of required pull request reviews is updated on a branch. | +| `update_required_status_checks_enforcement_level` | Triggered when enforcement of required status checks is updated on a branch. | +| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | +| `rejected_ref_update` | Triggered when a branch update attempt is rejected. | +| `policy_override` | Triggered when a branch protection requirement is overridden by a repository administrator.{% 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` | Triggered when force pushes are enabled or disabled for a protected branch. | +| `update_allow_deletions_enforcement_level` | Triggered when branch deletion is enabled or disabled for a protected branch. | +| `update_linear_history_requirement_enforcement_level` | Triggered when required linear commit history is enabled or disabled for a protected branch. | +{% endif %} + +#### `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. | +| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." | +| `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" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for 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)." | +| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for 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).".{% 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.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 {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} +| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `отключить` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %} +| `включить` | 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 {% data variables.product.prodname_actions %} secret is removed.{% 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 new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." | +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/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).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %} +| `передача` | 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 {% data variables.product.prodname_actions %} secret is updated.{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `repository_advisory` category actions + +| Действие | Description | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. | +| `open` | Triggered when someone opens a draft security advisory. | +| `publish` | Triggered when someone publishes a security advisory. | +| `reopen` | Triggered when someone reopens as draft security advisory. | +| `обновление` | Triggered when someone edits a draft or published security advisory. | + +#### `repository_content_analysis` category actions + +| Действие | Description | +| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `включить` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | +| `отключить` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | + +{% endif %}{% if currentVersion != "github-ae@latest" %} + +#### `repository_dependency_graph` category actions + +| Действие | Description | +| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | +| `включить` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### `repository_secret_scanning` category actions + +| Действие | Description | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | +| `включить` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. | + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### `repository_vulnerability_alert` category actions + +| Действие | Description | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | Triggered when {% data variables.product.product_name %} creates a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | +| `отклонить` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. | +| `разрешение проблем` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. | + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### `repository_vulnerability_alerts` category actions + +| Действие | 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)." | +| `отключить` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. | +| `включить` | 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" or currentVersion == "github-ae@latest" %} +#### `secret_scanning` category actions + +| Действие | Description | +| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | 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)." | +| `включить` | 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 + +| Действие | Description | +| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | Triggered when an organization owner disables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | +| `включить` | Triggered when an organization owner enables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `sponsors` category actions + +| Действие | Description | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo_funding_link_button_toggle` | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `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 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 "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| sponsored_developer_update_newsletter_send | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `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 %} + +#### `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.{% 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](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/managing-peoples-access-to-your-organization-with-roles/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 + +| Действие | Description | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `отключить` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." | +| `включить` | Triggered when an organization owner enables team discussions for an organization. | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +#### `workflows` category actions + +{% data reusables.actions.actions-audit-events-workflow %} + +{% endif %} + +### Дополнительная литература + +- "[Keeping your organization secure](/articles/keeping-your-organization-secure)" diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000..4e7d59f603 --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,25 @@ +--- +title: Reviewing your organization's installed integrations +intro: You can review the permission levels for your organization's installed integrations and configure each integration's access to organization repositories. +redirect_from: + - /articles/reviewing-your-organization-s-installed-integrations + - /articles/reviewing-your-organizations-installed-integrations + - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. In the left sidebar, click **Installed {% data variables.product.prodname_github_app %}s**. ![Installed {% data variables.product.prodname_github_app %}s tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png) +6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png) + - To give the {% data variables.product.prodname_github_app %} access to all of your organization's repositories, select **All repositories**. + - To choose specific repositories to give the application access to, select **Only select repositories**, then type a repository name. +7. Click **Save**. diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000..74b6f07781 --- /dev/null +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,30 @@ +--- +title: Viewing whether users in your organization have 2FA enabled +intro: 'You can see which organization owners, members, and outside collaborators have enabled two-factor authentication.' +redirect_from: + - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled + - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% 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. For more information, see "[Requiring two-factor authentication in your organization](/articles/requiring-two-factor-authentication-in-your-organization)." + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. To view organization members, including organization owners, who have enabled or disabled two-factor authentication, on the right, click **2FA**, and select **Enabled** or **Disabled**. ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png) +5. To view outside collaborators in your organization, under the "People" tab, click **Outside collaborators**. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) +6. To view which outside collaborators have enabled or disabled two-factor authentication, on the right, click **2FA**, and select **Enabled** or **Disabled**. ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) + +### Дополнительная литература + +- "[Viewing people's roles in an organization](/articles/viewing-people-s-roles-in-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000..eb7c9f5e72 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,40 @@ +--- +title: Adding GitHub App managers in your organization +intro: 'Organization owners can grant users the ability to manage some or all {% data variables.product.prodname_github_app %}s owned by the organization.' +redirect_from: + - /articles/adding-github-app-managers-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization#github-app-managers)." + +### Giving someone the ability to manage all {% data variables.product.prodname_github_app %}s owned by the organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Under "Management", type the username of the person you want to designate as a {% data variables.product.prodname_github_app %} manager in the organization, and click **Grant**. ![Add a {% data variables.product.prodname_github_app %} manager](/assets/images/help/organizations/add-github-app-manager.png) + +### Giving someone the ability to manage an individual {% 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. Under "{% 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. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Under "App managers", type the username of the person you want to designate as a GitHub App manager for the app, and click **Grant**. ![Add a {% data variables.product.prodname_github_app %} manager for a specific app](/assets/images/help/organizations/add-github-app-manager-for-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Дополнительная литература + +- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/index.md new file mode 100644 index 0000000000..07610efc3f --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -0,0 +1,18 @@ +--- +title: Managing access to your organization's apps +intro: 'As an organization owner, you can allow individual organization members to manage {% data variables.product.prodname_github_app %}s in your organization.' +redirect_from: + - /articles/managing-access-to-your-organization-s-apps + - /articles/managing-access-to-your-organizations-apps + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /adding-github-app-managers-in-your-organization %} +{% link_in_list /removing-github-app-managers-from-your-organization %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000..f3683fa04a --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,40 @@ +--- +title: Removing GitHub App managers from your organization +intro: 'Organization owners can revoke {% data variables.product.prodname_github_app %} manager permissions that were granted to a member of the organization.' +redirect_from: + - /articles/removing-github-app-managers-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization#github-app-managers)." + +### Removing a {% data variables.product.prodname_github_app %} manager's permissions for the entire organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.github-apps-settings-sidebar %} +1. Under "Management", find the username of the person you want to remove {% data variables.product.prodname_github_app %} manager permissions from, and click **Revoke**. ![Revoke {% data variables.product.prodname_github_app %} manager permissions](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) + +### Removing a {% data variables.product.prodname_github_app %} manager's permissions for an individual {% 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. Under "{% 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. ![Select {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +{% data reusables.organizations.app-managers-settings-sidebar %} +1. Under "App managers", find the username of the person you want to remove {% data variables.product.prodname_github_app %} manager permissions from, and click **Revoke**. ![Revoke {% data variables.product.prodname_github_app %} manager permissions](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) + +{% if currentVersion == "free-pro-team@latest" %} +### Дополнительная литература + +- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000..26843c4457 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Adding an outside collaborator to a project board in your organization +intro: 'As an organization owner or project board admin, you can add an outside collaborator and customize their permissions to a project board.' +redirect_from: + - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a project board in your 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 %} +9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or {% data variables.product.prodname_dotcom %} email. ![The Collaborators section with the Octocat's username entered in the search field](/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/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/index.md new file mode 100644 index 0000000000..22f18b40c8 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -0,0 +1,22 @@ +--- +title: Managing access to your organization’s project boards +intro: 'As an organization owner or project board admin, you can give organization members, teams, and outside collaborators different levels of access to project boards owned by your organization.' +redirect_from: + - /articles/managing-access-to-your-organization-s-project-boards + - /articles/managing-access-to-your-organizations-project-boards + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000..8f5d65c64f --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,39 @@ +--- +title: Managing access to a project board for organization members +intro: 'As an organization owner or project board admin, you can set a default permission level for a project board for all organization members.' +redirect_from: + - /articles/managing-access-to-a-project-board-for-organization-members + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +By default, organization members have write access to their organization's project boards unless organization owners or project board admins set different permissions for specific project boards. + +### Setting a baseline permission level for all organization members + +{% tip %} + +**Tip:** You can give an organization member higher permissions to project board. For more information, see "[Project board permissions for an organization](/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. Under "Organization member permission", choose a baseline permission level for all organization members: **Read**, **Write**, **Admin**, or **None**. ![Baseline project board permission options for all organization members](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. Click **Save**. + +### Дополнительная литература + +- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..cda001f767 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,62 @@ +--- +title: Managing an individual’s access to an organization project board +intro: 'As an organization owner or project board admin, you can manage an individual member''s access to a project board owned by your organization.' +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-project-board + - /articles/managing-an-individuals-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% note %} + +**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." + +{% endnote %} + +### Giving an organization member access to a project board + +{% 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. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email. ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} + +### Changing an organization member's access to a project board + +{% 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 %} + +### Removing an organization member's access to a project board + +When you remove a collaborator from a project board, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a project board, you must remove access for each role the person has. For instance, a person may have access to the project board as an organization member or team member. For more information, see "[Project board permissions for an organization](/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 %} + +### Дополнительная литература + +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..14426751a6 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,52 @@ +--- +title: Managing team access to an organization project board +intro: 'As an organization owner or project board admin, you can give a team access to a project board owned by your organization.' +redirect_from: + - /articles/managing-team-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% warning %} + +**Warnings:** +- You can change a team's permission level if the team has direct access to a project board. If the team's access to the project board is inherited from a parent team, you must change the parent team's access to the project board. +- If you add or remove project board access for a parent team, each of that parent's child teams will also receive or lose access to the project board. For more information, see "[About teams](/articles/about-teams)." + +{% endwarning %} + +### Giving a team access to a project board + +You can give an entire team the same permission level to a project board. + +{% note %} + +**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a project board, and a project board admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the project board. For more information see, "[Project board permissions for an organization](/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. In the left sidebar, click **Teams**. +9. To add a team, click **Add a team: Select team**. Then, choose a team from the drop-down menu or search for the team you'd like to add. ![Add a team drop-down menu with list of teams in organization](/assets/images/help/projects/add-a-team.png) +10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**. ![Team permissions drop-down menu with read, write, and admin options](/assets/images/help/projects/org-project-team-choose-permissions.png) + +### Configuring a team's access to a project board + +If a team's access to a project board is inherited from a parent team, you must change the parent team's access to the project board to update access to the child teams. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**. ![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png) +5. To change permissions levels, to the right of the project board you want to update, use the drop-down. To remove a project board, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png) diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000..c676036fe3 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -0,0 +1,44 @@ +--- +title: Project board permissions for an organization +intro: 'Organization owners and people with project board admin permissions can customize who has read, write, and admin permissions to your organization’s project boards.' +redirect_from: + - /articles/project-board-permissions-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Permissions overview + +There are three levels of permissions to a project board for people and teams: + +{% data reusables.project-management.project-board-permissions %} + +Organization owners and people with admin permissions can give a person access to an organization project board individually, as an outside collaborator or organization member, or through their membership in a team or organization. An outside collaborator is someone who is not an organization member but given permissions to collaborate in your organization. + +Organization owners and people with admin permissions to a project board can also: +- Set default project board permissions for all organization members. +- Manage access to the project board for organization members, teams, and outside collaborators. For more information, see "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)", "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)", or "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." +- Manage project board visibility. For more information, see "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)." + +### Cascading permissions for project boards + +{% data reusables.project-management.cascading-permissions %} + +For example, if an organization owner has given all organization members read permissions to a project board, and a project board admin gives an organization member write permissions to that board as an individual collaborator, that person would have write permissions to the project board. + +### 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)." + +### Дополнительная литература + +- "[Changing project board visibility](/articles/changing-project-board-visibility)" +- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)" +- "[Managing access to a project board for organization members](/articles/managing-access-to-a-project-board-for-organization-members)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000..4c2d3ff3cf --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,23 @@ +--- +title: Removing an outside collaborator from an organization project board +intro: 'As an organization owner or project board admin, you can remove an outside collaborator''s access to a project board.' +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000..0f725d928e --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,42 @@ +--- +title: Adding outside collaborators to repositories in your organization +intro: 'An *outside collaborator* is a person who isn''t explicitly a member of your organization, but who has Read, Write, or Admin permissions to one or more repositories in your organization.' +redirect_from: + - /articles/adding-outside-collaborators-to-repositories-in-your-organization + - github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} add outside collaborators to a repository, unless an organization owner has restricted the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/articles/setting-permissions-for-adding-outside-collaborators)." + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% if currentVersion != "github-ae@latest" %} +If your organization [requires members and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), they must enable two-factor authentication before they can accept your invitation to collaborate on an organization repository. +{% 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. In the search field, start typing the name of person you want to invite, then click a name in the list of matches. ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png) +6. Under "Choose a role", select the permissions to grant to the person, then click **Add NAME to REPOSITORY**. ![Selecting permissions for the person](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +{% else %} +5. In the left sidebar, click **Collaborators & teams**. ![Repository settings sidebar with Collaborators & teams highlighted](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**. ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. Next to the new collaborator's name, choose the appropriate permission level: *Write*, *Read*, or *Admin*. ![The repository permissions picker](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +{% endif %} + +### Дополнительная литература + +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000..3570e12c1d --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,24 @@ +--- +title: Canceling an invitation to become an outside collaborator in your organization +intro: You can cancel all invitations for a person to become an outside collaborator on repositories owned by your organization. +permissions: Organization owners can cancel an invitation to become an outside collaborator in the organization. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +You can view a list of all people with pending invitations to become an outside collaborator on any repository owned by your organization. + +For each pending collaborator, you can cancel all invitations to join organization repositories at the same time. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% 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 cancellation](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000..e0fe41d7ef --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,44 @@ +--- +title: Converting an organization member to an outside collaborator +intro: 'If a current member of your organization only needs access to certain repositories, such as consultants or temporary employees, you can convert them to an *outside collaborator*.' +redirect_from: + - /articles/converting-an-organization-member-to-an-outside-collaborator + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.owners-and-admins-can %} convert organization members into outside collaborators. + +{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} + +After converting an organization member to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The person will no longer be an explicit member of the organization, and will no longer be able to: + +- Create teams +- See all organization members and teams +- @mention any visible team +- Be a team maintainer + +For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)." + +We recommend reviewing the organization member's access to repositories to ensure their access is as you expect. For more information, see "[Managing an individual's access to an organization repository](/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. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Select the person or people you'd like to convert to outside collaborators. ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Above the list of members, use the drop-down menu and click **Convert to outside collaborator**. ![Drop-down menu with option to convert members to outside collaborators](/assets/images/help/teams/user-bulk-management-options.png) +6. Read the information about converting members to outside collaborators, then click **Convert to outside collaborator**. ![Information on outside collaborators permissions and Convert to outside collaborators button](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) + +### Дополнительная литература + +- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)" +- "[Converting an outside collaborator to an organization member](/articles/converting-an-outside-collaborator-to-an-organization-member)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000..3f893cc0fd --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,41 @@ +--- +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization owners can {% if currentVersion == "free-pro-team@latest" %}invite users to join{% else %}add users to{% endif %} an organization.' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization is on a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}{% endif %} + +{% 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 %} +{% 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. 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. 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 %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Дополнительная литература + +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..b8b30ba6d4 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/index.md @@ -0,0 +1,28 @@ +--- +title: Managing access to your organization's repositories +intro: Organization owners can manage individual and team access to the organization's repositories. Team maintainers can also manage a team's repository access. +redirect_from: + - /articles/permission-levels-for-an-organization-repository/ + - /articles/managing-access-to-your-organization-s-repositories + - /articles/managing-access-to-your-organizations-repositories + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000..3453a52987 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,39 @@ +--- +title: Managing an individual's access to an organization repository +intro: You can manage a person's access to a repository owned by your organization. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +People with admin permissions can manage the access of organization members and outside collaborators to an organization repository. + +### Removing access to repositories + +When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository. + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +### Managing an individual's access to an organization repository + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png) +5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. ![The manage access link](/assets/images/help/organizations/member-manage-access.png) +6. On the "Manage access" page, next to the repository, click **Manage access**. ![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png) +7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership. ![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png) + +### Дополнительная литература + +{% if currentVersion == "free-pro-team@latest" %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %} +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000..4db41b70a3 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +title: Managing team access to an organization repository +intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.' +redirect_from: + - /articles/managing-team-access-to-an-organization-repository-early-access-program/ + - /articles/managing-team-access-to-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository. + +{% warning %} + +**Warnings:** +- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository. +- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)." + +{% endwarning %} + +### Giving a team access to a repository + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. Above the list of repositories, click **Add repository**. ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png) +6. Type the name of a repository, then click **Add repository to team**. ![Repository search field](/assets/images/help/organizations/team-repositories-add.png) +7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team. ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png) + +### Removing a team's access to a repository + +You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams. + +{% 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. Select the repository or repositories you'd like to remove from the team. ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png) +6. Above the list of repositories, use the drop-down menu, and click **Remove from team**. ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png) +7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**. ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png) + +### Дополнительная литература + +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000..68763a5ce4 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,76 @@ +--- +title: Reinstating a former outside collaborator's access to your organization +intro: 'You can reinstate a former outside collaborator''s access permissions for organization repositories, forks, and settings.' +redirect_from: + - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization + - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +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. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +When you reinstate a former outside collaborator, you can restore: + - The user's former access to organization repositories + - Any private forks of repositories owned by the organization + - Membership in the organization's teams + - Previous access and permissions for the organization's repositories + - Stars for organization repositories + - Issue assignments in the organization + - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity) + +{% tip %} + +**Tips**: + - Only organization owners can reinstate outside collaborators' access to an organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." + - The reinstating a member flow on {% data variables.product.product_location %} may use the term "member" to describe reinstating an outside collaborator but if you reinstate this person and keep their previous privileges, they will only have their previous [outside collaborator permissions](/articles/permission-levels-for-an-organization/#outside-collaborators).{% if currentVersion == "free-pro-team@latest" %} + - If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."{% endif %} + +{% 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. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Invite and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Invite and start fresh**. + + {% warning %} + + **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Invite and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Invite and reinstate** instead. Once this person accepts the invitation, you can convert them to an organization member by [inviting them to join the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Add and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Add and start fresh**. + + {% warning %} + + **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Add and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Add and reinstate** instead. Then, you can convert them to an organization member by [adding them to the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). + + {% endwarning %} + + ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Send invitation**. ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Add member**. ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +8. The invited person will receive an email inviting them to the organization. They will need to accept the invitation before becoming an outside collaborator in the organization. {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Дальнейшее изучение + +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000..e3f416d858 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,57 @@ +--- +title: Removing an outside collaborator from an organization repository +intro: Owners and repository admins can remove an outside collaborator's access to a repository. +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Warning:** +- When removing an outside collaborator from a private repository, the paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." + +- You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. + +{% endwarning %} + +{% endif %} + +While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository. + +### Removing outside collaborators from all repositories in an organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. Select the outside collaborator or outside collaborators you'd like to remove from the organization. ![List of outside collaborators with two outside collaborators selected](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) +6. Above the list of outside collaborators, use the drop-down menu, and click **Remove from all repositories**. ![Drop-down menu with option to remove outside collaborators ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) +7. Review the outside collaborator or outside collaborators who will be removed from the organization, then click **Remove outside collaborators**. ![List of outside collaborators who will be removed and Remove outside collaborators button](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) + +### Removing an outside collaborator from a particular repository in an organization + +If you only want to remove an outside collaborator from certain repositories in your organization, you can remove this person's access to one specific repository at a time. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. To the right of the username of the person you want to remove, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. ![Manage access button](/assets/images/help/organizations/member-manage-access.png) +6. To the right of the repository that you want to remove the outside collaborator from, click **Manage access**. ![Select manage access button next to a repository the outside collaborator has access to](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) +7. To completely remove the outside collaborator's access to the repository, in the upper right corner, click **Remove access to this repository**. ![Remove access to this repository button](/assets/images/help/organizations/remove-access-to-this-repository.png) +8. To confirm, click **Remove access**. ![Confirm outside collaborator who will be removed from the repository](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) + +### Дополнительная литература + +- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000..7f48486660 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -0,0 +1,181 @@ +--- +title: Repository permission levels for an organization +intro: 'You can customize access to each repository in your organization with granular permission levels, giving people access to the features and tasks they need.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +People with admin permissions can manage individual and team access to an organization-owned repository. + +### Permission levels for repositories owned by an organization + +You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization. Each permission level progressively increases access to a repository's content and settings. Choose the level that best fits each person or team's role in your project without giving people more access to the project than they need. + +From least access to most access, the permission levels for an organization repository are: +- **Read**: Recommended for non-code contributors who want to view or discuss your project +- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access +- **Write**: Recommended for contributors who actively push to your project +- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions +- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +For more information about giving people and teams access to repositories, see "[Managing access to your organization's repositories](/articles/managing-access-to-your-organizations-repositories)." + +Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." + +Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)." + +In addition to managing organization-level settings, organization owners have admin permissions for every repository owned by the organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." + +{% warning %} + +**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization. + +{% endwarning %} + +### Repository access for each permission level +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**Note:** Repository permissions required to use security features are listed in "[Permission requirements for security features](#permission-requirements-for-security-features)" below. + +{% endnote %} + +{% 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](/communities/maintaining-your-safety-on-github/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" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [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](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/communities/moderating-comments-and-conversations/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" or currentVersion == "github-ae@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** | +| | | | | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **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](/communities/moderating-comments-and-conversations/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](/organizations/managing-access-to-your-organizations-repositories/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" or currentVersion ver_gt "enterprise-server@3.0" %} +| 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" %} +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +{% endif %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +#### Permission requirements for security features + +In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_advanced_security %} features. + +| Repository action | Read | Приоритизация | Write | Maintain | Admin | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:| +| {% if currentVersion == "free-pro-team@latest" %} | | | | | | +| 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** | +| 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.22" or currentVersion == "github-ae@latest" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** | +| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| [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@3.0" or currentVersion == 'github-ae@next' %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% if currentVersion == "enterprise-server@3.0" %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +[1] Repository writers and maintainers can only see alert information for their own commits. +{% endif %} +{% endif %} + +### Дополнительная литература + +- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)" +- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000..016f453c26 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -0,0 +1,36 @@ +--- +title: Setting base permissions for an organization +intro: You can set base permissions for the repositories that an organization owns. +permissions: Organization owners can set base permissions for an organization. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### About base permissions for an organization + +You can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. Base permissions do not apply to outside collaborators. + +{% if currentVersion == "free-pro-team@latest" %}By default, members of an organization will have **Read** permissions to the organization's repositories.{% endif %} + +If someone with admin permissions to an organization's repository grants a member a higher level of permission for the repository, the higher level of permission overrides the base permission. + +### Setting base permissions + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Base permissions", use the drop-down to select new base permissions. ![Selecting new permission level from base permissions drop-down](/assets/images/help/organizations/base-permissions-drop-down.png) +6. Review the changes. To confirm, click **Change default permission to PERMISSION**. ![Reviewing and confirming change of base permissions](/assets/images/help/organizations/base-permissions-confirm.png) + +### Дополнительная литература + +- "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" +- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000..70fba13ca5 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,41 @@ +--- +title: Viewing people with access to your repository +intro: 'Organization owners can view people’s access to a repository within an organization. Owners of organizations using {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} can also export a CSV list of people who have access to a repository.' +redirect_from: + - /articles/viewing-people-with-access-to-your-repository + - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Administrators can use this information to help off-board people, gather data for compliance, and other general security checkups. + +![Repository people permissions list](/assets/images/help/repository/repository-permissions-list.png) + +### Viewing people with access to your repository + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**Note**: You can also see a combined overview of teams and people with access to your repository. For more information, see "[Managing teams and people with access to your repository](/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 %} + +### Exporting a list of people with access to your repository + +Owners of organizations on {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %} can export a CSV list of people who have access to a repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} +4. Click **Export CSV**. ![People tab in the repository sidebar](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000..7b371b9ae4 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -0,0 +1,47 @@ +--- +title: About SSH certificate authorities +intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.' +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/about-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)." + +After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with 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 %} + +For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. + +When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +``` + +You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia. + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +{% if currentVersion == "free-pro-team@latest" %} + +Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, personal access tokens, and their own SSH keys. + +{% endif %} + +To prevent authentication errors, organization members should use a special URL that includes the organization ID to clone repositories using signed certificates. Anyone with read access to the repository can find this URL on the repository page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." diff --git a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..8bdd4f0224 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -0,0 +1,19 @@ +--- +title: Managing Git access to your organization's repositories +intro: You can add an SSH certificate authority (CA) to your organization and allow members to access the organization's repositories over Git using keys signed by the SSH CA. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% link_in_list /about-ssh-certificate-authorities %} +{% link_in_list /managing-your-organizations-ssh-certificate-authorities %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000..775efdaa45 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,38 @@ +--- +title: Managing your organization's SSH certificate authorities +intro: You can add or delete SSH certificate authorities from your organization. +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-your-organizations-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage an organization's SSH certificate authorities (CA). + +You can allow members to access your organization's repositories using SSH certificates you provide by adding an SSH CA to your organization. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)." + +### Adding an SSH certificate authority + +{% 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 %} + +### Deleting an SSH certificate authority + +{% 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/ru-RU/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md new file mode 100644 index 0000000000..3013e44b9d --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -0,0 +1,29 @@ +--- +title: Adding people to your organization +intro: 'You can make anyone a member of your organization using their {% data variables.product.product_name %} username or email address.' +redirect_from: + - /articles/adding-people-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization +versions: + enterprise-server: '*' + github-ae: '*' +permissions: 'Organization owners can add people to an organization.' +--- + +{% if currentVersion != "github-ae@latest" %} +If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization. +{% 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 %} + +### Дополнительная литература +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000..f13fa6a80f --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,21 @@ +--- +title: Can I create accounts for people in my organization? +intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization + - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Because you access an organization by logging in to a personal account, each of your team members needs a personal account. Once you have user names for each person you'd like to add to your organization, you can add them to teams. + +### Adding users to your organization + +1. Provide each person instructions to [create a personal account](/articles/signing-up-for-a-new-github-account). +2. Ask for the username of each person you want to give organization membership to. +3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account. diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000..981f6508b3 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,30 @@ +--- +title: Canceling or editing an invitation to join your organization +intro: Organization owners can edit or cancel an invitation to become a member of your organization any time before the user accepts. +redirect_from: + - /articles/canceling-or-editing-an-invitation-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. On the People tab, click **Pending invitation**. ![Pending invitation link](/assets/images/help/organizations/pending-invitation-link.png) +5. Next to the username or email address of the person whose invitation you'd like to edit or cancel, click **Edit invitation**. ![Edit invitation button](/assets/images/help/organizations/edit-invitation-button.png) + + You may need to click **View all invitations** at the bottom of the window to find the person you're looking for. +6. Decide whether to edit or cancel the user's invitation to join your organization. ![Update invitation and cancel invitation buttons](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) + - To edit the user's invitation, select a different role or team, then click **Update invitation**. + - To cancel the user's invitation to join your organization, click **Cancel invitation**. + +### Дополнительная литература + +{% if currentVersion == "free-pro-team@latest" %} +- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" +{% endif %} +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/index.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/index.md new file mode 100644 index 0000000000..f28c95e40d --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/index.md @@ -0,0 +1,23 @@ +--- +title: Managing membership in your organization +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. You can also remove members of the organization, and reinstate former members.' +redirect_from: + - /articles/removing-a-user-from-your-organization/ + - /articles/managing-membership-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000..dead387ff1 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Inviting users to join your organization +intro: 'You can invite anyone to become a member of your organization using their {% data variables.product.product_name %} username or email address.' +permissions: Organization owners can invite users to join an organization. +redirect_from: + - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ + - /articles/inviting-users-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Tips**: +- If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% 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](/organizations/keeping-your-organization-secure/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)." + +{% 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 %} + +### Дополнительная литература +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000..366ae7a1eb --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,63 @@ +--- +title: Reinstating a former member of your organization +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.' +redirect_from: + - /articles/reinstating-a-former-member-of-your-organization + - /github/setting-up-and-managing-organizations-and-teams/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. +topics: + - organizations + - teams +--- + +### 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. + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +When you reinstate a former organization member, you can restore: + - The user's role in the organization + - Any private forks of repositories owned by the organization + - Membership in the organization's teams + - Previous access and permissions for the organization's repositories + - Stars for organization repositories + - Issue assignments in the organization + - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity) + +{% if enterpriseServerVersions contains currentVersion %} +If an organization member was removed from the organization because they did not use two-factor authentication and your organization still requires members to use 2FA, the former member must enable two-factor authentication before you can reinstate their membership. +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +If your organization has a paid per-user subscription, an unused license must be available before you can 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 %} + +### Reinstating a former member of your organization + +{% 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. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Invite and reinstate** or **Invite and start fresh**. ![Choose to restore info or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Add and reinstate** or **Add and start fresh**. ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Send invitation**. ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Add member**. ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### Дополнительная литература + +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/ru-RU/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000..c7274bfb3d --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -0,0 +1,60 @@ +--- +title: Removing a member from your organization +intro: 'If members of your organization no longer require access to any repositories owned by the organization, you can remove them from the organization.' +redirect_from: + - /articles/removing-a-member-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Only organization owners can remove members from an organization. + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**Warning:** When you remove members from an organization: +- The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." +- Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. +- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible. + +{% endwarning %} + +{% else %} + +{% warning %} + +**Warning:** When you remove members from an organization: + - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. + - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible. + +{% endwarning %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +To help the person you're removing from your organization transition and help ensure they delete confidential information or intellectual property, we recommend sharing a checklist of best practices for leaving your organization. For an example, see "[Best practices for leaving your company](/articles/best-practices-for-leaving-your-company/)." + +{% endif %} + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} + +### Revoking the user's membership + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Select the member or members you'd like to remove from the organization. ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Above the list of members, use the drop-down menu, and click **Remove from organization**. ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png) +6. Review the member or members who will be removed from the organization, then click **Remove members**. ![List of members who will be removed and Remove members button](/assets/images/help/teams/confirm-remove-members-bulk.png) + +### Дополнительная литература + +- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000..2b4f1b54a6 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Allowing people to delete issues in your organization +intro: Organization owners can allow certain people to delete issues in repositories owned by your organization. +redirect_from: + - /articles/allowing-people-to-delete-issues-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +By default, issues cannot be deleted in an organization's repositories. An organization owner must enable this feature for all of the organization's repositories first. + +Once enabled, organization owners and people with admin permissions in an organization-owned repository can delete issues. People with admin permissions in a repository include organization members and outside collaborators with admin privileges. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)" and "[Deleting an issue](/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. Under "Issue deletion", select **Allow members to delete issues for this organization**. ![Checkbox to allow people to delete issues](/assets/images/help/settings/issue-deletion.png) +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/ru-RU/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000..c262ff9885 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,24 @@ +--- +title: Changing the visibility of your organization's dependency insights +intro: You can allow all organization members to view dependency insights for your organization or limit viewing to organization owners. +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/changing-the-visibility-of-your-organizations-dependency-insights + - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default. + +Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing a policy on dependency insights in your enterprise account](/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. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**. ![Checkbox to allow members to view insights](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000..a10c0b1708 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,22 @@ +--- +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.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} +{% data reusables.organizations.settings-sidebar-actions %} +{% data reusables.github-actions.change-retention-period-for-artifacts-logs %} diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/ru-RU/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000..134897705c --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -0,0 +1,33 @@ +--- +title: Converting an organization into a user +intro: 'It''s not possible to convert an organization into a personal user account, but you can create a new user account and transfer the organization''s repositories to it.' +redirect_from: + - /articles/converting-an-organization-into-a-user + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} + +1. [Sign up](/articles/signing-up-for-a-new-github-account) for a new GitHub user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. +5. [Delete the organization](/articles/deleting-an-organization-account). +6. [Rename the user](/articles/changing-your-github-username) to the organization's name. + +{% else %} + +1. Sign up for a new GitHub Enterprise user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. +5. [Delete the organization](/articles/deleting-an-organization-account). +6. [Rename the user](/articles/changing-your-github-username) to the organization's name. + +{% endif %} diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/ru-RU/content/organizations/managing-organization-settings/deleting-an-organization-account.md new file mode 100644 index 0000000000..9ab30b3656 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -0,0 +1,34 @@ +--- +title: Deleting an organization account +intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% 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 %}' +redirect_from: + - /articles/deleting-an-organization-account + - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content. + +{% endtip %} + +{% endif %} + +### 1. Back up your organization content + +Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. + +### 2. Delete the organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Near the bottom of the organization's settings page, click **Delete this Organization**. ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000..ba9aed9fc1 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,85 @@ +--- +title: Disabling or limiting GitHub Actions for your organization +intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### About {% data variables.product.prodname_actions %} permissions for your organization + +{% data reusables.github-actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." + +You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %} + +Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### Managing {% data variables.product.prodname_actions %} permissions for your organization + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Under **Local and third-party Actions**, select an option. ![Enable, disable, or limit actions for this organization](/assets/images/help/repository/enable-org-actions.png) +1. Click **Save**. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### Managing {% data variables.product.prodname_actions %} permissions for your organization + +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 %} + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. Under **Policies**, select an option. ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png) +1. Click **Save**. + +### Allowing specific actions to run + +{% 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. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Click **Save**. + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### Enabling workflows for private repository forks + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### Configuring the private fork policy for an organization + +{% 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/ru-RU/content/organizations/managing-organization-settings/index.md b/translations/ru-RU/content/organizations/managing-organization-settings/index.md new file mode 100644 index 0000000000..407237383f --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/index.md @@ -0,0 +1,39 @@ +--- +title: Managing organization settings +intro: 'Organization administrators can change several settings, including the names of repositories that belong to the organization and Owners team membership. In addition, organization admins can delete the organization and all of its repositories.' +redirect_from: + - /articles/managing-organization-settings + - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 /managing-the-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 %} diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/ru-RU/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000..844bcfb13e --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,26 @@ +--- +title: Integrating Jira with your organization project board +intro: 'You can integrate Jira Cloud with your organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.' +redirect_from: + - /articles/integrating-jira-with-your-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. In the left sidebar under **Organization settings**, click the name of your organization. ![Sidebar organization name](/assets/images/help/settings/organization-settings-from-sidebar.png) +3. In the left sidebar under **Developer settings**, click **OAuth applications**. ![OAuth applications tab in the left sidebar](/assets/images/help/organizations/org-oauth-applications-ghe.png) +4. Click **Register a new application**. +5. Under **Application name**, type "Jira". +6. Under **Homepage URL**, type the full URL to your Jira instance. +7. Under **Authorization callback URL**, type the full URL to your Jira instance. +8. Click **Register application**. ![Register application button](/assets/images/help/oauth/register-application-button.png) +9. Under **Organization owned applications**, note the "Client ID" and "Client Secret" values. ![Client ID and Client Secret](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### Дополнительная литература + +- ["Integrating Jira with your personal projects"](/articles/integrating-jira-with-your-personal-projects) +- Connect Jira Cloud to GitHub (Atlassian documentation) diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..dd0ee26c66 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,67 @@ +--- +title: Managing default labels for repositories in your organization +intro: You can customize the labels that are included in every new repository in your organization. +redirect_from: + - /articles/managing-default-labels-for-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage default labels for repositories in the organization. + +Default labels are included in every new repository in your organization, but anyone with write access to the repository can edit or delete the labels in that repository later. Adding, editing, or deleting a default label does not add, edit, or delete the label from existing repositories. + +### Creating a default label + +{% 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. Under "Repository labels", click **New label**. ![New label button](/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 %} + +### Editing a default label + +{% 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 %} + +### Deleting a default label + +{% 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 %} + +### Дополнительная литература + +- "[About labels](/articles/about-labels)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..5cacb9d87f --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,30 @@ +--- +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. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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. Click **Save**. !["Save" button for discussions settings](/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)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000..f27017b73f --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,66 @@ +--- +title: Managing scheduled reminders for your organization +intro: You can get reminders in Slack for all pull requests that teams in your organization have been requested to review. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About scheduled reminders for pull requests + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Organization owners can schedule a reminder for one or more teams in their organization, for all pull requests the team or teams have been requested to review. + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Creating a scheduled reminder for an organization +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Scheduled reminders button](/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. Under "Filter by team assigned to review code", click the **Add a team** dropdown and choose one or more teams. You can add up to 100 teams. If the team you select doesn't have access to the "Tracked repositories" selected above, you won't be able to create the scheduled reminder. ![Add a team dropdown](/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 %} + +### Managing a scheduled reminder for an organization +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Deleting a scheduled reminder for an organization +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![Scheduled reminders button](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.delete %} + +### Дополнительная литература + +- "[Managing your scheduled reminders](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" +- "[Managing scheduled reminders for your team](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..b9eb1f4a2b --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,36 @@ +--- +title: Managing the default branch name for repositories in your organization +intro: 'You can set the default branch name for repositories that members create in your organization on {% data variables.product.product_location %}.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +permissions: Organization owners can manage the default branch name for new repositories in the organization. +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - organizations + - teams +--- + +### About management of 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. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization 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 reusables.branches.change-default-branch %} + +If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Enforcing repository management policies in your enterprise](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." + +### Setting the default branch name + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. Under "Repository default branch", click **Change default branch name now**. ![Override button](/assets/images/help/organizations/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png) +5. Click **Update**. ![Update button](/assets/images/help/organizations/repo-default-name-update.png) + +### Дополнительная литература + +- "[Managing the default branch name for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000..625d7c1471 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,28 @@ +--- +title: Managing the display of member names in your organization +intro: You can allow members of your organization to see a comment author's profile name in private repositories in the organization. +product: '{% data reusables.gated-features.display-names %}' +redirect_from: + - /articles/managing-the-display-of-member-names-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can manage the display of member names in an organization. + +![Commenter's profile name displayed in comment](/assets/images/help/issues/commenter-full-name.png) + +Each organization member chooses their own profile name in their settings. For more information, see "[Personalizing your profile](/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. Under "Admin repository permissions", select or unselect **Allow members to see comment author's profile name in private repositories**. ![Checkbox to allow members to see comment author's full name in private repositories](/assets/images/help/organizations/allow-members-to-view-full-names.png) +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000..2c24961068 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Managing the forking policy for your organization +intro: 'You can can allow or prevent the forking of any private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories owned by your organization.' +redirect_from: + - /articles/allowing-people-to-fork-private-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization +permissions: Organization owners can manage the forking policy for an organization. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +By default, new organizations are configured to disallow the forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories. + +If you allow forking of private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." + +{% data reusables.organizations.internal-repos-enterprise %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository forking", select **Allow forking of private repositories** or **Allow forking of private and internal repositories**. ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png) +6. Click **Save**. + +### Дополнительная литература + +- "[About forks](/articles/about-forks)" +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..9f8b891551 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Managing the publication of GitHub Pages sites for your organization +intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization +topics: + - organizations + - teams +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-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 %}{% if currentVersion == "free-pro-team@latest" %} +1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} +1. Under "Pages creation", select or deselect **Allow members to publish sites**. ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} +1. Click **Save**. + +### Дополнительная литература + +- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ru-RU/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..562c8c2d39 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,28 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +topics: + - organizations + - teams +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +The developers and organizations that your organization sponsors can send you updates about their work. You can manage the email address that receives these updates. + +You can also disable updates from accounts your organization sponsors. For more information, see "[Managing your sponsorship](/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. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors. ![Textbox to enter the email address to receive updates from sponsored accounts](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. Click **Update profile**. ![Update profile button](/assets/images/help/organizations/update-profile-button.png) + +### Дополнительная литература + +- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/renaming-an-organization.md new file mode 100644 index 0000000000..5194b40bd3 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -0,0 +1,50 @@ +--- +title: Renaming an organization +intro: 'If your project or company has changed names, you can update the name of your organization to match.' +redirect_from: + - /articles/what-happens-when-i-change-my-organization-s-name/ + - /articles/renaming-an-organization + - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Tip:** Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +### What happens when I change my organization's name? + +After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect. + +#### Changes that occur automatically + +- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories. Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change. +- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +- Previous Git commits will also be correctly attributed to users within your organization. + +#### Changes that aren't automatic + +After changing your organization's name: +- Links to your previous organization profile page, such as `https://{% data variables.command_line.backticks %}/previousorgname`, will return a 404 error. 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 %}. +- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests. +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} + +### Changing your organization's name + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. Near the bottom of the settings page, under "Rename organization", click **Rename Organization**. ![Rename organization button](/assets/images/help/settings/settings-rename-organization.png) + +### Дополнительная литература + +* "[Why are my commits linked to the wrong user?](/articles/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000..f004cf1151 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,35 @@ +--- +title: Restricting repository creation in your organization +intro: 'To protect your organization''s data, you can configure permissions for creating repositories in your organization.' +redirect_from: + - /articles/restricting-repository-creation-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +You can choose whether members can create repositories in your organization. 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)." + +Organization owners can always create any type of repository. + +{% 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 %} + +{% warning %} + +**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/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. Under "Repository creation", select one or more options. ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..ce4b905e7e --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Restricting repository visibility changes in your organization +intro: 'To protect your organization''s data, you can configure permissions for changing repository visibility in your organization.' +redirect_from: + - /articles/restricting-repository-visibility-changes-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +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 %} + +**Warning**: If enabled, this setting allows people with admin permissions to change an existing repository to any visibility, even if you do not allow that type of repository to be created. For more information about restricting the visibility of repositories during creation, see "[Restricting repository creation in your organization](/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. Under "Repository visibility change", deselect **Allow members to change repository visibilities for this organization**. ![Checkbox to allow members to change repository visibility](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) +6. Click **Save**. + +### Дополнительная литература + +- "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000..acec392575 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,28 @@ +--- +title: Setting permissions for adding outside collaborators +intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.' +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners, and members with admin privileges for a repository, can invite outside collaborators to work on the repository. You can also restrict outside collaborator invite permissions to only organization owners. + +{% 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. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %} +![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %} +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000..9db1d155b8 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,24 @@ +--- +title: Setting permissions for deleting or transferring repositories +intro: 'You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.' +redirect_from: + - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ + - /articles/setting-permissions-for-deleting-or-transferring-repositories + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Owners can set permissions for deleting or transferring repositories in an organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository deletion and transfer", select or deselect **Allow members to delete or transfer repositories for this organization**. ![Checkbox to allow members to delete repositories](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000..c641903238 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Setting team creation permissions in your organization +intro: You can allow all organization members to create teams or limit team creation to organization owners. +redirect_from: + - /articles/setting-team-creation-permissions-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can set team creation permissions. + +If you do not set team creation permissions, all organization members will be able to create teams by default. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Team creation rules", select or deselect **Allow members to create teams**. ![Checkbox to allow members to create teams](/assets/images/help/organizations/allow-members-to-create-teams.png) +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md new file mode 100644 index 0000000000..36919bf9d1 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -0,0 +1,29 @@ +--- +title: 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.' +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership + - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +1. If you're the only member with *owner* privileges, give another organization member the owner role. For more information, see "[Appointing an organization owner](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)." +2. Contact the new owner and make sure he or she is able to [access the organization's settings](/articles/accessing-your-organization-s-settings). +{% if currentVersion == "free-pro-team@latest" %} +3. If you are currently responsible for paying for GitHub in your organization, you'll also need to have the new owner or a [billing manager](/articles/adding-a-billing-manager-to-your-organization/) update the organization's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)." + + {% warning %} + + **Warning**: Removing yourself from the organization **does not** update the billing information on file for the organization account. The new owner or a billing manager must update the billing information on file to remove your credit card or PayPal information. + + {% endwarning %} + +{% endif %} +4. [Remove yourself](/articles/removing-yourself-from-an-organization) from the organization. diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/ru-RU/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000..e4a719a245 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,24 @@ +--- +title: Upgrading to the Corporate Terms of Service +intro: Organizations can upgrade from the Standard Terms of Service to the Corporate Terms of Service. +redirect_from: + - /articles/upgrading-to-the-corporate-terms-of-service + - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +The Standard Terms of Service is an agreement between {% data variables.product.prodname_dotcom %} and you as an individual. To enter into an agreement with {% data variables.product.prodname_dotcom %} on behalf of an entity, such as a company, non-profit, or group, organization owners can upgrade to the Corporate Terms of Service. + +1. Contact {% data variables.contact.contact_support %} to request an upgrade to the Corporate Terms of Service. They will enable a banner on your organization's dashboard that will allow you to accept the Corporate Terms of Service. +{% data reusables.dashboard.access-org-dashboard %} +3. At the top of the page, to the right of the Terms of Service banner, click **Sign now**. ![Sign now button](/assets/images/help/organizations/sign-now-button.png) +4. Read the information about the Corporate Terms of Service, then select **Yes, I want to sign these terms on behalf of my business.** ![Check box to sign on behalf of your business](/assets/images/help/organizations/sign-on-behalf-business.png) +5. Type the name of the company, non-profit, or group that owns the organization account. This is the entity that will enter into an agreement with {% data variables.product.prodname_dotcom %}. ![Business name field](/assets/images/help/organizations/business-name-field.png) +6. To agree to the Corporate Terms of Service on behalf of your entity, click **Accept terms**. ![Accept terms button](/assets/images/help/organizations/accept-terms-button.png) + +### Дополнительная литература +- "[GitHub Corporate Terms of Service](/articles/github-corporate-terms-of-service/)" diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md b/translations/ru-RU/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md new file mode 100644 index 0000000000..995e8278ef --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md @@ -0,0 +1,42 @@ +--- +title: Verifying your organization's domain +intro: 'You can verify the domains controlled by your organization to confirm your organization''s identity on {% data variables.product.product_name %}.' +redirect_from: + - /articles/verifying-your-organization-s-domain + - /articles/verifying-your-organizations-domain + - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About domain verification + +To verify domains on {% data variables.product.product_name %}, you must have owner permissions in the organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." You will also need access to modify domain records with your domain hosting service. + +After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "[Upgrading to the Corporate Terms of Service](/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)." + +{% data reusables.organizations.verified-domains-details %} + +On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications to an approved domain](/articles/restricting-email-notifications-to-an-approved-domain)." + +### Verifying your organization's domain + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +5. Click **Add a domain**. ![Add a domain button](/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. You should see your new TXT record listed in the command output. + ```shell + $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT + ``` +8. After confirming your TXT record is added to your DNS, navigate to the Verified domains tab in your organization's settings. You can follow steps one through four above to locate the Verified domains tab. ![Verified domains settings page with pending domain](/assets/images/help/organizations/pending-domain-verification.png) +{% data reusables.organizations.continue-verifying-domain %} +11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service. ![Verified badge](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000..572ab60959 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,57 @@ +--- +title: Adding a billing manager to your organization +intro: 'A *billing manager* is a user who manages the billing settings for your organization, such as updating payment information. This is a great option if regular members of your organization don''t typically have access to billing resources.' +redirect_from: + - /articles/adding-a-billing-manager-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - выставление счетов +--- + +Members of your organization's Owners team can give *billing manager* permissions to people. Once a person accepts their invitation to become a billing manager for your organization, they can invite additional people to be billing managers. + +{% note %} + +**Note:** Billing managers do not use paid licenses in your organization's subscription. + +{% endnote %} + +### Permissions for billing managers + +Billing managers can: + +- Upgrade or downgrade the account +- Add, update, or remove payment methods +- View payment history +- Download receipts +- View, invite, and remove billing managers + +In addition, all billing managers will receive billing receipts by email on the organization's billing date. + +Billing managers **are not** able to: + +- Create or access repositories in your organizations +- See private members of your organization +- Be seen in the list of organization members +- Purchase, edit, or cancel subscriptions for {% data variables.product.prodname_marketplace %} apps + +{% tip %} + +**Tip:** If your organization [requires members, billing managers, and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), the user must enable two-factor authentication before they can accept your invitation to become a billing manager for the organization. + +{% endtip %} + +### Inviting a billing manager + +The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a GitHub account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. Next to Billing managers, click **Add a billing manager**. ![Invite billing manager](/assets/images/help/billing/settings_billing_managers_list.png) +6. Type the username or email address of the person you want to add and click **Send invitation**. ![Invite billing manager page](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000..481560522e --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,29 @@ +--- +title: Giving "team maintainer" permissions to an organization member +intro: 'An organization owner can promote any member of the organization to *team maintainer* for a team, giving them a subset of privileges available to organization owners.' +redirect_from: + - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ + - /articles/giving-team-maintainer-permissions-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team_maintainers_can %} + +### Promoting an organization member to team maintainer + +Before promoting an organization member to team maintainer, the person must already be a member of the team. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +4. Select the person or people you'd like to promote to team maintainer. ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png) +5. Above the list of team members, use the drop-down menu and click **Change role...**. ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png) +6. Select a new role and click **Change role**. ![Radio buttons for Maintainer or Member roles](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md new file mode 100644 index 0000000000..a6fedeb7bc --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -0,0 +1,21 @@ +--- +title: Managing people's access to your organization with roles +intro: 'A person''s role in your organization defines their level of access to your organization, its settings, and your data. You can make people owners, members, or billing managers for your organization, or you can give them team maintainer permissions.' +redirect_from: + - /articles/managing-people-s-access-to-your-organization-with-roles + - /articles/managing-peoples-access-to-your-organization-with-roles + - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000..07a0373218 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: Maintaining ownership continuity for your organization +intro: Organizations can have more than one organization owner to avoid lapses in ownership. +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization +permissions: Organization owners can promote any member of an organization to an organization owner. +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### About maintaining ownership continuity for your organization + +{% data reusables.organizations.org-ownership-recommendation %} + +Organization owners have full administrative access to the organization. {% data reusables.organizations.new-org-permissions-more-info %} + +### Appointing an organization owner + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. Select the person or people you'd like to promote to owner. ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. Above the list of members, use the drop-down menu and click **Change role**. ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png) +6. Select a new role for the person or people, then click **Change role**. ![Radio buttons with owner and member roles and Change role button](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md new file mode 100644 index 0000000000..4bca5a2ef7 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -0,0 +1,147 @@ +--- +title: Permission levels for an organization +intro: 'After you [create an organization](/articles/creating-a-new-organization-account), you should give Owner permissions to a small group of people who will manage the organization account.' +redirect_from: + - /articles/permission-levels-for-an-organization-early-access-program/ + - /articles/permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +### Permission levels for an organization + +Organization members can have *owner*{% if currentVersion == "free-pro-team@latest" %}, *billing manager*,{% endif %} or *member* roles: + +- **Owners** have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." +{% if currentVersion == "free-pro-team@latest" %} +- **Billing managers** allow a person to manage billing settings. For more information, see "[Adding a billing manager to your organization](/articles/adding-a-billing-manager-to-your-organization)". +{% endif %} +- **Members** are the default role for everyone else. + +{% if currentVersion == "free-pro-team@latest" %} + + +| Organization action | Owners | Members | Billing managers | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:-------:|:----------------:| +| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** | | +| View and edit billing information | **X** | | **X** | +| Invite people to join the organization | **X** | | | +| Edit and cancel invitations to join the organization | **X** | | | +| Remove members from the organization | **X** | | | +| Reinstate former members to the organization | **X** | | | +| Add and remove people from **all teams** | **X** | | | +| Promote organization members to *team maintainer* | **X** | | | +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | | | +| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | +| Add collaborators to **all repositories** | **X** | | | +| Access the organization audit log | **X** | | | +| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" for details) | **X** | | | +| Verify the organization's domains (see "[Verifying your organization's domain](/articles/verifying-your-organization-s-domain)" for details) | **X** | | | +| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | | +| Delete **all teams** | **X** | | | +| Delete the organization account, including all repositories | **X** | | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | | +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | +| See all organization members and teams | **X** | **X** | | +| @mention any visible team | **X** | **X** | | +| Can be made a *team maintainer* | **X** | **X** | | +| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Manage viewing of organization dependency insights (see "[Changing the visibility of your organization's dependency insights](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **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](/organizations/managing-organization-settings/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** | | | +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | +| Manage security and analysis settings (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" for details) | **X** | | | +| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | +| [Manage a user's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | | +| Transfer repositories | **X** | | | +| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | | +| List apps in {% data variables.product.prodname_marketplace %} | **X** | | | +| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **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** | | | +| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | +| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** | | | + +{% else %} + + +| Organization action | Owners | Members | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------------------------------------------------------------------------------------------------:| +| Invite people to join the organization | **X** | | +| Edit and cancel invitations to join the organization | **X** | | +| Remove members from the organization | **X** | | | +| Reinstate former members to the organization | **X** | | | +| Add and remove people from **all teams** | **X** | | +| Promote organization members to *team maintainer* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** | +{% endif %} +| Add collaborators to **all repositories** | **X** | | +| Access the organization audit log | **X** | | +| Edit the organization's profile page (see "[About your organization's profile](/articles/about-your-organization-s-profile)" for details) | **X** | | | +| Delete **all teams** | **X** | | +| Delete the organization account, including all repositories | **X** | | +| Create teams (see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)" for details) | **X** | **X** | +| See all organization members and teams | **X** | **X** | +| @mention any visible team | **X** | **X** | +| Can be made a *team maintainer* | **X** | **X** | +| Transfer repositories | **X** | | +| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** | | +| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | +| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | | +| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | | | +| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** | | | +| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** | +| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | | +| Set a team profile picture in **all teams** (see "[Setting your team's profile picture](/articles/setting-your-team-s-profile-picture)" for details) | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| Manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | +{% endif %} +| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | | +| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | +| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [Export a list of people with access to an organization repository](/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" %} +| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | +{% endif %} +{% if currentVersion == "github-ae@latest" %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %} + +{% endif %} + +### {% data variables.product.prodname_github_app %} managers + +By default, only organization owners can manage the settings of {% data variables.product.prodname_github_app %}s owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_app %}s owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions. + +When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_app %}s owned by the organization. Дополнительные сведения см. в: + +- "[Adding GitHub App managers in your organization](/articles/adding-github-app-managers-in-your-organization)" +- "[Removing GitHub App managers from your organization](/articles/removing-github-app-managers-from-your-organization)" + +### Outside collaborators + +To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %} + +### Дополнительная литература + +- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" +- "[About teams](/articles/about-teams)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000..d6cf1b9b37 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Removing a billing manager from your organization +intro: 'If a person with the *billing manager* role no longer needs to view or change your organization''s billing information, you can remove their access to the organization.' +redirect_from: + - /articles/removing-a-billing-manager-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams + - выставление счетов +--- + +{% warning %} + +**Note:** {% 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. In the Billing managers list, next to the name of the person you want to remove, click {% octicon "x" aria-label="X symbol" %}. ![Remove billing manager](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000..a88fd11214 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,62 @@ +--- +title: About identity and access management with SAML single sign-on +intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% 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 + - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About SAML SSO + +{% data reusables.saml.dotcom-saml-explanation %} + +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. + +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 %} + +Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." + +For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." + +Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue. + +To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." + +The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's {% data variables.product.prodname_dotcom %} account, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[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)." + +If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +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 %} + +Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +### Adding members to an organization using SAML SSO + +After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." + +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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### Дополнительная литература + +- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md new file mode 100644 index 0000000000..24edf457f4 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -0,0 +1,31 @@ +--- +title: About SCIM +intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-scim + - /github/setting-up-and-managing-organizations-and-teams/about-scim +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. + +If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. + +These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% data variables.product.product_name %} API documentation. +- 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)." + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)" +- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" +- "[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)" diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000..9152445b97 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,31 @@ +--- +title: Accessing your organization if your identity provider is unavailable +intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/). + +{% note %} + +**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours. + +{% endnote %} + +1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on. ![Link to enter your recovery code](/assets/images/help/saml/saml_use_recovery_code.png) +2. In the "Recovery Code" field, type your recovery code. ![Field to enter your recovery code](/assets/images/help/saml/saml_recovery_code_entry.png) +3. Click **Verify**. ![Button to verify your recovery code](/assets/images/help/saml/saml_verify_recovery_codes.png) + +After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code. + +### Дополнительная литература + +- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000..08716ed043 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,81 @@ +--- +title: Configuring SAML single sign-on and SCIM using Okta +intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta +product: '{% data reusables.gated-features.saml-sso %}' +permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization. +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About SAML and SCIM with Okta + +You can control access to your {% data variables.product.prodname_dotcom %} organization and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP). + +SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your {% data variables.product.prodname_dotcom %} organization when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta. + +| Feature | Description | +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Push New Users | When you create a new user in Okta, the user will receive an email to join your {% data variables.product.prodname_dotcom %} organization. | +| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your {% data variables.product.prodname_dotcom %} organization. | +| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your {% data variables.product.prodname_dotcom %} organization. | +| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your {% data variables.product.prodname_dotcom %} organization. | + +### Требования + +{% data reusables.saml.use-classic-ui %} + +### Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +4. To the right of "Github Enterprise Cloud - Organization", click **Add**. ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png) + +5. In the **GitHub Organization** field, type the name of your {% data variables.product.prodname_dotcom %} organization. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`. ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png) + +6. Click **Done**. + +### Enabling and testing SAML SSO + +{% 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. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)." + +### Configuring access provisioning with SCIM in 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. Click **Authenticate with Github Enterprise Cloud - Organization**. !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) + +7. To the right of your organization's name, click **Grant**. !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) + + {% note %} + + **Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." + + {% endnote %} +1. Click **Authorize OktaOAN**. !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} + +### Дополнительная литература + +- "[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 your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000..3108e20e06 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,34 @@ +--- +title: Connecting your identity provider to your organization +intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/connecting-your-identity-provider-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Before [enabling SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) in your {% data variables.product.product_name %} organization, you'll need to connect your identity provider (IdP) to your organization. + +You can find the SAML and SCIM implementation details for your IdP in their documentation: +- 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) and [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) and [SCIM](http://developer.okta.com/standards/SCIM/) +- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [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 %} + +**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. For more information about SCIM, see "[About SCIM](/articles/about-scim)." + +{% endnote %} + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000..ce978b7b5f --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,36 @@ +--- +title: Downloading your organization's SAML single sign-on recovery codes +intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.' +redirect_from: + - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes + - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes + - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/). + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**. ![Link to view and save your recovery codes](/assets/images/help/saml/saml_recovery_codes.png) +6. Save your recovery codes by clicking **Download**, **Print**, or **Copy**. ![Buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png) + + {% note %} + + **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated. + + {% endnote %} + +7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on. + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..624d934250 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,51 @@ +--- +title: Enabling and testing SAML single sign-on for your organization +intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization. + +If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." + +{% data reusables.saml.outside-collaborators-exemption %} + +Prior to enforcing SAML SSO in your organization, ensure that you've set up your identity provider (IdP). For more information, see "[Preparing to enforce SAML single sign-on in your organization](/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. Under "SAML single sign-on", select **Enable SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/saml/saml_enable.png) + + {% note %} + + **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)." + + {% endnote %} + +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.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. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests. ![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 organization, 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) + + {% tip %} + + **Tip:** {% data reusables.saml.testing-saml-sso %} + + {% endtip %} +11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." ![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png) +12. Click **Save**. ![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png) + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..1b9213a657 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Enforcing SAML single sign-on for your organization +intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider. +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enforcing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +If you enforce SAML SSO in your organization, any members, including admins who have not authenticated via your SAML identity provider (IdP), will be removed from the organization and will receive an email notifying them about the removal. Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed. For more information on bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)." You can restore organization members once they successfully complete single sign-on. + +If your organization is owned by an enterprise account, enabling SAML for the enterprise account will override your organization-level SAML configuration. 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)." + +{% tip %} + +**Tip:** {% data reusables.saml.testing-saml-sso %} + +{% endtip %} + +1. Enable and test SAML SSO for your organization. For more information on this process, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)." +2. After you select **Require SAML SSO authentication for all members of the SAML SSO Org organization**, organization members who haven't authenticated via your IdP will be shown. If you enforce SAML SSO, these members will be removed from the organization. +3. Click **Enforce SAML SSO** to enforce SAML SSO and remove the listed organization members. + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md new file mode 100644 index 0000000000..6dc52297a3 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -0,0 +1,24 @@ +--- +title: Managing SAML single sign-on for your organization +intro: Organization administrators can manage organization members' identities and access to the organization with SAML single sign-on (SSO). +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000..6b673186f1 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,79 @@ +--- +title: Managing team synchronization for your organization +intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% 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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization +permissions: Organization owners can manage team synchronization for an organization. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### About team synchronization + +You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. + +{% 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 %} + +You can also enable team synchronization for organizations owned by 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 team synchronization + +The steps to enable team synchronization depend on the IdP you want to use. There are prerequisites to enable team synchronization that apply to every IdP. Each individual IdP has additional prerequisites. + +#### Требования + +{% data reusables.identity-and-permissions.team-sync-required-permissions %} + +You must enable SAML single sign-on for your organization and your supported IdP. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." + +You must authenticate to your organization using SAML SSO and the supported IdP. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." + +#### Enabling team synchronization for 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. Review the identity provider tenant information you want to connect to your organization, 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) + +#### Enabling team synchronization for 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. Under your organization's name, type a valid SSWS token and the URL to your Okta instance. ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) +6. Review the identity provider tenant information you want to connect to your organization, then click **Create**. ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png) + +### Disabling team synchronization + +{% 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. Under "Team synchronization", click **Disable team synchronization**. ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000..90ef50c4e9 --- /dev/null +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Preparing to enforce SAML single sign-on in your organization +intro: 'Before you enforce SAML single sign-on in your organization, you should verify your organization''s membership and configure the connection settings to your identity provider.' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +When you [enforce SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) in your organization, members that haven't authenticated via your identity provider (IdP) will be removed from the organization and will receive an email notifying them about the removal. + +Before enforcing SAML SSO in your organization, you should: + +- [Add](/articles/inviting-users-to-join-your-organization) or [remove](/articles/removing-a-member-from-your-organization) members from your organization if needed. +- If you haven't already, connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)." +- Ensure that your organization members have signed in and linked their accounts with the IdP. + +{% data reusables.saml.outside-collaborators-exemption %} + +### Дополнительная литература + +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..30f8dcea86 --- /dev/null +++ b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,32 @@ +--- +title: Converting an admin team to improved organization permissions +intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.' +redirect_from: + - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ + - /articles/converting-an-admin-team-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +You can remove the ability for members of legacy admin teams to create repositories by creating a new team for these members, ensuring that the team has necessary access to the organization's repositories, then deleting the legacy admin team. + +For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)." + +{% warning %} + +**Warnings:** +- If there are members of your legacy Admin team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories. +- To prevent the loss of private forks made by members of the legacy Admin team, you must follow steps 1-3 below before deleting the legacy Admin team. +- Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on. + +{% endwarning %} + +1. [Create a new team](/articles/creating-a-team). +2. [Add each of the members](/articles/adding-organization-members-to-a-team) of your legacy admin team to the new team. +3. [Give the new team equivalent access](/articles/managing-team-access-to-an-organization-repository) to each of the repositories the legacy team could access. +4. [Delete the legacy admin team](/articles/deleting-a-team). diff --git a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..e256db3742 --- /dev/null +++ b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,52 @@ +--- +title: Converting an Owners team to improved organization permissions +intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. The "Owner" is now an administrative role given to individual members of your organization. Members of your legacy Owners team are automatically given owner privileges.' +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +You have a few options to convert your legacy Owners team: + +- Give the team a new name that denotes the members have a special status in the organization. +- Delete the team after ensuring all members have been added to teams that grant necessary access to the organization's repositories. + +### Give the Owners team a new name + +{% tip %} + + **Note:** Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. In the team name field, choose a new name for the Owners team. Например: + - If very few members of your organization were members of the Owners team, you might name the team "Core". + - If all members of your organization were members of the Owners team so that they could [@mention teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), you might name the team "Employees". ![The team name field, with the Owners team renamed to Core](/assets/images/help/teams/owners-team-new-name.png) +6. Under the team description, click **Save and continue**. ![The Save and continue button](/assets/images/help/teams/owners-team-save-and-continue.png) +7. Optionally, [make the team *public*](/articles/changing-team-visibility). + +### Delete the legacy Owners team + +{% warning %} + +**Warning:** If there are members of your Owners team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. At the bottom of the page, review the warning and click **Delete the Owners team**. ![Link for deleting the Owners team](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/index.md new file mode 100644 index 0000000000..5a0539da2a --- /dev/null +++ b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/index.md @@ -0,0 +1,20 @@ +--- +title: Migrating to improved organization permissions +intro: 'If your organization was created after September 2015, your organization includes improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved organization permissions model.' +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000..fd5c3fb2f1 --- /dev/null +++ b/translations/ru-RU/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,44 @@ +--- +title: Migrating admin teams to improved organization permissions +intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.' +redirect_from: + - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ + - /articles/migrating-admin-teams-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - organizations + - teams +--- + +By default, all organization members can create repositories. If you restrict [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) to organization owners, and your organization was created under the legacy organization permissions structure, members of legacy admin teams will still be able to create repositories. + +Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure. + +You can remove this ability by migrating your legacy admin teams to the improved organization permissions. + +For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." + +{% warning %} + +**Warning:** If your organization has disabled [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories. + +{% endwarning %} + +### Migrating all of your organization's legacy admin teams + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +1. Review your organization's legacy admin teams, then click **Migrate all teams**. ![Migrate all teams button](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) +1. Read the information about possible permissions changes for members of these teams, then click **Migrate all teams.** ![Confirm migration button](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) + +### Migrating a single admin team + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +1. In the team description box, click **Migrate team**. ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/about-teams.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/about-teams.md new file mode 100644 index 0000000000..43cfcad539 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/about-teams.md @@ -0,0 +1,79 @@ +--- +title: About teams +intro: Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions. +redirect_from: + - /articles/about-teams + - /github/setting-up-and-managing-organizations-and-teams/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +![List of teams in an organization](/assets/images/help/teams/org-list-of-teams.png) + +Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file. + +Дополнительные сведения см. в: +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" +- "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" +- "[About code owners](/articles/about-code-owners/)" + +![Image of a team mention](/assets/images/help/teams/team-mention.png) + +{% if enterpriseServerVersions contains currentVersion %} + +You can also use LDAP Sync to synchronize {% data variables.product.product_location %} team members and team roles against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.product_location %}. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)." + +{% endif %} + +{% data reusables.organizations.team-synchronization %} + +### Team visibility + +{% data reusables.organizations.types-of-team-visibility %} + +### Team pages + +Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page. + +Organization members can create and participate in discussions with the team. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." + +![Team page listing team members and discussions](/assets/images/help/organizations/team-page-discussions-tab.png) + +### Nested teams + +You can reflect your group or company's hierarchy within your {% data variables.product.product_name %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. + +Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people. + +For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification. + +![Teams page with a parent team and child teams](/assets/images/help/teams/nested-teams-eng-example.png) + +To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team. + +![Parent team page with all members of child teams](/assets/images/help/teams/team-and-subteam-members.png) + +You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)." + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +### Preparing to nest teams in your organization + +If your organization already has existing teams, you should audit each team's repository access permissions before you nest teams above or below it. You should also consider the new structure you'd like to implement for your organization. + +At the top of the team hierarchy, you should give parent teams repository access permissions that are safe for every member of the parent team and its child teams. As you move toward the bottom of the hierarchy, you can grant child teams additional, more granular access to more sensitive repositories. + +1. Remove all members from existing teams +2. Audit and adjust each team's repository access permissions and give each team a parent +3. Create any new teams you'd like to, choose a parent for each new team, and give them repository access +4. Add people directly to teams + +### Дополнительная литература + +- "[Creating a team](/articles/creating-a-team)" +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000..373ec5ec16 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,32 @@ +--- +title: Adding organization members to a team +intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% if currentVersion == "free-pro-team@latest" %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.' +redirect_from: + - /articles/adding-organization-members-to-a-team-early-access-program/ + - /articles/adding-organization-members-to-a-team + - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. Above the list of team members, click **Add a member**. ![Add member button](/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 %} + +### Дополнительная литература + +- "[About teams](/articles/about-teams)" +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/changing-team-visibility.md new file mode 100644 index 0000000000..d8450c6b27 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/changing-team-visibility.md @@ -0,0 +1,29 @@ +--- +title: Changing team visibility +intro: Team maintainers and organization owners can determine whether a team is *visible* or *secret*. +redirect_from: + - /articles/changing-team-visibility + - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.types-of-team-visibility %} + +{% tip %} + +**Tip:** If a team has [child or parent teams](/articles/about-teams), you cannot make it a secret team. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +3. Select the team or teams whose visibility you'd like to change. ![List of teams with two teams selected](/assets/images/help/teams/list-of-teams-selected.png) +4. Above the list of teams, use the drop-down menu and click **Change visibility**. ![Drop-down menu with option to change team visibility](/assets/images/help/teams/team-bulk-management-options.png) +5. Choose whether to make the team or teams visible or secret, then click **Change visibility**. ![Radio buttons for making a team visible or secret and Change visibility button](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/creating-a-team.md new file mode 100644 index 0000000000..42c1ec7fc0 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -0,0 +1,38 @@ +--- +title: Creating a team +intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people. +redirect_from: + - /articles/creating-a-team-early-access-program/ + - /articles/creating-a-team + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/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. Optionally, if your organization or enterprise account uses team synchronization, to connect an identity provider group to your team, use the "Identity Provider Groups" drop-down menu, and select up to 5 identity provider groups. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +{% endif %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} +9. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository). + +### Дополнительная литература + +- "[About teams](/articles/about-teams)" +- "[Changing team visibility](/articles/changing-team-visibility)" +- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/deleting-a-team.md new file mode 100644 index 0000000000..8dcd1238cb --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/deleting-a-team.md @@ -0,0 +1,27 @@ +--- +title: Deleting a team +intro: Organization owners can delete teams at any time from the team's settings page. +redirect_from: + - /articles/deleting-a-team + - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% tip %} + +**Tip:** Only organization owners can delete parent teams. For more information, see "[About teams](/articles/about-teams)." + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. Select the team or teams you'd like to delete. ![List of teams with two teams selected](/assets/images/help/teams/list-of-teams-selected.png) +5. Above the list of teams, use the drop-down menu and click **Delete**. ![Drop-down menu with option to change team visibility](/assets/images/help/teams/team-bulk-management-options.png) +6. Review the team or teams that will be deleted, then click **I understand, delete teams**. ![List of teams that will be deleted and Delete teams button](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000..bef774e006 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,23 @@ +--- +title: Disabling team discussions for your organization +intro: Organization owners can choose to disable or enable team discussions across the organization. +redirect_from: + - /articles/disabling-team-discussions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.team-discussions-default %} For more information on team discussions, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +5. Under "Team discussions", unselect **Enable team discussions for this organization**. ![Checkbox to enable or disable team discussions for an organization](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) +6. Click **Save**. diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/index.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/index.md new file mode 100644 index 0000000000..0efd481006 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/index.md @@ -0,0 +1,38 @@ +--- +title: Organizing members into teams +intro: You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions. +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 + - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000..7bb33d871c --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,51 @@ +--- +title: Managing code review assignment for your team +intro: Code review assignments clearly indicate which members of a team are expected to submit a review for a pull request. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - organizations + - teams +--- + +Team maintainers and organization owners can configure code review assignments. + +### About code review assignments + +By using code review assignments, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. Code review assignments allow you to decide whether the whole team or just a subset of team members are notified when a team is requested for review. + +When code owners are automatically requested for review, the team is still removed and replaced with individuals. The individual approvals don't satisfy the requirement for code owner approval in a protected branch. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." + +### Routing algorithms + +Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. + +The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. + +The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period. + +### Configuring code review assignment +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. In the left sidebar, click **Code review assignment** ![Code review assignment button](/assets/images/help/teams/review-assignment-button.png) +6. Select **Enable auto assignment**. ![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png) +7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request. ![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png) +8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)." ![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png) +9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip. ![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png) +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png) +11. Click **Save changes**. + +### Disabling code review assignment +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Select **Enable auto assignment** to remove the checkmark. ![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png) +6. Click **Save changes**. diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000..dceb54dec9 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,69 @@ +--- +title: Managing scheduled reminders for your team +intro: You can get reminders in Slack when your team has pull requests waiting for review. +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +### About scheduled reminders for teams + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +Team maintainers and organization owners can set scheduled reminders for any pull requests that a team has been requested to review. Before you can create a scheduled reminder for your team, an organization owner must authorize your Slack workspace. For more information, see "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)." + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### Creating a scheduled reminder for a team +{% 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 %} +![Scheduled reminders button](/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 %} + +### Managing a scheduled reminder for a team +{% 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 %} +![Scheduled reminders button](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Deleting a scheduled reminder for a team +{% 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 %} +![Scheduled reminders button](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.delete %} + +### Дополнительная литература + +- "[Managing scheduled reminders for your organization](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)" +- "[Managing your scheduled reminders](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000..b866e87f5e --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,42 @@ +--- +title: Moving a team in your organization’s hierarchy +intro: 'Team maintainers and organization owners can nest a team under a parent team, or change or remove a nested team''s parent.' +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 + - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Organization owners can change the parent of any team. Team maintainers can change a team's parent if they are maintainers in both the child team and the parent team. Team maintainers without maintainer permissions in the child team can request to add a parent or child team. For more information, see "[Requesting to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)" and "[Requesting to add a child team](/articles/requesting-to-add-a-child-team)." + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% tip %} + +**Советы:** +- You cannot change a team's parent to a secret team. For more information, see "[About teams](/articles/about-teams)." +- You cannot nest a parent team beneath one of its child teams. + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. In the list of teams, click the name of the team whose parent you'd like to change. ![List of the organization's teams](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Use the drop-down menu to choose a parent team, or to remove an existing parent, select **Clear selected value**. ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png) +7. Click **Update**. +{% data reusables.repositories.changed-repository-access-permissions %} +9. Click **Confirm new parent team**. ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png) + +### Дополнительная литература + +- "[About teams](/articles/about-teams)" diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000..9af60f3276 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,23 @@ +--- +title: Removing organization members from a team +intro: 'People with *owner* or *team maintainer* permissions can remove team members from a team. This may be necessary if a person no longer needs access to a repository the team grants, or if a person is no longer focused on a team''s projects.' +redirect_from: + - /articles/removing-organization-members-from-a-team-early-access-program/ + - /articles/removing-organization-members-from-a-team + - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% 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. Select the person or people you'd like to remove. ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png) +5. Above the list of team members, use the drop-down menu and click **Remove from team**. ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/renaming-a-team.md new file mode 100644 index 0000000000..b62593f46d --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/renaming-a-team.md @@ -0,0 +1,21 @@ +--- +title: Renaming a team +intro: Team maintainers and organization owners can edit the name and description of a team. +redirect_from: + - /articles/renaming-a-team + - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Type a new name or description for the team. ![Fields for team name and description](/assets/images/help/teams/team-name-description.png) +6. Click **Update**. diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000..a9884a1378 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,36 @@ +--- +title: Requesting to add a child team +intro: 'If you have maintainer permissions in a team, you can request to nest an existing team under your team in your organization’s hierarchy.' +redirect_from: + - /articles/requesting-to-add-a-child-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +When you request to add a team as a child, a request is sent to the maintainers of the child team. Once a maintainer of the child team approves your request, the child team is nested under the parent team in your organization's hierarchy. + +If you're an organization owner or you have team maintainer permissions in both the child team and the parent team, you can add the child team without requesting approval or change the child team's parent from the child team's settings page. For more information, see "[Moving a team in your organization's hierarchy](/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. In the list of teams, click the name of the team where you'd like to add the child team. ![List of the organization's teams](/assets/images/help/teams/click-team-name.png) +5. At the top of the team page, click {% octicon "people" aria-label="The people icon" %} **Teams**. ![Teams tab on a team page](/assets/images/help/teams/team-teams-tab.png) +6. Click **Add a team**. ![Add a team button on a team page](/assets/images/help/teams/add-a-team.png) +7. Type the name of the team you'd like to add as a child team, and select it from the drop-down list. ![Text box to type and drop-down menu to select the name of the child team](/assets/images/help/teams/type-child-team-name.png) +{% data reusables.repositories.changed-repository-access-permissions %} +9. Click **Confirm changes** to send a request to add the child team. ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png) + +### Дополнительная литература + +- "[About teams](/articles/about-teams)" +- "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Requesting to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)" diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000..de0edcabef --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,36 @@ +--- +title: Requesting to add or change a parent team +intro: 'If you have maintainer permissions in a team, you can request to nest your team under a parent team in your organization''s hierarchy.' +redirect_from: + - /articles/requesting-to-add-or-change-a-parent-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +When you request to add or change your team's parent, a request is sent to the maintainers of the parent team. When a maintainer of the new parent team approves your request, your team is nested as a child team under the parent team in your organization's hierarchy. + +If you're an organization owner or you have team maintainer permissions in the child team and the parent team, you can add the parent team without requesting approval or change your team's parent from your team's settings page. For more information, see "[Moving a team in your organization's hierarchy](/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. In the list of teams, click the name of the team you'd like to nest under a parent. ![List of the organization's teams](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. Under "Parent team", use the "Select parent team" drop-down menu and click the name of the new parent team. ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png) +7. Click **Save changes**. +{% data reusables.repositories.changed-repository-access-permissions %} +9. Click **Confirm changes** to send a request to add or change your team's parent. ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png) + +### Дополнительная литература + +- "[About teams](/articles/about-teams)" +- "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)" +- "[Requesting to add a child team](/articles/requesting-to-add-a-child-team)" diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000..03cac455eb --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,24 @@ +--- +title: Setting your team's profile picture +intro: 'Team maintainers and organization owners can set a profile picture for a team, which is displayed on the team''s page.' +redirect_from: + - /articles/setting-your-team-s-profile-picture + - /articles/setting-your-teams-profile-picture + - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +Unless you set a profile picture for a team, the team profile picture will match the organization's profile picture. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. Click **Upload new picture** and select your desired profile picture. ![Upload new picture](/assets/images/help/teams/org-team-profile-picture-upload.png) +6. Click and drag to crop the image as needed, then click **Set new team avatar**. ![Set new team avatar](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000..1f5ea80169 --- /dev/null +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,99 @@ +--- +title: Synchronizing a team with an identity provider group +intro: 'You can synchronize a {% data variables.product.product_name %} team with an identity provider (IdP) group to automatically add and remove team members.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group +product: '{% data reusables.gated-features.team-synchronization %}' +permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - organizations + - teams +--- + +{% data reusables.gated-features.okta-team-sync %} + +### About team synchronization + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% if currentVersion == "free-pro-team@latest" %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif currentVersion == "github-ae@latest" %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. + +{% if currentVersion == "free-pro-team@latest" %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} + +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 %}{% if currentVersion == "free-pro-team@latest" %} or using the API{% endif %}. + +{% if currentVersion == "free-pro-team@latest" %} +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)." +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs. +{% endif %} + +Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)." + +To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." + +{% if currentVersion == "free-pro-team@latest" %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### Requirements for members of synchronized teams + +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.product_name %} only if: +- The person is a member of the organization on {% data variables.product.product_name %}. +- The person has already logged in with their user account on {% data variables.product.product_name %} 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.product_name %} 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](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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)" 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 "[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)." + +{% endif %} + +### Требования + +{% if currentVersion == "free-pro-team@latest" %} +Before you can connect a {% data variables.product.product_name %} 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](/organizations/managing-saml-single-sign-on-for-your-organization/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. + +You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." + +{% elsif currentVersion == "github-ae@latest" %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." + +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. For more information, see [Configure automatic user provisioning to GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) in the Microsoft Docs. +{% endif %} + +### Connecting an IdP group to a team + +When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% if currentVersion == "github-ae@latest" %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. Click **Save changes**. + +### Disconnecting an IdP group from a team + +If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% if currentVersion == "github-ae@latest" %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Click **Save changes**. diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000..9b32fc01ec --- /dev/null +++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -0,0 +1,60 @@ +--- +title: About OAuth App access restrictions +intro: 'Organizations can choose which {% data variables.product.prodname_oauth_app %}s have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.' +redirect_from: + - /articles/about-third-party-application-restrictions/ + - /articles/about-oauth-app-access-restrictions + - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_app %}s they'd like to use, and organization owners receive a notification of pending requests. + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% tip %} + +**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources. + +{% endtip %} + +### Setting up {% data variables.product.prodname_oauth_app %} access restrictions + +When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time: + +- **Applications that are owned by the organization** are automatically given access to the organization's resources. +- **{% data variables.product.prodname_oauth_app %}s** immediately lose access to the organization's resources. +- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys). +- **SSH keys created by {% data variables.product.prodname_oauth_app %}s during or after February 2014** immediately lose access to the organization's resources. +- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_app %}s. +- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_app %}s. In addition, there are no privileged create, update, or delete actions on public organization resources. +- **Hooks created by users and hooks created before May 2014** will not be affected. +- **Private forks of organization-owned repositories** are subject to the organization's access restrictions. + +### Resolving SSH access failures + +When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place. + +### Webhooks + +When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching. + +When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted). + +### Re-enabling access restrictions + +If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources. + +### Дополнительная литература + +- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" +- "[Approving {% data variables.product.prodname_oauth_app %}s for your organization](/articles/approving-oauth-apps-for-your-organization)" +- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)" +- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" +- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" +- "[Requesting organization approval for {% data variables.product.prodname_oauth_app %}s](/articles/requesting-organization-approval-for-oauth-apps)" +- "[Authorizing {% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps)" diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000..9757a2f210 --- /dev/null +++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Approving OAuth Apps for your organization +intro: 'When an organization member requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.' +redirect_from: + - /articles/approving-third-party-applications-for-your-organization/ + - /articles/approving-oauth-apps-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members must [request approval](/articles/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Next to the application you'd like to approve, click **Review**. ![Review request link](/assets/images/help/settings/settings-third-party-approve-review.png) +6. After you review the information about the requested application, click **Grant access**. ![Grant access button](/assets/images/help/settings/settings-third-party-approve-grant.png) + +### Дополнительная литература + +- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000..c66ed142f3 --- /dev/null +++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,20 @@ +--- +title: Denying access to a previously approved OAuth App for your organization +intro: 'If an organization no longer requires a previously authorized {% data variables.product.prodname_oauth_app %}, owners can remove the application''s access to the organization''s resources.' +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 + - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="The edit icon" %}. ![Edit icon](/assets/images/help/settings/settings-third-party-deny-edit.png) +6. Click **Deny access**. ![Deny confirmation button](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..5e5847e2c7 --- /dev/null +++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: Disabling OAuth App access restrictions for your organization +intro: 'Organization owners can disable restrictions on the {% data variables.product.prodname_oauth_app %}s that have access to the organization''s resources.' +redirect_from: + - /articles/disabling-third-party-application-restrictions-for-your-organization/ + - /articles/disabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% danger %} + +**Warning**: When you disable {% data variables.product.prodname_oauth_app %} access restrictions for your organization, any organization member will automatically authorize {% data variables.product.prodname_oauth_app %} access to the organization's private resources when they approve an application for use in their personal account settings. + +{% enddanger %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Click **Remove restrictions**. ![Remove restrictions button](/assets/images/help/settings/settings-third-party-remove-restrictions.png) +6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**. ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..857938eae1 --- /dev/null +++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: Enabling OAuth App access restrictions for your organization +intro: 'Organization owners can enable {% data variables.product.prodname_oauth_app %} access restrictions to prevent untrusted apps from accessing the organization''s resources while allowing organization members to use {% data variables.product.prodname_oauth_app %}s for their personal accounts.' +redirect_from: + - /articles/enabling-third-party-application-restrictions-for-your-organization/ + - /articles/enabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% warning %} + +**Warnings**: +- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_app %}s and SSH keys. For more information, see "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)." +- Once you've set up {% data variables.product.prodname_oauth_app %} access restrictions, make sure to re-authorize any {% data variables.product.prodname_oauth_app %} that require access to the organization's private data on an ongoing basis. All organization members will need to create new SSH keys, and the organization will need to create new deploy keys as needed. +- When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, applications can use an OAuth token to access information about {% data variables.product.prodname_marketplace %} transactions. + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. Under "Third-party application access policy," click **Setup application access restrictions**. ![Set up restrictions button](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) +6. After you review the information about third-party access restrictions, click **Restrict third-party application access**. ![Restriction confirmation button](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/index.md new file mode 100644 index 0000000000..9cf976f93a --- /dev/null +++ b/translations/ru-RU/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -0,0 +1,19 @@ +--- +title: Restricting access to your organization's data +intro: '{% data variables.product.prodname_oauth_app %} access restrictions allow organization owners to restrict an untrusted app''s access to the organization''s data. Organization members can then use {% data variables.product.prodname_oauth_app %}s for their personal user accounts while keeping organization data safe.' +redirect_from: + - /articles/restricting-access-to-your-organization-s-data + - /articles/restricting-access-to-your-organizations-data + - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data +versions: + free-pro-team: '*' +topics: + - organizations + - teams +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/packages/index.md b/translations/ru-RU/content/packages/index.md index 56deb1e548..964974e6c9 100644 --- a/translations/ru-RU/content/packages/index.md +++ b/translations/ru-RU/content/packages/index.md @@ -20,8 +20,8 @@ featuredLinks: - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - label: 'packages' - prefix: 'Packages: ' + label: 'пакеты' + prefix: 'Packages:' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry diff --git a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..b41945b93a --- /dev/null +++ b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -0,0 +1,68 @@ +--- +title: About custom domains and GitHub Pages +intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.' +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 + - /github/working-with-github-pages/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +### Supported custom domains + +{% data variables.product.prodname_pages %} works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)." + +| Supported custom domain type | Пример | +| ---------------------------- | ------------------ | +| `www` subdomain | `www.example.com` | +| Custom subdomain | `blog.example.com` | +| Apex domain | `example.com` | + +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." + +We recommend always using a `www` subdomain, even if you also use an apex domain. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. 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)." + +After you configure a custom domain for a user or organization site, the custom domain will replace the `.github.io` or `.github.io` portion of the URL for any project sites owned by the account that do not have a custom domain configured. For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`. + +### Using a subdomain for your {% data variables.product.prodname_pages %} site + +A subdomain is the part of a URL before the root domain. You can configure your subdomain as `www` or as a distinct section of your site, like `blog.example.com`. + +Subdomains are configured with a `CNAME` record through your DNS provider. 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#configuring-a-subdomain)." + +#### `www` subdomains + +A `www` subdomain is the most commonly used type of subdomain. For example, `www.example.com` includes a `www` subdomain. + +`www` subdomains are the most stable type of custom domain because `www` subdomains are not affected by changes to the IP addresses of {% data variables.product.product_name %}'s servers. + +#### Custom subdomains + +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called `blog.example.com` and customize that section independently from `www.example.com`. + +### Using an apex domain for your {% data variables.product.prodname_pages %} site + +An apex domain is a custom domain that does not contain a subdomain, such as `example.com`. Apex domains are also known as base, bare, naked, root apex, or zone apex domains. + +An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through your DNS provider. 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#configuring-an-apex-domain)." + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." + +### Updating custom domains when your {% data variables.product.prodname_pages %} site is disabled + +If your {% data variables.product.prodname_pages %} site is disabled but has a custom domain set up, you should immediately update or remove your DNS records with your DNS provider to avoid the risk of a domain takeover. Having a custom domain configured with your DNS provider while your site is disabled could result in someone else hosting a site on one of your subdomains. 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)." + +There are a couple of reasons your site might be automatically disabled. + +- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[Downgrading your {% data variables.product.prodname_dotcom %} billing plan](/articles/downgrading-your-github-billing-plan)." +- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[Transferring a repository](/articles/transferring-a-repository)." + +### Дополнительная литература + +- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md new file mode 100644 index 0000000000..9e748a4882 --- /dev/null +++ b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -0,0 +1,23 @@ +--- +title: Configuring a custom domain for your GitHub Pages site +intro: 'You can customize the domain name of your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000..577f9efbde --- /dev/null +++ b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,121 @@ +--- +title: Managing a custom domain for your GitHub Pages site +intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.' +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 + - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site. + +### About custom domain configuration + +Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains. + +{% windows %} + +The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/). + +{% endwindows %} + +{% note %} + +**Note:** DNS changes can take up to 24 hours to propagate. + +{% endnote %} + +### Configuring a subdomain + +To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings, which will create a CNAME file in your site’s repository. After that, configure a CNAME record with your DNS provider. + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. ![Save custom domain button](/assets/images/help/pages/save-custom-subdomain.png) +5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `.github.io`. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `.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 %} + +{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %} +{% data reusables.command_line.open_the_multi_os_terminal %} +6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain. +```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 %} + +### Configuring an apex domain + +To set up an apex domain, such as `example.com`, you must configure a _CNAME_ file in your {% data variables.product.prodname_pages %} repository and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider. + +{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)." + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source. ![Save custom domain button](/assets/images/help/pages/save-custom-apex-domain.png) +5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. {% data reusables.pages.contact-dns-provider %} + - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %} + - To create `A` records, point your apex domain to the IP addresses for {% 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. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above. + ```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 %} + +### Configuring an apex domain and the `www` subdomain variant + +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. + +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." + +After you configure the apex domain, you must to configure a CNAME record with your DNS provider. + +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. +```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 +``` +### Removing a custom domain + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain," click **Remove**. ![Save custom domain button](/assets/images/help/pages/remove-custom-domain.png) + +### Дополнительная литература + +- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..3b7ee96541 --- /dev/null +++ b/translations/ru-RU/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,65 @@ +--- +title: Troubleshooting custom domains and GitHub Pages +intro: 'You can check for common errors to resolve issues with custom domains or HTTPS for your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +### _CNAME_ errors + +Custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. 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)." + +For your site to render at the correct domain, make sure your _CNAME_ file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the _CNAME_ file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to {% data variables.product.product_name %}, make sure to pull the commit that added the _CNAME_ file to your local repository first, so the file will be included in the build. + +Then, make sure the _CNAME_ file is formatted correctly. + +- The _CNAME_ filename must be all uppercase. +- The _CNAME_ file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider. +- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`. +- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository. + +### DNS misconfiguration + +If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider. + +You can also test whether your custom domain's DNS records are configured correctly. 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)." + +### Custom domain names that are unsupported + +If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names. + +Make sure your site does not: +- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`. +- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`. +- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`. + + The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)." + +{% data reusables.pages.wildcard-dns-warning %} + +For a list of supported custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)." + +### HTTPS errors + +{% data variables.product.prodname_pages %} sites using custom domains that are correctly configured with _CNAME_, `ALIAS`, `ANAME`, or `A` DNS records can be accessed over HTTPS. For more information, see "[Securing your {% data variables.product.prodname_pages %} site with HTTPS](/articles/securing-your-github-pages-site-with-https)." + +It can take up to an hour for your site to become available over HTTPS after you configure your custom domain. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. 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)." + +If you're using Certification Authority Authorization (CAA) records, at least one CAA record must exist with the value `letsencrypt.org` for your site to be accessible over HTTPS. For more information, see "[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)" in the Let's Encrypt documentation. + +### URL formatting on Linux + +If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.product_name %} username to remove non-alphanumeric characters. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username/)." + +### Browser cache + +If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new URL. For more information on clearing your cache, see your browser's documentation. diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000..c28b6b06e4 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -0,0 +1,150 @@ +--- +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/ + - /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 + - /github/working-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### About {% 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. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +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@3.0" %} +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." +{% endif %} + +### Types of {% data variables.product.prodname_pages %} sites + +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 %} + +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" %} +If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +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 %}. 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 %}. + +| 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///` + +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" %} +{% note %} + +**Note:** Repositories using the legacy `.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://.github.com` to `http(s)://.github.io`. If both a `.github.com` and `.github.io` repository exist, only the `.github.io` repository will be published. + +{% endnote %} +{% endif %} + +### Publishing sources for {% data variables.product.prodname_pages %} sites + +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" %} + +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. + +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`. 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 %} + +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. + +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. + +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`. 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 %} + +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 %} 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 %} 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 %} does not support server-side languages such as PHP, Ruby, or Python. + +### Guidelines for using {% data variables.product.prodname_pages %} + +{% if currentVersion == "free-pro-team@latest" %} +- {% 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 %} +- 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 %} 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 %} + - 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. + +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 %} 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). + +In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. For a list of prohibited uses, see "[{% data variables.product.prodname_dotcom %}'s Additional Product Terms for {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)." +{% endif %} + +### MIME types on {% data variables.product.prodname_pages %} + +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). + +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). + +### Дополнительная литература + +- [{% 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/ru-RU/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000..b756edeb04 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,46 @@ +--- +title: Adding a theme to your GitHub Pages site with the theme chooser +intro: 'You can add a theme to your {% data variables.product.prodname_pages %} site to customize your site’s look and feel.' +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site. + +### About the theme chooser + +The theme chooser adds a Jekyll theme to your repository. For more information about Jekyll, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." + +How the theme chooser works depends on whether your repository is public or private. + - If {% data variables.product.prodname_pages %} is already enabled for your repository, the theme chooser will add your theme to the current publishing source. + - If your repository is public and {% data variables.product.prodname_pages %} is disabled for your repository, using the theme chooser will enable {% data variables.product.prodname_pages %} and configure the default branch as your publishing source. + - If your repository is private and {% data variables.product.prodname_pages %} is disabled for your repository, you must enable {% data variables.product.prodname_pages %} by configuring a publishing source before you can use the theme chooser. + +For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." + +If you manually added a Jekyll theme to your repository in the past, those files may be applied even after you use the theme chooser. To avoid conflicts, remove all manually added theme folders and files before using the theme chooser. 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)." + +### Adding a theme with the theme chooser + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}," click **Choose a theme** or **Change theme**. ![Choose a theme button](/assets/images/help/pages/choose-a-theme.png) +4. On the top of the page, click the theme you want, then click **Select theme**. ![Theme options and Select theme button](/assets/images/help/pages/select-theme.png) +5. You may be prompted to edit your site's *README.md* file. + - To edit the file later, click **Cancel**. ![Cancel link when editing a file](/assets/images/help/pages/cancel-edit.png) + - To edit the file now, see "[Editing files in your repository](/articles/editing-files-in-your-repository/)." + +Your chosen theme will automatically apply to markdown files in your repository. To apply your theme to HTML files in your repository, you need to add YAML front matter that specifies a layout to each file. For more information, see "[Front Matter](https://jekyllrb.com/docs/front-matter/)" on the Jekyll site. + +### Дополнительная литература + +- [Themes](https://jekyllrb.com/docs/themes/) on the Jekyll site diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..d765eb4e9f --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: Changing the visibility of your GitHub Pages site +intro: 'You can manage access control for your project site by publishing the site publicly or privately.' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site. +redirect_from: + - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site +--- + +### About access control for {% data variables.product.prodname_pages %} sites + +If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." + +Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published: + +- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS. +- We use a unique subdomain for the private page to ensure that other repositories in your organization cannot publish content on the same origin as the private page. This protects your private page from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain. + +You can see your site's unique subdomain in the pages tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator. + +To use a shorter and more memorable domain for your private {% data variables.product.prodname_pages %} site, you can configure a custom domain. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site)." + +### Changing the visibility of your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) +4. To see your published site, under "{% data variables.product.prodname_pages %}", click your site's URL. ![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000..8fc3589bbb --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,38 @@ +--- +title: Configuring a publishing source for your GitHub Pages site +intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your{% if currentVersion ver_lt "enterprise-server@3.0" %} project{% endif %} site from a different branch or folder.' +redirect_from: + - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-your-github-pages-site + - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can configure a publishing source for a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." + +### Choosing a publishing source + +Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} 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 %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source. ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +4. Optionally, use the drop-down menu to select a folder for your publishing source. ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. Click **Save**. ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %} +3. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select a publishing source. ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +{% endif %} + +### Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site + +{% 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. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)." diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000..b039f65f75 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Creating a custom 404 page for your GitHub Pages site +intro: You can display a custom 404 error page when people try to access nonexistent pages on your site. +redirect_from: + - /articles/custom-404-pages/ + - /articles/creating-a-custom-404-page-for-your-github-pages-site + - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +{% data reusables.files.add-file %} +3. In the file name field, type `404.html` or `404.md`. ![File name field](/assets/images/help/pages/404-file-name.png) +4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file: + ```yaml + --- + permalink: /404.html + --- + ``` +5. Below the YAML front matter, if present, add the content you want to display on your 404 page. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_new_file %} + +### Дополнительная литература + +- [Front matter](http://jekyllrb.com/docs/frontmatter) in the Jekyll documentation diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000..4f9af63d06 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,63 @@ +--- +title: Creating a GitHub Pages site +intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.' +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 + - /github/working-with-github-pages/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Creating a repository for your site + +{% data reusables.pages.new-or-existing-repo %} + +{% 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 %} + +### Creating your site + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.decide-publishing-source %} +3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source. +4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site. +{% data reusables.pages.configure-publishing-source %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Дальнейшие шаги + +You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. 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.html`. + +You can also add a theme to customize your site’s look and feel. 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 %}." + +To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." + +### Дополнительная литература + +- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" +- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)" +- "[Creating new files](/articles/creating-new-files)" diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/index.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/index.md new file mode 100644 index 0000000000..6dcbaf8ab7 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/index.md @@ -0,0 +1,26 @@ +--- +title: Getting started with GitHub Pages +intro: 'You can set up a basic {% data variables.product.prodname_pages %} site for yourself, your organization, or your project.' +redirect_from: + - /categories/github-pages-basics + - /articles/additional-customizations-for-github-pages/ + - /articles/getting-started-with-github-pages + - /github/working-with-github-pages/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 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 /changing-the-visibility-of-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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000..cb9bf8e593 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,55 @@ +--- +title: Securing your GitHub Pages site with HTTPS +intro: 'HTTPS adds a layer of encryption that prevents others from snooping on or tampering with traffic to your site. You can enforce HTTPS for your {% data variables.product.prodname_pages %} site to transparently redirect all HTTP requests to HTTPS.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/securing-your-github-pages-site-with-https + - /github/working-with-github-pages/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +topics: + - pages +--- + +People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site. + +### About HTTPS and {% data variables.product.prodname_pages %} + +All {% data variables.product.prodname_pages %} sites, including sites that are correctly configured with a custom domain, support HTTPS and HTTPS enforcement. For more information about custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" and "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)." + +{% data reusables.pages.no_sensitive_data_pages %} + +{% data reusables.pages.private_pages_are_public_warning %} + +### Enforcing HTTPS for your {% data variables.product.prodname_pages %} site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. Under "{% data variables.product.prodname_pages %}," select **Enforce HTTPS**. ![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png) + +### Resolving problems with mixed content + +If you enable HTTPS for your {% data variables.product.prodname_pages %} site but your site's HTML still references images, CSS, or JavaScript over HTTP, then your site is serving *mixed content*. Serving mixed content may make your site less secure and cause trouble loading assets. + +To remove your site's mixed content, make sure all your assets are served over HTTPS by changing `http://` to `https://` in your site's HTML. + +Assets are commonly found in the following locations: +- If your site uses Jekyll, your HTML files will probably be found in the *_layouts* folder. +- CSS is usually found in the `` section of your HTML file. +- JavaScript is usually found in the `` section or just before the closing `` tag. +- Images are often found in the `` section. + +{% tip %} + +**Tip:** If you can't find your assets in your site's source files, try searching your site's source files for `http` in your text editor or on {% data variables.product.product_name %}. + +{% endtip %} + +#### Examples of assets referenced in an HTML file + +| Asset type | HTTP | HTTPS | +|:----------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:| +| CSS | `` | `` | +| JavaScript | `` | `` | +| Image | `Logo` | `Logo` | diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000..26904123a8 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: Unpublishing a GitHub Pages site +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' +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 + - /github/working-with-github-pages/unpublishing-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: 'People with admin or maintainer permissions for a repository can unpublish a {% data variables.product.prodname_pages %} site.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### Unpublishing a project site + +{% data reusables.repositories.navigate-to-repo %} +2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)." +3. If the `gh-pages` branch was your publishing source, {% if currentVersion == "free-pro-team@latest" %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.** ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} + +### Unpublishing a user or organization site + +{% data reusables.repositories.navigate-to-repo %} +2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)." +{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000..db370d1466 --- /dev/null +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,24 @@ +--- +title: Using submodules with GitHub Pages +intro: 'You can use submodules with {% data variables.product.prodname_pages %} to include other projects in your site''s code.' +redirect_from: + - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-github-pages + - /github/working-with-github-pages/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - pages +--- + +If the repository for your {% data variables.product.prodname_pages %} site contains submodules, their contents will automatically be pulled in when your site is built. + +You can only use submodules that point to public repositories, because the {% data variables.product.prodname_pages %} server cannot access private repositories. + +Use the `https://` read-only URL for your submodules, including nested submodules. You can make this change in your _.gitmodules_ file. + +### Дополнительная литература + +- "[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" from the _Pro Git_ book +- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/ru-RU/content/pages/index.md b/translations/ru-RU/content/pages/index.md new file mode 100644 index 0000000000..c3be861bf5 --- /dev/null +++ b/translations/ru-RU/content/pages/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages Documentation +shortTitle: Страницы GitHub +intro: 'You can create a website directly from a {% data variables.product.product_name %} repository.' +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 + - /github/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% link_with_intro /getting-started-with-github-pages %} +{% link_with_intro /setting-up-a-github-pages-site-with-jekyll %} +{% link_with_intro /configuring-a-custom-domain-for-your-github-pages-site %} \ No newline at end of file diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000..e9ada225c6 --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -0,0 +1,131 @@ +--- +title: About GitHub Pages and Jekyll +intro: 'Jekyll is a static site generator with built-in support for {% 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 + - /github/working-with-github-pages/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### About Jekyll + +Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. Jekyll takes Markdown and HTML files and creates a complete static website based on your choice of layouts. Jekyll supports Markdown and Liquid, a templating language that loads dynamic content on your site. For more information, see [Jekyll](https://jekyllrb.com/). + +Jekyll is not officially supported for Windows. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation. + +We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)." + +### Configuring Jekyll in your {% data variables.product.prodname_pages %} site + +You can configure most Jekyll settings, such as your site's theme and plugins, by editing your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. + +Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites. + +```yaml +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 +``` + +By default, Jekyll doesn't build files or folders that: +- are located in a folder called `/node_modules` or `/vendor` +- start with `_`, `.`, or `#` +- end with `~` +- are excluded by the `exclude` setting in your configuration file + +If you want Jekyll to process any of these files, you can use the `includes` setting in your configuration file. + +### Front matter + +{% data reusables.pages.about-front-matter %} + +You can add `site.github` to a post or page to add any repository references metadata to your site. For more information, see "[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)" in the Jekyll Metadata documentation. + +### Themes + +{% data reusables.pages.add-jekyll-theme %} For more information, see "[Themes](https://jekyllrb.com/docs/themes/)" in the Jekyll documentation. + +{% if currentVersion == "free-pro-team@latest" %} +You can add a supported theme to your site on {% data variables.product.prodname_dotcom %}. For more information, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and "[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)." + +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)." + +You can override any of your theme's defaults by editing the theme's files. For more information, see your theme's documentation and "[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" in the Jekyll documentation. + +### Plugins + +You can download or create Jekyll plugins to extend the functionality of Jekyll for your site. For example, the [jemoji](https://github.com/jekyll/jemoji) plugin lets you use {% data variables.product.prodname_dotcom %}-flavored emoji in any page on your site the same way you would on {% data variables.product.prodname_dotcom %}. For more information, see "[Plugins](https://jekyllrb.com/docs/plugins/)" in the Jekyll documentation. + +{% data variables.product.prodname_pages %} uses plugins that are enabled by default and cannot be disabled: +- [`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) + +You can enable additional plugins by adding the plugin's gem to the `plugins` setting in your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. + +For a list of supported plugins, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. For usage information for a specific plugin, see the plugin's documentation. + +{% tip %} + +**Tip:** You can make sure you're using the latest version of all plugins by keeping the {% data variables.product.prodname_pages %} gem updated. For more information, see "[Testing your GitHub Pages site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" and "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. + +{% endtip %} + +{% data variables.product.prodname_pages %} cannot build sites using unsupported plugins. If you want to use unsupported plugins, generate your site locally and then push your site's static files to {% data variables.product.product_name %}. + +### Syntax highlighting + +To make your site easier to read, code snippets are highlighted on {% data variables.product.prodname_pages %} sites the same way they're highlighted on {% data variables.product.product_name %}. For more information about syntax highlighting on {% data variables.product.product_name %}, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)." + +By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). If you specify Pygments in your *_config.yml* file, Rouge will be used instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." + +If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file. + +```yaml +kramdown: + syntax_highlighter_opts: + disable : true +``` + +If your theme doesn't include CSS for syntax highlighting, you can generate {% data variables.product.prodname_dotcom %}'s syntax highlighting CSS and add it to your project's `style.css` file. + +```shell +$ rougify style github > style.css +``` + +### Building your site locally + +{% data reusables.pages.test-locally %} diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..9b2ffcb839 --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,62 @@ +--- +title: About Jekyll build errors for GitHub Pages sites +intro: 'If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you''ll receive an error message with more information.' +redirect_from: + - /articles/viewing-jekyll-build-error-messages/ + - /articles/generic-jekyll-build-failures/ + - /articles/about-jekyll-build-errors-for-github-pages-sites + - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### About Jekyll build errors + +Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %} +- The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} +- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)." +- You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation. + +{% note %} + +**Note:** It can take up to 20 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}. + +{% endnote %} + +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. +- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. +- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. + +For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." + +### Viewing Jekyll build error messages + +We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." + +When you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/articles/about-status-checks)." + +When you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} + +You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. + +You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit. + +1. If you haven't already, add a file called _Gemfile_ in the root of your publishing source, with the following content: + ```ruby + source `https://rubygems.org` + gem `github-pages` + ``` + +2. Configure your site's repository for the testing service of your choice. For example, to use [Travis CI](https://travis-ci.org/), add a file named _.travis.yml_ in the root of your publishing source, with the following content: + ```yaml + language: ruby + rvm: + - 2.3 + script: "bundle exec jekyll build" + ``` +3. You may need to activate your repository with the third-party testing service. For more information, see your testing service's documentation. diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..831e9a3fb0 --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,71 @@ +--- +title: Adding a theme to your GitHub Pages site using Jekyll +intro: You can personalize your Jekyll site by adding and customizing a theme. +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +People with write permissions for a repository can add a theme to a {% data variables.product.prodname_pages %} site using Jekyll. + +{% data reusables.pages.test-locally %} + +### Adding a theme + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +2. Navigate to *_config.yml*. +{% data reusables.repositories.edit-file %} +4. Add a new line to the file for the theme name. + - 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. For a list of supported themes, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site. ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png) + - To use any other Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, type `remote_theme: THEME-NAME`, replacing THEME-NAME with the name of the theme as shown in the README of the theme's repository. ![Unsupported theme in config file](/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 %} + +### Customizing your theme's CSS + +{% 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. Create a new file called _/assets/css/style.scss_. +2. Add the following content to the top of the file: + ```scss + --- + --- + + @import "{{ site.theme }}"; + ``` +3. Add any custom CSS or Sass (including imports) you'd like immediately after the `@import` line. + +### Customizing your theme's HTML layout + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +1. On {% data variables.product.prodname_dotcom %}, navigate to your theme's source repository. For example, the source repository for Minima is https://github.com/jekyll/minima. +2. In the *_layouts* folder, navigate to your theme's _default.html_ file. +3. Copy the contents of the file. +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +6. Create a file called *_layouts/default.html*. +7. Paste the default layout content you copied earlier. +8. Customize the layout as you'd like. + +### Дополнительная литература + +- "[Creating new files](/articles/creating-new-files)" diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..f36bbce59d --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,72 @@ +--- +title: Adding content to your GitHub Pages site using Jekyll +intro: 'You can add a new page or post to your Jekyll site on {% data variables.product.prodname_pages %}.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/adding-content-to-your-github-pages-site-using-jekyll + - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +People with write permissions for a repository can add content to a {% data variables.product.prodname_pages %} site using Jekyll. + +### About content in Jekyll sites + +Before you can add content to a Jekyll site on {% data variables.product.prodname_pages %}, you must create a Jekyll site. For more information, see "[Creating a {% data variables.product.prodname_pages %} site with Jekyll](/articles/creating-a-github-pages-site-with-jekyll)." + +The main types of content for Jekyll sites are pages and posts. A page is for standalone content that isn't associated with a specific date, such as an "About" page. The default Jekyll site contains a file called `about.md`, which renders as a page on your site at `YOUR-SITE-URL/about`. You can edit the contents of that file to personalize your "About" page, and you can use the "About" page as a template to create new pages. For more information, see "[Pages](https://jekyllrb.com/docs/pages/)" in the Jekyll documentation. + +A post is a blog post. The default Jekyll site contains a directory named `_posts` that contains a default post file. You can edit the contents of that post, and you can use the default post as a template to create new posts. For more information, see "[Posts](https://jekyllrb.com/docs/posts/)" in the Jekyll documentation. + +Your theme includes default layouts, includes, and stylesheets that will automatically be applied to new pages and posts on your site, but you can override any of these defaults. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#themes)." + +{% data reusables.pages.about-front-matter %} + +{% data reusables.pages.test-locally %} + +### Adding a new page to your site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. In the root of your publishing source, create a new file for your page called _PAGE-NAME.md_, replacing _PAGE-NAME_ with a meaningful filename for the page. +4. Add the following YAML frontmatter to the top of the file, replacing _PAGE TITLE_ with the page's title and _URL-PATH_ with a path you want for the page's URL. For example, if the base URL of your site is `https://octocat.github.io` and your _URL-PATH_ is `/about/contact/`, your page will be located at `https://octocat.github.io/about/contact`. + ```shell + layout: page + title: "PAGE TITLE" + permalink: /URL-PATH/ + ``` +5. Below the frontmatter, add content for your page. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### Adding a new post to your site + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. Navigate to the `_posts` directory. +4. Create a new file called _YYYY-MM-DD-NAME-OF-POST.md_, replacing _YYYY-MM-DD_ with the date of your post and _NAME-OF-POST_ with the name of your post. +4. Add the following YAML frontmatter to the top of the file, replacing _POST TITLE_ with the post's title, _YYYY-MM-DD hh:mm:ss -0000_ with the date and time for the post, and _CATEGORY-1_ and _CATEGORY-2_ with as many categories you want for your post. + ```shell + layout: post + title: "POST TITLE" + date: YYYY-MM-DD hh:mm:ss -0000 + categories: CATEGORY-1 CATEGORY-2 + ``` +5. Below the frontmatter, add content for your post. +{% 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`. + +### Дальнейшие шаги + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000..ef7076651e --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,116 @@ +--- +title: Creating a GitHub Pages site with Jekyll +intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/creating-a-github-pages-site-with-jekyll + - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll +permissions: 'People with admin permissions for a repository can create a {% data variables.product.prodname_pages %} site with Jekyll.' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### Требования + +Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Creating a repository for your site + +{% data reusables.pages.new-or-existing-repo %} + +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} + +### Creating your site + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository. + ```shell + $ cd PARENT-FOLDER + ``` +3. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository. + ```shell + $ git init REPOSITORY-NAME + > Initialized empty Git repository in /Users/octocat/my-site/.git/ + # Creates a new folder on your computer, initialized as a Git repository + ``` + 4. Change directories to the repository. + ```shell + $ cd REPOSITORY-NAME + # Changes the working directory + ``` +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. + ```shell + $ mkdir docs + # Creates a new folder called docs + $ cd docs + ``` + If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch. + ```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. To create a new Jekyll site, use the `jekyll new` command: + ```shell + $ jekyll new . + # Creates a Jekyll site in the current directory + ``` +8. Open the Gemfile that Jekyll created. +1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line. +1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to: + + ```shell + gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins + ``` + + Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)." + + The correct version Jekyll will be installed as a dependency of the `github-pages` gem. +10. Save and close the Gemfile. +11. From the command line, run `bundle update`. +11. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." +12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository. +```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. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on. + ```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.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### Дальнейшие шаги + +To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)." + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md new file mode 100644 index 0000000000..90f13f8482 --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md @@ -0,0 +1,25 @@ +--- +title: Setting up a GitHub Pages site with Jekyll +intro: 'You can use Jekyll, a popular static site generator, to further customize your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..dee76a29d1 --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,36 @@ +--- +title: Setting a Markdown processor for your GitHub Pages site using Jekyll +intro: 'You can choose a Markdown processor to determine how Markdown is rendered on your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/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: '*' +topics: + - pages +--- + +People with write permissions for a repository can set the Markdown processor for a {% data variables.product.prodname_pages %} site. + +{% 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 %}. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." + +You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor, but only our CommonMark processor will always match the results you see on {% data variables.product.product_name %}. + +{% data reusables.pages.navigate-site-repo %} +2. In your repository, browse to the *_config.yml* file. +{% data reusables.repositories.edit-file %} +4. Find the line that starts with `markdown:` and change the value to `kramdown` or `GFM`. ![Markdown setting in 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 %} + +### Дополнительная литература + +- [kramdown Documentation](https://kramdown.gettalong.org/documentation.html) +- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000..d889fe2fc8 --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,62 @@ +--- +title: Testing your GitHub Pages site locally with Jekyll +intro: 'You can build your {% data variables.product.prodname_pages %} site locally to preview and test changes to your site.' +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 + - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +Anyone with read permissions for a repository can test a {% data variables.product.prodname_pages %} site locally. + +### Требования + +Before you can use Jekyll to test a site, you must: + - Install [Jekyll](https://jekyllrb.com/docs/installation/). + - Create a Jekyll site. For more information, see "[Creating a {% data variables.product.prodname_pages %} site with Jekyll](/articles/creating-a-github-pages-site-with-jekyll)." + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### Building your site locally + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.pages.navigate-publishing-source %} +3. Run `bundle install`. +3. Run your Jekyll site locally. + ```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. To preview your site, in your web browser, navigate to `http://localhost:4000`. + +### Updating the {% data variables.product.prodname_pages %} gem + +Jekyll is an active open source project that is updated frequently. If the `github-pages` gem on your computer is out of date with the `github-pages` gem on the {% data variables.product.prodname_pages %} server, your site may look different when built locally than when published on {% data variables.product.product_name %}. To avoid this, regularly update the `github-pages` gem on your computer. + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Update the `github-pages` gem. + - If you installed Bundler, run `bundle update github-pages`. + - If you don't have Bundler installed, run `gem update github-pages`. + +### Дополнительная литература + +- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in the Jekyll documentation diff --git a/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..907cb3c671 --- /dev/null +++ b/translations/ru-RU/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,191 @@ +--- +title: Troubleshooting Jekyll build errors for GitHub Pages sites +intro: 'You can use Jekyll build error messages to troubleshoot problems with your {% data variables.product.prodname_pages %} site.' +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 + - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - pages +--- + +### Troubleshooting build errors + +If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you can use error messages to troubleshoot. For more information about error messages and how to view them, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." + +If you received a generic error message, check for common issues. +- You're using unsupported plugins. 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" %} +- Your repository has exceeded our repository size limits. For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota)"{% endif %} +- You changed the `source` setting in your *_config.yml* file. {% data variables.product.prodname_pages %} overrides this setting during the build process. +- A filename in your publishing source contains a colon (`:`) which is not supported. + +If you received a specific error message, review the troubleshooting information for the error message below. + +After you've fixed any errors, push the changes to your site's publishing source to trigger another build on {% data variables.product.product_name %}. + +### Config file error + +This error means that your site failed to build because the *_config.yml* file contains syntax errors. + +To troubleshoot, make sure that your *_config.yml* file follows these rules: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +### Date is not a valid datetime + +This error means that one of the pages on your site includes an invalid datetime. + +To troubleshoot, search the file in the error message and the file's layouts for calls to any date-related Liquid filters. Make sure that any variables passed into date-related Liquid filters have values in all cases and never pass `nil` or `""`. For more information, see "[Liquid filters](https://help.shopify.com/en/themes/liquid/filters)" in the Liquid documentation. + +### File does not exist in includes directory + +This error means that your code references a file that doesn't exist in your *_includes* directory. + +{% data reusables.pages.search-for-includes %} If any of the files you've referenced aren't in the *_includes* directory, copy or move the files into the *_includes* directory. + +### File is a symlink + +This error means that your code references a symlinked file that does not exist in the publishing source for your site. + +{% data reusables.pages.search-for-includes %} If any of the files you've referenced are symlinked, copy or move the files into the *_includes* directory. + +### File is not properly UTF-8 encoded + +This error means that you used non-Latin characters, like `日本語`, without telling the computer to expect these symbols. + +To troubleshoot, force UTF-8 encoding by adding the following line to your *_config.yml* file: +```yaml +encoding: UTF-8 +``` + +### Invalid highlighter language + +This error means that you specified any syntax highlighter other than [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/) in your configuration file. + +To troubleshoot, update your *_config.yml* file to specify [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/). For more information, see "[About {% data variables.product.product_name %} and Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)." + +### Invalid post date + +This error means that a post on your site contains an invalid date in the filename or YAML front matter. + +To troubleshoot, make sure all dates are formatted as YYYY-MM-DD HH:MM:SS for UTC and are actual calendar dates. To specify a time zone with an offset from UTC, use the format YYYY-MM-DD HH:MM:SS +/-TTTT, like `2014-04-18 11:30:00 +0800`. + +If you specify a date format in your *_config.yml* file, make sure the format is correct. + +### Invalid Sass or SCSS + +This error means your repository contains a Sass or SCSS file with invalid content. + +To troubleshoot, review the line number included in the error message for invalid Sass or SCSS. To help prevent future errors, install a Sass or SCSS linter for your favorite text editor. + +### Invalid submodule + +This error means that your repository includes a submodule that hasn't been properly initialized. + +{% data reusables.pages.remove-submodule %} + +If do you want to use the submodule, make sure you use `https://` when referencing the submodule (not `http://`) and that the submodule is in a public repository. + +### Invalid YAML in data file + +This error means that one of more files in the *_data* folder contains invalid YAML. + +To troubleshoot, make sure the YAML files in your *_data* folder follow these rules: + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +For more information about Jekyll data files, see "[Data Files](https://jekyllrb.com/docs/datafiles/)" in the Jekyll documentation. + +### Markdown errors + +This error means that your repository contains Markdown errors. + +To troubleshoot, make sure you are using a supported Markdown processor. For more information, see "[Setting a Markdown processor for your {% data variables.product.prodname_pages %} site using Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)." + +Then, make sure the file in the error message uses valid Markdown syntax. For more information, see "[Markdown: Syntax](https://daringfireball.net/projects/markdown/syntax)" on Daring Fireball. + +### Missing docs folder + +This error means that you have chosen the `docs` folder on a branch as your publishing source, but there is no `docs` folder in the root of your repository on that branch. + +To troubleshoot, if your `docs` folder was accidentally moved, try moving the `docs` folder back to the root of your repository on the branch you chose for your publishing source. If the `docs` folder was accidentally deleted, you can either: +- Use Git to revert or undo the deletion. For more information, see "[git-revert](https://git-scm.com/docs/git-revert.html)" in the Git documentation. +- Create a new `docs` folder in the root of your repository on the branch you chose for your publishing source and add your site's source files to the folder. For more information, see "[Creating new files](/articles/creating-new-files)." +- Change your publishing source. For more information, see "[Configuring a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)." + +### Missing submodule + +This error means that your repository includes a submodule that doesn't exist or hasn't been properly initialized. + +{% data reusables.pages.remove-submodule %} + +If you do want to use a submodule, initialize the submodule. For more information, see "[Git Tools - Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" in the _Pro Git_ book. + +### Relative permalinks configured + +This errors means that you have relative permalinks, which are not supported by {% data variables.product.prodname_pages %}, in your *_config.yml* file. + +Permalinks are permanent URLs that reference a particular page on your site. Absolute permalinks begin with the root of the site, while relative permalinks begin with the folder containing the referenced page. {% data variables.product.prodname_pages %} and Jekyll no longer support relative permalinks. For more information about permalinks, see "[Permalinks](https://jekyllrb.com/docs/permalinks/)" in the Jekyll documentation. + +To troubleshoot, remove the `relative_permalinks` line from your *_config.yml* file and reformat any relative permalinks in your site with absolute permalinks. For more information, see "[Editing files in your repository](/articles/editing-files-in-your-repository)." + +### Symlink does not exist within your site's repository + +This error means that your site includes a symbolic link (symlink) that does not exist in the publishing source for your site. For more information about symlinks, see "[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)" on Wikipedia. + +To troubleshoot, determine if the file in the error message is used to build your site. If not, or if you don't want the file to be a symlink, delete the file. If the symlinked file is necessary to build your site, make sure the file or directory the symlink references is in the publishing source for your site. 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 %} + +### Syntax error in 'for' loop + +This error means that your code includes invalid syntax in a Liquid `for` loop declaration. + +To troubleshoot, make sure all `for` loops in the file in the error message have proper syntax. For more information about proper syntax for `for` loops, see "[Iteration tags](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" in the Liquid documentation. + +### Tag not properly closed + +This error message means that your code includes a logic tag that is not properly closed. For example, {% raw %}`{% capture example_variable %}` must be closed by `{% endcapture %}`{% endraw %}. + +To troubleshoot, make sure all logic tags in the file in the error message are properly closed. For more information, see "[Liquid tags](https://help.shopify.com/en/themes/liquid/tags)" in the Liquid documentation. + +### Tag not properly terminated + +This error means that your code includes an output tag that is not properly terminated. For example, {% raw %}`{{ page.title }` instead of `{{ page.title }}`{% endraw %}. + +To troubleshoot, make sure all output tags in the file in the error message are terminated with `}}`. For more information, see "[Liquid objects](https://help.shopify.com/en/themes/liquid/objects)" in the Liquid documentation. + +### Unknown tag error + +This error means that your code contains an unrecognized Liquid tag. + +To troubleshoot, make sure all Liquid tags in the file in the error message match Jekyll's default variables and there are no typos in the tag names. For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation. + +Unsupported plugins are a common source of unrecognized tags. If you use an unsupported plugin in your site by generating your site locally and pushing your static files to {% data variables.product.product_name %}, make sure the plugin is not introducing tags that are not in Jekyll's default variables. For a list of supported plugins, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)." diff --git a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md index 4d90a543dd..09b56ba277 100644 --- a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md @@ -170,7 +170,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap In the same way, we can [view repositories for the authenticated user][user repos api]: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -207,7 +207,7 @@ Fetching information for existing repositories is a common use case, but the we need to `POST` some JSON containing the details and configuration options. ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -242,7 +242,7 @@ The UI for Issues on {% data variables.product.product_name %} aims to provide ' Just like github.com, the API provides a few methods to view issues for the authenticated user. To [see all your issues][get issues api], call `GET /issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -250,7 +250,7 @@ To get only the [issues under one of your {% data variables.product.product_name /orgs//issues`: ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -283,7 +283,7 @@ Now that we've seen how to paginate lists of issues, let's [create an issue][cre To create an issue, we need to be authenticated, so we'll pass an OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON body to the `/issues` path underneath the repository in which we want to create the issue: ```shell -$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ +$ curl -i -H 'Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/ru-RU/content/rest/reference/enterprise-admin.md b/translations/ru-RU/content/rest/reference/enterprise-admin.md index b00f75e325..cc95c34e55 100644 --- a/translations/ru-RU/content/rest/reference/enterprise-admin.md +++ b/translations/ru-RU/content/rest/reference/enterprise-admin.md @@ -100,7 +100,7 @@ The IdP must use `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The enterprise SCIM API is only available to enterprises on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% endnote %} diff --git a/translations/ru-RU/content/rest/reference/migrations.md b/translations/ru-RU/content/rest/reference/migrations.md index 95c95947d2..d7fc4a9575 100644 --- a/translations/ru-RU/content/rest/reference/migrations.md +++ b/translations/ru-RU/content/rest/reference/migrations.md @@ -16,7 +16,7 @@ topics: ## Организация -The Migrations API is only available to authenticated organization owners. For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." +The Migrations API is only available to authenticated organization owners. For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/ru-RU/content/rest/reference/repos.md b/translations/ru-RU/content/rest/reference/repos.md index 88536274ab..4dd1d6d078 100644 --- a/translations/ru-RU/content/rest/reference/repos.md +++ b/translations/ru-RU/content/rest/reference/repos.md @@ -193,7 +193,7 @@ The authenticated user will be the author of any merges done through this endpoi ## Pages -The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." +The {% data variables.product.prodname_pages %} API retrieves information about your {% data variables.product.prodname_pages %} configuration, and the statuses of your builds. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." In {% data variables.product.prodname_pages %} API endpoints with a `status` key in their response, the value can be one of: * `null`: The site has yet to be built. @@ -205,7 +205,7 @@ In {% data variables.product.prodname_pages %} API endpoints with a `status` key In {% data variables.product.prodname_pages %} API endpoints that return GitHub Pages site information, the JSON responses include these fields: * `html_url`: The absolute URL (including scheme) of the rendered Pages site. For example, `https://username.github.io`. * `source`: An object that contains the source branch and directory for the rendered Pages site. This includes: - - `branch`: The repository branch used to publish your [site's source files](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. + - `branch`: The repository branch used to publish your [site's source files](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). For example, _main_ or _gh-pages_. - `path`: The repository directory from which the site publishes. Will be either `/` or `/docs`. {% for operation in currentRestOperations %} diff --git a/translations/ru-RU/content/rest/reference/scim.md b/translations/ru-RU/content/rest/reference/scim.md index ce72e89096..76f38bcea9 100644 --- a/translations/ru-RU/content/rest/reference/scim.md +++ b/translations/ru-RU/content/rest/reference/scim.md @@ -14,7 +14,7 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." {% endnote %} diff --git a/translations/ru-RU/content/rest/reference/teams.md b/translations/ru-RU/content/rest/reference/teams.md index 7f6b2a3bf4..d98f01e647 100644 --- a/translations/ru-RU/content/rest/reference/teams.md +++ b/translations/ru-RU/content/rest/reference/teams.md @@ -18,7 +18,7 @@ This API is only available to authenticated members of the team's [organization] ## Discussions -The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. +The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -26,7 +26,7 @@ The team discussions API allows you to get, create, edit, and delete discussion ## Discussion comments -The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)." This API is only available to authenticated members of the team's organization. +The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." This API is only available to authenticated members of the team's organization. {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -39,7 +39,7 @@ This API is only available to authenticated members of the team's organization. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "Synchronizing teams between your identity provider and GitHub." +**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "Synchronizing teams between your identity provider and GitHub." {% endnote %} @@ -54,7 +54,7 @@ This API is only available to authenticated members of the team's organization. The Team Synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups. To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "Authorizing a personal access token for use with a SAML single sign-on organization." -You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." +You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} diff --git a/translations/ru-RU/data/release-notes/2-21/18.yml b/translations/ru-RU/data/release-notes/2-21/18.yml new file mode 100644 index 0000000000..e27f2fe4a0 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/18.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. + - Security alerts are not reported when pushing to a repository on the command line. diff --git a/translations/ru-RU/data/release-notes/2-21/6.yml b/translations/ru-RU/data/release-notes/2-21/6.yml index d85f716f13..24127f581c 100644 Binary files a/translations/ru-RU/data/release-notes/2-21/6.yml and b/translations/ru-RU/data/release-notes/2-21/6.yml differ diff --git a/translations/ru-RU/data/release-notes/2-22/10.yml b/translations/ru-RU/data/release-notes/2-22/10.yml new file mode 100644 index 0000000000..fd5aa5a1d8 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-22/10.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. diff --git a/translations/ru-RU/data/release-notes/3-0/4.yml b/translations/ru-RU/data/release-notes/3-0/4.yml new file mode 100644 index 0000000000..b3a39c1743 --- /dev/null +++ b/translations/ru-RU/data/release-notes/3-0/4.yml @@ -0,0 +1,25 @@ +--- +date: '2021-04-01' +intro: 'The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."' +sections: + security_fixes: + - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." + - Packages have been updated to the latest security versions. + bugs: + - When maintenance mode was enabled, some services continued to be listed as "active processes" even though they were expected to be running, and should not have been listed. + - After upgrading from 2.22.x to 3.0.x with GitHub Actions enabled, the self-hosted runner version was not updated and no self-hosted updates were made. + - Old GitHub Pages builds were not cleaned up leading to increased disk usage. + - '`memcached` was not running on active replicas.' + - Upgrade failed when updating file permissions when GitHub Actions was enabled. + - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. + - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. + - The `ghe-saml-mapping-csv` command-line utility produced a warning message. + - The label on search results for internal repositories was shown as "Private" instead of "Internal". + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - 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. + - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. + - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text. diff --git a/translations/ru-RU/data/reusables/actions/actions-audit-events-workflow.md b/translations/ru-RU/data/reusables/actions/actions-audit-events-workflow.md index b0485e34c7..60434fafea 100644 --- a/translations/ru-RU/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/ru-RU/data/reusables/actions/actions-audit-events-workflow.md @@ -4,5 +4,7 @@ | `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." | | `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)." | | `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)." | +| `disable_workflow` | Triggered when a workflow is disabled. | +| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`. | | `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)." | | `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." | diff --git a/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md index baa32fddac..b6abfe68c7 100644 --- a/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md +++ b/translations/ru-RU/data/reusables/advanced-security/about-ghas-organization-policy.md @@ -2,4 +2,4 @@ You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose. -Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_advanced_security %} features, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." diff --git a/translations/ru-RU/data/reusables/branches/set-default-branch.md b/translations/ru-RU/data/reusables/branches/set-default-branch.md index 20d94881f6..61c5fb0903 100644 --- a/translations/ru-RU/data/reusables/branches/set-default-branch.md +++ b/translations/ru-RU/data/reusables/branches/set-default-branch.md @@ -1 +1 @@ -You can set the name of the default branch for new repositories. 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 %} +You can set the name of the default branch for new repositories. 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](/organizations/managing-organization-settings/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 %} diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-visibility.md index 3f4f17e1b2..303bb3669b 100644 --- a/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ The repositories for an assignment can be public or private. If you use private repositories, only the student or team can see the feedback you provide. -You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" and "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. diff --git a/translations/ru-RU/data/reusables/classroom/guide-create-new-classroom.md b/translations/ru-RU/data/reusables/classroom/guide-create-new-classroom.md index e554d4b605..b005e29ebd 100644 --- a/translations/ru-RU/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/ru-RU/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)." ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) +1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) 1. Type the name for your classroom. ![Text field for typing name of classroom](/assets/images/help/classroom/type-classroom-name.png) 1. Click **Create classroom**. ![Text field for typing name of classroom](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/ru-RU/data/reusables/code-scanning/click-alert-in-list.md b/translations/ru-RU/data/reusables/code-scanning/click-alert-in-list.md index af80aac75d..50f6e6458e 100644 --- a/translations/ru-RU/data/reusables/code-scanning/click-alert-in-list.md +++ b/translations/ru-RU/data/reusables/code-scanning/click-alert-in-list.md @@ -1 +1,6 @@ -1. Under "Code scanning," click the alert you'd like to explore. ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +1. Under "Code scanning," click the alert you'd like to explore. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% 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 7dd8f996d0..c3b22f4515 100644 --- a/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -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-dependencies)." You can configure access to private registries in a repository's _dependabot.yml_ configuration file. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." +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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)." You can configure access to private registries in a repository's _dependabot.yml_ configuration file. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." diff --git a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md index 9f6d4c86ad..deb30db8e8 100644 --- a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md @@ -6,7 +6,7 @@ The following table shows, for each package manager: | Package manager | YAML value | Supported versions | Private repositories | Private registries | Vendoring | | --------------------------------- | ---------------- | ------------------------------ |:--------------------:|:------------------:|:---------:| -| Средство увязки программ в пакеты | `bundler` | v1 | | **✓** | **✓** | +| Средство увязки программ в пакеты | `bundler` | v1, v2 | | **✓** | **✓** | | Cargo | `cargo` | v1 | **✓** | **✓** | | | Composer | `composer` | v1, v2 | **✓** | **✓** | | | Докер | `докер` | v1 | **✓** | **✓** | | diff --git a/translations/ru-RU/data/reusables/dotcom_billing/coupon-expires.md b/translations/ru-RU/data/reusables/dotcom_billing/coupon-expires.md new file mode 100644 index 0000000000..71beb790aa --- /dev/null +++ b/translations/ru-RU/data/reusables/dotcom_billing/coupon-expires.md @@ -0,0 +1 @@ +If you use a coupon to pay for a subscription, when the coupon expires, your payment method will be charged the full cost of your subscription. If you do not have a saved payment method, your account will be downgraded to {% data variables.product.prodname_free_user %} for user accounts or {% data variables.product.prodname_free_team %} for organizations. diff --git a/translations/ru-RU/data/reusables/education/about-github-education-link.md b/translations/ru-RU/data/reusables/education/about-github-education-link.md index 84a5d61418..4106c559a9 100644 --- a/translations/ru-RU/data/reusables/education/about-github-education-link.md +++ b/translations/ru-RU/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_education %} school. For more information, see "[About {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)." +Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)." diff --git a/translations/ru-RU/data/reusables/github-actions/actions-github-connect-requirement.md b/translations/ru-RU/data/reusables/github-actions/actions-github-connect-requirement.md new file mode 100644 index 0000000000..8b36658e05 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/actions-github-connect-requirement.md @@ -0,0 +1 @@ +To allow {% data variables.product.prodname_ghe_server %} to use actions directly from {% data variables.product.prodname_dotcom_the_website %}, you can use {% data variables.product.prodname_github_connect %}. You will need to enable the setting for "Server can use actions from {% data variables.product.prodname_dotcom_the_website %} in workflows runs," as described in "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." diff --git a/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md b/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md index 33c7bd3120..2814ee964b 100644 --- a/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/ru-RU/data/reusables/github-actions/java-jvm-architecture.md @@ -2,16 +2,17 @@ The starter workflow template sets up the `PATH` to contain OpenJDK 8 for the x64 platform. If you want to use a different version of Java, or target a different architecture (`x64` or `x86`), you can use the `setup-java` action to choose a different Java runtime environment. -For example, to use version 9.0.4 of the JDK for the x64 platform, you can use the `setup-java` action and configure the `java-version` and `architecture` parameters to `'9.0.4'` and `x64`. +For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'adopt'` and `x64`. {% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 + - name: Set up JDK 11 for x64 + uses: actions/setup-java@v2 with: - java-version: '9.0.4' + java-version: '11' + distribution: 'adopt' architecture: x64 ``` {% endraw %} 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 index b2c935e893..046848b19c 100644 --- 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 @@ -1,5 +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)." +**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](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endwarning %} diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 125c285ead..0b4022951d 100644 --- a/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/ru-RU/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." +After you enable team synchronization, team maintainers and organization owners can connect a team to an IdP group on {% data variables.product.prodname_dotcom %} or through the API. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)" and "[Team synchronization](/rest/reference/teams#team-sync)." diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm-saml.md index a0e1a12947..3ebd07b725 100644 --- a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm-saml.md +++ b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-confirm-saml.md @@ -1 +1 @@ -3. Confirm that SAML SSO is enabled. For more information, see "[Managing SAML single sign-on for your organization](/articles/managing-saml-single-sign-on-for-your-organization)." +3. Confirm that SAML SSO is enabled. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/)." diff --git a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-okta-requirements.md index f8ebbf4246..08aa1fad59 100644 --- a/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-okta-requirements.md +++ b/translations/ru-RU/data/reusables/identity-and-permissions/team-sync-okta-requirements.md @@ -1,5 +1,5 @@ To enable team synchronization for Okta, you or your IdP administrator must: -- Enable SAML SSO and SCIM for your organization using Okta. For more information, see "[Configuring SAML single sign-on and SCIM using Okta](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)." +- Enable SAML SSO and SCIM for your organization using Okta. For more information, see "[Configuring SAML single sign-on and SCIM using Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)." - Provide the tenant URL for your Okta instance. - Generate a valid SSWS token with read-only admin permissions for your Okta installation as a service user. For more information, see [Create the token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) and [Service users](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) in Okta's documentation. diff --git a/translations/ru-RU/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/ru-RU/data/reusables/organizations/team-discussions-are-for-orgs.md index cb0f53f8ed..656bb6a3b7 100644 --- a/translations/ru-RU/data/reusables/organizations/team-discussions-are-for-orgs.md +++ b/translations/ru-RU/data/reusables/organizations/team-discussions-are-for-orgs.md @@ -1 +1 @@ -Team discussions are only available on team pages in organizations. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)." +Team discussions are only available on team pages in organizations. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." diff --git a/translations/ru-RU/data/reusables/organizations/team-synchronization.md b/translations/ru-RU/data/reusables/organizations/team-synchronization.md index a609ef11b9..94743620fb 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" or currentVersion == "github-ae@latest" %} -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)." +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](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." {% endif %} diff --git a/translations/ru-RU/data/reusables/organizations/team_maintainers_can.md b/translations/ru-RU/data/reusables/organizations/team_maintainers_can.md index 586a4657f5..8c68c29077 100644 --- a/translations/ru-RU/data/reusables/organizations/team_maintainers_can.md +++ b/translations/ru-RU/data/reusables/organizations/team_maintainers_can.md @@ -11,5 +11,5 @@ Members with team maintainer permissions can: - [Remove organization members from the team](/articles/removing-organization-members-from-a-team) - [Promote an existing team member to team maintainer](/articles/giving-team-maintainer-permissions-to-an-organization-member) - Remove the team's access to repositories{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -- [Manage code review assignment for the team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} +- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [Manage scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md index d502dc5ee9..1581f1cf5e 100644 --- a/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/ru-RU/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. Create a new personal access token (PAT) with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token. {% warning %} - **Note:** If you select the `write:packages` scope, deselect the `repo` scope when creating the PAT. Adding a PAT with the `repo` scope as a secret in your repository allows the credential to be accessible to all collaborators in the repository. This gives unnecessary additional access when a PAT with the `repo` scope is used within an action. For more information on security best practices for actions, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." + **Note:** By default, when you select the `write:packages` scope for your personal access token (PAT) in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for GitHub Actions workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://github.com/settings/tokens/new?scopes=write:packages`. {% endwarning %} diff --git a/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index fb85de55b5..666a293400 100644 --- a/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/ru-RU/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,5 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} +PATs can grant broad access to your account. You should select only the necessary `read:packages`, `write:packages`, or `delete:packages` scope when creating a PAT to authenticate to the {% data variables.product.prodname_container_registry %}. + To authenticate to {% data variables.product.prodname_github_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)." diff --git a/translations/ru-RU/data/reusables/pages/choose-visibility.md b/translations/ru-RU/data/reusables/pages/choose-visibility.md index bd794a90d7..9ed7fac761 100644 --- a/translations/ru-RU/data/reusables/pages/choose-visibility.md +++ b/translations/ru-RU/data/reusables/pages/choose-visibility.md @@ -1 +1 @@ -1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file +1. Optionally, if you're publishing a project site from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, choose the visibility for your site. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". ![Drop-down to select visibility for your site](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md index fc98787aaa..26d5ca7f58 100644 --- a/translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md +++ b/translations/ru-RU/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)." +**Note:** Organization owners can restrict the publication of {% data variables.product.prodname_pages %} sites from repositories owned by the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md b/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md index 04d4ddeb1c..e8de190b64 100644 --- a/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/ru-RU/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} +**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. 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 currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} {% endwarning %} diff --git a/translations/ru-RU/data/reusables/pages/sidebar-pages.md b/translations/ru-RU/data/reusables/pages/sidebar-pages.md new file mode 100644 index 0000000000..41713183cc --- /dev/null +++ b/translations/ru-RU/data/reusables/pages/sidebar-pages.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +1. In the left sidebar, click **Pages**. ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png) +{% endif %} diff --git a/translations/ru-RU/data/reusables/pages/update_your_dns_settings.md b/translations/ru-RU/data/reusables/pages/update_your_dns_settings.md index 67317a2a04..6bb9bacc45 100644 --- a/translations/ru-RU/data/reusables/pages/update_your_dns_settings.md +++ b/translations/ru-RU/data/reusables/pages/update_your_dns_settings.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" %}1. If there's a custom domain enabled for your site, to avoid a domain takeover, update your DNS settings. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-custom-domain-for-your-github-pages-site)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. If there's a custom domain enabled for your site, to avoid a domain takeover, update your DNS settings. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site)."{% endif %} diff --git a/translations/ru-RU/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/ru-RU/data/reusables/pages/www-and-apex-domain-recommendation.md index 83de39755f..f94b04d6d4 100644 --- a/translations/ru-RU/data/reusables/pages/www-and-apex-domain-recommendation.md +++ b/translations/ru-RU/data/reusables/pages/www-and-apex-domain-recommendation.md @@ -1 +1 @@ -If you are using an apex domain as your custom domain, we recommend also setting up a `www` subdomain. If you configure the correct records for each domain type through your DNS provider, {% data variables.product.prodname_pages %} will automatically create redirects between the domains. For example, if you configure `www.example.com` as your custom domain for your site, and you have `ALIAS` and `CNAME` records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)." +If you are using an apex domain as your custom domain, we recommend also setting up a `www` subdomain. If you configure the correct records for each domain type through your DNS provider, {% data variables.product.prodname_pages %} will automatically create redirects between the domains. For example, if you configure `www.example.com` as the custom domain for your site, and you have {% data variables.product.prodname_pages %} DNS records set up for the apex and `www` domains, then `example.com` will redirect to `www.example.com`. Note that automatic redirects only apply to the `www` subdomain. Automatic redirects do not apply to any other subdomains, such as `blog`. diff --git a/translations/ru-RU/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/ru-RU/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md index 979cf68329..3dc1d84355 100644 --- a/translations/ru-RU/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ b/translations/ru-RU/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md @@ -6,6 +6,6 @@ - When [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync), if you remove a person from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync.{% endif %} - You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. -- 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. For more information, see "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." +- 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. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} diff --git a/translations/ru-RU/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/ru-RU/data/reusables/repositories/sidebar-code-scanning-alerts.md index 90992a248f..e5b3502439 100644 --- a/translations/ru-RU/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ b/translations/ru-RU/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -1 +1 @@ -1. In the left sidebar, click **Code scanning alerts**. Optionally, select the code scanning tool you used. !["Code scanning alerts" tab](/assets/images/help/repository/sidebar-code-scanning-alerts.png) +1. In the left sidebar, click **Code scanning alerts**. !["Code scanning alerts" tab](/assets/images/help/repository/sidebar-code-scanning-alerts.png) diff --git a/translations/ru-RU/data/reusables/saml/about-linked-identities.md b/translations/ru-RU/data/reusables/saml/about-linked-identities.md index 4f489081c2..f879d16402 100644 --- a/translations/ru-RU/data/reusables/saml/about-linked-identities.md +++ b/translations/ru-RU/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. When available, the entry will include SCIM data. For more information, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)." +You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." If a member links the wrong identity to their {% data variables.product.product_name %} account, you can revoke the linked identity to allow the member to try again. diff --git a/translations/ru-RU/data/reusables/saml/outside-collaborators-exemption.md b/translations/ru-RU/data/reusables/saml/outside-collaborators-exemption.md index f2936af1c5..598f6e88d5 100644 --- a/translations/ru-RU/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/ru-RU/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Outside collaborators aren't required to authenticate with an IdP to access the resources in an organization with SAML SSO. For more information on outside collaborators, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." +**Note:** Outside collaborators aren't required to authenticate with an IdP to access the resources in an organization with SAML SSO. For more information on outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)." {% endnote %} 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 index 0559438bb6..e75538fe3d 100644 --- 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 @@ -7,6 +7,7 @@ | 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 | +| Asana | Asana Personal Access Token | asana_personal_access_token | | 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 | @@ -37,8 +38,12 @@ | 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 | +| Grafana | Grafana API Key | grafana_api_key | | Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token | | Hubspot | Hubspot API Key | hubspot_api_key | +| Intercom | Intercom Access Token | intercom_access_token | +| Lob | Lob Live API Key | lob_live_api_key | +| Lob | Lob Test API Key | lob_test_api_key | | Mailchimp | Mailchimp API Key | mailchimp_api_key | | Mailgun | Mailgun API Key | mailgun_api_key | | npm | npm Access Token | npm_access_token | @@ -51,6 +56,7 @@ | Proctorio | Proctorio Secret Key | proctorio_secret_key | | Pulumi | Pulumi Access Token | pulumi_access_token | | PyPI | PyPI API Token | pypi_api_token | +| RubyGems | RubyGems API Key | rubygems_api_key | | Samsara | Samsara API Token | samsara_api_token | | Samsara | Samsara OAuth Access Token | samsara_oauth_access_token | | SendGrid | SendGrid API Key | sendgrid_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 index c9a8d65306..ebc268a20d 100644 --- 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 @@ -50,6 +50,7 @@ | Proctorio | Proctorio Secret Key | | Pulumi | Pulumi Access Token | | PyPI | PyPI API Token | +| RubyGems | RubyGems API Key | | Samsara | Samsara API Token | | Samsara | Samsara OAuth Access Token | | Shopify | Shopify App Shared Secret | diff --git a/translations/ru-RU/data/reusables/sponsors/choose-updates.md b/translations/ru-RU/data/reusables/sponsors/choose-updates.md index ade59cf05b..93f8807013 100644 --- a/translations/ru-RU/data/reusables/sponsors/choose-updates.md +++ b/translations/ru-RU/data/reusables/sponsors/choose-updates.md @@ -1 +1 @@ -4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) +4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![Checkbox to receive updates from sponsored account](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/ru-RU/data/reusables/sponsors/click-add-tier.md b/translations/ru-RU/data/reusables/sponsors/click-add-tier.md index 3b8ad38edf..0859f1368e 100644 --- a/translations/ru-RU/data/reusables/sponsors/click-add-tier.md +++ b/translations/ru-RU/data/reusables/sponsors/click-add-tier.md @@ -1 +1 @@ -1. On the bottom of the page, click **Add a tier**. ![Add a tier button](/assets/images/help/sponsors/add-a-tier-button.png) +1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![Add a tier button](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/ru-RU/data/reusables/sponsors/enable-custom-amounts.md b/translations/ru-RU/data/reusables/sponsors/enable-custom-amounts.md new file mode 100644 index 0000000000..1889367cb9 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/enable-custom-amounts.md @@ -0,0 +1,2 @@ +1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png) +1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png) diff --git a/translations/ru-RU/data/reusables/sponsors/feedback.md b/translations/ru-RU/data/reusables/sponsors/feedback.md new file mode 100644 index 0000000000..44c1bb7d3f --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/feedback.md @@ -0,0 +1 @@ +You can share your feedback about {% data variables.product.prodname_sponsors %} with {% data variables.product.company_short %}. To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)." diff --git a/translations/ru-RU/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/ru-RU/data/reusables/sponsors/manage-updates-for-orgs.md index 0cd08d5382..b47ac0599d 100644 --- a/translations/ru-RU/data/reusables/sponsors/manage-updates-for-orgs.md +++ b/translations/ru-RU/data/reusables/sponsors/manage-updates-for-orgs.md @@ -1 +1 @@ -You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)." +You can designate which email address receives updates from the accounts your organization sponsors. For more information, see "[Managing updates from accounts your organization sponsors](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)." diff --git a/translations/ru-RU/data/reusables/sponsors/pay-prorated-amount.md b/translations/ru-RU/data/reusables/sponsors/pay-prorated-amount.md index f201de957c..32f6b098f7 100644 --- a/translations/ru-RU/data/reusables/sponsors/pay-prorated-amount.md +++ b/translations/ru-RU/data/reusables/sponsors/pay-prorated-amount.md @@ -1 +1 @@ -1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Due today", click **Pay prorated $X.XX today**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file +1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![Link to pay prorated amount](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/sponsors/prorated-sponsorship.md b/translations/ru-RU/data/reusables/sponsors/prorated-sponsorship.md index 56a047d867..9e560bf708 100644 --- a/translations/ru-RU/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/ru-RU/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. +If you're starting a monthly sponsorship on behalf of your user account, you'll 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/ru-RU/data/reusables/sponsors/review-and-publish-tier.md b/translations/ru-RU/data/reusables/sponsors/review-and-publish-tier.md index 6d239c6919..a84fd2930a 100644 --- a/translations/ru-RU/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/ru-RU/data/reusables/sponsors/review-and-publish-tier.md @@ -1 +1 @@ -1. Proofread your tier, then click **Publish tier**. ![Publish tier button](/assets/images/help/sponsors/publish-tier-button.png) +1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/ru-RU/data/reusables/sponsors/review-tiers-to-select.md b/translations/ru-RU/data/reusables/sponsors/review-tiers-to-select.md new file mode 100644 index 0000000000..06e7cbd768 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/review-tiers-to-select.md @@ -0,0 +1 @@ +1. On the right side of the page, under "Select a tier", review the sponsorship tiers available. If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png) diff --git a/translations/ru-RU/data/reusables/sponsors/select-a-tier.md b/translations/ru-RU/data/reusables/sponsors/select-a-tier.md index 6ba1b8d427..b126110e6a 100644 --- a/translations/ru-RU/data/reusables/sponsors/select-a-tier.md +++ b/translations/ru-RU/data/reusables/sponsors/select-a-tier.md @@ -1 +1 @@ -1. On the right side of the page, under "Select a tier", review the sponsorship tiers available. Then, to the right of the tier you want, click **Select**. ![Select a tier box](/assets/images/help/sponsors/select-a-tier-box.png) +1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![Select a tier box](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/ru-RU/data/reusables/sponsors/sponsorship-details.md b/translations/ru-RU/data/reusables/sponsors/sponsorship-details.md index 6542580736..5f36b22238 100644 --- a/translations/ru-RU/data/reusables/sponsors/sponsorship-details.md +++ b/translations/ru-RU/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. Your sponsorship will share your account's existing billing date, payment method, and receipt. +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 one-time or monthly payment amounts and benefits that are set by the sponsored account. Your sponsorship will share your account's existing billing date, payment method, and receipt. diff --git a/translations/ru-RU/data/reusables/sponsors/tier-details.md b/translations/ru-RU/data/reusables/sponsors/tier-details.md index 9b80bb5aea..78c40c1054 100644 --- a/translations/ru-RU/data/reusables/sponsors/tier-details.md +++ b/translations/ru-RU/data/reusables/sponsors/tier-details.md @@ -1,3 +1,3 @@ -You can create up to ten sponsorship tiers for sponsors to choose from. Each tier has its own monthly payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. +You can create up to ten sponsorship tiers for sponsors to choose from. Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). -Once you have published a tier, you can't edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier or cancel their sponsorship. +Once you have published a tier, you can't edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/ru-RU/data/reusables/support/accessing-premium-content.md b/translations/ru-RU/data/reusables/support/accessing-premium-content.md index 95aae9361d..36beb80ba8 100644 --- a/translations/ru-RU/data/reusables/support/accessing-premium-content.md +++ b/translations/ru-RU/data/reusables/support/accessing-premium-content.md @@ -1,4 +1,4 @@ ### Accessing premium content -You can access premium content by signing in to the {% data variables.contact.contact_enterprise_portal %}. +You can access premium content by signing in to the {% data variables.contact.contact_landing_page_portal %}. diff --git a/translations/ru-RU/data/reusables/support/contacting-premium-support.md b/translations/ru-RU/data/reusables/support/contacting-premium-support.md index c3e8440e39..5e11eb52c6 100644 --- a/translations/ru-RU/data/reusables/support/contacting-premium-support.md +++ b/translations/ru-RU/data/reusables/support/contacting-premium-support.md @@ -1,4 +1,4 @@ ### Contacting {% data variables.contact.premium_support %} -{% data variables.contact.premium_support %} customers can use the {% data variables.contact.contact_enterprise_portal %} to report issues in writing, in English. You can also receive English-language support over the phone. For the {% data variables.contact.premium_support %} phone number, see "[24x7 Phone Support](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)" in the {% data variables.contact.enterprise_portal %}. +{% data variables.contact.premium_support %} customers can use the {% data variables.contact.contact_landing_page_portal %} to report issues in writing, in English. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/user_settings/billing_plans.md b/translations/ru-RU/data/reusables/user_settings/billing_plans.md new file mode 100644 index 0000000000..8d26ab1479 --- /dev/null +++ b/translations/ru-RU/data/reusables/user_settings/billing_plans.md @@ -0,0 +1 @@ +1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png) diff --git a/translations/ru-RU/data/variables/contact.yml b/translations/ru-RU/data/variables/contact.yml index 890e996840..6af47c26ee 100644 --- a/translations/ru-RU/data/variables/contact.yml +++ b/translations/ru-RU/data/variables/contact.yml @@ -24,9 +24,12 @@ contact_enterprise_portal: '[GitHub Enterprise Support portal](https://enterpris #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)' -#GitHub Support portal (for dotcom) +#GitHub Support portal (for dotcom - this sends users to a contact form) support_portal: 'GitHub Support portal' contact_support_portal: '[GitHub Support portal](https://support.github.com/contact)' +#GitHub Support portal (this sends users to the Support landing page) +landing_page_portal: 'GitHub Support portal' +contact_landing_page_portal: '[GitHub Support portal](https://support.github.com/)' #The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) community_support: 'GitHub Community Support' #The GitHub Community forum 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 a78995dc86..5bc74668f1 100644 --- a/translations/zh-CN/content/actions/creating-actions/about-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/about-actions.md @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概述' topics: - - 操作开发 - - 基础 + - '操作开发' + - '基础' --- {% 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 323e263e58..1cb95e4c2b 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 @@ -1,14 +1,14 @@ --- title: 创建组合运行步骤操作 -intro: 在本指南中，您将学习如何构建组合运行步骤操作。 +intro: '在本指南中，您将学习如何构建组合运行步骤操作。' product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 操作开发 + - '操作开发' --- {% data reusables.actions.enterprise-beta %} 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 fdda87309a..f94c52a715 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 @@ -1,6 +1,6 @@ --- title: 创建 Docker 容器操作 -intro: 本指南向您展示构建 Docker 容器操作所需的最少步骤。 +intro: '本指南向您展示构建 Docker 容器操作所需的最少步骤。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-docker-container-action @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 操作开发 - - Docker + - '操作开发' + - 'Docker' --- {% 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 bbd71cb04a..17f61e7996 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 @@ -1,6 +1,6 @@ --- title: 创建 JavaScript 操作 -intro: 在本指南中，您将了解如何使用操作工具包构建 JavaScript 操作。 +intro: '在本指南中，您将了解如何使用操作工具包构建 JavaScript 操作。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/creating-a-javascript-action @@ -11,10 +11,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 操作开发 - - JavaScript + - '操作开发' + - 'JavaScript' --- {% 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 882bb4709c..af3c907e4c 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 @@ -1,7 +1,7 @@ --- title: Dockerfile 对 GitHub Actions 的支持 shortTitle: Docker -intro: 为 Docker 容器创建 `Dockerfile` 时， 您应该知道一些 Docker 指令如何与 GitHub Actions 及操作的元数据文件交互。 +intro: '为 Docker 容器创建 `Dockerfile` 时， 您应该知道一些 Docker 指令如何与 GitHub Actions 及操作的元数据文件交互。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/building-actions/dockerfile-support-for-github-actions @@ -9,7 +9,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: '引用' --- {% data reusables.actions.enterprise-beta %} 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 c3cbd271aa..42b2be132c 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 @@ -12,7 +12,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: reference +type: '引用' --- {% data reusables.actions.enterprise-beta %} @@ -58,7 +58,7 @@ inputs: 在指定工作流程文件中某个操作的输入或者使用默认输入值时，{% data variables.product.prodname_dotcom %} 将为名称为 `INPUT_` 的输入创建环境变量。 创建的环境变量将输入名称转换为大写，并将空格替换为 `_` 字符。 -例如，如果工作流程定义了 numOctocats and octocatEyeColor 输入，操作代码可使用 `INPUT_NUMOCTOCATS` 和 `INPUT_OCTOCATEYECOLOR` 环境变量读取输入的值。 +例如，如果工作流程定义了 `numOctocats` 和 `octocatEyeColor` 输入，操作代码可使用 `INPUT_NUMOCTOCATS` 和 `INPUT_OCTOCATEYECOLOR` 环境变量读取输入的值。 #### `inputs.` @@ -76,6 +76,10 @@ inputs: **可选** 表示默认值的 `string`。 当工作流程文件中未指定输入参数时使用默认值。 +#### `inputs..deprecationMessage` + +**可选** 如果使用输入参数，此 `string` 将记录为警告消息。 您可以使用此警告通知用户输入已被弃用，并提及任何其他替代方式。 + ### `outputs` **可选** 输出参数允许您声明操作所设置的数据。 稍后在工作流程中运行的操作可以使用以前运行操作中的输出数据集。 例如，如果有操作执行两个输入的相加 (x + y = z)，则该操作可能输出总和 (z)，用作其他操作的输入。 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 5ee706c56a..c0d4693e97 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 @@ -9,9 +9,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概述' topics: - - 打包 + - '打包' --- {% 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 2265f4dec7..eb0a4bf155 100644 --- a/translations/zh-CN/content/actions/guides/about-service-containers.md +++ b/translations/zh-CN/content/actions/guides/about-service-containers.md @@ -1,6 +1,6 @@ --- title: 关于服务容器 -intro: 您可以使用服务容器将数据库、网络服务、内存缓存及其他工具连接到您的工作流程。 +intro: '您可以使用服务容器将数据库、网络服务、内存缓存及其他工具连接到您的工作流程。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/automating-your-workflow-with-github-actions/about-service-containers @@ -9,10 +9,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概述' topics: - - Containers - - Docker + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md b/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md index 6903851ca3..b1b7dbb421 100644 --- a/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md +++ b/translations/zh-CN/content/actions/guides/adding-labels-to-issues.md @@ -1,15 +1,15 @@ --- title: 向议题添加标签 -intro: '您可以使用 {% data variables.product.prodname_actions %} 自动标记议题。' +intro: 您可以使用 {% data variables.product.prodname_actions %} 自动标记议题。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 - - 项目管理 + - '工作流程' + - '项目管理' --- {% 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 8c404d16f8..bff8901b19 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CI - - Java - - Ant + - 'CI' + - 'Java' + - 'Ant' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Ant run: ant -noinput -buildfile build.xml ``` @@ -70,7 +71,7 @@ jobs: 此工作流程执行以下步骤： 1. `checkout` 步骤在运行器上下载仓库的副本。 -2. `setup-java` 步骤配置 Java 1.8 JDK。 +2. `setup-java` 步骤配置 Adoptium 的 Java 11 JDK。 3. “使用 Ant 构建”步骤以非交互模式运行 `build.xml` 中的默认目标。 在创建构建和测试工作流程时，默认工作流模板是很好的起点，然后您可以自定义模板以满足项目的需求。 @@ -91,9 +92,10 @@ jobs: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Ant jar target run: ant -noinput -buildfile build-ci.xml jar ``` @@ -109,7 +111,11 @@ Ant 通常会在 `build/jar` 目录中创建 JAR、EAR 或 WAR 等输出文件 ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ant -noinput -buildfile build.xml - uses: actions/upload-artifact@v2 with: 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 566f5b5b96..e850e0bdb4 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CI - - Java - - Gradle + - 'CI' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Gradle run: ./gradlew build ``` @@ -70,7 +71,7 @@ jobs: 此工作流程执行以下步骤： 1. `checkout` 步骤在运行器上下载仓库的副本。 -2. `setup-java` 步骤配置 Java 1.8 JDK。 +2. `setup-java` 步骤配置 Adoptium 的 Java 11 JDK。 3. “使用 Gradle 构建”步骤运行 `gradlew` wrapper 脚本以确保可以创建您的代码构建、测试通过和包。 在创建构建和测试工作流程时，默认工作流模板是很好的起点，然后您可以自定义模板以满足项目的需求。 @@ -91,9 +92,10 @@ jobs: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Gradle package task run: ./gradlew -b ci.gradle package ``` @@ -107,10 +109,11 @@ steps: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Gradle packages uses: actions/cache@v2 with: @@ -143,7 +146,11 @@ Gradle 通常会在 `build/libs` 目录中创建 JAR、EAR 或 WAR 等输出文 ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' + - run: ./gradlew build - uses: actions/upload-artifact@v2 with: 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 3475caee06..6b68e636a0 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 @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CI - - Java - - Maven + - 'CI' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -58,10 +58,11 @@ jobs: steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Build with Maven run: mvn --batch-mode --update-snapshots verify ``` @@ -70,7 +71,7 @@ jobs: 此工作流程执行以下步骤： 1. `checkout` 步骤在运行器上下载仓库的副本。 -2. `setup-java` 步骤配置 Java 1.8 JDK。 +2. `setup-java` 步骤配置 Adoptium 的 Java 11 JDK。 3. “使用 Maven 构建”步骤以非交互模式运行 Maven `package` 目标，以确保创建代码版本、测试通行证和软件包。 在创建构建和测试工作流程时，默认工作流模板是很好的起点，然后您可以自定义模板以满足项目的需求。 @@ -91,9 +92,10 @@ jobs: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Run the Maven verify phase run: mvn --batch-mode --update-snapshots verify ``` @@ -107,10 +109,11 @@ steps: ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 1.8 - uses: actions/setup-java@v1 + - name: Set up JDK 11 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Cache Maven packages uses: actions/cache@v2 with: @@ -134,7 +137,10 @@ Maven 通常会在 `target` 目录中创建 JAR、EAR 或 WAR 等输出文件。 ```yaml{:copy} steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 + with: + java-version: '11' + distribution: 'adopt' - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 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 index 222e7d2d66..964e2201ed 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-net.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-net.md @@ -44,7 +44,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: ['3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -81,7 +81,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet: [ '2.2.103', '3.0', '3.1.x' ] + dotnet: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 @@ -201,7 +201,7 @@ jobs: runs-on: ubuntu-latest strategy: matrix: - dotnet-version: [ '2.2.103', '3.0', '3.1.x' ] + dotnet-version: [ '3.0', '3.1.x', '5.0.x' ] steps: - uses: actions/checkout@v2 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 1aa2fb5168..2d56cafe6e 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 @@ -9,11 +9,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CI - - Node - - JavaScript + - 'CI' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} 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 b5ed0d049a..7bf667d7a1 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 @@ -8,10 +8,10 @@ versions: github-ae: '*' authors: - potatoqualitee -type: tutorial +type: '教程' topics: - - CI - - Powershell + - 'CI' + - 'Powershell' --- {% 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 46766392f2..dc48623298 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 @@ -8,10 +8,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CI - - Python + - 'CI' + - 'Python' --- {% data reusables.actions.enterprise-beta %} 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 6893e41a07..fad8f0bdf4 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 @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CI - - Ruby + - 'CI' + - 'Ruby' --- {% 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 2cf01cff0f..2a1a38cc1d 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 @@ -1,7 +1,7 @@ --- title: 缓存依赖项以加快工作流程 shortTitle: 缓存依赖项 -intro: 为了使工作流程更快、更高效，可以为依赖项及其他经常重复使用的文件创建和使用缓存。 +intro: '为了使工作流程更快、更高效，可以为依赖项及其他经常重复使用的文件创建和使用缓存。' product: '{% data reusables.gated-features.actions %}' redirect_from: - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows @@ -9,9 +9,9 @@ redirect_from: - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows versions: free-pro-team: '*' -type: tutorial +type: '教程' topics: - - 工作流程 + - '工作流程' --- {% data reusables.actions.ae-beta %} diff --git a/translations/zh-CN/content/actions/guides/closing-inactive-issues.md b/translations/zh-CN/content/actions/guides/closing-inactive-issues.md index 578e3a14d5..f646469914 100644 --- a/translations/zh-CN/content/actions/guides/closing-inactive-issues.md +++ b/translations/zh-CN/content/actions/guides/closing-inactive-issues.md @@ -1,15 +1,15 @@ --- title: 关闭不活跃的议题 -intro: '您可以使用 {% data variables.product.prodname_actions %} 评论或关闭在一定时间内未活动的议题。' +intro: 您可以使用 {% data variables.product.prodname_actions %} 评论或关闭在一定时间内未活动的议题。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 - - 项目管理 + - '工作流程' + - '项目管理' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md b/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md index 69578db5d0..a911ab5912 100644 --- a/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/zh-CN/content/actions/guides/commenting-on-an-issue-when-a-label-is-added.md @@ -1,15 +1,15 @@ --- title: 添加标签时评论议题 -intro: '您可以使用 {% data variables.product.prodname_actions %} 在应用特定标签时自动评论议题。' +intro: 您可以使用 {% data variables.product.prodname_actions %} 在应用特定标签时自动评论议题。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 - - 项目管理 + - '工作流程' + - '项目管理' --- {% data reusables.actions.enterprise-beta %} 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 8bd3d9335d..c622e4c343 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - Containers - - Docker + - 'Containers' + - 'Docker' --- {% 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 7b7b551842..5948e2380e 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 @@ -10,10 +10,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - Containers - - Docker + - 'Containers' + - 'Docker' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md index c2daf51adb..ebd50be6ed 100644 --- a/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/zh-CN/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CD - - Containers - - Amazon ECS + - 'CD' + - 'Containers' + - 'Amazon ECS' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md b/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md index 71d79b5f6a..ee90eecad9 100644 --- a/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/zh-CN/content/actions/guides/deploying-to-azure-app-service.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CD - - Containers - - Azure App Service + - 'CD' + - 'Containers' + - 'Azure App Service' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md index 880d8a6e45..8de9bf2299 100644 --- a/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/zh-CN/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -6,11 +6,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CD - - Containers - - Google Kubernetes Engine + - 'CD' + - 'Containers' + - 'Google Kubernetes Engine' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/zh-CN/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 3820b0efb2..fbca8cac7c 100644 --- a/translations/zh-CN/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/zh-CN/content/actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -6,10 +6,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CI - - Xcode + - 'CI' + - 'Xcode' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/moving-assigned-issues-on-project-boards.md b/translations/zh-CN/content/actions/guides/moving-assigned-issues-on-project-boards.md index aae772364a..f24e0201be 100644 --- a/translations/zh-CN/content/actions/guides/moving-assigned-issues-on-project-boards.md +++ b/translations/zh-CN/content/actions/guides/moving-assigned-issues-on-project-boards.md @@ -1,15 +1,15 @@ --- title: 在项目板上移动分配的议题 -intro: '您可以使用 {% data variables.product.prodname_actions %} 在议题被分配时自动将议题移到项目板上的特定列。' +intro: 您可以使用 {% data variables.product.prodname_actions %} 在议题被分配时自动将议题移到项目板上的特定列。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 - - 项目管理 + - '工作流程' + - '项目管理' --- {% data reusables.actions.enterprise-beta %} 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 45f69baea5..05aeb5f848 100644 --- a/translations/zh-CN/content/actions/guides/publishing-docker-images.md +++ b/translations/zh-CN/content/actions/guides/publishing-docker-images.md @@ -8,11 +8,11 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 打包 - - 发布 - - Docker + - '打包' + - '发布' + - 'Docker' --- {% 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 ebc6157ccf..67a0c42347 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 打包 - - 发布 - - Java - - Gradle + - '打包' + - '发布' + - 'Java' + - 'Gradle' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -143,9 +144,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: gradle publish env: @@ -209,9 +211,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to the Maven Central Repository run: gradle publish env: 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 e08883d974..9f430d7da9 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 @@ -8,12 +8,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 打包 - - 发布 - - Java - - Maven + - '打包' + - '发布' + - 'Java' + - 'Maven' --- {% data reusables.actions.enterprise-beta %} @@ -85,9 +85,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -147,9 +148,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - uses: actions/setup-java@v1 + - uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish package run: mvn --batch-mode deploy env: @@ -183,9 +185,10 @@ jobs: steps: - uses: actions/checkout@v2 - name: Set up Java for publishing to Maven Central Repository - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD @@ -195,9 +198,10 @@ jobs: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - uses: actions/setup-java@v1 + uses: actions/setup-java@v2 with: - java-version: 1.8 + java-version: '11' + distribution: 'adopt' - name: Publish to GitHub Packages run: mvn --batch-mode deploy env: 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 2ee15e80fa..c01e9da6f0 100644 --- a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md @@ -9,12 +9,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 打包 - - 发布 - - Node - - JavaScript + - '打包' + - '发布' + - 'Node' + - 'JavaScript' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index 01d30cf373..b39906fcc7 100644 --- a/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/zh-CN/content/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -1,15 +1,15 @@ --- title: 将卡片添加到项目板列时删除标签 -intro: '您可以使用 {% data variables.product.prodname_actions %} 在议题或拉取请求添加到项目板上的特定列时自动删除标签。' +intro: 您可以使用 {% data variables.product.prodname_actions %} 在议题或拉取请求添加到项目板上的特定列时自动删除标签。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 - - 项目管理 + - '工作流程' + - '项目管理' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md b/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md index 3546613d91..cbb20bf9ce 100644 --- a/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md +++ b/translations/zh-CN/content/actions/guides/scheduling-issue-creation.md @@ -1,15 +1,15 @@ --- title: 计划议题的创建 -intro: '您可以使用 {% data variables.product.prodname_actions %} 定期为日常会议或季度审查等事项创建议题。' +intro: 您可以使用 {% data variables.product.prodname_actions %} 定期为日常会议或季度审查等事项创建议题。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 - - 项目管理 + - '工作流程' + - '项目管理' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 3c4fbf8624..cede30f36c 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 @@ -12,10 +12,10 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 - - CI + - '工作流程' + - 'CI' --- {% 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 d593023f6e..bf5562ead8 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 @@ -12,9 +12,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - 工作流程 + - '工作流程' --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/using-github-actions-for-project-management.md b/translations/zh-CN/content/actions/guides/using-github-actions-for-project-management.md index 8551ea106e..6ea1fb01e8 100644 --- a/translations/zh-CN/content/actions/guides/using-github-actions-for-project-management.md +++ b/translations/zh-CN/content/actions/guides/using-github-actions-for-project-management.md @@ -1,14 +1,14 @@ --- title: 使用 GitHub Actions 进行项目管理 -intro: '您可以使用 {% data variables.product.prodname_actions %} 自动化许多项目管理任务。' +intro: 您可以使用 {% data variables.product.prodname_actions %} 自动化许多项目管理任务。 product: '{% data reusables.gated-features.actions %}' versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概述' topics: - - 项目管理 + - '项目管理' --- 您可以创建工作流程以使用 {% data variables.product.prodname_actions %} 自动化项目管理任务。 每个工作流程都包含一系列任务，每当工作流程运行时都会自动执行。 例如，您可以创建一个工作流程，在每次创建议题时运行，以添加标签、 留下评论并将议题移动到项目板。 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 158485714c..cfdb1018b2 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概述' --- {% data reusables.actions.ae-self-hosted-runners-notice %} @@ -125,7 +125,7 @@ type: overview 例如，如果你的实例名称是 `octoghie`，则需要允许自托管运行器访问 `octoghe. ithub.com`。 如果您对 -{% data variables.product.prodname_dotcom %} 组织或企业帐户使用 IP 地址允许列表，必须将自托管运行器的 IP 地址添加到允许列表。 更多信息请参阅“[管理组织允许的 IP 地址](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)”。 +{% data variables.product.prodname_dotcom %} 组织或企业帐户使用 IP 地址允许列表，必须将自托管运行器的 IP 地址添加到允许列表。 更多信息请参阅“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)”。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} @@ -145,7 +145,7 @@ pkg-containers.githubusercontent.com pkg-containers-az.githubusercontent.com ``` -如果您对 {% data variables.product.prodname_dotcom %} 组织或企业帐户使用 IP 地址允许列表，必须将自托管运行器的 IP 地址添加到允许列表。 更多信息请参阅“[管理组织允许的 IP 地址](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)”或“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)”。 +如果您对 {% data variables.product.prodname_dotcom %} 组织或企业帐户使用 IP 地址允许列表，必须将自托管运行器的 IP 地址添加到允许列表。 更多信息请参阅“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)”或“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)”。 {% else %} 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 b949e2be9a..6b595a07a8 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,15 +7,18 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' + github-ae: '*' +type: '教程' --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} 您可以将自托管的运行器添加到 {{ 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)”。 @@ -57,7 +60,7 @@ If you are an organization or enterprise administrator, you might want to add yo {% if currentVersion == "free-pro-team@latest" %} 要将自托管的运行器添加到企业帐户，您必须是组织所有者。 -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21"%} +{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} 要在 {% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是网站管理员。 {% endif %} @@ -72,10 +75,10 @@ If you are an organization or enterprise administrator, you might want to add yo {% 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)." +有关更改运行器组访问设置的更多信息，请参阅“[使用组管理对自托管运行器的访问](/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 a9bb648693..3bd60bcb92 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' 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 9ec4cace60..75f34a9f56 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 accca577db..cb89d66a4d 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,12 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' + github-ae: '*' +type: '教程' defaultPlatform: linux --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### 使用 {{ site.data.variables.product.prodname_dotcom }} 检查自托管运行器的状态 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 aa465e5264..655f913c54 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 11e3a28eea..0038132a07 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 @@ -7,7 +7,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 108b02aa7e..9d832114a0 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 @@ -5,7 +5,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' --- {% data reusables.actions.ae-self-hosted-runners-notice %} 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 fc3aeddd37..ec77881b31 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 @@ -1,6 +1,6 @@ --- title: 在工作流程中使用自托管的运行器 -intro: 要在工作流程中使用自托管的运行器，您可以使用标签为作业指定运行器类型。 +intro: '要在工作流程中使用自托管的运行器，您可以使用标签为作业指定运行器类型。' 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 @@ -8,7 +8,7 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' --- {% data reusables.actions.ae-self-hosted-runners-notice %} diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md index f30ba6242c..5705abbf42 100644 --- a/translations/zh-CN/content/actions/index.md +++ b/translations/zh-CN/content/actions/index.md @@ -22,8 +22,8 @@ featuredLinks: - /actions/reference/environment-variables - /actions/reference/encrypted-secrets changelog: - label: 'actions' - prefix: 'GitHub Actions: ' + label: '操作' + prefix: 'GitHub 操作:' product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU redirect_from: - /articles/automating-your-workflow-with-github-actions/ 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 694dac19c1..b7298617e2 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 @@ -6,9 +6,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概述' topics: - - 基础 + - '基础' --- {% data reusables.actions.enterprise-beta %} 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 3b9ff66fcd..59d79b5c69 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 @@ -10,9 +10,9 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: overview +type: '概述' topics: - - 基础 + - '基础' --- {% data reusables.actions.enterprise-beta %} 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 d80d7fb120..a6b9cbf2ac 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 @@ -1,52 +1,59 @@ --- -title: Migrating from Azure Pipelines to GitHub Actions -intro: '{% data variables.product.prodname_actions %} and Azure Pipelines share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.' +title: 从 Azure Pelines 迁移到 GitHub Actions +intro: '{% data variables.product.prodname_actions %} 和 Azure Pipelines 具有一些相似的配置，这使得迁移到 {% data variables.product.prodname_actions %} 很简单。' redirect_from: - /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'tutorial' + github-ae: '*' +type: '教程' +topics: + - 'Azure Pipelines' + - '迁移' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### Introduction +### 简介 -Azure Pipelines and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. Azure Pipelines and {% data variables.product.prodname_actions %} share some similarities in workflow configuration: +Azure Pipelines 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 Azure Pelines 和 {% data variables.product.prodname_actions %} 的工作流程配置有一些相似之处： -- Workflow configuration files are written in YAML and are stored in the code's repository. -- Workflows include one or more jobs. -- Jobs include one or more steps or individual commands. -- Steps or tasks can be reused and shared with the community. +- 工作流程配置文件以 YAML 编写并存储在代码仓库中。 +- 工作流程包括一项或多项作业。 +- 作业包括一个或多个步骤或单个命令。 +- 步骤或任务可以重复使用并与社区共享。 -For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)." +更多信息请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)”。 -### Key differences +### 主要差异 -When migrating from Azure Pipelines, consider the following differences: +从 Azure Pipelines 迁移时，考虑以下差异： -- Azure Pipelines supports a legacy _classic editor_, which lets you define your CI configuration in a GUI editor instead of creating the pipeline definition in a YAML file. {% data variables.product.prodname_actions %} uses YAML files to define workflows and does not support a graphical editor. -- Azure Pipelines allows you to omit some structure in job definitions. For example, if you only have a single job, you don't need to define the job and only need to define its steps. {% data variables.product.prodname_actions %} requires explicit configuration, and YAML structure cannot be omitted. -- Azure Pipelines supports _stages_ defined in the YAML file, which can be used to create deployment workflows. {% data variables.product.prodname_actions %} requires you to separate stages into separate YAML workflow files. -- On-premises Azure Pipelines build agents can be selected with capabilities. {% data variables.product.prodname_actions %} self-hosted runners can be selected with labels. +- Azure Pelines 支持传统的_经典编辑器_，可让您在 GUI 编辑器中定义 CI 配置，而不是在 YAML 文件中创建管道定义。 {% data variables.product.prodname_actions %} 使用 YAML 文件来定义工作流程，不支持图形编辑器。 +- Azure Pelines 允许您在作业定义中省略一些结构。 例如，如果您只有一个作业，则无需定义作业，只需要定义其步骤。 {% data variables.product.prodname_actions %} 需要明确的配置，且不能省略 YAML 结构。 +- Azure Pipelines 支持 YAML 文件中定义的_阶段_，可用于创建部署工作流程。 {% data variables.product.prodname_actions %} 要求您将阶段分成单独的 YAML 工作流程文件。 +- 可以使用功能选择本地 Azure Pipelines 构建代理。 通过标签可以选择 {% data variables.product.prodname_actions %} 自托管的运行器。 -### Migrating jobs and steps +### 迁移作业和步骤 -Jobs and steps in Azure Pipelines are very similar to jobs and steps in {% data variables.product.prodname_actions %}. In both systems, jobs have the following characteristics: +Azure Pelines 中的作业和步骤非常类似于 {% data variables.product.prodname_actions %} 中的作业和步骤。 在这两个系统中，作业具有以下特征： -* Jobs contain a series of steps that run sequentially. -* Jobs run on separate virtual machines or in separate containers. -* Jobs run in parallel by default, but can be configured to run sequentially. +* 作业包含一系列按顺序运行的步骤。 +* 作业在单独的虚拟机或单独的容器中运行。 +* 默认情况下作业并行运行，但可以配置为按顺序运行。 -### Migrating script steps +### 迁移脚本步骤 -You can run a script or a shell command as a step in a workflow. In Azure Pipelines, script steps can be specified using the `script` key, or with the `bash`, `powershell`, or `pwsh` keys. Scripts can also be specified as an input to the [Bash task](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops) or the [PowerShell task](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops). +可以将脚本或 shell 命令作为工作流程中的步骤运行。 在 Azure Pipelines 中，脚本步骤可以使用 `script` 键指定，或者使用 `bash`、`powershell` 或 `pwsh` 键指定。 脚本也可以指定为 [Bash 任务](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops)或 [PowerShell 任务](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops)的输入。 -In {% data variables.product.prodname_actions %}, all scripts are specified using the `run` key. To select a particular shell, you can specify the `shell` key when providing the script. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)." +在 {% data variables.product.prodname_actions %} 中，所有脚本都使用 `run` 键来指定。 要选择特定的 shell，您可以在提供脚本时指定 `shell` 键。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。 -Below is an example of the syntax for each system: +下面是每个系统的语法示例： @@ -62,16 +69,16 @@ Azure Pipelines {% 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" + - 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 %} @@ -82,32 +89,32 @@ 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 + - 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 %}
-### Differences in script error handling +### 脚本错误处理中的差异 -In Azure Pipelines, scripts can be configured to error if any output is sent to `stderr`. {% data variables.product.prodname_actions %} does not support this configuration. +在 Azure Pipelines 中，脚本可配置为有任何输出发送到 `stderr` 时出错。 {% data variables.product.prodname_actions %} 不支持此配置。 -{% data variables.product.prodname_actions %} configures shells to "fail fast" whenever possible, which stops the script immediately if one of the commands in a script exits with an error code. In contrast, Azure Pipelines requires explicit configuration to exit immediately on an error. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)." +{% data variables.product.prodname_actions %} 尽可能将 shell 配置为“快速失败”，如果脚本中的一个命令退出并有错误代码，则会立即停止脚本。 相反，Azure Pipelines 需要明确配置为在出错时立即退出。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)”。 -### Differences in the default shell on Windows +### Windows 上默认 shell 的差异 -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. +在 Azure Pelines 中，Windows 平台上脚本的默认 shell 是命令 shell (_cmd.exe_)。 在 {% data variables.product.prodname_actions %} 中，Windows 平台上脚本的默认 shell 是 PowerShell 。 PowerShell 在内置命令、变量扩展和流控制方面存在若干差异。 -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`. +如果您运行的是简单的命令，则可以在 PowerShell 中运行命令 shell 脚本，而无需进行任何更改。 但在大多数情况下，您需要使用 PowerShell 语法更新脚本，或者指示 {% data variables.product.prodname_actions %} 使用命令 shell 而不是 PowerShell 来运行脚本。 您可以通过将 `shell` 指定为 `Cmd` 来完成。 -Below is an example of the syntax for each system: +下面是每个系统的语法示例： @@ -123,11 +130,11 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_command - pool: - vmImage: 'windows-latest' - steps: - - script: echo "This step runs in CMD on Windows by default" + - job: run_command + pool: + vmImage: 'windows-latest' + steps: + - script: echo "This step runs in CMD on Windows by default" ``` {% endraw %} @@ -138,24 +145,24 @@ 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 + - run: echo "This step runs in PowerShell on Windows by default" + - run: echo "This step runs in CMD on Windows explicitly" + shell: cmd ``` {% endraw %}
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)." +更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)”。 -### Migrating conditionals and expression syntax +### 迁移条件和表达式语法 -Azure Pipelines and {% data variables.product.prodname_actions %} can both run steps conditionally. In Azure Pipelines, conditional expressions are specified using the `condition` key. In {% data variables.product.prodname_actions %}, conditional expressions are specified using the `if` key. +Azure Pipelines 和 {% data variables.product.prodname_actions %} 可以有条件地运行步骤。 在 Azure Pipelines 中，使用 `condition` 键指定条件表达式。 在 {% data variables.product.prodname_actions %} 中，条件表达式使用 `if` 键来指定。 -Azure Pipelines uses functions within expressions to execute steps conditionally. In contrast, {% data variables.product.prodname_actions %} uses an infix notation. For example, you must replace the `eq` function in Azure Pipelines with the `==` operator in {% data variables.product.prodname_actions %}. +Azure Pelines 使用表达式中的函数来有条件地执行步骤。 相反，{% data variables.product.prodname_actions %} 使用 infix 表示法。 例如，必须将 Azure Pipelines 中的 `eq` 函数替换为 {% data variables.product.prodname_actions %} 中的 `==` 运算符。 -Below is an example of the syntax for each system: +下面是每个系统的语法示例： @@ -171,12 +178,12 @@ Azure Pipelines {% 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)) + - 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 %} @@ -187,21 +194,21 @@ 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 }} + - run: echo "This step runs with str equals 'ABC' and num equals 123" + if: ${{ env.str == 'ABC' && env.num == 123 }} ``` {% endraw %}
-For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)." +更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 -### Dependencies between jobs +### 作业之间的依赖关系 -Both Azure Pipelines and {% data variables.product.prodname_actions %} allow you to set dependencies for a job. In both systems, jobs run in parallel by default, but job dependencies can be specified explicitly. In Azure Pipelines, this is done with the `dependsOn` key. In {% data variables.product.prodname_actions %}, this is done with the `needs` key. +Azure Pipelines 和 {% data variables.product.prodname_actions %} 允许您为作业设置依赖项。 在这两个系统中，默认情况下作业并行运行，但可以明确指定作业依赖项。 在 Azure Pipelines 中，这通过 `dependsOn` 键来完成。 在 {% data variables.product.prodname_actions %} 中，这通过 `needs` 键来完成。 -Below is an example of the syntax for each system. The workflows start a first job named `initial`, and when that job completes, two jobs named `fanout1` and `fanout2` will run. Finally, when those jobs complete, the job `fanin` will run. +下面是每个系统的语法示例： 工作流程启动第一个名为 `initial` 的作业，当该作业完成时，两个分别名为 `fanout1` 和 `fanout2` 的作业将会运行。 最后，当这些作业完成后，作业 `fanin` 将会运行。 @@ -217,29 +224,29 @@ Azure Pipelines {% 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." + - 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 %} @@ -250,35 +257,35 @@ jobs: initial: runs-on: ubuntu-latest steps: - - run: echo "This job will be run first." + - 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." + - 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." + - 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." + - run: echo "This job will run after fanout1 and fanout2 have finished." ``` {% endraw %}
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)." +更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)”。 -### Migrating tasks to actions +### 将任务迁移到操作 -Azure Pipelines uses _tasks_, which are application components that can be re-used in multiple workflows. {% data variables.product.prodname_actions %} uses _actions_, which can be used to perform tasks and customize your workflow. In both systems, you can specify the name of the task or action to run, along with any required inputs as key/value pairs. +Azure Pipelines 使用_任务_，这是可在多个工作流程中重复使用的应用程序组件。 {% data variables.product.prodname_actions %} 使用 _操作_，这可用于执行任务和自定义工作流程。 在这两个系统中，您可以指定要运行的任务或操作的名称，以及任何必需的输入作为键/值对。 -Below is an example of the syntax for each system: +下面是每个系统的语法示例： @@ -294,15 +301,15 @@ Azure Pipelines {% raw %} ```yaml jobs: -- job: run_python - pool: - vmImage: 'ubuntu-latest' - steps: - - task: UsePythonVersion@0 - inputs: - versionSpec: '3.7' - architecture: 'x64' - - script: python script.py + - job: run_python + pool: + vmImage: 'ubuntu-latest' + steps: + - task: UsePythonVersion@0 + inputs: + versionSpec: '3.7' + architecture: 'x64' + - script: python script.py ``` {% endraw %} @@ -313,15 +320,15 @@ jobs: run_python: runs-on: ubuntu-latest steps: - - uses: actions/setup-python@v2 - with: - python-version: '3.7' - architecture: 'x64' - - run: python script.py + - uses: actions/setup-python@v2 + with: + python-version: '3.7' + architecture: 'x64' + - run: python script.py ``` {% endraw %}
-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)." +您可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=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 f5a5fb86b8..f2cdb918fe 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 @@ -1,18 +1,18 @@ --- title: 从 CircleCI 迁移到 GitHub Actions -intro: GitHub Actions 和 CircleCI 在配置上具有若干相似之处，这使得迁移到 GitHub Actions 相对简单。 +intro: 'GitHub Actions 和 CircleCI 在配置上具有若干相似之处，这使得迁移到 GitHub Actions 相对简单。' redirect_from: - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - CircleCI - - 迁移 - - CI - - CD + - 'CircleCI' + - '迁移' + - 'CI' + - 'CD' --- {% 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 35a6b3f855..68a3065138 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 @@ -5,12 +5,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - GitLab - - 迁移 - - CI - - CD + - 'GitLab' + - '迁移' + - 'CI' + - 'CD' --- {% 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 c2255a62b7..c4aac91cfb 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - Jenkins - - 迁移 - - CI - - CD + - 'Jenkins' + - '迁移' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 1d0f5688c0..8de496bb7a 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 @@ -7,12 +7,12 @@ versions: free-pro-team: '*' enterprise-server: '>=2.22' github-ae: '*' -type: tutorial +type: '教程' topics: - - Travis CI - - 迁移 - - CI - - CD + - 'Travis CI' + - '迁移' + - 'CI' + - 'CD' --- {% data reusables.actions.enterprise-beta %} 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 c259cbf40a..a74a451907 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 @@ -1,5 +1,5 @@ --- -title: GitHub 操作的安全强化 +title: GitHub Actions 的安全强化 shortTitle: 安全强化 intro: '使用 {% data variables.product.prodname_actions %} 功能的良好安全实践。' product: '{% data reusables.gated-features.actions %}' @@ -8,13 +8,15 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'overview' + github-ae: '*' +type: '概述' topics: - '安全' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} ### 概览 @@ -22,7 +24,7 @@ topics: ### 使用密码 -敏感值绝不能以明文存储在工作流程文件中，而应存储为密码。 [密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)可在组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}、仓库或环境{% else %}或仓库{% endif %}级配置，可用于在 {% data variables.product.product_name %} 中存储敏感信息。 +敏感值绝不能以明文存储在工作流程文件中，而应存储为密码。 [密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)可在组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、仓库或环境{% else %}或仓库{% endif %}级配置，可用于在 {% data variables.product.product_name %} 中存储敏感信息。 密码使用 [Libsodium 密封箱](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)，以使它们在到达 {% data variables.product.product_name %} 前被加密处理。 [使用 UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) 或通过 [REST API](/rest/reference/actions#secrets) 提交密码时就会发生这种情况。 此客户端加密有助于最大程度地减少与 {% data variables.product.product_name %}基础架构中的意外日志记录相关的风险（例如，异常日志和请求日志等）。 密钥在上传后，{% data variables.product.product_name %} 可对其进行解密，以便它能够被注入工作流程运行时。 @@ -41,7 +43,7 @@ topics: - **审核并轮换注册密码** - 定期查查已注册的密码，以确认它们仍是必需的。 删除不再需要的密码。 - 定期轮换密码，以减小泄露的密码有效的时间窗。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} - **考虑要求对访问密码进行审查** - 您可以使用所需的审查者来保护环境机密。 在审查者批准之前，工作流程作业无法访问环境机密。 有关在环境中存储机密或需要审查环境的更多信息，请参阅“[加密秘密](/actions/reference/encrypted-secrets)”和“[环境](/actions/reference/environments)”。 {% endif %} @@ -75,7 +77,7 @@ topics: ### 考虑跨仓库访问 -{% data variables.product.product_name %} 的范围有意设为每次一个仓库。 `GITHUB_TOKEN` 授予与具有写入权限的用户相同的访问级别，因为任何具有写入权限的用户都可通过创建或修改工作流程文件来访问此令牌。 用户对每个仓库都有特定权限，因此，如果不谨慎实施，一个仓库的 `GITHUB_TOKEN` 库授予对另一个仓库的访问权限将会影响 {% data variables.product.prodname_dotcom %} 权限模型。 同样，在向工作流程添加 {% data variables.product.prodname_dotcom %} 授权令牌时也必须谨慎，因为这也会因无意中向协作者授予一般权限而影响 {% data variables.product.prodname_dotcom %} 权限模型。 +{% data variables.product.prodname_actions %} 的范围有意设为每次一个仓库。 `GITHUB_TOKEN` 授予与具有写入权限的用户相同的访问级别，因为任何具有写入权限的用户都可通过创建或修改工作流程文件来访问此令牌。 用户对每个仓库都有特定权限，因此，如果不谨慎实施，一个仓库的 `GITHUB_TOKEN` 库授予对另一个仓库的访问权限将会影响 {% data variables.product.prodname_dotcom %} 权限模型。 同样，在向工作流程添加 {% data variables.product.prodname_dotcom %} 授权令牌时也必须谨慎，因为这也会因无意中向协作者授予一般权限而影响 {% data variables.product.prodname_dotcom %} 权限模型。 我们已经[制定 {% data variables.product.prodname_dotcom %} 路线图](https://github.com/github/roadmap/issues/74)，以支持允许在 {% data variables.product.product_name %} 内跨仓库访问的流程，但这还不是一项受支持的功能。 目前，执行特权跨仓库交互的唯一方法就是将 {% data variables.product.prodname_dotcom %} 身份验证令牌或 SSH 密钥作为工作流程中的密码。 由于许多身份验证令牌类型不允许对特定资源进行细致的访问，因此使用错误的令牌类型存在很大风险，因为它可以授予比预期范围更广泛的访问。 @@ -115,33 +117,68 @@ topics: 您可以使用审核日志来监控组织中的管理任务。 审核日志记录操作类型、操作的运行时间以及执行操作的用户帐户。 -例如，您可以使用审核日志跟踪 `action:org.update_actions_secret` 事件，以跟踪组织机密的更改： ![审核日志条目](/assets/images/help/repository/audit-log-entries.png) +例如，您可以使用审核日志跟踪 `org.update_actions_secret` 事件，这些事件跟踪组织秘密的变化： ![审核日志条目](/assets/images/help/repository/audit-log-entries.png) -以下表格描述了您可以在审核日志中找到的 {% data variables.product.prodname_actions %} 事件。 有关使用审核日志的更多信息，请参阅“[查看组织的审核日志](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)”。 +以下表格描述了您可以在审核日志中找到的 {% data variables.product.prodname_actions %} 事件。 有关使用审核日志的更多信息，请参阅“[查看组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)”。 + +{% if currentVersion == "free-pro-team@latest" %} +#### 环境事件 + +| 操作 | 描述 | +| ----------------------------------- | ------------------------------------------------------------------------------------ | +| `environment.create_actions_secret` | 在环境中创建机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。 | +| `environment.delete` | 当环境被删除时触发。 更多信息请参阅“[删除环境](/actions/reference/environments#deleting-an-environment)”。 | +| `environment.remove_actions_secret` | 从环境中删除机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。 | +| `environment.update_actions_secret` | 当环境中的机密更新时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。 | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### 配置更改事件 +| 操作 | 描述 | +| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.actions_enabled` | 为仓库启用 {% data variables.product.prodname_actions %} 时触发。 可以使用用户界面查看。 当您使用 REST API 访问审计日志时，此事件不可见。 更多信息请参阅“[使用 REST API](#using-the-rest-api)”。 | +{% endif %} #### 机密管理的事件 -| 操作 | 描述 | -| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.create_actions_secret` | 组织管理员[创建 {% data variables.product.prodname_actions %} 机密](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)时触发。 | -| `action:org.remove_actions_secret` | 组织管理员删除 {% data variables.product.prodname_actions %} 机密时触发。 | -| `action:org.update_actions_secret` | 组织管理员更新 {% data variables.product.prodname_actions %} 机密时触发。 | -| `action:repo.create_actions_secret` | 仓库管理员[创建 {% data variables.product.prodname_actions %} 机密](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)时触发。 | -| `action:repo.remove_actions_secret` | 仓库管理员删除 {% data variables.product.prodname_actions %} 机密时触发。 | -| `action:repo.update_actions_secret` | 仓库管理员更新 {% data variables.product.prodname_actions %} 机密时触发。 | +| 操作 | 描述 | +| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org.create_actions_secret` | 为组织创建 {% data variables.product.prodname_actions %} 机密时触发。 更多信息请参阅“[为组织创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)”。 | +| `org.remove_actions_secret` | 当 {% data variables.product.prodname_actions %} 密码被移除时触发。 | +| `org.update_actions_secret` | 在 {% data variables.product.prodname_actions %} 密码更新时触发。 | +| `repo.create_actions_secret` | 为仓库创建 {% data variables.product.prodname_actions %} 密码时触发。 更多信息请参阅“[为仓库创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)”。 | +| `repo.remove_actions_secret` | 当 {% data variables.product.prodname_actions %} 密码被移除时触发。 | +| `repo.update_actions_secret` | 在 {% data variables.product.prodname_actions %} 密码更新时触发。 | #### 自托管运行器的事件 -| 操作 | 描述 | -| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| `action:org.register_self_hosted_runner` | 组织所有者[注册新的自托管运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)时触发。 | -| `action:org.remove_self_hosted_runner` | 组织所有者[删除自托管运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)时触发。 | -| `action:repo.register_self_hosted_runner` | 仓库管理员[注册新的自托管运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)时触发。 | -| `action:repo.remove_self_hosted_runner` | 仓库管理员[删除自托管运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)时触发。 | +| 操作 | 描述 | +| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% else %} | | +| `enterprise.register_self_hosted_runner` | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到企业](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)”。 | +| `enterprise.remove_self_hosted_runner` | 当自托管运行器被移除时触发。 | +| `enterprise.runner_group_runners_updated` | 当运行器组成员列表更新时触发。 更多信息请参阅“[为组织设置组中的自托管运行器](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)”。 | +| `enterprise.self_hosted_runner_updated` | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看。 当您将审核日志导出为 JSON 数据或 CSV 文件时，此事件不包括在内。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”和“[审查组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)”。{% endif %} +| `org.register_self_hosted_runner` | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到组织](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)”。 | +| `org.remove_self_hosted_runner` | 当自托管运行器被移除时触发。 更多信息请参阅“[从组织移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)”。 | +| `org.runner_group_runners_updated` | 当运行器组成员列表更新时触发。 更多信息请参阅“[为组织设置组中的自托管运行器](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)”。 | +| `org.runner_group_updated` | 当自托管运行器组的配置改变时触发。 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。 | +| `org.self_hosted_runner_updated` | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。 | +| `repo.register_self_hosted_runner` | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到仓库](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)”。 | +| `repo.remove_self_hosted_runner` | 当自托管运行器被移除时触发。 更多信息请参阅“[从仓库移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)”。 | +| `repo.self_hosted_runner_updated` | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。 | #### 自托管运行器组的事件 -| 操作 | 描述 | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `action:org.runner_group_created` | 组织管理员[删除自托管运行器](/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` | 组织管理员删除自托管运行器组时触发。 | -| `action:org.runner_group_renamed` | 组织管理员重命名自托管运行器组时触发。 | -| `action:org.runner_group_runners_added` | 组织管理员[添加自托管运行器到组](/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` | 组织管理员从组中删除自托管运行器时触发。 | +| 操作 | 描述 | +| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise.runner_group_created` | 在创建自托管运行器组时触发。 更多信息请参阅“[为企业创建自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)”。 | +| `enterprise.runner_group_removed` | 当自托管运行器组被移除时触发。 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。 | +| `enterprise.runner_group_runner_removed` | 当 REST API 用于从组中删除自托管运行器时触发。 | +| `enterprise.runner_group_runners_added` | 当自托管运行器添加到组时触发。 更多信息请参阅“[将自托管运行器移动到组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。 | +| `enterprise.runner_group_updated` | 当自托管运行器组的配置改变时触发。 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。 | +| `org.runner_group_created` | 在创建自托管运行器组时触发。 更多信息请参阅“[为组织创建自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)”。 | +| `org.runner_group_removed` | 当自托管运行器组被移除时触发。 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。 | +| `org.runner_group_runners_added` | 当自托管运行器添加到组时触发。 更多信息请参阅“[将自托管运行器移动到组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。 | +| `org.runner_group_runner_removed` | 当 REST API 用于从组中删除自托管运行器时触发。 更多信息请参阅“[为组织从组中删除自托管运行器](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)”。 | + +#### 工作流程活动事件 + +{% data reusables.actions.actions-audit-events-workflow %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md index 2b9f6be3fe..f8ee662b56 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -15,7 +15,7 @@ versions: 引用配置了所需审查者的环境的作业将等待审批后再开始。 当作业正在等待批准时，其状态为“等待”。 如果作业在 30 天内未获得批准，工作流程运行将自动取消。 -For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} +有关环境和必需批准的更多信息，请参阅“[环境](/actions/reference/environments)”。{% if currentversion == "free-proteam@latest" or currentversion == "github-ae@next" or currentversion ver_gt "enterprise-server@3. %} 有关如何使用 REST API 审查部署的信息，请参阅“[工作流程运行](/rest/reference/actions#workflow-runs)”。{% endif %} ### 批准或拒绝作业 diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index 76bbe4b06c..a80c0c499a 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -1,6 +1,6 @@ --- title: GitHub Actions 快速入门 -intro: '在 5 分钟或更短时间内将 {% data variables.product.prodname_actions %} 工作流程添加到现有仓库。' +intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.' allowTitleToDifferFromFilename: true redirect_from: - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates @@ -19,57 +19,58 @@ topics: ### 简介 -您只需要一个现有的 {% data variables.product.prodname_dotcom %} 仓库来创建和运行 {% data variables.product.prodname_actions %} 工作流程。 在本指南中，您将添加一个工作流程，使用 [{% data variables.product.prodname_dotcom %} Super-Linter 操作](https://github.com/github/super-linter)链接多种编码语言。 每次有新的提交被推送到您的仓库时，工作流程都会使用 Super-Linter 验证源代码。 +You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. + +The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository. ### 创建第一个工作流程 -1. 从 {% data variables.product.prodname_dotcom %} 上的仓库，在 `.github/workflows` 目录中创建一个名为 `superlinter.yml` 的新文件。 更多信息请参阅“[创建新文件](/github/managing-files-in-a-repository/creating-new-files)”。 -2. 将以下 YAML 内容复制到 `superlinter.yml` 文件中。 **注：** 如果您的默认分支不是 `main`，请更新 `DEFAULT_BRANCH` 的值以匹配您仓库的默认分支名称。 +1. 从 {% data variables.product.prodname_dotcom %} 上的仓库，在 `.github/workflows` 目录中创建一个名为 `github-actions-demo.yml` 的新文件。 更多信息请参阅“[创建新文件](/github/managing-files-in-a-repository/creating-new-files)”。 +2. Copy the following YAML contents into the `github-actions-demo.yml` file: {% raw %} ```yaml{:copy} - name: Super-Linter - - # Run this workflow every time a new commit pushed to your repository - on: push - + name: GitHub Actions Demo + 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 + Explore-GitHub-Actions: runs-on: ubuntu-latest - steps: - # Checks out a copy of your repository on the ubuntu-latest machine - - name: Checkout code + - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event." + - run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!" + - run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}." + - name: Check out repository code uses: actions/checkout@v2 + - run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner." + - run: echo "🖥️ The workflow is now ready to test your code on the runner." + - name: List files in the repository + run: | + ls ${{ github.workspace }} + - run: echo "🍏 This job's status is ${{ job.status }}." - # 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. 要运行您的工作流程， 滚动到页面底部，然后选择 **为此提交创建一个新分支并开始拉取请求**。 然后，若要创建拉取请求，请单击 **Propose new file（提议新文件）**。 ![提交工作流程文件](/assets/images/commit-workflow-file.png) +3. 滚动到页面底部，然后选择 **Create a new branch for this commit and start a pull request（为此提交创建一个新分支并开始拉取请求）**。 然后，若要创建拉取请求，请单击 **Propose new file（提议新文件）**。 ![提交工作流程文件](/assets/images/help/repository/actions-quickstart-commit-new-file.png) -在仓库中提交工作流程文件会触发 `push` 事件并运行工作流程。 +Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow. ### 查看工作流程结果 {% 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" or currentVersion == "github-ae@latest" %} -1. 在 **Jobs（作业）**下或可视化图中，单击 **Lint code base（Lint 代码基础）**作业。 ![Lint 代码库作业](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) -{% else %} -1. 在左侧边栏中，单击 **Lint code base（Lint 代码库）**作业。 ![Lint 代码库作业](/assets/images/help/repository/superlinter-lint-code-base-job.png) -{% endif %} -{% data reusables.repositories.view-failed-job-results-superlinter %} +1. 在左侧边栏中，单击您想要查看的工作流程。 + + ![左侧边栏中的工作流程列表](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png) +1. 从工作流程运行列表中，单击要查看的运行的名称。 + + ![工作流程运行的名称](/assets/images/help/repository/actions-quickstart-run-name.png) +1. Under **Jobs** , click the **Explore-GitHub-Actions** job. + + ![Locate job](/assets/images/help/repository/actions-quickstart-job.png) +1. The log shows you how each of the steps was processed. Expand any of the steps to view its details. + + ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png) + + For example, you can see the list of files in your repository: ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png) ### 更多工作流程模板 @@ -77,74 +78,12 @@ topics: ### 后续步骤 -每次将代码推送到仓库时，您刚添加的 super-linter 工作流程都会运行，以帮助您发现代码中的错误和不一致。 但是，这只是您可以对 {% data variables.product.prodname_actions %} 执行操作的开始。 您的仓库可以包含多个基于不同事件触发不同任务的工作流程。 {% data variables.product.prodname_actions %} 可以帮助您自动执行应用程序开发过程的几乎每个方面。 准备好开始了吗？ 以下是一些帮助您对 {% data variables.product.prodname_actions %} 执行后续操作的有用资源： +The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}: -- “[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”，以获取深入教程 -- “[指南](/actions/guides)”，以获取特定用例和示例 -- [github/super-linter](https://github.com/github/super-linter)，以获取有关配置 Super-Linter 操作的详细信息 +- 您的仓库可以包含多个基于不同事件触发不同任务的工作流程。 +- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners. - +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial. +- "[Guides](/actions/guides)" for specific uses cases and examples. diff --git a/translations/zh-CN/content/actions/reference/encrypted-secrets.md b/translations/zh-CN/content/actions/reference/encrypted-secrets.md index f7f502c99d..093ded47af 100644 --- a/translations/zh-CN/content/actions/reference/encrypted-secrets.md +++ b/translations/zh-CN/content/actions/reference/encrypted-secrets.md @@ -1,6 +1,6 @@ --- -title: Encrypted secrets -intro: Encrypted secrets allow you to store sensitive information in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environments{% else %} or repository{% endif %}. +title: 加密机密 +intro: 加密密码可让您将敏感信息存储在您的组织{% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@3. %}、仓库或者仓库环境{% else %} 或仓库{% endif %} 中。 product: '{% data reusables.gated-features.actions %}' redirect_from: - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets @@ -9,118 +9,125 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.environments-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### About encrypted secrets +### 关于加密密码 -Secrets are encrypted environment variables that you create in an organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environment{% else %} or repository{% endif %}. The secrets that you create are available to use in {% data variables.product.prodname_actions %} workflows. {% data variables.product.prodname_dotcom %} uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to help ensure that secrets are encrypted before they reach {% data variables.product.prodname_dotcom %} and remain encrypted until you use them in a workflow. +机密是您在组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、仓库或者仓库环境{% else %} 或仓库{% endif %} 中创建的加密环境变量。 您创建的机密可用于 {% data variables.product.prodname_actions %} 工作流程。 在机密到达 {% data variables.product.prodname_dotcom %} 之前，{% data variables.product.prodname_dotcom %} 使用 [libsodium 密封盒](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)对机密加密，并且在您于工作流程中使用它们之前一直保持加密状态。 {% data reusables.github-actions.secrets-org-level-overview %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -For secrets stored at the environment level, you can enable required reviewers to control access to the secrets. A workflow job cannot access environment secrets until approval is granted by required approvers. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +对于存储在环境级别的机密，您可以启用所需的审查者来控制对机密的访问。 在必要的审查者授予批准之前，工作流程作业无法访问环境机密。 {% endif %} -#### Naming your secrets +#### 命名您的密码 -The following rules apply to secret names: +以下规则适用于密码名称： -* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed. -* Secret names must not start with the `GITHUB_` prefix. -* Secret names must not start with a number. -* Secret names are not case-sensitive. -* Secret names must be unique at the level they are created at. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level. - - If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %} +* 密码名称只能包含字母数字字符（`[a-z]`、`[A-Z]`、`[0-9]`）或下划线 (`_`)。 不允许空格。 +* 密码名称不能以 `GITHUB_` 前缀开头。 +* 密码名称不能以数字开头。 +* 机密名称不区分大小写。 +* 密码名称在所创建的级别上必须是唯一的。 例如，{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}在环境级别创建的机密必须在环境中具有唯一的名称，{% endif %}在仓库级别创建的机密必须在该仓库中具有唯一的名称，而在组织级别创建的机密必须在该级别具有独特的名称。 -To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. For example, avoid creating secrets that contain JSON or encoded Git blobs. + 如果具有相同名称的机密存在于多个级别，则较低级别的机密优先。 例如，如果组织级机密与仓库级机密具有相同的名称，则仓库级机密优先。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} 同样，如果组织、仓库和环境都具有同名的机密，则环境级机密优先。{% endif %} -#### Accessing your secrets +为帮助确保 {% data variables.product.prodname_dotcom %} 在日志中编写密码，请勿将结构化数据用作密码的值。 例如，避免创建包含 JSON 或编码 Git blob 的密码。 -To make a secret available to an action, you must set the secret as an input or environment variable in the workflow file. Review the action's README file to learn about which inputs and environment variables the action expects. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)." +#### 访问您的密码 -You can use and read encrypted secrets in a workflow file if you have access to edit the file. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)." +为使密码用于操作，必须将密码设置为工作流程文件中的输入或环境变量。 查看操作的自述文件以了解操作预期的输入和环境变量。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)”。 + +如果您拥有编辑文件的权限，便可在工作流程文件中使用和读取加密密码。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/github/getting-started-with-github/access-permissions-on-github)”。 {% warning %} -**Warning:** {% data variables.product.prodname_dotcom %} automatically redacts secrets printed to the log, but you should avoid printing secrets to the log intentionally. +**警告：**{% data variables.product.prodname_dotcom %} 自动将密码编写到日志，但您应避免有意将密码打印到日志。 {% endwarning %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +当工作流程运行排队时读取组织和仓库机密，在引用环境的作业开始时读取环境机密。 {% endif %} -You can also manage secrets using the REST API. For more information, see "[Secrets](/rest/reference/actions#secrets)." +您还可以使用 REST API 管理密码。 更多信息请参阅“[密码](/rest/reference/actions#secrets)”。 -#### Limiting credential permissions +#### 限制凭据权限 -When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary. +生成凭据时，建议尽可能授予最低的权限。 例如，不使用个人凭据，而使用[部署密钥](/developers/overview/managing-deploy-keys#deploy-keys)或服务帐户。 请考虑授予只读权限（如果这是所需的全部权限）并尽可能限制访问。 生成个人访问令牌 (PAT) 时，选择所需的最小范围。 -### Creating encrypted secrets for a repository +### 为仓库创建加密密码 {% 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. Click **New repository secret**. -1. Type a name for your secret in the **Name** input box. -1. Enter the value for your secret. -1. Click **Add secret**. +1. 单击 **New repository 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. +如果您的仓库 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0"or currentVersion == "github-ae@latest" %}拥有环境机密或 {% endif %}可以访问父组织中的机密，则这些机密也会列入本页。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -### Creating encrypted secrets for an environment +{% note %} + +**注意：**具有协作员权限的用户可以使用 REST API 来管理仓库的机密。 更多信息请参阅“[{% data variables.product.prodname_actions %} 密码 API](/rest/reference/actions#secrets)”。 + +{% endnote %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" } +### 为环境创建加密密码 {% 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. Click on the environment that you want to add a secret to. -1. Under **Environment secrets**, click **Add secret**. -1. Type a name for your secret in the **Name** input box. -1. Enter the value for your secret. -1. Click **Add secret**. +1. 单击要向其添加机密的环境。 +1. 在 **Environment secrets（环境机密）**下，单击 **Add secret（添加机密）**。 +1. 在 **Name（名称）**输入框中键入密码的名称。 +1. 输入密码的值。 +1. 单击 **Add secret（添加密码）**。 {% endif %} -### Creating encrypted secrets for an organization +### 为组织创建加密密码 -When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories. +在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。 {% data reusables.github-actions.permissions-statement-secrets-organization %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.sidebar-secret %} -1. Click **New organization secret**. -1. Type a name for your secret in the **Name** input box. -1. Enter the **Value** for your secret. -1. From the **Repository access** dropdown list, choose an access policy. -1. Click **Add secret**. +1. 单击 **New organization secret（新组织机密）**。 +1. 在 **Name（名称）**输入框中键入密码的名称。 +1. 输入密码的 **Value（值）**。 +1. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。 +1. 单击 **Add secret（添加密码）**。 -### Reviewing access to organization-level secrets +### 审查对组织级别密码的访问权限 -You can check which access policies are being applied to a secret in your organization. +您可以检查哪些访问策略正被应用于组织中的密码。 {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.sidebar-secret %} -1. The list of secrets includes any configured permissions and policies. For example: -![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png) -1. For more details on the configured permissions for each secret, click **Update**. +1. 密码列表包括任何已配置的权限和策略。 例如： ![密码列表](/assets/images/help/settings/actions-org-secrets-list.png) +1. 有关已为每个密码配置的权限的更多信息，请单击 **Update（更新）**。 -### Using encrypted secrets in a workflow +### 在工作流程中使用加密密码 {% data reusables.actions.forked-secrets %} -To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)." +要提供以密码作为输入或环境变量的操作，可以使用 `secrets` 上下文访问您在仓库中创建的密码。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”和“[{% data variables.product.prodname_actions %} 的工作流程语法](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。 {% raw %} ```yaml @@ -133,11 +140,11 @@ steps: ``` {% endraw %} -Avoid passing secrets between processes from the command line, whenever possible. Command-line processes may be visible to other users (using the `ps` command) or captured by [security audit events](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing). To help protect secrets, consider using environment variables, `STDIN`, or other mechanisms supported by the target process. +尽可能避免使用命令行在进程之间传递密码。 命令行进程可能对其他用户可见（使用 `ps` 命令）或通过[安全审计事件](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing)获取。 为帮助保护密码，请考虑使用环境变量 `STDIN` 或目标进程支持的其他机制。 -If you must pass secrets within a command line, then enclose them within the proper quoting rules. Secrets often contain special characters that may unintentionally affect your shell. To escape these special characters, use quoting with your environment variables. For example: +如果必须在命令行中传递密码，则将它们包含在适当的引用规则中。 密码通常包含可能意外影响 shell 的特殊字符。 要转义这些特殊字符，请引用环境变量。 例如： -#### Example using Bash +#### 使用 Bash 的示例 {% raw %} ```yaml @@ -150,7 +157,7 @@ steps: ``` {% endraw %} -#### Example using PowerShell +#### 使用 PowerShell 的示例 {% raw %} ```yaml @@ -163,7 +170,7 @@ steps: ``` {% endraw %} -#### Example using Cmd.exe +#### 使用 Cmd.exe 的示例 {% raw %} ```yaml @@ -176,31 +183,31 @@ steps: ``` {% endraw %} -### Limits for secrets +### 密码的限制 -You can store up to 1,000 secrets per organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, 100 secrets per repository, and 100 secrets per environment{% else %} and 100 secrets per repository{% endif %}. A workflow may use up to 100 organization secrets and 100 repository secrets.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Additionally, a job referencing an environment may use up to 100 environment secrets.{% endif %} +最多可以每个组织存储 1,000 条机密{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}，每个仓库存储 100 条机密，每个环境存储 100 条机密{% else %}，每个仓库存储 100 条机密{% endif %}。 一个工作流程最多可以使用 100 条组织机密和 100 条仓库机密。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} 此外，引用环境的作业最多可以使用 100 条环境机密。{% endif %} -Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB, you can store encrypted secrets in your repository and save the decryption passphrase as a secret on {% data variables.product.prodname_dotcom %}. For example, you can use `gpg` to encrypt your credentials locally before checking the file in to your repository on {% data variables.product.prodname_dotcom %}. For more information, see the "[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)." +密码大小限于 64 KB。 要使用大于 64 KB 的密码，可以将加密的密码存储在仓库中，并将解密短语在 {% data variables.product.prodname_dotcom %} 上存储为密码。 例如，在将文件检入您在 {% data variables.product.prodname_dotcom %} 上的仓库之前，可以使用 `gpg` 在本地对您的凭据加密。 更多信息请参阅“[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)”。 {% warning %} -**Warning**: Be careful that your secrets do not get printed when your action runs. When using this workaround, {% data variables.product.prodname_dotcom %} does not redact secrets that are printed in logs. +**警告**：请注意，您的密码在操作运行时不会印出。 使用此解决方法时，{% data variables.product.prodname_dotcom %} 不会编写日志中印出的密码。 {% endwarning %} -1. Run the following command from your terminal to encrypt the `my_secret.json` file using `gpg` and the AES256 cipher algorithm. +1. 从终端运行以下命令，以使用 `gpg` 和 AES256 密码算法对 `my_secret.json` 文件加密。 ``` shell $ gpg --symmetric --cipher-algo AES256 my_secret.json ``` -1. You will be prompted to enter a passphrase. Remember the passphrase, because you'll need to create a new secret on {% data variables.product.prodname_dotcom %} that uses the passphrase as the value. +1. 将会提示您输入密码短语。 请记住该密码短语，因为需要在使用该密码短语作为值的 {% data variables.product.prodname_dotcom %} 上创建新密码。 -1. Create a new secret that contains the passphrase. For example, create a new secret with the name `LARGE_SECRET_PASSPHRASE` and set the value of the secret to the passphrase you selected in the step above. +1. 创建包含密码短语的新密码。 例如，使用名称 `LARGE_SECRET_PASSPHRASE` 创建新密码，并将密码的值设为上一步所选的密码短语。 -1. Copy your encrypted file into your repository and commit it. In this example, the encrypted file is `my_secret.json.gpg`. +1. 将加密的文件复制到仓库并提交。 在本例中，加密的文件是 `my_secret.json.gpg`。 -1. Create a shell script to decrypt the password. Save this file as `decrypt_secret.sh`. +1. 创建 shell 脚本对密码解密。 将此文件另存为 `decrypt_secret.sh`。 ``` shell #!/bin/sh @@ -213,7 +220,7 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB, --output $HOME/secrets/my_secret.json my_secret.json.gpg ``` -1. Ensure your shell script is executable before checking it in to your repository. +1. 确保 shell 脚本在检入仓库之前可执行。 ``` shell $ chmod +x decrypt_secret.sh @@ -222,7 +229,7 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB, $ git push ``` -1. From your workflow, use a `step` to call the shell script and decrypt the secret. To have a copy of your repository in the environment that your workflow runs in, you'll need to use the [`actions/checkout`](https://github.com/actions/checkout) action. Reference your shell script using the `run` command relative to the root of your repository. +1. 从工作流程使用 `step` 调用 shell 脚本并对密码解密。 要在工作流程运行的环境中创建仓库的副本，需要使用 [`actions/checkout`](https://github.com/actions/checkout) 操作。 使用与仓库根目录相关的 `run` 命令引用 shell 脚本。 {% raw %} ```yaml diff --git a/translations/zh-CN/content/actions/reference/environment-variables.md b/translations/zh-CN/content/actions/reference/environment-variables.md index a03494a59e..a0bd076287 100644 --- a/translations/zh-CN/content/actions/reference/environment-variables.md +++ b/translations/zh-CN/content/actions/reference/environment-variables.md @@ -22,6 +22,7 @@ versions: 要设置自定义环境变量，您需要在工作流程文件中指定变量。 您可以使用 [`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) 和 [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) 关键字定义步骤、作业或整个工作流程的环境变量。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)”。 +{% raw %} ```yaml jobs: weekday_job: @@ -30,13 +31,14 @@ jobs: DAY_OF_WEEK: Mon steps: - name: "Hello world when it's Monday" - if: env.DAY_OF_WEEK == 'Mon' + if: ${{ env.DAY_OF_WEEK == 'Mon' }} run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!" env: FIRST_NAME: Mona middle_name: The Last_Name: Octocat ``` +{% endraw %} 要在工作流程文件中使用环境变量的值，您应该使用 [`env` 上下文](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)。 如果要在运行器中使用环境变量的值，您可以使用运行器操作系统的正常方法来读取环境变量。 diff --git a/translations/zh-CN/content/actions/reference/environments.md b/translations/zh-CN/content/actions/reference/environments.md index d8614c15dd..d21a251c0a 100644 --- a/translations/zh-CN/content/actions/reference/environments.md +++ b/translations/zh-CN/content/actions/reference/environments.md @@ -16,12 +16,12 @@ versions: 您可以使用保护规则和机密配置环境。 当工作流程引用环境时，作业在环境的所有保护规则通过之前不会开始。 在所有环境保护规则通过之前，作业也不能访问在环境中定义的机密。 {% if currentVersion == "free-pro-team@latest" %} -环境保护规则和环境机密只能在公共仓库中使用。 如果您将仓库从公开转换为私密，任何配置的保护规则或环境机密将被忽略， 并且您将无法配置任何环境。 如果将仓库转换回公共，您将有权访问以前配置的任何保护规则和环境机密。 +环境保护规则和环境机密仅在企业计划上的公共仓库和私有仓库中提供。 如果您在非企业计划中将仓库从公开转换为私密，任何配置的保护规则或环境机密将被忽略， 并且您将无法配置任何环境。 如果将仓库转换回公共，您将有权访问以前配置的任何保护规则和环境机密。 {% endif %} #### 环境保护规则 -环境保护规则要求通过特定的条件，然后引用环境的作业才能继续。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %} +环境保护规则要求通过特定的条件，然后引用环境的作业才能继续。 {% if currentversion == "free-proteam@latest" or currentversion == "github-ae@next" or currentversion ver_gt "enterprise-server@3. %}您可以使用环境保护规则来要求手动批准、延迟作业或者将环境限于某些分支。{% else %}您可以使用环境保护规则要求手动批准或延迟作业。{% endif %} ##### 需要的审查者 @@ -59,7 +59,7 @@ versions: 1. 为环境输入一个名称, 然后单击 **Configure environment（配置环境）**。 环境名称不区分大小写。 环境名称不能超过 255 个字符，且必须在仓库中唯一。 1. 配置任何环境保护规则或环境机密。 -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %} +{% if currentversion == "free-proteam@latest" or currentversion == "github-ae@next " or currentversion ver_gt "enterprise-server@3.1" %}您也可以通过 REST API 创建和配置环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”和“[密码](/rest/reference/actions#secrets)”。{% endif %} 运行引用不存在的环境的工作流程将使用引用的名称创建环境。 新创建的环境将不配置任何保护规则或机密。 可在仓库中编辑工作流程的任何人都可以通过工作流程文件创建环境，但只有仓库管理员才能配置环境。 @@ -83,4 +83,4 @@ versions: 1. 在要删除的环境旁边，单击 {% octicon "trashcan" aria-label="The trashcan icon" %}。 2. 单击 **I understand, delete this environment（我了解，删除此环境）**。 -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %} +{% if currentversion == "free-proteam@latest" or currentversion == "github-ae@next " or currentversion ver_gt "enterprise-server@3.1" %}您也可以通过 REST API 删除环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”。{% endif %} diff --git a/translations/zh-CN/content/actions/reference/index.md b/translations/zh-CN/content/actions/reference/index.md index c94ae2f4eb..8de7728253 100644 --- a/translations/zh-CN/content/actions/reference/index.md +++ b/translations/zh-CN/content/actions/reference/index.md @@ -1,56 +1,57 @@ --- -title: Reference -intro: 'Reference documentation for creating workflows, using GitHub-hosted runners, and authentication.' +title: 参考 +intro: '使用 GitHub 托管的运行器和身份验证创建工作流程的参考文档。' redirect_from: - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.ae-beta %} -### Workflow syntax +### 工作流程语法 -The workflow file is written in YAML. In the YAML workflow file, you can use expression syntax to evaluate contextual information, literals, operators, and functions. Contextual information includes workflow, environment variables, secrets, and the events that triggered the workflow. When you use [`run`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun) in a workflow step to run shell commands, you can use specific workflow command syntax to set environment variables, set output parameters for subsequent steps, and set error or debug messages. +工作流程文件以 YAML 编写。 在 YAML 工作流程文件中，您可以使用表达式语法来评估上下文信息、文字、运算符和函数。 上下文信息包括工作流程、环境变量、密码和触发工作流程的事件。 当您在工作流程步骤中使用 [`run`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun) 运行 shell 命令时，您可以使用特定的工作流程命令语法来设置环境变量、设置后续步骤的输出参数，以及设置错误或调试信息。 {% 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 %} -### Events +### 事件 -You can configure workflows to run when specific GitHub events occur, at a scheduled time, manually, or when events outside of GitHub occur. +您可以配置工作流和在发生特定 GitHub 事件时运行、在计划的时间运行、手动运行、手动或者当 GitHub 外部事件发生时运行。 {% link_in_list /events-that-trigger-workflows %} -### Authentication and secrets +### 身份验证和密码 -{% data variables.product.prodname_dotcom %} provides a token that you can use to authenticate on behalf of {% data variables.product.prodname_actions %}. You can also store sensitive information as a secret in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environments{% else %} or repository{% endif %}. {% data variables.product.prodname_dotcom %} encrypts all secrets. +{% data variables.product.prodname_dotcom %} 提供一个令牌，可用于代表 {% data variables.product.prodname_actions %} 进行身份验证。 您还可以将敏感信息存储在您的组织{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %}、仓库或者环境{% else %} 或仓库{% endif %} 中。 {% data variables.product.prodname_dotcom %} 对所有密码加密。 {% 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" %} -### Environments +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@latest" %} +### 环境 -Workflow jobs can reference environments that have protection rules or environment-specific secrets. +工作流程作业可以引用具有保护规则或环境特定机密的环境。 {% link_in_list /environments %} {% endif %} -### {% data variables.product.prodname_dotcom %}-hosted runners +### 环境变量 -GitHub offers hosted virtual machines to run workflows. The virtual machine contains an environment with tools, packages, and environment variables for GitHub Actions to use. +{% data variables.product.prodname_dotcom %} 为每个 {% data variables.product.prodname_actions %} 工作流程运行设置默认环境变量。 您也可以在工作流程文件中设置自定义环境变量。 {% link_in_list /environment-variables %} -{% link_in_list /specifications-for-github-hosted-runners %} {% if currentVersion == "free-pro-team@latest" %} -### Administration +### 管理 -When you run workflows on {% data variables.product.prodname_dotcom %}-hosted runners, there are usage limits and potential usage charges. You can also disable or restrict the usage of {% data variables.product.prodname_actions %} in a repository and organization. +在 {% data variables.product.prodname_dotcom %} 托管的运行器上运行工作流程时，存在使用限制和潜在的使用费用。 您也可以禁用或限制 {% data variables.product.prodname_actions %} 在仓库和组织中的使用。 {% link_in_list /usage-limits-billing-and-administration %} diff --git a/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md b/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md index 2a72a3b149..4f0f23907f 100644 --- a/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md +++ b/translations/zh-CN/content/actions/reference/usage-limits-billing-and-administration.md @@ -70,7 +70,7 @@ GitHub Actions 使用对 更多信息请参阅： - [为仓库中构件和日志的 {% data variables.product.prodname_actions %} 配置保留期](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository) -- [为组织中构件和日志的 {% data variables.product.prodname_actions %} 配置保留期](/github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) +- [为组织中构件和日志的 {% data variables.product.prodname_actions %} 配置保留期](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization) - [为企业中构件和日志的 {% data variables.product.prodname_actions %} 配置保留期](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account) {% endif %} @@ -80,7 +80,7 @@ GitHub Actions 使用对 更多信息请参阅： - "[对仓库禁用或限制 {% data variables.product.prodname_actions %}](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository)" -- "[对组织禁用或限制 {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} +- "[对组织禁用或限制 {% data variables.product.prodname_actions %}](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"{% if currentVersion == "free-pro-team@latest" %} - "[在企业帐户中实施 {% data variables.product.prodname_ghe_cloud %} 的 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)"{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index a6418b5128..4e9b6efbda 100644 --- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -21,7 +21,7 @@ Azure Active Directory (Azure AD) 是一项来自 Microsoft 的服务，它允 * 为 Azure AD 上的 IdP 组分配 {% data variables.product.prodname_ghe_managed %} 应用程序，以为 IdP 组的所有成员授予对 {% data variables.product.product_name %} 上用户帐户的访问权限 。 此外，IdP 组也可以在 {% data variables.product.prodname_ghe_managed %} 上连接到团队及其父组织。 * 从 IdP 组取消分配 {% data variables.product.prodname_ghe_managed %} 应用程序来停用仅通过 IdP 组访问的所有 IdP 用户的 {% data variables.product.product_name %} 用户帐户，并从父组织中删除这些用户。 IdP 组将与 {% data variables.product.product_name %} 上的任何团队断开连接。 -有关在 {% data variables.product.product_location %} 上管理企业的身份和访问权限的详细信息，请参阅“[管理企业的身份和访问权限](/admin/authentication/managing-identity-and-access-for-your-enterprise)”。 有关与 IdP 组同步团队的更多信息，请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”。 +有关在 {% data variables.product.product_location %} 上管理企业的身份和访问权限的详细信息，请参阅“[管理企业的身份和访问权限](/admin/authentication/managing-identity-and-access-for-your-enterprise)”。 有关与 IdP 组同步团队的更多信息，请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 ### 基本要求 diff --git a/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md index 77961f7576..84d3631f08 100644 --- a/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/authentication/configuring-user-provisioning-for-your-enterprise.md @@ -28,7 +28,7 @@ IdP 上的预配应用程序通过企业的 SCIM API 与 {% data variables.produ {% data reusables.scim.supported-idps %} -在使用支持的 IdP 设置用户预配时，您也可以将 {% data variables.product.product_name %} 的应用程序分配或取消分配给用户组。 然后，这些组可供 {% data variables.product.product_location %} 中的组织所有者和团队维护员用来映射到 {% data variables.product.product_name %} 团队。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”。 +在使用支持的 IdP 设置用户预配时，您也可以将 {% data variables.product.product_name %} 的应用程序分配或取消分配给用户组。 然后，这些组可供 {% data variables.product.product_location %} 中的组织所有者和团队维护员用来映射到 {% data variables.product.product_name %} 团队。 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 ### 基本要求 diff --git a/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md b/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md index 7b73aa67cc..4785b9ff91 100644 --- a/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/restricting-network-traffic-to-your-enterprise.md @@ -13,7 +13,7 @@ versions: {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -您还可以为单个组织配置允许的 IP 地址。 更多信息请参阅“[管理组织允许的 IP 地址](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)”。 +您还可以为单个组织配置允许的 IP 地址。 更多信息请参阅“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)”。 默认情况下，Azure 网络安全组 (NSG) 规则允许所有入站流量在端口 22、80、443 和 25 打开。 企业所有者可以联系 {% data variables.contact.github_support %} 配置您实例的访问限制。 diff --git a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md index f87a3f3136..d20a671286 100644 --- a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server.md @@ -37,7 +37,7 @@ topics: {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} 更多信息请参阅“[联系 {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)”。 +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} diff --git a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md index 9a3ce91825..7f62ef9dba 100644 --- a/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md +++ b/translations/zh-CN/content/admin/enterprise-support/about-github-premium-support-for-github-enterprise.md @@ -35,7 +35,7 @@ topics: {% data reusables.support.signing-up-for-premium-support %} -{% data reusables.support.scope-of-support %} 更多信息请参阅“[联系 {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)”。 +{% data reusables.support.scope-of-support %} {% data reusables.support.contacting-premium-support %} 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 index 098ff48a13..6487e83ff3 100644 --- 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 @@ -1,12 +1,14 @@ --- -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.' +title: GitHub Actions for GitHub Enterprise Server 使用入门 +intro: '了解首次在 {% data variables.product.prodname_ghe_server %} 上启用和配置 {% data variables.product.prodname_actions %}。' 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' +topics: + - 企业 --- {% data reusables.actions.enterprise-beta %} @@ -15,25 +17,36 @@ versions: {% 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. +本文介绍站点管理员如何配置 {% data variables.product.prodname_ghe_server %} 来使用 {% data variables.product.prodname_actions %}。 它涵盖了硬件和软件需求、存储选项以及安全管理策略。 {% endif %} -### Review hardware considerations +### 查看硬件注意事项 {% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} {% note %} -**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)。” +**注**：{% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} 作为有限测试版适用于 {% data variables.product.prodname_ghe_server %} 2.22。 {% endif %}如果您将现有 {% data variables.product.prodname_ghe_server %} 实例升级到 3.0 或更高版本，并且要配置 {% data variables.product.prodname_actions %}，请注意，最低硬件要求有所增加。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)。” {% endnote %} {% endif %} -{% data reusables.actions.enterprise-hardware-considerations %} +{% data variables.product.product_location %} 可用的 CPU 和内存资源决定了 {% data variables.product.prodname_actions %} 的最大作业吞吐量。 -For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform. +{% data variables.product.company_short %} 的内部测试展示了具有系列 CPU 和内存配置的 {% data variables.product.prodname_ghe_server %} 实例的以下最大吞吐量。 您可能会看到不同的吞吐量，具体取决于实例的总体活动水平。 + +| vCPU | 内存 | 最大作业吞吐量 | +|:---- |:------ |:------- | +| 4 | 32 GB | 演示或轻量测试 | +| 8 | 64 GB | 25 个作业 | +| 16 | 160 GB | 35 个作业 | +| 32 | 256 GB | 100 个作业 | + +如果您{% if currentversion == "enterprise-server@2 %}启用了{% else %}计划中的测试版以便为现有实例的用户启用{% endif %} {% data variables.product.prodname_actions %}，请查看用户的活动级别和实例上的自动化，并确保已为用户预配足够的 CPU 和内存。 有关监控 {% data variables.product.prodname_ghe_server %} 容量和性能的更多信息，请参阅“[监控您的设备](/admin/enterprise-management/monitoring-your-appliance)”。 + +有关 {% data variables.product.product_location %} 的最低硬件要求的更多信息，请参阅实例平台的硬件考虑因素。 - [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) - [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) @@ -45,11 +58,11 @@ For more information about resource requirements for {% data variables.product.p {% data reusables.enterprise_installation.about-adjusting-resources %} -### 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 %} 使用 Blob 存储来存储工作流程运行生成的构件，如工作流程日志和用户上传的构建构件。 所需存储量取决于您使用 {% data variables.product.prodname_actions %} 的情况。 仅支持单个外部存储配置，不能同时使用多个存储提供程序。 {% data variables.product.prodname_actions %} 支持以下存储提供商： @@ -59,7 +72,7 @@ For more information about resource requirements for {% data variables.product.p {% 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. +**注：**只有这些是 {% data variables.product.company_short %} 支持并可以提供帮助的存储提供程序。 由于 S3 API 的差异，其他 S3 API 兼容的存储提供程序难以正常工作。 [联系我们](https://support.github.com/contact) 以请求支持额外的存储提供程序。 {% endnote %} @@ -71,7 +84,7 @@ For more information about resource requirements for {% data variables.product.p ### 启用 {% data variables.product.prodname_actions %} -{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +{% data variables.product.prodname_ghe_server %} 2.22 上的 {% data variables.product.prodname_actions %} 支持作为有限测试版提供。 要为实例配置 {% data variables.product.prodname_actions %} ，请升级到 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本。 更多信息请参阅 [{% data variables.product.prodname_ghe_server %} 3.0 发行说明](/enterprise-server@3.0/admin/release-notes)和“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)”。 ### 延伸阅读 @@ -81,32 +94,32 @@ For more information about resource requirements for {% data variables.product.p {% if currentVersion ver_gt "enterprise-server@2.22" %} -### Enabling {% data variables.product.prodname_actions %} with your storage provider +### 使用您的存储提供程序启用 {% data variables.product.prodname_actions %} -Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: +请按照以下过程之一使用所选存储提供程序启用 {% data variables.product.prodname_actions %}： -* [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) +* [使用 Azure Blob 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [使用 Amazon S3 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [使用 MinIO Gateway for NAS 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) -### Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise +### 管理企业中 {% data variables.product.prodname_actions %} 的访问权限 -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 variables.product.prodname_actions %} 的访问。 更多信息请参阅“[为企业执行 GitHub Actions 策略](/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)”。 +要运行 {% data variables.product.prodname_actions %} 工作流程，您需要添加自托管运行器。 您可以在企业、组织或仓库级别添加自托管运行器。 更多信息请参阅“[添加自托管的运行器](/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 %}. +您可以控制允许用户在企业中使用哪些操作。 这包括设置 {% data variables.product.prodname_github_connect %} 以自动访问来自 {% data variables.product.prodname_dotcom_the_website %} 的操作，或手动同步来自 {% 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)." +更多信息请参阅“[关于使用 {% 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 %} +### {% 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)." +如需了解有关 {% data variables.product.prodname_actions %} 安全实践的更多信息，请参阅“[{% 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/index.md b/translations/zh-CN/content/admin/github-actions/index.md index 6c4f2c2187..555130cfed 100644 --- a/translations/zh-CN/content/admin/github-actions/index.md +++ b/translations/zh-CN/content/admin/github-actions/index.md @@ -32,6 +32,7 @@ topics: {% 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 /using-the-latest-version-of-the-official-bundled-actions %} {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %} {% topic_link_in_list /advanced-configuration-and-troubleshooting %} 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 80cbb8df9c..13886debfb 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 @@ -28,8 +28,21 @@ topics: ### 基本要求 -* 在使用 `actions-sync` 工具之前，您必须确保所有目标组织已经存在于您的企业实例中。 以下示例演示如何将操作同步到企业实例上名为 `synced-actions` 的组织。 更多信息请参阅“[从头开始创建新组织](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)”。 +* 在使用 `actions-sync` 工具之前，您必须确保所有目标组织已经存在于您的企业实例中。 以下示例演示如何将操作同步到企业实例上名为 `synced-actions` 的组织。 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 * 您必须在企业实例上创建可以创建并写入目标组织中的仓库的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +* If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. + + {% note %} + + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. + + {% endnote %} + + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." + + ```shell + ghe-org-admin-promote -u USERNAME -o actions + ``` ### 示例：使用 `actions-sync` 工具 diff --git a/translations/zh-CN/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/translations/zh-CN/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md new file mode 100644 index 0000000000..2d6dcf047d --- /dev/null +++ b/translations/zh-CN/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md @@ -0,0 +1,45 @@ +--- +title: 使用官方捆绑操作的最新版本 +intro: '您可以更新与 {% data variables.product.prodname_ghe_server %} 实例捆绑的操作，或直接从 {% data variables.product.prodname_dotcom_the_website %} 使用操作。' +versions: + enterprise-server: '>=2.22' +topics: + - 企业 +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +您的 {% data variables.product.prodname_ghe_server %} 实例包含一些您可以在工作流程中使用的内置操作。 有关捆绑操作的更多信息，请参阅[“与 {% data variables.product.prodname_ghe_server %} 捆绑的正式操作”](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server)。 + +这些捆绑的操作是在 https://github.com/actions 上找到的正式操作的即时快照；因此，这些操作可能是可以更新的旧版本。 要更新这些操作，您可以使用 `actions-sync` 工具将更新的操作与 {% data variables.product.prodname_dotcom_the_website %} 同步。 + +或者，如果您的 {% data variables.product.prodname_ghe_server %} 实例已启用 {% data variables.product.prodname_github_connect %}，则您还有其他选项可以使用来自 {% data variables.product.prodname_dotcom_the_website %} 的最新操作： + +- 您的工作流程文件可以直接引用仅存在于 {% data variables.product.prodname_dotcom_the_website %} 上的特定标记。 +- 要强制工作流程文件在 {% data variables.product.prodname_dotcom_the_website %} 上使用操作，您可以编辑分配给捆绑操作的标记。 + +以下各节将更详细地介绍这些选项。 + +### 使用操作同步更新捆绑操作 + +要更新捆绑操作，您可以使用 `actions-sync` 工具将操作与 {% data variables.product.prodname_dotcom_the_website %} 同步。 有关使用 `actions-sync` 的更多信息，请参阅“[手动从 {% data variables.product.prodname_dotcom_the_website %} 同步选项](/admin/github-actions/manually-syncing-actions-from-githubcom)”。 + +### 从 {% data variables.product.prodname_dotcom_the_website %} 使用操作 + +{% data reusables.github-actions.actions-github-connect-requirement %} + +一旦配置，您即可手动指定工作流程文件中所需的版本，从 {% data variables.product.prodname_dotcom_the_website %} 使用操作的新版本。 例如，从 {% data variables.product.prodname_dotcom_the_website %} 使用 `v2.2.` 版的 `actions/setup-python`，您可以在工作流程文件中指定标记 `actions/setup-python@v2.2.1`。 + +### 删除特定操作的标记以使用最新版本 + +{% data reusables.github-actions.actions-github-connect-requirement %} + +如果您删除之前分配给操作的版本标记，{% data variables.product.prodname_ghe_server %} 将检查 {% data variables.product.prodname_dotcom_the_website %} 是否有所需的标记。 有关使用标记的更多信息，请参阅“[查看标记](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)”。 + +例如，要从 {% data variables.product.prodname_dotcom_the_website %} 使用 `v2.2.1` 版的 `actions/setup-python`： + +1. 在 {% data variables.product.prodname_ghe_server %} 中，从 `actions/setup-python` 仓库中删除 `v2` 标记。 +1. 创建同时使用 `actions/setup-python` 与 `v2` 标记的工作流程。 + +当工作流程无法在 {% data variables.product.prodname_ghe_server %} 上找到指定的 `v2` 标记时，它会检查 {% data variables.product.prodname_dotcom_the_website %} 是否有所需的标记。 如果找到该操作的标记版本，{% data variables.product.prodname_ghe_server %} 将使用 {% data variables.product.prodname_dotcom_the_website %} 中的版本。 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 b0d70de3bb..80e7ce7465 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 @@ -1,6 +1,6 @@ --- title: 在 Hyper-V 上安装 GitHub Enterprise Server -intro: '要在 Hyper-V 上安装 {% data variables.product.prodname_ghe_server %}，您必须部署到运行 Windows Server 2008 至 Windows Server 2016 的机器上。' +intro: '要在 Hyper-V 上安装 {% data variables.product.prodname_ghe_server %}，您必须部署到运行 Windows Server 2008 至 Windows Server 2019 的机器上。' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v @@ -13,7 +13,7 @@ topics: ### 基本要求 - {% data reusables.enterprise_installation.software-license %} -- 您必须具有 Windows Server 2008 至 Windows Server 2016，这些版本支持 Hyper-V。 +- 您必须具有 Windows Server 2008 至 Windows Server 2019，这些版本支持 Hyper-V。 - 创建虚拟机 (VM）所需的大部分操作也可以使用 [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts) 执行。 不过，我们建议使用 Windows PowerShell 命令行 shell 进行初始设置。 下文介绍了使用 PowerShell 的示例。 更多信息请参阅 Microsoft 指南“[Windows PowerShell 使用入门](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)”。 ### 硬件考量因素 diff --git a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md index 4c37b9eed5..db10c410fd 100644 --- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md +++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md @@ -1,34 +1,36 @@ --- -title: About enterprise accounts -intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management{% if enterpriseServerVersions contains currentVersion %} for billing and license usage{% endif %}.' +title: 关于企业帐户 +intro: '使用 {% data variables.product.product_name %}，可以创建企业帐户，为管理员{% if enterpriseServerVersions contains currentVersion %}的帐单和许可使用情况{% endif %}提供单一的可见点和管理点。' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts - /enterprise/admin/overview/about-enterprise-accounts versions: enterprise-server: '>=2.20' github-ae: '*' +topics: + - 企业 --- -### About enterprise accounts on {% data variables.product.product_name %} +### 关于 {% data variables.product.product_name %} 上的企业账户 -An enterprise account allows you to manage multiple organizations{% if enterpriseServerVersions contains currentVersion %} and {% data variables.product.prodname_ghe_server %} instances{% else %} on {% data variables.product.product_name %}{% endif %}. Your enterprise account must have a handle, like an organization or personal account on {% data variables.product.prodname_dotcom %}. Enterprise administrators can manage settings and preferences, like: +企业帐户可用于管理多个组织{% if enterpriseServerVersions contains currentVersion %} 和{% else %}{% data variables.product.product_name %} 上的{% endif %}{% data variables.product.prodname_ghe_server %} 实例。 您的企业帐户必须有操作点，如 {% data variables.product.prodname_dotcom %} 上的组织或个人帐户。 企业管理员可以管理设置和首选项，如： -- Member access and management (organization members, outside collaborators){% if enterpriseServerVersions contains currentVersion %} -- Billing and usage ({% data variables.product.prodname_ghe_server %} instances, user licenses, {% data variables.large_files.product_name_short %} packs){% endif %} -- Security {% if enterpriseServerVersions contains currentVersion %}(single sign-on, two factor authentication) -- Requests {% if enterpriseServerVersions contains currentVersion %}and support bundle sharing {% endif %}with {% data variables.contact.enterprise_support %}{% endif %} +- 成员访问和管理（组织成员、外部协作者）{% if enterpriseServerVersions contains currentVersion %} +- 计费和使用（{% data variables.product.prodname_ghe_server %} 实例、用户许可、{% data variables.large_files.product_name_short %} 包）{% endif %} +- 安全{% if enterpriseServerVersions contains currentVersion %}（单点登录、双重身份验证） +- {% endif %}通过 {% data variables.contact.enterprise_support %}{% endif %}请求 {% if enterpriseServerVersions contains currentVersion %}和支持包共享 -{% 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 %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %}有关管理 {% data variables.product.prodname_ghe_cloud %} 订阅的更多信息，请参阅“[查看企业帐户的订阅和使用情况](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)”。 {% endif %}有关管理 {% data variables.product.product_name %} 帐单设置的更多信息，请参阅“[管理企业的帐单](/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)." +有关 {% data variables.product.product_location %} 的用户、组织、数据和政策管理的更多信息，请参阅“[管理用户、组织和仓库](/admin/user-management)”和“[为企业设置政策](/admin/policies)”。 -For more information about the management of enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." +有关使用 GraphQL API 管理企业帐户的信息，请参阅“[企业帐户](/graphql/guides/managing-enterprise-accounts)”。 {% if enterpriseServerVersions contains currentVersion %} -For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." To upgrade to {% data variables.product.prodname_enterprise %} or to get started with an enterprise account, contact {% data variables.contact.contact_enterprise_sales %}. +有关 {% data variables.product.prodname_ghe_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 %}。 -### Managing {% data variables.product.prodname_ghe_server %} licenses linked to your enterprise account +### 管理链接至企业帐户的 {% data variables.product.prodname_ghe_server %} 许可 {% data reusables.enterprise-accounts.admin-managing-licenses %} diff --git a/translations/zh-CN/content/admin/overview/github-ae-release-notes.md b/translations/zh-CN/content/admin/overview/github-ae-release-notes.md index 47d163977e..76f21b7d8c 100644 --- a/translations/zh-CN/content/admin/overview/github-ae-release-notes.md +++ b/translations/zh-CN/content/admin/overview/github-ae-release-notes.md @@ -29,7 +29,7 @@ versions: #### 管理来自身份提供商 (IdP) 的团队 -使用 SCIM（跨域身份管理系统）的客户现在可以与 {% data variables.product.company_short %} 团队同步Azure Active Directory 中的安全组。 一旦团队已链接到安全组，则当用户从其指定的安全组添加或删除时，会员资格将在 {% data variables.product.product_name %} 中自动更新。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”。 +使用 SCIM（跨域身份管理系统）的客户现在可以与 {% data variables.product.company_short %} 团队同步Azure Active Directory 中的安全组。 一旦团队已链接到安全组，则当用户从其指定的安全组添加或删除时，会员资格将在 {% data variables.product.product_name %} 中自动更新。 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 #### IP 允许列表测试版 @@ -37,7 +37,7 @@ versions: 除了能够申请网络安全组更改以过滤到整个 {% data variables.product.product_name %} 租户的流量之外，还提供了这一功能。 -更多信息请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”和“[管理组织允许的 IP 地址](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)”。 +更多信息请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”和“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)”。 #### 拉取请求自动合并 @@ -47,8 +47,8 @@ versions: #### 开发者更改 -- [组织所有者现在可以禁用](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点。 这将不会取消发布现有站点。 -- 使用 {% data variables.product.prodname_pages %} 的仓库现在可以[从任何分支构建和部署](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)。 +- [组织所有者现在可以禁用](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点。 这将不会取消发布现有站点。 +- 使用 {% data variables.product.prodname_pages %} 的仓库现在可以[从任何分支构建和部署](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)。 - 在编写议题或拉取请求时，按下 `return` 或 `enter`后，项目符号、数字和任务的列表语法现在会自动完成。 - 您现在可以从仓库页面中删除仓库中的目录。 导航到目录时，“Add file（添加文件）”按钮旁边的新烤肉串按钮会提供删除目录的选项。 - 现在[引用议题或拉取请求](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests)更加简便、快速，在 "#" 后可搜索多个字词。 @@ -65,7 +65,7 @@ versions: ##### 默认分支重命名 -企业和组织所有者现在可以设置新仓库的默认分支名称。 企业所有者还可以在所有组织中强制选择默认分支名称，或允许各个组织自行选择。 更多信息请参阅“[在您的企业中执行仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)”和“[管理组织中仓库的默认分支名称](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)”。 +企业和组织所有者现在可以设置新仓库的默认分支名称。 企业所有者还可以在所有组织中强制选择默认分支名称，或允许各个组织自行选择。 更多信息请参阅“[在您的企业中执行仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name)”和“[管理组织中仓库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”。 现有仓库不受这些设置的影响，其默认分支名称也不会更改。 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 40281def35..c352805094 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 @@ -66,17 +66,16 @@ topics: - 告诉用户如何获得 {% data variables.product.product_location %} 帮助 - 确保所有用户阅读有关使用 {% data variables.product.product_location %} 的服务条款 -{% note %} - -**Note:** After you configure a mandatory message for {% data variables.product.product_location %}, you cannot change or remove the message. - -{% endnote %} - - 如果消息中包含 Markdown 复选框，则用户必须选中所有复选框才能忽略消息。 例如，如果您在必读消息中包含服务条款，您可以要求每个用户选中复选框以确认他们阅读了这些条款。 每次用户看到必读消息时，都会创建审核日志事件。 该事件包括用户看到的消息的版本。 更多信息请参阅“[已审核操作](/admin/user-management/audited-actions)”。 +{% note %} + +**注意：**如果您更改了 {% data variables.product.product_location %} 的强制消息，已经确认该消息的用户将不会看到新消息。 + +{% endnote %} + {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} diff --git a/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md b/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md index 68fb3e8fe5..6d86af37df 100644 --- a/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md +++ b/translations/zh-CN/content/code-security/secret-security/about-secret-scanning.md @@ -45,7 +45,7 @@ topics: {% data variables.product.prodname_secret_scanning_caps %} 作为 {% data variables.product.prodname_GH_advanced_security %} 的一部分，在组织拥有的所有仓库上可用。 它不适用于用户拥有的仓库。 {% endif %} -如果您是仓库管理员或组织所有者，您可以为组织拥有的{% 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)”。 +如果您是仓库管理员或组织所有者，您可以为组织拥有的{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_secret_scanning %}。 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." 将提交推送到启用了 {% data variables.product.prodname_secret_scanning %} 的{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库时，{% data variables.product.prodname_dotcom %} 会扫描提交的内容中是否有密码。 diff --git a/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md b/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md index cb6a2c9a75..89036ebbf2 100644 --- a/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md +++ b/translations/zh-CN/content/code-security/secret-security/configuring-secret-scanning-for-your-repositories.md @@ -70,4 +70,4 @@ topics: ### 延伸阅读 -- “[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)” +- “[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)” diff --git a/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md b/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md index 88a106c919..46c05d8028 100644 --- a/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md +++ b/translations/zh-CN/content/code-security/secure-coding/configuring-code-scanning.md @@ -1,8 +1,8 @@ --- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' +title: 配置代码扫描 +intro: '您可以配置 {% data variables.product.prodname_dotcom %} 如何扫描项目代码以查找漏洞和错误。' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' +permissions: '拥有仓库写入权限的人可配置仓库的 {% data variables.product.prodname_code_scanning %}。' miniTocMaxHeadingLevel: 4 redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning @@ -11,55 +11,63 @@ versions: enterprise-server: '>=3.0' github-ae: '*' topics: - - security + - 安全 --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### About {% data variables.product.prodname_code_scanning %} configuration +### 关于 {% data variables.product.prodname_code_scanning %} 配置 -You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)." +您可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_name %} 中运行 {% data variables.product.prodname_code_scanning %}，或使用 {% data variables.product.prodname_codeql_runner %} 从持续集成 (CI) 系统运行它。 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。 有关 {% data variables.product.prodname_codeql_runner %} 的更多信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system)”。 -This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}. +本文说明在 {% data variables.product.product_name %} 上运行 {% data variables.product.prodname_code_scanning %}。 -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." +在为仓库配置 {% data variables.product.prodname_code_scanning %} 之前，必须将 {% data variables.product.prodname_actions %} 工作流程添加到仓库中以设置 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。 {% data reusables.code-scanning.edit-workflow %} -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. +您可以为 {% data variables.product.prodname_code_scanning %} 编写配置文件。 {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} 在 {% data variables.product.prodname_dotcom_the_website %} 上，{% endif %}包含您可以使用的其他 {% data variables.product.prodname_code_scanning %} 工作流程。 {% if currentVersion == "free-pro-team@latest" %}您可以在“{% data variables.product.prodname_code_scanning %} 使用入门”页找到这些选项，该页面可从 **{% octicon "shield" aria-label="The shield symbol" %} Security（安全）**选项卡访问。{% endif %}本文给出的具体示例与 {% data variables.product.prodname_codeql_workflow %} 文件相关。 -### Editing a {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} 将工作流程文件保存在仓库的 _.github/workflows_ 目录中。 您可以通过搜索其文件名来查找已添加的工作流程。 例如，默认情况下，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的工作流程文件被称为 _codeql-analysis.yml_。 -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. 在仓库中，浏览至要编辑的工作流程文件。 +1. 要打开工作流程编辑器，在文件视图右上角单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑工作流程文件按钮](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. 编辑文件后，单击 **Start commit（开始提交）**并完成“Commit changes（提交更改）”表单。 您可以选择直接提交到当前分支，或者创建一个新分支并启动拉取请求。 ![将更新提交到 codeql.yml 工作流程](/assets/images/help/repository/code-scanning-workflow-update.png) -For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +有关编辑工作流程文件的更多信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 -### Configuring frequency +### 配置频率 -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +您可以按时间表或在仓库中发生特定事件时扫描代码。 -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +每当推送到仓库以及每次创建拉取请求时，时扫描代码可防止开发者在代码中引入新的漏洞和错误。 按时间表扫描可了解 {% data variables.product.company_short %}、安全研究者和社区发现的最新漏洞和错误，即使开发者并未主动维护仓库。 -#### Scanning on push +#### 按推送扫描 -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +如果使用默认工作流程，则除了事件触发的扫描之外，{% data variables.product.prodname_code_scanning %} 还会每周扫描一次仓库代码。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#on)”。 -#### Scanning pull requests +如果您在推送时扫描，则结果将出现在仓库的 **Security（安全性）**选项卡中。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +{% note %} -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +**注意**：如果您希望 {% data variables.product.prodname_code_scanning %} 警报显示为拉取请求检查，则必须使用下述 `pull_request` 事件。 -#### Avoiding unnecessary scans of pull requests +{% endnote %} -You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. +#### 扫描拉取请求 + +默认 {% data variables.product.prodname_codeql_workflow %} 使用 `pull_request` 事件在针对默认分支的拉取请求上触发代码扫描。 {% if currentversion ver_gt "enterprise-server@2.21" %}如果从私有复刻打开拉取请求，`pull_request` 事件不会触发。{% else %}如果拉取请求来自私有复刻，`pull_request` 事件仅在仓库设置中选择了“Run workflows from fork pull requests（从复刻拉取请求运行工作流程）”选项时触发。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 + +有关 `pull_request` 事件的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)”。 + +如果您扫描拉取请求，则结果在拉取请求检查中显示为警报。 更多信息请参阅“[对拉取请求中的代码扫描警报分类](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)”。 + +#### 避免对拉取请求进行不必要的扫描 + +您可能希望避免针对默认分支的特定拉取请求触发代码扫描，而不管更改了哪些文件。 可以通过在 {% data variables.product.prodname_code_scanning %} 工作流程中指定 `on:pull_request:paths-ignore` or `on:pull_request:paths` 来进行配置。 例如，如果拉取请求中唯一的更改是文件扩展名为 `.md` 或 `.txt` 的文件，则您可以使用以下 `paths-ignore` 数组。 ``` yaml on: @@ -74,28 +82,28 @@ on: {% note %} -**Notes** +**注：** -* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." -* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. +* `on:pull_request:paths-witch` 和 `on:pull_request:pull_request:path` 设置条件来确定工作流程中的操作是否会在拉取请求上运行。 它们无法确定在操作_运行_时将分析哪些文件。 当拉取请求包含 `on:pull_request:paths-with` 或 `on:pull_request:path:path` 未匹配的任何文件时，工作流程将运行操作并扫描拉取请求中更改的所有文件，包括 `on:pull_request:paths-ignore` 或 `on:pull_request:paths` 匹配的文件，除非文件被排除在外。 有关如何从分析中排除文件的信息，请参阅“[指定要扫描的目录](#specifying-directories-to-scan)”。 +* 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 工作流程文件， 不要对 `on:push` 事件使用 `paths-ignore` 或 `paths` 关键词， 因为这可能导致缺少分析。 为了获得准确的结果，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 需要能够与上次提交的分析比较新的变化。 {% endnote %} -For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." +有关使用 `on:pull_request:paths-ignore` 和 `on:pull_request:paths` 确定工作流程何时对拉取请求运行的详细信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 -#### Scanning on a schedule +#### 按时间表扫描 -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +默认 {% data variables.product.prodname_code_scanning %} 工作流程在拉取请求的 `HEAD` 提交时使用 `pull_request` 事件触发代码扫描。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onschedule)”。 {% note %} -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. +**注**：{% data variables.product.prodname_dotcom %} 只运行默认分支上工作流程中的预定作业。 在任何其他分支上的工作流程中更改时间表后，需要将该分支合并到默认分支才能使更改生效。 {% endnote %} -#### Example +#### 示例 -The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. +{% data variables.product.prodname_dotcom %} saves workflow files in the `.github/workflows` directory of your repository. 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`. ``` yaml on: @@ -107,16 +115,16 @@ on: - cron: '20 14 * * 1' ``` -This workflow scans: -* Every push to the default branch and the protected branch -* Every pull request to the default branch -* The default branch every Monday at 14:20 UTC +此工作流程扫描： +* 对默认分支和受保护分支的每次推送 +* 对默认分支的每个拉取请求 +* 默认分支（每个星期一 14:20 UTC） -### Specifying an operating system +### 指定操作系统 -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} +如果您的代码需要使用特定的操作系统进行编译，您可以在工作流程中配置它。 编辑 `jobs.analyze.runs-on` 的值以指定运行 {% data variables.product.prodname_code_scanning %} 操作的机器操作系统。 {% if currentVersion ver_gt "enterprise-server@2.21" %}在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% else %} -If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} +如果选择使用自托管的运行器进行代码扫描，可以在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% endif %} ``` yaml jobs: @@ -125,23 +133,23 @@ jobs: runs-on: [self-hosted, ubuntu-latest] ``` -{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。{% endif %} -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% data variables.product.prodname_code_scanning_capc %} 支持 macOS、Ubuntu 和 Windows 的最新版本。 因此，此设置的典型值为：`ubuntu-latest`、`windows-latest` 和 `macos-latest`。 更多信息请参阅 {% if currentVersion ver_gt "enterprise-server@2.21" %}“[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)”和“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}”[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}“。 -{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} +{% if currentversion ver_gt "enterprise-server@2.21" %}您必须确保 Git 位于自托管运行器的 PATH 变量中。{% else %}如果您使用自托管运行器，必须确保 Git 在 PATH 变量中。{% endif %} -### Changing the languages that are analyzed +### 更改分析的语言 -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages. +{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 会自动检测用受支持的语言编写的代码。 {% data reusables.code-scanning.supported-languages %} -The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +默认 {% data variables.product.prodname_codeql_workflow %} 文件包含一个名为 `language` 的构建矩阵，其中列出了仓库中被分析的语言。 将 {% data variables.product.prodname_code_scanning %} 添加到仓库时，{% data variables.product.prodname_codeql %} 会自动填充此矩阵。 使用 `language` 矩阵优化 {% data variables.product.prodname_codeql %} 以并行运行每个分析。 由于并行构建的性能优势，我们建议所有工作流程都采用此配置。 有关构建矩阵的更多信息，请参阅“[管理复杂的工作流程](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)”。 {% data reusables.code-scanning.specify-language-to-analyze %} -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. +如果您的工作流程使用 `language` 矩阵，则 {% data variables.product.prodname_codeql %} 会被硬编码为仅分析矩阵中的语言。 如需更改要分析的语言，请编辑矩阵变量的值。 您可以删除某种语言以防止被分析，也可以添加在设置 {% data variables.product.prodname_code_scanning %} 时仓库中不存在的语言。 例如，如果在设置 {% data variables.product.prodname_code_scanning %} 时，仓库最初只包含 JavaScript，但您后来添加了 Python 代码，则需要将 `python` 添加到矩阵中。 ```yaml jobs: @@ -154,7 +162,7 @@ jobs: language: ['javascript', 'python'] ``` -If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. +如果工作流程中不包含名为 `language` 的矩阵，则 {% data variables.product.prodname_codeql %} 将被配置为按顺序运行分析。 如果您未在工作流程中指定语言，则 {% data variables.product.prodname_codeql %} 将自动检测并尝试分析仓库中所有受支持的语言。 如果不愿意使用矩阵选择要分析的语言，您可以使用 `init` 操作下的 `languages` 参数。 ```yaml - uses: github/codeql-action/init@v1 @@ -162,15 +170,15 @@ If your workflow does not contain a matrix called `language`, then {% data varia languages: cpp, csharp, python ``` {% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies +### 分析 Python 依赖项 -For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: +对于仅使用 Linux 的 GitHub 托管的运行器，{% data variables.product.prodname_codeql_workflow %} 将尝试自动安装 Python 依赖项以提供更多 CodeQL 分析结果。 可通过为“初始化 CodeQL”步骤调用的操作指定 `setup-python-dependencies` 参数来控制此行为。 默认情况下，此参数设置为 `true`： -- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies. +- 如果仓库包含用 Python 编写的代码，“初始化 CodeQL”步骤将在 GitHub 托管的运行器上安装必要的依赖项。 如果自动安装成功，该操作还会将环境变量 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件。 -- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete. +- 如果仓库没有任何 Python 依赖项，或者依赖项是以意外方式指定的，您将收到警告，并且该操作会继续执行其余作业。 即使在解释依赖项时出现问题，该操作也可以成功运行，但结果可能不完整。 -Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract: +或者，您也可以在任何操作系统上手动安装 Python 依赖项。 您需要添加 `setup-python-dependencies` 并将其设置为 `false`，以及将 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件，如此工作流程摘要中所示： ```yaml jobs: @@ -204,29 +212,29 @@ jobs: ``` {% endif %} -### Running additional queries +### 运行额外查询 {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to the private repository. +要添加一个或多个查询套件，请在配置文件中添加 `queries` 部分。 如果查询在私有仓库中，请使用 `external-repository-token` 参数来指定可以访问私有仓库的令牌。 {% raw %} ``` yaml - uses: github/codeql-action/init@v1 with: queries: COMMA-SEPARATED LIST OF PATHS - # Optional. Provide a token to access private repositories. + # Optional. 提供令牌来访问私有仓库. external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` {% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +您也可以在配置文件中指定额外查询套件以运行它们。 查询套件是查询的集合，通常按目的或语言分组。 {% data reusables.code-scanning.codeql-query-suites %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +如果还使用配置文件进行自定义设置，则将使用工作流程中指定的任何额外查询，而不是配置文件中指定的任何查询。 如果您要运行此处指定的额外查询与配置文件中指定的查询的组合，请在工作流程中的 `queries` 值之前加上前缀 `+` 符号。 有关配置文件的示例，请参阅“[配置文件示例](#example-configuration-files)”。 -In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. +在下面的示例中，`+` 符号可确保结合使用额外查询与所引用配置文件中指定的任何查询。 {% raw %} ``` yaml @@ -238,11 +246,11 @@ In the following example, the `+` symbol ensures that the specified additional q ``` {% endraw %} -### Using a custom configuration file +### 使用第三方代码扫描工具 -As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. +除了在工作流程文件中指定要运行的查询之外，您还可以在单独的配置文件中执行此操作。 您还可以使用配置文件禁用默认查询，并指定分析过程中要扫描的目录。 -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. +在工作流程文件中，使用 `init` 操作的 `config-file` 参数指定要使用的配置文件的路径。 此示例加载配置文件 _./.github/codeql/codeql-config.yml_。 ``` yaml - uses: github/codeql-action/init@v1 @@ -252,7 +260,7 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp {% data reusables.code-scanning.custom-configuration-file %} -If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository. +如果配置文件位于外部私有仓库中，请使用 `init` 操作的 `external-repository-token` 参数来指定可以访问私有仓库的令牌。 {% raw %} ```yaml @@ -262,11 +270,11 @@ with: ``` {% endraw %} -The settings in the configuration file are written in YAML format. +配置文件中的设置以 YAML 格式编写。 -#### Specifying additional queries +#### 指定额外查询 -You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file. +您可以在 `queries` 数组中指定额外查询。 数组的每个元素都包含一个 `uses` 参数，该参数的值标识单个查询文件、包含查询文件的目录或查询套件定义文件。 ``` yaml queries: @@ -275,17 +283,17 @@ queries: - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls ``` -Optionally, you can give each array element a name, as shown in the example configuration files below. +（可选）您可以给每个数组元素一个名称，如下面的示例配置文件所示。 -For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. +有关额外查询的更多信息，请参阅上面的“[运行额外查询](#running-additional-queries)”。 -#### Disabling the default queries +#### 禁用默认查询 -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +如果只想运行自定义查询，您可以通过在配置文件中添加 `disable-default-queries: true` 来禁用默认安全查询。 -#### Specifying directories to scan +#### 指定要扫描的目录 -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. +对于 {% data variables.product.prodname_codeql %} 支持的解释语言（Python 和 JavaScript/TypeScript），您可以通过在配置文件中添加 `paths` 数组将 {% data variables.product.prodname_code_scanning %} 限制到特定目录中的文件。 添加 `paths-ignore` 数组可从分析排除特定目录中的文件。 ``` yaml paths: @@ -297,27 +305,27 @@ paths-ignore: {% note %} -**Note**: +**注**： -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* 在 {% data variables.product.prodname_code_scanning %} 配置文件上下文中使用的 `paths` 和 `paths-ignore` 关键字，不应与用于工作流程中 `on..paths` 的相同关键字相混淆。 当它们用于修改工作流程中的 `on.` 时，它们将决定在有人修改指定目录中的代码时是否运行操作。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 +* `**` 字符只能用在行的开头或结尾，或用斜杠包围，并且不能将 `**` 与其他字符混合在一起。 例如，`foo/**`、`**/foo` 和 `foo/**/bar` 都是允许的语法，但 `**foo` 不是。 但是，可以将单星号与其他字符一起使用，如示例中所示。 您需要引用任何包含 `*` 字符的内容。 {% endnote %} -For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +对于编译的语言，如果要将 {% data variables.product.prodname_code_scanning %} 限制到项目中的特定目录，您必须在工作流程中指定适当的构建步骤。 用于在构建过程中排除目录的命令将取决于您的构建系统。 更多信息请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +在修改特定目录中的代码时，您可以快速分析单个仓库中的小部分。 您需要在构建步骤中排除目录并在工作流程文件中对 [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) 使用 `paths-ignore` 和 `paths` 关键字。 -#### Example configuration files +#### 配置文件示例 {% data reusables.code-scanning.example-configuration-files %} -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages +### 为编译语言配置 {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} -{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)." +{% data reusables.code-scanning.autobuild-add-build-steps %} 有关如何为编译语言配置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)”。 -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} +### 将 {% data variables.product.prodname_code_scanning %} 数据上传到 {% data variables.product.prodname_dotcom %} -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)." +{% data variables.product.prodname_dotcom %} 可显示通过第三方工具在外部生成的代码分析数据。 通过在工作流程中添加 `upload-sarif` 操作，您可以在 {% data variables.product.prodname_dotcom %} 中显示第三方工具的代码分析。 更多信息请参阅“[将 SARIF 文件上传到 GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)”。 diff --git a/translations/zh-CN/content/code-security/secure-coding/index.md b/translations/zh-CN/content/code-security/secure-coding/index.md index 0f38a80525..8f7c649485 100644 --- a/translations/zh-CN/content/code-security/secure-coding/index.md +++ b/translations/zh-CN/content/code-security/secure-coding/index.md @@ -1,7 +1,7 @@ --- title: 查找代码中的安全漏洞和错误 shortTitle: 安全编码 -intro: '使用秘密扫描来识别和修复代码中潜在的安全漏洞和其他错误，以确保代码的安全。' +intro: 'Keep your code secure by using {% data variables.product.prodname_code_scanning %} to identify and fix potential security vulnerabilities and other errors in your code.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code diff --git a/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md index 90c0803d5f..50e8473128 100644 --- a/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/zh-CN/content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md @@ -45,7 +45,14 @@ topics: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -1. 在 "{% data variables.product.prodname_code_scanning_capc %}" 下，单击要探索的警报。 ![警报摘要](/assets/images/help/repository/code-scanning-click-alert.png) +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} +1. （可选）使用下拉菜单过滤警报。 例如，您可以通过用于识别警报的工具进行过滤。 ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +1. 在 "{% data variables.product.prodname_code_scanning_capc %}" 下，单击要探索的警报。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![警报摘要](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![来自 {% data variables.product.prodname_code_scanning %} 的警报列表](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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) @@ -57,7 +64,11 @@ topics: 警报只能在一个分支中修复。 您可以在警报摘要上使用“Branch（分支）”下拉菜单检查警报是否是在特定分支中修复的。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![按分支过滤警报](/assets/images/help/repository/code-scanning-branch-filter.png) +{% else %} +![按分支过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} @@ -110,11 +121,19 @@ topics: （可选）您可以使用过滤器显示警报子集，然后一次删除所有匹配的警报。 例如，如果您从 {% data variables.product.prodname_codeql %} 分析中删除了查询，您可以使用“Rule（规则）”过滤器仅列出该查询的警报，然后选择并删除所有这些警报。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![按规则过滤警报](/assets/images/help/repository/code-scanning-filter-by-rule.png) +{% else %} + ![按规则过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) +{% endif %} 1. 如果要忽略警报，请务必先了解警报，以便选择正确的忽略原因。 单击要了解的警报。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![从摘要列表中打开警报](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![来自 {% data variables.product.prodname_code_scanning %} 的警报列表](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 1. 查看警报，然后单击 **Dismiss（忽略）**并选择关闭警报的原因。 ![选择忽略警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) diff --git a/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md index 10ea8074d7..8a99c9580c 100644 --- a/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md +++ b/translations/zh-CN/content/code-security/secure-coding/setting-up-code-scanning-for-a-repository.md @@ -32,7 +32,7 @@ topics: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 2" %}工作流程仅在与仓库中检测到的编程语言相关时才会显示。 {% data variables.product.prodname_codeql_workflow %} 始终显示，但仅在 {% data variables.product.prodname_codeql %} 分析支持仓库中存在的语言时才启用“Set up this workflow（设置此工作流程）”按钮。{% endif %} 5. Optionally, to customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." @@ -72,7 +72,11 @@ topics: **注意：** 如果您提出拉取请求以将 {% data variables.product.prodname_code_scanning %} 工作流程添加到仓库，则在合并拉取请求之前，来自该拉取请求的警报不会直接显示在 {% data variables.product.prodname_code_scanning_capc %} 页面上。 如果发现任何警报，您可以在合并拉取请求之前查看这些警报，方法是在 {% data variables.product.prodname_code_scanning_capc %} 页面上的横幅中点击**发现的 _n_ 条警报**链接。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![点击"发现的 n 条警报"链接](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![点击"发现的 n 条警报"链接](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} {% endnote %} @@ -98,7 +102,11 @@ topics: 要检查是否扫描了分支，请转到 {% data variables.product.prodname_code_scanning_capc %} 页面，单击 **Branch<（分支）**下拉菜单并选择相关分支。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/help/repository/code-scanning-branch-dropdown.png) +{% else %} + ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) +{% endif %} {% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} diff --git a/translations/zh-CN/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md index 2353e87c59..39fa5c950f 100644 --- a/translations/zh-CN/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md +++ b/translations/zh-CN/content/code-security/secure-coding/troubleshooting-the-codeql-workflow.md @@ -1,7 +1,7 @@ --- -title: Troubleshooting the CodeQL workflow -shortTitle: Troubleshooting CodeQL -intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.' +title: CodeQL 工作流程疑难解答 +shortTitle: CodeQL 疑难解答 +intro: '如果您在 {% data variables.product.prodname_code_scanning %} 方面遇到问题，可使用这些提示来解决问题。' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning @@ -11,25 +11,25 @@ versions: enterprise-server: '>=3.0' github-ae: '*' topics: - - security + - 安全 --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.not-available %} -### Producing detailed logs for debugging +### 生成详细的调试日志 -To produce more detailed logging output, you can enable step debug logging. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)." +要生成更详细的日志输出，您可以启用步骤调试日志记录。 更多信息请参阅“[启用调试日志记录](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)”。 -### Automatic build for a compiled language fails +### 编译语言的自动构建失败 -If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps. +如果项目中编译语言的代码自动构建失败，请尝试以下疑难解答步骤。 -- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +- 从 {% data variables.product.prodname_code_scanning %} 工作流程中删除 `autobuild` 步骤，并添加特定构建步骤。 有关编辑工作流程的信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)”。 有关替换 `autobuild` 步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 -- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. +- 如果您的工作流程未明确指定要分析的语言，则 {% data variables.product.prodname_codeql %} 会隐式检测代码库中支持的语言。 在此配置中，对于编译语言 C/C++、C# 和 Java，{% data variables.product.prodname_codeql %} 只分析涵盖最多源文件的语言。 编辑工作流程并添加一个构建矩阵，以指定要分析的语言。 默认的 CodeQL 分析工作流程使用这种矩阵。 - The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step: + 以下工作流程摘录显示了如何在作业策略中使用矩阵来指定语言，然后在“初始化 {% data variables.product.prodname_codeql %}”步骤中引用每种语言： ```yaml jobs: @@ -47,14 +47,14 @@ If an automatic build of code for a compiled language within your project fails, with: languages: {% raw %}${{ matrix.language }}{% endraw %} ``` - - For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)." -### No code found during the build + 有关编辑工作流程的更多信息，请参阅“[配置代码扫描](/code-security/secure-coding/configuring-code-scanning)”。 -If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure: +### 构建过程中找不到代码 -1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by updating the list of languages in the `language` matrix. For example, the following configuration will analyze only Go, and JavaScript. +如果工作流程失败，出现错误 `No source code was seen during the build` 或 `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`，则表明 {% data variables.product.prodname_codeql %} 无法监控您的代码。 有几个原因可以解释这种失败： + +1. 自动语言检测发现了受支持的语言，但仓库中没有该语言的可分析代码。 一个典型的例子是，我们的语言检测服务发现了一个与特定的编程语言相关的文件，例如 `.h` 或 `.gyp` 文件，但仓库中没有相应的可执行代码。 要解决此问题，您可以通过更新 `language` 矩阵中的语言列表来手动定义要分析的语言。 例如，以下配置将仅分析 Go 和 JavaScript。 ```yaml strategy: @@ -65,81 +65,81 @@ If your workflow fails with an error `No source code was seen during the build` # ['csharp', 'cpp', 'go', 'java', 'javascript', 'python'] language: ['go', 'javascript'] ``` -For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. -1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually. For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. -1. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are: +更多信息请参阅上面“[编译语言的自动构建失败](#automatic-build-for-a-compiled-language-fails)”中的工作流程摘要。 +1. {% data variables.product.prodname_code_scanning %} 工作流程在分析一种已编译的语言（C、C++、C# 或 Java），但代码尚未编译。 默认情况下，{% data variables.product.prodname_codeql %} 分析工作流程包含 `autobuild` 步骤，但是，此步骤是一个尽力而为的过程，可能无法成功构建您的代码，具体取决于您的特定构建环境。 如果您删除了 `autobuild` 步骤但没有手动添加构建步骤，编译也可能会失败。 有关指定构建步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 +1. 工作流程在分析一种编译语言（C、C++、C# 或 Java），但构建的一部分被缓存以提高性能（最有可能发生在 Gradle 或 Bazel 等构建系统中）。 因为 {% data variables.product.prodname_codeql %} 观察编译器的活动以了解仓库中的数据流，因此 {% data variables.product.prodname_codeql %} 需要进行完整的构建才能执行分析。 +1. 工作流程在分析编译语言（C、C++、C# 或 Java），但工作流程中的 `init` 与 `analyze` 步骤之间不发生编译。 {% data variables.product.prodname_codeql %} 需要这两个步骤之间发生构建以观察编译器的活动并执行分析。 +1. 您的编译代码（使用 C、C ++、C＃ 或 Java）已成功编译，但 {% data variables.product.prodname_codeql %} 无法检测到编译器调用。 最常见的原因是： - * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)." - * Building using a distributed build system external to GitHub Actions, using a daemon process. - * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. + * 在独立于 {% data variables.product.prodname_codeql %} 的容器中运行构建过程。 更多信息请参阅“[在容器中运行 CodeQL 代码扫描](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)”。 + * 使用 GitHub Actions 外部的分布式构建系统，使用守护进程构建。 + * {% data variables.product.prodname_codeql %} 不知道您使用的特定编译器。 - For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. - - For example, the following configuration for C# will pass the flag during the first build step. + 对于 .NET Framework 项目以及使用 `dotnet build` 或 `msbuild`（目标 .NET Core 2）的 C# 项目，在构建代码时，您应该在工作流程的 `run` 步骤中指定 `/p:UseSharedCompilation=false`。 .NET Core 3.0 及更高版本不需要 `UseSharedCompilation` 标志。 + + 例如，以下 C# 的配置将在第一个构建步骤中传递标志。 ``` yaml - run: | dotnet build /p:UseSharedCompilation=false ``` - If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}. + 如果您在特定编译器或配置方面遇到其他问题，请联系 {% data variables.contact.contact_support %}。 -For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +有关指定构建步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 -### Portions of my repository were not analyzed using `autobuild` +### 我的仓库中有部分内容未使用 `autobuild` 进行分析 -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](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +{% data variables.product.prodname_codeql %} `autobuild` 功能使用启发式方法在仓库中构建代码，但有时这种方法会导致对仓库的分析不完整。 例如，当单个仓库中存在多个 `build.sh` 命令时，分析可能不完整，因为 `autobuild` 步骤将只执行其中一个命令。 解决方案是将 `autobuild` 步骤替换为可构建要分析的所有源代码的构建步骤。 更多信息请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 -### 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. +如果使用 {% data variables.product.prodname_codeql %} 分析进行的构建花费的时间太长，则可以尝试几种方法来减少构建时间。 -#### Increase the memory or cores - -If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners. - -#### Use matrix builds to parallelize the analysis - -The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. - -#### Reduce the amount of code being analyzed in a single workflow +#### 增加内存或内核 Analysis time is typically proportional to the amount of code being analyzed. You can reduce the analysis time by reducing the amount of code being analyzed at once, for example, by excluding test code, or breaking analysis into multiple workflows that analyze only a subset of your code at a time. -For compiled languages like Java, C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build only the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." +#### 使用矩阵构建来并行化分析 -For interpreted languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without a specific build, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)." +默认 {% data variables.product.prodname_codeql_workflow %} 使用语言的构建矩阵，这会导致每种语言的分析并行运行。 如果在“初始化 CodeQL”步骤中指定了要直接分析的语言，则将依次进行每种语言的分析。 要加快对多种语言的分析，请修改工作流程以使用矩阵。 更多信息请参阅上面“[编译语言的自动构建失败](#automatic-build-for-a-compiled-language-fails)”中的工作流程摘要。 -If you split your analysis into multiple workflows as described above, we still recommend that you have at least one workflow which runs on a `schedule` which analyzes all of the code in your repository. Because {% data variables.product.prodname_codeql %} analyzes data flows between components, some complex security behaviors may only be detected on a complete build. +#### 减少单个工作流程中要分析的代码量 -#### Run only during a `schedule` event +分析时间通常与要分析的代码量成正比。 您可以通过减少一次分析的代码量来缩短分析时间，例如，排除测试代码，或将分析分解为多个工作流程，这些工作流程一次只分析一部分代码。 -If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)." +对于 Java、C、C++ 和 C# 等编译语言，{% data variables.product.prodname_codeql %} 分析在工作流程运行过程中构建的所有代码。 要限制要分析的代码量，请通过在 `run` 块中指定自己的构建步骤，仅构建您要分析的代码。 您可以通过对 `pull_request` 和 `push` 事件使用 `paths` 或 `paths-ignore` 过滤器来组合指定自己的构建步骤，以确保工作流程仅在特定代码发生更改时运行。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 + +对于 Go、JavaScript、Python 和 TypeScript 等解释性语言，{% data variables.product.prodname_codeql %} 无需特定构建即可进行分析，您可以指定额外配置选项以限制要分析的代码量。 更多信息请参阅“[指定要扫描的目录](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)”。 + +如果您按上文所述将分析拆分为多个工作流程，我们仍然建议您至少保留一个按 `schedule` 运行的工作流程分析仓库中的所有代码。 因为 {% data variables.product.prodname_codeql %} 分析组件之间的数据流量，所以某些复杂的安全行为只能在完整的构建中检测到。 + +#### 仅在 `schedule` 事件期间运行 + +如果分析速度仍然太慢，无法在 `push` 或 `pull_request` 事件期间运行，则您可能需要设置仅在 `schedule` 事件期间运行。 更多信息请参阅“[事件](/actions/learn-github-actions/introduction-to-github-actions#events)”。 {% if currentVersion == "free-pro-team@latest" %} -### Results differ between analysis platforms +### 分析平台之间的结果差异 -If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows. +如果您分析的是使用 Python 编写的代码，根据您是在 Linux、macOS 还是 Windows 上运行 {% data variables.product.prodname_codeql_workflow %}，可能会看到不同的结果。 -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](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)." +在使用 Linux 的 GitHub 托管运行器上，{% data variables.product.prodname_codeql_workflow %} 会尝试安装和分析 Python 依赖项，这可能导致更多结果。 要禁用自动安装，请将 `setup-python-dependencies: false` 添加到工作流程的“初始化 CodeQL”步骤。 有关配置 Python 依赖项分析的更多信息，请参阅“[分析 Python 依赖项](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)”。 {% endif %} -### Error: "Server 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 %}. +如果 {% data variables.product.prodname_code_scanning %} 的工作流程运行因服务器错误而失败，请尝试再次运行工作流程。 如果问题仍然存在，请联系 {% data variables.contact.contact_support %}。 -### Error: "Out of disk" or "Out of memory" +### 错误：“Out of disk（磁盘空间不足）”或“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 %} +On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the hosted {% data variables.product.prodname_actions %} runner. If you encounter this issue, contact {% data variables.contact.contact_support %} so that we can investigate the problem. +{% if currentVersion == "free-pro-team@latest" %}如果您在托管的 {% data variables.product.prodname_actions %} 运行器上遇到此问题，请联系 {% data variables.contact.contact_support %}，以便我们调查。 +By default, {% data variables.product.prodname_codeql %} performs analysis of each language sequentially, which can impact performance, especially for repositories with more than one language. You can speed analysis up by using a build matrix that splits the analysis by language. For more information, see "[Configuring a build matrix](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)." -### Warning: "git checkout HEAD^2 is no longer necessary" +### 警告：“git checkout HEAD^2 is no longer necessary（不再需要 Git 检出头^2）” -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: +如果您使用的是旧 {% data variables.product.prodname_codeql %} 工作流程，您可能会在输出中收到来自“初始化 {% data variables.product.prodname_codeql %}”操作的以下警告： ``` Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer @@ -147,7 +147,7 @@ necessary. Please remove this step as Code Scanning recommends analyzing the mer 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. +通过从 {% data variables.product.prodname_codeql %} 工作流程中删除以下行来修复此问题。 这些行包含在 {% data variables.product.prodname_codeql %} 工作流程初始版本中 `Analyze` 作业的 `steps` 部分。 ```yaml with: @@ -159,9 +159,9 @@ Fix this by removing the following lines from the {% data variables.product.prod # 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: +修订后的工作流程 `steps` 部分将如下所示： ```yaml steps: @@ -175,4 +175,4 @@ The revised `steps` section of the workflow will look like this: ... ``` -For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." +有关编辑 {% data variables.product.prodname_codeql %} 工作流程文件的更多信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)”。 diff --git a/translations/zh-CN/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/zh-CN/content/code-security/security-advisories/editing-a-security-advisory.md index f624207715..0a543a0754 100644 --- a/translations/zh-CN/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/zh-CN/content/code-security/security-advisories/editing-a-security-advisory.md @@ -17,6 +17,8 @@ topics: 如果某人接受积分，则其用户名将显示在安全通告的“Credits（积分）”部分。 拥有仓库读取权限的任何人都可以看到通告和接受其积分的人。 +如果您认为您应该获得安全通告积分，请联系通告的创建者并让他们编辑通告以包含您的贡献积分。 只有通告创建者才可计入您的功劳积分，因此请不要就安全通告的积分一事联系 GitHub 支持。 + ### 编辑安全通告 {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/zh-CN/content/code-security/security-overview/exploring-security-alerts.md b/translations/zh-CN/content/code-security/security-overview/exploring-security-alerts.md index 091d73357b..d406d2af7f 100644 --- a/translations/zh-CN/content/code-security/security-overview/exploring-security-alerts.md +++ b/translations/zh-CN/content/code-security/security-overview/exploring-security-alerts.md @@ -11,7 +11,7 @@ versions: ### 关于安全概述 -您可以使用安全概述来简要了解组织的安全状态，或识别需要干预的问题仓库。 在组织级别，安全概述显示组织拥有的仓库的聚合和仓库特定安全信息。 在团队级别，安全概述显示团队拥有管理权限的仓库特定安全信息。 更多信息请参阅“[管理团队的组织仓库访问权限](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository)”。 +您可以使用安全概述来简要了解组织的安全状态，或识别需要干预的问题仓库。 在组织级别，安全概述显示组织拥有的仓库的聚合和仓库特定安全信息。 在团队级别，安全概述显示团队拥有管理权限的仓库特定安全信息。 更多信息请参阅“[管理团队的组织仓库访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)”。 安全概述指示是否为组织拥有的仓库启用了 {% data variables.product.prodname_GH_advanced_security %} 功能，并且合并来自 {% data variables.product.prodname_advanced_security %} 功能的警报，包括 {% data variables.product.prodname_code_scanning %} 警报、{% data variables.product.prodname_dependabot_alerts %} 和 {% data variables.product.prodname_secret_scanning %} 警报。 更多信息请参阅“[关于保护仓库](/code-security/getting-started/about-securing-your-repository)”。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md index ea3e7df054..8e2456a81e 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies.md @@ -49,9 +49,9 @@ topics: {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} 默认会检测_公共_仓库中有漏洞的依赖项并生成 {% data variables.product.prodname_dependabot_alerts %}。 私有仓库的所有者或具有管理员权限的人员可以通过为其仓库启用依赖关系图和 {% data variables.product.prodname_dependabot_alerts %} 来启用 {% data variables.product.prodname_dependabot_alerts %}。 -您也可以为用户帐户或组织拥有的所有仓库启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[管理用户帐户的安全和分析设置](/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_alerts %}。 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -有关 {% data variables.product.prodname_dependabot_alerts %} 相关操作的权限要求的信息，请参阅“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)”。 +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." {% data variables.product.product_name %} 将立即开始生成依赖关系图，并在发现任何有漏洞的依赖项后立即生成警报。 依赖关系图通常在几分钟之内填充，但对于依赖项很多的仓库，可能需要更长时间。 更多信息请参阅“[管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)”。 {% endif %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md index 8fc978f0dd..e2c3f43f36 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/about-dependabot-version-updates.md @@ -12,8 +12,6 @@ topics: - 仓库 --- -{% data reusables.dependabot.beta-note %} - ### 关于 {% data variables.product.prodname_dependabot_version_updates %} {% data variables.product.prodname_dependabot %} 负责维护您的依赖项。 您可以使用它来确保仓库自动跟上它所依赖的包和应用程序的最新版本。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md index 3f516de9cb..aedb7a4735 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/about-the-dependency-graph.md @@ -1,94 +1,95 @@ --- -title: About the dependency graph -intro: 'You can use the dependency graph to identify all your project''s dependencies. The dependency graph supports a range of popular package ecosystems.' +title: 关于依赖项图 +intro: '您可以使用依赖关系图来识别项目的所有依赖项。 依赖关系图支持一系列流行的软件包生态系统。' redirect_from: - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph versions: free-pro-team: '*' enterprise-server: '>=3.0' topics: - - repositories + - 仓库 --- + -### Dependency graph availability +### 依赖关系图可用性 -The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} +依赖关系图适用于使用支持的文件格式、以支持的包生态系统定义依赖项的每个{% if currentVersion == "free-pro-team@latest" %} 公共{% endif %} 仓库。{% if currentVersion == "free-pro-team@latest" %} 仓库管理员也可对私有仓库设置依赖关系图。{% endif %} {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### 关于依赖项图 -The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: +依赖项图是存储在仓库中的清单和锁定文件的摘要。 对于每个仓库，它会显示{% if currentversion == "free proteam@latest" %}： -- Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} +- 依赖项、它依赖的生态系统和包 +- 依赖项、依赖于它的仓库和包{% else %} 依赖项，即它所依赖的生态系统和包。 {% data variables.product.prodname_ghe_server %} 不计算有关依赖项、仓库和依赖于仓库的包的信息。{% endif %} -When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. +向 {% data variables.product.product_name %} 推送提交以更改支持的清单或锁定文件或将其添加到默认分支时，依赖项图会自动更新。.{% if currentVersion == "free-pro-team@latest" %}此外，当有人向某个依赖项的仓库推送更改时，该图也会更新。{% endif %}有关支持的生态系统和清单文件的信息，请参阅下面的“[支持的包生态系统](#supported-package-ecosystems)”。 {% if currentVersion == "free-pro-team@latest" %} -When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." +当创建包含针对默认分支的依赖项更改的拉取请求时，{% data variables.product.prodname_dotcom %} 使用依赖关系图向拉取请求添加依赖项审查。 它们指示依赖项是否包含漏洞，如果是，则指示已修复漏洞的依赖项版本。 更多信息请参阅“[关于依赖项审查](/code-security/supply-chain-security/about-dependency-review)”。 {% endif %} -### Dependencies included +### 包含的依赖项 -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +依赖关系图包括清单和锁定文件中详述的所有依赖项，或支持的生态系统的同等项。 这包括： -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- 在清单或锁定文件中明确定义的直接依赖项 +- 这些直接依赖项的间接依赖项，也称为过渡依赖项或子依赖项 -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +依赖项图通过锁定文件明确标识间接依赖项{% if currentVersion == "free-pro-team@latest" %} 或者通过检查直接依赖项的依赖项来标识间接依赖项。 对于最可靠的依赖关系图， 您应该使用锁定文件（或其等效项），因为它们准确地定义了您当前使用的直接和间接依赖项版本。 如果您使用锁定文件，还要确保仓库的所有贡献者都使用相同的版本，这样更便于您{% else %}从锁定文件{% endif %} 测试和调试代码。 {% if currentVersion == "free-pro-team@latest" %} -### Dependents included +### 包含的依赖关系 -For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} +对于公共仓库，仅报告依赖于它或它发布的包的公共仓库。 对于私有仓库，不报告此信息。{% endif %} -### Using the dependency graph +### 使用依赖关系图 -You can use the dependency graph to: +您可以使用依赖关系图： -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} -- See information about vulnerable dependencies in pull requests. 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 %} +- 探索您的代码所依赖的仓库{% if currentVersion == "free-pro-team@latest" %} 以及依赖于它的仓库{% endif %}。 更多信息请参阅“[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)”。 {% if currentVersion == "free-pro-team@latest" %} +- 在单个仪表板中查看组织仓库中使用的依赖项摘要。 更多信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)”。{% endif %} +- 查看和更新仓库中有漏洞的依赖项。 更多信息请参阅“[关于有漏洞依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。{% if currentVersion == "free-pro-team@latest" %} +- 查看拉取请求中有漏洞依赖项的相关信息。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。{% endif %} -### Enabling the dependency graph +### 启用依赖关系图 -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}要生成依赖关系图，{% data variables.product.product_name %} 需要对仓库的依赖项清单和锁定文件的只读访问权限。 依赖关系图自动为所有公共仓库生成，您可以选择为私有仓库启用它。 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" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}如果依赖项图在系统中不可用，则站点管理员可以启用依赖项图和 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上的有漏洞依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。{% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} 如果依赖项图在系统中不可用，则站点管理员可以启用依赖项图和安全警报。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。 {% endif %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +首次启用依赖关系图时，将立即剖析受支持的生态系统的任何清单和锁定文件。 依赖关系图通常在几分钟之内填充，但对于依赖项很多的仓库，可能需要更长时间。 启用后，该图将在每次推送到仓库{% if currentVersion == "free-pro-team@latest" %} 以及每次推送到该图中的其他仓库{% endif %} 时自动更新。 -### Supported package ecosystems +### 支持的包生态系统 -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +建议的格式明确定义哪些版本用于所有直接和所有间接依赖项。 如果使用这些格式，则依赖关系图更准确。 它还反映当前的构建设置，使依赖项图能够报告直接和间接依赖项中的漏洞。{% if currentVersion == "free-pro-team@latest" %} 从清单文件（或等效文件）推断的间接依赖项将不包括在漏洞依赖项检查中。{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +| 包管理器 | 语言 | 建议的格式 | 所有支持的格式 | +| ------------ | --------------------- | -------------------------------------------------- | -------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`、`composer.lock` | +| `dotnet` CLI | .NET 语言（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`、`pipfile.lock`、`setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`、`Gemfile`、`*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`、`yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**注：**如果在 `setup.py` 文件中列出 Python 依赖项，我们可能无法剖析和列出项目中的每个依赖项。 {% endnote %} -### Further reading +### 延伸阅读 -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia -- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} +- 维基百科上的“[依赖关系图](https://en.wikipedia.org/wiki/Dependency_graph)” +- “[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)” {% if currentVersion == "free-pro-team@latest" %} +- "[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" +- "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[漏洞依赖项检测疑难解答](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md index faf347e217..e61a3e3813 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/configuration-options-for-dependency-updates.md @@ -11,8 +11,6 @@ topics: - 仓库 --- -{% data reusables.dependabot.beta-note %} - ### 关于 *dependabot.yml* 文件 {% data variables.product.prodname_dependabot %} 配置文件 *dependabot.yml* 使用 YAML 语法。 如果您是 YAML 的新用户并想要了解更多信息，请参阅“[五分钟了解 YAML](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)”。 @@ -323,7 +321,7 @@ updates: {% note %} -**注意**：即使您将不可访问的依赖项添加到配置文件的`忽略`选项，{% data variables.product.prodname_dependabot %} 也仅在可以访问文件中的所有依赖项时才可在清单文件或锁定文件上运行版本更新。 更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)”和“[排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)”。 +**注意**：即使您将不可访问的依赖项添加到配置文件的`忽略`选项，{% data variables.product.prodname_dependabot %} 也仅在可以访问文件中的所有依赖项时才可在清单文件或锁定文件上运行版本更新。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)”和“[排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)”。 {% endnote %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md index 01f67e2205..96bdddfcae 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/configuring-dependabot-security-updates.md @@ -49,7 +49,7 @@ topics: 您可以对单个仓库启用或禁用 {% 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 %}。 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data variables.product.prodname_dependabot_security_updates %} 需要特定的仓库设置。 更多信息请参阅“[支持的仓库](#supported-repositories)”。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md index 182e15babb..705c0ac6f1 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies.md @@ -1,60 +1,60 @@ --- -title: Configuring notifications for vulnerable dependencies -shortTitle: Configuring notifications -intro: 'Optimize how you receive notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.' +title: 配置有漏洞依赖项的通知 +shortTitle: 配置通知 +intro: '优化您如何接收有关 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报的通知。' redirect_from: -- /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies + - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies versions: free-pro-team: '*' enterprise-server: '>=3.0' topics: - - security + - 安全 --- -### About notifications for vulnerable dependencies +### 关于有漏洞依赖项的通知 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. -{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}当 {% data variables.product.prodname_dependabot %} 在您的仓库中检测到有漏洞依赖项时，我们将生成 {% data variables.product.prodname_dependabot %} 警报，并将其显示在仓库的“Security（安全）”选项卡中。 {% data variables.product.product_name %} 根据通知首选项将新警报通知受影响仓库的维护员。{% else %}When {% data variables.product.product_name %} 在仓库中检测到有漏洞依赖项时，它将发送安全警报。{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} 在所有公共仓库中默认启用。 对于 {% data variables.product.prodname_dependabot_alerts %}，默认情况下，您将通过电子邮件收到按特定漏洞分组的 {% data variables.product.prodname_dependabot_alerts %}。 +{% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}如果您是组织所有者，您可以对组织中的所有仓库一键启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 您也可以设置是否对新建的仓库启用或禁用有漏洞依赖项检测。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/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" %} -Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +站点管理员必须先对 {% data variables.product.product_location %} 易受攻击的依赖项启用安全警报，然后您才可使用此功能。 更多信息请参阅“[为 {% 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" %} -By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %} +默认情况下，如果站点管理员已在您的企业上配置电子邮件通知，您将会通过电子邮件收到 {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}。{% endif %} -{% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}站点管理员还可以启用无通知 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上的有漏洞依赖项启用 {% data variables.product.prodname_dependabot_alerts %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。{% endif %} -{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if currentVersion ver_lt "enterprise-server@2.22" %}站点管理员还可以启用无通知安全警报。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。 -### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} +### 为 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}配置通知 -You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." +您可以从每个页面顶部显示的管理通知下拉菜单 {% octicon "bell" aria-label="The notifications bell" %} 为您自己或您的组织配置通知设置。 更多信息请参阅“[配置通知](/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" %} - ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png) + ![{% data variables.product.prodname_dependabot_alerts %} 选项](/assets/images/help/notifications-v2/dependabot-alerts-options.png) {% else %} - ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png) + ![安全警报选项](/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. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." +**注：** 您可以过滤 {% data variables.product.company_short %} 上的通知以显示{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} 安全{% endif %}警报。 更多信息请参阅“[从收件箱管理通知](/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 %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}”。{% endif %} -### How to reduce the noise from notifications for vulnerable dependencies +### 如何减少有漏洞依赖项通知的干扰 -If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +如果您担心会收到太多 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}通知，我们建议您在保持启用{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}的情况下，选择接收每周电子邮件摘要或关闭通知。 您仍然可以导航到仓库的“Security（安全）”选项卡以查看 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[查看和更新仓库中的有漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)”。{% endif %} -### Further reading +### 延伸阅读 -- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" -- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)" +- "[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" +- “[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)”。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/customizing-dependency-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/customizing-dependency-updates.md index 3baafd86c8..54bf5a1cbc 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/customizing-dependency-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/customizing-dependency-updates.md @@ -10,8 +10,6 @@ topics: - 仓库 --- -{% data reusables.dependabot.beta-note %} - ### 关于自定义依赖项更新 启用版本更新后，您可以自定义 {% data variables.product.prodname_dependabot %} 通过向 *dependabot.yml* 文件添加更多选项来维护依赖项。 例如，您可以： diff --git a/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md index d6453dd5fd..6f6f079022 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/enabling-and-disabling-version-updates.md @@ -12,8 +12,6 @@ topics: -{% data reusables.dependabot.beta-note-no-link %} - ### 关于依赖项的版本更新 通过将 *dependabot.yml* 配置文件检入仓库的 `.github` 目录，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 {% data variables.product.prodname_dependabot %} 然后提出拉取请求，使您配置的依赖项保持最新。 对于您想更新的每个包管理器的依赖项，必须指定包清单文件的位置及为文件所列的依赖项检查更新的频率。 有关启用安全更新的信息，请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)。” @@ -117,7 +115,7 @@ updates: interval: "daily" # Overwrite any ignores created using `@dependabot ignore` commands ignore: - # Ignore updates to packages that start 'aws' + # Ignore updates to packages that start with 'aws' # Wildcards match zero or more arbitrary characters - dependency-name: "aws*" # Ignore some updates to the 'express' package diff --git a/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md index 80fcfcb652..7f7e2ef42d 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository.md @@ -74,7 +74,7 @@ topics: 仓库管理员可以启用或禁用私有仓库的依赖关系图。 -您也可以为用户帐户或组织拥有的所有仓库启用或禁用依赖项图。 更多信息请参阅“[管理用户帐户的安全和分析设置](/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)”。 +您也可以为用户帐户或组织拥有的所有仓库启用或禁用依赖项图。 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](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -114,7 +114,7 @@ topics: ### 延伸阅读 - "[关于依赖项图](/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)" +- "[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/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)" {% endif %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md index e66b32a457..a74a634914 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot.md @@ -10,8 +10,6 @@ topics: - 仓库 --- -{% data reusables.dependabot.beta-note %} - ### 关于操作的 {% data variables.product.prodname_dependabot_version_updates %} 操作通常使用漏洞修复和新功能进行更新，以使自动化流程更可靠、更快速、更安全。 为 {% data variables.product.prodname_actions %} 启用 {% data variables.product.prodname_dependabot_version_updates %} 时，{% data variables.product.prodname_dependabot %} 将帮助确保仓库 *workflow.yml* 文件中操作的引用保持最新。 对于文件中的每个操作，{% data variables.product.prodname_dependabot %} 根据最新版本检查操作的引用（通常是与操作关联的版本号或提交标识符）。 如果操作有更新的版本，{% data variables.product.prodname_dependabot %} 将向您发送拉取请求，要求将工作流程文件中的引用更新到最新版本。 有关 {% data variables.product.prodname_dependabot_version_updates %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)”。 有关为 {% data variables.product.prodname_actions %} 配置工作流程的更多信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md index 9ff03171a0..058669db4d 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/listing-dependencies-configured-for-version-updates.md @@ -9,8 +9,6 @@ topics: - 仓库 --- -{% data reusables.dependabot.beta-note %} - ### 查看由 {% data variables.product.prodname_dependabot %} 监视的依赖项 启用版本更新后，可以使用仓库依赖关系图中的 **{% data variables.product.prodname_dependabot %}** 选项卡确认配置是否正确。 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md index 39c0ad0e23..b5a002dc0a 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates.md @@ -9,8 +9,6 @@ topics: - 仓库 --- -{% data reusables.dependabot.beta-note %} - ### 关于 {% data variables.product.prodname_dependabot %} 拉取请求 {% data reusables.dependabot.pull-request-introduction %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md b/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md index 3b794605c7..5773e924b1 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/troubleshooting-dependabot-errors.md @@ -1,106 +1,100 @@ --- -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 %}.' -shortTitle: Troubleshooting errors +title: 排查 Dependabot 错误 +intro: '有时，{% data variables.product.prodname_dependabot %} 无法提出拉取请求以更新依赖项。 您可以查看错误并取消阻止 {% data variables.product.prodname_dependabot %}。' +shortTitle: 排查错误 redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-github-dependabot-errors - /github/managing-security-vulnerabilities/troubleshooting-dependabot-errors versions: free-pro-team: '*' topics: - - security + - 安全 --- -{% 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. For more information, see "[Enabling and disabling 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 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. For more information, see "[Enabling and disabling 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. For more information, see "[Configuration options for dependency updates](/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 or access your dependencies +#### {% data variables.product.prodname_dependabot %} 无法解析或访问您的依赖项 -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 variables.product.prodname_dependabot %} 尝试检查是否需要更新仓库中的依赖项引用，但无法访问一个或多个依赖项文件，则操作将失败，并返回错误消息“{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files（无法解析语言依赖项文件）”。 API 错误类型为 `git_dependencies_not_reachable`。 -Similarly, if {% data variables.product.prodname_dependabot %} can't access a private package registry in which a dependency is located, one of the following errors is generated: +同样，如果 {% data variables.product.prodname_dependabot %} 不能访问依赖项所在的私有包注册表，则会产生以下错误之一： -* "Dependabot can't reach a dependency in a private package registry"
- (API error type: `private_source_not_reachable`) -* "Dependabot can't authenticate to a private package registry"
- (API error type:`private_source_authentication_failure`) -* "Dependabot timed out while waiting for a private package registry"
- (API error type:`private_source_timed_out`) -* "Dependabot couldn't validate the certificate for a private package registry"
- (API error type:`private_source_certificate_failure`) +* "Dependabot can't reach a dependency in a private package registry"
（Dependabot 无法连接私有包注册表中的依赖项） （API 错误类型：`private_source_not_reachable`） +* "Dependabot can't authenticate to a private package registry"
（Dependabot 无法向私有包注册表验证） （API 错误类型：`private_source_authentication_failure`） +* "Dependabot timed out while waiting for a private package registry"
（Dependabot 在等待私有包注册表时超时） （API 错误类型：`private_source_timed_out`） +* "Dependabot couldn't validate the certificate for a private package registry"
（Dependabot 无法验证私有包注册表的证书） （API 错误类型：`private_source_certificate_failure`） -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. +要让 {% data variables.product.prodname_dependabot %} 成功更新依赖项引用，请确保所有引用依赖项都托管在可访问的位置。 -**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)." +**仅限版本更新。**{% 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)”。 -### Triggering a {% data variables.product.prodname_dependabot %} pull request manually +### 手动触发 {% data variables.product.prodname_dependabot %} 拉取请求 -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**—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**. +- **安全更新**—显示 {% 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/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md index 6ff6af72f9..f60ba8fa2c 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit.md @@ -1,22 +1,22 @@ --- -title: Cherry-picking a commit -intro: You can pick a specific commit on one branch and copy the commit to another branch. +title: 优选提交 +intro: 您可以在一个分支上选择特定的提交，并将提交副本复制到另一个分支。 versions: free-pro-team: '*' --- -### About Git cherry-pick +### 关于 Git 优选 -You can cherry-pick a commit on one branch to create a copy of the commit with the same changes on another branch. If you commit changes to the wrong branch or want to make the same changes to another branch, you can cherry-pick the commit to apply the changes to another branch. You can also use cherry-picking to apply specific changes before you are ready to create or merge a pull request. For example, if you commit a bug fix to a feature branch, you can cherry-pick the commit with the bug fix to other branches of your project. +您可以在一个分支上优选提交在另一个分支上创建具有相同更改的提交副本。 如果将更改提交到错误的分支或想要对另一分支进行相同的更改，您可以优选提交将更改应用到另一个分支。 您也可以在准备创建或合并拉取请求之前使用优选来应用特定的更改。 例如，如果您向功能分支提交错误修复，则可优选包含错误修复的提交到项目的其他分支。 -You can also use cherry-picking when collaborating with a team. Some projects incorporate contributions by cherry-picking commits. For more information, see [Distributed Git - Maintaining a Project](https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_rebase_cherry_pick) in the Git documentation. +您还可以在与团队合作时使用优选。 有些项目包括通过优选提交所做的参与。 更多信息请参阅 Git 文档中的[分发的 Git - 维护项目](https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_rebase_cherry_pick)。 -### Cherry-picking a commit +### 优选提交 {% data reusables.desktop.current-branch-menu %} -2. In the list of branches, click the branch that has the commit that you want to cherry-pick. +2. 在分支列表中，单击包含您想要优的提交的分支。 {% data reusables.desktop.history-tab %} -4. Drag the commit that you want to cherry-pick to the {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** menu and drop the commit on the branch that you want to copy the commit to. ![Dragging a commit to another branch in the Current Branch menu](/assets/images/help/desktop/cherry-picking.png) +4. 将要优选的提交拖到 {% octicon "git-branch" aria-label="The branch icon" %} **当前分支**菜单，并放到您要复制该提交到其中的分支上。 ![将提交拖动到 Current Branch（当前分支）菜单中的另一个分支](/assets/images/help/desktop/cherry-picking.png) ### 延伸阅读 -- [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation +- Git 文档中的 [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) 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 6c59f3fb9d..f4f6b1a09e 100644 --- a/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/authorizing-oauth-apps.md @@ -86,18 +86,18 @@ topics: 默认情况下，响应采用以下形式： - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer 您也可以根据“接受”标头接收不同格式的内容： Accept: application/json - {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} + {"access_token":"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} Accept: application/xml bearer repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} #### 3. 使用访问令牌访问 API @@ -207,7 +207,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", "scope": "user" } @@ -304,3 +304,7 @@ http://localhost:1234/path {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} * "[设备流程错误](#errors-for-the-device-flow)" {% endif %} + +### 延伸阅读 + +- “[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github)” diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md index f64302245a..25ed2c1db4 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -54,16 +54,18 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app ##### GitHub 应用程序清单参数 - | 名称 | 类型 | 描述 | - | --------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------- | - | `name` | `字符串` | GitHub 应用程序的名称。 | - | `url` | `字符串` | **必填。**GitHub 应用程序的主页。 | - | `hook_attributes` | `对象` | GitHub 应用程序 web 挂钩的配置 | - | `redirect_url` | `字符串` | 用户安装 GitHub 应用程序后要重定向到的完整 URL。 | - | `说明` | `字符串` | GitHub 应用程序的说明。 | - | `public` | `布尔值` | 当 GitHub 应用程序可供公众使用时，设置为 `true` ；当它仅供应用程序的所有者访问时，设置为 `false`。 | - | `default_events` | `数组` | GitHub 应用程序订阅的[事件](/webhooks/event-payloads)列表。 | - | `default_permissions` | `对象` | GitHub 应用程序所需的[权限](/rest/reference/permissions-required-for-github-apps)集。 对象的格式使用键的权限名称（例如 `issues`）和值的访问类型（例如 `write`）。 | + | 名称 | 类型 | 描述 | + | --------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `name` | `字符串` | GitHub 应用程序的名称。 | + | `url` | `字符串` | **必填。**GitHub 应用程序的主页。 | + | `hook_attributes` | `对象` | GitHub 应用程序 web 挂钩的配置 | + | `redirect_url` | `字符串` | 在用户从清单创建 GitHub 应用程序后重定向到的完整 URL。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `字符串数组` | 在用户授权安装后重定向到的完整 URL。 您可以提供最多 10 个回叫 URL。{% else %} + | `callback_url` | `字符串` | 在用户授权安装后重定向到的完整 URL。{% endif %} + | `说明` | `字符串` | GitHub 应用程序的说明。 | + | `public` | `布尔值` | 当 GitHub 应用程序可供公众使用时，设置为 `true` ；当它仅供应用程序的所有者访问时，设置为 `false`。 | + | `default_events` | `数组` | GitHub 应用程序订阅的[事件](/webhooks/event-payloads)列表。 | + | `default_permissions` | `对象` | GitHub 应用程序所需的[权限](/rest/reference/permissions-required-for-github-apps)集。 对象的格式使用键的权限名称（例如 `issues`）和值的访问类型（例如 `write`）。 | `hook_attributes` 对象含有以下键： @@ -96,7 +98,10 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -111,10 +116,11 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app }) ``` + 此示例使用网页上的表单，其中包含一个按钮，该按钮可触发组织帐户的 `POST` 请求： 将 `ORGANIZATION` 替换为要在其中创建应用程序的组织帐户的名称。 ```html -
+ Create a GitHub App Manifest:
@@ -127,7 +133,10 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app "hook_attributes": { "url": "https://example.com/github/events", }, - "redirect_url": "https://example.com/callback", + "redirect_url": "https://example.com/redirect", + {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %}"callback_urls": [ + "https://example.com/callback" + ],{% else %}"callback_url": "https://example.com/callback",{% endif %} "public": true, "default_permissions": { "issues": "write", @@ -147,11 +156,11 @@ GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-app 当用户单击**创建 GitHub 应用程序**时，GitHub 将使用代码参数中的临时 `code` 重定向回 `redirect_url` 。 例如： - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 如果您提供了 `state` 参数，您还会在 `redirect_url` 中看到该参数。 例如： - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 + https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 #### 3. 交换临时代码以检索应用程序配置 diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md index caa417b0b6..4a3db577d5 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -22,9 +22,15 @@ topics: 以下 URL 使用预配置的说明和回调 URL 创建名为 `octocat-github-app` 的新公共应用程序。 此 URL 还选择了 `checks` 的读取和写入权限，订阅了 `check_run` 和 `check_suite` web 挂钩事件，并选择了在安装过程中请求用户授权 (OAuth) 的选项： - ``` - {% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite - ``` +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} +``` +{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite +``` +{% else %} +``` +{% 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 +``` +{% endif %} 下面几节列出了可用查询参数、权限和事件的完整列表。 @@ -34,8 +40,9 @@ topics: | -------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `name` | `字符串` | {% data variables.product.prodname_github_app %} 的名称。 给应用程序一个清晰简洁的名称。 应用程序不能与现有 GitHub 用户同名，除非它是您自己的用户或组织的名称。 当您的集成执行操作时，应用程序名称的缓存版本将显示在用户界面上。 | | `说明` | `字符串` | {% data variables.product.prodname_github_app %} 的说明。 | - | `url` | `字符串` | 您的 {% data variables.product.prodname_github_app %} 网站主页的完整 URL。 | - | `callback_url` | `字符串` | 在用户授权安装后重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。 | + | `url` | `字符串` | {% data variables.product.prodname_github_app %} 网站主页的完整 URL。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.0" %} + | `callback_urls` | `字符串数组` | 在用户授权安装后重定向到的完整 URL。 您可以提供最多 10 个回叫 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用这些 URL。 例如 `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`。{% else %} + | `callback_url` | `字符串` | 在用户授权安装后重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。{% endif %} | `request_oauth_on_install` | `布尔值` | 如果应用程序授权用户使用 OAuth 流程，您可以将此选项设置为 `true`，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则 `setup_url` 将不可用，用户在安装应用程序后将被重定向到您的 `callback_url`。 | | `setup_url` | `字符串` | 在用户安装 {% data variables.product.prodname_github_app %} 后重定向到的完整 URL（如果应用程序在安装之后需要额外设置）。 | | `setup_on_update` | `布尔值` | 设置为 `true` 可在更新安装后（例如在添加或删除仓库之后）将用户重定向到设置 URL。 | 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 c0653f3dc1..9a82462da4 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 @@ -844,7 +844,7 @@ end **答：**如果您看到以下错误，则说明您没有在 `initiate_check_run` 和/或 `take_requested_action` 方法中删除仓库的检出： ```shell - 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:v1.9b2080277016f797074c4debd350745f4257f8dd@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: + 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: ``` 将您的代码与 `server.rb` 文件进行比较，以确保您的 `initiate_check_run` 和 `take_requested_action` 方法中具有相同的代码。 diff --git a/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md b/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md index a4230a29ec..aaa44b403d 100644 --- a/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/identifying-and-authorizing-users-for-github-apps.md @@ -94,9 +94,9 @@ topics: ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": 28800, - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692{% endif %}", "refresh_token_expires_in": 15811200, "scope": "", "token_type": "bearer" @@ -106,7 +106,7 @@ topics: 默认情况下，响应采用以下形式： - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer + access_token={% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer {% endif %} @@ -934,3 +934,11 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre * [获取工作流程](/rest/reference/actions#get-a-workflow) * [获取工作流程使用情况](/rest/reference/actions#get-workflow-usage) {% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### 延伸阅读 + +- “[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)” + +{% endif %} diff --git a/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md index 2c4bc8b34c..4616ab58fb 100644 --- a/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,9 +42,9 @@ topics: ```json { - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", + "access_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghu_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", + "refresh_token": "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498{% else %}r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c{% endif %}", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" @@ -73,3 +73,11 @@ topics: 仅当应用程序所有者为其应用程序启用了过期用户令牌时，使用用户到服务器授权令牌的现有 {% data variables.product.prodname_github_app %} 才会受到这个新流程的影响。 要为现有 {% data variables.product.prodname_github_app %} 启用过期用户令牌，需要通过 OAuth 流程发送用户以重新颁发将在 8 小时后过期的新用户令牌，并使用刷新令牌发出请求以获取新的访问令牌和刷新令牌。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### 延伸阅读 + +- “[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)” + +{% endif %} diff --git a/translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md b/translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md index 9df871d61b..35a5ecebbe 100644 --- a/translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md +++ b/translations/zh-CN/content/developers/github-marketplace/about-marketplace-badges.md @@ -13,7 +13,7 @@ versions: - 已验证其域名的所有权，且其个人资料上有经过验证的徽章 - 已确认其电子邮件地址可用于 {% data variables.product.prodname_dotcom %} 支持人员联系该组织 -- 对其组织要求双重身份验证 更多信息请参阅“[您的组织中需要双重身份验证](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)”。 +- 对其组织要求双重身份验证 更多信息请参阅“[您的组织中需要双重身份验证](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)”。 ![GitHub 应用程序的 Marketplace 徽章](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png) diff --git a/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md b/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md index 8f155af674..982ac5a4d7 100644 --- a/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md +++ b/translations/zh-CN/content/developers/github-marketplace/applying-for-publisher-verification-for-your-organization.md @@ -22,8 +22,8 @@ topics: 1. 在“Developer settings（开发者设置）”下，单击 **Publisher Verification（发布者验证）**。 ![组织设置侧边栏中的发布者验证选项](/assets/images/marketplace/publisher-verification-settings-option.png) 1. 在“Publisher Verification（发布者验证）”下，填写检查列表中的信息： - 确保您的基本个人资料信息正确无误。 另外，确保您添加了接收 {% data variables.product.company_short %} 的更新和支持信息的最合适电子邮件地址。 - - 确保为您的组织启用双重身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)”。 - - 提交已验证的域名并确保您组织的个人资料页面上显示“已验证”徽章。 相关信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 + - 确保为您的组织启用双重身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)”。 + - 提交已验证的域名并确保您组织的个人资料页面上显示“已验证”徽章。 相关信息请参阅“[验证组织的域](/organizations/managing-organization-settings/verifying-your-organizations-domain)”。 ![发布者验证检查列表](/assets/images/marketplace/publisher-verification-checklist.png) diff --git a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md index d245d5f007..ad7b1f0dc0 100644 --- a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md +++ b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md @@ -112,6 +112,36 @@ Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` +### 服务器到服务器令牌 + +如果您的服务器需要访问一个或多个组织的仓库，您可以使用 GitHub 应用程序来定义您需要的访问权限，然后从该 GitHub 应用程序生成 _tightly-scoped_、_server-to-server_ 令牌。 服务器到服务器令牌可以扩展到单个或多个仓库，并且可以拥有细致的权限。 例如，您可以生成对仓库内容具有只读权限的令牌。 + +由于 GitHub 应用程序是 {% data variables.product.product_name %} 上的一类角色，因此服务器到服务器令牌不限于任何 GitHub 用户，这使它们堪比“服务令牌”。 此外，服务器到服务器令牌有专门的速率限制，与它们所依据的组织规模相当。 更多信息请参阅“[GitHub 应用程序的速率限制](/developers/apps/rate-limits-for-github-apps)”。 + +##### 优点 + +- 具有明确定义的权限集和到期时间的严格范围令牌（如果使用 API 手动撤销，则为 1 小时或更短时间）。 +- 随组织而增长的专用速率限制。 +- 与 GitHub 用户身份脱钩，因此他们不消耗任何许可席位。 +- 从未授予密码，因此无法直接登录。 + +##### 缺点 + +- 创建 GitHub 应用程序需要其他设置。 +- 服务器到服务器令牌 1 小时后过期，因此需要重新生成，通常是按需使用代码。 + +##### 设置 + +1. 确定您的 GitHub 应用程序是公开的还是私有的。 如果您的 GitHub 应用程序将仅在您组织内的仓库上操作，您可能希望它是私有的。 +1. 确定 GitHub 应用程序所需的权限，例如对仓库内容的只读访问权限。 +1. 通过组织的设置页面创建您的 GitHub 应用程序。 更多信息请参阅[创建 GitHub 应用程序](/developers/apps/creating-a-github-app)。 +1. 记下您的 GitHub 应用程序 `id`。 +1. 生成并下载 GitHub 应用程序的私钥，并妥善保管。 更多信息请参阅[生成私钥](/developers/apps/authenticating-with-github-apps#generating-a-private-key)。 +1. 将 GitHub 应用程序安装到需要执行它的仓库中，您可以在组织中的所有仓库上选择性地安装 GitHub 应用程序。 +1. 识别代表 GitHub 应用程序与它可以访问的组织仓库之间连接的 `installation_id`。 每个 GitHub 应用程序和组织对最多只有一个 `installation_id`。 您可以通过[为经过验证的应用程序获取组织安装](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app)来识别此 `installation_id`。 这需要使用 JWT 作为 GitHub 应用程序进行身份验证，更多信息请参阅[作为 GitHub 应用程序进行身份验证](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)。 +1. 使用相应的 REST API 端点 [为应用创建安装访问令牌](/rest/reference/apps#create-an-installation-access-token-for-an-app)生成服务器到服务器令牌。 这需要使用 JWT 作为 GitHub 应用程序进行身份验证，更多信息请参阅[作为 GitHub 应用程序进行身份验证](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)以及[作为安装进行身份验证](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)。 +1. 使用此服务器到服务器令牌，通过 REST 或 GraphQL API 或者通过 Git 客户端与您的仓库进行交互。 + ### 机器用户 如果您的服务器需要访问多个仓库，您可以创建一个新的 {% data variables.product.product_name %} 帐户并附加一个专用于自动化的 SSH 密钥。 由于此 {% data variables.product.product_name %} 帐户不会被人类使用，因此称为_机器用户_。 您可以将机器用户添加为个人仓库上的[协作者][collaborator]（授予读取和写入权限）、添加为组织仓库上的[外部协作者][outside-collaborator]（授予读取、写入或管理员权限）或添加到对需要自动化的仓库具有访问权限的[团队][team]（授予团队权限）。 diff --git a/translations/zh-CN/content/developers/overview/secret-scanning.md b/translations/zh-CN/content/developers/overview/secret-scanning.md index 827c3131cc..a76fd9527a 100644 --- a/translations/zh-CN/content/developers/overview/secret-scanning.md +++ b/translations/zh-CN/content/developers/overview/secret-scanning.md @@ -17,12 +17,6 @@ topics: 在配置为 {% data variables.product.prodname_secret_scanning %} 的私有仓库中找到密码格式的匹配项时，仓库管理员将收到警报，并且可以查看和管理 {% data variables.product.prodname_dotcom %} 上的 {% data variables.product.prodname_secret_scanning %} 结果。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。 -{% note %} - -**注：**私有仓库的 {% data variables.product.prodname_secret_scanning_caps %} 目前处于测试阶段。 - -{% endnote %} - 本文介绍作为服务提供者如何与 {% data variables.product.prodname_dotcom %} 合作并加入 {% data variables.product.prodname_secret_scanning %} 计划。 ### {% data variables.product.prodname_secret_scanning %} 流程 diff --git a/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md b/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md index f7324f0543..ec6c5da7c5 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/github-event-types.md @@ -183,6 +183,20 @@ Link: ; rel="next", {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} +### PullRequestReviewEvent + +{% data reusables.webhooks.pull_request_review_short_desc %} + +{% data reusables.webhooks.events_api_payload %} + +#### 事件 `payload` 对象 + +| 键 | 类型 | 描述 | +| -------------- | ----- | ----------------------- | +| `action` | `字符串` | 执行的操作内容. 可以是 `created`。 | +| `pull_request` | `对象` | 与审查相关的拉取请求。 | +| `审查` | `对象` | 受影响的审查。 | + ### PullRequestReviewCommentEvent {% data reusables.webhooks.pull_request_review_comment_short_desc %} @@ -200,6 +214,8 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} +#### 事件 `payload` 对象 + | 键 | 类型 | 描述 | | -------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------- | | `push_id` | `整数` | 推送的唯一标识符。 | diff --git a/translations/zh-CN/content/developers/webhooks-and-events/securing-your-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/securing-your-webhooks.md index 01f8b0a2ed..ff09e67383 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/securing-your-webhooks.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/securing-your-webhooks.md @@ -93,4 +93,4 @@ end{% endif %} * **不建议**使用普通的 `==` 运算符。 像 [`secure_compare`][secure_compare] 这样的方法执行“恒定时间”字符串比较，这有助于减轻针对常规相等运算符的某些定时攻击。 -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md index 5b29050e5b..1e6e7b525e 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -343,18 +343,18 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.discussions-webhooks-beta %} -Activity related to a discussion. For more information, see the "[Using the GraphQL API for discussions](/graphql/guides/using-the-graphql-api-for-discussions)." +与讨论有关的活动。 更多信息请参阅“[使用 GraphQL API 进行讨论](/graphql/guides/using-the-graphql-api-for-discussions)”。 #### 可用性 - 仓库 web 挂钩 - 组织 web 挂钩 -- {% data variables.product.prodname_github_app %}s with the `discussions` permission +- 具有 `discussions` 权限的 {% data variables.product.prodname_github_app %} #### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, or `unanswered`. | +| 键 | 类型 | 描述 | +| -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited`、`deleted`、`pinned`、`unpinned`、`locked`、`unlocked`、`transferred`、`category_changed`、`answered` 或 `unanswered`。 | {% data reusables.webhooks.discussion_desc %} {% data reusables.webhooks.repo_desc_graphql %} {% data reusables.webhooks.org_desc_graphql %} @@ -368,20 +368,20 @@ Activity related to a discussion. For more information, see the "[Using the Grap {% data reusables.webhooks.discussions-webhooks-beta %} -Activity related to a comment in a discussion. For more information, see "[Using the GraphQL API for discussions](/graphql/guides/using-the-graphql-api-for-discussions)." +与讨论中的评论相关的活动。 更多信息请参阅“[使用 GraphQL API 进行讨论](/graphql/guides/using-the-graphql-api-for-discussions)”。 #### 可用性 - 仓库 web 挂钩 - 组织 web 挂钩 -- {% data variables.product.prodname_github_app %}s with the `discussions` permission +- 具有 `discussions` 权限的 {% data variables.product.prodname_github_app %} #### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| -------- | ----- | ------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited` 或 `deleted`。 | -| `注释，评论` | `对象` | The [`discussion comment`](/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) resource. | +| 键 | 类型 | 描述 | +| -------- | ----- | --------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited` 或 `deleted`。 | +| `注释，评论` | `对象` | [`discussion comment`](/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) 资源。 | {% data reusables.webhooks.discussion_desc %} {% data reusables.webhooks.repo_desc_graphql %} {% data reusables.webhooks.org_desc_graphql %} diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 3f9c7b1027..a60609c63f 100644 --- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -19,7 +19,7 @@ versions: 您不需要像关闭议题或拉取请求那样结束讨论。 -如果仓库管理员或项目维护者支持存储库的讨论，则访问仓库的任何人都可以创建和参与仓库的讨论。 仓库管理员和项目维护者可以管理仓库中的讨论和讨论类别，并固定讨论以提高讨论的可见性。 主持人和协作者可以将评论标记为答案、锁定讨论并将议题转换为讨论。 更多信息请参阅“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)”。 +如果仓库管理员或项目维护者支持存储库的讨论，则访问仓库的任何人都可以创建和参与仓库的讨论。 仓库管理员和项目维护者可以管理仓库中的讨论和讨论类别，并固定讨论以提高讨论的可见性。 主持人和协作者可以将评论标记为答案、锁定讨论并将议题转换为讨论。 更多信息请参阅“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。 有关管理仓库讨论的更多信息，请参阅“[管理仓库中的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)”。 diff --git a/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md index 1c110ce826..f2be7d0ff0 100644 --- a/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -29,7 +29,7 @@ versions: 议题适用于讨论项目的具体细节，如漏洞修复和计划的改进。 更多信息请参阅“[关于议题](/articles/about-issues)”。 拉取请求允许您直接评论提议的更改。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests)”和“[评论拉取请求](/articles/commenting-on-a-pull-request)”。 -{% data reusables.organizations.team-discussions-purpose %} 更多信息请参阅“[关于团队讨论](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)”。 +{% data reusables.organizations.team-discussions-purpose %} 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 ### 遵守参与指南 diff --git a/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index d40f6f7c6b..2949244f5e 100644 --- a/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -21,7 +21,7 @@ versions: 对仓库具有分类权限的人可以通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持项目的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。 -有关仓库权限级别和 {% data variables.product.prodname_discussions %} 的更多信息，请参阅“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)”。 +有关仓库权限级别和 {% data variables.product.prodname_discussions %} 的更多信息，请参阅“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。 ### 第 3 步：更改顶级贡献者的权限级别 diff --git a/translations/zh-CN/content/discussions/index.md b/translations/zh-CN/content/discussions/index.md index e99b513074..e4aaa6321c 100644 --- a/translations/zh-CN/content/discussions/index.md +++ b/translations/zh-CN/content/discussions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /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 changelog: - label: 'discussions' + label: '讨论' product_video: https://www.youtube-nocookie.com/embed/IpBw2SJkFyk layout: product-landing versions: diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index 815d509ad5..1d479c28ba 100644 --- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -12,7 +12,7 @@ versions: {% data reusables.discussions.about-discussions %} 有关讨论的更多信息，请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。 -组织所有者可以选择为组织拥有的仓库创建讨论所需的权限。 更多信息请参阅“[管理组织中仓库的讨论创建](/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization)”。 +组织所有者可以选择为组织拥有的仓库创建讨论所需的权限。 更多信息请参阅“[管理组织中仓库的讨论创建](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)”。 作为讨论维护者，您可以创建社区资源，以鼓励与总体项目目标一致的讨论，并为协作者维护一个友好、开放的论坛。 为协作者制定行为守则或参与指南将有助于促进协作和富有成效的论坛。 有关创建社区资源的更多信息，请参阅“[为项目中添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和“[设置仓库参与者指南](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)”。 diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md index 49c74187ef..3d3c715397 100644 --- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors.md @@ -16,3 +16,7 @@ versions: **注：**作为讲师，无法为学生创建 {% data variables.product.prodname_dotcom %} 帐户。 学生必须创建自己的 {% data variables.product.prodname_dotcom %} 帐户。 {% endnote %} + +教师可以使用 {% data variables.product.prodname_education %} 管理软件开发课程。 {% data variables.product.prodname_classroom %} 可用于发布代码、提供反馈，以及使用 {% data variables.product.product_name %} 管理课程。 更多信息请参阅“[使用 {% data variables.product.prodname_classroom %} 管理课程](/education/manage-coursework-with-github-classroom)”。 + +如果您是学生或教师并且您的学校未作为 {% data variables.product.prodname_campus_program %} 学校与 {% data variables.product.prodname_dotcom %} 合作，您也可以个人申请使用 {% data variables.product.prodname_dotcom %} 的折扣。 更多信息请参阅“[使用 {% data variables.product.prodname_dotcom %} 做家庭作业](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)”或“[在课堂上和研究中使用 {% data variables.product.prodname_dotcom %}](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)”。 diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md index 20d9a1647b..52673fd56b 100644 --- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts.md @@ -9,4 +9,6 @@ versions: free-pro-team: '*' --- -作为 {% data variables.product.prodname_dotcom %} Campus Expert，学习公共演讲技能、技术写作、社区领导和软件开发技能。 更多信息请参阅 "[Campus Experts](https://education.github.com/students/experts)"。 +作为 {% data variables.product.prodname_dotcom %} Campus Expert，学习公共演讲技能、技术写作、社区领导和软件开发技能。 + +要详细了解学生领导者和教师的培训计划，请参阅 "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)" 和 "[Campus Advisors](https://education.github.com/teachers/advisors)"。 diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md new file mode 100644 index 0000000000..ac92bbcbaf --- /dev/null +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program.md @@ -0,0 +1,24 @@ +--- +title: 关于 GitHub 校园计划 +intro: '{% data variables.product.prodname_campus_program %} 免费向希望为其社区充分利用 {% data variables.product.prodname_dotcom %} 的学校提供 {% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_server %}。' +redirect_from: + - /education/teach-and-learn-with-github-education/about-github-education + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education + - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_campus_program %} 是授予学位、文凭或证书、以教学为重点的机构的高级 {% data variables.product.prodname_dotcom %} 访问包。 {% data variables.product.prodname_campus_program %} 包括： + +- 所有的技术和学术部门可以免费访问 {% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_server %} +- 通过 Campus Advisor 计划为教师提供 Git 和 {% data variables.product.prodname_dotcom %} 培训 +- 独家访问来自 {% data variables.product.prodname_dotcom %} 合作伙伴的 GitHub 教育版特定内容和免费开发者工具 +- 自动访问高级 {% data variables.product.prodname_education %} 功能，如 {% data variables.product.prodname_student_pack %} + +只要同意[计划条款](https://education.github.com/schools/terms)，欢迎任何学校加入。 + +更多信息请参阅[官方 {% data variables.product.prodname_campus_program %}](https://education.github.com/schools) 网页。 + +如果您是学生或教师并且您的学校未作为 {% data variables.product.prodname_campus_program %} 学校与 {% data variables.product.prodname_dotcom %} 合作，您也可以个人申请使用 {% data variables.product.prodname_dotcom %} 的折扣。 更多信息请参阅“[使用 {% data variables.product.prodname_dotcom %} 做家庭作业](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)”或“[在课堂上和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)”。 diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md index 563fec4118..15e9bcc38a 100644 --- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md @@ -13,7 +13,7 @@ versions: ### 目录 {% topic_link_in_list /use-github-at-your-educational-institution %} - {% link_in_list /about-github-education %} + {% link_in_list /about-github-campus-program %} {% link_in_list /about-campus-experts %} {% link_in_list /about-campus-advisors %} {% topic_link_in_list /use-github-for-your-schoolwork %} diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index 7d351287f0..2eaeaec67f 100644 --- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -59,11 +59,11 @@ versions: ### 学生身份不合格 以下情况时，您没有资格获得 {% data variables.product.prodname_student_pack %}： -- 您已注册参加不属于 [{% data variables.product.prodname_dotcom %} 校园计划](https://education.github.com/schools)的非正式学习计划，但未注册参加授予学位或文凭的学习课程。 +- 您已注册参加不属于 [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) 的非正式学习计划，但未注册参加授予学位或文凭的学习课程。 - 您正在攻读将在当前学术会议上终止的学位。 - 您未满 13 岁。 -您的讲师仍可申请 {% data variables.product.prodname_education %} 折扣供课堂使用。 如果您是编程学校或训练营的学生，并且您的学校参加 [{% data variables.product.prodname_dotcom %} 校园计划](https://education.github.com/schools)，您将有资格获得 {% data variables.product.prodname_student_pack %}。 +您的讲师仍可申请 {% data variables.product.prodname_education %} 折扣供课堂使用。 如果您是编程学校或训练营的学生，并且您的学校参加 [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools)，您将有资格获得 {% data variables.product.prodname_student_pack %}。 ### 延伸阅读 diff --git a/translations/zh-CN/content/education/index.md b/translations/zh-CN/content/education/index.md index ed76ef7a74..9de888abf7 100644 --- a/translations/zh-CN/content/education/index.md +++ b/translations/zh-CN/content/education/index.md @@ -20,7 +20,7 @@ featuredLinks: - /github/getting-started-with-github/github-cli - /education/manage-coursework-with-github-classroom/teach-with-github-classroom changelog: - label: 'education' + label: '教育版' layout: product-landing versions: free-pro-team: '*' diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 57c87a786c..8b8b21e026 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -17,7 +17,7 @@ redirect_from: {% data reusables.classroom.about-assignments %} -您可以决定一个任务可以拥有多少个团队，以及每个团队可以拥有多少成员。 学生为作业创建的每个团队都是 {% data variables.product.product_name %} 上组织内的团队。 团队的可见性是秘密。 您在 {% data variables.product.product_name %} 上创建的团队不会出现在 {% data variables.product.prodname_classroom %} 中。 更多信息请参阅“[关于团队](/github/setting-up-and-managing-organizations-and-teams/about-teams)”。 +您可以决定一个任务可以拥有多少个团队，以及每个团队可以拥有多少成员。 学生为作业创建的每个团队都是 {% data variables.product.product_name %} 上组织内的团队。 团队的可见性是秘密。 您在 {% data variables.product.product_name %} 上创建的团队不会出现在 {% data variables.product.prodname_classroom %} 中。 For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." 有关创建小组作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本知识](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。 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 76cfa929ce..2c9be1cee9 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 @@ -20,7 +20,7 @@ redirect_from: 创建教室后，{% data variables.product.prodname_classroom %} 将提示您邀请助教 (TA) 和管理员到教室。 每个教室可以有一个或多个管理员。 管理员可以是教师、TA 或您希望其控制您在 {% data variables.product.prodname_classroom %} 上的教室的任何其他课程管理员。 -邀请 TA 和管理员进入您的教室，操作方法是以组织所有者身份邀请 {% data variables.product.product_name %} 上的用户帐户到您的组织，并共享您教室的 URL。 组织所有者可以管理组织的任何教室。 更多信息请参阅“[组织的权限级别](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)”和“[邀请用户加入您的组织](/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization)”。 +邀请 TA 和管理员进入您的教室，操作方法是以组织所有者身份邀请 {% data variables.product.product_name %} 上的用户帐户到您的组织，并共享您教室的 URL。 组织所有者可以管理组织的任何教室。 更多信息请参阅“[组织的权限级别](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)”和“[邀请用户加入您的组织](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)”。 使用完教室后，可以存档教室，以后可以参考该教室、名册和作业，或者如果您不再需要该教室，也可以将其删除。 @@ -34,7 +34,7 @@ redirect_from: ### 基本要求 -您必须在 {% data variables.product.product_name %} 上拥有组织帐户才能管理 {% data variables.product.prodname_classroom %} 上的教室。 更多信息请参阅“[{% data variables.product.company_short %} 帐户的类型](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)”和“[从头开始创建新组织](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)”。 +您必须在 {% data variables.product.product_name %} 上拥有组织帐户才能管理 {% data variables.product.prodname_classroom %} 上的教室。 更多信息请参阅“[{% data variables.product.company_short %} 帐户的类型](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)”和“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 您必须为组织授权 {% data variables.product.prodname_classroom %} 的 OAuth 应用程序才可管理组织帐户的教室。 更多信息请参阅“[授权 OAuth 应用程序](/github/authenticating-to-github/authorizing-oauth-apps)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md index 9aeed0e996..a80929404c 100644 --- a/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository.md @@ -26,7 +26,7 @@ topics: {% note %} -**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 更多信息请参阅“[禁用或限制组织的 {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)”或{% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account)”。{% else if currentVersion ver_gt "enterprise-server@2.21"%}"[实施企业的 {% data variables.product.prodname_actions %} 策略](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)“。{% endif %} +**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} {% endnote %} @@ -47,7 +47,7 @@ topics: {% note %} -**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 更多信息请参阅“[禁用或限制组织的 {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)”或{% if currentVersion == "free-pro-team@latest" %}“[在企业帐户中实施 {% data variables.product.prodname_actions %} 策略](/github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account)”。{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[实施企业的 {% data variables.product.prodname_actions %} 策略](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)“。 +**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." {% endif %} 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 eeaa3c6efa..ce4395ffeb 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 @@ -11,7 +11,11 @@ topics: - 仓库 --- -如果您允许自动合并仓库中的拉取请求，则用户可以配置仓库中的单个拉取请求在满足所有合并要求时自动合并。 更多信息请参阅“[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)”。 +### 关于自动合并 + +如果您允许自动合并仓库中的拉取请求，则具有写入权限的用户可以配置仓库中的单个拉取请求在满足所有合并要求时自动合并。 {% if currentversion == "free-proteam@latest" or currentversion == "github-ae@next" or currentversion ver_gt "enterprise-server@3. %}如果没有写入权限的人将更改推送到已启用自动合并的拉请求，将对该拉取请求禁用自动合并。 {% endif %}更多信息请参阅“[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)”。 + +### 管理自动合并 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 a21bcaf87e..f13724a067 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 @@ -47,6 +47,9 @@ topics: 6. 键入发行版的标题和说明。 ![发行版说明](/assets/images/help/releases/releases_description.png) 7. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif) 8. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png) +{%- if currentVersion == "free-pro-team@latest" %} +1. （可选）选择 **Create a discussion for this release（为此版本创建讨论）**，然后选择 **Category（类别）**下拉菜单，然后点击类别进行版本讨论。 ![用于创建发行版讨论和下拉菜单以选择类别的复选框](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} 9. 如果您准备推广您的发行版，请单击 **Publish release（发布版本）**。 要在以后处理该发行版，请单击 **Save draft（保存草稿）**。 ![发布版本和草拟发行版按钮](/assets/images/help/releases/release_buttons.png) 您也可以从命令行或脚本自动创建发行版。 更多信息请参阅“[发行版](/rest/reference/repos/#create-a-release)”。 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 0c71f0592c..76230b8b82 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 @@ -106,4 +106,4 @@ topics: ### 延伸阅读 - “[关于保护仓库](/github/administering-a-repository/about-securing-your-repository)” -- “[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)” +- “[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)” diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md index f10c324b22..2b12340f30 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository.md @@ -16,7 +16,7 @@ topics: 此概览可帮助您审核对仓库、内部或外部承包商或员工的访问权限，并有效响应安全事件。 -有关仓库权限级别的更多信息，请参阅“[用户帐户仓库的权限级别](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)”和“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)”。 +有关仓库权限级别的更多信息，请参阅“[用户帐户仓库的权限级别](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)”和“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。 ![访问权限管理概览](/assets/images/help/repository/manage-access-overview.png) @@ -53,4 +53,4 @@ topics: ### 延伸阅读 - “[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)” -- “[设置组织的基本权限](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)” +- “[设置组织的基本权限](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)” diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md index 526f8f3418..79b2c38643 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-the-forking-policy-for-your-repository.md @@ -13,7 +13,7 @@ topics: - 仓库 --- -组织所有者必须在组织级别上允许复刻私有{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 和内部{% endif %} 仓库，然后才能允许或禁止对特定仓库进行复刻。 更多信息请参阅“[管理组织的复刻政策](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)”。 +组织所有者必须在组织级别上允许复刻私有{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 和内部{% endif %} 仓库，然后才能允许或禁止对特定仓库进行复刻。 更多信息请参阅“[管理组织的复刻政策](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)”。 {% data reusables.organizations.internal-repos-enterprise %} 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 index 324e8fe6b8..cdd94b2fc8 100644 --- 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 @@ -4,7 +4,7 @@ intro: 您可以更改仓库中分支的名称。 permissions: 拥有仓库写入权限的人可重命名仓库中的分支。 具有管理员权限的人可以重命名默认分支。 versions: free-pro-team: '*' - enterprise-server: '>=3.1' + enterprise-server: '>=3.2' topics: - 仓库 --- @@ -13,7 +13,9 @@ topics: 您可以重命名 {% 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 variables.product.product_location %}上重命名分支时，任何包含旧分支名称的网址都会自动重定向到重命名分支的等效 URL。 还更新了分支保护政策以及打开的拉取请求（包括复刻的拉取请求）的基础分支和草稿版本。 重命名完成后， {% data variables.product.prodname_dotcom %} 在仓库主页上提供说明，指示贡献者更新他们的本地 Git 环境。 + +虽然文件 URL 会自动重定向，但原始文件 URL 未被重定向。 此外，如果用户对前一个分支名称执行 `git pull`，则 {% data variables.product.prodname_dotcom %} 不会执行任何重定向。 ### 重命名分支 diff --git a/translations/zh-CN/content/github/administering-a-repository/renaming-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/renaming-a-repository.md index 42b4d5edb4..6fddf333e0 100644 --- a/translations/zh-CN/content/github/administering-a-repository/renaming-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/renaming-a-repository.md @@ -18,7 +18,7 @@ topics: * 星标 * 关注者 -有关项目网站的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +有关项目网站的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 除了重定向 Web 流量以外，所有目标为之前位置的 `git clone`、`git fetch` 或 `git push` 操作都将继续正常工作，如同在新位置进行一样。 不过，为了减少混淆，我们强烈建议将任何现有的本地克隆更新为指向新仓库 URL。 您可以通过在命令行中使用 `git remote` 来执行此操作： @@ -30,7 +30,7 @@ $ git remote set-url origin new_url {% if currentVersion == "free-pro-team@latest" %} -如果计划重命名具有 {% data variables.product.prodname_pages %} 网站的仓库，建议对网站使用自定义域。 这可确保重命名仓库不会影响网站的 URL。 更多信息请参阅“[关于自定义域和 {% data variables.product.prodname_pages %} 网站](/github/working-with-github-pages/about-custom-domains-and-github-pages)”。 +如果计划重命名具有 {% data variables.product.prodname_pages %} 网站的仓库，建议对网站使用自定义域。 这可确保重命名仓库不会影响网站的 URL。 更多信息请参阅“[关于自定义域和 {% data variables.product.prodname_pages %} 网站](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)”。 {% endif %} 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 feb0b3f80a..07e1095a4a 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 @@ -16,7 +16,7 @@ topics: ### 关于仓库可见性更改 -组织所有者可以限制只有组织所有者才能更改仓库可见性。 更多信息请参阅“[限制组织的仓库可见性更改](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)”。 +组织所有者可以限制只有组织所有者才能更改仓库可见性。 For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." 我们建议在您更改仓库可见性之前审查以下注意事项。 diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md index aa8c16b1f8..49022cf9ec 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-to-github.md @@ -55,3 +55,19 @@ topics: * 您可以通过 SSH 处理 {% data variables.product.product_name %} 上的所有仓库，尽管防火墙和代理可能拒绝允许 SSH 连接。 使用 SSH 需要在本地计算机上生成 SSH 公钥/私密对，并将公钥添加到 {% data variables.product.product_name %} 帐户。 除非您已[存储密钥](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)，否则每次使用 Git 向 {% data variables.product.product_name %} 验证时，系统都会提示您输入 SSH 密钥密码短语。 更多信息请参阅“[生成新的 SSH 密钥并添加到 ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 {% if currentVersion == "free-pro-team@latest" %}要使用个人访问令牌或 SSH 密钥访问由使用 SAML 单点登录的组织所拥有的资源，还必须授权个人令牌或 SSH 密钥。 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-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" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + +### {% data variables.product.company_short %} 的令牌格式 + +以前缀开头的 {% data variables.product.company_short %} 议题令牌表示令牌的类型。 + +| 令牌类型 | 前缀 | 更多信息 | +|:------------------------------------------------------------- |:------ |:------------------------------------------------------------------------------------------------------------------------------------------------ | +| 个人访问令牌 | `ghp_` | “[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 | +| OAuth 访问令牌 | `gho_` | "[授权 {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| {% data variables.product.prodname_github_app %} 的用户到服务器令牌 | `ghu_` | "[识别和授权 {% data variables.product.prodname_github_apps %} 的用户](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| {% data variables.product.prodname_github_app %} 的服务器到服务器令牌 | `ghs_` | "[向 {% data variables.product.prodname_github_apps %} 验证](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| {% data variables.product.prodname_github_app %} 的刷新令牌 | `ghr_` | "[刷新用户到服务器访问令牌](/developers/apps/refreshing-user-to-server-access-tokens)" | + +{% endif %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md index fd16a10fde..5baa32f96d 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-authentication-with-saml-single-sign-on.md @@ -1,47 +1,55 @@ --- -title: About authentication with SAML single sign-on -intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}' +title: 关于使用 SAML 单点登录进行身份验证 +intro: '您可以通过使用 SAML 单点登录 (SSO) {% endif %}通过身份提供程序 (IdP)验证 {% if currentVersion == "github-ae@latest" %}，来访问 {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}使用 SAML 单点登录 (SSO) 的组织{% endif %}。{% if currentVersion == "free-pro-team@latest" %}从 {% data variables.product.product_name %} 使用 IdP 成功验证后，您必须授权要用于访问组织资源的的任何个人访问令牌、SSH 密钥或 {% data variables.product.prodname_oauth_app %}。{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/about-authentication-with-saml-single-sign-on versions: free-pro-team: '*' github-ae: '*' +topics: + - sso --- +### 关于使用 SAML SSO 进行身份验证 + {% if currentVersion == "github-ae@latest" %} -SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. +SAML SSO 允许企业所有者从 SAML IdP 集中控制和安全访问 {% data variables.product.product_name %}。 在浏览器中访问 {% data variables.product.product_location %} 时，{% data variables.product.product_name %} 会将用户重定向到您的 IdP 进行身份验证。 在使用 IdP 上的帐户成功进行身份验证后，IdP 会将您重定向回 {% data variables.product.product_location %}。 {% data variables.product.product_name %} 将验证 IdP 的响应，然后授予访问权限。 {% data reusables.saml.you-must-periodically-authenticate %} -If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. +如果您无法访问 {% data variables.product.product_name %}，请与本地企业所有者或 {% data variables.product.product_name %} 的管理员联系。 您可以在 {% data variables.product.product_name %} 上的任何页面底部单击 **Support（支持）**找到企业的联系信息。 {% data variables.product.company_short %} 和 {% data variables.contact.github_support %} 无法访问您的 IdP，并且无法解决身份验证问题。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. +{% data reusables.saml.dotcom-saml-explanation %} 组织所有者可以邀请您在 {% data variables.product.prodname_dotcom %} 上的用户帐户加入其使用 SAML SSO 的组织，这样您可以对该组织做出贡献，并且保留您在 {% data variables.product.prodname_dotcom %} 上的现有身份和贡献。 -When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. +在访问使用 SAML SSO 的组织中的资源时，{% data variables.product.prodname_dotcom %} 会将您重定向到组织的 SAML IdP 进行身份验证。 在 IdP 上成功验证您的帐户后，IdP 会将您重定向回到 {% data variables.product.prodname_dotcom %}，您可以在那里访问组织的资源。 {% data reusables.saml.outside-collaborators-exemption %} -If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. +如果您最近在浏览器中使用组织的 SAML IdP 进行过身份验证，则在访问使用 SAML SSO 的 {% data variables.product.prodname_dotcom %} 组织时会自动获得授权。 如果您最近没有在浏览器中使用组织的 SAML IdP 进行身份验证，则必须在 SAML IdP 进行身份验证后才可访问组织。 {% data reusables.saml.you-must-periodically-authenticate %} -To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. {% data variables.product.prodname_oauth_app %} access tokens are authorized by default. +要在命令行上使用 API 或 Git 访问使用 SAML SSO 的组织中受保护的内容，需要使用授权的 HTTPS 个人访问令牌或授权的 SSH 密钥。 -If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +如果没有个人访问令牌或 SSH 密钥，可以创建用于命令行的个人访问令牌或生成新的 SSH 密钥。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”或“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 -To use a new or existing personal access token or SSH key with an organization that enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +要对使用或实施 SAML SSO 的组织使用新的或现有的个人访问令牌或 SSH 密钥，需要授权该令牌或授权 SSH 密钥用于 SAML SSO 组织。 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”或“[授权 SSH 密钥用于 SAML 单点登录](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。 -You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %}. +### 关于 {% data variables.product.prodname_oauth_apps %} 和 SAML SSO + +每次授权 {% data variables.product.prodname_oauth_app %} 访问使用或实施 SAML SSO 的组织时，您必须有一个活动的 SAML 会话。 + +在企业或组织所有者为组织启用或实施 SAML SSO 后，您必须重新授权先前已授权访问组织的任何 {% data variables.product.prodname_oauth_app %}。 要查看您已授权或重新授权 {% data variables.product.prodname_oauth_app %} 的 {% data variables.product.prodname_oauth_apps %}，请访问您的 [{% data variables.product.prodname_oauth_apps %} 页面](https://github.com/settings/applications)。 {% endif %} -### Further reading +### 延伸阅读 -{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} -{% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% if currentVersion == "github-ae@latest" %}- "[关于企业的身份和访问权限管理](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md b/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md index 7967897fd4..b2eefc3b91 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/translations/zh-CN/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -36,8 +36,15 @@ topics: ![选择令牌作用域](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} 7. 单击 **Generate token（生成令牌）**。 ![生成令牌按钮](/assets/images/help/settings/generate_token.png) -8. 单击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 将令牌复制到剪贴板。 出于安全原因，离开此页面后，您将无法再次看到令牌。{% 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 %} +8. 单击 +{% octicon "clippy" aria-label="The copy to clipboard icon" %} 以将令牌复制到剪贴板。 出于安全原因，在离开页面后，您将无法再次看到令牌。 + {% if currentVersion == "free-pro-team@latest" %} + ![新建的令牌](/assets/images/help/settings/personal_access_tokens.png) + {% elsif currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} + ![新建的令牌](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![新建的令牌](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) + {% endif %} {% warning %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/creating-a-strong-password.md b/translations/zh-CN/content/github/authenticating-to-github/creating-a-strong-password.md index 04558bcbef..42ff134a62 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/creating-a-strong-password.md +++ b/translations/zh-CN/content/github/authenticating-to-github/creating-a-strong-password.md @@ -20,7 +20,7 @@ topics: - 使用 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/) 等密码管理器生成至少 15 个字符的密码。 - 为 {% data variables.product.product_name %} 生成唯一的密码。 如果您在别处使用 {% data variables.product.product_name %} 密码，并且该服务遭到入侵，则攻击者或其他恶意行为者可能使用该信息访问您的 {% data variables.product.product_name %} 帐户。 - 为您的帐户配置双重身份验证。 更多信息请参阅“[关于双重身份验证](/articles/about-two-factor-authentication)”。 -- 不与任何人分享您的密码，即使是潜在协作者。 在 {% data variables.product.product_name %} 上每个人都应使用自己的个人帐户。 有关协作方式的更多信息，请参阅：“[邀请协作者参与个人仓库](/articles/inviting-collaborators-to-a-personal-repository)”、“[关于协作开发模式](/articles/about-collaborative-development-models/)”或“[与组织中的团体协作](/articles/collaborating-with-groups-in-organizations/)”。 +- 不与任何人分享您的密码，即使是潜在协作者。 在 {% data variables.product.product_name %} 上每个人都应使用自己的个人帐户。 有关协作方式的更多信息，请参阅：“[邀请协作者参与个人仓库](/articles/inviting-collaborators-to-a-personal-repository)”、“[关于协作开发模式](/articles/about-collaborative-development-models/)”或“[与组织中的团体协作](/organizations/collaborating-with-groups-in-organizations/)”。 {% data reusables.repositories.blocked-passwords %} 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 e33e89c17d..d9008c9117 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 @@ -193,7 +193,7 @@ topics: | `sponsored_developer_create` | 当您的 {% 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)”） | | `sponsored_developer_profile_update` | 在编辑您的被赞助开发者个人资料时触发（请参阅“[编辑 {% 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` | 提交您对 {% 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)”） | -| `sponsored_developer_tier_description_update` | 当您更改赞助等级的说明时触发（请参阅“[更改赞助等级](/articles/changing-your-sponsorship-tiers)”） | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | | `sponsored_developer_update_newsletter_send` | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/articles/contacting-your-sponsors)”） | | `waitlist_invite_sponsored_developer` | 当您从等候名单被邀请加入 {% 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)”） | | `waitlist_join` | 当您加入成为被赞助开发者的等候名单时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） | diff --git a/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md index e258855a89..83190dc4a7 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md +++ b/translations/zh-CN/content/github/authenticating-to-github/telling-git-about-your-signing-key.md @@ -31,12 +31,12 @@ topics: {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} -1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file: +1. 如果您使用的不是 GPG 套件， 在 `zsh` shell 中运行以下命令将GPG 密钥添加到您的 `shrc` 文件或 `.zprofile` 文件（如果存在）： ```shell $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \ else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi ``` - Alternatively, if you use the `bash` shell, run this command: + 或者，如果您使用 `bash` shell，则运行皮命令： ```shell $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \ else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi @@ -93,7 +93,7 @@ topics: {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} -1. To add your GPG key to your bash profile, run the following command: +1. 要将 GPG 密钥添加到您的 bash 配置文件中，请运行以下命令： ```shell $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \ else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md index fcdb04309f..dccfd53be8 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github.md @@ -18,7 +18,7 @@ topics: 议题适用于讨论项目的具体细节，如漏洞修复和计划的改进。 更多信息请参阅“[关于议题](/articles/about-issues)”。 拉取请求允许您直接评论提议的更改。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests)”和“[评论拉取请求](/articles/commenting-on-a-pull-request)”。 -{% data reusables.organizations.team-discussions-purpose %} 更多信息请参阅“[关于团队讨论](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)”。 +{% data reusables.organizations.team-discussions-purpose %} 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 ### 反应评论意见 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 d25077aab3..f4c7590005 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 @@ -15,7 +15,7 @@ topics: 打开拉取请求后，具有*读取*权限的任何人都可以查看该拉取请求提议的更改并进行评论。 您也可以建议对代码行的具体更改，作者可直接从拉取请求应用这些更改。 更多信息请参阅“[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)”。 -仓库所有者和协作者可向具体的个人申请拉取请求审查。 组织成员也可向具有仓库读取权限的团队申请拉取请求审查。 更多信息请参阅“[申请拉取请求审查](/articles/requesting-a-pull-request-review)”。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}您可以指定自动分配一部分团队成员，而不是分配整个团队。 更多信息请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”。{% endif %} +仓库所有者和协作者可向具体的个人申请拉取请求审查。 组织成员也可向具有仓库读取权限的团队申请拉取请求审查。 更多信息请参阅“[申请拉取请求审查](/articles/requesting-a-pull-request-review)”。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}您可以指定自动分配一部分团队成员，而不是分配整个团队。 更多信息请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”。{% endif %} 审查允许讨论提议的更改，帮助确保更改符合仓库的参与指南及其他质量标准。 您可以在 CODEOWNERS 文件中定义哪些个人或团队拥有代码的特定类型或区域。 当拉取请求修改定义了所有者的代码时，该个人或团队将自动被申请为审查者。 更多信息请参阅“[关于代码所有者](/articles/about-code-owners/)”。 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 1a65d6b099..7effc9f189 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -14,7 +14,9 @@ topics: 如果启用拉取请求自动合并，则拉取请求在满足所有必需审查并且状态检查通过时将自动合并。 自动合并使您无需等待满足要求，可以继续执行其他任务。 -在使用拉取请求自动合并之前，必需对仓库启用自动合并。 更多信息请参阅“[管理仓库中的拉取请求自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)”。 +在使用拉取请求自动合并之前，必需对仓库启用自动合并。 更多信息请参阅“[管理仓库中拉取请求的自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)”。{% if currentversion == "free-proteam@latest" or currentversion == "github-ae@next " or currentversion ver_gt "enterprise-server@3.1" %} + +对拉取请求启用自动合并后，如果没有仓库写入权限的人员将新更改推送到头部分支或切换拉取请求的基础分支，则自动合并将被禁用。 例如，如果维护者允许从复刻自动合并拉取请求，则在贡献者推送对拉取请求的新更改后，自动合并将被禁用。{% endif %} 您可以通过[联系我们](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback)提供关于自动合并的反馈。 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md index 6d3d545967..e333d784eb 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review.md @@ -13,7 +13,7 @@ topics: 用户帐户拥有的仓库的所有者和协作者可以分配拉取请求审查。 拥有仓库查验漏洞权限的组织成员可以分配拉取请求审查。 -所有者或协作者可以将拉取请求审核分配给被明确授予用户拥有仓库[读取权限](/articles/access-permissions-on-github)的任何人。 组织成员也可将拉取请求审查分配给拥有仓库读取权限的任何个人或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 更多信息请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”。{% endif %} +所有者或协作者可以将拉取请求审核分配给被明确授予用户拥有仓库[读取权限](/articles/access-permissions-on-github)的任何人。 组织成员也可将拉取请求审查分配给拥有仓库读取权限的任何个人或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 更多信息请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”。{% endif %} {% note %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index 30a135be9e..5ae1882a3b 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -79,5 +79,5 @@ topics: - “[设置仓库可见性](/articles/setting-repository-visibility)” - "[关于复刻](/articles/about-forks)" - "[管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" -- "[管理组织的复刻策略](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" +- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" - "{% if currentversion == "free-proteam@latest" %}[在企业帐户中执行仓库管理策略](/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 %}[在企业中执行仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}" 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 cfaeecdc73..e889cb5c49 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 @@ -23,7 +23,7 @@ topics: 当具有管理员或所有者权限的人员启用必需审查时，他们也可选择性要求代码所有者批准后，作者才可合并仓库中的拉取请求。 更多信息请参阅“[关于受保护分支](/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 %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}如果团队启用了代码审查分配，则个别审批无法满足受保护分支中代码所有者审批的要求。 更多信息请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-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.22" %} 如果文件具有代码所有者，则在打开拉取请求之前可以看到代码所有者是谁。 在仓库中，您可以浏览文件并将鼠标悬停在上方 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md index bf605857b9..2756dded18 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-languages.md @@ -19,7 +19,7 @@ topics: {% data variables.product.product_name %} 使用开源 [Linguist 库](https://github.com/github/linguist)来 确定用于语法突出显示和仓库统计信息的文件语言。 语言统计数据在您推送更改到默认分支后将会更新。 -有些文件难以识别，有时项目包含的库和供应商文件多于其主要代码。 如果您收到错误结果，请查阅 Linguist [故障排除指南](https://github.com/github/linguist#troubleshooting)寻求帮助。 +有些文件难以识别，有时项目包含的库和供应商文件多于其主要代码。 如果您收到错误结果，请查阅 Linguist [故障排除指南](https://github.com/github/linguist/blob/master/docs/troubleshooting.md)寻求帮助。 ### 标记语言 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md index 62f0b18ae7..d78781b376 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repository-visibility.md @@ -22,7 +22,7 @@ topics: 互联网上的所有人都可以访问公共仓库。 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 企业成员可以访问内部仓库。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。 {% endif %} -组织所有者始终有权访问其组织中创建的每个仓库。 更多信息请参阅“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)”。 +组织所有者始终有权访问其组织中创建的每个仓库。 更多信息请参阅“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。 拥有仓库管理员权限的人可更改现有仓库的可见性。 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md index 33a8150647..b5d0272abd 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -23,13 +23,13 @@ topics: ``` 3. 镜像推送至新仓库。 ```shell - $ cd old-repository.git + $ cd old-repository $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git ``` 4. 删除您之前创建的临时本地仓库。 ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### 镜像包含 {% data variables.large_files.product_name_long %} 对象的仓库。 @@ -41,7 +41,7 @@ topics: ``` 3. 导航到刚克隆的仓库。 ```shell - $ cd old-repository.git + $ cd old-repository ``` 4. 拉取仓库的 {% data variables.large_files.product_name_long %} 对象。 ```shell @@ -58,7 +58,7 @@ topics: 7. 删除您之前创建的临时本地仓库。 ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf old-repository ``` ### 镜像其他位置的仓库 @@ -72,7 +72,7 @@ topics: ``` 3. 设置到镜像的推送位置。 ```shell - $ cd repository-to-mirror.git + $ cd repository-to-mirror $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored ``` diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md index 472d623265..3da283ddca 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/error-repository-not-found.md @@ -41,7 +41,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} > provide shell access. ``` -如果仓库属于组织，并且您使用的是 OAuth App 生成的 SSH 密钥，则 OAuth App 访问权限可能已被组织所有者限制。 更多信息请参阅“关于 OAuth App 访问限制”。 +如果仓库属于组织，并且您使用的是 OAuth App 生成的 SSH 密钥，则 OAuth App 访问权限可能已被组织所有者限制。 For more information, see "About OAuth App access restrictions." 更多信息请参阅[添加 SSH 密钥到 GitHub 帐户](/articles/adding-a-new-ssh-key-to-your-github-account)。 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 21e5372ef1..c71143a9b2 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 @@ -1,6 +1,6 @@ --- title: 在 Visual Studio 中使用代码空间 -intro: '通过与 {% data variables.product.product_name %} 上的帐户连接，您可以直接在 {% data variables.product.prodname_vs %} 的代码空间中进行开发。' +intro: '此预览已结束，将不再接受注册。' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,50 +10,10 @@ topics: {% note %} -**注：**{% data variables.product.prodname_codespaces %} 目前是有限公测版，可能会有变动。 在公测期间，{% data variables.product.prodname_dotcom %} 不对 {% data variables.product.prodname_codespaces %} 的可用性做任何保证。 [注册有限公测版](https://github.com/features/codespaces/signup-vs)。 有关加入公测的更多信息，请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)”。 +**注：**{% data variables.product.prodname_codespaces %} 目前是有限公测版，可能会有变动。 在公测期间，{% data variables.product.prodname_dotcom %} 不对 {% data variables.product.prodname_codespaces %} 的可用性做任何保证。 {% endnote %} ### 关于 {% data variables.product.prodname_vs %} 中的代码空间 -您可以在 {% data variables.product.prodname_vs %} 中创建代码来开发 Windows 环境中的应用程序。 在 {% data variables.product.prodname_vs %} 中使用代码空间时，您可以浏览源代码、构建解决方案以及将更改提交到仓库。 - -您必须在 {% data variables.product.prodname_vs %} 中创建代码空间才能将其用于应用程序。 在 {% data variables.product.prodname_vs %} 外部创建的代码空间目前无法与 {% data variables.product.prodname_vs %} 结合使用。 - -### 基本要求 - -在 {% data variables.product.prodname_vs %} 中配置代码空间之前，您必须下载最新版本的 [{% data variables.product.prodname_vs %} 预览](https://aka.ms/vspreview)。 - -#### 启用 {% data variables.product.prodname_vs %} 与 {% data variables.product.prodname_github_codespaces %} 之间的连接 - -{% data variables.product.prodname_github_codespaces %} 与 {% data variables.product.prodname_vs %} 的连接在默认情况下未启用，因此您首先需要启用 Preview Features（预览功能）选项。 - -1. 在 {% data variables.product.prodname_vs %} 预览中，使用 Tools（工具）下拉菜单，然后单击 **Options（选项）**。 -2. 在 **Environment（环境）**下，选择 **Preview Features（预览功能）**，然后选中**连接到 {% data variables.product.prodname_github_codespaces %}** 预览功能。 ![选中“连接到 {% data variables.product.prodname_github_codespaces %} 预览功能”](/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png) -3. 您需要重新启动 {% data variables.product.prodname_vs %} 才能使用该功能。 - -### 在 {% data variables.product.prodname_vs %} 中创建代码空间 - -1. 启动 {% data variables.product.prodname_vs %} 时，Start （开始）窗口将在“Get started（开始使用）”下显示 **Connect to a codespace（连接到代码空间）**按钮。 ![带有“连接到代码空间”的 Visual Studio 开始窗口](/assets/images/help/codespaces/visual-studio-start-window.png) -2. 单击 **Connect to a codespace（连接到代码空间）**。 -3. 单击**登录 {% data variables.product.prodname_dotcom %}** 并按提示操作，或者单击 **Create one!（创建一个！）**以创建新的 {% data variables.product.prodname_dotcom %} 帐户并登录该帐户。 ![Visual Studio 登录到 {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/visual-studio-sign-in-to-github.png) -4. 在“Codespace details（代码空间详情）”下，键入您希望 {% data variables.product.prodname_github_codespaces %} 克隆到代码空间的仓库 URL。 -5. （可选）使用 Instance type（实例类型）和 Suspend after（完成后挂起）下拉菜单配置更多代码空间详细信息。 ![Visual Studio 代码空间详情](/assets/images/help/codespaces/visual-studio-codespace-details.png) -6. 单击 **Create and Connect（创建并连接）**。 {% data variables.product.prodname_github_codespaces %} 将开始准备代码空间，并在代码空间准备就绪后打开 {% data variables.product.prodname_vs %}。 代码空间名称将出现在菜单的远程指示器中。 ![连接到 eShopOnWeb 仓库代码空间的 Visual Studio](/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png) - -### 在 {% data variables.product.prodname_vs %} 中打开代码空间 - -1. 使用 File（文件）下拉菜单，然后单击 **Connect to a Codespace（连接到代码空间）**。 ![Visual Studio 文件连接到代码空间菜单项](/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png) -2. 在 "{% data variables.product.prodname_github_codespaces %}" 下，单击要连接到的代码空间，然后单击 **Connect（连接）**。 ![显示可用代码空间和详细信息的 Visual Studio](/assets/images/help/codespaces/visual-studio-connect-codespace.png) - -### 配置 {% 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) 允许您将额外的框架和工具安装到 Windows 开发代码空间中以及修改环境变量等。 - -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)。 有关 devinit 的更多信息，请参阅 [devinit 使用入门](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit)。 +GitHub Codespaces 在 Visual Studio 2019 中的私人预览已结束。 更多信息请参阅 [Visual Studio 2019 文档](https://docs.microsoft.com/visualstudio/ide/codespaces/codespaces-overview?view=vs-2019)。 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 9684696ef4..835490ee4a 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -1,51 +1,49 @@ --- -title: About code scanning -intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' +title: 关于代码扫描 +intro: '您可以使用 {% data variables.product.prodname_code_scanning %} 在 {% data variables.product.prodname_dotcom %} 上查找项目中的安全漏洞和代码错误。' product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/managing-security-vulnerabilities/about-automated-code-scanning versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - 安全 --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### About {% data variables.product.prodname_code_scanning %} +### 关于 {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.about-code-scanning %} -You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. +您可以使用 {% data variables.product.prodname_code_scanning %} 来查找代码中现有的问题，并且对其进行分类和确定修复的优先级。 {% data variables.product.prodname_code_scanning_capc %} 还可防止开发者引入新问题。 您可以计划在特定的日期和时间进行扫描，或在仓库中发生特定事件（如推送）时触发扫描。 -If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." +如果 {% data variables.product.prodname_code_scanning %} 发现您的代码中可能存在漏洞或错误，{% data variables.product.prodname_dotcom %} 会在仓库中显示警报。 在修复触发警报的代码之后，{% data variables.product.prodname_dotcom %} 将关闭警报。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use 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 %} 结果，您可以使用 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)”。 -To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." +要开始 {% data variables.product.prodname_code_scanning %}，请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)”。 -### About {% data variables.product.prodname_codeql %} +### 关于 {% data variables.product.prodname_codeql %} -You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +您可以在 [`github/codeql`](https://github.com/github/codeql) 仓库中查看并参与 {% data variables.product.prodname_code_scanning %} 的查询。 {% data variables.product.prodname_codeql %} 将代码视为数据，允许您在代码中查找潜在漏洞，比传统的静态分析工具更可靠。 -{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. +{% data variables.product.prodname_ql %} 是授权 {% data variables.product.prodname_codeql %} 的查询语言。 {% data variables.product.prodname_ql %} 是一种面向对象的逻辑编程语言。 {% data variables.product.company_short %}、语言专家和安全研究人员创建用于 {% data variables.product.prodname_code_scanning %} 的查询，查询是开源的。 社区维护和更新查询，以改善分析和减少误报。 更多信息请参阅 GitHub Security Lab 网站上的 [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)。 -{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. +有关 {% data variables.product.prodname_code_scanning %} 的 API 端点的更多信息，请参阅“[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)”。 {% data reusables.code-scanning.supported-languages %} -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. +您可以在 [`github/codeql`](https://github.com/github/codeql) 仓库中查看并参与 {% data variables.product.prodname_code_scanning %} 的查询。 更多信息请参阅 {% data variables.product.prodname_codeql %} 文档中的 [{% data variables.product.prodname_codeql %} 查询](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/)。 {% if currentVersion == "free-pro-team@latest" %} -### About billing for {% data variables.product.prodname_code_scanning %} +### 关于 {% data variables.product.prodname_code_scanning %} 的计费 -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data variables.product.prodname_code_scanning_capc %} 使用 {% data variables.product.prodname_actions %}，{% data variables.product.prodname_code_scanning %} 工作流程的每次运行将耗用 {% data variables.product.prodname_actions %} 的分钟数。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)”。 {% endif %} -### About third-party code scanning tools +### 关于第三方代码扫描工具 {% data reusables.code-scanning.you-can-upload-third-party-analysis %} @@ -53,9 +51,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### Further reading +### 延伸阅读 {% if currentVersion == "free-pro-team@latest" 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 +- 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 612c2f6227..7ba19e1c1a 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 @@ -1,60 +1,59 @@ --- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' +title: 配置代码扫描 +intro: '您可以配置 {% data variables.product.prodname_dotcom %} 如何扫描项目代码以查找漏洞和错误。' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' +permissions: '拥有仓库写入权限的人可配置仓库的 {% data variables.product.prodname_code_scanning %}。' miniTocMaxHeadingLevel: 4 versions: - free-pro-team: '*' - enterprise-server: '>=2.22' + enterprise-server: '2.22' +topics: + - 安全 --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -### About {% data variables.product.prodname_code_scanning %} configuration +### 关于 {% data variables.product.prodname_code_scanning %} 配置 -You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." +您可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_name %} 中运行 {% data variables.product.prodname_code_scanning %}，或使用 {% data variables.product.prodname_codeql_runner %} 从持续集成 (CI) 系统运行它。 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。 有关 {% data variables.product.prodname_codeql_runner %} 的更多信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”。 -This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. +本文说明在 {% data variables.product.product_name %} 上运行 {% data variables.product.prodname_code_scanning %}。 -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." +在为仓库配置 {% data variables.product.prodname_code_scanning %} 之前，必须将 {% data variables.product.prodname_actions %} 工作流程添加到仓库中以设置 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)”。 {% data reusables.code-scanning.edit-workflow %} -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. +您可以为 {% data variables.product.prodname_code_scanning %} 编写配置文件。 {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} 在 {% data variables.product.prodname_dotcom_the_website %} 上，{% endif %}包含您可以使用的其他 {% data variables.product.prodname_code_scanning %} 工作流程。 {% if currentVersion == "free-pro-team@latest" %}您可以在“{% data variables.product.prodname_code_scanning %} 使用入门”页找到这些选项，该页面可从 **{% octicon "shield" aria-label="The shield symbol" %} Security（安全）**选项卡访问。{% endif %}本文给出的具体示例与 {% data variables.product.prodname_codeql_workflow %} 文件相关。 -### Editing a {% data variables.product.prodname_code_scanning %} workflow +### Editing a code scanning workflow -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. +{% data variables.product.prodname_dotcom %} 将工作流程文件保存在仓库的 _.github/workflows_ 目录中。 您可以通过搜索其文件名来查找已添加的工作流程。 例如，默认情况下，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的工作流程文件被称为 _codeql-analysis.yml_。 -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) +1. 在仓库中，浏览至要编辑的工作流程文件。 +1. 要打开工作流程编辑器，在文件视图右上角单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑工作流程文件按钮](/assets/images/help/repository/code-scanning-edit-workflow-button.png) +1. 编辑文件后，单击 **Start commit（开始提交）**并完成“Commit changes（提交更改）”表单。 您可以选择直接提交到当前分支，或者创建一个新分支并启动拉取请求。 ![将更新提交到 codeql.yml 工作流程](/assets/images/help/repository/code-scanning-workflow-update.png) -For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +有关编辑工作流程文件的更多信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 -### Configuring frequency +### 配置频率 -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. +您可以按时间表或在仓库中发生特定事件时扫描代码。 -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. +每当推送到仓库以及每次创建拉取请求时，时扫描代码可防止开发者在代码中引入新的漏洞和错误。 按时间表扫描可了解 {% data variables.product.company_short %}、安全研究者和社区发现的最新漏洞和错误，即使开发者并未主动维护仓库。 -#### Scanning on push +#### 按推送扫描 -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." +如果使用默认工作流程，则除了事件触发的扫描之外，{% data variables.product.prodname_code_scanning %} 还会每周扫描一次仓库代码。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#on)”。 -#### Scanning pull requests +#### 扫描拉取请求 -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +默认 {% data variables.product.prodname_codeql_workflow %} 使用 `pull_request` 事件在针对默认分支的拉取请求上触发代码扫描。 {% if currentversion ver_gt "enterprise-server@2.21" %}如果从私有复刻打开拉取请求，`pull_request` 事件不会触发。{% else %}如果拉取请求来自私有复刻，`pull_request` 事件仅在仓库设置中选择了“Run workflows from fork pull requests（从复刻拉取请求运行工作流程）”选项时触发。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." +有关 `pull_request` 事件的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)”。 -#### Avoiding unnecessary scans of pull requests +#### 避免对拉取请求进行不必要的扫描 -You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array. +您可能希望避免针对默认分支的特定拉取请求触发代码扫描，而不管更改了哪些文件。 可以通过在 {% data variables.product.prodname_code_scanning %} 工作流程中指定 `on:pull_request:paths-ignore` or `on:pull_request:paths` 来进行配置。 例如，如果拉取请求中唯一的更改是文件扩展名为 `.md` 或 `.txt` 的文件，则您可以使用以下 `paths-ignore` 数组。 ``` yaml on: @@ -69,28 +68,28 @@ on: {% note %} -**Notes** +**注：** -* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)." -* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit. +* `on:pull_request:paths-witch` 和 `on:pull_request:pull_request:path` 设置条件来确定工作流程中的操作是否会在拉取请求上运行。 它们无法确定在操作_运行_时将分析哪些文件。 当拉取请求包含 `on:pull_request:paths-with` 或 `on:pull_request:path:path` 未匹配的任何文件时，工作流程将运行操作并扫描拉取请求中更改的所有文件，包括 `on:pull_request:paths-ignore` 或 `on:pull_request:paths` 匹配的文件，除非文件被排除在外。 有关如何从分析中排除文件的信息，请参阅“[指定要扫描的目录](#specifying-directories-to-scan)”。 +* 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 工作流程文件， 不要对 `on:push` 事件使用 `paths-ignore` 或 `paths` 关键词， 因为这可能导致缺少分析。 为了获得准确的结果，{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 需要能够与上次提交的分析比较新的变化。 {% endnote %} -For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." +有关使用 `on:pull_request:paths-ignore` 和 `on:pull_request:paths` 确定工作流程何时对拉取请求运行的详细信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 -#### Scanning on a schedule +#### 按时间表扫描 -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." +默认 {% data variables.product.prodname_code_scanning %} 工作流程在拉取请求的 `HEAD` 提交时使用 `pull_request` 事件触发代码扫描。 要调整此时间表，请编辑工作流程中的 `cron` 值。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onschedule)”。 {% note %} -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. +**注**：{% data variables.product.prodname_dotcom %} 只运行默认分支上工作流程中的预定作业。 在任何其他分支上的工作流程中更改时间表后，需要将该分支合并到默认分支才能使更改生效。 {% endnote %} -#### Example +#### 示例 -The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. +{% data variables.product.prodname_dotcom %} saves workflow files in the `.github/workflows` directory of your repository. 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`. ``` yaml on: @@ -99,19 +98,19 @@ on: pull_request: branches: [main] schedule: - - cron: '0 15 * * 0' + - cron: '40 7 * * 2' ``` -This workflow scans: -* Every push to the default branch and the protected branch -* Every pull request to the default branch -* The default branch at 3 P.M. every Sunday +此工作流程扫描： +* 对默认分支和受保护分支的每次推送 +* 对默认分支的每个拉取请求 +* 默认分支（每个星期二 7:40 UTC） -### Specifying an operating system +### 指定操作系统 -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} +如果您的代码需要使用特定的操作系统进行编译，您可以在工作流程中配置它。 编辑 `jobs.analyze.runs-on` 的值以指定运行 {% data variables.product.prodname_code_scanning %} 操作的机器操作系统。 {% if currentVersion ver_gt "enterprise-server@2.21" %}在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% else %} -If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} +如果选择使用自托管的运行器进行代码扫描，可以在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% endif %} ``` yaml jobs: @@ -120,23 +119,23 @@ jobs: runs-on: [self-hosted, ubuntu-latest] ``` -{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。{% endif %} -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." +{% data variables.product.prodname_code_scanning_capc %} 支持 macOS、Ubuntu 和 Windows 的最新版本。 因此，此设置的典型值为：`ubuntu-latest`、`windows-latest` 和 `macos-latest`。 更多信息请参阅 {% if currentVersion ver_gt "enterprise-server@2.21" %}“[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)”和“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}”[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}“。 -{% if currentVersion ver_gt "enterprise-server@2.21" %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} +{% if currentversion ver_gt "enterprise-server@2.21" %}您必须确保 Git 位于自托管运行器的 PATH 变量中。{% else %}如果您使用自托管运行器，必须确保 Git 在 PATH 变量中。{% endif %} -### Changing the languages that are analyzed +### 更改分析的语言 -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages. +{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 会自动检测用受支持的语言编写的代码。 {% data reusables.code-scanning.supported-languages %} -The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." +默认 {% data variables.product.prodname_codeql_workflow %} 文件包含一个名为 `language` 的构建矩阵，其中列出了仓库中被分析的语言。 将 {% data variables.product.prodname_code_scanning %} 添加到仓库时，{% data variables.product.prodname_codeql %} 会自动填充此矩阵。 使用 `language` 矩阵优化 {% data variables.product.prodname_codeql %} 以并行运行每个分析。 由于并行构建的性能优势，我们建议所有工作流程都采用此配置。 有关构建矩阵的更多信息，请参阅“[管理复杂的工作流程](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)”。 {% data reusables.code-scanning.specify-language-to-analyze %} -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix. +如果您的工作流程使用 `language` 矩阵，则 {% data variables.product.prodname_codeql %} 会被硬编码为仅分析矩阵中的语言。 如需更改要分析的语言，请编辑矩阵变量的值。 您可以删除某种语言以防止被分析，也可以添加在设置 {% data variables.product.prodname_code_scanning %} 时仓库中不存在的语言。 例如，如果在设置 {% data variables.product.prodname_code_scanning %} 时，仓库最初只包含 JavaScript，但您后来添加了 Python 代码，则需要将 `python` 添加到矩阵中。 ```yaml jobs: @@ -149,7 +148,7 @@ jobs: language: ['javascript', 'python'] ``` -If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. +如果工作流程中不包含名为 `language` 的矩阵，则 {% data variables.product.prodname_codeql %} 将被配置为按顺序运行分析。 如果您未在工作流程中指定语言，则 {% data variables.product.prodname_codeql %} 将自动检测并尝试分析仓库中所有受支持的语言。 如果不愿意使用矩阵选择要分析的语言，您可以使用 `init` 操作下的 `languages` 参数。 ```yaml - uses: github/codeql-action/init@v1 @@ -157,15 +156,15 @@ If your workflow does not contain a matrix called `language`, then {% data varia languages: cpp, csharp, python ``` {% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies +### 分析 Python 依赖项 -For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: +对于仅使用 Linux 的 GitHub 托管的运行器，{% data variables.product.prodname_codeql_workflow %} 将尝试自动安装 Python 依赖项以提供更多 CodeQL 分析结果。 可通过为“初始化 CodeQL”步骤调用的操作指定 `setup-python-dependencies` 参数来控制此行为。 默认情况下，此参数设置为 `true`： -- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies. +- 如果仓库包含用 Python 编写的代码，“初始化 CodeQL”步骤将在 GitHub 托管的运行器上安装必要的依赖项。 如果自动安装成功，该操作还会将环境变量 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件。 -- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete. +- 如果仓库没有任何 Python 依赖项，或者依赖项是以意外方式指定的，您将收到警告，并且该操作会继续执行其余作业。 即使在解释依赖项时出现问题，该操作也可以成功运行，但结果可能不完整。 -Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract: +或者，您也可以在任何操作系统上手动安装 Python 依赖项。 您需要添加 `setup-python-dependencies` 并将其设置为 `false`，以及将 `CODEQL_PYTHON` 设置为包含依赖项的 Python 可执行文件，如此工作流程摘要中所示： ```yaml jobs: @@ -199,38 +198,45 @@ jobs: ``` {% endif %} -### Running additional queries +### 运行额外查询 {% data reusables.code-scanning.run-additional-queries %} -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. +要添加一个或多个查询套件，请在配置文件中添加 `queries` 部分。 如果查询在私有仓库中，请使用 `external-repository-token` 参数来指定可以访问私有仓库的令牌。 +{% raw %} ``` yaml - uses: github/codeql-action/init@v1 with: queries: COMMA-SEPARATED LIST OF PATHS + # Optional. 提供令牌来访问私有仓库. + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. +您也可以在配置文件中指定额外查询套件以运行它们。 查询套件是查询的集合，通常按目的或语言分组。 {% data reusables.code-scanning.codeql-query-suites %} -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." +如果还使用配置文件进行自定义设置，则将使用工作流程中指定的任何额外查询，而不是配置文件中指定的任何查询。 如果您要运行此处指定的额外查询与配置文件中指定的查询的组合，请在工作流程中的 `queries` 值之前加上前缀 `+` 符号。 有关配置文件的示例，请参阅“[配置文件示例](#example-configuration-files)”。 -In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. +在下面的示例中，`+` 符号可确保结合使用额外查询与所引用配置文件中指定的任何查询。 +{% raw %} ``` 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 + external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` +{% endraw %} -### Using a custom configuration file +### 使用第三方代码扫描工具 -As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. +除了在工作流程文件中指定要运行的查询之外，您还可以在单独的配置文件中执行此操作。 您还可以使用配置文件禁用默认查询，并指定分析过程中要扫描的目录。 -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. +在工作流程文件中，使用 `init` 操作的 `config-file` 参数指定要使用的配置文件的路径。 此示例加载配置文件 _./.github/codeql/codeql-config.yml_。 ``` yaml - uses: github/codeql-action/init@v1 @@ -238,13 +244,23 @@ 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 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_. +{% data reusables.code-scanning.custom-configuration-file %} -The settings in the file are written in YAML format. +如果配置文件位于外部私有仓库中，请使用 `init` 操作的 `external-repository-token` 参数来指定可以访问私有仓库的令牌。 -#### Specifying additional queries +{% raw %} +```yaml +uses: github/codeql-action/init@v1 +with: + external-repository-token: ${{ secrets.ACCESS_TOKEN }} +``` +{% endraw %} -You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file. +配置文件中的设置以 YAML 格式编写。 + +#### 指定额外查询 + +您可以在 `queries` 数组中指定额外查询。 数组的每个元素都包含一个 `uses` 参数，该参数的值标识单个查询文件、包含查询文件的目录或查询套件定义文件。 ``` yaml queries: @@ -253,17 +269,17 @@ queries: - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls ``` -Optionally, you can give each array element a name, as shown in the example configuration files below. +（可选）您可以给每个数组元素一个名称，如下面的示例配置文件所示。 -For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. +有关额外查询的更多信息，请参阅上面的“[运行额外查询](#running-additional-queries)”。 -#### Disabling the default queries +#### 禁用默认查询 -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. +如果只想运行自定义查询，您可以通过在配置文件中添加 `disable-default-queries: true` 来禁用默认安全查询。 -#### Specifying directories to scan +#### 指定要扫描的目录 -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array. +对于 {% data variables.product.prodname_codeql %} 支持的解释语言（Python 和 JavaScript/TypeScript），您可以通过在配置文件中添加 `paths` 数组将 {% data variables.product.prodname_code_scanning %} 限制到特定目录中的文件。 添加 `paths-ignore` 数组可从分析排除特定目录中的文件。 ``` yaml paths: @@ -275,46 +291,27 @@ paths-ignore: {% note %} -**Note**: +**注**： -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. +* 在 {% data variables.product.prodname_code_scanning %} 配置文件上下文中使用的 `paths` 和 `paths-ignore` 关键字，不应与用于工作流程中 `on..paths` 的相同关键字相混淆。 当它们用于修改工作流程中的 `on.` 时，它们将决定在有人修改指定目录中的代码时是否运行操作。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 +* `**` 字符只能用在行的开头或结尾，或用斜杠包围，并且不能将 `**` 与其他字符混合在一起。 例如，`foo/**`、`**/foo` 和 `foo/**/bar` 都是允许的语法，但 `**foo` 不是。 但是，可以将单星号与其他字符一起使用，如示例中所示。 您需要引用任何包含 `*` 字符的内容。 {% endnote %} -For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +对于编译的语言，如果要将 {% data variables.product.prodname_code_scanning %} 限制到项目中的特定目录，您必须在工作流程中指定适当的构建步骤。 用于在构建过程中排除目录的命令将取决于您的构建系统。 更多信息请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. +在修改特定目录中的代码时，您可以快速分析单个仓库中的小部分。 您需要在构建步骤中排除目录并在工作流程文件中对 [`on.`](https://help.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) 使用 `paths-ignore` 和 `paths` 关键字。 -#### Example configuration files +#### 配置文件示例 {% data reusables.code-scanning.example-configuration-files %} -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages +### 为编译语言配置 {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} -{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)." +{% data reusables.code-scanning.autobuild-add-build-steps %} 有关如何为编译语言配置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)”。 -### Accessing private repositories +### 将 {% data variables.product.prodname_code_scanning %} 数据上传到 {% data variables.product.prodname_dotcom %} -If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs..steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." - -For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. - -{% 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 %} - -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} - -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." +{% data variables.product.prodname_dotcom %} 可显示通过第三方工具在外部生成的代码分析数据。 通过在工作流程中添加 `upload-sarif` 操作，您可以在 {% data variables.product.prodname_dotcom %} 中显示第三方工具的代码分析。 更多信息请参阅“[将 SARIF 文件上传到 GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)”。 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 5e040149d8..876c9bd7f9 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 @@ -37,7 +37,7 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -1. 在 "{% data variables.product.prodname_code_scanning_capc %}" 下，单击要探索的警报。 ![警报摘要](/assets/images/help/repository/code-scanning-click-alert.png) +1. 在 "{% data variables.product.prodname_code_scanning_capc %}" 下，单击要探索的警报。 ![警报摘要](/assets/images/enterprise/3.1/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) @@ -49,7 +49,7 @@ versions: 警报只能在一个分支中修复。 您可以在警报摘要上使用“Branch（分支）”下拉菜单检查警报是否是在特定分支中修复的。 -![按分支过滤警报](/assets/images/help/repository/code-scanning-branch-filter.png) +![按分支过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) {% if currentVersion == "enterprise-server@2.22" %} @@ -102,11 +102,11 @@ versions: （可选）您可以使用过滤器显示警报子集，然后一次删除所有匹配的警报。 例如，如果您从 {% data variables.product.prodname_codeql %} 分析中删除了查询，您可以使用“Rule（规则）”过滤器仅列出该查询的警报，然后选择并删除所有这些警报。 - ![按规则过滤警报](/assets/images/help/repository/code-scanning-filter-by-rule.png) + ![按规则过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) 1. 如果要忽略警报，请务必先了解警报，以便选择正确的忽略原因。 单击要了解的警报。 - ![从摘要列表中打开警报](/assets/images/help/repository/code-scanning-click-alert.png) + ![从摘要列表中打开警报](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) 1. 查看警报，然后单击 **Dismiss（忽略）**并选择关闭警报的原因。 ![选择忽略警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md index 077944452c..786ff2412b 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -25,7 +25,7 @@ topics: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) 4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 2" %}工作流程仅在与仓库中检测到的编程语言相关时才会显示。 {% data variables.product.prodname_codeql_workflow %} 始终显示，但仅在 {% data variables.product.prodname_codeql %} 分析支持仓库中存在的语言时才启用“Set up this workflow（设置此工作流程）”按钮。{% endif %} 5. Optionally, to customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." @@ -65,7 +65,7 @@ topics: **注意：** 如果您提出拉取请求以将 {% data variables.product.prodname_code_scanning %} 工作流程添加到仓库，则在合并拉取请求之前，来自该拉取请求的警报不会直接显示在 {% data variables.product.prodname_code_scanning_capc %} 页面上。 如果发现任何警报，您可以在合并拉取请求之前查看这些警报，方法是在 {% data variables.product.prodname_code_scanning_capc %} 页面上的横幅中点击**发现的 _n_ 条警报**链接。 - ![点击"发现的 n 条警报"链接](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![点击"发现的 n 条警报"链接](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) {% endnote %} @@ -91,7 +91,7 @@ topics: 要检查是否扫描了分支，请转到 {% data variables.product.prodname_code_scanning_capc %} 页面，单击 **Branch<（分支）**下拉菜单并选择相关分支。 - ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) {% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} 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 f1c4d3e53a..0ba16c8786 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 @@ -1,27 +1,30 @@ --- -title: Troubleshooting the CodeQL workflow -shortTitle: Troubleshooting CodeQL -intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.' +title: CodeQL 工作流程疑难解答 +shortTitle: CodeQL 疑难解答 +intro: '如果您在 {% data variables.product.prodname_code_scanning %} 方面遇到问题，可使用这些提示来解决问题。' 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' + enterprise-server: '2.22' +topics: + - 安全 --- {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.not-available %} -### Automatic build for a compiled language fails +### 生成详细的调试日志 -If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps. +要生成更详细的日志输出，您可以启用步骤调试日志记录。 更多信息请参阅“[启用调试日志记录](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)”。 -- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, 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)." For more information about replacing the `autobuild` step, 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)." +### 编译语言的自动构建失败 -- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. +如果项目中编译语言的代码自动构建失败，请尝试以下疑难解答步骤。 - The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step: +- 从 {% data variables.product.prodname_code_scanning %} 工作流程中删除 `autobuild` 步骤，并添加特定构建步骤。 有关编辑工作流程的信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)”。 有关替换 `autobuild` 步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/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_codeql %} 会隐式检测代码库中支持的语言。 在此配置中，对于编译语言 C/C++、C# 和 Java，{% data variables.product.prodname_codeql %} 只分析涵盖最多源文件的语言。 编辑工作流程并添加一个构建矩阵，以指定要分析的语言。 默认的 CodeQL 分析工作流程使用这种矩阵。 + + 以下工作流程摘录显示了如何在作业策略中使用矩阵来指定语言，然后在“初始化 {% data variables.product.prodname_codeql %}”步骤中引用每种语言： ```yaml jobs: @@ -39,14 +42,14 @@ If an automatic build of code for a compiled language within your project fails, with: languages: {% raw %}${{ matrix.language }}{% endraw %} ``` - - For more information about editing the workflow, see "[Configuring code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." -### No code found during the build + 有关编辑工作流程的更多信息，请参阅“[配置代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)”。 -If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure: +### 构建过程中找不到代码 -1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by updating the list of languages in the `language` matrix. For example, the following configuration will analyze only Go, and JavaScript. +如果工作流程失败，出现错误 `No source code was seen during the build` 或 `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`，则表明 {% data variables.product.prodname_codeql %} 无法监控您的代码。 有几个原因可以解释这种失败： + +1. 自动语言检测发现了受支持的语言，但仓库中没有该语言的可分析代码。 一个典型的例子是，我们的语言检测服务发现了一个与特定的编程语言相关的文件，例如 `.h` 或 `.gyp` 文件，但仓库中没有相应的可执行代码。 要解决此问题，您可以通过更新 `language` 矩阵中的语言列表来手动定义要分析的语言。 例如，以下配置将仅分析 Go 和 JavaScript。 ```yaml strategy: @@ -57,81 +60,82 @@ If your workflow fails with an error `No source code was seen during the build` # ['csharp', 'cpp', 'go', 'java', 'javascript', 'python'] language: ['go', 'javascript'] ``` -For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. -1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually. For more information about specifying build steps, 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)." -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. -1. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are: +更多信息请参阅上面“[编译语言的自动构建失败](#automatic-build-for-a-compiled-language-fails)”中的工作流程摘要。 +1. {% data variables.product.prodname_code_scanning %} 工作流程在分析一种已编译的语言（C、C++、C# 或 Java），但代码尚未编译。 默认情况下，{% data variables.product.prodname_codeql %} 分析工作流程包含 `autobuild` 步骤，但是，此步骤是一个尽力而为的过程，可能无法成功构建您的代码，具体取决于您的特定构建环境。 如果您删除了 `autobuild` 步骤但没有手动添加构建步骤，编译也可能会失败。 有关指定构建步骤的更多信息，请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 +1. 工作流程在分析一种编译语言（C、C++、C# 或 Java），但构建的一部分被缓存以提高性能（最有可能发生在 Gradle 或 Bazel 等构建系统中）。 因为 {% data variables.product.prodname_codeql %} 观察编译器的活动以了解仓库中的数据流，因此 {% data variables.product.prodname_codeql %} 需要进行完整的构建才能执行分析。 +1. 工作流程在分析编译语言（C、C++、C# 或 Java），但工作流程中的 `init` 与 `analyze` 步骤之间不发生编译。 {% data variables.product.prodname_codeql %} 需要这两个步骤之间发生构建以观察编译器的活动并执行分析。 +1. 您的编译代码（使用 C、C ++、C＃ 或 Java）已成功编译，但 {% data variables.product.prodname_codeql %} 无法检测到编译器调用。 最常见的原因是： - * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. 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)." - * Building using a distributed build system external to GitHub Actions, using a daemon process. - * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. + * 在独立于 {% data variables.product.prodname_codeql %} 的容器中运行构建过程。 更多信息请参阅“[在容器中运行 CodeQL 代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container)”。 + * 使用 GitHub Actions 外部的分布式构建系统，使用守护进程构建。 + * {% data variables.product.prodname_codeql %} 不知道您使用的特定编译器。 - For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. - - For example, the following configuration for C# will pass the flag during the first build step. + 对于 .NET Framework 项目以及使用 `dotnet build` 或 `msbuild`（目标 .NET Core 2）的 C# 项目，在构建代码时，您应该在工作流程的 `run` 步骤中指定 `/p:UseSharedCompilation=false`。 .NET Core 3.0 及更高版本不需要 `UseSharedCompilation` 标志。 + + 例如，以下 C# 的配置将在第一个构建步骤中传递标志。 ``` yaml - run: | dotnet build /p:UseSharedCompilation=false ``` - If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}. + 如果您在特定编译器或配置方面遇到其他问题，请联系 {% data variables.contact.contact_support %}。 -For more information about specifying build steps, 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_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 -### Portions of my repository were not analyzed using `autobuild` +### 我的仓库中有部分内容未使用 `autobuild` 进行分析 -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)." +{% data variables.product.prodname_codeql %} `autobuild` 功能使用启发式方法在仓库中构建代码，但有时这种方法会导致对仓库的分析不完整。 例如，当单个仓库中存在多个 `build.sh` 命令时，分析可能不完整，因为 `autobuild` 步骤将只执行其中一个命令。 解决方案是将 `autobuild` 步骤替换为可构建要分析的所有源代码的构建步骤。 更多信息请参阅“[为编译语言配置 {% data variables.product.prodname_codeql %} 工作流程](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)”。 -### 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. +如果使用 {% data variables.product.prodname_codeql %} 分析进行的构建花费的时间太长，则可以尝试几种方法来减少构建时间。 -#### Increase the memory or cores - -If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners. - -#### Use matrix builds to parallelize the analysis - -The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. - -#### Reduce the amount of code being analyzed in a single workflow +#### 增加内存或内核 Analysis time is typically proportional to the amount of code being analyzed. You can reduce the analysis time by reducing the amount of code being analyzed at once, for example, by excluding test code, or breaking analysis into multiple workflows that analyze only a subset of your code at a time. -For compiled languages like Java, C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build only the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." +#### 使用矩阵构建来并行化分析 -For interpreted languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without a specific build, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)." +默认 {% data variables.product.prodname_codeql_workflow %} 使用语言的构建矩阵，这会导致每种语言的分析并行运行。 如果在“初始化 CodeQL”步骤中指定了要直接分析的语言，则将依次进行每种语言的分析。 要加快对多种语言的分析，请修改工作流程以使用矩阵。 更多信息请参阅上面“[编译语言的自动构建失败](#automatic-build-for-a-compiled-language-fails)”中的工作流程摘要。 -If you split your analysis into multiple workflows as described above, we still recommend that you have at least one workflow which runs on a `schedule` which analyzes all of the code in your repository. Because {% data variables.product.prodname_codeql %} analyzes data flows between components, some complex security behaviors may only be detected on a complete build. +#### 减少单个工作流程中要分析的代码量 -#### Run only during a `schedule` event +分析时间通常与要分析的代码量成正比。 您可以通过减少一次分析的代码量来缩短分析时间，例如，排除测试代码，或将分析分解为多个工作流程，这些工作流程一次只分析一部分代码。 -If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)." +对于 Java、C、C++ 和 C# 等编译语言，{% data variables.product.prodname_codeql %} 分析在工作流程运行过程中构建的所有代码。 要限制要分析的代码量，请通过在 `run` 块中指定自己的构建步骤，仅构建您要分析的代码。 您可以通过对 `pull_request` 和 `push` 事件使用 `paths` 或 `paths-ignore` 过滤器来组合指定自己的构建步骤，以确保工作流程仅在特定代码发生更改时运行。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)”。 + +对于 Go、JavaScript、Python 和 TypeScript 等解释性语言，{% data variables.product.prodname_codeql %} 无需特定构建即可进行分析，您可以指定额外配置选项以限制要分析的代码量。 更多信息请参阅“[指定要扫描的目录](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)”。 + +如果您按上文所述将分析拆分为多个工作流程，我们仍然建议您至少保留一个按 `schedule` 运行的工作流程分析仓库中的所有代码。 因为 {% data variables.product.prodname_codeql %} 分析组件之间的数据流量，所以某些复杂的安全行为只能在完整的构建中检测到。 + +#### 仅在 `schedule` 事件期间运行 + +如果分析速度仍然太慢，无法在 `push` 或 `pull_request` 事件期间运行，则您可能需要设置仅在 `schedule` 事件期间运行。 更多信息请参阅“[事件](/actions/learn-github-actions/introduction-to-github-actions#events)”。 {% if currentVersion == "free-pro-team@latest" %} -### Results differ between analysis platforms +### 分析平台之间的结果差异 -If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows. +如果您分析的是使用 Python 编写的代码，根据您是在 Linux、macOS 还是 Windows 上运行 {% data variables.product.prodname_codeql_workflow %}，可能会看到不同的结果。 -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)." +在使用 Linux 的 GitHub 托管运行器上，{% data variables.product.prodname_codeql_workflow %} 会尝试安装和分析 Python 依赖项，这可能导致更多结果。 要禁用自动安装，请将 `setup-python-dependencies: false` 添加到工作流程的“初始化 CodeQL”步骤。 有关配置 Python 依赖项分析的更多信息，请参阅“[分析 Python 依赖项](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)”。 {% endif %} -### Error: "Server 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 %}. +如果 {% data variables.product.prodname_code_scanning %} 的工作流程运行因服务器错误而失败，请尝试再次运行工作流程。 如果问题仍然存在，请联系 {% data variables.contact.contact_support %}。 -### Error: "Out of disk" or "Out of memory" +### 错误：“Out of disk（磁盘空间不足）”或“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 %} +{% data variables.product.prodname_codeql %} 可能会耗尽运行器上的磁盘或内存。 +{% if currentVersion == "free-pro-team@latest" %}如果您在托管的 {% data variables.product.prodname_actions %} 运行器上遇到此问题，请联系 {% data variables.contact.contact_support %}，以便我们调查。 +By default, {% data variables.product.prodname_codeql %} performs analysis of each language sequentially, which can impact performance, especially for repositories with more than one language. You can speed analysis up by using a build matrix that splits the analysis by language. For more information, see "[Configuring a build matrix](/actions/configuring-and-managing-workflows/configuring-a-workflow#configuring-a-build-matrix)." -### Warning: "git checkout HEAD^2 is no longer necessary" +### 警告：“git checkout HEAD^2 is no longer necessary（不再需要 Git 检出头^2）” -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: +如果您使用的是旧 {% data variables.product.prodname_codeql %} 工作流程，您可能会在输出中收到来自“初始化 {% data variables.product.prodname_codeql %}”操作的以下警告： ``` Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer @@ -139,7 +143,7 @@ necessary. Please remove this step as Code Scanning recommends analyzing the mer 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. +通过从 {% data variables.product.prodname_codeql %} 工作流程中删除以下行来修复此问题。 这些行包含在 {% data variables.product.prodname_codeql %} 工作流程初始版本中 `Analyze` 作业的 `steps` 部分。 ```yaml with: @@ -151,9 +155,9 @@ Fix this by removing the following lines from the {% data variables.product.prod # 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: +修订后的工作流程 `steps` 部分将如下所示： ```yaml steps: @@ -167,4 +171,4 @@ The revised `steps` section of the workflow will look like this: ... ``` -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 +有关编辑 {% data variables.product.prodname_codeql %} 工作流程文件的更多信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)”。 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 index 87a9feff51..fc3a8b45b7 100644 --- 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 @@ -38,7 +38,7 @@ topics: {% data variables.product.product_location %} 启用 {% data variables.product.prodname_advanced_security %}，您才能使用这些功能。 更多信息请参阅“[配置高级安全功能](/admin/configuration/configuring-advanced-security-features)”。 {% endif %} -设置系统后，您可以在组织或仓库级别启用和禁用这些功能。 更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 +设置系统后，您可以在组织或仓库级别启用和禁用这些功能。 For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)." {% endif %} @@ -47,7 +47,7 @@ topics: 对于 {% data variables.product.prodname_dotcom_the_website %} 上的公共仓库，这些功能是永久性的，仅当您更改项目的可见性使代码不再公开时才会禁用。 -对于其他仓库，一旦您拥有企业帐户的许可，就可以在组织或仓库级别启用和禁用这些功能。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} +对于其他仓库，一旦您拥有企业帐户的许可，就可以在组织或仓库级别启用和禁用这些功能。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/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)."{% endif %} {% endif %} 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 1695dd5c2c..20efbc8a1f 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 @@ -92,7 +92,7 @@ topics: - {% data variables.contact.enterprise_support %}. 更多信息请参阅“{% data variables.product.prodname_ghe_cloud %} 支持”和“{% data variables.product.prodname_ghe_cloud %} 附录”。 - 50,000 {% data variables.product.prodname_actions %} 分钟 - 50GB {% data variables.product.prodname_registry %} 存储空间 -- {% data variables.product.prodname_pages %} 站点的访问控制。 更多信息请参阅“更改 {% data variables.product.prodname_pages %} 站点的可见性” +- {% data variables.product.prodname_pages %} 站点的访问控制。 更多信息请参阅“更改 {% data variables.product.prodname_pages %} 站点的可见性” - 99.9% 月持续运行时间的服务等级协议 - 通过企业帐户集中管理多个 {% data variables.product.prodname_dotcom_the_website %} 组织的策略和帐单的选项。 更多信息请参阅“关于企业帐户”。 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 02148a2dad..2621099678 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 @@ -52,6 +52,7 @@ versions: | control z 或 command z | 撤消 | | control y 或 command y | 重做 | | cmd + shift + p | 在 **Edit file（编辑文件）** 与 **Preview changes（预览更改）**选项卡之间切换 | +| control s 或 command s | 填写提交消息 | 有关更多键盘快捷键，请参阅 [CodeMirror 文档](https://codemirror.net/doc/manual.html#commands)。 diff --git a/translations/zh-CN/content/github/index.md b/translations/zh-CN/content/github/index.md index eeda05fdad..8e048d6e56 100644 --- a/translations/zh-CN/content/github/index.md +++ b/translations/zh-CN/content/github/index.md @@ -23,7 +23,7 @@ versions: {% link_in_list /managing-subscriptions-and-notifications-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 %} @@ -57,7 +57,6 @@ versions: {% 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 %} diff --git a/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md b/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md index b04c985005..5086f7180e 100644 --- a/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md +++ b/translations/zh-CN/content/github/managing-large-files/conditions-for-large-files.md @@ -1,6 +1,6 @@ --- -title: Conditions for large files -intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories, and will block a push to a repository if the files are larger than the maximum file limit.' +title: 大文件的条件 +intro: '{% data variables.product.product_name %} 限制了仓库允许的文件大小，如果文件大于最大文件限制，将会阻止推送到仓库。' redirect_from: - /articles/conditions-for-large-files versions: @@ -11,10 +11,10 @@ versions: {% data reusables.large_files.use_lfs_tip %} -### Warning for files larger than {% data variables.large_files.warning_size %} +### 文件大于 {% data variables.large_files.warning_size %} 时的警告 -If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](/github/managing-large-files/removing-files-from-a-repositorys-history)." +如果尝试添加或更新大于 {% data variables.large_files.warning_size %} 的文件，您将从 Git 收到警告。 更改仍将成功推送到仓库，但您可以考虑删除提交，以尽量减少对性能的影响。 更多信息请参阅“[从仓库的历史记录中删除文件](/github/managing-large-files/removing-files-from-a-repositorys-history)”。 -### Blocked pushes for large files +### 阻止大文件的推送 -{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %} +{% if enterpriseServersions contained currentversion or currentversion == "github-ae@latest" %}默认情况下，{% endif %}{% data variables.product.product_name %} 会阻止超过 {% data variables.large_files.max_github_size %} 的推送。 {% if enterpriseServersions contained currentversion or currentversion == "github-ae@latest" %}但站点管理员可为 {% data variables.product.product_location %} 配置不同的限制。 更多信息请参阅“[设置 Git 推送限制](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)”。{% endif %} diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 67f9613edb..f25dfb1bf4 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -1,90 +1,99 @@ --- -title: About alerts for vulnerable dependencies -intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.' -redirect_from: - - /articles/about-security-alerts-for-vulnerable-dependencies - - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies +title: 关于易受攻击的依赖项的警报 +intro: '当我们检测到影响仓库的漏洞时，{% data variables.product.product_name %} 将会发送 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}。' versions: - free-pro-team: '*' - enterprise-server: '*' + enterprise-server: '<=2.22' +topics: + - 安全 --- -### About vulnerable dependencies +### 关于易受攻击的依赖项 {% data reusables.repositories.a-vulnerability-is %} -When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it. +当代码依赖于具有安全漏洞的包时，这种易受攻击的依赖项可能会导致项目或使用它的人遇到一系列问题。 -### Detection of vulnerable dependencies +### 有漏洞依赖项的检测 - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} 在以下情况下检测有漏洞的依赖项并发送 {% data variables.product.prodname_dependabot_alerts %}{% else %}{% data variables.product.product_name %}检测有漏洞的依赖项并发送安全警报{% endif %}： {% if currentVersion == "free-pro-team@latest" %} -- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)." -- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %} -- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}."{% endif %} -- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +- 新漏洞添加到 {% data variables.product.prodname_advisory_database %}。 更多信息请参阅“[浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)”。{% else %} +- 新公告数据每小时从 {% data variables.product.prodname_dotcom_the_website %} 同步到 {% data variables.product.prodname_ghe_server %}。 有关公告数据的更多信息，请参阅“浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞”。{% endif %} +- 仓库的依赖关系图发生更改。 例如，当参与者推送提交以更改所依赖的包或版本时{% if currentVersion == "free-pro-team@latest" %}，或者当某个依赖项的代码发生更改时{% endif %}。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 {% data reusables.repositories.dependency-review %} -For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +有关 {% data variables.product.product_name %} 可以检测到漏洞和依赖项的生态系统列表，请参阅“[支持的包生态系统](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 {% note %} -**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use. +**注：**保持清单和锁定文件为最新状态非常重要。 如果依赖关系图不能准确反映您当前的依赖项和版本，则可能错过有关您使用的有漏洞依赖项的警报。 您还可以收到不再使用的依赖项的警报。 {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %} -### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies +### 有漏洞依赖项的 {% data variables.product.prodname_dependabot %} 警报 {% else %} -### Security alerts for vulnerable dependencies +### 对有漏洞的依赖项发出安全警报 {% endif %} {% data reusables.repositories.enable-security-alerts %} -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} 默认会检测_公共_仓库中有漏洞的依赖项并生成 {% data variables.product.prodname_dependabot_alerts %}。 私有仓库的所有者或具有管理员权限的人员可以通过为其仓库启用依赖关系图和 {% data variables.product.prodname_dependabot_alerts %} 来启用 {% data variables.product.prodname_dependabot_alerts %}。 -You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +您也可以为用户帐户或组织拥有的所有仓库启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 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](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)." -{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." +For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)." + +{% data variables.product.product_name %} 将立即开始生成依赖关系图，并在发现任何有漏洞的依赖项后立即生成警报。 依赖关系图通常在几分钟之内填充，但对于依赖项很多的仓库，可能需要更长时间。 更多信息请参阅“[管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)”。 {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +当 +{% data variables.product.product_name %} 发现易受攻击的依赖项时，我们会生成 {% data variables.product.prodname_dependabot %} 警报，并显示在仓库的 Security（安全）选项卡上。 该警报包括指向项目中受影响的文件的链接，以及有关修复的版本的信息。 {% data variables.product.product_name %} 还根据受影响仓库的管理员的通知首选项向他们通知新的警报。 更多信息请参阅“[为易受攻击的依赖项配置通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)”。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +对于 +已启用 {% data variables.product.prodname_dependabot_security_updates %} 的仓库，警报中还包含一个拉取请求链接，用于将清单或锁定文件更新到能解决该漏洞的最小版本。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. +当 +{% data variables.product.product_name %} 发现有漏洞的依赖项时， 我们会发送安全警报给受影响仓库的维护员，其中包含该漏洞的详细说明、项目中受影响文件的链接以及有关修复版本的信息。 {% endif %} {% warning %} -**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary. +**注**：{% data variables.product.product_name %} 的安全功能并不要求捕获所有漏洞。 虽然我们一直在努力更新漏洞数据库，生成包含最新信息的警报，但我们无法捕获一切或在保证的时间范围内向您警示已知的漏洞。 这些功能不是要替代人工检查每个依赖项的潜在漏洞或任何其他问题，并且我们建议在必要时咨询安全服务或全面检查漏洞。 {% endwarning %} -### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts +### 访问 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报 -You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +您可以在{% if currentVersion == "free-pro-team@latest" %} 仓库的 Security（安全）选项卡或{% endif %} 仓库的依赖关系图{% if currentVersion == "free-pro-team@latest" %} 中查看影响特定项目的所有警报。更多信息请参阅“[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)”。{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +默认情况下，我们会通知受影响仓库中具有管理权限的人有新的 +{% data variables.product.prodname_dependabot_alerts %}。{% endif %} {% if currentversion == "free proteam@latest" %}{% data variables.product.product_name %} 永远不公开披露任何仓库中已经发现的漏洞。 您也可以将 {% data variables.product.prodname_dependabot_alerts %} 设为对操作您拥有或具有管理员权限的仓库的其他人或团队可见。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. +默认情况下，我们会向具有受影响仓库管理员权限的人员发送安全警报。 +{% data variables.product.product_name %} 从不公开披露在任何仓库中发现的漏洞。 {% endif %} -{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServersions contains currentversion and currentver_lt "enterprise-server@2 1" %} 更多信息请参阅“[选择通知的递送方式](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)”。{% endif %}{% if currentversion == "free-proteam@latest" or currentversion ver_gt "enterprise-server@2. 0" %} 解更多信息请参阅“[配置漏洞依赖项的通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)”。{% endif %} {% if currentVersion == "free-pro-team@latest" %} -### Further reading +您也可以 +查看与 {% data variables.product.prodname_advisory_database %} 中的特定漏洞对应的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[浏览 {% data variables.product.prodname_advisory_database %} 中的安全漏洞](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)”。 +{% endif %} -- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +### 延伸阅读 + +- "[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" +- "[查看和更新仓库中的漏洞依赖项](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[了解 {% data variables.product.product_name %} 如何使用和保护数据](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} 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 b1097a9342..3a24aa3f5f 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 @@ -1,56 +1,59 @@ --- -title: Configuring notifications for vulnerable dependencies -shortTitle: Configuring notifications -intro: 'Optimize how you receive notifications about {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts.' +title: 配置有漏洞依赖项的通知 +shortTitle: 配置通知 +intro: '优化您如何接收有关 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报的通知。' versions: - free-pro-team: '*' - enterprise-server: '>=2.21' + enterprise-server: '>=2.21 <=2.22' +topics: + - 安全 --- -### About notifications for vulnerable dependencies +### 关于有漏洞依赖项的通知 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. -{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}当 {% data variables.product.prodname_dependabot %} 在您的仓库中检测到有漏洞依赖项时，我们将生成 {% data variables.product.prodname_dependabot %} 警报，并将其显示在仓库的“Security（安全）”选项卡中。 {% data variables.product.product_name %} 根据通知首选项将新警报通知受影响仓库的维护员。{% else %}When {% data variables.product.product_name %} 在仓库中检测到有漏洞依赖项时，它将发送安全警报。{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} 在所有公共仓库中默认启用。 对于 {% data variables.product.prodname_dependabot_alerts %}，默认情况下，您将通过电子邮件收到按特定漏洞分组的 {% data variables.product.prodname_dependabot_alerts %}。 +{% endif %} -{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created 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#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." +{% if currentVersion == "free-pro-team@latest" %}如果您是组织所有者，您可以对组织中的所有仓库一键启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 您也可以设置是否对新建的仓库启用或禁用有漏洞依赖项检测。 For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/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" %} -Your site administrator needs to enable security alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use the feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +您的站点管理员需要对 +{% data variables.product.product_location %} 启用有漏洞依赖项安全警报，您才能使用该功能。 更多信息请参阅“[为 {% 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" %} -By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %} +默认情况下，如果站点管理员配置了使用电子邮件接收企业通知，您将 +通过电子邮件收到{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}。{% endif %} -{% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if currentVersion ver_gt "enterprise-server@2.21" %}站点管理员还可以启用无通知 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上的有漏洞依赖项启用 {% data variables.product.prodname_dependabot_alerts %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。{% endif %} -{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if currentVersion ver_lt "enterprise-server@2.22" %}站点管理员还可以启用无通知安全警报。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。 -### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} +### 为 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}配置通知 -You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." +您可以从每个页面顶部显示的管理通知下拉菜单 {% octicon "bell" aria-label="The notifications bell" %} 为您自己或您的组织配置通知设置。 更多信息请参阅“[配置通知](/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" %} - ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png) + ![{% data variables.product.prodname_dependabot_alerts %} 选项](/assets/images/help/notifications-v2/dependabot-alerts-options.png) {% else %} - ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png) + ![安全警报选项](/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. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)." +**注：** 您可以过滤 {% data variables.product.company_short %} 上的通知以显示{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %} 安全{% endif %}警报。 更多信息请参阅“[从收件箱管理通知](/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 %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}”。{% endif %} -### How to reduce the noise from notifications for vulnerable dependencies +### 如何减少有漏洞依赖项通知的干扰 -If you are concerned about receiving too many notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} enabled. You can still navigate to see your {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} in your repository's Security tab.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} +如果您担心会收到太多 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}通知，我们建议您在保持启用{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}的情况下，选择接收每周电子邮件摘要或关闭通知。 您仍然可以导航到仓库的“Security（安全）”选项卡以查看 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %}。{% if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[查看和更新仓库中的有漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)”。{% endif %} -### Further reading +### 延伸阅读 -- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" -- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)" +- "[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" +- “[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)”。 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 da5677a50f..651009f9ca 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 @@ -66,7 +66,7 @@ topics: ### 关于参与和查看通知 -关注仓库，意味着订阅该仓库中的活动更新。 同样，关注特定团队的讨论，意味着订阅该团队页面上的所有对话更新。 更多信息请参阅“[关于团队讨论](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)”。 +关注仓库，意味着订阅该仓库中的活动更新。 同样，关注特定团队的讨论，意味着订阅该团队页面上的所有对话更新。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 要查看您关注的仓库，请参阅[关注页面](https://github.com/watching)。 更多信息请参阅“[在 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" %} @@ -78,7 +78,7 @@ topics: #### 关于自定义通知 {% data reusables.notifications-v2.custom-notifications-beta %} 您可以自定义仓库的通知，例如，您可以选择仅在仓库中发生一类或多类事件（议题、拉取请求、发布、讨论）的更新时收到通知，或者忽略仓库的所有通知。 -{% endif %} 更多信息请参阅“[查看订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)”。 +{% endif %} 更多信息请参阅下面的“[配置单个仓库的关注设置](#configuring-your-watch-settings-for-an-individual-repository)”。 #### 参与对话 每当您在对话中发表评论或有人 @提及您的用户名时，您都在_参与_对话。 默认情况下，当您参与对话时，会自动订阅该对话。 您可以通过单击议题或拉取请求上的 **Unsubscribe（取消订阅）**或通过通知收件箱中的 **Unsubscribe（取消订阅）**选项，手动取消订阅已参与的对话。 @@ -248,8 +248,8 @@ topics: 1. 在底部菜单中，单击 **Profile（个人资料）**。 2. 要查看设置，请点击 {% octicon "gear" aria-label="The Gear icon" %}。 -3. 要更新通知设置，请点击 **Notifications（通知）** ，然后使用切换来启用或禁用首选类型的推送通知。 -4. （可选）要安排 {% data variables.product.prodname_mobile %} 何时向移动设备发送推送通知，请点击 **Receive Notifications（接收通知）**，使用 **Custom working hours（自定义工作时间）** 切换，然后选择何时接收推送通知。 +3. 要更新通知设置，请点击 **Configure Notifications（配置通知）** ，然后使用切换来启用或禁用首选类型的推送通知。 +4. （可选）要安排 {% data variables.product.prodname_mobile %} 何时向移动设备发送推送通知，请点击 **Working Hours（工作时间）**，使用 **Custom working hours（自定义工作时间）** 切换，然后选择何时接收推送通知。 ### 使用 {% data variables.product.prodname_mobile %} 配置个别仓库的关注设置 @@ -258,6 +258,5 @@ topics: 1. 在 {% data variables.product.prodname_mobile %} 上，导航到仓库的主页面。 2. 点击 **Watch（关注）**。 ![{% data variables.product.prodname_mobile %} 上的关注按钮](/assets/images/help/notifications-v2/mobile-watch-button.png) 3. 要选择接收通知的活动，请点击首选的关注设置。 ![{% data variables.product.prodname_mobile %} 中的关注设置下拉菜单](/assets/images/help/notifications-v2/mobile-watch-settings.png) -{% data reusables.notifications-v2.custom-notifications-beta %} {% endif %} diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md index 2680817b44..ecf4f621c1 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions.md @@ -38,7 +38,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**提示：**您可以在[关注页面](https://github.com/watching)或 {% data variables.product.prodname_dotcom_the_website %} 上的任何仓库页面，使用 **Watch/Unwatch（关注/取消关注）**下拉列表中的 **Custom（自定义）**选项选择要通知的事件类型。 更多信息请参阅下面的“[配置单个仓库的关注设置](#configuring-your-watch-settings-for-an-individual-repository)”。 +**提示：**您可以在[关注页面](https://github.com/watching)或 {% data variables.product.prodname_dotcom_the_website %} 上的任何仓库页面，使用 **Watch/Unwatch（关注/取消关注）**下拉列表中的 **Custom（自定义）**选项选择要通知的事件类型。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)”。 {% endtip %} {% endif %} 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 a97eca67f3..254c32a1b9 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 @@ -8,6 +8,8 @@ redirect_from: - /articles/discounted-subscriptions-for-github-accounts versions: free-pro-team: '*' +topics: + - 计费，帐单 --- {% tip %} @@ -18,11 +20,11 @@ versions: ### 个人帐户折扣 -拥有 {% 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_free_user %} 的学生和教职工除了可使用无限公共和私有仓库外，经验证的学生还可以申请 {% data variables.product.prodname_student_pack %}，以便从 {% data variables.product.prodname_dotcom %} 合作伙伴处获得其他好处。 更多信息请参阅“[申请学生开发包](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)”。 ### 学校和大学折扣 -经验证的教师可出于教学和学术研究目的申请 {% 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/)。 +经验证的教师可出于教学和学术研究目的申请 {% data variables.product.prodname_team %}。 更多信息请参阅“[在课堂上和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-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 23dadae170..4f5d7096da 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 @@ -19,14 +19,14 @@ topics: {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### 取消赞助 {% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} +{% data reusables.user_settings.billing_plans %} {% data reusables.sponsors.billing-switcher %} -{% data reusables.user_settings.subscriptions-tab %} 3. 在“{% data variables.product.prodname_sponsors %}”下的被赞助开源贡献者右侧，单击被赞助帐户旁边的 {% octicon "triangle-down" aria-label="The down triangle octicon" %}，然后单击 **Cancel sponsorship（取消赞助）**。 ![取消赞助按钮](/assets/images/help/billing/edit-sponsor-billing.png) 4. 审查有关取消赞助的信息，然后单击 **OK（确定）**。 ![取消确认框](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md index 113b3a9cfa..6da244827d 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon.md @@ -14,6 +14,8 @@ topics: 如果您在应用优惠券之前为帐户付款，则 {% data variables.product.product_name %} 无法发起退款。 如果您将优惠券应用到错误的帐户，我们也无法转移已兑换的优惠券或为您提供一张新的优惠券。 在兑换优惠券之前，请确认是否将优惠券应用到正确的帐户。 +{% data reusables.dotcom_billing.coupon-expires %} + 您无法将优惠券应用到 {% data variables.product.prodname_marketplace %} 应用程序的付费计划。 ### 兑换个人帐户的优惠券 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md index 2dd7c13cd5..30ed01008d 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method.md @@ -15,6 +15,8 @@ topics: 如果您使用优惠券为 {% data variables.product.product_name %} 订阅付款，并且不会将付款方式用于 {% data variables.product.product_name %} 上的任何[其他付费功能或产品](/articles/about-billing-on-github)，则可以删除信用卡或 PayPal 信息。 +{% data reusables.dotcom_billing.coupon-expires %} + {% tip %} **提示：**如果您[将帐户降级为免费产品](/articles/downgrading-your-github-subscription)并且没有任何其他付费功能或产品的订阅，我们将自动删除您的付款信息。 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 cab7002d4a..c14af1d5e9 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 @@ -19,5 +19,6 @@ topics: {% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-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 89d0d6cb9c..b26f30fd06 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 @@ -59,7 +59,7 @@ topics: #### 使用 {% data variables.product.prodname_ghe_cloud %} 的组织的后续步骤 -如果您已将组织升级到 {% data variables.product.prodname_ghe_cloud %}，便可设置组织的身份和访问管理。 更多信息请参阅“[管理组织的 SAML 单点登录](/articles/managing-saml-single-sign-on-for-your-organization)”。 +如果您已将组织升级到 {% data variables.product.prodname_ghe_cloud %}，便可设置组织的身份和访问管理。 更多信息请参阅“[管理组织的 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization)”。 如果想要将企业帐户与 {% data variables.product.prodname_ghe_cloud %} 一起使用，请联系 {% data variables.contact.contact_enterprise_sales %}。 更多信息请参阅“[关于企业帐户](/articles/about-enterprise-accounts)”。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md index c788d7b899..2994fe4835 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage.md @@ -20,5 +20,5 @@ versions: “{% data variables.product.prodname_GH_advanced_security %}”部分显示了当前使用详情。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) 如果您的席位用完了，该部分将为红色。 您应该减少您对 {% data variables.product.prodname_GH_advanced_security %} 的使用，或者购买更多席位。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 企业许可证的许可](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security#getting-the-most-out-of-your-github-advanced-security-enterprise-license)”。 ![企业许可设置中的 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. （可选）要查看每个组织的使用详情，请在左侧边栏中单击 **Billing（计费）**。 ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) 在“{% data variables.product.prodname_GH_advanced_security %}”部分，您可以查看每个组织的提交者和唯一提交者数量。 ![企业计费设置中的 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/billing/ghas-orgs-list-enterprise.png) 5. （可选）单击您是所有者的组织的名称，以显示组织的安全和分析设置。 ![在企业帐单设置的 {% data variables.product.prodname_GH_advanced_security %} 部分中拥有的组织](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) -6. 在“Security & analysis（安全性和分析）”设置页面上，滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分以查看此组织的仓库使用明细。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 更多信息请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”。 +6. 在“Security & analysis（安全性和分析）”设置页面上，滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分以查看此组织的仓库使用明细。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 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 index eb9345110a..417e0eefa3 100644 --- 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 @@ -11,7 +11,7 @@ topics: ### 关于企业帐户的 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)”。 +{% data reusables.saml.dotcom-saml-explanation %}更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”。 {% data reusables.saml.about-saml-enterprise-accounts %} 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 89014380be..ab58c84103 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 @@ -49,7 +49,7 @@ topics: {% data reusables.identity-and-permissions.ip-allow-lists-enable %} -您还可以为单个组织配置允许的 IP 地址。 更多信息请参阅“[管理组织允许的 IP 地址](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)”。 +您还可以为单个组织配置允许的 IP 地址。 更多信息请参阅“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)”。 #### 添加允许的 IP 地址 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md index 924f8d7a19..cf8507b427 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account.md @@ -15,7 +15,7 @@ topics: ### 执行团队讨论策略 -在企业帐户拥有的所有组织中，可以启用或禁用团队讨论，或允许所有者在组织级别管理设置。 更多信息请参阅“[关于团队讨论](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)”。 +在企业帐户拥有的所有组织中，可以启用或禁用团队讨论，或允许所有者在组织级别管理设置。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions/)”。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 cb6ec2c195..e973667abd 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 @@ -39,7 +39,7 @@ topics: 虽然不是必需的，但我们建议组织所有者将邀请发送到 {% data variables.product.prodname_vs %} 订阅者的用户主名 (UPN) 使用的同一电子邮件地址。 当 {% data variables.product.product_name %} 上的电子邮件地址与订阅者的 UPN 匹配时，您可以确保组织的其他成员不会索要该订阅者的许可证。 -更多信息请参阅“[邀请用户加入组织](/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)”。 +更多信息请参阅“[邀请用户加入组织](/organizations/managing-membership-in-your-organization/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)”。 ### 查看 {% data variables.product.prodname_enterprise %} 许可 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 index 449cca7dcf..7b5b369194 100644 --- 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 @@ -19,7 +19,7 @@ topics: {% data reusables.identity-and-permissions.team-sync-disable %} -您也可以配置和管理单个组织的团队同步。 更多信息请参阅“[管理组织的团队同步](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)”。 +您也可以配置和管理单个组织的团队同步。 更多信息请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”。 ### 基本要求 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md index cc1f7fb592..71f3bb3d16 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains.md @@ -11,7 +11,7 @@ topics: ### 关于企业帐户的电子邮件限制 -当您将电子邮件通知限制为已验证域时，企业成员只能使用与已验证域关联的电子邮件地址来接收有关企业帐户所拥有组织中活动的电子邮件通知。 可以从企业帐户继承域，也可以为特定组织配置域。 有关组织电子邮件限制的更多信息，请参阅“[将电子邮件通知限制为已批准的域](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)”。 +当您将电子邮件通知限制为已验证域时，企业成员只能使用与已验证域关联的电子邮件地址来接收有关企业帐户所拥有组织中活动的电子邮件通知。 可以从企业帐户继承域，也可以为特定组织配置域。 有关组织电子邮件限制的更多信息，请参阅“[将电子邮件通知限制为已批准的域](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)”。 如果对企业帐户启用了电子邮件限制，则组织所有者无法禁用该企业帐户拥有的任何组织的电子邮件限制。 如果发生更改导致某个组织没有已验证的域（从拥有该组织的企业帐户继承的域或特定组织的域），则该组织的电子邮件限制将被禁用。 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 a6d7bee5c5..0074c9cb3f 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 @@ -1,6 +1,6 @@ --- -title: Roles in an enterprise -intro: 'Everyone in an enterprise is a member of the enterprise. To control access to your enterprise''s settings and data, you can assign different roles to members of your enterprise.' +title: 企业中的角色 +intro: '企业中的每个人都是企业的成员。 要控制对企业的设置和数据的访问权限，您可以为企业成员分配不同的角色。' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account @@ -10,52 +10,54 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - 企业 --- -### About roles in an enterprise +### 关于企业中的角色 -Everyone in an enterprise is a member of the enterprise. You can also assign administrative roles to members of your enterprise. Each administrator role maps to business functions and provides permissions to do specific tasks within the enterprise. +企业中的每个人都是企业的成员。 您还可以为企业成员分配管理角色。 每个管理员角色都映射到业务职能，并提供在企业中执行特定任务的权限。 {% data reusables.enterprise-accounts.enterprise-administrators %} -For more information about adding people to your enterprise, see "{% if currentVersion == "free-pro-team@latest" %}[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Authentication](/admin/authentication){% endif %}". +有关将人员添加到企业的更多信息，请参阅“{% if currentVersion == "free-pro-team@latest" %}[邀请人员管理企业](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[身份验证](/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 %} +企业所有者可以完全控制企业，并可以采取所有操作，包括： +- 管理管理员 +- {% if currentVersion == "free-pro-team@latest" %}添加和删除{% elsif currentVersion == "github-ae@latest" %}管理{% endif %}{% elsif currentVersion == "github-ae@latest" %}{% endif %}企业中的组织{% if currentVersion == "free-pro-team@latest" %}。 +- 管理企业设置 +- 在组织范围内强制实施政策 +{% if currentVersion == "free-pro-team@latest" %}- 管理帐单设置{% endif %} -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. +企业所有者仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 {% if currentVersion == "free-pro-team@latest" %}企业所有者必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。{% endif %} 作为最佳实践，我们建议只将少数人设为公司的企业所有者，以降低业务风险。 -### 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 %}. +您的企业所拥有组织的成员也会自动成为企业的成员。 成员可以在组织中进行协作，也可以是组织所有者，但成员无法访问或配置企业设置{% if currentVersion == "free-pro-team@latest" %}，包括计费设置{% 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. 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)." +企业中的人员可能对您的企业拥有的各种组织以及这些组织中的仓库具有不同级别的访问权限。 您可以查看每个人具有访问权限的资源。 更多信息请参阅“[查看企业中的人员](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise)”。 -For more information about organization-level permissions, see "[Permission levels for an organization](/articles/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. For more information about outside collaborators, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization#outside-collaborators)." +对组织所拥有仓库具有外部协作者访问权限的人员也会在企业的 People（人员）选项卡中列出，但他们不是企业成员，也没有对企业的任何访问权限。 有关外部协作者的更多信息，请参阅“[组织的权限级别](/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: -- 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 +帐单管理员只能访问企业的帐单设置。 企业的帐单管理员可以： +- 查看和管理用户许可证、{% data variables.large_files.product_name_short %} 包以及其他计费设置 +- 查看帐单管理员列表 +- 添加或删除其他帐单管理员 -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 %}. +帐单管理员仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 帐单管理员无权访问企业中的组织或仓库，也无法添加或删除企业所有者。 帐单管理员必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。 -### Further reading +### 延伸阅读 -- "[About enterprise accounts](/articles/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 862606d7fc..d4c7f43b09 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 @@ -14,7 +14,7 @@ topics: ### 关于域验证 -您可以通过验证域，确认企业控制的企业帐户所拥有的任何组织资料中列出的网站和电子邮件地址。 企业帐户的已验证域适用于企业帐户拥有的每个组织，组织所有者可以验证其组织的其他域。 更多信息请参阅“[验证组织的域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)”。 +您可以通过验证域，确认企业控制的企业帐户所拥有的任何组织资料中列出的网站和电子邮件地址。 企业帐户的已验证域适用于企业帐户拥有的每个组织，组织所有者可以验证其组织的其他域。 更多信息请参阅“[验证组织的域](/organizations/managing-organization-settings/verifying-your-organizations-domain)”。 验证企业帐户域的所有权后，每个在其资料中列出域的组织资料中将显示"已验证"徽章。 {% data reusables.organizations.verified-domains-details %} @@ -22,7 +22,7 @@ topics: 验证企业帐户的域后，您可以将企业帐户拥有的所有组织的电子邮件通知限制为已验证域。 更多信息请参阅“[将企业帐户的电子邮件通知限制为已批准的域](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)”。 -即使您不限制企业帐户的电子邮件通知，但如果组织所有者限制了组织的电子邮件通知，则组织成员除了能够接收来自组织的任何已验证域的通知之外，还能够接收来自企业帐户的任何已验证域的通知。 有关限制组织通知的更多信息，请参阅“[将电子邮件通知限制为已批准的域](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)”。 +即使您不限制企业帐户的电子邮件通知，但如果组织所有者限制了组织的电子邮件通知，则组织成员除了能够接收来自组织的任何已验证域的通知之外，还能够接收来自企业帐户的任何已验证域的通知。 有关限制组织通知的更多信息，请参阅“[将电子邮件通知限制为已批准的域](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)”。 ### 验证企业帐户的域 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 83bcae98bd..dd64b4bd81 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 @@ -53,4 +53,4 @@ topics: ### 延伸阅读 -- "[查看和管理成员对组织的 SAML 访问](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" +- "[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" 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 afbfe3a772..888b311418 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 @@ -14,7 +14,7 @@ topics: 您可以选择为组织添加说明、地点、网站和电子邮件地址，以及将重要仓库固定于页面顶部。 -{% if currentVersion == "free-pro-team@latest" %}要确认组织的身份并在组织资料页面显示“已验证”徽章，必须使用 {% 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 %} 验证组织的域。 更多信息请参阅“[验证组织的域](/organizations/managing-organization-settings/verifying-your-organizations-domain)”。 ![验证过的组织资料页面示例](/assets/images/help/profile/org_profile_verified.png) {% else %} @@ -23,4 +23,4 @@ topics: ### 延伸阅读 -- "[关于组织](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" +- "[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)" 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 9eef937b50..44d6d0931f 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 @@ -25,7 +25,7 @@ topics: - 在仓库的默认分支中 - 在 `gh-pages` 分支中（对于包含项目站点的仓库） -有关项目网站的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +有关项目网站的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 此外，必须**至少**满足以下条件之一： - 您是仓库中的协作者，或者是拥有该仓库的组织的成员。 @@ -66,7 +66,7 @@ Subject: [PATCH] updated index for better welcome message #### 提交没有在默认或 `gh-pages` 分支中进行 -仅发生在默认分支或 `gh-pages` 分支（对于包含项目站点的仓库）中的提交才会计入。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +仅发生在默认分支或 `gh-pages` 分支（对于包含项目站点的仓库）中的提交才会计入。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 如果您的提交位于非默认或非 `gh-pages` 分支中，并且您希望将其计入您的贡献，则需要执行以下操作之一： - [打开拉取请求](/articles/creating-a-pull-request)以将您的更改合并到默认分支或 `gh-pages` 分支。 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 200ca9d664..f145600a7b 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 @@ -52,7 +52,7 @@ topics: {% tip %} -**提示**：将用户帐户转换为组织时，我们会将属于该帐户的仓库中的协作者作为*外部协作者*添加到新组织。 然后，您可以根据需要邀请*外部协作者*成为新组织的成员。 更多信息请参阅“[组织的权限级别](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)”。 +**提示**：将用户帐户转换为组织时，我们会将属于该帐户的仓库中的协作者作为*外部协作者*添加到新组织。 然后，您可以根据需要邀请*外部协作者*成为新组织的成员。 更多信息请参阅“[组织的权限级别](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)”。 {% endtip %} 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 e7df42ba99..9394888d0e 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 @@ -56,4 +56,4 @@ topics: - “[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)” - "[从个人仓库删除协作者](/articles/removing-a-collaborator-from-a-personal-repository)" - "[从协作者的仓库删除您自己](/articles/removing-yourself-from-a-collaborator-s-repository)" -- "[将成员组织成团队](/articles/organizing-members-into-teams)" +- "[将成员组织成团队](/organizations/organizing-members-into-teams)" 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 e436b64e2d..288a40a557 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 @@ -25,4 +25,4 @@ topics: ### 延伸阅读 -- /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md index cfd307cfa3..c5cfac78eb 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders.md @@ -13,7 +13,7 @@ topics: 对于某些事件，您还可以为预定提醒启用实时警报。 实时警报会在重要事件（例如分配审查时）发生时立即发送到您的 Slack 通道。 -对于您所在组织的拉取请求，您可以为个人或团队级审查请求设置预定提醒。 组织所有者必须先授权您的 Slack 工作区，然后您才可为自己创建预定提醒。 更多信息请参阅“[管理组织的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)”。 +对于您所在组织的拉取请求，您可以为个人或团队级审查请求设置预定提醒。 组织所有者必须先授权您的 Slack 工作区，然后您才可为自己创建预定提醒。 更多信息请参阅“[管理组织的预定提醒](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)”。 {% data reusables.reminders.scheduled-reminders-limitations %} @@ -50,5 +50,5 @@ topics: ### 延伸阅读 -- “[管理组织的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)” -- “[管理团队的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)” +- “[管理组织的预定提醒](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)” +- “[管理团队的预定提醒](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)” 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 e5e8e235fa..cc0230e528 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 @@ -125,7 +125,7 @@ GitHub 在[企业服务等级协议](/github/site-policy/github-enterprise-servi 客户对服务的使用必须遵守 [GitHub 可接受的使用政策](/articles/github-acceptable-use-policies)和 [GitHub 社区指导方针](/articles/github-community-guidelines)。 客户不得在任何司法管辖区将服务用于非法、淫秽、冒犯性或欺诈性内容或活动，例如鼓吹或造成伤害；干扰或违反网络或系统的完整性或安全性；避开过滤器；发送主动、辱骂或欺诈性消息、病毒或有害代码；或者违反第三方权利。 #### 3. 隐私 -[GitHub 隐私声明](/articles/github-privacy-statement)和 [GitHub 数据保护附录](/github/site-policy/github-data-protection-addendum)详细介绍了 GitHub 的隐私保护和数据使用实践，以及 GitHub 在处理和保护客户个人数据方面的义务。 任何个人、实体或服务从服务收集数据都必须遵守 GitHub 隐私声明，特别是收集用户个人信息（定义见“GitHub 隐私声明”）时。 如果客户从 GitHub 收集任何用户个人信息，则客户仅将其用于外部用户已授权的目的。 客户将合理保护任何此类个人信息，并且客户会及时响应 GitHub 或外部用户的投诉、删除请求以及“不要联系”请求。 +[GitHub 隐私声明](/articles/github-privacy-statement)和 [GitHub 数据保护协议](/github/site-policy/github-data-protection-agreement-non-enterprise-customers)详细介绍了 GitHub 的隐私保护和数据使用实践，以及 GitHub 在处理和保护客户个人数据方面的义务。 任何个人、实体或服务从服务收集数据都必须遵守 GitHub 隐私声明，特别是收集用户个人信息（定义见“GitHub 隐私声明”）时。 如果客户从 GitHub 收集任何用户个人信息，则客户仅将其用于外部用户已授权的目的。 客户将合理保护任何此类个人信息，并且客户会及时响应 GitHub 或外部用户的投诉、删除请求以及“不要联系”请求。 ### D. 内容责任；所有权；许可权利 diff --git a/translations/zh-CN/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/translations/zh-CN/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md new file mode 100644 index 0000000000..20b3d0f1a5 --- /dev/null +++ b/translations/zh-CN/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md @@ -0,0 +1,348 @@ +--- +title: GitHub 数据保护协议（非企业客户） +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum +versions: + free-pro-team: '*' +--- + +_这些条款适用于非企业客户。 它们也适用于在 2021 年 1 月 4 日之前许可 GitHub 产品的企业客户。 在此日期之后购买 GitHub 产品的企业客户将被定向至 https://www.github.com/enterprise-legal 了解当前条款。_ + +## 简介 + +双方同意，GitHub 数据保护协议（非企业客户）(**“DPA”**) 管辖双方在与 GitHub Enterprise Cloud 托管服务（简称为**“服务”**）相关的客户个人数据处理方面的义务。 GitHub 在此 DPA 中向使用服务的所有非企业客户做出承诺。 客户对非 GitHub 产品的使用由单独的条款（包括不同的隐私条款）管辖。 + +如果 DPA 与客户与 GitHub 的协议中任何其他条款之间有任何冲突或不一致，以 DPA 为准。 DPA 的条款取代 GitHub 隐私声明中的任何冲突条款，非冲突条款可能适用于处理本文定义的客户个人数据。 为明确起见，与附件 1 中标准合同条款第 10 条一致，标准合同条款优先于 DPA 中任何其他条款。 + + +## GITHUB 数据保护 + +### 1. 定义。 + +1.1 “**适用数据保护法律**”是指与处理及使用客户个人数据相关、适用于客户使用 GitHub 和 GitHub 服务的法律、法规、监管框架或其他立法，包括： + + a. 《欧盟通用数据保护条例 2016/679》(**"GDPR"**)，以及生效且适用的任何实施中或相应的等效国家法律或法规；以及 + + b. 《2018 年加州消费者隐私法案》，加利福尼亚州 民事 法典第 1798.100 及其后各段 (**"CCPA"**)；以及 + + c. 《 2018 年英国数据保护法》及其中包含的 GDPR 实施条例。 + +1.2 “**控制方**”、“**数据主体**”、“**成员国**”、“**个人数据**”、“**个人数据泄露**”、“**处理**”、“**处理方**”和“**监督机构**”的含义采用“适用数据保护法律”中的定义。 如果发生冲突，GDPR 中的含义优先。 + +1.3 “**客户个人数据**”是指客户为控制方的任何个人数据，无论是客户提供给 GitHub 处理还是 GitHub 履行其在本协议下义务的过程中产生的个人数据。 包括诸如帐单信息、IP 地址、公司电子邮件地址以及客户作为控制方的任何其他个人数据。 + +1.4 “**客户仓库数据**”是指客户在其任何私有仓库中上传或创建的任何数据或信息。 + +1.5 “**数据泄露**”是指个人数据泄露或者任何其他已确认或合理怀疑的客户受保护数据泄露。 + +1.6 “**最终用户**”是指控制 GitHub 帐户并且已同意 GitHub 服务条款及其个人数据被 GitHub 传输、存储或处理的个别数据主体。 例如，客户每个有 GitHub 帐户的员工或承包商也是 GitHub 最终用户。 + +1.7 数据处理“**允许的目的**”是指按本协议“GitHub 隐私声明”及本附录 A 所述提供服务的有限和特定目的，或者数据主体授权使用客户个人数据的目的。 + +1.8 “**受保护数据**”包括 GitHub 根据本协议代表客户处理的任何客户个人数据和任何客户仓库数据。 + +1.9 “**敏感数据**”是指显示种族或民族；政见、宗教、信仰或工会成员资格；为唯一识别自然人而进行的遗传数据或生物数据处理；健康、自然人性别或性取向相关数据；违法行为、刑事定罪或安全措施相关数据等的任何客户个人数据。 + +### 2. 身份与合规。 + +#### 2.1 数据处理。 +GitHub 可作为其接收的与本协议相关的任何客户个人数据的处理方，并且 GitHub 只根据本协议及其他书面通信所述的客户指示将客户个人数据用于允许的目的。 如果 GitHub 无法遵守客户的指示，比如由于与适用数据保护法律冲突，或者适用数据保护法律或其他法律要求处理，则 GitHub 将在允许的范围内通知客户。 GitHub 在美国或欧盟处理所有客户个人数据；但 GitHub 的子处理方可能在美国或欧盟以外处理数据。 此外，GitHub 可作为任何客户仓库数据的处理方。 + +#### 2.2 数据控制方。 +GitHub 从客户以及直接从创建最终用户帐户的数据主体接收客户个人数据。 客户其直接传输到 GitHub 的客户个人数据的唯一控制方。 + +#### 2.3 GitHub 合规性；数据传输。 +GitHub 将遵守与客户个人数据处理相关的适用数据保护法律。 + +为提供服务而从欧盟、欧洲经济区、英国和瑞士传出任何客户个人数据，均应遵守附件 1（标准合同条款）中的标准合同条款。 GitHub 将遵守欧洲经济区和瑞士数据保护法有关收集、使用、传输、保留和其他方式处理来自欧洲经济区、英国和瑞士的客户个人数据的要求。 所有向第三国或国际组织传输客户个人数据的行为都将受到 GDPR 第 46 条所述的适当保护措施的约束，并且此类传输和保护措施将根据 GDPR 第 30(2) 条的规定进行记录。 + +此外，GitHub 还通过了欧盟-美国 和瑞士-美国认证。 In addition, GitHub is certified to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-U.S. Privacy Shield Framework as a legal basis for transfers of Personal Data in light of the judgment of the Court of Justice of the EU in Case C-311/18. GitHub agrees to notify Customer if it makes a determination that it can no longer meet its obligation to provide the same level of protection as is required by the Privacy Shield principles. GitHub 同意，在确定无法再履行其义务提供隐私盾原则所要求的保护级别时通知客户。 + + +### 3. 数据保护。 + +#### 3.1 目的限制。 +GitHub 仅为允许的目的处理和传播受保护数据，除非双方书面同意扩展的目的。 + +#### 3.2 数据质量和相称性。 +GitHub 将保持客户个人数据的准确性和最新性，或使客户能够做到这一点。 GitHub 将采取商业上合理的措施来确保其代表客户收集的任何受保护数据充分、相关且传输和处理符合相关目的。 在任何情况下 GitHub 都不会有意代表客户收集敏感数据。 客户同意，GitHub 服务未预期存储敏感数据；如果客户选择将敏感数据上传到服务，则客户必须遵守 GDPR 第 9 条或适用数据保护法律中的同等条款。 + +#### 3.3 数据保留和删除。 +在客户合理要求时，除非法律禁止，否则 GitHub 将在三天内退回、销毁或去识别所有位置存储、不再需要用于允许目的的所有客户个人数据及相关数据。 GitHub 可在适用数据保护法律需要的范围内保留客户个人数据及相关数据，并且仅保留适用数据保护法律要求的范围和期限，但 GitHub 要确保客户个人数据仅用于适用数据保护法律指定的目的，而不能用于其他目的，同时客户个人数据仍受适用数据保护法律的保护。 + +#### 3.4 数据处理。 +关于处理客户的受保护数据，GitHub 根据 GDPR 第 28(3) 条的要求提供以下信息： + +a. 客户个人数据*处理的主题和期限*在协议和本附录中描述。 + +b. 客户个人数据的*处理性质和目的*在本附录第 3.1 条描述。 + +c. *要处理的客户个人数据类型*在“GitHub 隐私声明”中描述，包括用户名、密码、电子邮件地址和 IP 地址等客户个人数据。 GitHub 还处理客户帐户记帐所需的信息，但不处理或存储信用卡信息。 客户可选择向 GitHub 提供其他客户个人数据，如客户的配置文件设置，或者将客户个人数据上传到其 GitHub 仓库。 + +d. *与客户个人数据相关的数据主体类别*是客户本身及其最终用户。 + +e. *客户的义务和权利*在协议和本附录中描述。 + +### 4. 安全和审核义务。 + +#### 4.1 技术和组织安全措施。 +考虑技术、实施成本、处理性质、处理范围、处理背景和目的，以及自然人权利和自由的不同可能性和严重性的风险，GitHub 在处理受保护数据时将实施适当的技术和组织措施来确保适合风险的安全性，比如防止意外或非法销毁、丢失、篡改、未授权披露或访问。 GitHub 将定期监控是否符合这些措施，并在协议整个期限内继续采取适当的保护措施。 + +#### 4.2 事件响应和违规通知。 +GitHub 遵守适用的数据保护法。 + +#### 4.3 GitHub 人员。 +GitHub 声明并保证，将采取合理措施确保处理受保护数据的所有 GitHub 人员已同意对受保护数据保密，并且已接受遵守本附录和适用数据保护法律的适当培训。 + +#### 4.4 记录。 +GitHub 将维护代表客户执行的处理活动所有类别的完整、准确和最新书面记录，其中包含适用数据保护法律要求的信息。 在协助不会对 GitHub 的安全性或个别数据主体的隐私权利产生风险的范围内，GitHub 将应客户要求向其提供合理需要的这些记录，比如帮助客户证明其遵守适用数据保护法律。 + +#### 4.5 协助。 +对于数据隐私影响评估、数据主体权利请求、监督机构咨询及其他类似事务等问题，GitHub 将向客户提供合理的协助，在每一种情况下只与客户个人数据的处理相关，并且考虑处理的性质。 + +### 5. 受保护数据的使用和披露。 + +#### 5.1 不用于营销。 +GitHub 不将受保护数据用于宣传第三方内容，也不向任何第三方销售受保护数据，因合并或收购而造成的数据转移除外。 + +#### 5.2 GitHub 隐私声明。 +“GitHub 隐私声明”公布在 [https://help.github.com/articles/github-privacy-statement/](/articles/github-privacy-statement) 上，详细说明 GitHub 的隐私和数据使用做法，包括对 cookie 的使用、争议解决流程以及 GitHub 的 GDPR 合规的进一步详情。 + +### 6. 再处理和向外传输。 + +#### 6.1 数据保护。 +GitHub 对受保护数据向外传输到其再处理方（如其第三方支付处理方）负责。 如果 GitHub 将受保护数据传输到第三方再处理方，或者 GitHub 安装、使用或允许第三方或第三方服务代表 GitHub 处理受保护数据，GitHub 将确保第三方再处理方受书面协议约束，要求他们提供至少与本 DPA 和适用数据保护法律对 GitHub 要求相同级别的机密性、安全性和隐私保护。 + +#### 6.2 GitHub 再处理方的接受。 +客户授权 GitHub 根据协议的第 6 部分以及任何其他限制指定（并允许每个再处理方根据第 6 部分指定）再处理方。 GitHub 自本附录生效日期起可继续使用当前使用的再处理方。 + +#### 6.3 外部再处理的总体同意。 +客户总体上同意 GitHub 使用外部再处理方，条件是 GitHub 符合以下要求： + +a. 任何外部再处理方必须书面同意只在欧洲委员会已经宣布具有“充分”保护级别的国家处理数据；或只按照与“标准合同条款”相当的条款处理数据，或根据适当欧洲数据保护机构授予的“具约束力公司规则”批准处理数据，或根据合规且有效的欧盟-美国和瑞士-美国 隐私盾认证处理数据；以及 + +b. GitHub 将外部再处理方对客户个人数据的访问严格限于仅执行此服务所需，并且 GitHub 会禁止再处理方出于任何其他目的而处理客户个人数据。 + +#### 6.4 再处理方披露协议。 +GitHub 在 [https://docs.github.com/articles/github-subprocessors-and-cookies/](/articles/github-subprocessors-and-cookies) 上维护其用来处理客户个人数据的外部再处理方清单，包括处理的客户个人数据类别、再处理方执行的处理类型说明以及处理的地点。 GitHub 将应客户的书面申请而向客户提供再处理方清单以及规范他们处理客户个人数据的条款。 根据再处理方保密性限制，GitHub 在向客户提供清单和条款之前可能会删除任何机密或商业敏感信息。 在 GitHub 不能向客户披露机密或敏感信息的情况下，双方同意，GitHub 将提供其合理可以提供的与其再处理协议相关的所有信息。 + +#### 6.5 对再处理方的异议。 +GitHub 在增加或删除任何再处理方时，将在其 网站中公告更改，提前向第三方提供书面通知，包括第 6.4 条中所列的类别。 如果客户对 GitHub 新增再处理方持有合理的异议，客户必须及时书面通知 GitHub。 GitHub 将尽可能采取商业合理的努力为受影响的服务提供替代解决方案，以避免招异议的再处理方处理数据。 如果 GitHub 无法提供替代解决方案而双方在九十天内无法解决冲突，客户可终止协议。 + +### 7. 终止。 + +#### 7.1 暂停。 +如果 GitHub 未履行保持适当安全或隐私保护级别的义务，客户可临时暂停所有客户个人数据的传输，或禁止代表客户进行的客户个人数据收集和处理，直到 GitHub 履行义务或协议终止。 + +#### 7.2 因故终止。 +除了客户在协议项上拥有的任何终止权利之外，在下列情况下，客户亦可在不损害法律或衡平法的任何其他要求时终止协议： + +a. GitHub 通知客户无法再履行其隐私保护义务； + +b. 根据第 7.1 条，所有客户个人数据的传输、收集或处理已经临时暂停超过一个月； + +c. GitHub 实质性或持续违反本附录下的任何保证或表示； + +d. GitHub 不再经营业务、解散、破产或清盘；或 + +e. 客户根据第 6.5 条反对再处理方，并且 GitHub 在九十天内无法提供替代解决方案。 + +#### 7.3 违约。 +不遵守本附录的重大条款被视为协议下的重大违约。 + +#### 7.4 未履行义务。 +如果法律或法规的变动导致本附录的执行无法进行或商业上不合理，则双方可善意重新协商本附录。 如果重新协调无法解决问题，或者双方无法达成协议，则双方可在三十天后终止协议。 + +#### 7.5 通知。 +如果 GitHub 确定其无法再履行本附录项下的隐私义务，GitHub 将立即书面通知客户。 + +#### 7.6 修改。 +GitHub 可在提前三十天通知客户后，根据适用数据保护法律的要求不时修改本附录。 + +#### 7.7 终止要求。 +终止后，GitHub 必须： + +a. 采取合理、适当的措施停止处理客户个人数据； + +b. 在终止后的九十天内，删除或去识别 GitHub 根据第 3.3 条代表客户存储的任何客户个人数据；以及 + +c. 向客户提供合理的保证，确保 GitHub 已履行其在第 7.7 条中的义务。 + +### 8. 数据处理责任。 + +#### 8.1 限制。 +适用数据保护法律限制的除外，在本附录下提出的任何要求需遵守关于责任限制的协议条款。 + +## 附件 1 - 标准合同条款 (处理方) +客户执行的适用协议包括由 GitHub, Inc 签署的《数据保护附录》的本附件 1。 + +在使用标准合同条款需要监管机构批准的国家/地区，除非客户获得了所需的监管机构批准，否则根据欧洲委员会 2010/87/EU（2010 年 2 月）的规定，客户不得根据标准合同条款确定从此类国家/地区出口数据的合法性。 + +根据《通用数据保护条例》(EU 2016/679) 第 46(2) 条针对将个人数据转移给在无法确保充分数据保护级别的第三国设立的处理方之规定，客户（作为数据出口方）和 GitHub（作为数据进口方，其签名见下文）每一方（合称为“双方”）都同意以下合同条款（以下简称“条款”或“标准合同条款”），以便在数据出口方将附录 1 中规定的个人数据转移给数据进口方时，为个人的隐私、基本权利和自由提供充分保障。 + +#### 第 1 条：定义 +(a) “个人数据”、“特殊数据类别”、“处理”、“控制方”、“处理方”、“数据主体”和“监督机构”应采用《通用数据保护条例》(EU 2016/679) 在个人数据处理和此类数据自由流通的个人保护方面规定的含义； + +(b) “数据出口方”是指负责转移个人数据的控制方； + +(c) “数据进口方”是指从数据出口方接收个人数据，并在数据转移后，根据数据出口方的指示和条款规定代表其处理此类数据的处理方，并且不受第三国系统的约束，确保数据根据《通用数据保护条例》(EU 2016/679) 第 45(2) 条的规定得到充分保护。 + +(d) “再处理方”是指数据进口方或数据进口方的任何其他再处理方雇佣的任何处理方，他们从数据进口方或数据进口方的任何其他再处理方接收个人数据，并在数据转移后，根据其指示、条款规定以及书面分包合同的条款代表其执行数据处理活动； + +(e) “适用的数据保护法”是指保护个人基本权利和自由的立法，尤其是保护个人在处理个人数据方面的隐私权，适用于数据出口方所在成员国的数据控制方； + +(f) “技术和组织安全措施”是指旨在保护个人数据不受意外或非法破坏或意外丢失、更改、未经授权披露或访问的措施，尤其是涉及网络数据传输的处理以及针对所有其他非法处理方式。 + +#### 第 2 条：转移细节 +转移细节，尤其是特殊类别个人数据的转移，应遵守下文附录 1 中的规定，该附录构成了本条款的组成部分。 + +#### 第 3 条：第三方受益人条款 +1. 数据主体可以作为第三方受益人对数据出口方执行本条、第 4(b) 至 (i)、第 5(a) 至 (e) 和 (g) 至 (j)、第 6(1) 和 (2)、第 7、第 8(2) 和第 9 至 12 条。 + +2. 在数据出口方事实上已经消失或在法律上不复存在的情况下，数据主体可对数据进口方执行本条、第 5(a) 至 (e) 和 (g)、第 6、第 7、第 8(2) 和第 9 至 12 条，除非任何继承实体通过合同或法律的实施承担了数据出口方的全部法律义务，并因此承担了数据出口方的权利和义务，在这种情况下，数据主体可以针对此类实体执行这些条款。 + +3. 在数据出口方和数据进口方事实上已经消失或在法律上不复存在或已经破产的情况下，数据主体可对再处理方执行本条、第 5(a) 至 (e) 和 (g)、第 6、第 7、第 8(2) 和第 9 至 12 条，除非任何继承实体通过合同或法律的实施承担了数据出口方的全部法律义务，并因此承担了数据出口方的权利和义务，在这种情况下，数据主体可以针对此类实体执行这些条款。 再处理方的此类第三方责任应限于其在本条款下的处理业务。 + +4. 如果数据主体有明确的意愿并且国家法律允许，当事方不反对由协会或其他机构代表数据主体。 + +#### 第 4 条：数据出口方的义务 +数据出口方同意并保证： + +(a) 个人数据的处理，包括数据转移过程，已经并将继续按照适用的数据保护法的相关规定进行（并且在适用的情况下通知数据出口方所在成员国的相关当局），并且不违反该国有关规定； + +(b) 已指示并将在个人数据处理服务期间指示数据进口方，仅代表数据出口方并根据适用的数据保护法和本条款来处理所转移的个人数据； + +(c) 数据进口方将为下文附录 2 中规定的技术和组织安全措施提供充分保证； + +(d) 在评估了适用数据保护法的要求后，安全措施适用于保护个人数据，使其免受意外或非法破坏或意外丢失、更改、未经授权的披露或访问，尤其是涉及网络数据传输的处理以及针对所有其他非法处理方式，并在考虑到最新技术和实施成本的情况下，确保这些措施能够提供与处理所带来的风险和要保护数据的性质相适应的安全水平； + +(e) 确保遵循安全措施； + +(f) 如果数据转移涉及特殊类别的数据，则已经或将在转移之前或之后尽快告知数据主体，其数据可能被传输到《一般数据保护条例》 (EU 2016/679) 所指的无法提供充分保护的第三国； + +(g) 如果数据出口方决定继续转移或取消中止，则根据第 5(b) 和第 8(3) 条，将从数据进口方或任何再处理方收到的任何通知转发给数据保护监管机构； + +(h) 应要求向数据主体提供条款副本（附录 2 除外）、安全措施概要说明，以及必须根据条款制定的任何再处理服务合同副本，除非条款或合同包含商业信息，在这种情况下，它可以删除这些商业信息； + +(i) 在再处理的情况下，处理活动由再处理方根据第 11 条执行，对个人数据和数据主体的权利提供至少与本条款下数据进口方相同的保护级别；以及 + +(j) 确保遵守第 4(a) 至 (i) 条。 + +#### 第 5 条：数据进口方的义务 +数据进口方同意并保证： + +(a) 只代表数据出口方并按照其指示和条款处理个人数据；如果出于任何原因无法提供此类遵循，则迅速将无法遵循的情况通知数据出口方， 在这种情况下，数据出口方有权中止数据转移和/或终止合同； + +(b) 没有理由认为适用于它的法律会阻止它履行从数据出口方那里收到的指示和它在合同下的义务，如果该立法发生变化，可能对条款规定的保证和义务产生重大不利影响，则在知情后立即通知数据出口方，在这种情况下，数据出口方有权中止数据转移和/或终止合同； + +(c) 在处理所转移的个人数据之前，已实施附录 2 中规定的技术和组织安全措施； + +(d) 将以下情况迅速通知数据出口方： + +(i) 执法机关提出披露个人数据等任何具有法律约束力的要求，除非另有禁止，例如刑法禁止通知以保护执法调查的机密性， + +(ii) 任何意外或未经授权的访问，以及 + +(iii) 直接从数据主体收到的任何请求，但不会对该请求作出回应，除非另有授权； + +(e) 迅速妥善处理数据出口方就其处理所转移个人数据而提出的所有询问，并遵守监管机构关于处理所转移数据的建议； + +(f) 应数据出口方的要求，提交其数据处理设施，以供审核本条款所涵盖的处理活动，此类审核应由数据出口方或由独立成员组成并拥有受保密义务约束的所需专业资格的检查机构进行，在适用的情况下，经监管机构同意，由数据出口方选择； + +(g) 应要求向数据主体提供条款副本或任何现有的再处理合同，除非条款或合同包含商业信息，在这种情况下，可以删除此类商业信息，但附录 2 除外，在数据主体无法从数据出口方获得副本的情况下应替换为安全措施概要说明； + +(h) 在再处理的情况下，事先通知数据出口方并获得其事先书面同意； + +(i) 再处理方的处理服务将按照第 11 条的规定执行；以及 + +(j) 迅速将其根据本条款缔结的任何再处理方协议的副本发送给数据出口方。 + +#### 第 6 条：赔偿责任 +1. 双方同意，因任何一方或再处理方违反第 3 条或第 11 条所述义务而遭受损害的任何数据主体，有权就所遭受的损害向数据出口方索取赔偿。 + +2. 如果由于数据进口方或其再处理方违反第 3 条或第 11 条所述的任何义务，数据主体无法根据第 1 款向数据出口方提出索赔，其原因是数据出口方事实上已消失或在法律上不复存在或已破产，数据进口方同意，数据主体可以像向数据出口方索赔一样向数据进口方提出索赔，除非任何继承实体通过合同或法律实施承担了数据出口方的全部法律义务，在这种情况下，数据主体可以针对此类实体履行其权利。 数据进口方不得以再处理方违反其义务为由而推卸自己的责任。 + +3. 如果由于再处理方违反第 3 条或第 11 条所述的任何义务，数据主体无法根据第 1 和第 2 款向数据出口方或数据进口方提出索赔，其原因是数据出口方和数据进口方均事实上已消失或在法律上不复存在或已破产，再处理方同意，数据主体可以像向数据出口方或数据进口方索赔一样，就再处理方在本条款下的处理业务向其提出索赔，除非任何继承实体通过合同或法律实施承担了数据出口方或数据进口方的全部法律义务，在这种情况下，数据主体可以针对此类实体履行其权利。 再处理方的赔偿责任应限于其在本条款下的处理业务。 + +#### 第 7 条：调解和管辖权 +1. 数据进口方同意，如果数据主体援引第三方受益权和/或根据条款要求赔偿损失，数据进口方将接受数据主体的以下决定： + +(a) 将争议交由独立人士调解，或在适用的情况下，由监管机构进行调解； + +(b) 将争议提交给数据出口方所在成员国的法院处理。 + +2. 双方同意，数据主体的选择不影响其根据国内法或国际法的其他规定寻求补救的实质性或程序性权利。 + +#### 第 8 条：与监管机构的合作 +1. 数据出口方同意向监督机构交存本合同副本，如果监督机构或适用的数据保护法要求交存此类副本。 + +2. 双方同意，监管机构有权对数据进口方和任何再处理方进行审核，审计范围和条件与适用数据保护法对数据出口方规定的审核相同。 + +3. 如果存在阻止根据第 2 款对数据进口方或任何再处理方进行审核的适用立法，数据进口方应立即通知数据出口方。 在这种情况下，数据出口方应有权采取第 5(b) 条规定的措施。 + +#### 第 9 条：管辖法律。 +本条款应受数据出口方所在成员国的法律管辖。 + +#### 第 10 条：合同变更 +双方承诺不改变或修改条款。 但这并不妨碍双方在必要时添加有关业务问题的条款，前提是它们不与本条款相冲突。 + +#### 第 11 条：再处理 +1. 未经数据出口方事先书面同意，数据进口方不得将其代表数据出口方执行的任何处理业务分包出去。 如果数据进口方在征得数据出口方同意的情况下，将其在本条款下的义务分包出去，则必须与再处理方签订书面协议，该协议对再处理方施加的义务应与本条款对数据进口方施加的义务相同。 如果再处理方未能履行该书面协议规定的数据保护义务，则数据进口方仍应对数据出口方负全部责任，以履行该协议下的再处理方义务。 + +2. 数据进口方与再处理方之间的事先书面合同还应规定第 3 条中所述的第三方受益人条款，以防数据出口方或数据进口方事实上已消失或在法律上不复存在或已破产，而且没有任何继承实体通过合同或法律实施承担数据出口方或数据进口方的全部法律义务，导致数据主体无法向他们提出第 6 条第 1 款所述的索赔。 再处理方的此类第三方责任应限于其在本条款下的处理业务。 + +3. 第 1 款所述再处理合同的数据保护方面的规定应受数据出口方所在成员国的法律管辖。 + +4. 数据出口方应保留根据本条款缔结并由数据进口方根据第 5(j) 条通知的再处理协议的清单，该清单应每年至少更新一次。 该清单应提供给数据出口方的数据保护监管机构。 + +#### 第 12 条：个人数据处理服务终止后的义务 +1. 双方同意，在终止提供数据处理服务时，数据进口方和再处理方应根据数据出口方的选择，将传输的所有个人数据及其副本返还给数据出口方，或者销毁所有个人数据并向数据出口方提供相关证明，除非适用于数据进口方的法律阻止其返还或销毁所传输的全部或部分个人数据。 在这种情况下，数据进口方应保证将确保所传输个人数据的机密性，并且不再主动处理所传输的个人数据。 + +2. 数据进口方和再处理方保证，将应数据出口方和/或监管机构的要求，提交其数据处理设施以接受第 1 款所述的审核。 + +### 标准合同条款附录 1 +数据出口方：客户是数据出口方。 + +**数据进口方：**数据进口方是全球软件和服务生产商 GitHub, Inc.。 + +**数据主体：**数据主体是数据出口方的代表和最终用户，包括数据出口方的员工、承包商、协作者和客户。 数据主体还可能包括试图向数据进口方提供的服务的用户传达或传输个人信息的个人。 GitHub 承认，根据客户对服务的使用情况，客户可以选择在客户个人数据中包含来自以下任何类型数据主体的个人数据： + +- 数据出口方的员工、承包商和临时工（现任、前任、未来）； +- 上述人员的家属； +- 数据出口方的协作者/联系人（自然人）或法律实体协作者/联系人的员工、承包商或临时工（现任、未来、前任）； +- 用户（例如，顾客、客户、患者、访客等）以及作为数据出口方服务用户的其他数据主体； +- 合作伙伴、利益相关者或与数据出口方的员工积极协作、交流或以其他方式互动的个人和/或使用数据出口方提供的应用程序和网站等沟通工具的个人； +- 被动地与数据出口方交互的利益相关者或个人（例如，因为他们是调查、研究的对象，或者是数据出口方的文件或通信中提到的对象）；或 +- 具有职业特权的专业人士（如医生、律师、公证人、宗教工作者等）。 + +**数据类别：**在服务范围内，以电子形式包含在电子邮件、文档和其他数据中的所传输个人数据。 GitHub 承认，根据客户对服务的使用情况，客户可以选择在客户个人数据中包含来自以下任何类别的个人数据： +- 身份验证数据（例如，用户名、电子邮件、密码）； +- 联系信息（例如，电子邮件）; +- 唯一标识号和签名（IP 地址、跟踪 Cookie 或类似技术中的唯一标识符）。 +- 其他的唯一识别信息。 数据主体可能包含更多数据，例如真实姓名、头像图片和其他个人信息； + +**特殊类别的数据（如适用）：**数据进口方在向数据出口方提供服务时不会有意收集或处理任何特殊类别的数据。 + +但是，由于数据进口方提供存储服务，并且不控制其存储的数据类别，因此数据出口方可以选择传输特殊类别的数据。 所以，数据出口方应全权负责确保其遵守适用法律和法规规定的与收集和处理任何特殊类别数据有关的所有义务，包括在处理敏感个人数据之前获得数据主体的明确同意。 + +**处理业务：**所传输的个人数据将受以下基本处理活动的约束：GitHub 将个人数据用于《GitHub 隐私声明》（见 [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement)）和 DPA 的“数据处理”部分规定的有限目的。 分包商：根据 DPA，数据进口方可以雇佣其他公司代表他们提供有限的服务，例如提供客户支持。 任何此类分包商只能以提供数据进口商委托的服务为目的而获取客户个人数据，并且不得将客户个人数据用于任何其他目的。 + +### 标准合同条款附录 2 +数据进口方根据第 4(d) 和 5(c) 条实施的技术和组织安全措施的说明： + +**1. 人员。**数据进口方的人员未经授权不得处理客户个人数据。 人员有义务对任何客户个人数据保密，即使在他们的工作结束后，这一义务仍将继续。 + +**2. 数据隐私联系人。**数据进口方的数据隐私专员的联系地址如下： GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA + +**3. 技术和组织措施。**数据导入者已实施并将保持适当的技术和组织措施、内部控制和信息安全程序，旨在保护客户个人数据免受意外丢失、破坏、更改、未经授权的披露或访问或非法销毁。 + +GitHub Inc. 的签名如下。 + +代表数据进口方签署标准合同条款、附录 1 和附录 2 + +![屏幕截图，2020-07-20，下午 2 20 29](/assets/images/help/site-policy/docusign-signature.png) + +Lynn Hashimoto，产品与监管法律部主管 + +GitHub, Inc. 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 916042989e..2f8fda3dec 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 @@ -192,7 +192,7 @@ GitHub 的许多服务和功能都是面向公众的。 如果您的内容是面 #### 组织 -您可以通过在 GitHub 上的操作来表明您愿意分享自己的用户个人信息。 如果您与组织协作或成为组织成员，则其帐户所有者可能会收到您的用户个人信息。 当您接受组织邀请时，您将被告知所有者可以看到的信息类型（更多信息请参阅[关于组织成员](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)）。 如果您接受含有[验证域](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)的组织的邀请，则该组织的所有者将能够在该组织的验证域中查看您的完整电子邮件地址。 +您可以通过在 GitHub 上的操作来表明您愿意分享自己的用户个人信息。 如果您与组织协作或成为组织成员，则其帐户所有者可能会收到您的用户个人信息。 当您接受组织邀请时，您将被告知所有者可以看到的信息类型（更多信息请参阅[关于组织成员](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)）。 如果您接受含有[验证域](/organizations/managing-organization-settings/verifying-your-organizations-domain)的组织的邀请，则该组织的所有者将能够在该组织的验证域中查看您的完整电子邮件地址。 请注意，GitHub 可能会将您的用户名、[使用信息](#usage-information)和[设备信息](#device-information)分享给您所属组织的所有者，但提供这些用户个人信息的目的仅限于调查或响应可能影响或损害该特定组织安全性的安全事件。 @@ -321,7 +321,7 @@ GitHub 处理美国境内外的个人信息，并依靠标准合同条款作为 ### 隐私声明的变更 -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)或经常查看我们的网站政策仓库。 +GitHub 可能会不时更改我们的隐私声明，不过大多数情况都是小变动。 如果本隐私声明发生重大变更，我们会在变更生效之前至少 30 天通知用户 - 在我们网站的主页上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 我们还会更新我们的[站点政策仓库](https://github.com/github/site-policy/)，通过它可跟踪本政策的所有变更。 对于本隐私声明的其他更改，我们建议用户[关注](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)或经常查看我们的网站政策仓库。 ### 许可 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 29f0395335..278e43c234 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 @@ -13,7 +13,7 @@ topics: - 法律 --- -生效日期：**2021 年 1 月 29 日** +Effective date: **April 2, 2021** GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享您的数据方面提供很大的透明度。 为此，我们提供此页面，以详细介绍了我们的[子处理商](#github-subprocessors)，以及我们如何使用 [cookie](#cookies-on-github)。 @@ -33,7 +33,6 @@ GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享 | MailChimp | 客户事件单邮件服务提供商 | 美国 | 美国 | | Mailgun | 交易邮件服务提供商 | 美国 | 美国 | | Microsoft | Microsoft 服务 | 美国 | 美国 | -| Monday.com | 团队协作和项目管理平台 | 美国 | 以色列 | | Nexmo | 短信通知提供商 | 美国 | 美国 | | Salesforce.com | 客户关系管理 | 美国 | 美国 | | Sentry.io | 应用程序监控提供商 | 美国 | 美国 | diff --git a/translations/zh-CN/content/github/site-policy/index.md b/translations/zh-CN/content/github/site-policy/index.md index ebef5bf709..9163eeac64 100644 --- a/translations/zh-CN/content/github/site-policy/index.md +++ b/translations/zh-CN/content/github/site-policy/index.md @@ -16,6 +16,7 @@ topics: {% 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-agreement-non-enterprise-customers %} {% link_in_list /global-privacy-practices %} {% link_in_list /github-insights-and-data-protection-for-your-organization %} {% link_in_list /github-sponsors-additional-terms %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md index fd97f6ea58..2d4c8e5def 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -24,7 +24,9 @@ topics: ### 赞助级别 -{% data reusables.sponsors.tier-details %} 更多信息请参阅“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”、“[为组织设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)”和“[更改赞助级别](/articles/changing-your-sponsorship-tiers)”。 +{% data reusables.sponsors.tier-details %} 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)," "[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), and "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)." + +It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. ### 赞助付款 @@ -34,5 +36,9 @@ topics: 更多信息请参阅“[从 {% data variables.product.prodname_sponsors %} 管理您的付款](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)”。 +### 共享关于 {% data variables.product.prodname_sponsors %} 的反馈 + +{% data reusables.sponsors.feedback %} + ### 延伸阅读 - {% data variables.product.prodname_blog %} 上的“[{% data variables.product.prodname_sponsors %} 团队常见问题](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)” 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 225296b4a9..3da85116e9 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 @@ -37,7 +37,7 @@ topics: ### 共享关于 {% data variables.product.prodname_sponsors %} 的反馈 -这只是开始 - 我们欢迎大家提供意见，确保 {% data variables.product.prodname_sponsors %} 满足您未来的需求。 请联系 [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors)，向我们发送您的反馈或建议。 +{% data reusables.sponsors.feedback %} ### 延伸阅读 - "[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" 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 604c749541..c27bd1652d 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 @@ -15,6 +15,8 @@ topics: 对于被赞助开发者帐户，更新将来自您用户帐户的主电子邮件地址。 如果您对用户帐户启用了电子邮件地址保密，则更新邮件将从 `noreply@github.com` 发出。 对于被赞助的组织，更新将来自组织的 `noreply@github.com` 电子邮件地址。 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。 +You can also contact any one-time sponsors who contributed within the last 30 days and enabled updates. + ### 联系赞助者 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/index.md index 6d66c50e57..162cbf8285 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/index.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/index.md @@ -25,7 +25,7 @@ topics: {% 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 /managing-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 %} 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 0d833c9ce4..a3dafd298d 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 @@ -13,6 +13,12 @@ topics: 您的目标可设为您想要的赞助者数量或您希望每月赚取的金额。 每次只能设置一个目标。 一个目标达成后，可以设置另一个目标。 +{% note %} + +**Note:** Goals are intended to help people track momentum so only monthly sponsors contribute toward your goal. + +{% endnote %} + ### 设置目标 {% data reusables.sponsors.navigate-to-sponsors-dashboard %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md new file mode 100644 index 0000000000..55c48d33eb --- /dev/null +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers.md @@ -0,0 +1,45 @@ +--- +title: Managing your sponsorship tiers +intro: '您可以添加新的赞助等级，也可以编辑或撤销现有等级。' +redirect_from: + - /articles/changing-your-sponsorship-tiers + - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers +versions: + free-pro-team: '*' +topics: + - sponsors +--- + +### 关于赞助等级 + +{% 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.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 %} + +### Enabling tiers with custom amounts + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} +{% data reusables.sponsors.enable-custom-amounts %} + +### Disabling tiers with custom amounts + +You can disable tiers with custom amounts by deselecting the **Enable custom amounts** option on the **Sponsor tiers** tab. If you disable custom amounts, all custom tiers are retired. diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 765bc2225d..3ece0959b8 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -48,6 +48,7 @@ topics: {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### 提交您的银行信息 diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index a1e7783b10..74c0bb2a4d 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -48,6 +48,7 @@ topics: {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} +{% data reusables.sponsors.enable-custom-amounts %} {% data reusables.sponsors.add-more-tiers %} ### 提交您的银行信息 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 702bf7b2d1..03339e5f14 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 @@ -1,6 +1,6 @@ --- title: 赞助开源贡献者 -intro: '您可以向设计、创建或维护您所依赖的开源项目的开发者或组织每月定期付款。' +intro: 'You can make a one-time or monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on.' redirect_from: - /articles/sponsoring-a-developer - /articles/sponsoring-an-open-source-contributor @@ -24,11 +24,11 @@ topics: - 作为重视开源的组织，培养品牌知名度 - 感谢开源开发者构建库来补充您的组织提供的产品 -您可以使用信用卡赞助 {% data variables.product.product_name %} 上的帐户。 如果您的组织希望按发票付款，请[联系我们](https://support.github.com/contact/org-sponsors-waitlist)。 +You use your normal payment method to sponsor an account on {% 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)”。 -使用信用卡赞助帐户后，更改将立即生效。 {% data reusables.sponsors.prorated-sponsorship %} +When you sponsor an account the change is effective immediately, unless you are sponsoring on behalf of an organization that pays by invoice. {% data reusables.sponsors.prorated-sponsorship %} Your sponsorship is included in the next scheduled payment to the sponsored account. {% data reusables.sponsors.manage-updates-for-orgs %} @@ -53,6 +53,7 @@ topics: - 要赞助开发者，请在开发者的名称下单击 **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.review-tiers-to-select %} {% 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/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index 1a66878f1a..7cf358484b 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md @@ -1,89 +1,94 @@ --- -title: About the dependency graph -intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' +title: 关于依赖项图 +intro: '有关依赖关系图、它支持的生态系统及其如何确定仓库所依赖的软件包的详细信息。' versions: - free-pro-team: '*' - enterprise-server: '*' + enterprise-server: '<=2.22' +topics: + - 仓库 --- -### Dependency graph availability +### 依赖关系图可用性 -The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} +依赖关系图适用于使用支持的文件格式、以支持的包生态系统定义依赖项的每个{% if currentVersion == "free-pro-team@latest" %} 公共{% endif %} 仓库。{% if currentVersion == "free-pro-team@latest" %} 仓库管理员也可对私有仓库设置依赖关系图。{% endif %} {% data reusables.repositories.enable-security-alerts %} -### About the dependency graph +### 关于依赖项图 -The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: +依赖项图是存储在仓库中的清单和锁定文件的摘要。 对于每个仓库，它会显示{% if currentversion == "free proteam@latest" %}： -- Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} +- 依赖项、它依赖的生态系统和包 +- 依赖项、依赖于它的仓库和包{% else %} 依赖项，即它所依赖的生态系统和包。 {% data variables.product.prodname_ghe_server %} 不计算有关依赖项、仓库和依赖于仓库的包的信息。{% endif %} -When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. +向 {% data variables.product.product_name %} 推送提交以更改支持的清单或锁定文件或将其添加到默认分支时，依赖项图会自动更新。.{% if currentVersion == "free-pro-team@latest" %}此外，当有人向某个依赖项的仓库推送更改时，该图也会更新。{% endif %}有关支持的生态系统和清单文件的信息，请参阅下面的“[支持的包生态系统](#supported-package-ecosystems)”。 {% if currentVersion == "free-pro-team@latest" %} -When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. 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 %} 使用依赖项图向拉取请求添加依赖项审查。 它们指示依赖项是否包含漏洞，如果是，则指示已修复漏洞的依赖项版本。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 {% endif %} -### Dependencies included +### 包含的依赖项 -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: +依赖关系图包括清单和锁定文件中详述的所有依赖项，或支持的生态系统的同等项。 这包括： -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies +- 在清单或锁定文件中明确定义的直接依赖项 +- 这些直接依赖项的间接依赖项，也称为过渡依赖项或子依赖项 -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +依赖项图通过锁定文件明确标识间接依赖项{% if currentVersion == "free-pro-team@latest" %} 或者通过检查直接依赖项的依赖项来标识间接依赖项。 对于最可靠的依赖关系图， 您应该使用锁定文件（或其等效项），因为它们准确地定义了您当前使用的直接和间接依赖项版本。 如果您使用锁定文件，还要确保仓库的所有贡献者都使用相同的版本，这样更便于您{% else %}从锁定文件{% endif %} 测试和调试代码。 {% if currentVersion == "free-pro-team@latest" %} -### Dependents included +### 包含的依赖关系 -For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} +对于公共仓库，仅报告依赖于它或它发布的包的公共仓库。 对于私有仓库，不报告此信息。{% endif %} -### Using the dependency graph +### 使用依赖关系图 -You can use the dependency graph to: +您可以使用依赖关系图： -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% if currentVersion == "free-pro-team@latest" %} -- See information about vulnerable dependencies in pull requests. 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 %} +- 探索您的代码所依赖的仓库{% if currentVersion == "free-pro-team@latest" %} 以及依赖于它的仓库{% endif %}。 更多信息请参阅“[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)”。 {% if currentVersion == "free-pro-team@latest" %} +- 在单个仪表板中查看组织仓库中使用的依赖项摘要。 更多信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)”。{% endif %} +- 查看和更新仓库中有漏洞的依赖项。 更多信息请参阅“[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。{% if currentVersion == "free-pro-team@latest" %} +- 查看拉取请求中有漏洞依赖项的相关信息。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。{% endif %} -### Enabling the dependency graph +### 启用依赖关系图 -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %}要生成依赖关系图，{% data variables.product.product_name %} 需要对仓库的依赖项清单和锁定文件的只读访问权限。 依赖关系图自动为所有公共仓库生成，您可以选择为私有仓库启用它。 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" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}如果依赖项图在系统中不可用，则站点管理员可以启用依赖项图和 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上的有漏洞依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。{% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} 如果依赖项图在系统中不可用，则站点管理员可以启用依赖项图和安全警报。 更多信息请参阅“[为 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项启用安全警报](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)”。 {% endif %} -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. +首次启用依赖关系图时，将立即剖析受支持的生态系统的任何清单和锁定文件。 依赖关系图通常在几分钟之内填充，但对于依赖项很多的仓库，可能需要更长时间。 启用后，该图将在每次推送到仓库{% if currentVersion == "free-pro-team@latest" %} 以及每次推送到该图中的其他仓库{% endif %} 时自动更新。 -### Supported package ecosystems +### 支持的包生态系统 -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} +建议的格式明确定义哪些版本用于所有直接和所有间接依赖项。 如果使用这些格式，则依赖关系图更准确。 它还反映当前的构建设置，使依赖项图能够报告直接和间接依赖项中的漏洞。{% if currentVersion == "free-pro-team@latest" %} 从清单文件（或等效文件）推断的间接依赖项将不包括在漏洞依赖项检查中。{% endif %} -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | +{% if currentVersion == "free-pro-team@latest" %}下列生态系统支持依赖关系图、{% data variables.product.prodname_dependabot_alerts %} 和 {% data variables.product.prodname_dependabot_security_updates %}。{% endif %} +| +{% if currentVersion ver_gt "enterprise-server@2.21" %}下列生态系统支持依赖关系图和 {% data variables.product.prodname_dependabot_alerts %}。{% endif %} +| 包管理器 | 语言 | 建议的格式 | 所有支持的格式 | +| ------------ | --------------------- | -------------------------------------------------- | -------------------------------------------------------------------- | +| Composer | PHP | `composer.lock` | `composer.json`、`composer.lock` | +| `dotnet` CLI | .NET 语言（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`、`pipfile.lock`、`setup.py`* | +| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`、`Gemfile`、`*.gemspec` | +| Yarn | JavaScript | `yarn.lock` | `package.json`、`yarn.lock` | {% note %} -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. +**注：**如果在 `setup.py` 文件中列出 Python 依赖项，我们可能无法剖析和列出项目中的每个依赖项。 {% endnote %} -### Further reading +### 延伸阅读 -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia -- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} +- 维基百科上的“[依赖关系图](https://en.wikipedia.org/wiki/Dependency_graph)” +- “[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)” {% if currentVersion == "free-pro-team@latest" %} +- "[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" +- "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[漏洞依赖项检测疑难解答](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} 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 af57a40c27..64c58bdd9d 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 @@ -68,7 +68,7 @@ topics: 仓库管理员可以启用或禁用私有仓库的依赖关系图。 -您也可以为用户帐户或组织拥有的所有仓库启用或禁用依赖项图。 更多信息请参阅“[管理用户帐户的安全和分析设置](/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)”。 +您也可以为用户帐户或组织拥有的所有仓库启用或禁用依赖项图。 更多信息请参阅“[管理用户帐户的安全和分析设置](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)”或“[管理组织的安全和分析设置](//organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)”。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -109,7 +109,7 @@ topics: ### 延伸阅读 - "[关于依赖项图](/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)" +- "[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/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)" {% endif %} diff --git a/translations/zh-CN/content/github/working-with-github-support/submitting-a-ticket.md b/translations/zh-CN/content/github/working-with-github-support/submitting-a-ticket.md index c65580353e..4440a4f208 100644 --- a/translations/zh-CN/content/github/working-with-github-support/submitting-a-ticket.md +++ b/translations/zh-CN/content/github/working-with-github-support/submitting-a-ticket.md @@ -11,7 +11,7 @@ topics: 如果您的帐户使用付费的 {% data variables.product.prodname_dotcom %} 产品，您可以直接联系 {% data variables.contact.github_support %}。 如果您的帐户使用 {% data variables.product.prodname_free_user %} 支持用户帐户和组织，您可以联系 {% data variables.contact.contact_support %} 以报告帐户、安全和滥用问题。 更多信息请参阅“[关于 GitHub 支持](/github/working-with-github-support/about-github-support)”。 -如果您使用 {% data variables.product.prodname_ghe_server %}、{% data variables.product.prodname_ghe_cloud %} 或 {% data variables.product.premium_support_plan %}，则必须通过 {% data variables.contact.enterprise_portal %} 提交事件单。 +如果您没有企业帐户，请使用 {% data variables.contact.enterprise_portal %} 提交工单。 有关企业帐户的更多信息，请参阅“[关于企业帐户](/github/setting-up-and-managing-your-enterprise/about-enterprise-accounts)”。 ### 使用 {% data variables.contact.support_portal %}提交事件单 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 f6ca69abb9..6006a19270 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: 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.' +title: 创建 Gist +intro: '您可以创建两种 gist：{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}和秘密。 如果您准备与{% if currentVersion == "github-ae@latest" %}企业成员{% else %}全世界{% endif %}分享您的创意，请创建{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %} gist，否则请创建秘密 gist。' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -12,69 +12,67 @@ versions: github-ae: '*' --- -### About gists +### 关于 gists -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 都是一个 Git 仓库，意即可以复刻和克隆。 如果您在{% else %}在{% endif %}创建 Gist 时登录了 {% data variables.product.product_name %}，则该 Gist 将与您的帐户相关联， 当您导航到 {% data variables.gists.gist_homepage %} 时，您会在 Gist 列表中看到它。 -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. +Gist 可设为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}或秘密。 {% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %} gist 显示在 {% data variables.gists.discover_url %} 中，{% if currentVersion == "github-ae@latest" %}企业成员{% else %}人们{% endif %}可以在其中浏览新建的 gist。 它们也可供搜索，因此，如果您希望其他人查找和查看您的工作，便可使用公共 gists。 -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. +密码 gist 不会显示在 {% data variables.gists.discover_url %} 中，也不可搜索。 秘密 Gist 不是私有 Gist。 如果您将秘密 Gist 的 URL 发送给{% if currentVersion == "github-ae@latest" %}a其他企业成员{% else %}朋友{% endif %}，他们将能够看到它。 但是，如果{% if currentVersion == "github-ae@latest" %}任何其他企业成员{% else %}您不认识的人{% endif %}发现了该 URL，他们也能够看到您的 Gist。 如果需要让您的代码不被偷窥，可能要改为[创建私有仓库](/articles/creating-a-new-repository)。 {% data reusables.gist.cannot-convert-public-gists-to-secret %} {% if enterpriseServerVersions contains currentVersion %} -If your site administrator has disabled private mode, you can also use anonymous gists, which can be public or secret. +如果您的站点管理员禁用了私有模式，您也可以使用匿名 gists，可以是公共 gists 或秘密 gists。 {% data reusables.gist.anonymous-gists-cannot-be-deleted %} {% endif %} -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. +您在以下情况下会收到通知： +- 您是新 gist 的作者。 +- 有人在 gist 中提及您。 +- 单击任何 gist 顶部的 **Subscribe（订阅）**以订阅 gist。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -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)." +您可以在个人资料中置顶 Gist，使其他人更容易看到它们。 更多信息请参阅“[将项目嵌入到个人资料](/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**. 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). +通过访问 {% data variables.gists.gist_homepage %} 并单击 **All Gists（所有 Gist）**，您可以发现其他人创建的{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %} gist。 将会显示所有 gists 存储的页面，gist 按创建或更新时间显示。 您也可以通过 {% data variables.gists.gist_search_url %} 按语言搜索 gist。 Gist 搜索使用的搜索语法与[代码搜索](/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). +由于 gists 是 Git 仓库，因此您可以查看其整个提交历史记录，包括差异。 您也可以复刻或克隆 gists。 更多信息请参阅[“复刻和克隆 gists”](/articles/forking-and-cloning-gists)。 -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`. +您可以单击 gist 顶部的 **Download ZIP（下载 ZIP）**按钮下载 gist 的 ZIP 文件。 您可以将 gist 嵌入到支持 Javascript 的任何文本字段中，如博文。 要获取嵌入的代码，请单击 gist 的**嵌入** URL 旁边的剪贴板图标。 要嵌入特定的 gist 文件，请使用 `?file=FILENAME` 附加**嵌入** URL。 {% if currentVersion == "free-pro-team@latest" %} -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)." +Gist 支持地图 GeoJSON 文件。 这些地图显示在嵌入的 Gist 中，因此您可以轻松分享和嵌入地图。 更多信息请参阅“[{% data variables.product.product_name %} 上的地图 GeoJSON 文件](/articles/mapping-geojson-files-on-github)”。 {% endif %} -### Creating a gist +### 创建 Gist -You can also drag and drop a text file from your desktop directly into the gist editor. +按照以下步骤创建 gist。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% note %} -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. +您也可以使用 {% data variables.product.prodname_cli %} 创建 Gist。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh Gist 创建`](https://cli.github.com/manual/gh_gist_create)”。 + +或者，也可以将桌面上的文本文件直接拖放到编辑器中。 {% endnote %} {% endif %} -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) +1. 登录 {% data variables.product.product_name %}。 +2. 导航到 {% data variables.gists.gist_homepage %}。 +3. 键入 Gist 的说明（可选）和名称。 ![Gist 名称说明](/assets/images/help/gist/gist_name_description.png) -4. Type the text of your gist into the gist text box. -![Gist text box](/assets/images/help/gist/gist_text_box.png) +4. 在 Gist 文本框中键入 Gist 的文本内容。 ![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 %} +5. （可选）要创建{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %} gist，请单击 {% octicon "triangle-down" aria-label="The downwards triangle icon" %}，然后单击**创建{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %} gist**。 ![选择 Gist 可见性的下拉菜单]{% 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) +6. 单击 **Create secret Gist（创建秘密 Gist）**或**创建{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %} gist**。 ![创建 Gist 的按钮](/assets/images/help/gist/create-secret-gist-button.png) diff --git a/translations/zh-CN/content/index.md b/translations/zh-CN/content/index.md index 8fe13b7d18..cf0f029e00 100644 --- a/translations/zh-CN/content/index.md +++ b/translations/zh-CN/content/index.md @@ -13,5 +13,43 @@ featuredLinks: - /github/getting-started-with-github/managing-remote-repositories - /github/working-with-github-pages versions: '*' +children: + - github + - 管理员 + - 组织 + - code-security + - 操作 + - 包 + - developers + - rest + - graphql + - insights + - 讨论 + - 社区 + - 页面 + - 教育版 + - 电脑版 + - early-access +externalProducts: + cli: + id: cli + name: GitHub CLI + href: 'https://cli.github.com/manual' + external: true + atom: + id: atom + name: Atom + href: 'https://atom.io/docs' + external: true + electron: + id: electron + name: Electron + href: 'https://electronjs.org/docs' + external: true + codeql: + id: codeql + name: 'CodeQL' + href: 'https://codeql.github.com/docs' + external: true --- diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md new file mode 100644 index 0000000000..b15037900d --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -0,0 +1,33 @@ +--- +title: 关于组织 +intro: 组织是共享帐户，其中业务和开源项目可一次协助处理多个项目。 所有者和管理员可通过复杂的安全和管理功能管理成员对组织数据和项目的访问。 +redirect_from: + - /articles/about-organizations + - /github/setting-up-and-managing-organizations-and-teams/about-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.organizations.organizations_include %} + +{% if currentVersion == "free-pro-team@latest" %} +### 组织和企业帐户 + +企业帐户允许所有者集中管理多个 {% data variables.product.prodname_dotcom_the_website %} 组织的策略和帐单。 + +对于属于企业帐户的组织，帐单在企业帐户级别管理，并且帐单设置在组织级别不可用。 企业所有者可以为企业帐户中的所有组织设置策略，或者允许组织所有者在组织级别设置策略。 组织所有者无法更改在企业帐户级对组织执行的设置。 如果对组织的策略或设置有疑问，请联系企业帐户的所有者。 + +{% data reusables.gated-features.enterprise-accounts %} + +{% data reusables.organizations.org-ownership-recommendation %} 更多信息请参阅“[管理组织的所有权连续性](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)”。 + +### 组织的服务条款和数据保护 + +实体（如公司、非营利组织或集团）可同意用于其组织的标准服务条款或公司服务条款。 更多信息请参阅“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。 + +{% endif %} diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md new file mode 100644 index 0000000000..5914662ee2 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -0,0 +1,49 @@ +--- +title: 关于组织仪表板 +intro: '作为组织成员，您可以全天访问组织仪表板，以了解近期活动的最新信息，跟踪您参与的议题和拉取请求，或者关注组织。' +redirect_from: + - /articles/about-your-organization-dashboard + - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### 访问组织仪表板 + +{% data reusables.dashboard.access-org-dashboard %} + +### 查找近期活动 + +在消息馈送的“Recent activity（最近活动）”部分，您可以快速找到并跟进组织中最近更新的议题和拉取请求。 + +{% data reusables.dashboard.recent-activity-qualifying-events %} + +### 查找组织中的仓库 + +在仪表板的左侧栏中，可以访问您参与的组织顶部仓库。 + +![组织中您参与最多的仓库列表](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) + +### 了解组织中活动的最新信息 + +在消息馈送的“All activity（所有活动）”部分，您可以查看来自组织中其他团队和仓库的更新。 + +“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)”。 + +例如，当组织中有人执行以下操作时，组织消息馈送会显示更新： + - 创建新分支。 + - 评论议题或拉取请求。 + - 提交拉取请求审查评论。 + - 对仓库复刻。 + - 创建 wiki 页面。 + - 推送提交。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} + - 创建公共仓库。{% endif %} + +### 更多信息 + +- "[关于个人仪表板](/articles/about-your-personal-dashboard)" diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md new file mode 100644 index 0000000000..63a789a1c3 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -0,0 +1,26 @@ +--- +title: 关于组织的消息馈送 +intro: 您可以使用组织的消息馈送跟进该组织拥有的仓库上的近期活动。 +redirect_from: + - /articles/news-feed/ + - /articles/about-your-organization-s-news-feed + - /articles/about-your-organizations-news-feed + - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织的消息馈送显示其他人在该组织拥有的仓库上的活动。 您可以使用组织的消息馈送来查看何时有人打开、关闭或合并议题或拉取请求，创建或删除分支，创建标记或发行版，评论议题，拉取请求，或者提交或推送提交到 {% data variables.product.product_name %}。 + +### 访问组织的消息馈送 + +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. 从下拉菜单中选择组织。{% 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/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md new file mode 100644 index 0000000000..321209186a --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -0,0 +1,34 @@ +--- +title: 访问组织的设置 +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 + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings +intro: '组织帐户设置页面提供几种管理帐户的方式，如帐单、团队成员资格和仓库设置。' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% tip %} + +**提示：**只有组织所有者和帐单管理员可以查看及更改组织的帐单信息与帐户设置。 {% 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/zh-CN/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md new file mode 100644 index 0000000000..b7ee965968 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md @@ -0,0 +1,28 @@ +--- +title: 从头开始创建新组织 +intro: 创建组织以对仓库应用更细化的访问权限。 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +redirect_from: + - /articles/creating-a-new-organization-from-scratch + - /admin/user-management/creating-organizations + - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch +topics: + - 组织 + - 团队 +--- + +从头开始创建新组织时，它没有任何与之关联的仓库。 有关为组织添加仓库的更多信息，请参阅“[创建新仓库](/articles/creating-a-new-repository)”和“[转让仓库](/articles/transferring-a-repository)”。 + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. 按照提示创建组织。 {% if currentVersion == "free-pro-team@latest" %}要详细了解可用于您的团队的计划，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。{% endif %} + +### 延伸阅读 + +{% if currentVersion == "free-pro-team@latest" %} +- "[设置帐单邮箱](/articles/setting-your-billing-email)"{% endif %} +- "[关于组织](/articles/about-organizations)" diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md new file mode 100644 index 0000000000..bb5022a581 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md @@ -0,0 +1,22 @@ +--- +title: 与组织中的团体协作 +intro: 组织帐户中的人员团体可同时跨多个项目展开协作。 +redirect_from: + - /articles/creating-a-new-organization-account/ + - /articles/collaborating-with-groups-in-organizations + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md new file mode 100644 index 0000000000..4de46609a3 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -0,0 +1,50 @@ +--- +title: 查看组织的洞察 +intro: '组织洞察提供有关组织的活动、贡献和依赖项的数据。' +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/viewing-insights-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +组织的所有成员均可查看组织洞察。 更多信息请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。 + +您可以使用组织活动洞察来帮助您更好地了解组织成员如何使用 {% data variables.product.product_name %} 进行协作和处理代码。 依赖项洞察可帮助您跟踪、报告和处理组织的开源使用情况。 + +### 查看组织活动洞察 + +{% note %} + +**注：**组织活动目前处于公开测试阶段，随时可能发生变化。 + +{% endnote %} + +通过组织活动洞察，您可以查看整个组织或特定仓库每周、每月和每年的数据可视化，包括议题和拉取请求活动、热门使用语言以及有关组织成员花费其时间累积的信息。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. 在组织名称下，单击 {% octicon "graph" aria-label="The bar graph icon" %} **Insights（洞察）**。 ![单击组织洞察选项卡](/assets/images/help/organizations/org-nav-insights-tab.png) +4. （可选）在页面的右上角，选择查看过去 **1 周**、**1 个月**或 **1 年**的数据。 ![选择查看组织洞察的时间段](/assets/images/help/organizations/org-insights-time-period.png) +5. （可选）在页面的右上角，选择查看最多三个仓库的数据，然后单击 **Apply（应用）**。 ![选择查看组织洞察的仓库](/assets/images/help/organizations/org-insights-repos.png) + +### 查看组织依赖项洞察 +通过依赖项洞察，您可以查看组织所依赖的开源项目的漏洞、许可证和其他重要信息。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +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（许可证）**图表中的结果，按漏洞状态、许可证或两者的组合进行过滤。 ![我的组织漏洞和许可证图表](/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) + +### 延伸阅读 + - "[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)" + - "[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" + - “[更改组织依赖项洞察的可见性](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)” + - "[在企业帐户中实施关于依赖项洞察的策略](/github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)" diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md new file mode 100644 index 0000000000..6ed755d221 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -0,0 +1,49 @@ +--- +title: 关于团队讨论 +intro: '您的团队可以共同计划、互相更新，或者在组织中团队页面的讨论帖子中讨论任何主题。' +redirect_from: + - /articles/about-team-discussions + - /github/building-a-strong-community/about-team-discussions + - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 社区 +--- + +{% data reusables.organizations.team-discussions-purpose %} + +任何组织成员都可以在团队的页面上发帖或参与公共讨论。 {% data reusables.organizations.team-discussions-permissions %} + +![具有公共和私人讨论的团队页面的讨论选项卡](/assets/images/help/organizations/team-page-discussions-tab.png) + +您可以在其他位置链接到任何团队讨论以引用它。 您可以将重要帖子嵌入到团队页面，便于以后快速参考。 更多信息请参阅“[嵌入团队讨论](/organizations/collaborating-with-your-team/pinning-a-team-discussion)”。 + +![具有嵌入讨论的团队页面的嵌入讨论选项卡](/assets/images/help/organizations/team-discussions-pinned.png) + +{% data reusables.organizations.team-discussions-default %} 所有者可对整个组织禁用团队讨论。 更多信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”。 + +### 团队讨论通知 + +当有人在团队页面上发帖或回复公共讨论时，团队成员和任何子团队的成员都会收到电子邮件或 web 通知。 当有人在团队页面上对私人讨论发帧或回复时，只有团队成员才会收到通知。 + +{% tip %} + +**提示：**根据通知设置，您将通过电子邮件和/或 {% data variables.product.product_name %} 上的 web 通知页面收到更新。 更多信息请参阅 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”和“[关于 web 通知](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}”。 + +{% endtip %} + +默认情况下，如果团队讨论中提及您的用户名，则对于提及您的用户名的帖子，您将收到其通知以及所有回复。 此外，默认情况下，如果您回复帖子，该帖子有其他回复您也会收到通知。 + +要关闭团队讨论的通知，您可以取消订阅特定的讨论帖子，或者更改通知设置，以取消关注或完全忽略特定团队的讨论。 即使您取消关注团队的讨论，也可订阅特定讨论帖子的通知。 + +更多信息请参阅 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}“[订阅和退订通知](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}”和“[嵌套的团队](/articles/about-teams/#nested-teams)”。 + +### 延伸阅读 + +- "[关于 {% data variables.product.prodname_dotcom %} 中的对话](/articles/about-conversations-on-github)" +- "[关于团队](/articles/about-teams)" +- "[创建团队讨论](/organizations/collaborating-with-your-team/creating-a-team-discussion)" +- "[编辑或删除团队讨论](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md new file mode 100644 index 0000000000..7d14223d7c --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md @@ -0,0 +1,30 @@ +--- +title: 创建团队讨论 +intro: '任何组织成员都可以创建公开的团队讨论帖子。 要创建私密的团队讨论帖子，您必须是团队成员或组织所有者。' +redirect_from: + - /articles/creating-a-team-discussion + - /github/building-a-strong-community/creating-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 社区 +--- + +{% data reusables.organizations.team-discussions-permissions %} 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/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. 输入团队讨论标题和评论以开始对话。 ![新的团队讨论评论](/assets/images/help/projects/team-discussions-comment.png) +7. （可选）使用下拉菜单选择您的帖子是私密还是公开。 ![团队讨论隐私设置菜单](/assets/images/help/projects/team-discussions-privacy-menu.png) +8. 单击 **Comment（注释）**。 ![创建新的团队讨论评论按钮](/assets/images/help/projects/team-discussions-comment-button.png) + +### 延伸阅读 + + - "[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[编辑或删除团队讨论](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" + - "[嵌入团队讨论](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md new file mode 100644 index 0000000000..980b5cffcf --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md @@ -0,0 +1,28 @@ +--- +title: 编辑或删除团队讨论 +intro: '组织成员可在编辑或删除团队页面上的讨论 如果您是组织成员，您可以编辑或删除讨论。' +redirect_from: + - /articles/editing-or-deleting-a-team-discussion + - /github/building-a-strong-community/editing-or-deleting-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 社区 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +6. 单击要编辑或删除的团队讨论旁边的 {% octicon "kebab-horizontal" aria-label="The edit icon" %}。 +7. 单击 **Edit（编辑）**。 可选择单击 **Delete（删除）**。 ![编辑团队讨论按钮](/assets/images/help/projects/edit-team-discussions-button.png) +8. 根据需要修改团队讨论标题和评论，然后单击 **Update comment（更新评论）**。 ![更新评论按钮](/assets/images/help/projects/update-comment-button.png) + +### 延伸阅读 + + - "[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[创建团队讨论](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[嵌入团队讨论](/organizations/collaborating-with-your-team/pinning-a-team-discussion)" diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/index.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/index.md new file mode 100644 index 0000000000..7af1f7cce6 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/index.md @@ -0,0 +1,19 @@ +--- +title: 与您的团队协作 +intro: '在组织内，您的团队可使用团队讨论功能展开跨项目协作。' +redirect_from: + - /articles/collaborating-with-your-team + - /github/building-a-strong-community/collaborating-with-your-team + - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 社区 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md new file mode 100644 index 0000000000..20febaa722 --- /dev/null +++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md @@ -0,0 +1,26 @@ +--- +title: 固定团队讨论 +intro: '您可以将重要的讨论固定到组织的团队页面，以便于参考，也可取消固定不再相关的讨论。' +redirect_from: + - /articles/pinning-a-team-discussion + - /github/building-a-strong-community/pinning-a-team-discussion + - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 社区 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-discussions-tab %} +5. 单击要固定的团队讨论旁边的 {% octicon "pin" aria-label="The pin icon" %}。 单击该图标也可以取消固定讨论。 ![固定讨论](/assets/images/help/projects/pin-discussion-button.png) + +### 延伸阅读 + + - "[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)" + - "[创建团队讨论](/organizations/collaborating-with-your-team/creating-a-team-discussion)" + - "[编辑或删除团队讨论](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)" diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md new file mode 100644 index 0000000000..f9bc27722c --- /dev/null +++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -0,0 +1,26 @@ +--- +title: 关于双重身份验证和 SAML 单点登录 +intro: 组织管理员可启用 SAML 单点登录及双重身份验证，为其组织成员增加额外的身份验证措施。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-two-factor-authentication-and-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +双重身份验证 (2FA) 为组织成员提供基本验证。 通过启用 2FA，组织管理员可降低成员的 {% data variables.product.product_name %} 帐户被盗的可能性。 有关 2FA 的更多信息，请参阅“[关于双重身份验证](/articles/about-two-factor-authentication)”。 + +为增加额外的身份验证措施，组织管理员也可[启用 SAML 单点登录 (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)，这样组织成员必须使用单点登录来访问组织。 有关 SAML SSO 的更多信息，请参阅“[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)”。 + +如果同时启用了 2FA 和 SAML SSO，组织成员必须执行以下操作： +- 使用 2FA 登录其 {% data variables.product.product_name %} 帐户 +- 使用单点登录访问组织 +- 使用授权用于 API 或 Git 访问的令牌，并使用单点登录授权令牌 + +### 延伸阅读 + +- "[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md new file mode 100644 index 0000000000..516a929c2e --- /dev/null +++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md @@ -0,0 +1,16 @@ +--- +title: 使用 SAML 单点登录授予对组织的访问 +intro: '组织管理员可使用 SAML 单点登录授予对其组织的访问。 此访问权限可授予组织成员、自动程序和服务帐户。' +redirect_from: + - /articles/granting-access-to-your-organization-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md new file mode 100644 index 0000000000..f24278228b --- /dev/null +++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md @@ -0,0 +1,25 @@ +--- +title: 使用 SAML 单点登录管理自动程序和服务帐户 +intro: 启用了 SAML 单点登录的组织可保留对自动程序和服务帐户的访问权限。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on + - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +要保留对自动程序和服务帐户的访问权限，组织可以对组织[启用](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)但**不**[实施](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML 单点登录。 如果需要对组织实施 SAML 单点登录，您可以通过身份提供程序 (IdP) 为自动程序或服务帐户创建外部身份。 + +{% warning %} + +**注：**如果对组织实施 SAML 单点登录但**未**通过 IdP 为自动程序和服务帐户设置外部身份，它们将会从组织中删除。 + +{% endwarning %} + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md new file mode 100644 index 0000000000..f4e3c60f16 --- /dev/null +++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -0,0 +1,64 @@ +--- +title: 查看和管理成员对组织的 SAML 访问 +intro: '您可以查看和撤销组织成员的链接身份、活动会话和授权凭据。' +permissions: 组织所有者可以查看和管理成员对组织的 SAML 访问。 +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 + - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +### 关于对组织的 SAML 访问 + +对组织启用 SAML 单点登录时，每个组织成员都可以将其在身份提供程序 (IdP) 上的外部身份链接到其现有的 {% data variables.product.product_name %} 帐户。 要在 {% data variables.product.product_name %} 上访问组织的资源，成员必须在其浏览器中启动 SAML 会话。 要使用 API 或 Git 访问组织的资源，成员必须使用被授权用于组织的个人访问令牌或 SSH 密钥。 + +您可以在同一页面上查看和撤销每个成员的链接身份、活动会话和授权凭据。 + +### 查看和撤销链接的身份 + +{% 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 %} + +### 查看和撤销活动的 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 %} + +### 查看和撤销授权的凭据 + +{% 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 %} + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[查看和管理用户对企业帐户的 SAML 访问](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)" diff --git a/translations/zh-CN/content/organizations/index.md b/translations/zh-CN/content/organizations/index.md new file mode 100644 index 0000000000..03ac21fe15 --- /dev/null +++ b/translations/zh-CN/content/organizations/index.md @@ -0,0 +1,32 @@ +--- +title: 组织和团队 +shortTitle: 组织 +intro: 跨多个项目协作，同时管理对项目和数据的访问，并为组织自定义设置。 +redirect_from: + - /articles/about-improved-organization-permissions/ + - /categories/setting-up-and-managing-organizations-and-teams + - /github/setting-up-and-managing-organizations-and-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% link_with_intro /collaborating-with-groups-in-organizations %} +{% link_with_intro /managing-membership-in-your-organization %} +{% link_with_intro /managing-peoples-access-to-your-organization-with-roles %} +{% link_with_intro /organizing-members-into-teams %} +{% link_with_intro /collaborating-with-your-team %} +{% link_with_intro /managing-access-to-your-organizations-repositories %} +{% link_with_intro /managing-access-to-your-organizations-project-boards %} +{% link_with_intro /managing-access-to-your-organizations-apps %} +{% link_with_intro /managing-organization-settings %} +{% link_with_intro /restricting-access-to-your-organizations-data %} +{% link_with_intro /keeping-your-organization-secure %} +{% link_with_intro /managing-saml-single-sign-on-for-your-organization %} +{% link_with_intro /granting-access-to-your-organization-with-saml-single-sign-on %} +{% link_with_intro /managing-git-access-to-your-organizations-repositories %} +{% link_with_intro /migrating-to-improved-organization-permissions %} diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md new file mode 100644 index 0000000000..14148d4e6d --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md @@ -0,0 +1,24 @@ +--- +title: 保护组织安全 +intro: '组织所有者有多项功能来帮助保护其项目和数据的安全。 如果您是组织的所有者，应定期检查组织的审核日志{% if currentVersion != "github-ae@latest" %}、成员 2FA 状态{% endif %} 和应用程序设置，以确保没有未授权或恶意的活动。' +redirect_from: + - /articles/preventing-unauthorized-access-to-organization-information/ + - /articles/keeping-your-organization-secure + - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md new file mode 100644 index 0000000000..42684b40e4 --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md @@ -0,0 +1,76 @@ +--- +title: 管理组织允许的 IP 地址 +intro: 您可以通过配置允许连接的 IP 地址列表来限制对组织资产的访问。 +product: '{% data reusables.gated-features.allowed-ip-addresses %}' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者可以管理组织允许的 IP 地址。 + +### 关于允许的 IP 地址 + +您可以通过为特定 IP 地址配置允许列表来限制对组织资产的访问。 {% 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 %} + +您还可以为企业帐户中的组织配置允许的 IP 地址。 更多信息请参阅{% if currentVersion == "github-ae@latest" %}“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”。 {% else %}“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)”。{% endif %} + +### 添加允许的 IP 地址 + +{% 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 %} + +### 启用允许的 IP 地址 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +3. 在“IP allow list（IP 允许列表）”下，选择 **Enable IP allow list（启用 IP 允许列表）**。 ![允许 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) +4. 单击 **Save（保存）**。 + +### 编辑允许的 IP 地址 + +{% 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. 单击 **Update（更新）**。 + +### 删除允许的 IP 地址 + +{% 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 %} + +### 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表 + +{% if currentVersion == "github-ae@latest" %} + +{% data reusables.github-actions.ip-allow-list-hosted-runners %} + +{% else %} + +{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} + +{% endif %} diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md new file mode 100644 index 0000000000..f942a533e1 --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -0,0 +1,143 @@ +--- +title: 管理组织的安全性和分析设置 +intro: '您可以控制功能以保护组织在 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。' +permissions: 组织所有者可以管理组织中仓库的安全性和分析设置。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### 关于安全性和分析设置的管理 + +{% 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 %} + +### 显示安全和分析设置 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security-and-analysis %} + +显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。 + +{% if currentVersion == "free-pro-team@latest" %}如果您的组织属于具有 {% data variables.product.prodname_GH_advanced_security %} 许可的企业，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %}如果您具有 {% data variables.product.prodname_GH_advanced_security %} 许可，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %} + +{% if currentversion == "github-ae@latest" %}该页面还将包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。{% endif %} + +### 为所有现有仓库启用或禁用功能 + +您可以启用或禁用所有仓库的功能。 {% if currentVersion == "free-pro-team@latest" %}您的更改对组织中仓库的影响取决于其可见性： + +- **依赖项图** - 您的更改仅影响私有仓库，因为该功能对公共仓库始终启用。 +- **{% 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 %} + +{% data reusables.advanced-security.note-org-enable-uses-seats %} + +1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 +2. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}如果您的 {% data variables.product.prodname_GH_advanced_security %} 许可中没有可用的席位，对“{% data variables.product.prodname_GH_advanced_security %}”的控制将会禁用。{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + !["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 %} + {% if currentVersion == "github-ae@latest" %} + !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) + {% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +3. （可选）为组织中的新仓库默认启用该功能。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![新仓库的"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 %} +4. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![用于禁用或启用功能的按钮](/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 %} + {% endif %} + {% if currentVersion == "github-ae@latest" %} +3. Click **Enable for all eligible repositories** to enable the feature for all the new repositories in your organization that will have {% data variables.product.prodname_advanced_security %} enabled. ![用于为组织中所有符合条件的仓库启用功能的按钮](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png) + {% endif %} + + {% data reusables.security.displayed-information %} + +### 添加新仓库时自动启用或禁用功能 + +1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 +2. 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" or currentVersion ver_gt "enterprise-server@3.0" %} + ![用于对新仓库启用或禁用功能的复选框](/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 %} + {% if currentVersion == "github-ae@latest" %} + ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) + {% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +### 允许 {% data variables.product.prodname_dependabot %} 访问私有依赖项 + +{% data variables.product.prodname_dependabot %} 可以检查项目中过时的依赖项引用，并自动生成拉取请求来更新它们。 为此，{% data variables.product.prodname_dependabot %} 必须有权访问所有目标依赖项文件。 通常，如果一个或多个依赖项无法访问，版本更新将失败。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot %} 版本更新](/github/administering-a-repository/about-dependabot-version-updates)”。 + +默认情况下，{% data variables.product.prodname_dependabot %} 无法更新位于私有仓库或私有仓库注册表中的依赖项。 但是，如果依赖项位于与使用该依赖项之项目相同的组织内的私有 {% data variables.product.prodname_dotcom %} 仓库中，则可以通过授予对主机仓库的访问权限来允许 {% data variables.product.prodname_dependabot %} 成功更新版本。 + +如果您的代码依赖于私有注册表中的软件包，您可以在仓库级别进行配置，允许 {% data variables.product.prodname_dependabot %} 更新这些依赖项的版本。 可通过将身份验证详细信息添加到仓库的 _dependabot.yml_ 文件来做到这一点。 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)。” + +要允许 {% data variables.product.prodname_dependabot %} 访问私有 {% data variables.product.prodname_dotcom %} 仓库： + +1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 +1. 在“{% data variables.product.prodname_dependabot %} 私有仓库访问”下，单击 **Add private repositories（添加私有仓库）**或 **Add internal and private repositories（添加内部和私有仓库）**。 ![添加仓库按钮](/assets/images/help/organizations/dependabot-private-repository-access.png) +1. 开始键入要允许的仓库的名称。 ![添加仓库按钮](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. 单击您想要允许的仓库。 + +1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}. !["X" 按钮来删除仓库。](/assets/images/help/organizations/dependabot-private-repository-list.png) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### 从组织中的个别仓库中移除对 {% data variables.product.prodname_GH_advanced_security %} 的访问权限 + +您可以从仓库的“Settings（设置）”选项卡管理对仓库 {% data variables.product.prodname_GH_advanced_security %} 功能的访问。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 但您也可以从“Settings（设置）”选项卡对仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 功能。 + +1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 +1. 要查看您组织中启用 {% data variables.product.prodname_GH_advanced_security %} 的所有仓库的列表，请滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png) 表格列出了每个仓库的唯一提交者数量。 这是您可以通过移除 {% data variables.product.prodname_GH_advanced_security %} 访问权限释放的席位数。 您的许可证大小显示在组织级许可证中。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的许可](/github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security)”。 +1. 要从仓库删除对 {% data variables.product.prodname_GH_advanced_security %} 的访问，并释放任何提交者使用的对仓库唯一的席位，请单击相邻的 {% octicon "x" aria-label="X symbol" %}。 +1. 在确认对话框中，单击击 **Remove repository（移除仓库）** 以移除对 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限。 + +{% note %} + +**注意：**如果移除对仓库 {% data variables.product.prodname_GH_advanced_security %} 的访问权限， 您应该与受影响的开发团队进行沟通，以便他们知道改变的意图。 这确保他们不会浪费时间调试运行失败的代码扫描。 + +{% endnote %} + +{% 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 %}{% if currentVersion != "github-ae@latest" %} +- “[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)” +- "[管理项目依赖项中的漏洞](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %} diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..658d5b527b --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md @@ -0,0 +1,23 @@ +--- +title: 准备在组织中要求双重身份验证 +intro: '在要求双重身份验证 (2FA) 之前，您可以向用户通知即将发生的更改，并验证谁已使用 2FA。' +redirect_from: + - /articles/preparing-to-require-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +如果您的组织中需要 2FA，建议至少提前一周通知{% if currentVersion == "free-pro-team@latest" %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}。 + +需要对您的组织使用双重身份验证时，不使用 2FA 的成员、外部协作者和帐单管理员（包括自动程序帐户）将从组织中删除，并且失去访问其仓库的权限。 他们还会失去对组织私有仓库的复刻的访问权限。 + +在组织中要求 2FA 之前，建议： + - 在个人帐户上[启用 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) + - 要求组织中的人员为其帐户设置 2FA + - 查看[组织中的用户是否启用 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/) + - 提醒用户：2FA 一旦启用，没有 2FA 的用户会自动从组织中删除 diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md new file mode 100644 index 0000000000..274fe37fae --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md @@ -0,0 +1,80 @@ +--- +title: 您的组织中需要双重身份验证 +intro: '组织所有者可以要求{% if currentVersion == "free-pro-team@latest" %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}为其个人帐户启用双重身份验证，从而使恶意行为者更难以访问组织的仓库和设置。' +redirect_from: + - /articles/requiring-two-factor-authentication-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +### 关于组织的双重身份验证 + +{% 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" %} + +您还可以要求企业中的组织使用双重身份验证。 更多信息请参阅“[在企业帐户中实施安全设置](/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 %} + +**警告：** + +- 要求您的组织使用双重身份验证时，不使用 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 %} + +{% data reusables.two_fa.auth_methods_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" %}组织成员、外部协作者和帐单管理员{% else %}组织成员和外部协作者{% endif %}，要求他们为其帐户设置 2FA。 您可以查看成员和外部协作者是否已经使用 2FA。 更多信息请参阅“[查看组织中的用户是否已启用 2FA](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)”。 + +### 您的组织中需要双重身份验证 + +{% 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. 如果从组织中删除了任何成员或外部协作者，我们建议向他们发送邀请，以恢复其以前对组织的权限和访问权限。 他们必须启用双重身份验证，然后才能接受您的邀请。 +{% endif %} + +### 查看从您的组织中删除的人员 + +要查看在您要求双重身份验证时因为不合规而被从组织中自动删除的人员，您可以对从组织中删除的人员[搜索组织的审核日志](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log)。 审核日志事件将显示是否因为 2FA 不合规而删除该人员。 + +![显示因 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. 输入您的搜索查询。 要搜索： + - 删除的组织成员，请在搜索查询中使用 `action:org.remove_member` + - 删除的外部协作者，请在搜索查询中使用 `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)查看从组织中删除的人员。 + +### 帮助被删除的成员和外部协作者重新加入您的组织 + +如果在您启用双重身份验证使用要求时有任何成员或外部协作者被从组织中删除，他们将收到通知他们已被删除的电子邮件。 他们应当为个人帐户启用双重身份验证，并联系组织所有者来请求您的组织的访问权限。 + +### 延伸阅读 + +- “[查看组织中的用户是否已启用 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)” +- “[使用双重身份验证 (2FA) 保护您的帐户](/articles/securing-your-account-with-two-factor-authentication-2fa)” +- “[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)” +- “[恢复前外部协作者对组织的访问权限](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)” diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md new file mode 100644 index 0000000000..09a9c1b8e3 --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md @@ -0,0 +1,31 @@ +--- +title: 将电子邮件通知限于已批准的域 +intro: '为防止将组织信息泄露到个人帐户，组织所有者可以将关于组织活动的电子邮件通知限于经过验证的域。' +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 + - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +### 关于电子邮件限制 + +当组织中启用了受限电子邮件通知时，成员只能使用与组织的已验证域相关联的电子邮件地址来接收有关组织活动的电子邮件通知。 更多信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”。 + +外部协作者不受限于已验证域的电子邮件通知。 有关外部协作者的更多信息，请参阅“[组织的权限级别](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)”。 + +如果您的组织由企业帐户拥有，则组织成员除了能够接收来自组织的任何已验证域的通知之外，还能够接收来自企业帐户的任何已验证域的通知。 更多信息请参阅“[验证企业帐户的域](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)”。 + +### 将电子邮件通知限于已批准的域 + +{% 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. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md new file mode 100644 index 0000000000..c8608a3837 --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -0,0 +1,643 @@ +--- +title: 审查组织的审核日志 +intro: '审核日志允许组织管理员快速审查组织成员执行的操作。 其中包含操作执行人、操作内容和执行时间等详细信息。' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/reviewing-the-audit-log-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### 访问审核日志 + +审核日志列出过去 90 天内影响组织的活动触发的事件。 只有所有者才能访问组织的审核日志。 + +{% 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 %} + +### 搜索审核日志 + +{% data reusables.audit_log.audit-log-search %} + +#### 基于执行的操作搜索 + +要搜索特定事件，请在查询中使用 `action` 限定符。 审核日志中列出的操作分为以下类别： + +| 类别名称 | 描述 | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} +| [`帐户`](#account-category-actions) | 包含与组织帐户相关的所有活动。 | +| [`advisory_credit`](#advisory_credit-category-actions) | 包含与 {% data variables.product.prodname_advisory_database %} 中安全通告的贡献者积分相关的所有活动。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 | +| [`计费，帐单`](#billing-category-actions) | 包含与组织帐单相关的所有活动。 | +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | 包含现有仓库中 {% data variables.product.prodname_dependabot %} 警报的组织级配置活动。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 | +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | 包含组织新建仓库中 {% data variables.product.prodname_dependabot %} 警报的组织级配置活动。 | +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | 包含现有仓库中 {% data variables.product.prodname_dependabot_security_updates %} 的组织级配置活动。 更多信息请参阅“[配置 {% 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) | 包含组织新建仓库中 {% data variables.product.prodname_dependabot_security_updates %} 的组织级配置活动。 | +| [`dependency_graph`](#dependency_graph-category-actions) | 包含仓库依赖项图的组织级配置活动。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 | +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | 包含组织新建仓库的组织级配置活动。{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | 包含与发布到团队页面的讨论相关的所有活动。 | +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | 包含与回复发布到团队页面的讨论相关的所有活动。 | +| [`挂钩`](#hook-category-actions) | 包含与 web 挂钩相关的所有活动。 | +| [`integration_installation_request`](#integration_installation_request-category-actions) | 包含与组织成员请求所有者批准用于组织的集成相关的所有活动。 | +| [`议题`](#issue-category-actions) | 包含与删除议题相关的活动。 |{% if currentVersion == "free-pro-team@latest" %} +| [`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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | 包含与管理组织仓库的 {% data variables.product.prodname_pages %} 站点发布相关的所有活动。 更多信息请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 |{% endif %} +| [`org`](#org-category-actions) | 包含与组织成员身份相关的活动。{% if currentVersion == "free-pro-team@latest" %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | 包含与授权凭据用于 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) | 包含与组织中仓库的默认标签相关的所有活动。{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | 包含与 OAuth 应用程序相关的所有活动。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`包`](#packages-category-actions) | 包含与 {% data variables.product.prodname_registry %} 相关的所有活动。{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`payment_method`](#payment_method-category-actions) | 包含与组织如何支付 GitHub 相关的所有活动。{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | 包含与组织的头像相关的所有活动。 | +| [`project`](#project-category-actions) | 包含与项目板相关的所有活动。 | +| [`protected_branch`](#protected_branch-category-actions) | 包含与受保护分支相关的所有活动。 | +| [`repo`](#repo-category-actions) | 包含与组织拥有的仓库相关的所有活动。{% if currentVersion == "free-pro-team@latest" %} +| [`repository_advisory`](#repository_advisory-category-actions) | 包含与 {% data variables.product.prodname_advisory_database %} 中的安全通告相关的仓库级活动。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 | +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | 包含与[启用或禁用私有仓库的数据使用](/articles/about-github-s-use-of-your-data)相关的所有活动。{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | 包含与启用或禁用依赖项图相关的仓库级活动 | +| {% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库。 更多信息请参阅“[关于依赖项图](/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" or currentVersion == "github-ae@latest" %} | | +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | 包含与密码扫描相关的仓库级活动。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 |{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | 包含与[有漏洞依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)相关的所有活动。{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | 包含 {% data variables.product.prodname_dependabot %} 警报的仓库级配置活动。 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| [`secret_scanning`](#secret_scanning-category-actions) | 包含现有仓库中密码扫描的组织级配置活动。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 | +| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | 包含组织新建仓库中密码扫描的组织级配置活动。 |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | 包含与与赞助者按钮相关的所有事件（请参阅“[在仓库中显示赞助者按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）{% endif %} +| [`团队`](#team-category-actions) | 包含与您的组织中的团队相关的所有活动。 | +| [`team_discussions`](#team_discussions-category-actions) | 包含与管理组织的团队讨论相关的活动。 | + +您可以使用这些词搜索特定的操作集。 例如： + + * `action:team` 会找到团队类别中的所有事件。 + * `-action:hook` 会排除 web 挂钩类别中的所有事件。 + +每个类别都有一组可进行过滤的关联操作。 例如： + + * `action:team.create` 会找到团队创建处的所有事件。 + * `-action:hook.events_changed` 会排除 web 挂钩上事件已经改动的所有事件。 + +#### 基于操作时间搜索 + +使用 `created` 限定符在审核日志中根据事件发生的时间过滤事件。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +例如： + + * `created:2014-07-08` 会找到在 2014 年 7 月 8 日发生的所有事件。 + * `created:>=2014-07-08` 查找在 2014 年 7 月 8 日或之后发生的所有事件。 + * `created:<=2014-07-08` 查找在 2014 年 7 月 8 日或之前发生的所有事件。 + * `created:2014-07-01..2014-07-31` 会找到在 2014 年 7 月发生的所有事件。 + +审核日志包含过去 90 天的数据，但使用 `created` 限定符可搜索更早发生的事件。 + +#### 基于位置搜索 + +使用限定符 `country`，您可以在审核日志中根据发生事件的国家/地区过滤事件。 您可以使用国家/地区的两字母短代码或完整名称。 请注意，名称中包含空格的国家/地区需要加引号。 例如： + + * `country:de` 会找到在德国发生的所有事件。 + * `country:Mexico` 会找到在墨西哥发生的所有事件。 + * `country:"United States"` 会找到在美国发生的所有事件。 + +{% if currentVersion == "free-pro-team@latest" %} +### 导出审核日志 + +{% data reusables.audit_log.export-log %} +{% data reusables.audit_log.exported-log-keys-and-values %} +{% endif %} + +### 使用审核日志 API + +您可以使用 GraphQL API{% if currentVersion == "free-pro-team@latest" %} 或 REST API{% endif %} 与审核日志交互。 + +{% if currentVersion == "free-pro-team@latest" %} + +#### 使用 GraphQL API + +{% endif %} + +{% note %} + +**注**：审核日志 GraphQL API 可用于使用 {% data variables.product.prodname_enterprise %} 的组织。 {% data reusables.gated-features.more-info-org-products %} + +{% endnote %} + +要确保组织的 IP 安全和合规性，您可以使用审核日志 GraphQL API 保留审核日志数据的副本并监控： +{% data reusables.audit_log.audit-log-api-info %} + +{% if currentVersion == "free-pro-team@latest" %} +请注意，您不能使用 GraphQL API 检索 Git 事件。 要检索 Git 事件，请改为使用 REST API。 更多信息请参阅“[`git` 类操作](#git-category-actions)”。 +{% endif %} + +GraphQL 响应可包含长达 90 至 120 天的数据。 + +例如，您可以创建 GraphQL 请求以查看添加到组织的所有新组织成员。 更多信息请参阅“[GraphQL API 审核日志](/graphql/reference/interfaces#auditentry/)”。 + +{% if currentVersion == "free-pro-team@latest" %} + +#### 使用 REST API + +{% note %} + +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. + +{% endnote %} + +要确保组织的 IP 安全和合规性，您可以使用审核日志 REST API 保留审核日志数据的副本并监控： +{% data reusables.audit_log.audit-log-api-info %} +* Git 事件，如克隆、获取和推送 + +{% data reusables.audit_log.audit-log-git-events-retention %} + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endif %} + +### 审核日志操作 + +审核日志中记录为事件的一些最常见操作的概述。 + +{% if currentVersion == "free-pro-team@latest" %} + +#### `account` 类操作 + +| 操作 | 描述 | +| ----------------------------- | -------------------------------------------------------------------------------------------------------------------- | +| `billing_plan_change` | 当组织的[结算周期](/articles/changing-the-duration-of-your-billing-cycle)发生更改时触发。 | +| `plan_change` | 当组织的[订阅](/articles/about-billing-for-github-accounts)发生更改时触发。 | +| `pending_plan_change` | 当组织所有者或帐单管理员[取消或降级付费订阅](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/)时触发。 | +| `pending_subscription_change` | 当 [{% data variables.product.prodname_marketplace %} 免费试用开始或到期](/articles/about-billing-for-github-marketplace/)时触发。 | + +#### `advisory_credit` 类操作 + +| 操作 | 描述 | +| --------- | ---------------------------------------------------------------------------------------------------------- | +| `accept` | 当有人接受安全通告的积分时触发。 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory)”。 | +| `create` | 当安全通告的管理员将某人添加到积分部分时触发。 | +| `decline` | 当有人拒绝安全通告的积分时触发。 | +| `destroy` | 当安全通告的管理员将某人从积分部分删除时触发。 | + +#### `billing` 类操作 + +| 操作 | 描述 | +| --------------------- | ------------------------------------------------------------------------------------------------------------ | +| `change_billing_type` | 当组织[更改 {% data variables.product.prodname_dotcom %} 的支付方式](/articles/adding-or-editing-a-payment-method)时触发。 | +| `change_email` | 当组织的[帐单电子邮件地址](/articles/setting-your-billing-email)发生更改时触发。 | + +#### `dependabot_alerts` 类操作 + +| 操作 | 描述 | +| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `禁用` | 当组织所有者对所有现有{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库禁用 {% data variables.product.prodname_dependabot_alerts %} 时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 | +| `启用` | 当组织所有者对所有现有{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_dependabot_alerts %} 时触发。 | + +#### `dependabot_alerts_new_repos` 类操作 + +| 操作 | 描述 | +| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对所有新{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库禁用 {% data variables.product.prodname_dependabot_alerts %} 时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 | +| `启用` | 当组织所有者对所有新{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用 {% data variables.product.prodname_dependabot_alerts %} 时触发。 | + +#### `dependabot_security_updates` 类操作 + +| 操作 | 描述 | +| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对所有现有仓库禁用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 | +| `启用` | 当组织所有者对所有现有仓库启用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。 | + +#### `dependabot_security_updates_new_repos` 类操作 + +| 操作 | 描述 | +| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对所有新仓库禁用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 | +| `启用` | 当组织所有者对所有新仓库启用 {% data variables.product.prodname_dependabot_security_updates %} 时触发。 | + +#### `dependency_graph` 类操作 + +| 操作 | 描述 | +| ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对所有现有仓库禁用依赖项图时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 | +| `启用` | 当组织所有者对所有现有仓库启用依赖项图时触发。 | + +#### `dependency_graph_new_repos` 类操作 + +| 操作 | 描述 | +| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对所有新仓库禁用依赖项图时触发。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 | +| `启用` | 当组织所有者对所有新仓库启用依赖项图时触发。 | + +{% endif %} + +#### `discussion_post` 类操作 + +| 操作 | 描述 | +| --------- | ---------------------------------------------------------------------------- | +| `update` | 当[团队讨论帖子被编辑](/articles/managing-disruptive-comments/#editing-a-comment)时触发。 | +| `destroy` | 当[团队讨论帖子被删除](/articles/managing-disruptive-comments/#deleting-a-comment)时触发。 | + +#### `discussion_post_reply` 类操作 + +| 操作 | 描述 | +| --------- | ------------------------------------------------------------------------------- | +| `update` | 当[团队讨论帖子的回复被编辑](/articles/managing-disruptive-comments/#editing-a-comment)时触发。 | +| `destroy` | 当[团队讨论帖子的回复被删除](/articles/managing-disruptive-comments/#deleting-a-comment)时触发。 | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +#### `enterprise` 类别操作 + +{% data reusables.actions.actions-audit-events-for-enterprise %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `environment` 类别操作 + +| 操作 | 描述 | +| ----------------------- | ------------------------------------------------------------------------------------ | +| `create_actions_secret` | 在环境中创建机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。 | +| `delete` | 当环境被删除时触发。 更多信息请参阅“[删除环境](/actions/reference/environments#deleting-an-environment)”。 | +| `remove_actions_secret` | 从环境中删除机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。 | +| `update_actions_secret` | 当环境中的机密更新时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。 | +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `git` 类操作 + +{% note %} + +**注：**要访问审核日志中的 Git 事件，必须使用审核日志 REST API。 The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| 操作 | 描述 | +| ---- | ------------ | +| `克隆` | 当仓库被克隆时触发。 | +| `获取` | 从仓库获取更改时触发。 | +| `推送` | 将更改推送到仓库时触发。 | + +{% endif %} + +#### `hook` 类操作 + +| 操作 | 描述 | +| ---------------- | -------------------------------------------------- | +| `create` | 当[新挂钩被添加](/articles/creating-webhooks)到组织拥有的仓库时触发. | +| `config_changed` | 当现有挂钩的配置发生更改时触发。 | +| `destroy` | 从仓库中删除现有挂钩时触发。 | +| `events_changed` | 当挂钩上的事件发生更改时触发。 | + +#### `integration_installation_request` 类操作 + +| 操作 | 描述 | +| -------- | ------------------------------------------- | +| `create` | 当组织成员请求组织所有者安装集成以用于组织时触发。 | +| `close` | 当安装集成以用于组织的请求被组织所有者批准或拒绝，或者被提出请求的组成成员取消时触发。 | + +#### `issue` 类操作 + +| 操作 | 描述 | +| --------- | ------------------------------------ | +| `destroy` | 当组织所有者或仓库中具有管理员权限的人从组织拥有的仓库中删除议题时触发。 | + +{% if currentVersion == "free-pro-team@latest" %} + +#### `marketplace_agreement_signature` 类操作 + +| 操作 | 描述 | +| -------- | --------------------------------------------------------------- | +| `create` | 在签署 {% data variables.product.prodname_marketplace %} 开发者协议时触发。 | + +#### `marketplace_listing` 类操作 + +| 操作 | 描述 | +| --------- | -------------------------------------------------------------------- | +| `批准` | 当您的列表被批准包含在 {% data variables.product.prodname_marketplace %} 中时触发。 | +| `create` | 当您在 {% data variables.product.prodname_marketplace %} 中为应用程序创建列表时触发。 | +| `delist` | 当您的列表从 {% data variables.product.prodname_marketplace %} 中被删除时触发。 | +| `redraft` | 将您的列表被返回到草稿状态时触发。 | +| `reject` | 当您的列表被拒绝包含在 {% data variables.product.prodname_marketplace %} 中时触发。 | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +#### `members_can_create_pages` 类操作 + +更多信息请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 + +| 操作 | 描述 | +|:---- |:-------------------------------------------------------------------- | +| `启用` | 当组织所有者启用在组织中的仓库发布 {% data variables.product.prodname_pages %} 站点时触发。 | +| `禁用` | 当组织所有者禁止在组织中的仓库发布 {% data variables.product.prodname_pages %} 站点时触发。 | + +{% endif %} + +#### `org` 类操作 + +| 操作 | 描述 | +| ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_policy_selected_member_disabled` | 当企业所有者阻止为组织拥有的仓库启用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | 当企业所有者允许为组织拥有的仓库启用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `audit_log_export` | 组织管理员[创建组织审核日志导出](#exporting-the-audit-log)时触发。 如果导出包含查询，则日志将列出所使用的查询以及与该查询匹配的审核日志条目数量。 | +| `block_user` | 当组织所有者[阻止用户访问组织的仓库](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)时触发。 | +| `cancel_invitation` | 当组织邀请被撤销时触发的。 |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | 为组织创建 {% 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` | 当所有者为组织[禁用 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/disabling-oauth-app-access-restrictions-for-your-organization)时触发。 | +| `disable_saml` | 当组织管理员禁用组织的 SAML 单点登录时触发。{% endif %} +| `disable_member_team_creation_permission` | 当组织所有者将团队创建限于所有者时触发。 更多信息请参阅“[设置组织中的团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”。 |{% if currentVersion != "github-ae@latest" %} +| `disable_two_factor_requirement` | 当所有者对组织中的所有成员{% if currentVersion == "free-pro-team@latest" %}、帐单管理员{% endif %} 和外部协作者禁用双重身份验证要求时触发。{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| `enable_oauth_app_restrictions` | 当所有者为组织[启用 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/enabling-oauth-app-access-restrictions-for-your-organization)时触发。 | +| `enable_saml` | 当组织管理员对组织[启用 SAML 单点登录](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)时触发。{% endif %} +| `enable_member_team_creation_permission` | 当组织所有者允许成员创建团队时触发。 更多信息请参阅“[设置组织中的团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”。 |{% if currentVersion != "github-ae@latest" %} +| `enable_two_factor_requirement` | 当所有者对组织中的所有成员{% if currentVersion == "free-pro-team@latest" %}、帐单管理员{% endif %} 和外部协作者要求双重身份验证时触发。{% endif %} +| `invite_member` | 当[新用户被邀请加入您的组织](/articles/adding-organization-members-to-a-team)时触发。{% if currentVersion == "free-pro-team@latest" %} +| `oauth_app_access_approved` | 当所有者[授权组织访问 {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/) 时触发。 | +| `oauth_app_access_denied` | 当所有者对组织[禁用先前批准的 {% data variables.product.prodname_oauth_app %} 权限](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)时触发。 | +| `oauth_app_access_requested` | 当组织成员请求所有者对组织授予 {% data variables.product.prodname_oauth_app %} 权限时触发。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `register_self_hosted_runner` | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到组织](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)”。 | +| `remove_actions_secret` | 当 {% data variables.product.prodname_actions %} 密码删除时触发。{% endif %}{% if currentVersion == "free-pro-team@latest"%} +| `remove_billing_manager` | 当[所有者从组织中删除帐单管理员](/articles/removing-a-billing-manager-from-your-organization/)，或者当[组织中要求使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)但帐单管理员未使用 2FA 或禁用 2FA 时触发。 +{% endif %} +| `remove_member` | 当[所有者从组织中删除成员](/articles/removing-a-member-from-your-organization/)，{% if currentVersion != "github-ae@latest" %} 或者当[组织中要求使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)但组织成员未使用 2FA 或禁用 2FA 时触发{% endif %}。 当[组织成员从组织中删除自己](/articles/removing-yourself-from-an-organization/)时也会触发。 | +| `remove_outside_collaborator` | 当所有者从组织中删除外部协作者，{% if currentVersion != "github-ae@latest" %或者当[组织中要求使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)但外部协作者未使用 2FA 或禁用 2FA 时触发{% endif %}。 |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_self_hosted_runner` | 当自托管运行器被移除时触发。 更多信息请参阅“[从组织移除运行器](/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` | 当组织所有者撤销成员的链接身份时触发。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”。 | +| `revoke_sso_session` | 当组织所有者撤销成员的 SAML 会话时触发。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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` | 在创建自托管运行器组时触发。 更多信息请参阅“[为组织创建自托管运行器组](/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` | 当自托管运行器组被移除时触发。 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。 | +| `runner_group_updated` | 当自托管运行器组的配置改变时触发。 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。 | +| `runner_group_runners_added` | 当自托管运行器添加到组时触发。 更多信息请参阅“[将自托管运行器移动到组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。 | +| `runner_group_runner_removed` | 当 REST API 用于从组中删除自托管运行器时触发。 更多信息请参阅“[为组织从组中删除自托管运行器](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)”。 | +| `runner_group_runners_updated` | 当运行器组成员列表更新时触发。 更多信息请参阅“[为组织设置组中的自托管运行器](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)”。{% endif %}{% if currentversion == "free-proteam@latest"%}{% if currentversion == "free-pro-team@latest" or currentversion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。{% endif %} +| `unblock_user` | 当组织所有者[取消阻止用户访问组织](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)时触发。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | 当 {% 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` | 当所有者更改组织中新仓库的默认分支名称时触发。 更多信息请参阅“[管理组织中仓库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”。{% endif %} +| `update_default_repository_permission` | 当所有者更改组织成员的默认仓库权限级别时触发的。 | +| `update_member` | 当所有者将某人的角色从所有者更改为成员或者从成员更改为所有者时触发。 | +| `update_member_repository_creation_permission` | 当所有者更改组织成员创建仓库的权限时触发。{% if currentVersion == "free-pro-team@latest" %} +| `update_saml_provider_settings` | 当组织的 SAML 提供程序设置被更新时触发。 | +| `update_terms_of_service` | 当组织在标准服务条款和公司服务条款之间切换时触发。 更多信息请参阅“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `org_credential_authorization` 类操作 + +| 操作 | 描述 | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `grant` | 当成员[授权用于 SAML 单点登录的凭据](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)时触发。 | +| `deauthorized` | 当成员[取消授权用于 SAML 单点登录的凭据](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)时触发。 | +| `revoke` | 当所有者[撤销授权的凭据](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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" %} +#### `organization_label` 类操作 + +| 操作 | 描述 | +| --------- | ---------- | +| `create` | 创建默认标签时触发。 | +| `update` | 编辑默认标签时触发。 | +| `destroy` | 删除默认标签时触发。 | + +{% endif %} + +#### `oauth_application` 类操作 + +| 操作 | 描述 | +| --------------- | ----------------------------------------------------------------- | +| `create` | 在创建新 {% data variables.product.prodname_oauth_app %} 时触发。 | +| `destroy` | 当现有 {% data variables.product.prodname_oauth_app %} 被删除时触发。 | +| `reset_secret` | 当 {% data variables.product.prodname_oauth_app %} 的客户端密钥被重置时触发。 | +| `revoke_tokens` | 当 {% data variables.product.prodname_oauth_app %} 的用户令牌被撤销时触发。 | +| `转让` | 当现有 {% data variables.product.prodname_oauth_app %} 被转让到新组织时触发。 | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +#### `packages` 类操作 + +| 操作 | 描述 | +| --------------------------- | ------------------------------------------------------------------------------------------------------ | +| `package_version_published` | 当软件包版本发布时触发。 | +| `package_version_deleted` | 当特定软件包版本被删除时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 | +| `package_deleted` | 在整个软件包被删除时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 | +| `package_version_restored` | 当特定软件包版本被删除时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 | +| `package_restored` | 在整个软件包恢复时触发。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `payment_method` 类操作 + +| 操作 | 描述 | +| -------- | ------------------------------------------------------ | +| `clear` | 当存档的付款方式被[删除](/articles/removing-a-payment-method)时触发。 | +| `create` | 在添加新的付款方式（例如新的信用卡或 PayPal 帐户）时触发。 | +| `update` | 当现有付款方式被更新时触发。 | + +{% endif %} + +#### `profile_picture` 类操作 +| 操作 | 描述 | +| ------ | ----------------- | +| update | 在设置或更新组织的资料图片时触发。 | + +#### `project` 类操作 + +| 操作 | 描述 | +| ------------------------ | -------------------------------------- | +| `create` | 在创建项目板时触发。 | +| `link` | 当仓库被链接到项目板时触发。 | +| `rename` | 当项目板被重命名时触发。 | +| `update` | 当项目板被更新时触发。 | +| `delete` | 在删除项目板时触发。 | +| `unlink` | 当仓库从项目板解除链接时触发。 | +| `update_org_permission` | 当所有组织成员的基本级别权限被更改或删除时触发。 | +| `update_team_permission` | 当团队的项目板权限级别被更改，或者在项目板中添加或删除团队时触发。 | +| `update_user_permission` | 在项目板中添加或删除组织成员或外部协作者时，或者他们的权限级别被更改时触发。 | + +#### `protected_branch` 类操作 + +| 操作 | 描述 | +| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | 在分支上启用分支保护时触发。 | +| `destroy` | 在分支上禁用分支保护时触发。 | +| `update_admin_enforced` | 为仓库管理员实施分支保护时触发。 | +| `update_require_code_owner_review` | 在分支上更新必需代码所有者审查的实施时触发。 | +| `dismiss_stale_reviews` | 在分支上更新忽略旧拉取请求的实施时触发。 | +| `update_signature_requirement_enforcement_level` | 在分支上更新必需提交签名的实施时触发。 | +| `update_pull_request_reviews_enforcement_level` | 在分支上更新必需拉取请求审查的实施时触发。 | +| `update_required_status_checks_enforcement_level` | 在分支上更新必需状态检查的实施时触发。 | +| `update_strict_required_status_checks_policy` | 当分支在合并之前保持最新的要求被更改时触发。 | +| `rejected_ref_update` | 当分支更新尝试被拒绝时触发。 | +| `policy_override` | 当分支保护要求被仓库管理员覆盖时触发。{% 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` | 对受保护分支启用或禁用强制推送时触发。 | +| `update_allow_deletions_enforcement_level` | 对受保护分支启用或禁用分支删除时触发。 | +| `update_linear_history_requirement_enforcement_level` | 对受保护分支启用或禁用必要线性提交历史记录时触发。 | +{% endif %} + +#### `repo` 类操作 + +| 操作 | 描述 | +| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | 当用户[更改组织中仓库的可见性](/github/administering-a-repository/setting-repository-visibility)时触发。 | +| `actions_enabled` | 为仓库启用 {% data variables.product.prodname_actions %} 时触发。 可以使用用户界面查看。 当您使用 REST API 访问审计日志时，不包括此事件。 更多信息请参阅“[使用 REST API](#using-the-rest-api)”。 | +| `add_member` | 当用户接受[邀请以获取仓库协作权限](/articles/inviting-collaborators-to-a-personal-repository)时触发。 | +| `add_topic` | 当仓库管理员[添加主题](/articles/classifying-your-repository-with-topics)到仓库时触发。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %} +| `advanced_security_disabled` | 当仓库管理员为仓库禁用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 | +| `advanced_security_enabled` | 当仓库管理员为仓库启用 {% data variables.product.prodname_GH_advanced_security %} 功能时触发。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% 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.unlock_anonymous_git_access` | 当仓库的[匿名 Git 读取权限设置被解锁](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)时触发。{% endif %} +| `create` | 在[创建新仓库](/articles/creating-a-new-repository)时触发。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `create_actions_secret` | 为仓库创建 {% data variables.product.prodname_actions %} 密码时触发。 更多信息请参阅“[为仓库创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)”。{% endif %} +| `destroy` | 当[仓库被删除](/articles/deleting-a-repository)时触发。{% if currentVersion == "free-pro-team@latest" %} +| `禁用` | 当仓库被禁用（例如，因[资金不足](/articles/unlocking-a-locked-account)）时触发。{% endif %} +| `启用` | 当仓库被重新启用时触发。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `remove_actions_secret` | 当 {% data variables.product.prodname_actions %} 密码被移除时触发。{% endif %} +| `remove_member` | 当用户[被删除仓库协作者身份](/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` | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到仓库](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)”。 | +| `remove_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)时触发。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `self_hosted_runner_updated` | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。{% endif %} +| `转让` | 当[仓库被转让](/articles/how-to-transfer-a-repository)时触发。 | +| `transfer_start` | 在仓库转让即将发生时触发。 | +| `unarchived` | 当仓库管理员取消存档仓库时触发。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| `update_actions_secret` | 当 {% data variables.product.prodname_actions %} 密码更新时触发。{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +#### `repository_advisory` 类操作 + +| 操作 | 描述 | +| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `close` | 当有人关闭安全通告时触发。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 | +| `cve_request` | 当有人从 {% data variables.product.prodname_dotcom %} 为安全通告草稿申请 CVE（通用漏洞披露）编号时触发。 | +| `github_broadcast` | 当 {% data variables.product.prodname_dotcom %} 在 {% data variables.product.prodname_advisory_database %} 中公开安全通告时触发。 | +| `github_withdraw` | 当 {% data variables.product.prodname_dotcom %} 撤回错误发布的安全通告时触发。 | +| `已激活` | 当有人打开安全通告草稿时触发。 | +| `publish` | 当有人发布安全通告时触发。 | +| `重新激活` | 当有人重新打开安全通告草稿时触发。 | +| `update` | 当有人编辑草稿或发布安全通告时触发。 | + +#### `repository_content_analysis` 类操作 + +| 操作 | 描述 | +| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `启用` | 当组织所有者或对仓库有管理员权限的人[对私有仓库启用数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/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 %}{% if currentVersion != "github-ae@latest" %} + +#### `repository_dependency_graph` 类操作 + +| 操作 | 描述 | +| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当仓库所有者或对仓库拥有管理员权限的人对{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库禁用依赖项图时触发。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 | +| `启用` | 当仓库所有者或对仓库拥有管理员权限的人对{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用依赖项图时触发。 | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### `repository_secret_scanning` 类操作 + +| 操作 | 描述 | +| ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当仓库所有者或对仓库拥有管理员权限的人对{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库禁用密码扫描时触发。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 | +| `启用` | 当仓库所有者或对仓库拥有管理员权限的人对{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用密码扫描时触发。 | + +{% endif %}{% if currentVersion != "github-ae@latest" %} +#### `repository_vulnerability_alert` 类操作 + +| 操作 | 描述 | +| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | 当 {% data variables.product.product_name %} 为使用有漏洞依赖项的仓库创建{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报时触发。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 | +| `忽略` | 当组织所有者或对仓库拥有管理员权限的人忽略关于有漏洞依赖项的{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报时触发。 | +| `解决` | 当对仓库具有写入权限的人推送更改以更新和解决项目依赖项中的漏洞时触发。 | + +{% endif %}{% if currentVersion == "free-pro-team@latest" %} +#### `repository_vulnerability_alerts` 类操作 + +| 操作 | 描述 | +| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `authorized_users_teams` | 当组织所有者或对仓库有管理员权限的人更新有权接收仓库中有漏洞依赖项 {% data variables.product.prodname_dependabot_alerts %} 的人员或团队列表时触发。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 | +| `禁用` | 当仓库所有者或对仓库有管理员权限的人禁用 {% data variables.product.prodname_dependabot_alerts %} 时触发。 | +| `启用` | 当仓库所有者或对仓库有管理员权限的人启用 {% data variables.product.prodname_dependabot_alerts %} 时触发。 | + +{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +#### `secret_scanning` 类操作 + +| 操作 | 描述 | +| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对所有现有{% if currentVersion == "free-pro-team@latest" %} 私有{% endif %} 仓库禁用密码扫描时触发。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 | +| `启用` | 当组织所有者对所有现有{% if currentVersion == "free-pro-team@latest" %} 私有{% endif %} 仓库启用密码扫描时触发。 | + +#### `secret_scanning_new_repos` 类操作 + +| 操作 | 描述 | +| ---- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对所有新{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库禁用密码扫描时触发。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 | +| `启用` | 当组织所有者对所有新{% if currentVersion == "free-pro-team@latest" %}私有{% endif %}仓库启用密码扫描时触发。 | + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +#### `sponsors` 类操作 + +| 操作 | 描述 | +| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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` | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/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-organization)”） | +| `sponsored_developer_create` | 当您的 {% 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-organization)”） | +| `sponsored_developer_profile_update` | 在编辑您的赞助组织资料时触发（请参阅“[编辑 {% 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` | 提交您对 {% 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-organization)”） | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| sponsored_developer_update_newsletter_send | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/articles/contacting-your-sponsors)”） | +| `waitlist_invite_sponsored_developer` | 当您从等候名单被邀请加入 {% 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-organization)”） | +| `waitlist_join` | 当您加入成为赞助组织的等候名单时触发（请参阅“[为您的组织设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)”） | +{% endif %} + +#### `team` 类操作 + +| 操作 | 描述 | +| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_member` | 当组织成员被[添加到团队](/articles/adding-organization-members-to-a-team)时触发。 | +| `add_repository` | 当团队被授予控制仓库的权限时触发。 | +| `change_parent_team` | 在创建子团队或[更改子团队的父级](/articles/moving-a-team-in-your-organization-s-hierarchy)时触发。 | +| `change_privacy` | 当团队的隐私级别发生更改时触发。 | +| `create` | 当创建新团队时触发。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} + + +`demote_maintainer` | 当用户从团队维护员降级为团队成员时触发。 For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/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](/organizations/managing-peoples-access-to-your-organization-with-roles/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` | 当仓库不再在团队控制之下时触发。 + +#### `team_discussions` 类操作 + +| 操作 | 描述 | +| ---- | ----------------------------------------------------------------------------------------------------- | +| `禁用` | 当组织所有者对组织禁用团队讨论时触发。 更多信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”。 | +| `启用` | 当组织所有者对组织启用团队讨论时触发。 | + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +#### `workflows` 类操作 + +{% data reusables.actions.actions-audit-events-workflow %} + +{% endif %} + +### 延伸阅读 + +- “[保护组织安全](/articles/keeping-your-organization-secure)” diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md new file mode 100644 index 0000000000..dbbf794c1a --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -0,0 +1,25 @@ +--- +title: 审查组织安装的集成 +intro: 您可以审查组织安装的集成的权限级别，并配置每个集成对组织仓库的访问权限。 +redirect_from: + - /articles/reviewing-your-organization-s-installed-integrations + - /articles/reviewing-your-organizations-installed-integrations + - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. 在左侧边栏中，单击 **Installed {% data variables.product.prodname_github_app %}s（安装的 GitHub 应用程序）**。 ![组织设置边栏中安装的 {% data variables.product.prodname_github_app %}选项卡](/assets/images/help/organizations/org-settings-installed-github-apps.png) +5. 在您要审查的 {% data variables.product.prodname_github_app %} 旁边，单击 **Configure（配置）**。 ![配置按钮](/assets/images/help/organizations/configure-installed-integration-button.png) +6. 审查 {% data variables.product.prodname_github_app %} 的权限和仓库访问权限。 ![授予 {% data variables.product.prodname_github_app %}所有仓库或特定仓库访问权限的选项](/assets/images/help/organizations/toggle-integration-repo-access.png) + - 要授予 {% data variables.product.prodname_github_app %}所有组织仓库的访问权限，请选择 **All repositories（所有仓库）**。 + - 要选择特定仓库授予应用程序的访问权限，请选择 **Only select repositories（仅选择仓库）**，然后输入仓库名称。 +7. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md new file mode 100644 index 0000000000..76ecf57dc8 --- /dev/null +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md @@ -0,0 +1,30 @@ +--- +title: 查看组织中的用户是否已启用 2FA +intro: '您可以查看哪些组织所有者、成员和外部协作者已启用双因素身份验证。' +redirect_from: + - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled + - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +{% note %} + +**注：**您可以要求所有成员{% if currentVersion == "free-pro-team@latest" %}（包括组织中的所有者、帐单管理员和{% else %} 和{% endif %} 外部协作者）均启用双因素身份验证。 更多信息请参阅“[您的组织中需要双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)”。 + +{% endnote %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. 要查看已启用或已禁用双因素身份验证的组织成员（包括组织所有者），在右侧单击 **2FA**，然后选择 **Enabled（启用）**或 **Disabled（禁用）**。 ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png) +5. 要查看组织中的外部协作者，在“People（人员）”选项卡下，单击 **Outside collaborators（外部协作者）**。 ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) +6. 要查看哪些外部协作者已启用或已禁用双因素身份验证，在右侧单击 **2FA**，然后选择 **Enabled（启用）**或 **Disabled（禁用）**。 ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) + +### 延伸阅读 + +- “[查看组织中人员的角色](/articles/viewing-people-s-roles-in-an-organization)” diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md new file mode 100644 index 0000000000..ca32eecd39 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -0,0 +1,40 @@ +--- +title: 为组织添加 GitHub 应用程序管理员 +intro: '组织所有者可授权用户管理组织拥有的某些或所有 {% data variables.product.prodname_github_app %}。' +redirect_from: + - /articles/adding-github-app-managers-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +有关 {% data variables.product.prodname_github_app %} 管理员权限的更多信息，请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization#github-app-managers)”。 + +### 授权某人管理组织拥有的所有 {% 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. 在“Management（管理）”下，输入您要指定为组织中 {% data variables.product.prodname_github_app %} 管理员的人员，然后单击 **Grant（授权）**。 ![添加 {% data variables.product.prodname_github_app %} 管理员](/assets/images/help/organizations/add-github-app-manager.png) + +### 授权某人管理个别 {% 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. 在 "{% 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) + +{% if currentVersion == "free-pro-team@latest" %} +### 延伸阅读 + +- "[关于 {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md new file mode 100644 index 0000000000..6e48bd89cd --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -0,0 +1,18 @@ +--- +title: 管理对组织应用程序的访问 +intro: '作为组织所有者，您可以允许个别组织成员管理组织中的 {% data variables.product.prodname_github_app %}。' +redirect_from: + - /articles/managing-access-to-your-organization-s-apps + - /articles/managing-access-to-your-organizations-apps + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% link_in_list /adding-github-app-managers-in-your-organization %} +{% link_in_list /removing-github-app-managers-from-your-organization %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md new file mode 100644 index 0000000000..ec6f84083c --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -0,0 +1,40 @@ +--- +title: 从组织中删除 GitHub 应用程序管理员 +intro: '组织所有者可以撤销授予组织成员的 {% data variables.product.prodname_github_app %}管理员权限。' +redirect_from: + - /articles/removing-github-app-managers-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +有关 {% data variables.product.prodname_github_app %} 管理员权限的更多信息，请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization#github-app-managers)”。 + +### 删除整个组织的 {% 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. 在“Management（管理）”下，找到您要从其删除 {% data variables.product.prodname_github_app %}管理员权限的人员的用户名，然后单击 **Revoke（撤销）**。 ![撤销 {% data variables.product.prodname_github_app %}管理员权限](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) + +### 删除单个 {% data variables.product.prodname_github_app %}的 {% 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. 在 "{% 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) + +{% if currentVersion == "free-pro-team@latest" %} +### 延伸阅读 + +- "[关于 {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" +{% endif %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md new file mode 100644 index 0000000000..8a80c402d9 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: 添加外部协作者到组织的项目板 +intro: '作为组织所有者或项目板管理员，可以添加外部协作者并自定义他们对项目板的权限。' +redirect_from: + - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +外部协作者并未明确是组织的成员，但对组织的项目板具有访问权限。 + +{% 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. 在 "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/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/index.md new file mode 100644 index 0000000000..2c1f69f398 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -0,0 +1,22 @@ +--- +title: 管理对组织项目板的访问 +intro: '作为组织所有者或项目板管理员，您可以向组织成员、团队及外部协作者授予对组织项目板不同的访问权限。' +redirect_from: + - /articles/managing-access-to-your-organization-s-project-boards + - /articles/managing-access-to-your-organizations-project-boards + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md new file mode 100644 index 0000000000..4d29ebce0c --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -0,0 +1,39 @@ +--- +title: 管理组织成员对项目板的访问 +intro: '作为组织所有者或项目板管理员，您可以为所有组织成员设置项目板的默认权限级别。' +redirect_from: + - /articles/managing-access-to-a-project-board-for-organization-members + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +默认情况下，组织成员对其组织的项目板具有写入权限，除非组织所有者或项目板管理员对特定项目板设置不同的权限。 + +### 为所有组织成员设置基线权限级别 + +{% tip %} + +**提示：**您可以授予组织更高的项目板权限。 更多信息请参阅“[组织的项目板权限](/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. 在 "Organization member permission"（组织成员权限）下，为所有组织成员选择基线权限级别：**Read（读取）**、**Write（写入）**、**Admin（管理员）**或 **None（无）**。 ![用于所有组织成员的基线项目板权限选项](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. 单击 **Save（保存）**。 + +### 延伸阅读 + +- "[管理个人对组织项目板的访问](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[管理团队对组织项目板的访问](/articles/managing-team-access-to-an-organization-project-board)" +- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..a1672d0c29 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -0,0 +1,62 @@ +--- +title: 管理个人对组织项目板的访问 +intro: '作为组织所有者或项目板管理员，您可以管理个别成员对组织拥有的项目板的访问。' +redirect_from: + - /articles/managing-an-individual-s-access-to-an-organization-project-board + - /articles/managing-an-individuals-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% note %} + +**注：** {% data reusables.project-management.cascading-permissions %} 更多信息请参阅“[组织的项目板权限](/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 %} +{% data reusables.project-management.collaborator-option %} +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 %} + +### 更改组织成员对项目板的访问 + +{% 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 %} + +### 删除组织成员对项目板的访问 + +从项目板删除协作者时，根据他们其他角色的权限，他们可能仍然保有对项目板的访问权限。 要完全删除个人对项目板的访问权限，必须删除其每个角色的访问权限。 例如，某个人可能对项目板具有组织成员或团队成员的访问权限。 更多信息请参阅“[组织的项目板权限](/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 %} + +### 延伸阅读 + +- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md new file mode 100644 index 0000000000..05014f69a3 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -0,0 +1,52 @@ +--- +title: 管理团队对组织项目板的访问 +intro: '作为组织所有者或项目板管理员，您可以向团队授予对组织拥有的项目板的访问权限。' +redirect_from: + - /articles/managing-team-access-to-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% warning %} + +**警告：** +- 如果团队能够直接访问项目板，您可以更改其权限级别。 如果团队对项目板的访问权限继承自父团队，则您必须更改团队对项目板的访问权限。 +- 如果您添加或删除父团队的项目板访问权限，则其每个子团队也会获得或失去相应的项目板访问权限。 更多信息请参阅“[关于团队](/articles/about-teams)”。 + +{% endwarning %} + +### 授予团队项目板访问权限 + +您可以向整个团队授予相同级别的项目板访问权限。 + +{% note %} + +**注：** {% data reusables.project-management.cascading-permissions %} 例如，如果组织所有者向团队授予了读取项目板的权限，而项目板管理员向其中一个团队成员（作为个人贡献者）授予项目板管理员权限，则此人对项目板具有管理员权限。 更多信息请参阅“[组织的项目板权限](/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. 在左侧边栏中，单击 **Teams（团队）**。 +9. 要添加团队，请单击 **Add a team: Select team（添加团队：选择团队）**。 然后，从下拉菜单中选择一个团队，或者搜索要添加的团队。 ![添加包含组织中团队列表的团队下拉菜单](/assets/images/help/projects/add-a-team.png) +10. 在团队名称旁边，使用下拉菜单选择所需的权限级别：**Read（读取）**、**Write（写入）**或 **Admin（管理员）**。 ![包含读取、写入和管理员选项的团队权限下拉菜单](/assets/images/help/projects/org-project-team-choose-permissions.png) + +### 配置团队对项目板的访问 + +如果团队的项目板访问权限继承自父团队，您必须删除父团队的项目板访问权限，以更新子团队的访问权限。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +4. 在团队的对话上方，单击 {% octicon "project" aria-label="The Projects icon" %} **Projects（项目）**。 ![团队仓库选项卡](/assets/images/help/organizations/team-project-board-button.png) +5. 要更改权限级别，在要更新的项目板右侧使用下拉列表。 要删除项目板，请单击 **{% octicon "trashcan" aria-label="The trashcan icon" %}**。 ![从团队删除项目板的垃圾桶按钮](/assets/images/help/organizations/trash-button.png) diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md new file mode 100644 index 0000000000..a4c671f11f --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md @@ -0,0 +1,44 @@ +--- +title: 组织的项目板权限 +intro: '组织所有者以及具有项目板管理员权限的人员能够自定义谁对您组织的项目板具有读取、写入和管理员权限。' +redirect_from: + - /articles/project-board-permissions-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### 权限概述 + +人员和团队的项目板协作者有三种权限级别： + +{% data reusables.project-management.project-board-permissions %} + +组织所有者以及具有管理员权限的人员可授予个人作为外部协作者或组织成员，或者通过其在团队或组织中的成员资格来访问组织项目板。 外部协作者是指并非组织成员但被授予协作参与组织的人员。 + +组织所有者以及对项目板具有管理员权限的人员还可以： +- 设置所有组织成员的默认项目板权限。 +- 管理组织成员、团队和外部协作者对项目板的访问。 更多信息请参阅“[管理团队对组织项目板的访问](/articles/managing-team-access-to-an-organization-project-board)”、“[管理个人对组织项目板的访问](/articles/managing-an-individual-s-access-to-an-organization-project-board)”或“[管理组织成员对项目板的访问](/articles/managing-access-to-a-project-board-for-organization-members)”。 +- 管理项目板可见性。 更多信息请参阅“[管理组织成员对项目板的访问](/articles/managing-access-to-a-project-board-for-organization-members)”。 + +### 级联项目板的权限 + +{% data reusables.project-management.cascading-permissions %} + +例如，如果组织所有者向所有组织成员授予了读取项目板的权限，而项目板管理员向组织成员（作为个人协作者）授予项目板写入权限，则此人对项目板具有写入权限。 + +### 项目板可见性 + +{% data reusables.project-management.project-board-visibility %} 您可以将项目板的可见性从私有更改为{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}，反之亦然。 更多信息请参阅“[更改项目板可见性](/articles/changing-project-board-visibility)”。 + +### 延伸阅读 + +- "[更改项目板可见性](/articles/changing-project-board-visibility)" +- "[管理个人对组织项目板的访问](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[管理团队对组织项目板的访问](/articles/managing-team-access-to-an-organization-project-board)" +- "[管理组织成员对项目板的访问](/articles/managing-access-to-a-project-board-for-organization-members)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md new file mode 100644 index 0000000000..848667915d --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -0,0 +1,23 @@ +--- +title: 从组织项目板删除外部协作者 +intro: '作为组织所有者或项目板管理员，您可以删除外部协作者对项目板的访问权限。' +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md new file mode 100644 index 0000000000..499f2de9b8 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -0,0 +1,42 @@ +--- +title: 添加外部协作者到组织的仓库 +intro: '*外部协作者*并未明确是组织的成员，但对组织中的一个或多个仓库具有、读取、写入或管理员权限。' +redirect_from: + - /articles/adding-outside-collaborators-to-repositories-in-your-organization + - github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.organizations.owners-and-admins-can %} 可将外部协作者添加到仓库，除非组织所有者限制了邀请协作者的能力。 更多信息请参阅“[设置添加外部协作者的权限](/articles/setting-permissions-for-adding-outside-collaborators)”。. + +{% data reusables.organizations.outside-collaborators-use-seats %} + +{% if currentVersion != "github-ae@latest" %} +如果您的组织[要求成员和外部协作者使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)，则他们必须启用双重身份验证后才可接受您的邀请，协作处理组织仓库。 +{% 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. 在搜索字段中，开始键入您想邀请的人员的姓名，然后单击匹配列表中的姓名。 ![搜索字段以键入要邀请加入仓库的人员姓名](/assets/images/help/repository/manage-access-invite-search-field.png) +6. 在“Choose a role（选择角色）”下，选择要授予此人的权限，然后单击 **Add NAME to REPOSITORY（将姓名添加到仓库）**。 ![为此人选择权限](/assets/images/help/repository/manage-access-invite-choose-role-add.png) +{% else %} +5. 在左侧边栏中，单击 **Collaborators & teams（协作者和团队）**。 ![突出显示协作者和团队的仓库设置侧边栏](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) +6. 在 "Collaborators"（协作者）下，输入您要授权其访问仓库的人员的名称，然后单击 **Add collaborator（添加协作者）**。 ![在搜索字段中输入了 Octocat 用户名的协作者部分](/assets/images/help/repository/org-repo-collaborators-find-name.png) +7. 在新协作者名称旁边，选择适当的权限级别：*写入*、*读取*或*管理员*。 ![仓库权限选择器](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) +{% endif %} + +### 延伸阅读 + +- "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[从组织仓库删除外部协作者](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md new file mode 100644 index 0000000000..e255eeabcd --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md @@ -0,0 +1,24 @@ +--- +title: 取消成为组织外部协作者的邀请 +intro: 您可以取消让某人成为组织拥有仓库的外部协作者的所有邀请。 +permissions: 组织所有者可取消成为组织外部协作者的邀请。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +您可以查看所有待定邀请（邀请成为组织拥有的任何仓库上的外部协作者）人员列表。 + +对于每个待定协作者，您可以同时取消加入组织仓库的所有邀请。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. 单击 **X pending collaborators（删除待定协作者）**。 !["待定协作者" 按钮](/assets/images/help/organizations/pending-collaborator-list.png) +6. 在您要取消邀请的人员的右侧，单击 **Cancel invitations（取消邀请）**。 !["取消邀请" 按钮](/assets/images/help/organizations/cancel-pending-collaborators.png) +7. 单击 **Cancel invitations for pending collaborators（取消对待定协作者的邀请）**。 ![确认取消按钮](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md new file mode 100644 index 0000000000..97f8811af0 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md @@ -0,0 +1,44 @@ +--- +title: 将组织成员转换为外部协作者 +intro: '如果组织的某些当前成员只需要访问特定仓库，例如顾问或临时员工，您可以将他们转换为*外部协作者*。' +redirect_from: + - /articles/converting-an-organization-member-to-an-outside-collaborator + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.organizations.owners-and-admins-can %} 将组织成员转换为外部协作者。 + +{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} + +将组织成员转换为外部协作者后，他们将只能访问其当前团队成员资格允许的仓库。 他们将不再是组织的正式成员，不再能够： + +- 创建团队 +- 查看所有组织成员和团队 +- @提及任何可见团队 +- 成为团队维护员 + +更多信息请参阅“[组织的权限级别](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)”。 + +建议查看组织成员对仓库的访问权限，以确保其访问权限符合您的预期。 更多信息请参阅“[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)”。 + +将组织成员转换为外部协作者时，他们作为组织成员的权限将保存三个月，因此，如果您在该时间范围内{% 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 %} +{% data reusables.organizations.people %} +4. 选择要转换为外部协作者的人员。 ![选择了两名成员的成员列表](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. 在成员列表的上方，使用下拉菜单并单击 **Convert to outside collaborator（转换为外部协作者）**。 ![含有将成员转换为外部协作者选项的下拉菜单](/assets/images/help/teams/user-bulk-management-options.png) +6. 阅读有关将成员转换为外部协作者的信息，然后单击 **Convert to outside collaborator（转换为外部协作者）**。 ![有关外部协作者权限的信息和转换为外部协作者按钮](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) + +### 延伸阅读 + +- “[将外部协作者添加到组织中的仓库](/articles/adding-outside-collaborators-to-repositories-in-your-organization)” +- "[从组织仓库删除外部协作者](/articles/removing-an-outside-collaborator-from-an-organization-repository)" +- “[将外部协作者转换为组织成员](/articles/converting-an-outside-collaborator-to-an-organization-member)” diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md new file mode 100644 index 0000000000..fb0d421ca7 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md @@ -0,0 +1,41 @@ +--- +title: 将外部协作者转换为组织成员 +intro: '如果您希望为组织仓库的外部协作者提供更广泛的组织内权限，您可以{% if currentVersion == "free-pro-team@latest" %}邀请他们成为组织的成员{% else %}让他们成为组织的成员{% endif %}。' +redirect_from: + - /articles/converting-an-outside-collaborator-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: '组织所有者可以{% if currentVersion == "free-pro-team@latest" %}邀请用户加入{% else %}将用户添加到{% endif %}组织。' +topics: + - 组织 + - 团队 +--- + +{% if currentVersion == "free-pro-team@latest" %} +如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/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 %} +{% 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. 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**.![邀请外部协作者加入组织](/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) +{% 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 %} + +### 延伸阅读 + +- "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..c5f43b34d0 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md @@ -0,0 +1,28 @@ +--- +title: 管理对组织仓库的访问 +intro: 组织所有者可以管理个人和团队对组织仓库的访问。 团队维护员也可以管理团队的仓库访问权限。 +redirect_from: + - /articles/permission-levels-for-an-organization-repository/ + - /articles/managing-access-to-your-organization-s-repositories + - /articles/managing-access-to-your-organizations-repositories + - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md new file mode 100644 index 0000000000..d7878b1860 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -0,0 +1,39 @@ +--- +title: 管理个人对组织仓库的访问 +intro: 您可以管理个人对组织拥有的仓库的访问。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +具有管理员权限的人员可以管理组织成员和外部协作者对组织仓库的访问。 + +### 删除对仓库的访问权限 + +从组织中的仓库删除协作者时，该协作者会失去对仓库的读写权限。 如果仓库是私有的，并且协作者对仓库进行了复刻，则其复刻也会被检测到，但协作者仍然保留仓库的任何本地克隆副本。 + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +### 管理个人对组织仓库的访问 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. 单击 **Members（成员）**或 **Outside collaborators（外部协作者）**以管理具有不同访问权限的人员。 ![邀请成员或外部协作者参加组织的按钮](/assets/images/help/organizations/select-outside-collaborators.png) +5. 在您要管理的人员名称右侧，使用 {% octicon "gear" aria-label="The Settings gear" %} 下拉菜单，并单击 **Manage（管理）**。 ![管理访问链接](/assets/images/help/organizations/member-manage-access.png) +6. 在 "Manage access"（管理访问权限）页面上的仓库旁边，单击 **Manage access（管理访问权限）**。 ![管理对仓库的访问权限按钮](/assets/images/help/organizations/repository-manage-access.png) +7. 检查个人对指定仓库的访问权限，例如他们是协作者还是通过团队成员资格来访问仓库。 ![用户的仓库访问矩阵](/assets/images/help/organizations/repository-access-matrix-for-user.png) + +### 延伸阅读 + +{% 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/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md new file mode 100644 index 0000000000..022c12c0fc --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -0,0 +1,53 @@ +--- +title: 管理团队对组织仓库的访问 +intro: '您可以向团队授予仓库访问权限，删除团队的仓库访问权限，或者更改团队对仓库的权限级别。' +redirect_from: + - /articles/managing-team-access-to-an-organization-repository-early-access-program/ + - /articles/managing-team-access-to-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +对仓库具有管理员权限的人员可以管理团队对仓库的访问权限。 团队维护员可以删除团队对仓库的访问权限。 + +{% warning %} + +**警告：** +- 如果团队能够直接访问仓库，您可以更改其权限级别。 如果团队对仓库的访问权限继承自父团队，则您必须更改团队对仓库的访问权限。 +- 如果您添加或删除父团队的仓库访问权限，则其每个子团队也会获得或失去相应的仓库访问权限。 更多信息请参阅“[关于团队](/articles/about-teams)”。 + +{% endwarning %} + +### 授予团队对仓库的访问权限 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team-repositories-tab %} +5. 在仓库列表上方，单击 **Add repository（添加仓库）**。 ![添加仓库按钮](/assets/images/help/organizations/add-repositories-button.png) +6. 输入仓库的名称，然后单击 **Add repository to team（添加仓库到团队）**。 ![仓库搜索字段](/assets/images/help/organizations/team-repositories-add.png) +7. 也可选择在仓库名称右侧使用下拉菜单，为团队选择不同的权限级别。 ![仓库访问权限下拉菜单](/assets/images/help/organizations/team-repositories-change-permission-level.png) + +### 删除团队对仓库的访问权限 + +如果团队能够直接访问仓库，您可以更改其对仓库的访问权限。 如果团队对仓库的访问权限继承自父团队，则必须删除父团队对仓库的访问权限才可删除其子团队的相应权限。 + +{% 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. 选择要从团队删除的仓库。 ![某些仓库的勾选框已选中的团队仓库列表](/assets/images/help/teams/select-team-repositories-bulk.png) +6. 在仓库列表上方，使用下拉菜单，然后单击 **Remove from team（从团队删除）**。 ![包含从团队删除仓库的选项的下拉菜单](/assets/images/help/teams/remove-team-repo-dropdown.png) +7. 检查要从团队删除的仓库，然后单击 **Remove repositories（删除仓库）**。 ![包含团队无法再访问的仓库列表的模态框](/assets/images/help/teams/confirm-remove-team-repos.png) + +### 延伸阅读 + +- "[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md new file mode 100644 index 0000000000..1c70d4ade8 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -0,0 +1,76 @@ +--- +title: 恢复前外部协作者对组织的访问权限 +intro: '您可以恢复前外部协作者对组织仓库、复刻和设置的访问权限。' +redirect_from: + - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization + - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +当外部协作者对组织私有仓库的权限被删除时，该用户的访问权限和设置将保存三个月。 如果您在该时间范围内将用户{% if currentVersion == "free-pro-team@latest" %}邀请{% else %}添加{% endif %}回组织，则可以恢复该用户的权限。 + +{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} + +恢复前外部协作者时，您可以恢复以下各项： + - 用户对组织仓库以前的访问权限 + - 组织拥有的仓库的任何私有复刻 + - 组织团队的成员身份 + - 组织仓库以前的访问权限和权限 + - 组织仓库的星标 + - 组织中的议题分配 + - 仓库订阅（关注、不关注或忽略仓库活动的通知设置） + +{% tip %} + +**提示**： + - 只有组织所有者才能恢复外部协作者对组织的访问权限。 更多信息请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。 + - {% 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 %} + +{% 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. 通过单击 **Invite and reinstate（邀请并恢复）**选择恢复外部协作者在组织中以前的权限，或通过单击 **Invite and start fresh（邀请并重新开始）**选择清除其以前的权限并设置新的访问权限。 + + {% warning %} + + **警告：**如果想要将外部协作者升级为组织成员，则选择 **Invite and start fresh（邀请并重新开始）**，然后为此人员选择新角色。 但是，请注意，如果您选择重新开始，则此人员组织仓库的私人复刻将会丢失。 要使前外部协作者成为您组织的成员*并*保留其私有复刻，请选择 **Invite and reinstate（邀请并恢复）**。 此人员接受邀请后，您可以通过[邀请他们作为成员加入组织](/articles/converting-an-outside-collaborator-to-an-organization-member)，将其转换为组织成员。 + + {% endwarning %} + + ![选择是否恢复设置](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. 通过单击 **Add and reinstate（添加并恢复）**选择恢复外部协作者在组织中以前的权限，或通过单击 **Add and start fresh（添加并重新开始）**选择清除其以前的权限并设置新的访问权限。 + + {% warning %} + + **警告：**如果想要将外部协作者升级为组织成员，则选择 **Add and start fresh（添加并重新开始）**，然后为此人员选择新角色。 但是，请注意，如果您选择重新开始，则此人员组织仓库的私人复刻将会丢失。 要使前外部协作者成为您组织的成员*并*保留其私有复刻，请选择 **Add and reinstate（添加并恢复）**。 然后，您可以通过[将他们作为成员添加到组织](/articles/converting-an-outside-collaborator-to-an-organization-member)，将其转换为组织成员。 + + {% endwarning %} + + ![选择是否恢复设置](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. 如果已清除前外部协作者以前的权限，请为该用户选择一个角色，并（可选）将其添加到某些团队，然后单击 **Send invitation（发送邀请）**。 ![角色和团队选项及发送邀请按钮](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. 如果已清除前外部协作者以前的权限，请为该用户选择一个角色，并（可选）将其添加到某些团队，然后单击 **Add member（添加成员）**。 ![角色和团队选项及添加成员按钮](/assets/images/help/organizations/add-role-add-member.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +8. 被邀请的人员将收到邀请其加入组织的电子邮件。 它们需要接受邀请，然后才能成为组织中的外部协作者。 {% data reusables.organizations.cancel_org_invite %} +{% endif %} + +### 延伸阅读 + +- "[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md new file mode 100644 index 0000000000..0a267677f9 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -0,0 +1,57 @@ +--- +title: 从组织仓库中删除外部协作者 +intro: 所有者和仓库管理员可以删除外部协作者对仓库的访问权限。 +redirect_from: + - /articles/removing-an-outside-collaborator-from-an-organization-repository + - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**警告：** +- 从私有仓库删除外部协作者后，付费许可数不会自动降级。 要在从组织中删除用户后减少付费的许可数，请按照“[降级组织的付费席位](/articles/downgrading-your-organization-s-paid-seats)”中的步骤操作。 + +- 您负责确保无法访问仓库的人员删除任何机密信息或知识产权。 + +{% endwarning %} + +{% endif %} + +尽管删除协作者时将删除私有仓库的复刻，但此人员将仍保留您仓库的任何本地克隆。 + +### 从组织中的所有仓库删除外部协作者 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. 选择您想要从组织中删除的一个或多个外部协作者。 ![已选择两个外部协作者的外部协作者列表](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) +6. 在外部协作者列表上方，使用下拉菜单，然后单击 **Remove from all repositories（从所有仓库中删除）**。 ![含有删除外部协作者选项的下拉菜单 ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) +7. 查看将从组织中删除的一个或多个外部协作者，然后单击 **Remove outside collaborators（删除外部协作者）**。 ![将被删除的外部协作者列表和删除外部协作者按钮](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) + +### 从组织的特定仓库中删除外部协作者 + +如果只是想要从组织的特定仓库中删除外部协作者，则可以一次删除此人员对一个特定仓库的访问权限。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.people_tab_outside_collaborators %} +5. 在您想要删除的人员用户名右侧，使用 {% octicon "gear" aria-label="The Settings gear" %} 下拉菜单，并单击 **Manage（管理）**。 ![管理访问权限按钮](/assets/images/help/organizations/member-manage-access.png) +6. 在您想要从其删除外部协作者的仓库右侧，单击 **Manage access（管理访问权限）**。 ![选择外部协作者具有访问权限的仓库旁边的管理访问权限按钮](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) +7. 要完全删除外部协作者对仓库的访问权限，在右上角单击 **Remove access to this repository（删除对此仓库的访问权限）**。 ![删除此仓库访问权限按钮](/assets/images/help/organizations/remove-access-to-this-repository.png) +8. 要确认，请单击 **Remove access（删除访问权限）**。 ![确认将从仓库中删除的外部协作者](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) + +### 延伸阅读 + +- “[将外部协作者添加到组织中的仓库](/articles/adding-outside-collaborators-to-repositories-in-your-organization)” +- "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md new file mode 100644 index 0000000000..550e809479 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -0,0 +1,181 @@ +--- +title: 组织的仓库权限级别 +intro: '您可以通过细化权限级别自定义组织中每个仓库的权限，从而为每个用户提供所需的功能和任务权限。' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /articles/repository-permission-levels-for-an-organization-early-access-program/ + - /articles/repository-permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +具有管理员权限的人员可以管理对组织所拥有仓库的个人和团队访问权限。 + +### 组织所拥有仓库的权限级别 + +您可以为组织成员、外部协作者和人员团队提供对组织仓库不同级别的权限。 每个权限级别都会逐步增加对仓库内容和设置的权限。 选择最适合每个人或团队在项目中的角色的权限级别，而不是提供超过其需求的项目权限。 + +组织仓库从低到高的权限级别分别为： +- **读取**：建议授予要查看或讨论项目的非代码参与者 +- **分类**：建议授予需要主动管理议题和拉取请求的参与者，无写入权限 +- **写入**：建议授予积极向项目推送的参与者 +- **维护**：建议授予需要管理仓库的项目管理者，没有执行敏感或破坏性操作的权限 +- **管理员**：建议授予需要完全项目权限的人员，包括执行敏感和破坏性操作，例如管理安全性或删除仓库 + +{% if currentVersion == "free-pro-team@latest" %} + +{% endif %} + +有关为人员和团队提供仓库权限的更多信息，请参阅“[管理组织仓库的权限](/articles/managing-access-to-your-organizations-repositories)”。 + +组织所有者可以在访问组织的任何仓库时设置适用于组织所有成员的基本权限。 更多信息请参阅“[设置组织的基本权限](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)”。 + +组织所有者还可以选择进一步限制对整个组织中某些设置和操作的权限。 有关特定设置选项的更多信息，请参阅“[管理组织设置](/articles/managing-organization-settings)”。 + +除了管理组织范围的设置之外，组织所有者对组织拥有的每个仓库都具有管理员权限。 更多信息请参阅“[组织的权限级别](/articles/permission-levels-for-an-organization)”。 + +{% warning %} + +**警告：**当有人向仓库添加部署密钥时，拥有私钥的任何用户都可以读取或写入仓库（具体取决于密钥设置），即使他们后来从组织中被删除。 + +{% endwarning %} + +### 每个权限级别的仓库权限 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% note %} + +**注：**使用安全功能所需的仓库权限列于下面的“[安全功能的权限要求](#permission-requirements-for-security-features)”。 + +{% endnote %} + +{% 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 工作流程运行](/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" %} +| [举报滥用或垃圾内容](/communities/maintaining-your-safety-on-github/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" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [在拉取请求上启用和禁用自动合并](/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** | +| [隐藏任何人的评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [锁定对话](/communities/moderating-comments-and-conversations/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 工作流程](/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" or currentVersion == "github-ae@latest" %} +| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **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" %} +| 限制[仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +{% endif %} +| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | +| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** | +| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | +| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/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" or currentVersion ver_gt "enterprise-server@3.0" %} +| 重命名仓库的默认分支（请参阅“[重命名分支](/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/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +#### 安全功能的权限要求 + +在本节中，您可以找到一些安全功能所需的仓库权限级别，例如 {% data variables.product.prodname_advanced_security %} 功能。 + +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-----:|:-----:|:-------------------:|:-------------------:|:-------------------------------------------------------------------------------------------------------------------------------------------------------------:| +| {% if currentVersion == "free-pro-team@latest" %} | | | | | | +| 接收仓库中[易受攻击的依赖项的 {% 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/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** | +| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| [查看拉取请求上的 {% 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@3.0" or currentVersion == 'github-ae@next' %} +| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | +| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% if currentVersion == "enterprise-server@3.0" %} +| [查看仓库中的 {% 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-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| [指定其他人员或团队接收仓库中的 {% 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 %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == 'github-ae@next' %} +[1] 仓库作者和维护者只能看到他们自己提交的警报信息。 +{% endif %} +{% endif %} + +### 延伸阅读 + +- “[管理对组织仓库的访问](/articles/managing-access-to-your-organization-s-repositories)” +- “[将外部协作者添加到组织中的仓库](/articles/adding-outside-collaborators-to-repositories-in-your-organization)” +- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md new file mode 100644 index 0000000000..ae13dbf796 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -0,0 +1,36 @@ +--- +title: 设置组织的基本权限 +intro: 您可以为组织拥有的仓库设置基本权限。 +permissions: 组织所有者可设置组织的基本权限。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### 关于组织的基本权限 + +您可以在访问组织的任何仓库时设置适用于组织所有成员的基本权限。 基本权限不适用于外部协作者。 + +{% if currentVersion == "free-pro-team@latest" %}默认情况下，组织成员具有对组织仓库的**读取**权限。{% endif %} + +如果拥有组织仓库管理员权限的人向组织成员授予更高级别的仓库权限，则更高级别的权限将覆盖基本权限。 + +### 设置基本权限 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. 在“Base permissions（基本权限）”下，使用下拉菜单选择新的基本权限。 ![从基本权限下拉菜单中选择新的权限级别](/assets/images/help/organizations/base-permissions-drop-down.png) +6. 审查更改。 要确认，请单击 **Change default permission to PERMISSION（将默认权限更改为所设权限）**。 ![审查并确认基本权限的更改](/assets/images/help/organizations/base-permissions-confirm.png) + +### 延伸阅读 + +- "[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" +- “[将外部协作者添加到组织中的仓库](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)” diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md new file mode 100644 index 0000000000..2cbe693352 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -0,0 +1,41 @@ +--- +title: 查看具有仓库访问权限的人员 +intro: '组织所有者可以查看人员对组织内仓库的访问权限。 使用 {% data variables.product.prodname_ghe_cloud %} 或 {% data variables.product.prodname_ghe_server %} 的组织所有者还可导出具有仓库访问权限人员的 CSV 列表。' +redirect_from: + - /articles/viewing-people-with-access-to-your-repository + - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +管理员可以使用此信息帮助非内部人员，收集数据用于合规性以及其他常规安全检查。 + +![仓库人员权限列表](/assets/images/help/repository/repository-permissions-list.png) + +### 查看具有仓库访问权限的人员 + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**注**：您还可以查看有权访问仓库的团队和人员的组合概述。 更多信息请参阅“[管理有权访问仓库的团队和人员](/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 %} + +### 导出具有您的仓库访问权限人员的列表 + +{% data variables.product.prodname_ghe_cloud %} 或 {% data variables.product.prodname_ghe_server %} 上的组织所有者可以导出具有仓库访问权限人员的 CSV 列表。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.accessing-repository-people %} +4. 单击 **Export CSV（导出 CSV）**。 ![仓库边栏中的人员选项卡](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md new file mode 100644 index 0000000000..e75c173606 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -0,0 +1,47 @@ +--- +title: 关于 SSH 认证中心 +intro: '通过 SSH 认证中心，组织或企业帐户可提供 SSH 证书，供成员用来通过 Git 访问您的资源。' +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/about-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。 如果使用 SSH 认证中心 (CA) 为组织成员提供已签名的 SSH 证书，您可以将 CA 添加到企业帐户或组织，以便组织成员使用其证书访问组织资源。 更多信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”。 + +在将 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 %} 上的仓库。 在一天结束时，证书会自动到期，以保护仓库，避免证书以后被窃取。 + +在颁发每个证书时，必须包含扩展，以指定证书用于哪个 {% data variables.product.product_name %} 用户。 例如，您可以使用 OpenSSH 的 `ssh-keygen` 命令，将 _KEY-IDENTITY_ 替换为密钥标识，_USERNAME_ 替换为 {% data variables.product.product_name %} 用户名： + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +``` + +要为使用 SSH 访问多个 {% data variables.product.company_short %} 产品的人颁发证书，您可以包括两个登录扩展，以指定每个产品的用户名。 例如，以下命令将为 {% data variables.product.prodname_ghe_cloud %} 的用户帐户颁发 _USERNAME-1_ 的证书，为 _HOSTNAME_ 的 {% data variables.product.prodname_ghe_managed %} 或 {% data variables.product.prodname_ghe_server %} 上的用户帐户颁发 _USERNAME-2_ 的证书。 + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +``` + +您可以使用 `source-address` 扩展来限制组织成员用来访问组织资源的 IP 地址。 扩展接受采用 CIDR 表示法的特定 IP 地址或一个 IP 地址范围。 您可以指定多个地址或范围，用逗号分隔值。 更多信息请参阅维基百科上的“[无类别域间路由](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)”。 + +```shell +$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +``` + +{% if currentVersion == "free-pro-team@latest" %} + +即使您实施了 SAML 单点登录，组织成员也可使用其签名的证书进行身份验证。 除非您将 SSH 证书设为要求，组织成员可继续使用其他验证方式通过 Git 访问组织的资源，包括他们的用户名和密码、个人访问令牌及其自己的 SSH 密钥。 + +{% endif %} + +为防止身份验证错误，组织成员应使用包含组织 ID 的特殊 URL，以使用签名证书克隆仓库。 对仓库具有读取权限的任何人都可在仓库页面上找到此 URL。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。 diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md new file mode 100644 index 0000000000..2909f18351 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -0,0 +1,19 @@ +--- +title: 管理对组织仓库的 Git 访问 +intro: 您可以将 SSH 证书颁发机构 (CA) 添加到组织，并允许成员使用 SSH CA 签名的密钥通过 Git 访问组织的仓库。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% link_in_list /about-ssh-certificate-authorities %} +{% link_in_list /managing-your-organizations-ssh-certificate-authorities %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md new file mode 100644 index 0000000000..331c9df759 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -0,0 +1,38 @@ +--- +title: 管理组织的 SSH 认证中心 +intro: 可在组织中添加或删除 SSH 认证中心。 +product: '{% data reusables.gated-features.ssh-certificate-authorities %}' +redirect_from: + - /articles/managing-your-organizations-ssh-certificate-authorities + - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者可以管理组织的 SSH 认证中心 (CA)。 + +您可以通过向组织添加 SSH CA 来允许成员使用提供的 SSH 证书访问组织的仓库。 {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/articles/about-ssh-certificate-authorities)”。 + +### 添加 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 %} + +### 删除 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/zh-CN/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md new file mode 100644 index 0000000000..32ff9899dc --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md @@ -0,0 +1,29 @@ +--- +title: 将人员添加到您的组织 +intro: '您可以使用任何人的 {% data variables.product.product_name %} 用户名或电子邮件地址使其成为组织的成员。' +redirect_from: + - /articles/adding-people-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization +versions: + enterprise-server: '*' + github-ae: '*' +permissions: '组织所有者可以向组织添加人员。' +--- + +{% if currentVersion != "github-ae@latest" %} +如果您的组织[要求成员使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)，则用户必须[启用双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)，然后您才可将他们添加到组织。 +{% 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 %} + +### 延伸阅读 +- "[向团队添加组织成员](/articles/adding-organization-members-to-a-team)" diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md new file mode 100644 index 0000000000..88f0f0b599 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md @@ -0,0 +1,21 @@ +--- +title: 我可以为组织中的人员创建帐户吗？ +intro: '虽然您可以将用户添加到您创建的组织，但您无法代表其他人创建其个人用户帐户。' +redirect_from: + - /articles/can-i-create-accounts-for-those-in-my-organization/ + - /articles/can-i-create-accounts-for-people-in-my-organization + - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +由于访问组织需要登录个人帐户，因此每个团队成员都需要个人帐户。 您有了要添加到组织的每个人的用户名后，就可以将他们添加到团队。 + +### 将用户添加到您的组织 + +1. 向每个人提供关于[创建个人用户](/articles/signing-up-for-a-new-github-account)的说明。 +2. 获取要赋予其组织成员资格的每个人的用户名。 +3. [邀请新个人帐户加入](/articles/inviting-users-to-join-your-organization)您的组织。 使用[组织角色](/articles/permission-levels-for-an-organization)和[仓库权限](/articles/repository-permission-levels-for-an-organization)限制每个帐户的访问权限。 diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md new file mode 100644 index 0000000000..81e1888543 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md @@ -0,0 +1,30 @@ +--- +title: 取消或编辑加入组织的邀请 +intro: 在用户接受成为组织成员的邀请之前，组织所有者可随时编辑或取消该邀请。 +redirect_from: + - /articles/canceling-or-editing-an-invitation-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. 在 People（人员）选项卡上，单击 **Pending invitation（待定邀请）**。 ![待定邀请链接](/assets/images/help/organizations/pending-invitation-link.png) +5. 在要编辑或取消其邀请的受邀人用户名或电子邮件地址旁边，单击 **Edit invitation（编辑邀请）**。 ![编辑邀请按钮](/assets/images/help/organizations/edit-invitation-button.png) + + 您可能需要单击窗口底部的 **View all invitations（查看所有邀请）**来查找所需的人员。 +6. 决定是编辑还是取消加入组织的用户邀请。 ![更新邀请和取消邀请按钮](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) + - 要编辑用户邀请，请选择不同的角色或团队，然后单击 **Update invitation（更新邀请）**。 + - 要取消加入组织的用户邀请，请单击 **Cancel invitation（取消邀请）**。 + +### 延伸阅读 + +{% if currentVersion == "free-pro-team@latest" %} +- “[邀请用户加入您的组织](/articles/inviting-users-to-join-your-organization)” +{% endif %} +- "[向团队添加组织成员](/articles/adding-organization-members-to-a-team)" diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md new file mode 100644 index 0000000000..c470fadb8b --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md @@ -0,0 +1,23 @@ +--- +title: 管理组织中的成员资格 +intro: '在创建组织后，您可以{% if currentVersion == "free-pro-team@latest" %}邀请人员成为{% else %}添加人员为{% endif %}组织的成员。 您也可以删除组织的成员，以及恢复前成员。' +redirect_from: + - /articles/removing-a-user-from-your-organization/ + - /articles/managing-membership-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md new file mode 100644 index 0000000000..a5450c3d9a --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -0,0 +1,36 @@ +--- +title: 邀请用户参加您的组织 +intro: '您可以使用任何人的 {% data variables.product.product_name %} 用户名或电子邮件地址邀请其成为组织的成员。' +permissions: 组织所有者可以邀请用户加入组织。 +redirect_from: + - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ + - /articles/inviting-users-to-join-your-organization + - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% tip %} + +**提示**： +- 如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 {% data reusables.organizations.org-invite-expiration %} +- 如果您的组织要求成员使用双重身份验证，则您邀请的用户在接受邀请之前必须启用双重身份验证。 更多信息请参阅“[在组织中要求双重身份验证](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)”和“[使用双重身份验证 (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 %} + +### 延伸阅读 +- "[向团队添加组织成员](/articles/adding-organization-members-to-a-team)" diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md new file mode 100644 index 0000000000..99e8f5b152 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md @@ -0,0 +1,63 @@ +--- +title: 恢复组织的前成员 +intro: '组织所有者可以{% if currentVersion == "free-pro-team@latest" %}邀请前组织成员重新加入{% else %}将前成员添加到{% endif%}您的组织，并可选择是否恢复该人员以前的角色、访问权限、复刻和设置。' +redirect_from: + - /articles/reinstating-a-former-member-of-your-organization + - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +permissions: 组织所有者可以恢复组织的前成员。 +topics: + - 组织 + - 团队 +--- + +### 关于成员恢复 + +如果您[从组织中删除用户](/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 %} + +恢复前组织成员时，您可以恢复以下各项： + - 用户在组织中的角色 + - 组织拥有的仓库的任何私有复刻 + - 组织团队的成员身份 + - 组织仓库以前的访问权限和权限 + - 组织仓库的星标 + - 组织中的议题分配 + - 仓库订阅（关注、不关注或忽略仓库活动的通知设置） + +{% if enterpriseServerVersions contains currentVersion %} +如果组织成员由于未使用双因素身份验证已从组织中删除，并且您的组织仍要求成员使用 2FA，则前成员必须启用双因素身份验证，然后才能恢复其成员身份。 +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 {% data reusables.organizations.org-invite-expiration %} +{% 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.reinstate-user-type-username %} +{% if currentVersion == "free-pro-team@latest" %} +6. 选择是恢复该人员在组织中以前的权限还是清除其以前的权限并设置新的访问权限，然后单击 **Invite and reinstate（邀请并恢复）**或 **Invite and start fresh（邀请并重新开始）**。 ![选择是否恢复信息](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) +{% else %} +6. 选择是恢复该人员在组织中以前的权限还是清除其以前的权限并设置新的访问权限，然后单击 **Add and reinstate（添加并恢复）**或 **Add and start fresh（添加并重新开始）**。 ![选择是否恢复权限](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +7. 如果已清除前组织成员以前的权限，请为该用户选择一个角色，并（可选）将其添加到某些团队，然后单击 **Send invitation（发送邀请）**。 ![角色和团队选项及发送邀请按钮](/assets/images/help/organizations/add-role-send-invitation.png) +{% else %} +7. 如果已清除前组织成员以前的权限，请为该用户选择一个角色，并（可选）将其添加到某些团队，然后单击 **Add member（添加成员）**。 ![角色和团队选项及添加成员按钮](/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 %} + +### 延伸阅读 + +- "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md new file mode 100644 index 0000000000..2d64684c02 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -0,0 +1,60 @@ +--- +title: 从组织中删除成员 +intro: '如果组织的成员不再需要访问组织拥有的任何仓库，则可以从组织中删除他们。' +redirect_from: + - /articles/removing-a-member-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +只有组织所有者才能从组织中删除成员。 + +{% if currentVersion == "free-pro-team@latest" %} + +{% warning %} + +**警告：**当您从组织删除成员时： +- 付费的许可数不会自动降级。 要在从组织中删除用户后减少付费的许可数，请按照“[降级组织的付费席位](/articles/downgrading-your-organization-s-paid-seats)”中的步骤操作。 +- 被删除的成员将无法访问组织私有仓库的私人复刻，但仍可拥有本地副本。 但是，它们无法将本地副本与组织的仓库同步。 如果用户在从组织中删除后的三个月内[恢复为组织成员](/articles/reinstating-a-former-member-of-your-organization)，则可以恢复其私人复刻。 最终，您负责确保无法访问仓库的人员删除任何机密信息或知识产权。 +- 被删除成员发出的任何组织邀请，如果没有被接受，都会取消，且无法访问。 + +{% endwarning %} + +{% else %} + +{% warning %} + +**警告：**当您从组织删除成员时： + - 被删除的成员将无法访问组织私有仓库的私人复刻，但仍可拥有本地副本。 但是，它们无法将本地副本与组织的仓库同步。 如果用户在从组织中删除后的三个月内[恢复为组织成员](/articles/reinstating-a-former-member-of-your-organization)，则可以恢复其私人复刻。 最终，您负责确保无法访问仓库的人员删除任何机密信息或知识产权。 + - 被删除用户发出的任何组织邀请，如果没有被接受，都会取消，且无法访问。 + +{% endwarning %} + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} + +为帮助您从组织中删除的人员过渡并帮助确保他们删除机密信息或知识产权，我们建议您共享一份离开组织的最佳实践检查列表。 例如，请参阅“[关于离开公司的最佳实践](/articles/best-practices-for-leaving-your-company/)”。 + +{% endif %} + +{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} + +### 撤销用户的成员身份 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. 选择您想要从组织中删除的成员。 ![选择了两名成员的成员列表](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. 在成员列表上方，使用下拉菜单，然后单击 **Remove from organization（从组织中删除）**。 ![包含删除成员选项的下拉菜单](/assets/images/help/teams/user-bulk-management-options.png) +6. 查看将从组织中删除的一个或多个成员，然后单击 **Remove members（删除成员）**。 ![将被删除的成员列表和删除成员按钮](/assets/images/help/teams/confirm-remove-members-bulk.png) + +### 延伸阅读 + +- “[从团队中删除组织成员](/articles/removing-organization-members-from-a-team)” diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md new file mode 100644 index 0000000000..dc82fb4823 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: 允许人们删除组织中的议题 +intro: 组织所有者可以允许特定人员从组织拥有的仓库中删除议题。 +redirect_from: + - /articles/allowing-people-to-delete-issues-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +默认情况下，无法从组织的仓库中删除议题。 组织所有者必须先对所有组织的仓库启用此功能。 + +在启用后，组织所有者以及在组织拥有的仓库中具有管理员权限的人员便可删除议题。 在仓库中具有管理员权限的人员包括具有管理员权限的组织成员以及外部协作者。 更多信息请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization/)”和“[删除议题](/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. 在 "Issue deletion"（删除议题）下，选择 **Allow members to delete issues for this organization（允许成员删除此组织的议题）**。 ![允许人们删除议题的复选框](/assets/images/help/settings/issue-deletion.png) +6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/zh-CN/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md new file mode 100644 index 0000000000..0d48f06df9 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -0,0 +1,24 @@ +--- +title: 更改组织依赖项洞察图的可见性 +intro: 您可以允许所有组织成员查看组织的依赖项洞察图或仅限组织所有者查看。 +product: '{% data reusables.gated-features.org-insights %}' +redirect_from: + - /articles/changing-the-visibility-of-your-organizations-dependency-insights + - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者可设置查看组织依赖项洞察图的限制。 默认情况下，组织的所有成员都可以查看组织依赖项洞察图。 + +企业所有者可设置企业帐户中所有组织的查看组织依赖项洞察图限制。 更多信息请参阅“[在企业帐户中实施关于依赖项洞察的策略](/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. 在“Member organization permissions（成员组织权限）”下，选中或取消选中 **Allow members to view dependency insights（允许成员查看依赖项洞察图）**。 ![允许成员查看洞察图的复选框](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md new file mode 100644 index 0000000000..d273ad8708 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md @@ -0,0 +1,22 @@ +--- +title: 为组织中的 GitHub Actions 构件和日志配置保留期 +intro: '您可以为组织中的 {% data variables.product.prodname_actions %} 构件和日志配置保留期。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.actions.about-artifact-log-retention %} + +## 设置组织的保留期 + +{% 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/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md new file mode 100644 index 0000000000..44181cc05e --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -0,0 +1,33 @@ +--- +title: 将组织转换为用户 +intro: '无法将组织转换为个人用户帐户，但您可以创建一个新用户帐户，然后将组织的仓库转让给该帐户。' +redirect_from: + - /articles/converting-an-organization-into-a-user + - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +{% if currentVersion == "free-pro-team@latest" %} + +1. [注册](/articles/signing-up-for-a-new-github-account)新 GitHub 用户帐户。 +2. [将用户的角色更改为所有者](/articles/changing-a-person-s-role-to-owner)。 +3. {% data variables.product.signin_link %} 到新用户帐户。 +4. [将每个组织仓库转让](/articles/how-to-transfer-a-repository)给新用户帐户。 +5. [删除组织](/articles/deleting-an-organization-account)。 +6. [将用户重命名](/articles/changing-your-github-username)为组织的名称。 + +{% else %} + +1. 注册新 GitHub Enterprise 用户帐户。 +2. [将用户的角色更改为所有者](/articles/changing-a-person-s-role-to-owner)。 +3. {% data variables.product.signin_link %} 到新用户帐户。 +4. [将每个组织仓库转让](/articles/how-to-transfer-a-repository)给新用户帐户。 +5. [删除组织](/articles/deleting-an-organization-account)。 +6. [将用户重命名](/articles/changing-your-github-username)为组织的名称。 + +{% endif %} diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md new file mode 100644 index 0000000000..5649b233a4 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -0,0 +1,34 @@ +--- +title: 删除组织帐户 +intro: '删除组织时，所有仓库、私有仓库复刻、wiki、议题、拉取请求和项目或组织页面也被删除。 {% if currentVersion == "free-pro-team@latest" %}组织名称可用于新用户或组织帐户，并且计费将结束。{% endif %}' +redirect_from: + - /articles/deleting-an-organization-account + - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% if currentVersion == "free-pro-team@latest" %} +{% tip %} + +**提示**：如果要取消已付费的订阅，可以[将组织下载到 {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) 而非删除组织及其内容。 + +{% endtip %} + +{% endif %} + +### 1. 备份组织内容 + +删除组织后，GitHub **无法恢复内容**。 因此，在删除组织之前，请确保您拥有该帐户中所有仓库、wiki、议题和项目板的副本。 + +### 2. 删除组织 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. 在组织设置页面底部附近，单击 **Delete this Organization（删除此组织）**。 ![删除此组织按钮](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md new file mode 100644 index 0000000000..d68e135a9c --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -0,0 +1,85 @@ +--- +title: 禁用或限制组织的 GitHub Actions +intro: '组织所有者可禁用、启用和限制组织的 GitHub Actions。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +### 关于组织的 {% data variables.product.prodname_actions %} 权限 + +{% data reusables.github-actions.disabling-github-actions %} 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。 + +您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.enabled-actions-description %} 您可以对组织中的所有仓库禁用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.disabled-actions-description %} + +此外，您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作。 {% data reusables.github-actions.enabled-local-github-actions %} + +{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %} + +### 管理组织的 {% data variables.product.prodname_actions %} 权限 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. 在 **Local and third-party Actions（本地和第三方操作）**下，选择一个选项。 ![启用、禁用或限制此组织的操作](/assets/images/help/repository/enable-org-actions.png) +1. 单击 **Save（保存）**。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} + +### 管理组织的 {% data variables.product.prodname_actions %} 权限 + +您可以禁用组织的所有工作流程，或者设置策略来配置哪些操作可用于组织中。 + +{% data reusables.actions.actions-use-policy-settings %} + +{% note %} + +**注：**如果您的组织由具有覆盖策略的企业管理，您可能无法管理这些设置。 更多信息请参阅{% 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 %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.settings-sidebar-actions %} +1. 在 **Policies（策略）**下，选择一个选项。 ![设置此组织的操作策略](/assets/images/help/organizations/actions-policy.png) +1. 单击 **Save（保存）**。 + +### 允许特定操作运行 + +{% 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. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 ![添加操作到允许列表](/assets/images/help/organizations/actions-policy-allow-list.png) +1. 单击 **Save（保存）**。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +### 为私有仓库复刻启用工作流程 + +{% data reusables.github-actions.private-repository-forks-overview %} + +#### 为组织配置私有复刻策略 + +{% 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/zh-CN/content/organizations/managing-organization-settings/index.md b/translations/zh-CN/content/organizations/managing-organization-settings/index.md new file mode 100644 index 0000000000..e93dfdc53a --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/index.md @@ -0,0 +1,39 @@ +--- +title: 管理组织设置 +intro: '组织管理员可以更改多项设置，包括属于组织的仓库名称和所有者团队成员资格。 此外，组织管理员还可以删除组织及其所有仓库。' +redirect_from: + - /articles/managing-organization-settings + - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 /managing-the-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 %} diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md new file mode 100644 index 0000000000..7927a13d56 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md @@ -0,0 +1,26 @@ +--- +title: 集成 Jira 与组织项目板 +intro: '您可以将 Jira Cloud 与组织帐户集成，以扫描提交和拉取请求，在任何提及的 Jira 议题中创建相关的元数据和超链接。' +redirect_from: + - /articles/integrating-jira-with-your-organization-project-board + - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board +versions: + enterprise-server: '*' + github-ae: '*' +--- + +{% data reusables.user_settings.access_settings %} +2. 在左侧边栏的 **Organization settings（组织设置）**下，单击组织的名称。 ![侧边栏组织名称](/assets/images/help/settings/organization-settings-from-sidebar.png) +3. 在左侧边栏的 **Developer settings（开发者设置）**下，单击 **OAuth applications（OAuth 应用程序）**。 ![左侧边栏中的 OAuth 应用程序选项卡](/assets/images/help/organizations/org-oauth-applications-ghe.png) +4. 单击 **Register a new application（注册新应用程序）**。 +5. 在 **Application name（应用程序名称）**下输入 "Jira"。 +6. 在 **Homepage URL（主页 URL）**下，输入 Jira 实例的完整 URL。 +7. 在 **Authorization callback URL（授权回叫 URL）**下，输入 Jira 实例的完整 URL。 +8. 单击 **Register application（注册应用程序）**。 ![注册应用程序按钮](/assets/images/help/oauth/register-application-button.png) +9. 在 **Organization owned applications（组织拥有的应用程序）**下，记下 "Client ID"（客户 ID）和 "Client Secret"（客户端密钥）值。 ![客户端 ID 和客户端密码](/assets/images/help/oauth/client-id-and-secret.png) +{% data reusables.user_settings.jira_help_docs %} + +### 延伸阅读 + +- ["将 Jira 与个人项目集成"](/articles/integrating-jira-with-your-personal-projects) +- 将 Jira Cloud 连接到 GitHub（Atlassian 文档） diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..d64876bc80 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md @@ -0,0 +1,67 @@ +--- +title: 管理组织中仓库的默认标签 +intro: 您可以自定义组织的每个新仓库中包含的标签。 +redirect_from: + - /articles/managing-default-labels-for-repositories-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者可以管理组织中仓库的默认标签。 + +默认标签包含在组织的每个新仓库中，但对仓库具有写入权限的任何人以后都能编辑或删除该仓库中的标签。 添加、编辑或删除默认标签不会从在现有仓库中添加、编辑或删除标签。 + +### 创建默认标签 + +{% 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. 在“Repository labels（仓库标签）”下，单击 **New label（新标签）**。 ![新标签按钮](/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 %} + +### 编辑默认标签 + +{% 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 %} + +### 删除默认标签 + +{% 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 %} + +### 延伸阅读 + +- "[关于标签](/articles/about-labels)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..458496db54 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,30 @@ +--- +title: 管理您组织中仓库的讨论创建 +intro: 您可以选择成员在组织拥有的仓库中创建讨论所需的权限级别。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization +permissions: 组织所有者可以管理组织拥有的仓库的讨论创建。 +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.discussions.beta %} + +### 允许或禁止具有读取权限的用户创建讨论 + +默认情况下，如果仓库管理员或组织所有者为组织拥有的仓库启用了讨论，则具有读取权限的组织成员可以创建讨论。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +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) + +### 延伸阅读 + +- "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[管理社区的讨论](/discussions/managing-discussions-for-your-community)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md new file mode 100644 index 0000000000..bf031bed28 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md @@ -0,0 +1,66 @@ +--- +title: 管理组织的预定提醒 +intro: 对于组织中的团队已请求审查的所有拉取请求，您可以在 Slack 中收到提醒。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +### 关于拉取请求的预定提醒 + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +对于团队的所有拉取请求或团队已经请求审查的所有拉取请求，组织所有者可为其组织中的一个或多个团队预定提醒。 + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### 为组织创建预定提醒 +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![预定提醒按钮](/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. 在“Filter by team assigned to review code（按分配给审查代码的团队过滤）”下，单击 **Add a team（添加团队）**下拉列表并选择一个或多个团队。 您最多可以添加 100 个团队。 如果您选择的团队无法访问上面选择的“跟踪的仓库”，您将无法创建预定提醒。 ![添加团队下拉菜单](/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 %} + +### 管理组织的预定提醒 +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### 删除组织的预定提醒 +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.reminders.scheduled-reminders %} +![预定提醒按钮](/assets/images/help/organizations/scheduled-reminders-org.png) +{% data reusables.reminders.delete %} + +### 延伸阅读 + +- “[管理您的预定提醒](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)” +- “[管理团队的预定提醒](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)” diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..87b5913536 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -0,0 +1,36 @@ +--- +title: 管理组织中仓库的默认分支名称 +intro: 'You can set the default branch name for repositories that members create in your organization.' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization +permissions: Managing the default branch name for your repositories +versions: + free-pro-team: '*' + enterprise-server: '>=2.23' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### About the default branch name + +当组织成员在组织中创建一个新仓库时，该仓库将包含一个分支，它就是默认分支。 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 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)”。 + +### 设置默认分支名称 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. 在“Repository default branch（仓库默认分支）”下，单击 **Change default branch name now（立即更改默认分支名称）**。 ![覆盖按钮](/assets/images/help/organizations/repo-default-name-button.png) +4. 键入要用于新分支的默认名称。 ![输入默认名称的文本框](/assets/images/help/organizations/repo-default-name-text.png) +5. 单击 **Update（更新）**。 ![更新按钮](/assets/images/help/organizations/repo-default-name-update.png) + +### 延伸阅读 + +- /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md new file mode 100644 index 0000000000..158af6ac3f --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md @@ -0,0 +1,28 @@ +--- +title: 管理组织中成员名称的显示 +intro: 您可以允许组织成员在组织的私有仓库中查看评论作者的个人资料名称。 +product: '{% data reusables.gated-features.display-names %}' +redirect_from: + - /articles/managing-the-display-of-member-names-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者可管理组织中成员名称的显示。 + +![评论中显示的评论者个人资料名称](/assets/images/help/issues/commenter-full-name.png) + +每个组织成员在自己的设置中选择自己的个人资料名称。 更多信息请参阅“[个性化您的个人资料](/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. 在“Admin repository permissions（管理仓库权限）”下，选中或取消选中 **Allow members to see comment author's profile name in private repositories（允许成员在私有仓库中查看评论作者的个人资料名称）**。 ![允许成员在私有仓库中查看评论作者的全名复选框](/assets/images/help/organizations/allow-members-to-view-full-names.png) +6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md new file mode 100644 index 0000000000..0d85cfd0fa --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: 管理组织的复刻政策 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization +permissions: 组织所有者可以管理组织组织的复刻政策。 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +默认情况下，新的组织被配置为禁止复刻私有{% 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 %} 仓库，则还可以配置复刻特定{% 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 %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. 在“Repository forking（仓库复刻）”下，选择 **Allow forking of private repositories（允许复刻私有仓库）**或 **Allow forking of private and internal repositories（允许复刻私有和内部仓库）**。 ![允许或禁止组织复刻的复选框](/assets/images/help/repository/allow-disable-forking-organization.png) +6. 单击 **Save（保存）**。 + +### 延伸阅读 + +- "[关于复刻](/articles/about-forks)" +- "[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md new file mode 100644 index 0000000000..a38ad18ddd --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -0,0 +1,34 @@ +--- +title: 管理组织的 GitHub Pages 站点发布 +intro: '您可以控制组织成员是否可以从组织仓库中发布 {% data variables.product.prodname_pages %} 站点，并限制成员是否可以为站点选择可见性{% endif %}。' +permissions: '组织所有者可以管理组织中仓库的 {% data variables.product.prodname_pages %} 站点发布。' +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.0' + github-ae: '*' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization +topics: + - 组织 + - 团队 +--- + +{% if currentVersion == "free-pro-team@latest" %} +If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. 否则，您可以选择允许或禁止公开发布。 有关 {% data variables.product.prodname_pages %} 站点访问权限控制的更多信息，请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 +{% endif %} + +禁止发布 {% data variables.product.prodname_pages %} 站点后，任何已发布的站点仍将保持已发布状态。 您可以手动取消发布站点。 更多信息请参阅“[取消发布 {% data variables.product.prodname_pages %} 站点](/pages/getting-started-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 %}{% if currentVersion == "free-pro-team@latest" %} +1. 在“Pages creation（页面创建）”下，选择要允许的可见性，取消选择要禁止的可见性。 ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png)用于启用 Public Pages 的复选框{% else %} +1. 在“Pages creation（页面创建）”下，选择或取消选择 **Allow members to publish sites（允许成员发布站点）**。 ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png)用于启用 Public Pages 的复选框{% endif %} +1. 单击 **Save（保存）**。 + +### 延伸阅读 + +- "[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..6f3e18fdd6 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,28 @@ +--- +title: 管理组织赞助帐户的更新 +intro: 您可以管理用于接收组织赞助帐户更新的电子邮件地址。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors +versions: + free-pro-team: '*' +permissions: 组织所有者可管理组织赞助帐户的更新。 +topics: + - 组织 + - 团队 +--- + +{% data reusables.sponsors.org-sponsors-release-phase %} + +组织赞助的开发者和组织可向您发送有关其工作的更新。 您可以管理用于接收这些更新的电子邮件地址。 + +您也可以禁用组织赞助帐户的更新。 更多信息请参阅“[管理您的赞助](/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. 在“Sponsors update email (Private)（赞助更新电子邮件（私有））”下，输入要用于接收组织赞助帐户更新的电子邮件地址。 ![输入用于接收被赞助帐户更新的电子邮件地址的文本框](/assets/images/help/sponsors/organization-update-email-textbox.png) +1. 单击 **Update profile（更新个人资料）**。 ![更新个人资料按钮](/assets/images/help/organizations/update-profile-button.png) + +### 延伸阅读 + +- "[使用 {% data variables.product.prodname_sponsors %} 支持开源社区](/github/supporting-the-open-source-community-with-github-sponsors)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md new file mode 100644 index 0000000000..d3ed8a99bc --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md @@ -0,0 +1,50 @@ +--- +title: 重命名组织 +intro: '如果您的项目或公司已更改名称，您可以更新组织的名称以匹配。' +redirect_from: + - /articles/what-happens-when-i-change-my-organization-s-name/ + - /articles/renaming-an-organization + - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% tip %} + +**提示：**只有组织所有者才能重命名组织。 {% data reusables.organizations.new-org-permissions-more-info %} + +{% endtip %} + +### 更改我的组织名称时会发生什么？ + +更改组织名称后，您的旧组织名称可供其他人申请使用。 当您更改组织的名称后，在旧组织名称下对仓库的大多数引用都会更改为新名称。 不过，指向您个人资料的某些链接不会自动重定向。 + +#### 自动进行的更改 + +- {% data variables.product.prodname_dotcom %} 将引用自动重定向到您的仓库。 指向您组织现有**仓库**的 Web 链接将继续有效。 启动更改后，可能需要几分钟时间才能完成。 +- 您可以继续将本地仓库推送到旧的远程跟踪 URL 而不进行更新。 但是，我们建议您在更改组织名称后更新所有现有的远程仓库 URL。 由于您的旧组织名称在更改后可供其他人使用，因此新组织所有者可以创建覆盖仓库重定向条目的仓库。 更多信息请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。 +- 以前的 Git 提交也将正确归于组织内的用户。 + +#### 并非自动的更改 + +更改组织的名称后： +- 指向以前组织资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previousorgname`）将返回 404 错误。 我们建议您更新从其他站点指向组织的链接{% if currentVersion == "free-pro-team@latest" %}，例如 LinkedIn 或 Twitter 个人资料{% endif %}。 +- 使用旧组织名称的 API 请求将返回 404 错误。 我们建议您更新 API 请求中的旧组织名称。 +- There are no automatic [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) redirects for teams that use the old organization's name.{% if currentVersion == "free-pro-team@latest" %} +- If SAML single sign-on (SSO) is enabled for the organization, you must update the organization name in the application for {% data variables.product.prodname_ghe_cloud %} on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."{% endif %} + +### 更改组织的名称 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. 在设置页面底部附近的“Rename organization（重命名组织）”下，单击 **Rename Organization（重命名组织）**。 ![重命名组织按钮](/assets/images/help/settings/settings-rename-organization.png) + +### 延伸阅读 + +* “[我的提交为什么链接到错误的用户？](/articles/why-are-my-commits-linked-to-the-wrong-user)” diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md new file mode 100644 index 0000000000..3760f907da --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -0,0 +1,35 @@ +--- +title: 限制在组织中创建仓库 +intro: '为保护组织的数据，您可以配置在组织中创建仓库的权限。' +redirect_from: + - /articles/restricting-repository-creation-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +您可以选择成员是否可以在组织中创建仓库。 如果允许成员创建仓库，您可以选择允许创建哪些类型的仓库。{% 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" %}企业所有者{% 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 %} + +**警告**：此设置仅限制在仓库创建时可用的可见性选项，而不会限制以后更改仓库可见性的能力。 有关限制更改现有仓库可见性的更多信息，请参阅“[限制组织的仓库可见性更改](/organizations/managing-organization-settings/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. 在“Repository creation（仓库创建）”下，选择一个或多个选项。 ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) +6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md new file mode 100644 index 0000000000..552883ee7d --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -0,0 +1,34 @@ +--- +title: 限制在组织中更改仓库可见性 +intro: '为保护组织的数据，您可以配置在组织中更改仓库可见性的权限。' +redirect_from: + - /articles/restricting-repository-visibility-changes-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +您可以将更改仓库可见性的权限仅限于组织所有者，或者允许具有仓库管理员权限的成员也可以更改仓库可见性。 + +{% warning %} + +**警告**：如果启用，此设置允许具有管理员权限的用户将现有仓库更改为任何可见性，即使您不允许创建该类型的仓库。 有关在创建过程中限制仓库可见性的更多信息，请参阅“[限制组织中的仓库创建](/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. 在“Repository visibility change（仓库可见性更改）”下，取消选择 **Allow members to change repository visibilities for this organization（允许成员为此组织更改仓库可见性）**。 ![允许成员更改仓库可见性的复选框](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) +6. 单击 **Save（保存）**。 + +### 延伸阅读 + +- "[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md new file mode 100644 index 0000000000..e213377597 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -0,0 +1,28 @@ +--- +title: 设置添加外部协作者的权限 +intro: '为了保护组织的数据和组织中使用的付费许可数，您可以只允许所有者邀请外部协作者加入组织仓库。' +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 + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者和具有仓库管理员权限的成员可以邀请外部协作者处理仓库。 您还可以将外部协作者邀请权限仅限于组织所有者。 + +{% 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. 在“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/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md new file mode 100644 index 0000000000..1014b8cb92 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md @@ -0,0 +1,24 @@ +--- +title: 设置删除或转让仓库的权限 +intro: '您可以允许具有仓库管理员权限的组织成员删除或转让仓库，或者将删除或转让仓库的功能限制为仅组织所有者。' +redirect_from: + - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ + - /articles/setting-permissions-for-deleting-or-transferring-repositories + - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +所有者可以设置删除或转让组织中仓库的权限。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. 在 Repository deletion and transfer（仓库删除和转让）下，选择或取消选择 **Allow members to delete or transfer repositories for this organization（允许成员删除或转让此组织的仓库）**。 ![允许成员删除仓库的复选框](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) +6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md new file mode 100644 index 0000000000..ae29ac8d35 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: 设置组织中的团队创建权限 +intro: 您可以允许所有组织成员创建团队或将团队创建限制为组织所有者。 +redirect_from: + - /articles/setting-team-creation-permissions-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者可以设置团队创建权限。 + +如果您没有设置团队创建权限，默认情况下所有组织成员都能够创建团队。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. 在“Team creation rules（团队创建规则）”下，选择或取消选择 **Allow members to create teams（允许成员创建团队）**。 ![允许成员创建团队的复选框](/assets/images/help/organizations/allow-members-to-create-teams.png) +6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md new file mode 100644 index 0000000000..3800ca6b3b --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -0,0 +1,29 @@ +--- +title: 转让组织所有权 +intro: '要使其他人成为组织帐户的所有者，您必须添加新所有者{% if currentVersion == "free-pro-team@latest" %}，确保帐单信息已更新，{% endif %} 然后将自身从该帐户中删除。' +redirect_from: + - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ + - /articles/transferring-organization-ownership + - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +1. 如果您是具有*所有者*权限的唯一成员，则授予其他组织成员所有者角色。 更多信息请参阅“[任命组织所有者](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)”。 +2. 联系新的所有者，确保其能够[访问组织的设置](/articles/accessing-your-organization-s-settings)。 +{% if currentVersion == "free-pro-team@latest" %} +3. 如果您目前负责为组织中的 GitHub 付款，则还需要让新所有者或[帐单管理员](/articles/adding-a-billing-manager-to-your-organization/)更新组织的付款信息。 更多信息请参阅“[添加或编辑付款方式](/articles/adding-or-editing-a-payment-method)”。 + + {% warning %} + + **警告**：从组织中删除自身**不会**更新组织帐户存档的帐单信息。 新的所有者或帐单管理员必须更新存档的帐单信息，以删除您的信用卡或 PayPal 信息。 + + {% endwarning %} + +{% endif %} +4. 从组织中[删除自身](/articles/removing-yourself-from-an-organization)。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/zh-CN/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md new file mode 100644 index 0000000000..f8fa2b5e3c --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -0,0 +1,24 @@ +--- +title: 升级到公司服务条款 +intro: 组织可从标准服务条款升级到公司服务条款。 +redirect_from: + - /articles/upgrading-to-the-corporate-terms-of-service + - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +标准服务条款是 {% data variables.product.prodname_dotcom %} 与您个人之间的协议。 要代表实体（例如公司、非营利性组织或团体）与 {% data variables.product.prodname_dotcom %} 签订协议，组织所有者可升级到公司服务条款。 + +1. 联系 {% 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) +5. 输入拥有该组织帐户的公司、非营利性组织或团体的名称。 这是将与 {% data variables.product.prodname_dotcom %} 签订协议的实体。 ![企业名称字段](/assets/images/help/organizations/business-name-field.png) +6. 要代表您的实体同意公司服务条款，请单击 **Accept terms（接受条款）**。 ![接受条款按钮](/assets/images/help/organizations/accept-terms-button.png) + +### 延伸阅读 +- “[GitHub 公司服务条款](/articles/github-corporate-terms-of-service/)” diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md b/translations/zh-CN/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md new file mode 100644 index 0000000000..02b4791038 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-organization-settings/verifying-your-organizations-domain.md @@ -0,0 +1,42 @@ +--- +title: 验证组织的域 +intro: '您可以验证组织控制的域来确认组织在 {% data variables.product.product_name %} 上的身份。' +redirect_from: + - /articles/verifying-your-organization-s-domain + - /articles/verifying-your-organizations-domain + - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +### 关于域验证 + +要在 {% 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)”。 + +如果您的组织由企业帐户拥有，则“已验证”徽章将显示在组织的基本资料上，除了显示组织的任何已验证域之外，还能够显示企业帐户的任何已验证域。 更多信息请参阅“[验证企业帐户的域](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)”。 + +{% data reusables.organizations.verified-domains-details %} + +在 {% data variables.product.prodname_ghe_cloud %} 上，验证组织域的所有权后，您可以将组织的电子邮件通知限制为该域。 更多信息请参阅“[将电子邮件通知限于经批准的域](/articles/restricting-email-notifications-to-an-approved-domain)”。 + +### 验证组织的域 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.verified-domains %} +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. 等待 DNS 配置更改，最多可能需要 72 小时。 您可以通过在命令行上运行 `dig` 命令来确认您的 DNS 配置已更改，将 `ORGANIZATION` 替换为您组织的名称，将 `example.com` 替换为要验证的域。 您应看到命令输出中列出的新 TXT 记录。 + ```shell + $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT + ``` +8. 确认您的 TXT 记录添加到 DNS 后，导航到组织设置中的 Verified domains（已验证的域）选项卡。 您可以按照上面的步骤 1 至 4 操作找到 Verified domains（已验证的域）选项卡。 ![验证含有待定域的域设置页面](/assets/images/help/organizations/pending-domain-verification.png) +{% data reusables.organizations.continue-verifying-domain %} +11. （可选）组织的资料页面中显示“Verified（已验证）”徽章后，您可以从域托管服务的 DNS 记录中删除 TXT 条目。 ![已验证徽章](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md new file mode 100644 index 0000000000..381def79bc --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -0,0 +1,57 @@ +--- +title: 为组织添加帐单管理员 +intro: '*帐单管理员*是负责为组织管理帐单设置的用户管理员，例如更新付款信息。 如果组织的常规成员通常不能访问帐单资源，这将是一个很好的选择。' +redirect_from: + - /articles/adding-a-billing-manager-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 + - 计费，帐单 +--- + +组织所有者团队的成员可向人们授予*帐单管理员*权限。 在个人接受其邀请成为组织的帐单管理员后，他们可邀请其他人员为帐单管理员。 + +{% note %} + +**注：**帐单管理员在组织的订阅中不使用付费许可。 + +{% endnote %} + +### 帐单管理员的权限 + +帐单管理员可以： + +- 升级或降级帐户 +- 添加、更新或删除付款方式 +- 查看付款历史记录 +- 下载收据 +- 查看、邀请和删除帐单管理员 + +此外，所有帐单管理员在组织的结算日期都会通过电子邮件收到结算收据。 + +帐单管理员**不**能： + +- 在组织中创建或访问仓库 +- 查看组织的私人成员 +- 出现在组织成员列表中 +- 购买、编辑或取消 {% data variables.product.prodname_marketplace %} 应用程序订阅 + +{% tip %} + +**提示：**如果您的组织[要求成员、帐单管理员和外部协作者使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)，则用户必须启用双重身份验证后才可接受您的邀请，成为组织的帐单管理员。 + +{% endtip %} + +### 邀请帐单管理员 + +受邀人员将会收到邀请电子邮件，邀请他们成为您的组织的帐单管理员。 在受邀人员单击其邀请电子邮件中的接受链接后，他们会自动加入组织成为帐单管理员。 如果他们还没有 GitHub 帐户，将被重定向到注册页面注册一个，在创建帐户后会自动加入组织成为帐单管理员。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.billing %} +5. 在帐单管理员旁边，单击 **Add a billing manager（添加帐单管理员）**。 ![邀请帐单管理员](/assets/images/help/billing/settings_billing_managers_list.png) +6. 输入您要添加的人员的用户名或电子邮件地址，然后单击 **Send invitation（发送邀请）**。 ![邀请帐单管理员页面](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md new file mode 100644 index 0000000000..a8709c360d --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md @@ -0,0 +1,29 @@ +--- +title: 向组织成员授予“团队维护员”权限 +intro: '组织所有者可将组织的任何成员升级为团队的*团队维护员*，向他们授予组织所有者的部分权限。' +redirect_from: + - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ + - /articles/giving-team-maintainer-permissions-to-an-organization-member + - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.organizations.team_maintainers_can %} + +### 将组织成员升级为团队维护员 + +在将组织成员升级为团队维护员之前，此人必须已经是该团队的成员。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_members_tab %} +4. 选择要将其升级为团队维护员的人员。 ![组织成员旁的复选框](/assets/images/help/teams/team-member-check-box.png) +5. 在团队成员列表的上方，使用下拉菜单并单击 **Change role...（更改角色...）**。 ![包含更改角色选项的下拉菜单](/assets/images/help/teams/bulk-edit-drop-down.png) +6. 选择新角色并单击 **Change role（更改角色）**。 ![维护员或成员角色的单选按钮](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md new file mode 100644 index 0000000000..b682943a1f --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -0,0 +1,21 @@ +--- +title: 使用角色管理人们对您的组织的访问 +intro: '组织中的人员角色确定他们对您的组织、其设置和数据的访问权限。 您可以将人们设为组织的所有者、成员或帐单管理员，或者向他们授予团队维护员权限。' +redirect_from: + - /articles/managing-people-s-access-to-your-organization-with-roles + - /articles/managing-peoples-access-to-your-organization-with-roles + - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md new file mode 100644 index 0000000000..8bdbdebcce --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md @@ -0,0 +1,32 @@ +--- +title: 保持组织的所有权连续性 +intro: 为避免所有权失效，组织可以有多个组织所有者。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization +permissions: 组织所有者可以将组织的任何成员提升为组织所有者。 +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### 关于保持组织的所有权连续性 + +{% data reusables.organizations.org-ownership-recommendation %} + +组织所有者对组织具有完全管理权限。 {% data reusables.organizations.new-org-permissions-more-info %} + +### 任命组织所有者 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.people %} +4. 选择要晋升为所有者的人员。 ![选择了两名成员的成员列表](/assets/images/help/teams/list-of-members-selected-bulk.png) +5. 在成员列表的上方，使用下拉菜单并单击 **Change role（更改角色）**。 ![包含删除成员选项的下拉菜单](/assets/images/help/teams/user-bulk-management-options.png) +6. 为人员选择新角色，然后单击 **Change role（更改角色）**。 ![选择所有者和成员角色的单选按钮和更改角色按钮](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md new file mode 100644 index 0000000000..cbfd56f0ad --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -0,0 +1,147 @@ +--- +title: 组织的权限级别 +intro: '在 [创建组织](/articles/creating-a-new-organization-account) 后，您应向一小组负责管理组织帐户的人授予所有者权限。' +redirect_from: + - /articles/permission-levels-for-an-organization-early-access-program/ + - /articles/permission-levels-for-an-organization + - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +### 组织的权限级别 + +组织成员可以是*所有者*{% if currentVersion == "free-pro-team@latest" %}、*帐单管理员*{% endif %} 或*成员*角色。 + +- **所有者**对组织具有全面的管理权限。 此角色应限于组织中的少数几个人，但不少于两人。 更多信息请参阅“[管理组织的所有权连续性](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)”。 +{% if currentVersion == "free-pro-team@latest" %} +- **帐单管理员**允许个人管理帐单设置。 更多信息请参阅“[为组织添加帐单管理员](/articles/adding-a-billing-manager-to-your-organization)”。 +{% endif %} +- **成员**是其他每个人的默认角色。 + +{% if currentVersion == "free-pro-team@latest" %} + + +| 组织操作 | 所有者 | 成员 | 帐单管理员 | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:| +| 创建仓库（详细信息请参阅“[限制在组织中创建仓库](/articles/restricting-repository-creation-in-your-organization)”） | **X** | **X** | | +| 查看和编辑帐单信息 | **X** | | **X** | +| 邀请人员加入组织 | **X** | | | +| 编辑和取消邀请加入组织 | **X** | | | +| 从组织删除成员 | **X** | | | +| 恢复组织的前成员 | **X** | | | +| 添加和删除**所有团队**的人员 | **X** | | | +| 将组织成员升级为*团队维护员* | **X** | | | +| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”） | **X** | | | +| 设置预定提醒（请参阅“[管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)”） | **X** | | | +| 添加协作者到**所有仓库** | **X** | | | +| 访问组织审核日志 | **X** | | | +| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”） | **X** | | | +| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”） | **X** | | | +| 将电子邮件通知限制为经验证的域（更多信息请参阅“[将电子邮件通知限制为经批准的域](/organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain)”） | **X** | | | +| 删除**所有团队** | **X** | | | +| 删除组织帐户，包括所有仓库 | **X** | | | +| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”） | **X** | **X** | | +| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”） | **X** | **X** | | +| 查看所有组织成员和团队 | **X** | **X** | | +| @提及任何可见团队 | **X** | **X** | | +| 可成为*团队维护员* | **X** | **X** | | +| 查看组织洞见（详细信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization)”） | **X** | **X** | | +| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”） | **X** | **X** | | +| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”） | **X** | | | +| 编辑和删除**所有团队**的团队讨论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”） | **X** | | | +| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”） | **X** | **X** | | +| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | | +| 管理组织依赖项洞见的显示（详细信息请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”） | **X** | | | +| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | | +| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”） | **X** | **X** | | +| 管理赞助帐户的电子邮件更新（更多信息请参阅“[管理组织赞助帐户的更新](/organizations/managing-organization-settings/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 %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | | | +| 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | **X** | | | +| 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | +| [管理用户对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | +| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”） | **X** | | | +| 转让仓库 | **X** | | | +| 购买、安装、管理其帐单以及取消 {% data variables.product.prodname_marketplace %} 应用程序 | **X** | | | +| 列出 {% data variables.product.prodname_marketplace %} 中的应用程序 | **X** | | | +| 接收所有组织仓库[关于易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | **X** | | | +| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”） | **X** | | | +| [管理复刻策略](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** | | | +| [限制组织中公共仓库的活动](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | | +| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库* | **X** | | | +| 将组织成员转换为[外部协作者](#outside-collaborators) | **X** | | | +| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository) | **X** | | | +| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | +| Manage the default branch name (see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)") | **X** | | | +| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | | | +| 启用团队同步（详情请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”） | **X** | | | + +{% else %} + + +| 组织操作 | 所有者 | 成员 | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------------------------------------------------------------------------:| +| 邀请人员加入组织 | **X** | | +| 编辑和取消邀请加入组织 | **X** | | +| 从组织删除成员 | **X** | | | +| 恢复组织的前成员 | **X** | | | +| 添加和删除**所有团队**的人员 | **X** | | +| 将组织成员升级为*团队维护员* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”） | **X** | +{% endif %} +| 添加协作者到**所有仓库** | **X** | | +| 访问组织审核日志 | **X** | | +| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/articles/about-your-organization-s-profile)”） | **X** | | | +| 删除**所有团队** | **X** | | +| 删除组织帐户，包括所有仓库 | **X** | | +| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”） | **X** | **X** | +| 查看所有组织成员和团队 | **X** | **X** | +| @提及任何可见团队 | **X** | **X** | +| 可成为*团队维护员* | **X** | **X** | +| 转让仓库 | **X** | | +| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”） | **X** | | +| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”） | **X** | **X** | | +| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”） | **X** | **X** | | +| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”） | **X** | | | +| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”） | **X** | | | +| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”） | **X** | **X** | **X** | +| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | | +| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | |{% if currentVersion ver_gt "enterprise-server@3.0" %} +| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | +{% endif %} +| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | +| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库* | **X** | | +| 将组织成员转换为[外部协作者](#outside-collaborators) | **X** | | +| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository) | **X** | | +| [导出具有组织仓库访问权限人员的列表](/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" %} +| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”） | **X** | +{% endif %} +{% if currentversion == "github-ae@latest" %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** |{% endif %} + +{% endif %} + +### {% data variables.product.prodname_github_app %} 管理员 + +默认情况下，只有组织所有者才可管理组织拥有的 {% data variables.product.prodname_github_app %} 的设置。 要允许其他用户管理组织拥有的 {% data variables.product.prodname_github_app %}，所有者可向他们授予 {% data variables.product.prodname_github_app %} 管理员权限。 + +指定用户为组织中 {% data variables.product.prodname_github_app %} 的管理员时，您可以授予他们对组织拥有的部分或全部 {% data variables.product.prodname_github_app %} 的设置进行管理的权限。 更多信息请参阅： + +- "[为组织添加 GitHub 应用程序管理员](/articles/adding-github-app-managers-in-your-organization)" +- "[从组织删除 GitHub 应用程序管理员](/articles/removing-github-app-managers-from-your-organization)" + +### 外部协作者 + +在允许访问仓库时，为确保组织数据的安全，您可以添加*外部协作者*。 {% data reusables.organizations.outside_collaborators_description %} + +### 延伸阅读 + +- "[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)" +- "[关于团队](/articles/about-teams)" +- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md new file mode 100644 index 0000000000..269cd47c1e --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md @@ -0,0 +1,25 @@ +--- +title: 从组织中删除帐单管理员 +intro: '如果具有*帐单管理员*角色的人员不再需要查看或更改组织的帐单信息，您可以删除其对组织的访问权限。' +redirect_from: + - /articles/removing-a-billing-manager-from-your-organization + - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 + - 计费，帐单 +--- + +{% warning %} + +**注：**{% 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. 在 Billing managers（帐单管理员）列表中您要删除的人员姓名旁边，单击 {% octicon "x" aria-label="X symbol" %}。 ![删除帐单管理员](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md new file mode 100644 index 0000000000..f067c82f55 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -0,0 +1,62 @@ +--- +title: 关于使用 SAML 单点登录管理身份和访问 +intro: '如果您使用身份提供程序 (IdP) 集中管理用户身份和应用程序，可以配置安全声明标记语言 (SAML) 单点登录 (SSO) 来保护组织在 {% 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 + - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +### 关于 SAML SSO + +{% data reusables.saml.dotcom-saml-explanation %} + +配置 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，企业所有者可以为企业帐户中的所有组织强制实施 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 %} + +在为您的组织启用 SAML SSO 之前，您需要将 IdP 连接到组织。 更多信息请参阅“[将身份提供程序连接到组织](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)”。 + +对于组织，SAML SSO 可以禁用、启用但不实施或者启用并实施。 为组织启用 SAML SSO 并且组织成员使用 IdP 成功完成身份验证后，您可以实施 SAML SSO 配置。 有关对 {% data variables.product.prodname_dotcom %} 组织实施 SAML SSO 的更多信息，请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 + +成员必须定期使用您的 IdP 进行身份验证，以获得对组织资源的访问权限。 此登录期的持续时间由 IdP 指定，一般为 24 小时。 此定期登录要求会限制访问的时长，您必须重新验证身份后才可继续访问。 + +要在命令行使用 API 和 Git 访问组织受保护的资源，成员必须授权并使用个人访问令牌或 SSH 密钥验证身份。 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”和“[授权 SSH 密钥用于 SAML 单点登录](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。 + +成员第一次使用 SAML SSO 访问您的组织时，{% data variables.product.prodname_dotcom %} 会自动创建一条记录，以链接您的组织、成员的 {% data variables.product.prodname_dotcom %} 帐户以及成员在 IdP 上的帐户。 您可以查看和撤销组织成员或企业帐户关联的 SAML 身份、活动的会话以及授权的凭据。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)”和“[查看和管理用户对企业帐户的 SAML 访问](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)”。 + +如果成员在创建新的仓库时使用 SAML SSO 会话登录，则该仓库的默认可见性为私密。 否则，默认可见性为公开。 有关仓库可见性的更多信息，请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)。” + +组织成员还必须具有活动的 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 %} + +有些 IdP 支持配置通过 SCIM 访问 {% data variables.product.prodname_dotcom %} 组织。 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 + +### 使用 SAML SSO 添加成员到组织 + +在启用 SAML SSO 后，可通过多种方式向组织添加新成员。 组织所有者可在 {% data variables.product.product_name %} 上或使用 API 手动邀请新成员。 更多信息请参阅“[邀请用户加入组织](/articles/inviting-users-to-join-your-organization)”和“[成员](/rest/reference/orgs#add-or-update-organization-membership)”。 + +要供应新用户而不使用组织所有者的邀请，您可以使用 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](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 + +{% data reusables.organizations.team-synchronization %} + +{% data reusables.saml.saml-single-logout-not-supported %} + +### 延伸阅读 + +- "[关于双重身份验证和 SAML 单点登录](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md new file mode 100644 index 0000000000..99cbc5a779 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -0,0 +1,31 @@ +--- +title: 关于 SCIM +intro: '通过“跨域身份管理系统”(System for Cross-domain Identity Management, SCIM)，管理员可以在系统之间自动交换用户身份信息。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/about-scim + - /github/setting-up-and-managing-organizations-and-teams/about-scim +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +如果在组织中使用 [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)，您可以实施 SCIM 来添加、管理和删除组织成员对 {% data variables.product.product_name %} 的访问权限。 例如，管理员可以使用 SCIM 撤销配置组织成员，以及从组织中自动删除成员。 + +如果您使用 SAML SSO 而不实施 SCIM，将不能自动撤销配置。 当组织成员的会话在其访问权限从 IdP 删除后到期时，他们就会自动从组织中删除。 即使会话已到期，通过授权的令牌也可授予对组织的访问。 要删除访问权限，组织管理员可以手动从组织删除授权的令牌，或者通过 SCIM 自动执行删除。 + +这些身份提供程序兼容组织的 {% data variables.product.product_name %} SCIM API。 更多信息请参阅 {% data variables.product.product_name %} API 文档中的 [SCIM](/rest/reference/scim)。 +- Azure AD +- Okta +- OneLogin + +{% data reusables.scim.enterprise-account-scim %}更多信息请参阅“[关于企业帐户中组织的用户配置](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)”。 + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[将身份提供程序连接到组织](/articles/connecting-your-identity-provider-to-your-organization)" +- "[对组织启用并测试 SAML 单点登录](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" +- "[查看和管理成员对组织的 SAML 访问](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md new file mode 100644 index 0000000000..5e26e15756 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -0,0 +1,31 @@ +--- +title: 身份提供程序不可用时访问组织 +intro: '即使身份提供程序不可用，组织管理员也可绕过单点登录使用其恢复代码登录 {% data variables.product.product_name %}。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable + - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +组织管理员可以使用[下载或保存的恢复代码](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)绕过单点登录。 您可能已将这些保存到密码管理器，如 [LastPass](https://lastpass.com/)、[1Password](https://1password.com/) 或 [Keeper](https://keepersecurity.com/)。 + +{% note %} + +**注：**恢复代码只能使用一次，并且必须按连续的顺序使用。 恢复代码授予 24 小时访问权限。 + +{% endnote %} + +1. 在单点登录对话框底部，单击 **Use a recovery code（使用恢复代码）**绕过单点登录。 ![用于输入恢复代码的链接](/assets/images/help/saml/saml_use_recovery_code.png) +2. 在 "Recovery Code"（恢复代码）字段中，输入您的恢复代码。 ![无法输入恢复代码](/assets/images/help/saml/saml_recovery_code_entry.png) +3. 单击 **Verify（验证）**。 ![用于确认恢复代码的按钮](/assets/images/help/saml/saml_verify_recovery_codes.png) + +请务必注意，恢复代码在使用后便不再有效。 恢复代码不能重复使用。 + +### 延伸阅读 + +- "[关于使用 SAML SSO 管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md new file mode 100644 index 0000000000..1c4838f2cf --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -0,0 +1,81 @@ +--- +title: 使用 Octa 配置 SAML 单个登录和 SCIM +intro: '您可以使用安全声明标记语言 (SAML) 单点登录 (SSO) 和跨域身份管理系统 (SCIM) 与 Okta 一起来自动管理对 {% data variables.product.prodname_dotcom %} 上组织的访问。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta +product: '{% data reusables.gated-features.saml-sso %}' +permissions: 组织所有者可以使用 Okta 为组织配置 SAML SSO 和 SCIM。 +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +### 关于 SAML 和 SCIM 与 Octa + +您可以通过配置组织使用 SAML SSO 和 SCIM 以及身份提供程序 (IdP) Okta，从一个中心界面控制对 {% data variables.product.prodname_dotcom %} 组织及其他 web 应用程序的访问。 + +SAML SSO 控制并保护对组织资源（如仓库、议题和拉取请求）的访问。 当您在 Octa 中进行更改时，SCIM 会自动添加、管理和删除成员对您的 {% data variables.product.prodname_dotcom %} 组织的访问权限。 更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”和“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 + +启用 SCIM 后，您在 Okta 中为其分配了 {% data variables.product.prodname_ghe_cloud %} 应用程序的任何用户都可以使用以下配置。 + +| 功能 | 描述 | +| -------- | -------------------------------------------------------------------------------------------------- | +| 推送新用户 | 在 Okta 中创建新用户时，该用户将收到一封电子邮件，让其加入您的 {% data variables.product.prodname_dotcom %} 组织。 | +| 推送用户停用 | 当您在 Okta 中停用某用户时，Okta 会将该用户从您的 {% data variables.product.prodname_dotcom %} 组织中删除。 | +| 推送个人资料更新 | 当您在 Okta 中更新某用户的个人资料时，Okta 会在您的 {% data variables.product.prodname_dotcom %} 组织中更新该用户成员资格的元数据。 | +| 重新激活用户 | 当您在 Okta 中重新激活某用户时，Okta 会向该用户发送一封邀请电子邮件，邀请其重新加入您的 {% data variables.product.prodname_dotcom %} 组织。 | + +### 基本要求 + +{% data reusables.saml.use-classic-ui %} + +### 在 Okta 中添加 {% data variables.product.prodname_ghe_cloud %} 应用程序 + +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.add-okta-application %} +{% data reusables.saml.search-ghec-okta %} +4. 在“Github Enterprise Cloud - Organization（Github Enterprise Cloud - 组织）”的右侧单击 **Add（添加）**。 ![对 {% data variables.product.prodname_ghe_cloud %} 应用程序单击"Add（添加）"](/assets/images/help/saml/okta-add-ghec-application.png) + +5. 在 **GitHub Organization（GitHub 组织）**字段中，键入您的 {% data variables.product.prodname_dotcom %} 组织的名称。 例如，如果组织的 URL 是 https://github.com/octo-org，则组织名称为 `octo-org`。 ![键入 GitHub 组织名称](/assets/images/help/saml/okta-github-organization-name.png) + +6. 单击 **Done（完成）**。 + +### 启用和测试 SAML SSO + +{% 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. 按照“如何配置 SAML 2.0”指南，使用登录 URL、发行机构 URL 和公共证书在 {% data variables.product.prodname_dotcom %} 上启用并测试 SAML SSO。 更多信息请参阅“[对组织启用并测试 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)”。 + +### 在 Okta 中使用 SCIM 配置访问配置 + +{% 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. 单击 **Authenticate with Github Enterprise Cloud - Organization（向 Github Enterprise Cloud 验证 - 组织）**。 ![Okta 应用程序的"Authenticate with Github Enterprise Cloud - Organization（ 向 Github Enterprise Cloud 验证 - 组织）"按钮](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) + +7. 在组织名称的右侧，单击 **Grant（授予）**。 ![用于授权 Okta SCIM 集成访问组织的"Grant（授予）"按钮](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) + + {% note %} + + **注**：如果在列表中看不到您的组织，请在浏览器中访问 `https://github.com/orgs/ORGANIZATION-NAME/sso`，并使用 IdP 上的管理员帐户通过 SAML SSO 向您的组织验证身份。 例如，如果您的组织名称是 `octo-org`，则 URL 是 `https://github.com/orgs/octo-org/so`。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”。 + + {% endnote %} +1. 单击 **Authorize OktaOAN（授权 OktaOAN）**。 ![用于授权 Okta SCIM 集成访问组织的"Authorize OktaOAN（授权 OktaOAN）"按钮](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} + +### 延伸阅读 + +- “[使用 Okta 为企业帐户配置 SAML 单点登录和 SCIM](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)” +- "[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" +- Okta 文档中的[了解 SAML](https://developer.okta.com/docs/concepts/saml/) +- Okta 文档中的[了解 SCIM](https://developer.okta.com/docs/concepts/scim/) diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md new file mode 100644 index 0000000000..ab1e0c31c9 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -0,0 +1,34 @@ +--- +title: 将身份提供程序连接到组织 +intro: '要使用 SAML 单点登录和 SCIM，必须将身份提供程序连接到您的 {% data variables.product.product_name %} 组织。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/connecting-your-identity-provider-to-your-organization + - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +在您的 {% data variables.product.product_name %} 组织中[启用 SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) 之前，需要将身份提供程序 (IdP) 连接到您的组织。 + +您可以在以下文档中找到 IdP 的 SAML 和 SCIM 实现详细信息： +- 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) 和 [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) 和 [SCIM](http://developer.okta.com/standards/SCIM/) +- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) 和 [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 %} + +**注：**{% data variables.product.product_name %} 支持的用于 SCIM 的身份提供程序为 Azure AD、Okta 和 OneLogin。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/articles/about-scim)”。 + +{% endnote %} + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- "[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md new file mode 100644 index 0000000000..be863612e9 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -0,0 +1,36 @@ +--- +title: 下载组织的 SAML 单点登录恢复代码 +intro: '组织管理员应下载组织的 SAML 单点登录恢复代码，以确保即使组织的身份提供程序不可用，也可以访问 {% data variables.product.product_name %}。' +redirect_from: + - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes + - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes + - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes +product: '{% data reusables.gated-features.saml-sso %}' +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +恢复代码不应共享或分发。 我们建议使用一个密码管理器保存它们，例如 [LastPass](https://lastpass.com/)、 [1Password](https://1password.com/) 或 [Keeper](https://keepersecurity.com/)。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.security %} +5. 在“SAML single sign-on”（SAML 单点登录）下，在有关恢复代码的注释中，单击 **Save your recovery codes（保存恢复代码）**。 ![查看和保存恢复代码的链接](/assets/images/help/saml/saml_recovery_codes.png) +6. 通过单击 **Download（下载）**、**Print（打印）** 或 **Copy（复制）**保存恢复代码。 ![下载、打印或复制恢复代码的按钮](/assets/images/help/saml/saml_recovery_code_options.png) + + {% note %} + + **注：** 如果您的 IdP 不可用，恢复代码将帮助您返回 {% data variables.product.product_name %}。 如果生成新的恢复代码，“单点登录恢复代码”页面上显示的恢复代码会自动更新。 + + {% endnote %} + +7. 使用恢复代码重新获得 {% data variables.product.product_name %} 的访问权限后，无法重复使用该恢复代码。 对 {% data variables.product.product_name %} 的访问权限将仅在 24 小时内可用，之后系统会要求您使用单点登录进行登录。 + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" +- “[在身份提供程序不可用的情况下访问组织](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)” diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..de857b3d31 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,51 @@ +--- +title: 启用和测试组织的 SAML 单点登录 +intro: 组织所有者和管理员可以启用 SAML 单点登录，以将额外的安全层添加到其组织。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +无需所有成员使用 SAML SSO，即可在组织中将其启用。 在组织中启用但不实施 SAML SSO 可帮助组织顺利采用 SAML SSO。 一旦组织内的大多数成员使用 SAML SSO，即可在组织内将其实施。 + +如果启用但不实施 SAML SSO，则选择不使用 SAML SSO 的组织成员仍可以是组织的成员。 有关实施 SAML SSO 的更多信息，请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 + +{% data reusables.saml.outside-collaborators-exemption %} + +在组织中实施 SAML SSO 之前，请确保已设置身份提供程序 (IdP)。 更多信息请参阅“[准备在组织中实施 SAML 单点登录](/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. 在“SAML single sign-on”（SAML 单点登录）下，选择 **Enable SAML authentication（启用 SAML 身份验证）**。 ![用于启用 SAML SSO 的复选框](/assets/images/help/saml/saml_enable.png) + + {% note %} + + **注意：** 启用 SAML SSO 后，可以下载单点登录恢复代码，以便即使 IdP 不可用也可以访问组织。 更多信息请参阅“[下载组织的单点登录恢复代码](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)”。 + + {% endnote %} + +6. 在“Sign on URL”（登录 URL）字段中，为单点登录请求输入 IdP 上的 HTTPS 端点。 此值可在 IdP 配置中找到。 ![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url.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. 单击 {% 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) + + {% tip %} + + **提示：** {% data reusables.saml.testing-saml-sso %} + + {% endtip %} +11. 要实施 SAML SSO 并删除未通过 IdP 进行身份验证的所有组织成员，请选择 **Require SAML SSO authentication for all members of the _organization name_ organization（要求组织的所有成员进行 SAML SSO 身份验证）**。 有关实施 SAML SSO 的更多信息，请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 ![对组织要求 SAML SSO 的复选框 ](/assets/images/help/saml/saml_require_saml_sso.png) +12. 单击 **Save（保存）**。 ![保存 SAML SSO 设置的按钮](/assets/images/help/saml/saml_save.png) + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md new file mode 100644 index 0000000000..75e95c05ac --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: 实施组织的 SAML 单点登录 +intro: 组织所有者和管理员可以实施 SAML SSO，以便所有组织成员都必须通过身份提供程序进行身份验证。 +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/enforcing-saml-single-sign-on-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +如果您在组织中实施 SAML SSO，则任何成员（包括未通过 SAML 身份提供程序 (IdP) 进行身份验证的管理员）都将从组织中删除，并会收到一封告知此类删除的电子邮件。 未在组织的 IdP 中设置外部身份的自动程序和服务帐户也将被删除。 有关自动程序和服务帐户的更多信息，请参阅“[使用 SAML 单点登录管理自动程序和服务帐户](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)”。 成功完成单点登录后，可以恢复组织成员。 + +如果您的组织由企业帐户拥有，则为企业帐户启用 SAML 将覆盖组织级的 SAML 配置。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)”。 + +{% tip %} + +**提示：** {% data reusables.saml.testing-saml-sso %} + +{% endtip %} + +1. 启用和测试组织的 SAML SSO。 有关此过程的更多信息，请参阅“[启用和测试组织的 SAML 单点登录](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)”。 +2. 选择 **Require SAML SSO authentication for all members of the SAML SSO Org organization（要求对 SAML SSO 组织的所有成员进行 SAML SSO 身份验证）**后，将显示未通过您的 IdP 进行身份验证的组织成员。 如果实施 SAML SSO，则将从组织中删除这些成员。 +3. 单击 **Enforce SAML SSO（实施 SAML SSO）**，以实施 SAML SSO 并删除所列的组织成员。 + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md new file mode 100644 index 0000000000..afd517d526 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -0,0 +1,24 @@ +--- +title: 管理组织的 SAML 单点登录 +intro: 组织管理员可以使用 SAML 单点登录 (SSO) 管理组织成员的身份以及对组织的访问。 +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 + - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md new file mode 100644 index 0000000000..9a675c1b65 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -0,0 +1,79 @@ +--- +title: 管理组织的团队同步 +intro: '您可以在身份提供程序 (IdP) 与 {% 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 + - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization +permissions: 组织所有者可管理组织的团队同步。 +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.gated-features.okta-team-sync %} + +### 关于团队同步 + +您可以在 IdP 与 {% data variables.product.product_name %} 之间启用团队同步，以允许组织所有者和团队维护员将组织中的团队与 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 %} + +您还可以为企业帐户拥有的组织启用团队同步。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)”。 + +### 启用团队同步 + +启用团队同步的步骤取决于要使用的 IdP。 有些启用团队同步的基本要求适用于每个 IdP。 每个 IdP 都有额外的基本要求。 + +#### 基本要求 + +{% data reusables.identity-and-permissions.team-sync-required-permissions %} + +您必须为您的组织和支持的 IdP 启用 SAML 单点登录。 更多信息请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 + +您必须使用 SAML SSO 和支持的 IdP 向组织验证。 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。 + +#### 为 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. 查看要与组织连接的身份提供程序租户信息，然后单击 **Approve（批准）**。 ![启用特定 IdP 租户团队同步且含有批准或取消请求选项的待处理请求](/assets/images/help/teams/approve-team-synchronization.png) + +#### 为 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. 在组织名称下，输入有效的 SSWS 令牌和 Okta 实例的 URL。 ![启用团队同步 Okta 组织表单](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) +6. 查看要与组织连接的身份提供程序租户信息，然后单击 **Create（创建）**。 ![启用团队同步创建按钮](/assets/images/help/teams/confirm-team-synchronization-okta.png) + +### 禁用团队同步 + +{% 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. 在“Team synchronization（团队同步）”下，单击 **Disable team synchronization（禁用团队同步）**。 ![禁用团队同步](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md new file mode 100644 index 0000000000..fcb9cd9336 --- /dev/null +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: 准备在组织中实施 SAML 单点登录 +intro: '在组织中实施 SAML 单点登录之前，应验证组织的成员资格，并配置到身份提供程序的连接设置。' +product: '{% data reusables.gated-features.saml-sso %}' +redirect_from: + - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization + - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +当您在组织中[实施 SAML 单点登录](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)时，未通过身份提供程序 (IdP) 验证的成员将从组织中删除，并且会收到通知删除的电子邮件。 + +在组织中实施 SAML SSO 之前，您应该： + +- 根据需要[添加](/articles/inviting-users-to-join-your-organization)或[删除](/articles/removing-a-member-from-your-organization)组织中的成员。 +- 如果您尚未将 IdP 连接到组织，请连接。 更多信息请参阅“[将身份提供程序连接到组织](/articles/connecting-your-identity-provider-to-your-organization)”。 +- 确保组织成员已登录并且将其帐户与 IdP 链接。 + +{% data reusables.saml.outside-collaborators-exemption %} + +### 延伸阅读 + +- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..d75ae0ede8 --- /dev/null +++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md @@ -0,0 +1,32 @@ +--- +title: 将管理员团队转换为改进的组织权限 +intro: '如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认具有改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的权限模型。 旧管理员团队的成员在其团队被迁移到改进的组织权限模型之前，自动保留创建仓库的权限。' +redirect_from: + - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ + - /articles/converting-an-admin-team-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +要删除旧管理员团队成员创建仓库的权限，请为这些成员创建新团队，确保该团队对组织仓库具有必要的权限，然后删除旧管理员团队。 + +更多信息请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization/)”。 + +{% warning %} + +**警告：** +- 如果旧管理员团队中有成员不是其他团队的成员，则删除该团队将导致从组织中删除这些成员。 在删除该团队之前，请确保其成员已经是组织的直接成员，或者具有对必要仓库的协作者权限。 +- 为防止丢失旧管理员团队成员创建的私有复刻，在删除旧管理员团队之前必须完成下面的步骤 1-3。 +- 由于“管理员”是用于[对某些仓库具有特定权限](/articles/repository-permission-levels-for-an-organization)的组织成员的术语，因此我们建议在您决定的任何团队名称中避免使用该术语。 + +{% endwarning %} + +1. [创建新团队](/articles/creating-a-team)。 +2. [将旧管理员团队的每个成员添加](/articles/adding-organization-members-to-a-team)到新团队。 +3. 对于旧团队可访问的每个仓库，[为新团队提供同等的访问权限](/articles/managing-team-access-to-an-organization-repository) 。 +4. [删除旧管理员团队](/articles/deleting-a-team)。 diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md new file mode 100644 index 0000000000..d1d8932097 --- /dev/null +++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md @@ -0,0 +1,52 @@ +--- +title: 将所有者团队转换为改进的组织权限 +intro: '如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认具有改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的权限模型。 “所有者”现在是赋予组织中个别成员的管理角色。 旧所有者团队的成员自动获得所有者权限。' +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 + - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +您可以通过几种方式转换旧所有者团队： + +- 给团队一个新名称以表明其成员在组织中具有特殊地位。 +- 在确保所有成员已被添加到对组织仓库具有必要权限的其他团队后，删除该团队。 + +### 给所有者团队一个新名称 + +{% tip %} + + **注：**由于“管理员”是用于[对某些仓库具有特定权限](/articles/repository-permission-levels-for-an-organization)的组织成员的术语，因此我们建议在您决定的任何团队名称中避免使用该术语。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. 在团队名称字段中，为所有者团队选择一个新名称。 例如： + - 如果组织中只有极少数成员是所有者团队的成员，您可以将该团队命名为“核心”。 + - 如果组织中的所有成员都是所有者团队的成员（以便他们能够 [@提及团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)），您可以将该团队命名为“员工”。 ![在团队名称字段将所有者团队重命名为核心](/assets/images/help/teams/owners-team-new-name.png) +6. 在团队说明下，单击 **Save and continue（保存并继续）**。 ![保存并继续按钮](/assets/images/help/teams/owners-team-save-and-continue.png) +7. （可选）[让团队*公开*](/articles/changing-team-visibility)。 + +### 删除旧所有者团队 + +{% warning %} + +**警告：**如果所有者团队中有成员不是其他团队的成员，则删除该团队将导致从组织中删除这些成员。 在删除该团队之前，请确保其成员已经是组织的直接成员，或者具有对必要仓库的协作者权限。 + +{% endwarning %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.owners-team %} +{% data reusables.organizations.convert-owners-team-confirm %} +5. 在页面底部，查看警告，然后单击 **Delete the Owners team（删除所有者团队）**。 ![删除所有者团队的链接](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md new file mode 100644 index 0000000000..2e05a6a553 --- /dev/null +++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md @@ -0,0 +1,20 @@ +--- +title: 迁移到改进的组织权限 +intro: '如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认包括改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的组织权限模型。' +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 + - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md new file mode 100644 index 0000000000..dd75577d16 --- /dev/null +++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md @@ -0,0 +1,44 @@ +--- +title: 将管理团队迁移到改进的组织权限 +intro: '如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认具有改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的权限模型。 旧管理员团队的成员在其团队被迁移到改进的组织权限模型之前，自动保留创建仓库的权限。' +redirect_from: + - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ + - /articles/migrating-admin-teams-to-improved-organization-permissions + - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions +versions: + free-pro-team: '*' + enterprise-server: '*' +topics: + - 组织 + - 团队 +--- + +默认情况下，所有组织成员都可以创建仓库。 如果将[仓库创建权限](/articles/restricting-repository-creation-in-your-organization)限于组织所有者，并且您的组织已在旧组织权限结构下创建，则旧管理员团队的成员仍可创建仓库。 + +旧管理员团队是在旧组织权限结构下使用管理员权限级别创建的团队。 这些团队成员可以为组织创建仓库，我们在改进的组织权限结构中保留了这种能力。 + +您可以将旧管理员团队迁移到改进的组织权限，以删除此能力。 + +更多信息请参阅“[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)”。 + +{% warning %} + +**警告：**如果您的组织对所有成员禁用了[仓库创建权限](/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.teams_sidebar %} +1. 检查组织的旧管理员团队，然后单击 **Migrate all teams（迁移所有团队）**。 ![迁移所有团队按钮](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) +1. 阅读这些团队成员的可能权限更改的信息，然后单击 **Migrate all teams（迁移所有团队）**。 ![确认迁移按钮](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) + +### 迁移单一管理员团队 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +1. 在团队说明框中，单击 **Migrate team（迁移团队）**。 ![迁移团队按钮](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md new file mode 100644 index 0000000000..9e87e74cf6 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md @@ -0,0 +1,79 @@ +--- +title: 关于团队 +intro: 团队是通过级联访问权限和提及来反映公司或群组结构的组织成员组。 +redirect_from: + - /articles/about-teams + - /github/setting-up-and-managing-organizations-and-teams/about-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +![组织中的团队列表](/assets/images/help/teams/org-list-of-teams.png) + +组织所有者和团队维护员可向团队授予仓库的管理员、读取或写入权限。 组织成员可通过提及团队的名称向整个团队发送通知。 组织成员也可通过向该团队申请审查来发送通知给整个团队。 组织成员可以向能够读取其中打开了拉取请求的仓库的特定团队申请审查。 可在 CODEOWNERS 文件中将团队指定为某些代码类型或区域的所有者。 + +更多信息请参阅： +- "[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)" +- "[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" +- "[关于代码所有者](/articles/about-code-owners/)" + +![团队提及图像](/assets/images/help/teams/team-mention.png) + +{% if enterpriseServerVersions contains currentVersion %} + +您也可以使用 LDAP 同步根据建立的 LDAP 组同步 {% data variables.product.product_location %} 团队成员和团队角色。 这可让您从 LDAP 服务器为用户建立基于角色的访问控制，而无需在 {% data variables.product.product_location %} 中手动创建。 更多信息请参阅“[启用 LDAP 同步](/enterprise/{{ page.version }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)”。 + +{% endif %} + +{% data reusables.organizations.team-synchronization %} + +### 团队可见性 + +{% data reusables.organizations.types-of-team-visibility %} + +### 团队页面 + +每个团队都在组织中有自己的页面。 在团队的页面上，您可以查看团队成员、子团队和团队的仓库。 组织所有者和团队维护员可从团队页面访问团队设置以及更新团队的说明和头像。 + +组织成员可以创建和参与团队讨论。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 + +![列出团队成员和讨论的团队页面](/assets/images/help/organizations/team-page-discussions-tab.png) + +### 嵌套团队 + +您可以在 {% data variables.product.product_name %} 组织中通过多级嵌套团队反映您的组或公司的层级。 一个父团队可有多个子团队，而每个子团队只能有一个父团队。 您无法嵌套机密团队。 + +子团队继承父团队的访问权限，简化大组的权限管理。 当父团队被 @提及时，子团队的成员也会收到通知，因此简化与多组人员的沟通。 + +例如，如果您的团队结构是“员工 > 工程 > 应用工程 > 身份”，则向“工程”授予对仓库的写入权限意味着“应用工程”和“身份”也会获得该访问权限。 如果您 @提及“身份”团队或组织层次结构底部的任何团队，则它们是唯一会收到通知的团队。 + +![包含父团队和子团队的团队页面](/assets/images/help/teams/nested-teams-eng-example.png) + +要轻松了解谁共享父团队的权限和提及，可以在父团队页面的 Members（成员）选项卡上查看其子团队的所有成员。 子团队的成员不是父团队的直接成员。 + +![包含子团队所有成员的父团队页面](/assets/images/help/teams/team-and-subteam-members.png) + +在创建团队时您可以选择父团队，或者以后在组织的层次结构中移动团队。 更多信息请参阅“[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)”。 + +{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} + +### 准备在组织中嵌套团队 + +如果您的组织已经有团队，则在其上面或下面嵌套团队之前，应审计每个团队的仓库访问权限。 也应考虑要为组织实施的新结构。 + +在团队层次结构的顶部，应向父团队授予对父团队及其子团队每个成员都安全的仓库访问权限。 随着在向层次结构底部的移动，可以更细致地向子团队成员授予访问敏感仓库的其他权限。 + +1. 从现有团队删除所有成员 +2. 审计并调整每个团队的仓库访问权限，并为每个团队指定一个父团队 +3. 创建需要的任何新团队，为每个新团队选择一个父团队，并向他们授予仓库访问权限 +4. 直接向团队添加人员 + +### 延伸阅读 + +- "[创建团队](/articles/creating-a-team)" +- "[向团队添加组织成员](/articles/adding-organization-members-to-a-team)" diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md new file mode 100644 index 0000000000..ce6386ee43 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md @@ -0,0 +1,32 @@ +--- +title: 添加组织成员到团队 +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 + - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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. 在团队成员列表上方，单击 **Add a member（添加成员）**。 ![添加成员按钮](/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 %} + +### 延伸阅读 + +- "[关于团队](/articles/about-teams)" +- "[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/changing-team-visibility.md new file mode 100644 index 0000000000..47b5bd4032 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/changing-team-visibility.md @@ -0,0 +1,29 @@ +--- +title: 更改团队可见性 +intro: 团队维护员和组织所有者可决定将团队设为*可见*或*机密*。 +redirect_from: + - /articles/changing-team-visibility + - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.organizations.types-of-team-visibility %} + +{% tip %} + +**提示：**如果团队有[子或父团队](/articles/about-teams)，则无法将其设为机密团队。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +3. 选择要更改其可见性的一个或多个团队。 ![选择了两个团队的团队列表](/assets/images/help/teams/list-of-teams-selected.png) +4. 在团队列表的上方，使用下拉菜单并单击 **Change visibility（更改可见性）**。 ![包含更改团队可见性选项的下拉菜单](/assets/images/help/teams/team-bulk-management-options.png) +5. 选择要将一个或多个团队设为可见还是机密，然后单击 **Change visibility（更改可见性）**。 ![将团队设为可见或机密的单选按钮以及更改可见性按钮](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md new file mode 100644 index 0000000000..593e0e67b2 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -0,0 +1,38 @@ +--- +title: 创建团队 +intro: 您可以创建独立或嵌套团队来管理仓库权限和提及人群。 +redirect_from: + - /articles/creating-a-team-early-access-program/ + - /articles/creating-a-team + - /github/setting-up-and-managing-organizations-and-teams/creating-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +只有父团队的组织所有者和维护员才能在父团队下创建新的子团队。 所有者还可以限制组织中所有团队的创建权限。 更多信息请参阅“[设置组织中的团队创建权限](/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. （可选）如果您的组织或企业帐户使用团队同步，要将身份提供程序组连接到您的团队，请使用“Identity Provider Groups（身份提供程序组）”下拉菜单，并选择最多 5 个身份提供程序组。 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 ![用于选择身份提供程序组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png) +{% endif %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} +9. （可选）[授予团队访问组织仓库的权限](/articles/managing-team-access-to-an-organization-repository)。 + +### 延伸阅读 + +- "[关于团队](/articles/about-teams)" +- “[更改团队可见性](/articles/changing-team-visibility)” +- “[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)” diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/deleting-a-team.md new file mode 100644 index 0000000000..879803eecf --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/deleting-a-team.md @@ -0,0 +1,27 @@ +--- +title: 删除团队 +intro: 组织所有者可随时从团队设置页面删除团队。 +redirect_from: + - /articles/deleting-a-team + - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% tip %} + +**提示：**仅组织所有者可删除父团队。 更多信息请参阅“[关于团队](/articles/about-teams)”。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. 选择要删除的团队。 ![选择了两个团队的团队列表](/assets/images/help/teams/list-of-teams-selected.png) +5. 在团队列表上方，使用下拉菜单并单击 **Delete（删除）**。 ![包含更改团队可见性选项的下拉菜单](/assets/images/help/teams/team-bulk-management-options.png) +6. 审查要删除的团队，然后单击 **I understand, delete teams（我理解，删除团队）**。 ![将删除团队的哦列表和删除团队按钮](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md new file mode 100644 index 0000000000..c21461b49d --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md @@ -0,0 +1,23 @@ +--- +title: 禁用组织的团队讨论 +intro: 组织所有者可选择禁用或启用组织内的团队讨论。 +redirect_from: + - /articles/disabling-team-discussions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.organizations.team-discussions-default %} 有关团队讨论的更多信息，请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.teams_sidebar %} +5. 在“Team discussions”（团队讨论）下，取消选择 **Enable team discussions for this organization（启用本组织的团队讨论）**。 ![用于启用或禁用组织的团队讨论的复选框](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) +6. 单击 **Save（保存）**。 diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/index.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/index.md new file mode 100644 index 0000000000..2e38056e49 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/index.md @@ -0,0 +1,38 @@ +--- +title: 将成员组织为团队 +intro: 您可以将组织成员组成团队，通过级联访问权限和提及来反映公司或群组结构。 +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 + - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md new file mode 100644 index 0000000000..eea8c98f4b --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -0,0 +1,51 @@ +--- +title: 管理团队的代码审查分配 +intro: 代码审查分配明确指出哪些团队成员应为拉取请求提交审查。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team +product: '{% data reusables.gated-features.code-review-assignment %}' +versions: + free-pro-team: '*' + enterprise-server: '>=2.20' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +团队维护员和组织所有者可以配置代码审查分配。 + +### 关于代码审查分配 + +通过使用代码审查分配，每当请求您的团队审查拉取请求时，团队将作为审查者被删除，并将一部分指定的团队成员分配到团队的位置。 代码审查分配允许您决定在请求团队审查时是通知整个团队，还是只通知一部分团队成员。 + +当自动请求代码所有者进行审查时，团队也会被删除，并替换为个人。 单个审批不符合受保护分支中代码所有者审批的要求。 更多信息请参阅“[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)”。 + +### 路由算法 + +代码审查分配根据两种可能的算法之一自动选择和分配审查者。 + +循环算法根据最近收到最少审查请求的人员选择审查者，侧重于在团队所有成员之间的轮替，而不管他们目前拥有多少未完成的审查。 + +负载平衡算法根据每个成员最近的审查请求总数选择审查者，并考虑每个成员未完成的审查数。 负载平衡算法努力确保每个团队成员在任意 30 天内审查相同数量的拉取请求。 + +### 配置代码审查分配 +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. 在左侧边栏中，单击 **Code review assignment（代码审查分配）**。 ![代码审查分配按钮](/assets/images/help/teams/review-assignment-button.png) +6. 选择 **Enable auto assignment（启用自动分配）**。 ![代码审查分配按钮](/assets/images/help/teams/review-assignment-enable.png) +7. 在“How many team members should be assigned to review?（应分配多少团队成员进行审查？）”下，使用下拉菜单选择多个要分配给每个拉取请求的审查者。 ![审查者人数下拉列表](/assets/images/help/teams/review-assignment-number.png) +8. 在“Routing algorithm（路由算法）”下，使用下拉菜单选择要使用的算法。 更多信息请参阅“[路由算法](#routing-algorithms)”。 ![路由算法下拉列表](/assets/images/help/teams/review-assignment-algorithm.png) +9. （可选）要始终跳过某些团队成员，请选择 **Never assign certain team members（永不分配某些团队成员）**。 然后，选择要始终跳过的一个或多个团队成员。 ![永不分配某些团队成员复选框和下拉列表](/assets/images/help/teams/review-assignment-skip-members.png) +10. （可选）要对每个拉取请求审查只通知代码审查分配所选择的团队成员，在“Notifications（通知）”下选择 **If assigning team members, don't notify the entire team（如果分配团队成员，请不要通知整个团队）**。 ![代码审查分配通知](/assets/images/help/teams/review-assignment-notifications.png) +11. 单击 **Save changes（保存更改）**。 + +### 禁用代码审查分配 +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. 选择 **Enable auto assignment（启用自动分配）**以删除复选标记。 ![代码审查分配按钮](/assets/images/help/teams/review-assignment-enable.png) +6. 单击 **Save changes（保存更改）**。 diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md new file mode 100644 index 0000000000..16ad20a497 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -0,0 +1,69 @@ +--- +title: 管理团队的预定提醒 +intro: 当您的团队有等待审查的拉取请求时，您可以在 Slack 中收到提醒。 +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +### 关于团队的预定提醒 + +{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} + +团队维护员和组织所有者可为团队已请求审查的任何拉取请求设置预定提醒。 组织所有者必须先授权您的 Slack 工作区，然后您才可为团队创建预定提醒。 更多信息请参阅“[管理组织的预定提醒](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)”。 + +{% data reusables.reminders.scheduled-reminders-limitations %} + +### 为团队创建预定提醒 +{% 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 %} +![预定提醒按钮](/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 %} + +### 管理团队的预定提醒 +{% 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 %} +![预定提醒按钮](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.edit-existing %} +{% data reusables.reminders.edit-page %} +{% data reusables.reminders.update-buttons %} + +### Deleting a scheduled reminder for a team +{% 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 %} +![预定提醒按钮](/assets/images/help/teams/scheduled-reminders-teams.png) +{% data reusables.reminders.delete %} + +### 延伸阅读 + +- “[管理组织的预定提醒](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)” +- “[管理您的预定提醒](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)” diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md new file mode 100644 index 0000000000..80ea38dc1d --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md @@ -0,0 +1,42 @@ +--- +title: 在组织的层次结构中移动团队 +intro: '团队维护员和组织所有者可以在父团队下嵌套团队，或者更改或删除已嵌套团队的父团队。' +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 + - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +组织所有者可以更改任何团队的父团队。 团队维护员如果同时是子团队和父团队的维护员，则可更改团队的父团队。 没有子团队维护员权限的团队维护员可以申请添加父团队或子团队。 更多信息请参阅“[申请添加或更改父团队](/articles/requesting-to-add-or-change-a-parent-team)”和“[申请添加子团队](/articles/requesting-to-add-a-child-team)”。 + +{% data reusables.organizations.child-team-inherits-permissions %} + +{% tip %} + +**提示：** +- 不能将团队的父团队更改为机密团队。 更多信息请参阅“[关于团队](/articles/about-teams)”。 +- 不能将父团队嵌套在其子团队下面。 + +{% endtip %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.teams %} +4. 在团队列表中，单击您要更改其父团队的团队名称。 ![组织的团队列表](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. 使用下拉菜单选择父团队，要删除现有团队，则选择 **Clear selected value（清除所选值）**。 ![列出组织团队的下拉菜单](/assets/images/help/teams/choose-parent-team.png) +7. 单击 **Update（更新）**。 +{% data reusables.repositories.changed-repository-access-permissions %} +9. 单击 **Confirm new parent team（确认新的父团队）**。 ![包含仓库访问权限更改相关信息的模态框](/assets/images/help/teams/confirm-new-parent-team.png) + +### 延伸阅读 + +- "[关于团队](/articles/about-teams)" diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md new file mode 100644 index 0000000000..836bbbd729 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md @@ -0,0 +1,23 @@ +--- +title: 从团队中删除组织成员 +intro: '具有*所有者*或*团队维护员*权限的人员可以从团队中删除团队成员。 如果人员不再需要团队授予的仓库访问权限，或者人员不再关注团队的项目，则可能有必要这样做。' +redirect_from: + - /articles/removing-organization-members-from-a-team-early-access-program/ + - /articles/removing-organization-members-from-a-team + - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% 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. 选择您想要删除的一个或多个人员。 ![组织成员旁的复选框](/assets/images/help/teams/team-member-check-box.png) +5. 在团队成员列表上方，使用下拉菜单，然后单击 **Remove from team（从团队中删除）**。 ![包含更改角色选项的下拉菜单](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/renaming-a-team.md new file mode 100644 index 0000000000..fd21035e3e --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/renaming-a-team.md @@ -0,0 +1,21 @@ +--- +title: 重命名团队 +intro: 团队维护员和组织所有者可以编辑团队的名称和说明。 +redirect_from: + - /articles/renaming-a-team + - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. 输入团队的新名称或说明。 ![团队名称和说明的字段](/assets/images/help/teams/team-name-description.png) +6. 单击 **Update（更新）**。 diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md new file mode 100644 index 0000000000..ee7c124424 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md @@ -0,0 +1,36 @@ +--- +title: 申请添加子团队 +intro: '如果您在团队中具有维护员权限，可以申请在组织的层次结构中将现有团队嵌套在您的团队下面。' +redirect_from: + - /articles/requesting-to-add-a-child-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +申请将某个团队添加为子团队时，申请会发送到子团队的维护员。 在子团队的维护员批准申请后，该子团队将嵌套在组织的层次结构中的父团队下面。 + +如果您是组织所有者或者在子团队及父团队中具有团队维护员权限，无需申请批准便可添加子团队，或者从子团队的设置页面更改其父团队。 更多信息请参阅“[在组织的层次结构中移动团队](/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. 在团队列表中，单击您要在其中添加子团队的父团队名称。 ![组织的团队列表](/assets/images/help/teams/click-team-name.png) +5. 在团队页面顶部，单击 {% octicon "people" aria-label="The people icon" %} **Teams（团队）**。 ![团队页面上的团队选项卡](/assets/images/help/teams/team-teams-tab.png) +6. 单击 **Add a team（添加团队）**。 ![团队页面上的添加团队按钮](/assets/images/help/teams/add-a-team.png) +7. 键入要添加为子团队的团队名称，然后从下拉列表中选择它。 ![用于键入子团队名称的文本框和用于选择的下拉菜单](/assets/images/help/teams/type-child-team-name.png) +{% data reusables.repositories.changed-repository-access-permissions %} +9. 单击 **Confirm changes（确认更改）**以发送添加子团队的申请。 ![包含仓库访问权限更改相关信息的模态框](/assets/images/help/teams/confirm-new-parent-team.png) + +### 延伸阅读 + +- "[关于团队](/articles/about-teams)" +- “[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)” +- "[申请添加或更改父团队](/articles/requesting-to-add-or-change-a-parent-team)" diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md new file mode 100644 index 0000000000..740196468a --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md @@ -0,0 +1,36 @@ +--- +title: 申请添加或更改父团队 +intro: '如果您在团队中具有维护员权限，可以申请在组织的层次结构中将团队嵌套在父团队下面。' +redirect_from: + - /articles/requesting-to-add-or-change-a-parent-team + - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +申请添加或更改团队的父团队时，申请会发送给父团队的维护员。 新父团队的维护员批准申请后，您的团队将作为子团队嵌套在组织的层次结构中该父团队下。 + +如果您是组织所有者或者在子团队及父团队中具有团队维护员权限，无需申请批准便可添加父团队，或者从您团队的设置页面更改其父团队。 更多信息请参阅“[在组织的层次结构中移动团队](/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. 在团队列表中，单击您要在父团队下嵌套的团队的名称。 ![组织的团队列表](/assets/images/help/teams/click-team-name.png) +{% data reusables.organizations.team_settings %} +6. 在“Parent team（父团队）”下，使用“Select parent team（选择父团队）”下拉菜单，然后单击新父团队的名称。 ![列出组织团队的下拉菜单](/assets/images/help/teams/choose-parent-team.png) +7. 单击 **Save changes（保存更改）**。 +{% data reusables.repositories.changed-repository-access-permissions %} +9. 单击 **Confirm changes（确认更改）**以发送添加或更改父团队的申请。 ![包含仓库访问权限更改相关信息的模态框](/assets/images/help/teams/confirm-new-parent-team.png) + +### 延伸阅读 + +- "[关于团队](/articles/about-teams)" +- “[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)” +- “[申请添加子团队](/articles/requesting-to-add-a-child-team)” diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md new file mode 100644 index 0000000000..77932c2377 --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md @@ -0,0 +1,24 @@ +--- +title: 设置团队的头像 +intro: '团队维护员和组织所有者可以设置团队的头像，这将在团队的页面中显示。' +redirect_from: + - /articles/setting-your-team-s-profile-picture + - /articles/setting-your-teams-profile-picture + - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +除非您设置团队的头像，否则团队头像将与组织的头像一致。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +5. 单击 **Upload new picture（上传新图片）**并选择所需的头像。 ![上传新图片](/assets/images/help/teams/org-team-profile-picture-upload.png) +6. 单击并拖动以根据需要裁剪图像，然后单击 **Set new team avatar（设置新的团队头像）**。 ![设置新的团队头像](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md new file mode 100644 index 0000000000..f101f1150a --- /dev/null +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -0,0 +1,99 @@ +--- +title: 将团队与身份提供程序组同步 +intro: '您可以将 {% data variables.product.product_name %} 团队与身份提供程序 (IdP) 组同步，以自动添加和删除团队成员。' +redirect_from: + - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group +product: '{% data reusables.gated-features.team-synchronization %}' +permissions: '组织所有者和团队维护员可将 {% data variables.product.prodname_dotcom %} 团队与 IdP 组同步。' +versions: + free-pro-team: '*' + github-ae: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.gated-features.okta-team-sync %} + +### 关于团队同步 + +{% data reusables.identity-and-permissions.about-team-sync %} + +{% if currentversion == "free proteam@latest" %}您可以将最多 5 个 IdP 组连接到 {% data variables.product.product_name %} 团队。{% elsif currentVersion == "github-ae@latest" %}您可以将 {% data variables.product.product_name %} 上的团队连接到一个 IdP 组。 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。 + +{% if currentversion == "free-proteam@latest" %}团队同步不支持超过 5000 个成员的 IdP 组。{% endif %} + +{% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 您不能在 {% data variables.product.product_name %} 上{% if currentVersion == "free-pro-team@latest" %}或使用 API{% endif %} 管理团队成员资格。 + +{% if currentVersion == "free-pro-team@latest" %} +通过 IdP 进行的所有团队成员资格更改都将在 {% data variables.product.product_name %} 审核日志中显示为团队同步自动程序所进行的更改。 您的 IdP 会将团队成员数据发送至 {% data variables.product.prodname_dotcom %}，每小时一次。 将团队连接到 IdP 组可能会删除一些团队成员。 更多信息请参阅“[已同步团队成员的要求](#requirements-for-members-of-synchronized-teams)”。 +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. 更改 {% data variables.product.prodname_dotcom %} 团队或组织成员资格的任何请求都将在审核日志中注册为用于配置用户预配的帐户所做的更改。 有关此帐户的更多信息，请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 有关 SCIM 请求计划的更多信息，请参阅 Microsoft 文档中的“[检查用户预配状态](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)”。 +{% endif %} + +父团队无法与 IdP 组同步。 如果要连接到 IdP 组的团队是父团队，我们建议您创建一个新团队或删除使团队成为父团队的嵌套关系。 更多信息请参阅“[关于团队](/articles/about-teams#nested-teams)”、“[创建团队](/organizations/organizing-members-into-teams/creating-a-team)”和“[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organizations-hierarchy)”。 + +要管理 {% data variables.product.prodname_dotcom %} 团队（包括连接到 IdP 组的团队）的仓库访问权限，您必须使用 {% data variables.product.product_name %} 进行更改。 更多信息请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)”。 + +{% if currentversion == "free proteam@latest" %}您也可以使用 API 管理团队同步。 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +### 已同步团队成员的要求 + +将团队连接到 IdP 组后，团队同步将 IdP 组的每个成员添加到 {% data variables.product.product_name %} 上的相应团队，但需满足以下条件： +- 此人是 {% data variables.product.product_name %} 上的组织的成员。 +- 此人已使用 {% data variables.product.product_name %} 上的用户帐户登录，并且至少一次通过 SAML 单点登录向组织或企业帐户验证。 +- 此人的 SSO 身份是 IdP 组的成员。 + +不符合这些条件的现有团队或组成员将被从 {% data variables.product.product_name %} 团队中自动删除，并失去对仓库的访问权限。 撤销用户关联的身份也会将用户从映射到 IdP 组的任何团队中删除。 For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/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)." + +删除后的团队成员在使用 SSO 向组织或企业帐户进行身份验证后可以自动添加回团队，并移动到已连接的 IdP 组。 + +为避免无意中删除团队成员，建议在组织或企业帐户中强制实施 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/managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 + +{% endif %} + +### 基本要求 + +{% if currentVersion == "free-pro-team@latest" %} +Before you can connect a {% data variables.product.product_name %} 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](/organizations/managing-saml-single-sign-on-for-your-organization/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)." + +为避免无意中删除团队成员，请访问 IdP 的管理门户，并确认每个当前团队成员也位于要连接到此团队的 IdP 组中。 如果您没有身份提供程序的这一访问权限，在可以联系 IdP 管理员。 + +您必须使用 SAML SSO 进行身份验证。 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。 + +{% elsif currentVersion == "github-ae@latest" %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.product.product_location %} using a supported System for Cross-domain Identity Management (SCIM). 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 + +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. 更多信息请参阅 Microsoft 文档中的[配置 GitHub AE 的自动用户预配](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae)。 +{% endif %} + +### 将 IdP 组连接到团队 + +将 IdP 组连接到 {% data variables.product.product_name %} 团队时，组中的所有用户都会自动添加到团队中。 {% if currentversion == "github-ae@latest" %}任何尚未成为父组织成员的用户也会添加到组织。{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. 在“Identity Provider Groups（身份提供程序组）”下，使用下拉菜单，选择最多 5 个身份提供程序组。 ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. 在“Identity Provider Groups（身份提供程序组）”下，使用下拉菜单从列表中选择身份提供程序组。 ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. 单击 **Save changes（保存更改）**。 + +### 断开 IdP 组与团队的连接 + +如果您断开 IdP 组与 {% data variables.product.prodname_dotcom %} 团队的连接，则通过 IdP 组分配给 {% data variables.product.prodname_dotcom %} 团队的团队成员将从团队中删除。 {% if currentversion == "github-ae@latest" %} 任何只是因为团队连接而成为父组织成员的用户也会从组织中删除。{% endif %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% if currentVersion == "free-pro-team@latest" %} +6. 在“Identity Provider Groups（身份提供程序组）”下，单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif currentVersion == "github-ae@latest" %} +6. 在“Identity Provider Group（身份提供程序组）”下，单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. 单击 **Save changes（保存更改）**。 diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md new file mode 100644 index 0000000000..94e157e896 --- /dev/null +++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -0,0 +1,60 @@ +--- +title: 关于 OAuth App 访问限制 +intro: '组织可通过启用 {% data variables.product.prodname_oauth_app %} 访问限制，选择哪些 {% data variables.product.prodname_oauth_app %} 可以访问其仓库及其他资源。' +redirect_from: + - /articles/about-third-party-application-restrictions/ + - /articles/about-oauth-app-access-restrictions + - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +当 {% data variables.product.prodname_oauth_app %} 访问限制启用后，组织成员无法授权 {% data variables.product.prodname_oauth_app %} 访问组织资源。 组织成员可以申请所有者批准他们想使用的 {% data variables.product.prodname_oauth_app %}，并且组织所有者会收到待处理申请的通知。 + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% tip %} + +**提示**：当组织尚未设置 {% data variables.product.prodname_oauth_app %} 访问限制时，组织成员授权的任何 {% data variables.product.prodname_oauth_app %} 也可访问组织的私有资源。 + +{% endtip %} + +### 设置 {% data variables.product.prodname_oauth_app %} 访问限制 + +当组织所有者第一次设置 {% data variables.product.prodname_oauth_app %} 访问限制时： + +- **组织拥有的应用程序**会自动获得对组织资源的访问权限。 +- **{% data variables.product.prodname_oauth_app %}** 会立即失去对组织资源的访问权限。 +- **2014 年 2 月之前创建的 SSH 密钥**会立即失去对组织资源（包括用户和部署密钥）的访问权限。 +- **{% data variables.product.prodname_oauth_app %} 在 2017 年 2 月期间或以后创建的 SSH 密钥**会立即失去对组织资源的访问权限。 +- **来自私有组织仓库的挂钩**不再发送到未批准的 {% data variables.product.prodname_oauth_app %}。 +- 对私有组织资源的 **API 访问**不适用于未批准的 {% data variables.product.prodname_oauth_app %}。 此外，也没有在公共资源资源上执行创建、更新或删除操作的权限。 +- **用户创建的挂钩和 2014 年 5 月之前创建的挂钩**不受影响。 +- **组织拥有的仓库的私有复刻**需遵守组织的访问限制。 + +### 解决 SSH 访问失败 + +当 2014 年 2 月之前创建的 SSH 密钥因 {% data variables.product.prodname_oauth_app %} 访问限制启用而失去对组织的访问权限时，后续 SSH 访问尝试就会失败。 用户将会收到错误消息，将他们导向至可以批准密钥或在其位置上传可信密钥的 URL。 + +### Web 挂钩 + +当 {% data variables.product.prodname_oauth_app %} 在限制启用后被授予对组织的访问权限时，该 {% data variables.product.prodname_oauth_app %} 创建的任何原有 web 挂钩会继续分发。 + +当组织从之前批准的 {% data variables.product.prodname_oauth_app %} 删除访问权限时，该应用程序创建的任何原有 web 挂钩不再分发（这些挂钩将被禁用，但不会删除）。 + +### 重新启用访问限制 + +如果组织禁用 {% data variables.product.prodname_oauth_app %} 访问应用程序限制，后来又重新启用它们，则之前批准的 {% data variables.product.prodname_oauth_app %} 会被自动授予访问组织资源的权限。 + +### 延伸阅读 + +- "[为组织启用 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" +- "[为组织审批 {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization)" +- "[审查组织安装的集成](/articles/reviewing-your-organization-s-installed-integrations)" +- "[拒绝访问以前为组织批准的 {% data variables.product.prodname_oauth_app %}](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" +- "[为组织禁用 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" +- "[请求组织对 {% data variables.product.prodname_oauth_app %} 的审批](/articles/requesting-organization-approval-for-oauth-apps)" +- "[授权 {% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps)" diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md new file mode 100644 index 0000000000..426468381e --- /dev/null +++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: 批准组织的 OAuth Apps +intro: '当组织成员申请 {% data variables.product.prodname_oauth_app %} 访问组织资源时，组织所有者可以批准或拒绝该申请。' +redirect_from: + - /articles/approving-third-party-applications-for-your-organization/ + - /articles/approving-oauth-apps-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +当 {% data variables.product.prodname_oauth_app %} 访问限制启用后，组织成员必须向组织所有者[申请批准](/articles/requesting-organization-approval-for-oauth-apps)，然后才可授权对组织资源具有访问权限的 {% data variables.product.prodname_oauth_app %}。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. 在要批准的应用程序的旁边，单击 **Review（审查）**。 ![审查申请链接](/assets/images/help/settings/settings-third-party-approve-review.png) +6. 在审查申请的应用程序相关信息后，单击 **Grant access（授予访问）**。 ![授予访问按钮](/assets/images/help/settings/settings-third-party-approve-grant.png) + +### 延伸阅读 + +- "[关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md new file mode 100644 index 0000000000..87d3cc9deb --- /dev/null +++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md @@ -0,0 +1,20 @@ +--- +title: 拒绝此前批准的 OAuth 应用程序对组织的访问权限 +intro: '如果组织不再需要之前授权的 {% data variables.product.prodname_oauth_app %}，所有者可删除此应用程序对组织资源的访问权限。' +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 + - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.oauth_app_access %} +5. 在要禁用的应用程序旁边，单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑图标](/assets/images/help/settings/settings-third-party-deny-edit.png) +6. 单击 **Deny access（拒绝访问）**。 ![拒绝确认按钮](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..813e637e1c --- /dev/null +++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,26 @@ +--- +title: 禁用 OAuth 应用程序对您的组织的访问权限限制 +intro: '组织所有者可禁用对拥有组织资源访问权限的 {% data variables.product.prodname_oauth_app %} 的限制。' +redirect_from: + - /articles/disabling-third-party-application-restrictions-for-your-organization/ + - /articles/disabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% danger %} + +**警告**：禁用 {% data variables.product.prodname_oauth_app %} 对组织的访问权限限制后，任何组织成员批准某一应用程序使用其私有帐户设置时，将自动授予 {% data variables.product.prodname_oauth_app %} 对组织私有资源的访问权限。 + +{% enddanger %} + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% 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（是，删除应用程序限制）**。 ![删除确认按钮](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md new file mode 100644 index 0000000000..d1f5c2760a --- /dev/null +++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -0,0 +1,31 @@ +--- +title: 对组织启用 OAuth App 访问限制 +intro: '组织所有者可启用 {% data variables.product.prodname_oauth_app %} 访问限制，以便在组织成员在其个人账户上使用允许 {% data variables.product.prodname_oauth_app %} 的同时，防止不受信任的应用程序访问组织的资源。' +redirect_from: + - /articles/enabling-third-party-application-restrictions-for-your-organization/ + - /articles/enabling-oauth-app-access-restrictions-for-your-organization + - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% data reusables.organizations.oauth_app_restrictions_default %} + +{% warning %} + +**警告**： +- 启用 {% data variables.product.prodname_oauth_app %} 访问限制将撤销对所有之前已授权 {% data variables.product.prodname_oauth_app %} 和 SSH 密钥的组织访问权限。 更多信息请参阅“[关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)”。 +- 在设置 {% data variables.product.prodname_oauth_app %} 访问限制后，确保重新授权任何需要持续访问组织私有数据的 {% data variables.product.prodname_oauth_app %}。 所有组织成员将需要创建新的 SSH 密钥，并且组织将需要根据需要创建新的部署密钥。 +- 启用 {% data variables.product.prodname_oauth_app %} 访问限制后，应用程序可以使用 OAuth 令牌访问有关 {% 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. 在“Third-party application access policy”（第三方应用程序访问策略）下，单击 **Setup application access restrictions（设置应用程序访问限制）**。 ![设置限制按钮](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) +6. 审查有关第三方访问限制的信息后，单击 **Restrict third-party application access（限制第三方应用程序访问）**。 ![限制确认按钮](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md new file mode 100644 index 0000000000..c081e47f9f --- /dev/null +++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -0,0 +1,19 @@ +--- +title: 限制对组织数据的访问 +intro: '{% data variables.product.prodname_oauth_app %} 访问限制允许组织所有者限制不受信任的应用程序访问组织的数据。 然后，组织成员可对其个人用户帐户使用 {% data variables.product.prodname_oauth_app %}，同时保证组织数据安全。' +redirect_from: + - /articles/restricting-access-to-your-organization-s-data + - /articles/restricting-access-to-your-organizations-data + - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data +versions: + free-pro-team: '*' +topics: + - 组织 + - 团队 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md index 98ab1d6cb9..920bf908ce 100644 --- a/translations/zh-CN/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md +++ b/translations/zh-CN/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -1,6 +1,6 @@ --- -title: Configuring RubyGems for use with GitHub Packages -intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.' +title: 配置 RubyGems 用于 GitHub 包 +intro: '您可以配置 RubyGems 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作带 Bundler 的 Ruby 项目中的依赖项。' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-rubygems-for-use-with-github-package-registry @@ -10,59 +10,62 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.package_registry.admins-can-configure-package-types %} +**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。 -### Prerequisites +### 基本要求 -- You must have rubygems 2.4.1 or higher. To find your rubygems version: +- 必须拥有 rubygems 2.4.1 或更高版本. 要查找您的 rubygems 版本： ```shell $ gem --version ``` - - - You must have bundler 1.6.4 or higher. To find your Bundler version: + + - 必须拥有 bundler 1.6.4 或更高版本. 要查找您的 Bundler 版本： ```shell $ bundle --version Bundler version 1.13.7 ``` - - - Install keycutter to manage multiple credentials. To install keycutter: + + - 安装 keycutter 以管理多个凭据. 要安装 keycutter： ```shell $ gem install keycutter ``` - -### Authenticating to {% data variables.product.prodname_registry %} - + +### 向 {% data variables.product.prodname_registry %} 验证 + {% data reusables.package_registry.authenticate-packages %} - -#### Authenticating with a personal access token - + +#### 使用个人访问令牌进行身份验证 + {% data reusables.package_registry.required-scopes %} - -You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems. - -To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your personal access token. Create a new *~/.gem/credentials* file if this file doesn't exist. - -For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your personal access token. - + +通过编辑用于发布 gem 的 *~/.gem/credentials* 文件、编辑用于安装单个 gem 的 *~/.gemrc* 文件或使用用于跟踪和安装一个或多个 gem 的 Bundler，使用 RubyGems 向 {% data variables.product.prodname_registry %} 验证。 + +要发布新的 gem，您需要通过编辑 *~/.gem/credentials* 文件以包含您的个人访问令牌，使用 RubyGems 向 {% data variables.product.prodname_registry %} 验证。 如果 *~/.gem/credentials* 文件不存在，请新建该文件。 + +例如，您要创建或编辑 *~/.gem/credentials* 以包含以下内容，将 *TOKEN* 替换为您的个人访问令牌。 + ```shell ---- -:github: Bearer TOKEN +gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" } ``` - -To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace: - - `USERNAME` with your {% data variables.product.prodname_dotcom %} username. - - `TOKEN` with your personal access token. - - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} - - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance. -{% endif %} - -If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example. - + +要安装 gem，您需要通过编辑项目的 *~/.gemrc* 文件以包含 `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`，向 {% data variables.product.prodname_registry %} 验证。 必须： + - 将 `USERNAME` 替换为您的 {% data variables.product.prodname_dotcom %} 用户名。 + - 将 `TOKEN` 替换为您的个人访问令牌。 + - 将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称。{% if enterpriseServerVersions contains currentVersion %} + - `REGISTRY-URL` 替换为您实例的 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，都将 *HOSTNAME* 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。 +{% elsif currentVersion == "github-ae@latest" %} + - `REGISTRY-URL` 替换为您实例的 Rubygems 注册表的 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。 +{% endif %} + +如果您没有 *~/.gemrc* 文件，请使用此示例创建新的 *~/.gemrc* 文件。 + ```shell --- :backtrace: false @@ -74,29 +77,29 @@ If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this exa :verbose: true ``` - -To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - + +要使用 Bundler 进行身份验证，请配置 Bundler 使用您的个人访问令牌，将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *OWNER* 替换为拥有项目所在仓库的用户或组织帐户的名称。{% if enterpriseServerVersions contains currentVersion %}将 `REGISTRY-URL` 替换为实例 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，将 *HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif currentVersion == "github-ae@latest" %}将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} + ```shell $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN ``` - -#### Authenticating with the `GITHUB_TOKEN` - -{% data reusables.package_registry.package-registry-with-github-tokens %} - -### Publishing a package -{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation. - +#### 使用 `GITHUB_TOKEN` 进行身份验证 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### 发布包 + +{% data reusables.package_registry.default-name %} 例如，您将 `octo-gem` 发布到 `octo-org` 组织时，{% data variables.product.prodname_registry %} 将 gem 发布到 `octo-org/octo-gem` 仓库。 有关创建 gem 的更多信息，请参阅 RubyGems 文档中的“[创建自己的 gem](http://guides.rubygems.org/make-your-own-gem/)”。 + {% data reusables.package_registry.viewing-packages %} - + {% data reusables.package_registry.authenticate-step %} -2. Build the package from the *gemspec* to create the *.gem* package. +2. 从 *gemspec* 构建包以创建 *.gem* 包。 ```shell gem build OCTO-GEM.gemspec ``` -3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} +3. 将包发布到 {% data variables.product.prodname_registry %}，将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称，将 `OCTO-GEM` 替换为 gem 包的名称。{% if enterpriseServerVersions contains currentVersion %}将 `REGISTRY-URL` 替换为实例 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，将 *HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif currentVersion == "github-ae@latest" %}将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} ```shell $ gem push --key github \ @@ -104,22 +107,22 @@ $ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygem OCTO-GEM-0.0.1.gem ``` -### Publishing multiple packages to the same repository +### 将多个包发布到同一个仓库 -To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% if enterpriseServerVersions contains currentVersion %} Replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} +要将多个 gem 发布到同一个仓库，您可以在 `gem.metadata` 的 `github_repo` 字段中包含 {% data variables.product.prodname_dotcom %} 仓库的 URL。 如果您包含此字段，则 {% data variables.product.prodname_dotcom %} 根据此值匹配仓库，而不使用 gem 名称。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名称。{% endif %} -``` +```ruby gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` -### Installing a package +### 安装包 -You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing you *Gemfile*. +您可以使用来自 {% data variables.product.prodname_registry %} 的 gem，就像使用来自 *rubygems.org* 的 gem 一样。 您需要通过将您的 {% data variables.product.prodname_dotcom %} 用户或组织添加为 *~/.gemrc* 文件中的源，或者使用 Bundler 并编辑 *Gemfile*，向 {% data variables.product.prodname_registry %} 验证。 {% data reusables.package_registry.authenticate-step %} -2. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if enterpriseServerVersions contains currentVersion %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} +1. 对于 Bundler，请将您的 {% data variables.product.prodname_dotcom %} 用户或组织添加为 *Gemfile* 中的源，以便从这个新源获取 gem。 例如，您可以将新的 `source` 块添加到仅对您指定的包使用 {% data variables.product.prodname_registry %} 的 *Gemfile*，将 *GEM NAME* 替换为要从 {% data variables.product.prodname_registry %} 安装的包，将 *OWNER* 替换为拥有要安装的 gem 所在仓库的用户或组织。{% if enterpriseServerVersions contains currentVersion %}将 `REGISTRY-URL` 替换为实例 Rubygems 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `rubygems.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下，将 *HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif currentVersion == "github-ae@latest" %}将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 URL `rubygems.HOSTNAME`。 将 *HOSTNAME* 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} - ``` + ```ruby source "https://rubygems.org" gem "rails" @@ -129,9 +132,9 @@ You can use gems from {% data variables.product.prodname_registry %} much like y end ``` -3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html). +3. 对于 1.7.0 之前的 Bundler 版本，您需要增加新的全局 `source`。 有关使用 Bundler 的更多信息，请参阅 [bundler.io 文档](http://bundler.io/v1.5/gemfile.html)。 - ``` + ```ruby source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" source "https://rubygems.org" @@ -139,11 +142,11 @@ You can use gems from {% data variables.product.prodname_registry %} much like y gem "GEM NAME" ``` -4. Install the package: +4. 安装包： ```shell $ gem install octo-gem --version "0.1.1" ``` -### Further reading +### 延伸阅读 -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" +- "{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}" 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 8f9a3f5c6d..a8dc5b4925 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 @@ -1,6 +1,6 @@ --- -title: Using GitHub Packages with GitHub Actions -intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.' +title: 将 GitHub 包用于 GitHub Actions +intro: '您可以配置 {% data variables.product.prodname_actions %} 中的工作流程以自动发布或安装 {% 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 @@ -8,44 +8,87 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} +{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-self-hosted-runners-notice %} -### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} +### 关于 {% data variables.product.prodname_registry %} 与 {% data variables.product.prodname_actions %} -{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} 更多信息请参阅“[关于 {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)”。 -You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. +您可以通过在工作流程中发布或安装包来扩展仓库的 CI 和 CD 功能。 {% if currentVersion == "free-pro-team@latest" %} -#### Authenticating to {% data variables.product.prodname_github_container_registry %} +#### 向 {% data variables.product.prodname_github_container_registry %} 验证 {% data reusables.package_registry.container-registry-beta %} {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} -For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)." +有关身份验证示例，请参阅“[向 {% data variables.product.prodname_container_registry %} 验证](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)”。 {% endif %} -#### Authenticating to package registries on {% data variables.product.prodname_dotcom %} +#### 向 {% data variables.product.prodname_dotcom %} 上的软件包注册表验证 -{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The `GITHUB_TOKEN` has `read:packages` and `write:packages` scopes to the current repository. For forks, the token also has the `read:packages` scope for the parent repository. +{% if currentVersion == "free-pro-team@latest" %}如果您希望工作流程向 {% data variables.product.prodname_registry %} 验证以访问 {% data variables.product.product_name %} 上 {% data variables.product.prodname_container_registry %} 以外的软件包注册表，则{% else %}要向 {% data variables.product.product_name %} 上的软件包注册表验证，{% endif %}我们建议使用 {% data variables.product.product_name %} 在您启用 {% data variables.product.prodname_actions %} 时自动为您的仓库创建的 `GITHUB_TOKEN` 来验证，而不是使用个人访问令牌来验证。 `GITHUB_TOKEN` 具有对仓前仓库的 `read:packages` 和 `write:packages` 作用域。 对于复刻，该令牌还具有对父仓库的 `read:packages` 作用域。 -You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." +您还可以使用 {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} 上下文在工作流程文件中引用 `GITHUB_TOKEN`。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)”。 -### Publishing a package using an action +### 关于仓库拥有的包的权限和包访问权限 -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 %}. +{% note %} + +**注意：**仓库拥有的包包括 RubyGems、npm、Apache Maven、NuGet、Gradle 和 Docker 包，它们使用包命名空间 `docker.pkg.github.com`。 + +{% endnote %} + +启用 GitHub 操作后，GitHub 会在您的仓库中安装 GitHub 应用程序。 `GITHUB_TOKEN` 密码是一种 GitHub 应用程序安装访问令牌。 您可以使用安装访问令牌代表仓库中安装的 GitHub 应用程序进行身份验证。 令牌的权限仅限于包含您的工作流程的仓库。 更多信息请参阅“[GITHUB_TOKEN 的权限](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)”。 + +{% data variables.product.prodname_registry %} 允许您通过可用于 {% data variables.product.prodname_actions %} 工作流程的 `GITHUB_TOKEN` 推送和拉取包。 + +{% if currentVersion == "free-pro-team@latest" %} +### 关于 {% data variables.product.prodname_container_registry %} 的权限和包访问权限 + +{% data variables.product.prodname_container_registry %} (`ghcr.io`) 允许用户创建和管理容器，作为组织一级的独立资源。 容器可以归组织或个人用户帐户所有，您可以自定义与存储库权限分开的每个容器访问权限。 + +所有访问 {% data variables.product.prodname_container_registry %} 的工作流程都应该使用 `GITHUB_TOKEN` 而不是个人访问令牌。 有关安全最佳实践的更多信息，请参阅“[GitHub Actions 的安全强化](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)”。 + +### 通过工作流程修改的容器的默认权限和访问设置 + +当您通过工作流程创建、安装、修改或删除容器时，有一些默认权限和访问设置用于确保管理员能够访问工作流程。 您也可以调整这些访问设置。 + +例如，默认情况下，如果工作流程使用 `GITHUB_TOKEN` 创建容器，则： +- 容器继承运行工作流程的仓库的可见性和权限模型。 +- 在创建容器后，工作流程运行的仓库管理员将成为容器的管理员。 + +以下是管理包的工作流程的默认权限如何运作的更多示例。 + +| {% data variables.product.prodname_actions %} 工作流程任务 | 默认权限和访问 | +| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 下载现有容器 | - 如果容器是公开的，则任何仓库中运行的任何工作流程都可以下载容器。
- 如果容器是内部容器，则在企业帐户拥有的任何仓库中运行的所有工作流程都可以下载容器。 对于企业拥有的组织，您可以阅读企业中的任何仓库
- 如果容器是私有的，则只有在仓库中运行但在容器上获得读取权限的工作流程才可下载容器。
| +| 上传新版本到现有容器 | - 如果容器是私有、内部或公共的，则只有在该容器上获得写入权限的仓库中运行的工作流程才可将新版本上传到容器中。 | +| 删除容器或容器版本 | - 如果容器是私有、内部或公共的，则只有在该容器上获得删除权限的仓库中运行的工作流程才可删除容器的现有版本。 | + +您还可以使用更精细的方式调整对容器的访问，或调整一些默认权限行为。 更多信息请参阅“[配置容器映像的访问控制和可见性](/packages/guides/configuring-access-control-and-visibility-for-container-images)”。 + +{% endif %} + +### 使用操作发布包 + +您可以使用 {% data variables.product.prodname_actions %} 在持续集成 (CI) 流程中自动发布包。 如果代码符合您的质量标准，可使用这种持续部署 (CD) 方法自动创建新的包版本。 例如，您可以创建一个每当开发者向特定分支推送代码时运行 CI 测试的工作流程。 如果测试通过，则工作流程可以将新的包版本发布到 {% 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 %}: +下面的示例演示如何使用 {% data variables.product.prodname_actions %} 构建和测试应用程序，然后自动创建 Docker 映像并将其发布到 {% 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: +- 在仓库中创建新的工作流程文件（例如 `.github/workflows/deploy-image.yml`），并添加以下 YAML： {% raw %} - ``` + ```yaml{:copy} name: Create and publish a package on: push: @@ -99,16 +142,14 @@ The following example demonstrates how you can use {% data variables.product.pro with: username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - registry: docker.pkg.github.com + registry: {% endraw %}{% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %} repository: ${{ github.repository }}/octo-image tag_with_sha: true tag_with_ref: true ``` {% endraw %} - The relevant settings are explained in the following table: - - + 下表介绍了相关设置：
@@ -145,7 +186,7 @@ on: {% endraw %} @@ -180,7 +221,7 @@ on: {% endraw %} @@ -193,7 +234,7 @@ on: {% endraw %} @@ -206,7 +247,7 @@ uses: docker/build-push-action@v1 {% endraw %} @@ -219,7 +260,7 @@ with: {% endraw %} @@ -232,7 +273,7 @@ username: ${{ github.actor }} {% endraw %} @@ -245,20 +286,18 @@ password: ${{ secrets.GITHUB_TOKEN }} {% endraw %} @@ -271,7 +310,7 @@ repository: ${{ github.repository }}/octo-image {% endraw %} @@ -284,12 +323,12 @@ tag_with_sha: true {% endraw %}
@@ -121,7 +162,7 @@ on: {% endraw %} - Configures the Create and publish a package workflow to run every time a change is pushed to the branch called release. + 配置 Create and publish a package 工作流程，以在每次向名为 release 的分支推送更改时运行。
- This job installs NPM and uses it to build the app. + 此作业会安装 NPM 并使用它来构建应用程序。
- 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. + 此作业使用 npm test 测试代码。 needs: run-npm-build 命令使此作业依赖于 run-npm-build 作业。
- 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. + 创建名为 Build container image 的新步骤。 此步骤在 build-and-push-image 作业中运行。 needs: run-npm-test 命令使此作业依赖于 run-npm-test 作业。
- 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 %}. + 使用 Docker build-push-action 操作构建基于仓库的 Dockerfile 的映像。 如果构建成功，它会将映像推送到 {% data variables.product.prodname_registry %}。
- Sends the required parameters to the build-push-action action. This are defined in the subsequent lines. + 将所需参数发送到 build-push-action 操作。 这将在后面的行中定义。
- Defines the user account that will publish the packages. Once published, the packages are owned by the account defined here. + 定义将发布包的用户帐户。 发布后，包归此处定义的帐户所有。
- Defines the password that is used to access {% data variables.product.prodname_registry %}. + 定义用于访问 {% data variables.product.prodname_registry %} 的密码。
-{% raw %} ```yaml -registry: docker.pkg.github.com +registry: {% if currentVersion == "github-ae@latest" %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %} ``` -{% endraw %} - Defines the registry that will host the resulting packages. This example uses {% data variables.product.prodname_registry %}. + 定义将托管所生成的包的注册表。 此示例使用 {% data variables.product.prodname_registry %}。{% if currentversion == "github-ae@latest" %} 将 YOUR-HOSTNAME 替换为您的企业名称。{% endif %} {% if currentversion == "free proteam@latest" %} 如果您使用的是 {% data variables.product.prodname_container_registry %}，则使用 ghcr.io 作为主机名。{% endif %}
- 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. + 定义哪个仓库将托管所生成的包，并设置已发布包的名称。 将 octo-image 替换为要用于包的名称。
- Tags the published package with the first seven characters of the commit's SHA. For example, sha-2f2d842. + 使用提交 SHA 的前七个字符标记已发布的包。 例如，sha-2f2d842。
- + {% raw %} ```yaml tag_with_ref: true @@ -297,22 +336,100 @@ 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. + 使用 git ref 标记已发布的包。 这可以是用于创建包的分支名称。
-- 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)." +- 每次将更改推送至仓库中名为 `release` 的分支时，这个新工作流程都会自动运行。 您可以在 **Actions（操作）**选项卡中查看进度。 +- 工作流程完成几分钟后，新包将在您的仓库中可见。 要查找可用的包，请参阅“[查看仓库的包](/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. +### 使用操作安装包 -Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %} +您可以使用 {% data variables.product.prodname_actions %} 将安装包作为 CI 流程的一部分。 例如，您可以配置一个工作流程：每当开发者向拉取请求推送代码时，该工作流程就会通过下载并安装 {% data variables.product.prodname_registry %} 托管的包来解析依赖项。 然后，该工作流程就可以运行需要这些依赖项的 CI 测试。 + +使用 `GITHUB_TOKEN` 时，通过 {% data variables.product.prodname_actions %} 安装 {% data variables.product.prodname_registry %} 托管的包只需极少的配置或额外身份验证。{% if currentVersion == "free-pro-team@latest" %} 使用操作安装包时，数据传输也是免费的。 更多信息请参阅“[关于 {% 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` cannot install packages from any private repository besides the repository where the action runs. You cannot currently use `GITHUB_TOKEN` to authenticate to {% data variables.product.prodname_github_container_registry %}. {% endif %} {% data reusables.package_registry.actions-configuration %} + +{% if currentVersion == "free-pro-team@latest" %} +### 升级访问 `ghcr.io`的工作流程 + +{% data reusables.package_registry.github-token-security-over-pat %} + +使用 `GITHUB_TOKEN` 而不是 PAT（包括 `repo` 范围），可提高仓库的安全性，因为您不需要使用长期 PAT，以免对运行工作流程的仓库提供不必要的访问权限。 有关安全最佳实践的更多信息，请参阅“[GitHub Actions 的安全强化](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)”。 + +1. 导航到包登陆页面。 +1. 在左侧边栏中，单击 **Actions access（操作访问）**。 ![左侧菜单中的"Actions access（操作访问）"选项](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) +2. 为了确保您的容器包能够访问您的工作流程，您必须添加仓库，其中工作流程存储到您的容器。 单击 **Add repository（添加仓库）**并搜索要添加的仓库。 !["添加仓库"按钮](/assets/images/help/package-registry/add-repository-button.png) + {% note %} + + **注意：**通过 **Actions access（操作访问）**菜单选项将仓库添加到容器不同于将容器连接到仓库。 更多信息请参阅“[确保工作流程访问您的包](/packages/guides/configuring-access-control-and-visibility-for-container-images#ensuring-workflow-access-to-your-package)”和“[将仓库连接到容器映像](/packages/guides/connecting-a-repository-to-a-container-image)”。 + + {% endnote %} +3. （可选）使用“role（角色）”下拉菜单，选择您希望仓库访问您的容器映像所必须拥有的默认访问权限。 ![授予仓库的权限访问级别](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) +5. 打开工作流程文件。 在您登录到 `ghcr.io` 的行上，将 PAT 替换为 {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}。 + +例如，此工作流程发布使用 {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} 进行身份验证的 Docker 容器。 + +{% raw %} +```yaml{:copy} +name: Demo Push + +on: + push: + # Publish `master` as Docker `latest` image. + branches: + - master + - seed + + # Publish `v1.2.3` tags as releases. + tags: + - v* + + # Run tests for any PRs. + pull_request: + +env: + IMAGE_NAME: ghtoken_product_demo + +jobs: + # Push image to GitHub Packages. + # See also https://docs.docker.com/docker-hub/builds/ + push: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Build image + run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}" + + - name: Log into registry + # This is where you will update the PAT to GITHUB_TOKEN + run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin + + - name: Push image + run: | + IMAGE_ID=ghcr.io/${{ github.repository_owner }}/$IMAGE_NAME + + # Change all uppercase to lowercase + IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]') + # Strip git ref prefix from version + VERSION=$(echo "${{ github.ref }}" | sed -e 's,.*/\(.*\),\1,') + # Strip "v" prefix from tag name + [[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//') + # Use Docker `latest` tag convention + [ "$VERSION" == "master" ] && VERSION=latest + echo IMAGE_ID=$IMAGE_ID + echo VERSION=$VERSION + docker tag $IMAGE_NAME $IMAGE_ID:$VERSION + docker push $IMAGE_ID:$VERSION +``` +{% endraw %} + +{% endif %} diff --git a/translations/zh-CN/content/packages/index.md b/translations/zh-CN/content/packages/index.md index 3364477bef..014fd381ee 100644 --- a/translations/zh-CN/content/packages/index.md +++ b/translations/zh-CN/content/packages/index.md @@ -20,8 +20,8 @@ featuredLinks: - /packages/guides/enabling-improved-container-support - /packages/guides/configuring-rubygems-for-use-with-github-packages changelog: - label: 'packages' - prefix: 'Packages: ' + label: '包' + prefix: '包:' redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry 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 bfbe056655..9a46526eeb 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 @@ -1,6 +1,6 @@ --- title: 关于 GitHub 包 -intro: '{% data variables.product.prodname_registry %} 是一种软件包托管服务，允许您私下或公开托管软件包，并将包用作项目中的依赖项。' +intro: '{% data variables.product.prodname_registry %} 是一项软件包托管服务，允许您私下为指定的用户托管您的软件包{% if currentversion == "github-ae@latest" %}，或在内部为您的企业{% else %}或公开{% endif %}托管，以及在您的项目中使用软件包作为依赖项。' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/about-github-package-registry @@ -10,32 +10,27 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' + github-ae: '*' --- {% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} ### 关于 {% data variables.product.prodname_registry %} -{% data variables.product.prodname_registry %} 是一种包托管服务，与 {% data variables.product.prodname_dotcom %} 完全集成。 {% data variables.product.prodname_registry %} 将您的源代码和包组合在一起，以提供集成的权限管理和计费，使您能够在 {% data variables.product.product_name %} 上专注于软件开发。 +{% data variables.product.prodname_registry %} 是一种包托管服务，与 {% data variables.product.prodname_dotcom %} 完全集成。 {% data variables.product.prodname_registry %} 将您的源代码和软件包组合在一起，以提供集成的权限管理{% if currentVersion != "github-ae@latest" %}和计费{% endif %}，使您能够在 {% data variables.product.product_name %} 上专注于软件开发。 您可以将 {% data variables.product.prodname_registry %} 与 {% data variables.product.product_name %} API、{% data variables.product.prodname_actions %} 以及 web 挂钩集成在一起，以创建端到端的 DevOps 工作流程，其中包括您的代码、CI 和部署解决方案。 您可以在一个仓库中托管多个包，并通过查看包的自述文件、下载统计、版本历史等，了解每个包的更多信息。 - -{% if currentVersion ver_gt "enterprise-server@2.21" %} - -![显示托管 npm、Rubygems、Apache Maven、Gradle、Nuget 和 Docker 的 URL 的 GitHub Packages 图表](/assets/images/help/package-registry/ghes-packages-diagram.png) - -{% endif %} +![显示支持 npm、RubyGems、Apache Maven、Gradle、Nuget 和 Docker 的软件包的示意图](/assets/images/help/package-registry/packages-overview-diagram.png) {% 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 %} -![显示托管 npm、Rubygems、Apache Maven、Gradle、Nuget 和 Docker 的 URL 的 GitHub Packages 图表](/assets/images/help/package-registry/packages-overview-diagram.png) - {% endif %} #### 查看包 @@ -44,10 +39,10 @@ versions: #### 关于包权限和可见性 -| | 包注册表 | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 托管位置 | 您可以在一个仓库中托管多个包。 | -| 权限 | {% data reusables.package_registry.public-or-private-packages %} 您可以使用 {% data variables.product.prodname_dotcom %} 角色和团队来限制谁可以安装或发布每个包，因为包会继承仓库的权限。 对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | +| | 包注册表 | +| ---- | ---------------------------------------------------------------------------------------- | +| 托管位置 | 您可以在一个仓库中托管多个包。 | +| 权限 | 每个包都继承托管包的仓库的权限。

例如，对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | | 可见性 | {% data reusables.package_registry.public-or-private-packages %} {% if currentVersion == "free-pro-team@latest" %} @@ -63,49 +58,16 @@ versions: {% data variables.product.prodname_registry %} 使用您已经熟悉的原生包工具命令来发布和安装包版本。 #### 对包注册表的支持 -{% if currentVersion == "free-pro-team@latest" %} -包注册表使用 `PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` 作为包主机 URL，用包命名空间替换 `PACKAGE-TYPE`。 例如，Gemfile 将托管在 `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` 上。 - -{% else %} - -{% data variables.product.product_location %} 支持的软件包类型可能有所不同，因为您的网站管理员可能启用或禁用对不同软件包的支持。 更多信息请参阅“[为企业管理 GitHub Packages](/enterprise/admin/packages)”。 - -如果 {% data variables.product.product_location %} 已启用子域隔离，则软件包注册表将使用 `PACKAGE-TYPE.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` 作为软件包主机 URL，用软件包命名空间替换 `PACKAGE-TYPE`。 例如，Dockerfile 将托管在 `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` 上。 - -如果 {% data variables.product.product_location %} 已禁用子域隔离，则软件包注册表将使用 `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` 作为软件包主机 URL。 例如，Gemfile 将托管在 `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` 上，用 {% data variables.product.prodname_ghe_server %} 实例的主机名称替换 *HOSTNAME*。 |{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -| 语言 | 描述 | 包格式 | 包客户端 | 包命名空间 | -| ---------- | ---------------------- | ----------------------------------- | ------------ | ----------------------------------------------------- | -| JavaScript | 节点包管理器 | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | RubyGems 包管理器 | `Gemfile` | `gem` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Apache Maven 项目管理和理解工具 | `pom.xml` | `mvn` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Java 的 Gradle 构建自动化工具 | `build.gradle` 或 `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | .NET 的 NuGet 包管理 | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | - -{% else %} - -在 {% data variables.product.product_location %} 上启用了子域隔离： - -| 语言 | 描述 | 包格式 | 包客户端 | 包命名空间 | -| ---------- | ---------------------- | ----------------------------------- | ------------ | ----------------------------------------------- | -| JavaScript | 节点包管理器 | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | RubyGems 包管理器 | `Gemfile` | `gem` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Apache Maven 项目管理和理解工具 | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Java 的 Gradle 构建自动化工具 | `build.gradle` 或 `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | .NET 的 NuGet 包管理 | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| 不适用 | Docker 容器管理平台 | `Dockerfile` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | - -在 {% data variables.product.product_location %} 上禁用了子域隔离： - -| 语言 | 描述 | 包格式 | 包客户端 | 包命名空间 | -| ---------- | ---------------------- | ----------------------------------- | ------------ | --------------------------------------------------------- | -| JavaScript | 节点包管理器 | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | RubyGems 包管理器 | `Gemfile` | `gem` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Apache Maven 项目管理和理解工具 | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Java 的 Gradle 构建自动化工具 | `build.gradle` 或 `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | .NET 的 NuGet 包管理 | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` | +| 语言 | 描述 | 包格式 | 包客户端 | +| ---------- | ---------------------- | ----------------------------------- | ------------ | +| JavaScript | 节点包管理器 | `package.json` | `npm` | +| Ruby | RubyGems 包管理器 | `Gemfile` | `gem` | +| Java | Apache Maven 项目管理和理解工具 | `pom.xml` | `mvn` | +| Java | Java 的 Gradle 构建自动化工具 | `build.gradle` 或 `build.gradle.kts` | `gradle` | +| .NET | .NET 的 NuGet 包管理 | `nupkg` | `dotnet` CLI | +| 不适用 | Docker 容器管理平台 | `Dockerfile` | `Docker` | +{% if currentVersion ver_gt "enterprise-server@2.22" %} {% note %} **注：**禁用子域隔离时，不支持 Docker。 @@ -132,14 +94,16 @@ versions: 例如： - 要从仓库下载和安装包，您的令牌必须具有 `read:packages` 作用域，并且您的用户帐户必须对该仓库具有读取权限。 -- 要在 {% data variables.product.product_name %} 上删除私有包的特定版本，您的令牌必须具有 `delete:packages` 和 `repo` 作用域。 公共包无法删除。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”。 +- {% if currentversion == "free-proteam@latest" or if currentversion ver_gt "enterprise-server@3. %}要在 {% data variables.product.product_name %}上删除软件包，您的令牌至少必须有 `delete:packages` 和 `read:packages` 作用域。 Repo-scoped 软件包也需要 `repo` 作用域。{% elsif currentVersion ver_lt "enterprise-server@3.1" %}要在 {% data variables.product.product_name %} 上删除私有软件的指定版本，您的令牌必须具有 `delete:packages` 和 `repo` 作用域。 公共包不能删除。{% elsif currentVersion == "github-ae@latest" %}要在 {% data variables.product.product_name %} 上删除包的指定版本，您必须具有 `delete:packages` 和 `repo` 作用域。{% endif %} 更多信息请参阅“{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}”。 -| 作用域 | 描述 | 仓库权限 | -| ----------------- | ----------------------------------------------------------- | ------ | -| `read:packages` | 从 {% data variables.product.prodname_registry %} 下载和安装包 | 读取 | -| `write:packages` | 将包上传和发布到 {% data variables.product.prodname_registry %} | 写入 | -| `delete:packages` | 从 {% data variables.product.prodname_registry %} 删除私有包的特定版本 | 管理员 | -| `repo` | 上传和删除包（连同 `write:packages` 或 `delete:packages`） | 写入或管理员 | +| 作用域 | 描述 | 仓库权限 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------ | +| `read:packages` | 从 {% data variables.product.prodname_registry %} 下载和安装包 | 读取 | +| `write:packages` | 将包上传和发布到 {% data variables.product.prodname_registry %} | 写入 | +| `delete:packages` | | | +| {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 从 {% data variables.product.prodname_registry %} 删除包 {% elsif currentVersion ver_lt "enterprise-server@3.1" %} 从 {% data variables.product.prodname_registry %} 删除私有包的指定版本{% elsif currentVersion == "github-ae@latest" %} 从 {% data variables.product.prodname_registry %} 删除包的指定版本 {% endif %} | | | +| 管理员 | | | +| `repo` | 上传和删除包（连同 `write:packages` 或 `delete:packages`） | 写入或管理员 | 创建 {% data variables.product.prodname_actions %} 工作流程时，您可以使用 `GITHUB_TOKEN` 发布和安装 {% data variables.product.prodname_registry %} 中的包，无需存储和管理个人访问令牌。 @@ -150,7 +114,27 @@ 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)”。 +{% if currentVersion == "free-pro-team@latest" %} +您可以在 +{% data variables.product.product_name %} 用户界面中或使用 REST API 删除包。 更多信息请参阅“[{% data variables.product.prodname_registry %} API](/rest/reference/packages)”。 +{% endif %} + +{% if currentVersion ver_gt "enterprise-server@3.0" %} +您可以在 +{% data variables.product.product_name %} 用户界面中删除私有或公共包。 或者对 repo-scoped 包，您可以使用 GraphQL 删除私有包的版本。 +{% endif %} + +{% if currentVersion ver_lt "enterprise-server@3.1" %} +您可以在 +{% data variables.product.product_name %} 用户界面中或使用 GraphQL API 删除私有包的版本。 +{% endif %} + +{% if currentVersion == "github-ae@latest" %} +您可以在 +{% data variables.product.product_name %} 用户界面中或使用 GraphQL API 删除私有包的版本。 +{% endif %} + +使用 GraphQL API 查询和删除私有包时，必须使用与向 {% data variables.product.prodname_registry %} 验证时相同的令牌。 更多信息请参阅“{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif currentVersion ver_lt "enterprise-server@3.1" or currentVersion == "github-ae@latest" %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}”和“[使用 GraphQL 建立呼叫](/graphql/guides/forming-calls-with-graphql)”。 您可以配置 web 挂钩来订阅与包相关的事件，例如包的发布或更新等事件。 更多信息请参阅“[`package` web 挂钩事件](/webhooks/event-payloads/#package)”。 diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..d1013e5b50 --- /dev/null +++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md @@ -0,0 +1,68 @@ +--- +title: 关于自定义域名和 GitHub 页面 +intro: '{% data variables.product.prodname_pages %} 支持使用自定义域名，或者将网站的 URL 根目录从默认值（如 `octocat.github.io`）更改为您拥有的任何域名。' +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 + - /github/working-with-github-pages/about-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - 页面 +--- + +### 支持的自定义域 + +{% data variables.product.prodname_pages %} 可使用两种类型的域名：子域名和 apex 域名。 有关不支持的自定义域名列表，请参阅“[自定义域名和 {% data variables.product.prodname_pages %} 疑难解答](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)“。 + +| 支持的自定义域类型 | 示例 | +| --------- | ------------------ | +| `www` 子域 | `www.example.com` | +| 自定义子域 | `blog.example.com` | +| Apex 域 | `example.com` | + +You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)." + +建议始终使用 `www` 子域名，即使您也同时使用 apex 域。 When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。 + +在配置用户或组织网站的自定义域后，自定义域名将替换未配置自定义域的帐户所拥有的任何项目网站 URL 的 `.github.io` 或 `.github.io` 部分。 例如，如果您的用户网站的自定义域名为 `www.octocat.com`，并且您拥有一个未自定义域名的项目网站，该网站从名为 `octo-project` 的仓库发布，则该仓库的 {% data variables.product.prodname_pages %} 网站将在 `www.octocat.com/octo-project` 上提供。 + +### 对您的 {% data variables.product.prodname_pages %} 网站使用子域名 + +子域名是根域前 URL 的一部分。 您可以将子域名配置为 `www` 或网站的独特部分，如 `blog.example.com`。 + +子域名配置通过 DNS 提供商使用 `CNAME` 记录配置。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)。 + +#### `www` 子域 + +`www` 子域名是最常用的一种子域名。 例如，`www.example.com` 包含 `www` 子域名。 + +`www` 子域名是最稳定的一种自定义域，因为 `www` 子域名不受 {% data variables.product.product_name %} 服务器 IP 地址变动的影响。 + +#### 自定义子域 + +A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. 自定义子域主要在您需要将网站分为两个不同的部分时使用。 例如，您可以创建一个名为 `blog.example.com` 并自定义该部分与 `www.example.com` 分开。 + +### 对您的 {% data variables.product.prodname_pages %} 网站使用 apex 域 + +Apex 域是一个不包含子域的自定义域，如 `example.com`。 Apex 域也称为基础域、裸域、根 apex 域或区域 apex 域。 + +Apex 域配置通过 DNS 提供商使用 `A`, `ALAS` 或 `ANAME` 记录配置。 更多信息请参阅“[管理 {% 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 %}更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)”。 + +### 在 {% data variables.product.prodname_pages %} 站点禁用时更新自定义域 + +如果您的 {% data variables.product.prodname_pages %} 站点设置了自定义域，并且站点已禁用，您应立即通过 DNS 提供商更新或删除 DNS 记录，以避免域接管的风险。 在您的网站被禁用时拥有通过 DNS 提供商配置的自定义域，可能会导致其他人在您的一个子域上托管网站。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。 + +有许多原因会导致您的网站被自动禁用。 + +- 如果您从 {% data variables.product.prodname_pro %} 降级到 {% data variables.product.prodname_free_user %}，则目前发布自您的帐户中私有仓库的任何 {% data variables.product.prodname_pages %} 站点都会取消发布。 更多信息请参阅“[Downgrading your {% data variables.product.prodname_dotcom %} 结算方案](/articles/downgrading-your-github-billing-plan)”。 +- 如果将私人仓库转让给使用 {% data variables.product.prodname_free_user %} 的个人帐户，仓库将失去对 {% data variables.product.prodname_pages %} 功能的访问，当前发布的 {% data variables.product.prodname_pages %} 站点将取消发布。 更多信息请参阅“[转让仓库](/articles/transferring-a-repository)”。 + +### 延伸阅读 + +- "[自定义域名和 {% data variables.product.prodname_pages %} 疑难解答](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md new file mode 100644 index 0000000000..f3fcb3d1f6 --- /dev/null +++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md @@ -0,0 +1,23 @@ +--- +title: 配置 GitHub Pages 站点的自定义域 +intro: '您可以自定义 {% 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 + - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - 页面 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md new file mode 100644 index 0000000000..430305f57a --- /dev/null +++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -0,0 +1,121 @@ +--- +title: 管理 GitHub Pages 站点的自定义域 +intro: '您可以设置或更新某些 DNS 记录和仓库设置，以将 {% data variables.product.prodname_pages %} 站点的默认域指向自定义域。' +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 + - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - 页面 +--- + +拥有仓库管理员权限的人可为 {% data variables.product.prodname_pages %} 站点配置自定义域。 + +### 关于自定义域配置 + +使用 DNS 提供程序配置自定义域之前，请确保将自定义域添加到您的 {% data variables.product.prodname_pages %} 站点。 使用 DNS 提供程序配置自定义域而不将其添加到 {% data variables.product.product_name %}，可能导致其他人能够在您的某个子域上托管站点。 + +{% windows %} + +`dig` 命令可用于验证 DNS 记录的配置是否正确，它未包含在 Windows 中。 在验证 DNS 记录的配置是否正确之前，必须安装 [BIND](https://www.isc.org/bind/)。 + +{% endwindows %} + +{% note %} + +**注：**DNS 更改可能需要最多 24 小时才能传播。 + +{% endnote %} + +### 配置子域 + +要设置 `www` 或自定义子域，例如 `www.example.com` 或 `blog.example.com`，您必须将域添加到仓库设置，这将在站点的仓库中创建 CNAME 文件。 然后，通过 DNS 提供商配置 CNAME 记录。 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. 在 "Custom domain（自定义域）"下，输入自定义域，然后单击 **Save（保存）**。 这将创建一个在发布源根目录中添加 _CNAME _ 文件的提交。 ![保存自定义域按钮](/assets/images/help/pages/save-custom-subdomain.png) +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 %} +6. 要确认您的 DNS 记录配置正确，请使用 `dig` 命令，将 _WWW.EXAM.COM_ 替换为您的子域。 +```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 %} + +### 配置 apex 域 + +要设置 apex 域，例如 `example.com`，您必须使用 DNS 提供程序配置 {% data variables.product.prodname_pages %} 仓库中的 _CNAME_ 文件以及至少一条 `ALIAS`、`ANAME` 或 `A` 记录。 + +{% data reusables.pages.www-and-apex-domain-recommendation %}更多信息请参阅“[配置子域](#configuring-a-subdomain)”。 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. 在 "Custom domain（自定义域）"下，输入自定义域，然后单击 **Save（保存）**。 这将创建一个在发布源根目录中添加 _CNAME _ 文件的提交。 ![保存自定义域按钮](/assets/images/help/pages/save-custom-apex-domain.png) +5. 导航到 DNS 提供程序并创建一个 `ALIAS`、`ANAME` 或 `A` 记录。 {% data reusables.pages.contact-dns-provider %} + - 要创建 `ALIAS` 或 `ANAME` 记录，请将 apex 域指向站点的默认域。 {% data reusables.pages.default-domain-information %} + - 要创建 `A` 记录，请将 apex 域指向 {% data variables.product.prodname_pages %} 的 IP 地址。 + ```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. 要确认您的 DNS 记录配置正确，请使用 `dig` 命令，将 _EXAM.COM_ 替换为您的 apex 域。 确认结果与上面 {% data variables.product.prodname_pages %} 的 IP 地址相匹配。 + ```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 %} + +### Configuring an apex domain and the `www` subdomain variant + +When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant. + +To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain, which will create an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)." + +After you configure the apex domain, you must to configure a CNAME record with your DNS provider. + +1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %} +2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant. +```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 +``` +### Removing a custom domain + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +4. Under "Custom domain," click **Remove**. ![保存自定义域按钮](/assets/images/help/pages/remove-custom-domain.png) + +### 延伸阅读 + +- "[自定义域名和 {% data variables.product.prodname_pages %} 疑难解答](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md new file mode 100644 index 0000000000..9d4c6cec87 --- /dev/null +++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -0,0 +1,65 @@ +--- +title: 自定义域和 GitHub Pages 疑难解答 +intro: '您可以检查常见错误，以解决与 {% data variables.product.prodname_pages %} 站点的自定义域或 HTTPS 相关的问题。' +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 + - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - 页面 +--- + +### _CNAME_ 错误 + +自定义域存储在发布源的根目录下的 _CNAME_ 文件中。 您可以通过仓库设置或手动添加或更新此文件。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。 + +要让您的站点呈现在正确的域中，请确保您的 _CNAME_ 文件仍存在于仓库中。 例如，许多静态站点生成器会强制推送到您的仓库，这可能会覆盖在配置自定义域时添加到仓库中的 _CNAME_ 文件。 如果您在本地构建站点并将生成的文件推送到 {% data variables.product.product_name %}，请确保先将添加 _CNAME_ 文件的提交拉取到本地仓库，使该文件纳入到构建中。 + +然后，确保 _CNAME_ 文件格式正确。 + +- _CNAME_ 文件名必须全部大写。 +- _CNAME_ 文件只能包含一个域。 要将多个域指向您的站点，必须通过 DNS 提供程序设置重定向。 +- _CNAME_ 文件只能包含一个域名。 例如，`www.example.com`、`blog.example.com` 或 `example.com`。 +- 域名在所有 {% data variables.product.prodname_pages %} 站点中必须是唯一的。 例如，如果另一个仓库的 _CNAME_ 文件包含 `example.com`，则不能在您仓库的 _CNAME_ 文件中使用 `example.com`。 + +### DNS 配置错误 + +如果将站点的默认域指向自定义域时遇到问题，请联系 DNS 提供商。 + +您还可以测试自定义域的 DNS 记录是否配置正确。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。 + +### 自定义域名不受支持 + +如果您的自定义域不受支持，则可能需要将您的域更改为受支持的域。 也可以联系您的 DNS 提供商，看他们是否提供域名转发服务。 + +确保您的站点没有： +- 使用多个 apex 域。 例如，同时使用 `example.com` 和 `anotherexample.com`。 +- 使用多个 `www` 子域。 例如，同时使用 `www.example.com` 和 `www.anotherexample.com`。 +- 同时使用 apex 域和自定义子域。 例如，同时使用 `example.com` 和 `docs.example.com`。 + + 一个例外是 `www` 子域。 如果配置正确， `www` 子域将自动重定向到 apex 域。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)”。 + +{% data reusables.pages.wildcard-dns-warning %} + +有关支持的自定义域列表，请参阅“[关于自定义域和 {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)”。 + +### HTTPS 错误 + +通过 _CNAME_、`ALIAS`、`ANAME` 或 `A` DNS 记录正确配置的使用自定义域的 {% data variables.product.prodname_pages %} 站点可通过 HTTPS 进行访问。 更多信息请参阅“[使用 HTTPS 保护 {% data variables.product.prodname_pages %} 站点](/articles/securing-your-github-pages-site-with-https)”。 + +配置自定义域后，您的站点可能需要最多一个小时才能通过 HTTPS 访问。 更新现有 DNS 设置后，您可能需要删除自定义域并将其重新添加到站点仓库，以触发启用 HTTPS 的进程。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。 + +如果您使用的是证书颁发机构授权 (CAA) 记录，则必须存在至少一个值为 `letsencrypt.org` 的 CAA 记录，才能通过 HTTPS 访问您的站点。 更多信息请参阅 Let's Encrypt 文档中的“[证书颁发机构授权 (CAA)](https://letsencrypt.org/docs/caa/)”。 + +### Linux 上的 URL 格式 + +如果您站点的 URL 包含以破折号开头或结尾的用户名或组织名称，或者包含连续破折号，则使用 Linux 浏览的用户在尝试访问您的站点时会收到服务器错误。 要解决此问题，请更改您的 {% data variables.product.product_name %} 用户名以删除非字母数字字符。 更多信息请参阅“[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username/)”。 + +### 浏览器缓存 + +如果您最近更改或删除了自定义域，但无法在浏览器中访问新 URL，则可能需要清除浏览器的缓存才能访问新 URL。 有关清除缓存的更多信息，请参阅浏览器的文档。 diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md new file mode 100644 index 0000000000..aec5119f8b --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -0,0 +1,150 @@ +--- +title: 关于 GitHub Pages +intro: '您可以使用 {% data variables.product.prodname_pages %} 直接从 {% 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 + - /github/working-with-github-pages/about-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +### 关于 {% 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 %} 站点的示例。 + +{% if currentVersion == "free-pro-team@latest" %} +您可以在 {% data variables.product.prodname_dotcom %} 的 `github.io` 域或自己的自定义域上托管站点。 更多信息请参阅“[对 {% data variables.product.prodname_pages %} 使用自定义域](/articles/using-a-custom-domain-with-github-pages)”。 +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.about-private-publishing %}更多信息请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 +{% endif %} + +要开始使用，请参阅“[创建 {% data variables.product.prodname_pages %} 站点](/articles/creating-a-github-pages-site)”。 + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +组织所有者可禁止从组织的仓库发布 {% data variables.product.prodname_pages %} 站点。 更多信息请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 +{% endif %} + +### {% data variables.product.prodname_pages %} 站点的类型 + +有三种类型的 {% data variables.product.prodname_pages %} 站点：项目、用户和组织。 项目站点连接到 {% data variables.product.product_name %} 上托管的特定项目，例如 JavaScript 库或配方集合。 用户和组织站点连接到特定的 {% data variables.product.product_name %} 帐户。 + +要发布用户站点，必须创建用户帐户所拥有的名为 {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}` 的仓库。`{% endif %}. 要发布组织站点，必须创建组织所拥有的名为 {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}` 的仓库。`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}除非您使用的是自定义域，否则用户和组织站点位于 `http(s)://.github.io` 或 `http(s)://.github.io`。{% elsif currentVersion == "github-ae@latest" %}用户和组织站点位于 `http(s)://pages./` 或 `http(s)://pages./`。{% endif %} + +项目站点的源文件与其项目存储在同一个仓库中。 {% if currentVersion == "free-pro-team@latest" %}除非您使用的是自定义域，否则项目站点位于 `http(s)://.github.io/` 或 `http(s)://.github.io/`。{% elsif currentVersion == "github-ae@latest" %}项目站点位于 `http(s)://pages.///` 或 `http(s)://pages.///`。{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +如果您私下发布站点，则站点的 URL 将有所不同。 更多信息请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +有关自定义域如何影响站点 URL 的更多详细，请参阅“[关于自定义域和 {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)”。 +{% endif %} + +您只能为 {% data variables.product.product_name %} 上的每个帐户创建一个用户或组织站点。 项目站点（无论是组织还是用户帐户拥有）没有限制。 + +{% if enterpriseServerVersions contains currentVersion %} +您的站点可用的 URL 取决于是否为 {% data variables.product.product_location %} 启用了子域隔离。 + +| 站点类型 | 子域隔离已启用 | 子域隔离已禁用 | +| ---- | ------- | ------- | +| | | | + 用户 | + +`http(s)://pages./` | `http(s):///pages/` | 组织 | `http(s)://pages./` | `http(s):///pages/` | 用户帐户拥有的项目站点 | `http(s)://pages.///` | `http(s):///pages///` 组织帐户拥有的项目站点 | `http(s)://pages.///` | `http(s):///pages///` + +更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)”或联系您的站点管理员。 +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +{% note %} + +**注：**使用旧版 `.github.com` 命名方案的仓库仍将发布，但访问者将从 `http(s)://.github.com` 重定向到 `http(s)://.github.io`。 如果 `.github.com` 和 `.github.io` 仓库均存在，将仅发布 `.github.io` 仓库。 + +{% endnote %} +{% endif %} + +### {% data variables.product.prodname_pages %} 站点的发布来源 + +{% data variables.product.prodname_pages %} 站点的发布来源是存储站点源文件的分支和文件夹。 + +{% 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` 分支的根目录。 + +如果要将站点的源文件保留在不同的位置，您可以更改站点的发布源。 您可以从仓库的任何分支发布站点 - 从该分支上仓库的根目录 `/` 或从该分支上的 `/docs` 文件夹发布。 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)”。 + +如果选择任何分支的 `/docs` 文件夹作为您的发布来源，{% data variables.product.prodname_pages %} 将读取 `/docs` 文件夹中的所有内容以发布您的站点{% if currentVersion == "free-pro-team@latest" %}（包括 _CNAME_ 文件）{% endif %}。{% if currentVersion == "free-pro-team@latest" %}例如，当您通过 {% data variables.product.prodname_pages %} 设置编辑自定义域时，该自定义域将写入 `/docs/CNAME`。 有关 _CNAME_ 文件的更多信息，请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %} + +{% else %} + +用户和组织站点的默认发布来源是 `master` 分支。 如果用户和组织站点的仓库是 `master` 分支，您的站点将从该分支自动发布。 您无法为用户或组织站点选择不同的发布来源。 + +项目站点的默认发布来源是 `gh-pages` 分支。 如果项目站点的仓库有 `gh-pages` 分支，您的站点将从该分支自动发布。 + +项目站点也可以从 `master` 分支或 `master` 分支上的 `/docs` 文件夹发布。 要从这些来源之一发布站点，您必须配置不同的发布来源。 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)”。 + +如果选择 `master` 分支的 `/docs` 文件夹作为您的发布来源，{% data variables.product.prodname_pages %} 将读取 `/docs` 文件夹中的所有内容以发布您的站点{% if currentVersion == "free-pro-team@latest" %}（包括 _CNAME_ 文件）{% endif %}。{% if currentVersion == "free-pro-team@latest" %}例如，当您通过 {% data variables.product.prodname_pages %} 设置编辑自定义域时，该自定义域将写入 `/docs/CNAME`。 有关 _CNAME_ 文件的更多信息，请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %} + +您不能从任何其他分支发布项目站点，即使默认分支不是 `master` 或 `gh-pages`。 + +{% endif %} + +### 静态站点生成器 + +{% 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 %} 将使用 Jekyll 来构建您的站点。 如果您想使用除 Jekyll 以外的静态站点生成器，通过在发布来源的根目录中创建一个名为 `.nojekyll` 的空文件来禁用 Jekyll 构建过程，然后按照静态站点生成器的说明在 本地构建站点。 + +{% data variables.product.prodname_pages %} 不支持服务器端语言，例如 PHP、Ruby 或 Python。 + +### 使用 {% 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 reusables.pages.no_sensitive_data_pages %} +- 您对 {% data variables.product.prodname_pages %} 的使用受 [GitHub 服务条款](/articles/github-terms-of-service/)的约束，包括禁止转售。 + +#### 使用限制 +{% endif %} +{% data variables.product.prodname_pages %} 站点受到以下使用限制的约束： + + - {% data variables.product.prodname_pages %} 源仓库建议的限制为 1GB。if currentVersion == "free-pro-team@latest" %} 更多信息请参阅“[我的磁盘配额是多少？](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)”{% endif %} + - 发布的 {% data variables.product.prodname_pages %} 站点不得超过 1 GB。 +{% if currentVersion == "free-pro-team@latest" %} + - {% data variables.product.prodname_pages %} 站点的*软*带宽限制为每月 100GB。 + - {% data variables.product.prodname_pages %} 站点的*软*限制为每小时 10 次构建。 + +如果您的站点超出这些使用配额，我们可能无法为您的站点提供服务；或者您可能收到来自 {% data variables.contact.contact_support %} 的礼貌电子邮件，建议降低站点对服务器影响的策略，包括将第三方内容分发网络 (CDN) 置于您的站点前，利用其他 {% data variables.product.prodname_dotcom %} 功能（如发行版）或转用可能更符合您需求的其他托管服务。 + +#### 禁止使用 + +{% data variables.product.prodname_pages %} 并非旨在用于或允许用作免费的 Web 托管服务来运行您的在线业务、电子商务站点或主要针对促进商业交易或提供商业软件即服务 (SaaS) 的任何其他网站。 + +此外，{% data variables.product.prodname_dotcom %} 不允许 {% data variables.product.prodname_pages %} 用于某些目的或活动。 有关禁止用途的列表，请参阅“[{% data variables.product.prodname_dotcom %} {% data variables.product.prodname_pages %} 附加产品条款](/github/site-policy/github-additional-product-terms#4-pages)”。 +{% endif %} + +### {% data variables.product.prodname_pages %} 上的 MIME 类型 + +MIME 类型是服务器发送到浏览器的标头，提供有关浏览器所请求文件性质和格式的信息。 {% data variables.product.prodname_pages %} 支持数千种文件扩展名中 750 多种 MIME 类型。 支持的 MIME 类型列表从 [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)。 + +### 延伸阅读 + +- {% data variables.product.prodname_learning %} 上的 [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md new file mode 100644 index 0000000000..8d4544525c --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -0,0 +1,46 @@ +--- +title: 使用主题选择器将主题添加到 GitHub Pages 站点 +intro: '您可以将主题添加到 {% data variables.product.prodname_pages %} 站点，以自定义站点的外观。' +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - 页面 +--- + +拥有仓库管理员权限的人可以使用主题选择器向 {% data variables.product.prodname_pages %} 站点添加主题。 + +### 关于主题选择器 + +主题选择器可用于向仓库添加 Jekyll 主题。 有关 Jekyll 的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll)”。 + +主题选择器如何工作取决于您的资源库是公共的还是私有的。 + - 如果已为仓库启用 {% data variables.product.prodname_pages %}，主题选择器会将主题添加到当前发布源。 + - 如果您的仓库是公共的，并且已对仓库禁用 {% data variables.product.prodname_pages %}，则使用主题选择器将启用 {% data variables.product.prodname_pages %} 并将默认分支配置为发布源。 + - 如果您的仓库是公共的，并且已对仓库禁用 {% data variables.product.prodname_pages %}，则必须先通过配置发布源来启用 {% data variables.product.prodname_pages %}，然后才可使用主题选择器。 + +有关发布源的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)”。 + +如果以前曾手动向仓库添加 Jekyll 主题，则这些文件在使用主题选择器后也可能应用。 为避免冲突，请先删除所有手动添加的主题文件夹和文件，然后再使用主题选择器。 更多信息请参阅“[使用 Jekyll 添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)”。 + +### 使用主题选择器添加主题 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. 在“{% data variables.product.prodname_pages %}”下，单击 **Choose a theme（选择主题）**或 **Change theme（更改主题）**。 ![选择主题按钮](/assets/images/help/pages/choose-a-theme.png) +4. 在页面顶部单击所需的主题，然后单击 **Select theme（选择主题）**。 ![主题选项和选择主题按钮](/assets/images/help/pages/select-theme.png) +5. 系统可能会提示您编辑站点的 *README.md* 文件。 + - 要稍后编辑该文件，请单击 **Cancel（取消）**。 ![编辑文件时取消链接](/assets/images/help/pages/cancel-edit.png) + - 要立即编辑该文件，请参阅“[编辑仓库中的文件](/articles/editing-files-in-your-repository/)”。 + +您选择的主题将自动应用到仓库中的 Markdown 文件。 要将主题应用到仓库中的 HTML 文件，您需要添加 YAML 前页，以指定每个文件的布局。 更多信息请参阅 Jekyll 网站上的“[前页](https://jekyllrb.com/docs/front-matter/)”。 + +### 延伸阅读 + +- Jekyll 网站上的[主题](https://jekyllrb.com/docs/themes/) diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md new file mode 100644 index 0000000000..fea9239650 --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -0,0 +1,37 @@ +--- +title: 更改 GitHub Pages 站点的可见性 +intro: '您可以通过公开或私下发布站点来管理项目站点的访问控制。' +product: '{% data reusables.gated-features.private-pages %}' +versions: + free-pro-team: '*' +permissions: 拥有仓库管理员权限的人可以更改 {% data variables.product.prodname_pages %} 站点的可见性。 +redirect_from: + - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site +--- + +### 关于 {% data variables.product.prodname_pages %} 站点的访问控制 + +如果您的项目站点是从使用 {% data variables.product.prodname_ghe_cloud %} 的组织拥有的私有或内部仓库发布的，您可以管理站点的访问控制。 通过访问控制，您可以选择将站点公开发布给互联网上的任何人，也可以选择私下发布给对仓库拥有读取权限的人。 私下发布的站点可用于与企业成员分享您的内部文档或知识库。 您无法管理组织站点的访问控制。 有关 {% data variables.product.prodname_pages %} 站点类型的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 + +私下发布的站点与公开发布的站点位于不同的子域中。 这可确保您的 {% data variables.product.prodname_pages %} 站点从发布之日起是安全的： + +- 我们使用 TLS 证书自动保护 `*.pages.github.io` 的每个子域，并强制执行 HSTS 以确保浏览器始终通过 HTTPS 提供页面。 +- 我们对私有页面使用独特的子域，以确保您组织中的其他仓库不能在与私有页面相同的来源发布内容。 这可保护您的私有页面免受“[cookie 抛掷](https://github.blog/2013-04-09-yummy-cookies-across-domains/)”。 这也是为什么我们不在 `github.com` 域上托管 {% data variables.product.prodname_pages %} 站点的原因。 + +您可以在仓库设置的页面选项卡中看到站点独特的子域。 如果您使用配置为以仓库名称为路径来构建站点的静态站点生成器，则在将站点更改为私有站点时可能需要更新静态站点生成器的设置。 更多信息请参阅“[在 {% data variables.product.prodname_pages %} 站点中配置 Jekyll](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)”或静态站点生成器的文档。 + +要为您的私有 {% data variables.product.prodname_pages %} 站点使用更短、更令人难忘的域名，您可以配置自定义域名。 更多信息请参阅“[为 {% data variables.product.prodname_pages %} 站点配置自定义域](/pages/configuring-a-custom-domain-for-your-github-pages-site)”。 + +### 更改 {% data variables.product.prodname_pages %} 站点的可见性 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. 在 "{% data variables.product.prodname_pages %}" 下，选择 **{% data variables.product.prodname_pages %} visibility（可见性）**下拉菜单，然后单击可见性。 ![选择站点可见性的下拉菜单](/assets/images/help/pages/public-or-private-visibility.png) +4. 要查看您已发布的站点，请在“{% data variables.product.prodname_pages %}”下点击您的站点 URL。 ![私下发布站点的 URL](/assets/images/help/pages/click-private-pages-url-to-preview.png) + + {% note %} + + {% data reusables.pages.twenty-minutes-to-publish %} + + {% endnote %} diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md new file mode 100644 index 0000000000..d69a138b30 --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -0,0 +1,38 @@ +--- +title: 配置 GitHub Pages 站点的发布源 +intro: '如果您使用 {% data variables.product.prodname_pages %} 站点的默认发布源，您的站点将自动发布。 您也可以从不同的分支或文件夹发布{% if currentVersion ver_lt "enterprise-server@3.0" %}项目{% endif %}站点。' +redirect_from: + - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-your-github-pages-site + - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: '拥有仓库管理员或维护员权限的人可为 {% data variables.product.prodname_pages %} 站点配置发布源。' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +有关发布源的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)”。 + +### 选择发布源 + +Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@3.0" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@3.0" %} 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 %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +3. 在“{% data variables.product.prodname_pages %}”下，使用 **None（无）**或 **Branch（分支）**下拉菜单选择发布源。 ![用于选择发布源的下拉菜单](/assets/images/help/pages/publishing-source-drop-down.png) +4. （可选）使用下拉菜单选择发布源的文件夹。 ![用于选择发布源文件夹的下拉菜单](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. 单击 **Save（保存）**。 ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png){% else %} +3. 在“{% data variables.product.prodname_pages %}”下，使用 **Source（源）**下拉菜单选择发布源。 ![用于选择发布源的下拉菜单](/assets/images/help/pages/publishing-source-drop-down.png) +{% endif %} + +### {% data variables.product.prodname_pages %} 站点发布问题疑难排解 + +{% data reusables.pages.admin-must-push %} + +如果选择 {% 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/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md new file mode 100644 index 0000000000..68813ccee4 --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: 为 GitHub Pages 站点创建自定义 404 页面 +intro: 您可以自定义在人们尝试访问您站点上不存在的页面时显示的 404 错误页面。 +redirect_from: + - /articles/custom-404-pages/ + - /articles/creating-a-custom-404-page-for-your-github-pages-site + - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +{% data reusables.files.add-file %} +3. 在文件名字段中，键入 `404.html` 或 `404.md`。 ![文件名字段](/assets/images/help/pages/404-file-name.png) +4. 如果将文件命名为 `404.md`，请将以下 YAML 前页添加到文件的开头： + ```yaml + --- + permalink: /404.html + --- + ``` +5. 在 YAML 前页（如果存在）下方添加要在 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 %} + +### 延伸阅读 + +- Jekyll 文档中的[前页](http://jekyllrb.com/docs/frontmatter) diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md new file mode 100644 index 0000000000..d56fcadc11 --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -0,0 +1,63 @@ +--- +title: 创建 GitHub Pages 站点 +intro: '您可以在新仓库或现有仓库中创建 {% data variables.product.prodname_pages %} 站点。' +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 + - /github/working-with-github-pages/creating-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### 为站点创建仓库 + +{% data reusables.pages.new-or-existing-repo %} + +{% 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 %} + +### 创建站点 + +{% data reusables.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.decide-publishing-source %} +3. 如果所选发布源已存在，请导航到发布源。 如果所选发布源不存在，则创建发布源。 +4. 在发布源的根目录中，创建一个名为 `index.md`、包含要在网站主页上显示的内容的文件。 +{% data reusables.pages.configure-publishing-source %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %}{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### 后续步骤 + +您可以通过创建更多新文件向网站添加更多页面。 每个文件都将在网站上与发布源相同的目录结构中。 例如，如果项目网站的发布源是 `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.html` 下。 + +您还可以添加主题以自定义网站的外观。 更多信息请参阅{% 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)”。 + +### 延伸阅读 + +- "[排查 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" +- “[在仓库内创建和删除分支](/articles/creating-and-deleting-branches-within-your-repository)” +- "[创建新文件](/articles/creating-new-files)" diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md new file mode 100644 index 0000000000..eca39351f2 --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md @@ -0,0 +1,26 @@ +--- +title: GitHub Pages 使用入门 +intro: '您可以为自己、您的组织或项目设置一个基本 {% data variables.product.prodname_pages %} 站点。' +redirect_from: + - /categories/github-pages-basics + - /articles/additional-customizations-for-github-pages/ + - /articles/getting-started-with-github-pages + - /github/working-with-github-pages/getting-started-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +{% 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 /changing-the-visibility-of-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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md new file mode 100644 index 0000000000..fe5bd0c7bb --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -0,0 +1,55 @@ +--- +title: 使用 HTTPS 保护 GitHub Pages 站点 +intro: 'HTTPS 增加一层加密，用于防止其他人窥探或篡改您的站点的流量。 您可对 {% data variables.product.prodname_pages %} 站点强制实施 HTTPS，从而将所有 HTTP 请求透明地重定向到 HTTPS。' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/securing-your-github-pages-site-with-https + - /github/working-with-github-pages/securing-your-github-pages-site-with-https +versions: + free-pro-team: '*' +topics: + - 页面 +--- + +拥有仓库管理员权限的人可对 {% data variables.product.prodname_pages %} 站点实施 HTTPS。 + +### 关于 HTTPS 和 {% data variables.product.prodname_pages %} + +所有 {% data variables.product.prodname_pages %} 站点（包括使用自定义域正确配置的站点）均支持 HTTPS 和 HTTPS 强制实施。 有关自定义域的更多信息，请参阅“[关于自定义域和 {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)”以及“[自定义域和 {% data variables.product.prodname_pages %} 疑难解答](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)”。 + +{% data reusables.pages.no_sensitive_data_pages %} + +{% data reusables.pages.private_pages_are_public_warning %} + +### 对您的 {% data variables.product.prodname_pages %} 站点强制实施 HTTPS + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +3. 在 "{% data variables.product.prodname_pages %}" 下，选择 **Enforce HTTPS（实施 HTTPS）**。 ![强制实施 HTTPS 复选框](/assets/images/help/pages/enforce-https-checkbox.png) + +### 解决具有混合内容的问题 + +如果您对 {% data variables.product.prodname_pages %} 站点启用了 HTTPS，但站点的 HTML 仍通过 HTTP 引用图像、CSS 或 JavaScript，则您的站点将提供*混合内容*。 提供混合内容可能会降低站点的安全性，并导致在加载资产时出现问题。 + +要删除站点的混合内容，请在站点的 HTML 中将 `http://` 更改为 `https://`，确保所有资产都通过 HTTPS 提供。 + +资产通常位于以下位置： +- 如果您的站点使用 Jekyll，则 HTML 文件可能位于 *_layouts* 文件夹中。 +- CSS 通常位于 HTML 文件的 `` 部分。 +- JavaScript 通常位于 `` 部分或结束 `` 标记之前。 +- 图像通常位于 `` 部分。 + +{% tip %} + +**提示：**如果您在站点的源文件中找不到您的资产，请尝试在文本编辑器或 {% data variables.product.product_name %} 上搜索站点源文件中的 `http`。 + +{% endtip %} + +#### HTML 文件中引用的资产示例 + +| 前端资源类型 | HTTP | HTTPS | +|:----------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:| +| CSS | `` | `` | +| JavaScript | `` | `` | +| 图像 | `Logo` | `Logo` | diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md new file mode 100644 index 0000000000..6eb86474e1 --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -0,0 +1,35 @@ +--- +title: 取消发布 GitHub Pages 站点 +intro: '您可以取消发布 {% data variables.product.prodname_pages %} 站点，使该站点不再可用。' +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 + - /github/working-with-github-pages/unpublishing-a-github-pages-site +product: '{% data reusables.gated-features.pages %}' +permissions: '拥有仓库管理员或维护员权限的人可取消发布 {% data variables.product.prodname_pages %} 站点。' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +### 取消发布项目站点 + +{% 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" %}跳到步骤 6{% else %}您的站点现已取消发布，您可以跳过其余步骤{% endif %}。 +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. 在“{% data variables.product.prodname_pages %}”下，使用 **Source（源）**下拉菜单并选择 **None（无）**。 ![用于选择发布源的下拉菜单](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} + +### 取消发布用户或组织站点 + +{% data reusables.repositories.navigate-to-repo %} +2. 删除用作发布源的分支，或删除整个仓库。 更多信息请参阅“[在仓库中创建和删除分支](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)”和“[删除仓库](/articles/deleting-a-repository)”。 +{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md new file mode 100644 index 0000000000..ee3ea86dfd --- /dev/null +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -0,0 +1,24 @@ +--- +title: 将子模块用于 GitHub Pages +intro: '您可以将子模块用于 {% data variables.product.prodname_pages %} 以在站点代码中包含其他项目。' +redirect_from: + - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-github-pages + - /github/working-with-github-pages/using-submodules-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' +topics: + - 页面 +--- + +如果 {% data variables.product.prodname_pages %} 站点的仓库包含子模块，则在构建站点时会自动拉取其内容。 + +只能使用指向公共仓库的子模块，因为 {% data variables.product.prodname_pages %} 服务器无法访问私有仓库。 + +对子模块（包括嵌套子模块）使用 `https://` 只读 URL。 您可以在 _.gitmodules_ 文件中进行此更改。 + +### 延伸阅读 + +- _Pro Git_ 手册中的“[Git 工具 - 子模块](https://git-scm.com/book/en/Git-Tools-Submodules)”。 +- "[排查 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/zh-CN/content/pages/index.md b/translations/zh-CN/content/pages/index.md new file mode 100644 index 0000000000..41c3e4fed9 --- /dev/null +++ b/translations/zh-CN/content/pages/index.md @@ -0,0 +1,25 @@ +--- +title: GitHub Pages 文档 +shortTitle: GitHub Pages +intro: '您可以直接从 {% 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 + - /github/working-with-github-pages +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +{% link_with_intro /getting-started-with-github-pages %} +{% link_with_intro /setting-up-a-github-pages-site-with-jekyll %} +{% link_with_intro /configuring-a-custom-domain-for-your-github-pages-site %} \ No newline at end of file diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md new file mode 100644 index 0000000000..5f7cf897c0 --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -0,0 +1,131 @@ +--- +title: 关于 GitHub Pages 和 Jekyll +intro: 'Jekyll 是一个静态站点生成器，内置 {% 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 + - /github/working-with-github-pages/about-github-pages-and-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +### 关于 Jekyll + +Jekyll 是一个静态站点生成器，内置 {% data variables.product.prodname_pages %} 支持和简化的构建过程。 Jekyll 使用 Markdown 和 HTML 文件，并根据您选择的布局创建完整静态网站。 Jekyll 支持 Markdown 和 Lick，这是一种可在网站上加载动态内容的模板语言。 更多信息请参阅 [Jekyll](https://jekyllrb.com/)。 + +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)”。 + +### 在 {% data variables.product.prodname_pages %} 网站中配置 Jekyll + +您可以通过编辑 *_config.yml* 文件来配置大多数 Jekyll 设置，例如网站的主题和插件。 更多信息请参阅 Jekyll 文档中的“[配置](https://jekyllrb.com/docs/configuration/)”。 + +对于 {% data variables.product.prodname_pages %} 站点，有些配置设置不能更改。 + +```yaml +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 +``` + +默认情况下，Jekyll 不会构建以下文件或文件夹： +- 位于文件夹 `/node_modules` 或 `/vendor` 中 +- 开头为 `_`、`.` 或 `#` +- 结尾为 `~` +- 被配置文件中的 `exclude` 设置排除 + +如果您想要 Jekyll 处理其中任何文件，可以使用配置文件中的 `includes` 设置。 + +### 前页附属资料 + +{% data reusables.pages.about-front-matter %} + +您可以添加 `site.github` 到帖子或页面，以将任何仓库引用元数据添加到您的网站。 更多信息请参阅 Jekyll 元数据文档中的“[使用`site.github`](https://jekyll.github.io/github-metadata/site.github/)”。 + +### 主题 + +{% data reusables.pages.add-jekyll-theme %} 更多信息请参阅 Jekyll 文档中的“[主题](https://jekyllrb.com/docs/themes/)”。 + +{% if currentVersion == "free-pro-team@latest" %} +您可以在 {% 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 %} 上托管的任何其他开源 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)“。 + +### 插件 + +您可以下载或创建 Jekyll 插件，以便为您的网站扩展 Jekyll 的功能。 例如， [jemoji](https://github.com/jekyll/jemoji) 插件允许您在站点的任何页面上使用 {% data variables.product.prodname_dotcom %} 风格的表情符号，就像在 {% data variables.product.prodname_dotcom %} 上使用一样。 更多信息请参阅 Jekyll 文档中的“[插件](https://jekyllrb.com/docs/plugins/)”。 + +{% data variables.product.prodname_pages %} 使用默认启用且不能禁用的插件： +- [`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) + +您可以通过在 *_config.yml* 文件中添加插件的 gem 到 `plugins` 设置来启用额外的插件。 更多信息请参阅 Jekyll 文档中的“[配置](https://jekyllrb.com/docs/configuration/)”。 + +有关支持的插件列表，请参阅 {% data variables.product.prodname_pages %} 网站上的“[依赖项版本](https://pages.github.com/versions/)”。 有关特定插件的使用信息，请参阅插件的文档。 + +{% tip %} + +**提示：** 您可以保持更新 {% data variables.product.prodname_pages %} gem，确保使用所有插件的最新版本。 更多信息请参阅 {% data variables.product.prodname_pages %} 网站上的“[使用 Jekyll 本地测试 GitHub Pages 站点](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)”和“[依赖项版本](https://pages.github.com/versions/)”。 + +{% endtip %} + +{% data variables.product.prodname_pages %} 无法使用不支持的插件构建网站。 如果想使用不支持的插件，请在本地生成网站，然后将网站的静态文件推送到 {% data variables.product.product_name %}。 + +### 语法突显 + +为了使网站更容易读取，代码片段在 {% data variables.product.prodname_pages %} 上突显，就像在 {% data variables.product.product_name %} 上突显一样。 有关在 {% data variables.product.product_name %} 上突显语法的更多信息，请参阅“[创建和突显代码块](/articles/creating-and-highlighting-code-blocks)”。 + +默认情况下，网站上的代码块将被 Jekyll 突出显示。 Jekyll 使用 [Rouge](https://github.com/jneen/rouge) 突显工具，它兼容于 [Pygments](http://pygments.org/)。 如果在 *_config.yml* 文件中指定 Pygments，将改用 Rouge。 Jekyll 不能使用任何其他语法突显工具，如果您在 *_config.yml* 文件中指定其他语法突显工具，将会收到页面构建警告。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/about-jekyll-build-errors-for-github-pages-sites)”。 + +如果想使用其他突显工具，如 `highlight.js`，则必须更新项目的 *_config.yml* 文件来禁用 Jekyll 的语法突显。 + +```yaml +kramdown: + syntax_highlighter_opts: + disable : true +``` + +如果您的主题不含用于语法突显的 CSS，可以生成 {% data variables.product.prodname_dotcom %} 的语法突显 CSS 并将其添加到项目的 `style.css` 文件。 + +```shell +$ rougify style github > style.css +``` + +### 本地构建网站 + +{% data reusables.pages.test-locally %} diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..944d4922b6 --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,62 @@ +--- +title: 关于 GitHub Pages 站点的 Jekyll 构建错误 +intro: '如果在本地或 {% data variables.product.product_name %} 上构建 {% data variables.product.prodname_pages %} 站点发生 Jekyll 错误，您将收到一条错误消息，其中包含相关详细信息。' +redirect_from: + - /articles/viewing-jekyll-build-error-messages/ + - /articles/generic-jekyll-build-failures/ + - /articles/about-jekyll-build-errors-for-github-pages-sites + - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +### 关于 Jekyll 构建错误 + +有时，在您推送更改到站点的发布源之后，{% 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 服务的文档。 + +{% note %} + +**注：**对站点的更改在推送到 {% data variables.product.product_name %} 后，最长可能需要 20 分钟才会发布。 + +{% endnote %} + +如果 Jekyll 尝试构建站点但遇到错误，您将收到一条构建错误消息。 Jekyll 构建错误消息有两种主要类型。 +- “Page build warning（页面构建警告）”消息表示构建已成功完成，但您可能需要进行更改以防止将来出现问题。 +- “Page build failed（页面构建失败）”消息表示构建未能完成。 如果 Jekyll 能够检测到失败的原因，您将看到描述性错误消息。 + +有关排查构建错误的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误疑难排解](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)”。 + +### 查看 Jekyll 构建错误消息 + +我们建议在本地测试您的站点，这样您可以在命令行上看到构建错误消息，并在更改推送到 {% data variables.product.product_name %} 之前解决任何构建失败。 更多信息请参阅“[使用 Jekyll 在本地测试 {% data variables.product.prodname_pages %} 站点](/articles/testing-your-github-pages-site-locally-with-jekyll)”。 + +创建拉取请求以更新您在 {% data variables.product.product_name %} 上的发布源时，您可以在拉取请求的 **Checks（检查）**选项卡上看到构建错误消息。 更多信息请参阅“[关于状态检查](/articles/about-status-checks)”。 + +将更改推送到您在 {% data variables.product.product_name %} 上的发布源时，{% data variables.product.prodname_pages %} 将尝试构建您的站点。 如果构建失败，您将在您的主要电子邮件地址收到一封电子邮件。 您还将收到关于构建警告的电子邮件。 {% data reusables.pages.build-failure-email-server %} + +您可以在 {% data variables.product.product_name %} 上站点仓库的 **Settings（设置）**选项卡中查看构建失败（而不是构建警告）。 + +您可以配置第三方服务（例如 [Travis CI](https://travis-ci.org/)）以在每次提交后显示错误消息。 + +1. 如果尚未在发布源的根目录中添加名为 _Gemfile_、包含以下内容的文件，请添加： + ```ruby + source `https://rubygems.org` + gem `github-pages` + ``` + +2. 为您选择的测试服务配置站点仓库。 例如，要使用 [Travis CI](https://travis-ci.org/)，请在发布源的根目录下添加一个名为 _.travis.yml_、包含以下内容的文件： + ```yaml + language: ruby + rvm: + - 2.3 + script: "bundle exec jekyll build" + ``` +3. 您可能需要使用第三方测试服务激活仓库。 更多信息请参阅测试服务的文档。 diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..6513ef5053 --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,71 @@ +--- +title: 使用 Jekyll 向 GitHub Pages 站点添加主题 +intro: 您可以通过添加和自定义主题来个性化 Jekyll 站点。 +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 + - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +拥有仓库写入权限的人员可以使用 Jekyll 将主题添加到 {% data variables.product.prodname_pages %} 网站。 + +{% data reusables.pages.test-locally %} + +### 添加主题 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +2. 导航到 *_config.yml*。 +{% data reusables.repositories.edit-file %} +4. 为主题名称添加新行。 + - 要使用支持的主题，请键入 `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 %} +{% data reusables.files.propose_file_change %} + +### 自定义主题的 CSS + +{% 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. 创建一个名为 _/assets/css/style.scss_ 的新文件。 +2. 在文件顶部添加以下内容： + ```scss + --- + --- + + @import "{{ site.theme }}"; + ``` +3. 在 `@import` 行的后面直接添加您喜欢的任何自定义 CSS 或 Sass（包括导入）。 + +### 自定义主题的 HTML 布局 + +{% data reusables.pages.best-with-supported-themes %} + +{% data reusables.pages.theme-customization-help %} + +1. 在 {% data variables.product.prodname_dotcom %} 上，导航到主题的源仓库。 例如，Minima 的源仓库为 https://github.com/jekyll/minima。 +2. 在 *_layouts* 文件夹中，导航到主题的 _default.html_ 文件。 +3. 复制文件的内容。 +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +6. 创建名为 *_layouts/default.html* 的文件。 +7. 粘贴之前复制的默认布局内容。 +8. 根据需要自定义布局。 + +### 延伸阅读 + +- "[创建新文件](/articles/creating-new-files)" diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..4e83113dab --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md @@ -0,0 +1,72 @@ +--- +title: 使用 Jekyll 向 GitHub Pages 站点添加内容 +intro: '您可以在 {% data variables.product.prodname_pages %} 上向 Jekyll 站点添加新页面或帖子。' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/adding-content-to-your-github-pages-site-using-jekyll + - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +拥有仓库写入权限的人员可以使用 Jekyll 向 {% data variables.product.prodname_pages %} 站点添加内容。 + +### 关于 Jekyll 站点中的内容 + +必须先创建一个 Jekyll 站点，然后才可将内容添加到 {% data variables.product.prodname_pages %} 上的 Jekyll 站点。 更多信息请参阅“[使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点](/articles/creating-a-github-pages-site-with-jekyll)”。 + +Jekyll 站点中内容的主要类型是页面和帖子。 页面是指与某个特定日期没有关联的独立内容，例如“关于”页面。 默认 Jekyll 站点包含一个名为 `about.md` 的文件，在站点的 `YOUR-SITE-URL/about` 下显示为一个页面。 您可以编辑该文件的内容以个性化“关于”页面，也可以使用“关于”页作为模板创建新页面。 更多信息请参阅 Jekyll 文档中的“[页面](https://jekyllrb.com/docs/pages/)”。 + +帖子是博客文章。 默认 Jekyll 站点包含名为 `_posts`、其中包含默认帖子文件的目录。 您可以编辑该帖子的内容，也可以将默认帖子用作模板来创建新帖子。 更多信息请参阅 Jekyll 文档中的“[帖子](https://jekyllrb.com/docs/posts/)”。 + +主题包括默认布局、包含和样式表，它们将自动应用到站点上的新页面和帖子，但您可以覆盖其中任何默认值。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll#themes)”。 + +{% data reusables.pages.about-front-matter %} + +{% data reusables.pages.test-locally %} + +### 向站点添加新页面 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. 在发布源的根目录中，为名为 _PAGE-NAME.md_ 的页面创建新文件，将 _PAGE-NAME_ 替换为对该页面有意义的文件名。 +4. 在文件顶部添加以下 YAML 前页，将 _PAGE TITLE_ 替换为页面的标题，将 _URL-PATH_ 替换为您想要的页面 URL 的路径。 例如，如果站点的基础 URL 是 `https://octocat.github.io`，并且 _URL-PATH_ 是 `/about/contact/`，您的页面将位于 `https://octocat.github.io/about/contact`。 + ```shell + layout: page + title: "PAGE TITLE" + permalink: /URL-PATH/ + ``` +5. 在前页下方，为页面添加内容。 +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} + +### 向站点添加新帖子 + +{% data reusables.pages.navigate-site-repo %} +{% data reusables.pages.navigate-publishing-source %} +3. 导航到 `_posts` 目录。 +4. 创建一个名为 _YYYY-MM-DD-NAME-OF-POST.md_ 的新文件，将 _YYYY-MM-DD_ 替换为帖子的日期，并将 _NAME-OF-POST_ 替换为帖子的名称。 +4. 在文件顶部添加以下 YAML 前页，将 _POST TITLE_ 替换为帖子标题，将 _YYYY-MM-DD hh:mm:ss -0000_ 替换为帖子的日期和时间，将 _CATEGORY-1_ 和 _CATEGORY-2_ 替换为您要为帖子选择的多个类别。 + ```shell + layout: post + title: "POST TITLE" + date: YYYY-MM-DD hh:mm:ss -0000 + categories: CATEGORY-1 CATEGORY-2 + ``` +5. 在前页下方，为帖子添加内容。 +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md new file mode 100644 index 0000000000..0c4ee8fd1a --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -0,0 +1,116 @@ +--- +title: 使用 Jekyll 创建 GitHub Pages 站点 +intro: '您可以使用 Jekyll 在新仓库或现有仓库中创建 {% data variables.product.prodname_pages %} 站点。' +product: '{% data reusables.gated-features.pages %}' +redirect_from: + - /articles/creating-a-github-pages-site-with-jekyll + - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll +permissions: '拥有仓库管理员权限的人员可以使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点。' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +{% data reusables.pages.org-owners-can-restrict-pages-creation %} + +### 基本要求 + +必须安装 Jekyll 和 Git 后才可使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点。 更多信息请参阅 Jekyll 文档中的[安装](https://jekyllrb.com/docs/installation/)和“[设置 Git](/articles/set-up-git)”。 + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### 为站点创建仓库 + +{% data reusables.pages.new-or-existing-repo %} + +{% 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.pages.must-have-repo-first %} + +{% data reusables.pages.private_pages_are_public_warning %} + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. 如果您还没有本地版仓库，请导航到您想要存储站点源文件的位置，将 _PARENT-FOLDER_ 替换为要包含仓库文件夹的文件夹。 + ```shell + $ cd PARENT-FOLDER + ``` +3. 如果尚未初始化本地 Git 仓库，请将 _REPOSITORY-NAME_ 替换为仓库名称。 + ```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. 将目录更改为仓库。 + ```shell + $ cd REPOSITORY-NAME + # Changes the working directory + ``` +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + 例如，如果选择从默认分支上的 `docs` 文件夹发布站点，则创建并切换目录到 `docs` 文件夹。 + ```shell + $ mkdir docs + # Creates a new folder called docs + $ cd docs + ``` + 如果选择从 `gh-pages` 分支发布站点，则创建并检出 `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. 要创建新 Jekyll 站点，请使用 `jekyll new` 命令： + ```shell + $ jekyll new . + # Creates a Jekyll site in the current directory + ``` +8. 打开 Jekyll 创建的 Gemfile 文件。 +1. 将 "#" 添加到以 `gem "jekyll "` 开头的行首，以注释此行。 +1. 编辑以 `# gem "github-pages"` 开头的行来添加 `github-pages` gem。 将此行更改为： + + ```shell + gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins + ``` + + 将 _GITHUB-PAGES-VERSION_ 替换为 `github-pages` gem 的最新支持版本。 您可以在这里找到这个版本：“[依赖项版本](https://pages.github.com/versions/)”。 + + 正确版本 Jekyll 将安装为 `github-pages` gem 的依赖项。 +10. 保存并关闭 Gemfile。 +11. 从命令行运行 `bundle update`。 +11. （可选）在本地测试您的站点。 更多信息请参阅“[使用 Jekyll 在本地测试 {% data variables.product.prodname_pages %} 站点](/articles/testing-your-github-pages-site-locally-with-jekyll)”。 +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 +{% else %} +$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git +{% endif %} +``` +13. 将仓库推送到 {% data variables.product.product_name %}，_BRANCH_ 替换为您所操作的分支的名称。 + ```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.sidebar-pages %} +{% if currentVersion == "free-pro-team@latest" %} +{% data reusables.pages.choose-visibility %}{% endif %} +{% data reusables.pages.visit-site %} + +{% data reusables.pages.admin-must-push %} + +### 后续步骤 + +要向站点添加新页面或帖子，请参阅“[使用 Jekyll 添加内容到 {% data variables.product.prodname_pages %} 站点](/articles/adding-content-to-your-github-pages-site-using-jekyll)”。 + +{% 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/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md new file mode 100644 index 0000000000..f87bdd6502 --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md @@ -0,0 +1,25 @@ +--- +title: 使用 Jekyll 设置 GitHub Pages 站点 +intro: '您可以使用流行的静态站点生成器 Jekyll 进一步自定义 {% 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 + - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +{% 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 %} \ No newline at end of file diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md new file mode 100644 index 0000000000..480fe1a91c --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -0,0 +1,36 @@ +--- +title: 使用 Jekyll 为 GitHub Pages 站点设置 Markdown 处理器 +intro: '您可以选择一个 Markdown 处理器来确定 Markdown 在 {% 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 + - /github/working-with-github-pages/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: '*' +topics: + - 页面 +--- + +拥有仓库写入权限的人可为 {% data variables.product.prodname_pages %} 站点设置 Markdown 处理器。 + +{% 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 %} 上看到的结果相匹配。 + +{% data reusables.pages.navigate-site-repo %} +2. 在仓库中，浏览到 *_config.yml* 文件。 +{% data reusables.repositories.edit-file %} +4. 找到以 `markdown:` 开头的行，然后将值更改为 `kramdown` 或 `GFM`。 ![config.yml 中的 Markdown 设置](/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 %} + +### 延伸阅读 + +- [kramdown 文档](https://kramdown.gettalong.org/documentation.html) +- [{% data variables.product.prodname_dotcom %} Flavored Markdown 规格](https://github.github.com/gfm/) diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md new file mode 100644 index 0000000000..b527229000 --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -0,0 +1,62 @@ +--- +title: 使用 Jekyll 在本地测试 GitHub Pages 站点 +intro: '您可以在本地构建 {% data variables.product.prodname_pages %} 站点，以预览和测试对站点的更改。' +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 + - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +任何拥有仓库读取权限的人都可以在本地测试 {% data variables.product.prodname_pages %} 站点。 + +### 基本要求 + +在使用 Jekyll 测试站点之前，您必须： + - 安装 [Jekyll](https://jekyllrb.com/docs/installation/)。 + - 创建一个 Jekyll 站点。 更多信息请参阅“[使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点](/articles/creating-a-github-pages-site-with-jekyll)”。 + +{% data reusables.pages.recommend-bundler %} + +{% data reusables.pages.jekyll-install-troubleshooting %} + +### 本地构建网站 + +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.pages.navigate-publishing-source %} +3. 运行 `bundle install`。 +3. 在本地运行您的 Jekyll 站点。 + ```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. 要预览站点，请在 web 浏览器中导航到 `http://localhost:4000`。 + +### 更新 {% data variables.product.prodname_pages %} gem + +Jekyll 是一个活跃的开源项目，经常更新。 如果您计算机上的 `github-pages` gem 版本落后于 {% data variables.product.prodname_pages %} 服务器上的 `github-pages` gem 版本，则您的站点在本地构建时的外观与在 {% data variables.product.product_name %} 上发布时的外观可能不同。 为避免这种情况，请定期更新计算机上的 `github-pages` gem。 + +{% data reusables.command_line.open_the_multi_os_terminal %} +2. 更新 `github-pages` gem。 + - 如果您安装了 Bundler，请运行 `bundle update github-pages`。 + - 如果未安装 Bundler，则运行 `gem update github-pages`. + +### 延伸阅读 + +- Jekyll 文档中的 [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md new file mode 100644 index 0000000000..e3a5555e3e --- /dev/null +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -0,0 +1,191 @@ +--- +title: 排查 GitHub Pages 站点的 Jekyll 构建错误 +intro: '您可以使用 Jekyll 构建错误消息来排查 {% 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 + - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites +product: '{% data reusables.gated-features.pages %}' +versions: + free-pro-team: '*' + enterprise-server: '*' + github-ae: '*' +topics: + - 页面 +--- + +### 排查构建错误 + +如果在本地或 {% 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)”。 + +如果您收到一般错误消息，请检查常见问题。 +- 您使用的插件不受支持。 更多信息请参阅“[关于 {% 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 %} 在构建过程中会覆盖此设置。 +- 发布源中的文件名包含不受支持的冒号 (`:`)。 + +如果您收到特定的错误消息，请查看下面的错误消息疑难解答信息。 + +修复任何错误后，请将更改推送到站点的发布源，以触发 {% data variables.product.product_name %} 上的再次构建。 + +### Config 文件错误 + +此错误意味着 *_config.yml* 文件包含语法错误导致您的站点无法构建。 + +要排除故障，请确保 *_config.yml* 文件遵循以下规则： + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +### 日期不是有效的日期时间 + +此错误意味着站点上的某个页面包含无效的日期时间。 + +要排除故障，请搜索错误消息中的文件和文件布局，以调用任何与日期相关的 Liquid 过滤器。 确保在所有情况下传递给日期相关 Liquid 过滤器的任何变量都有值，并且永远不会传递 `nil` 或 `""`。 更多信息请参阅 Liquid 文档中的“[Liquid 过滤器](https://help.shopify.com/en/themes/liquid/filters)”。 + +### 文件在包含目录中不存在 + +此错误意味着您的代码引用了 *_includes* 目录中不存在的文件。 + +{% data reusables.pages.search-for-includes %} 如果您引用的任何文件不在 *_includes* 目录中，请将这些文件复制或移动到 *_includes* 目录中。 + +### 文件是符号链接 + +此错误意味着您的代码引用了站点发布源中不存在的符号链接文件。 + +{% data reusables.pages.search-for-includes %} 如果您引用的任何文件是符号链接的文件，请将这些文件复制或移动到 *_includes* 目录中。 + +### 文件未采用正确的 UTF-8 编码 + +此错误意味着您使用了非拉丁字符（如 `日本語`）但没有告诉计算机预期这些符号。 + +要排除故障，请将以下行添加到 *_config.yml* 文件以实施 UTF-8 编码： +```yaml +encoding: UTF-8 +``` + +### 高亮插件语言无效 + +此错误意味着您在配置文件中指定了 [Rouge](https://github.com/jneen/rouge) 或 [Pygments](http://pygments.org/) 以外的任何语法高亮插件。 + +要排除故障，请更新 *_config.yml* 文件以指定 [Rouge](https://github.com/jneen/rouge) 或 [Pygments](http://pygments.org/)。 更多信息请参阅“[关于 {% data variables.product.product_name %} 和 Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)”。 + +### 帖子日期无效 + +此错误意味着站点上的帖子在文件名或 YAML 前页中包含无效的日期。 + +要排除故障，请确保所有日期的 UTC 格式均为 YYYY-MM-DD HH:MM:SS， 并且都是实际日历日期。 要指定与 UTC 偏移的时区，请使用格式 YYYY-MM-DD HH:MM:SS +/-TTTT，例如 `2014-04-18 11:30:00 +0800`。 + +如果您在 *_config.yml* 文件中指定日期格式，请确保格式正确。 + +### Sass 或 SCSS 无效 + +此错误意味着您的仓库包含内容无效的 Sass 或 SCSS 文件。 + +要排除故障，请查看指示 Sass 或 SCSS 无效的错误消息中包含的行号。 为防止以后出错，请在您的常用文本编辑器中安装 Sass 或 SCSS 语法检查插件。 + +### 子模块无效 + +此错误意味着您的仓库包含尚未正确初始化的子模块。 + +{% data reusables.pages.remove-submodule %} + +如果要使用子模块，请确保在引用子模块时使用 `https://`（而不是 `http://`），并确保该子模块在公共仓库中。 + +### 数据文件中的 YAML 无效 + +此错误意味着 *_data* 文件夹中的一个或多个文件包含无效的 YAML。 + +要排除故障，请确保 *_data* 文件夹中的 YAML 文件遵循以下规则： + +{% data reusables.pages.yaml-rules %} + +{% data reusables.pages.yaml-linter %} + +有关 Jekyll 数据文件的更多信息，请参阅 Jekyll 文档中的“[数据文件](https://jekyllrb.com/docs/datafiles/)”。 + +### Markdown 错误 + +此错误意味着您的仓库包含 Markdown 错误。 + +要排除故障，请确保使用受支持的 Markdown 处理器。 更多信息请参阅“[使用 Jekyll 为 {% data variables.product.prodname_pages %} 站点设置 Markdown 处理器](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)”。 + +然后，确认错误消息中的文件使用有效的 Markdown 语法。 更多信息请参阅 Daring Fireball 上的“[Markdown：语法](https://daringfireball.net/projects/markdown/syntax)”。 + +### 缺少 docs 文件夹 + +此错误意味着您已选择分支上的 `docs` 文件夹作为发布源，但该分支上仓库的根目录中没有 `docs` 文件夹。 + +要排除故障，如果 `docs` 文件夹被意外移动，请尝试将 `docs` 文件夹移回到您为发布源所选分支上仓库的根目录中。 如果 `docs` 文件夹被意外删除，您执行以下任一操作： +- 使用 Git 还原或撤消删除。 更多信息请参阅 Git 文档中的“[git-revert](https://git-scm.com/docs/git-revert.html)”。 +- 在您为发布源所选分支上仓库的根目录中创建新的 `docs` 文件夹，然后将站点的源文件添加到该文件夹中。 更多信息请参阅“[创建新文件](/articles/creating-new-files)”。 +- 更改发布源。 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages)”。 + +### 缺少子模块 + +此错误意味着您的仓库包含不存在或尚未正确初始化的子模块。 + +{% data reusables.pages.remove-submodule %} + +如果要使用子模块，请初始化子模块。 更多信息请参阅 _Pro Git_ 手册中的“[Git 工具 - 子模块](https://git-scm.com/book/en/v2/Git-Tools-Submodules)”。 + +### 配置了相对永久链接 + +此错误意味着您的 *_config.yml* 文件中存在 {% data variables.product.prodname_pages %} 不支持的相对永久链接。 + +永久链接是引用站点上特定页面的永久 URL。 绝对永久链接以站点的根目录开头，而相对永久链接以包含引用页面的文件夹开头。 {% data variables.product.prodname_pages %} 和 Jekyll 不再支持相对永久链接。 有关永久链接的更多信息，请参阅 Jekyll 文档中的“[永久链接](https://jekyllrb.com/docs/permalinks/)”。 + +要排除故障，请从 *_config.yml* 文件中删除 `relative_permalinks` 行，并将站点中的任何相对永久链接重新格式化为绝对永久链接。 更多信息请参阅“[编辑仓库中的文件](/articles/editing-files-in-your-repository)”。 + +### 符号链接不存在于站点的仓库中 + +此错误意味着您的站点包含站点发布源中不存在的符号链接。 有关符号链接的更多信息，请参阅维基百科上的“[符号链接](https://en.wikipedia.org/wiki/Symbolic_link)”。 + +要排除故障，请确定错误消息中的文件是否用于构建站点。 如果否，或者您不希望文件成为符号链接，请删除该文件。 如果符号链接文件是构建站点的必需项，请确保符号链接引用的文件或目录存在于站点的发布源中。 要包括外部资产，请考虑使用 {% 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' 循环中的语法错误 + +此错误意味着您的代码在 Liquid `for` 循环声明中包含无效语法。 + +要排除故障，请确保错误消息所指文件中的所有 `for` 循环都具有正确的语法。 有关 `for` 循环之正确语法的更多信息，请参阅 Liquid 文档中的“[迭代标记](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)”。 + +### 标记未正确关闭 + +此错误消息意味着您的代码包含未正确关闭的逻辑标记。 例如，{% raw %}`{% capture example_variable %}` 必须用 `{% endcapture %}`{% endraw %} 关闭。 + +要排除故障，请确保错误消息所指文件中的所有逻辑标记都正确关闭。 更多信息请参阅 Liquid 文档中的“[Liquid 标记](https://help.shopify.com/en/themes/liquid/tags)”。 + +### 标记未正确终止 + +此错误意味着您的代码包含未正确终止的输出标记。 例如，用 {% raw %}`{{ page.title }` 代替 `{{ page.title }}`{% endraw %}。 + +要排除故障，请确保错误消息所指文件中的所有输出标记都用 `}}` 终止。 更多信息请参阅 Liquid 文档中的“[Liquid 对象](https://help.shopify.com/en/themes/liquid/objects)”。 + +### 未知标记错误 + +此错误意味着您的代码包含无法识别的 Liquid 标记。 + +要排除故障，请确保错误消息所指文件中的所有 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/rest/guides/basics-of-authentication.md b/translations/zh-CN/content/rest/guides/basics-of-authentication.md index f26ce95e39..eda125aa80 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: Basics of authentication -intro: Learn about the different ways to authenticate with some examples. +title: 身份验证基础知识 +intro: 通过一些示例了解几种不同的身份验证方法。 redirect_from: - /guides/basics-of-authentication - /v3/guides/basics-of-authentication @@ -9,39 +9,32 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- -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. +在本节中，我们将重点介绍身份验证的基础知识。 具体来说，我们将创建一个 Ruby 服务器（使用 [Sinatra][Sinatra])， 以几种不同的方式实现应用程序的 [web 流][webflow]。 {% tip %} -You can download the complete source code for this project [from the platform-samples repo](https://github.com/github/platform-samples/tree/master/api/). +您可以[从平台样本仓库](https://github.com/github/platform-samples/tree/master/api/)下载此项目的完整源代码。 {% endtip %} -### Registering your app +### 注册您的应用程序 -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. +首先，您需要注册[您的应用程序][new oauth app]。 每个注册的 OAuth 应用程序都被分配了一个唯一的客户端 ID 和客户端密钥。 不应共享客户端密钥！ 也不应将该字符串检入您的仓库。 -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. +您可以根据喜好填写任何信息，但**授权回调 URL** 除外。 这往往是设置应用程序中最重要的部分。 它是在身份验证成功后，{% data variables.product.product_name %} 将用户返回到的回调 URL。 -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`. +由于我们运行常规的 Sinatra 服务器，因此本地实例的位置设置为 `http://localhost:4567`。 回调 URL 应填写为 `http://localhost:4567/callback`。 -### Accepting user authorization +### 接受用户授权 {% data reusables.apps.deprecating_auth_with_query_parameters %} -Now, let's start filling out our simple server. Create a file called _server.rb_ and paste this into it: +现在开始设置我们简单的服务器。 创建一个名为 _server.rb_ 的文件并将以下代码粘贴到其中： ``` ruby require 'sinatra' @@ -56,12 +49,12 @@ get '/' do end ``` -Your client ID and client secret keys come from [your application's configuration -page][app settings].{% if currentVersion == "free-pro-team@latest" %} You should **never, _ever_** store these values in -{% data variables.product.product_name %}--or any other public place, for that matter.{% endif %} We recommend storing them as -[environment variables][about env vars]--which is exactly what we've done here. +客户端 ID 和客户端密钥[来自应用程序的配置页面][app settings]。 +{% if currentVersion == "free-pro-team@latest" %} **永远_不要_**将该事项的这些值存储在 +{% data variables.product.product_name %} 中或任何其他公共的地方。{% endif %} 建议将它们存储为 +[环境变量][about env vars]--我们正是这样做的。 -Next, in _views/index.erb_, paste this content: +接下来，在 _views/index.erb_ 中粘贴此内容： ``` erb @@ -82,26 +75,19 @@ Next, in _views/index.erb_, paste this content: ``` -(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra guide].) +（如果您不熟悉 Sinatra 的工作方式，建议您阅读 [ Sinatra 指南][Sinatra guide]）。 -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. +另请注意，URL 使用 `scope` 查询参数来定义应用程序请求的[作用域][oauth scopes]。 对于我们的应用程序，我们请求 `user:email` 作用域来读取私密电子邮件地址。 -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) +将浏览器导航到 `http://localhost:4567`。 单击链接后，您应该会转到 {% data variables.product.product_name %}，并显示如下所示的对话框： ![GitHub 的 OAuth 提示](/assets/images/oauth_prompt.png) -If you trust yourself, click **Authorize App**. Wuh-oh! Sinatra spits out a -`404` error. What gives?! +如果您觉得没问题，请单击 **Authorize App（授权应用程序）**。 哇！ Sinatra 弹出 `404` 错误。 是什么原因呢？ -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! +哦，还记得我们指定了一个回调 URL 用于 `callback` 吗？ 我们没有为它提供路由，因此 {% data variables.product.product_name %} 在用户授权应用程序后不知道将他们带去哪里。 现在我们来解决这个问题！ -#### Providing a callback +#### 提供回调 -In _server.rb_, add a route to specify what the callback should do: +在 _server.rb_ 中，添加路由以指定回调应执行的操作： ``` ruby get '/callback' do @@ -120,18 +106,13 @@ get '/callback' do end ``` -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]. +在应用程序身份验证成功后，{% data variables.product.product_name %} 将提供一个临时的 `code` 值。 您需要将此代码 `POST` 到 {% data variables.product.product_name %} 以换取 `access_token`。 为了简化我们的 GET 和 POST HTTP 请求，我们使用 [rest-client][REST Client]。 请注意，您可能永远不会通过 REST 访问 API。 对于更重要的应用程序，您可能需要使用[一个用您选择的语言编写的库][libraries]。 -#### Checking 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)." +用户可以通过直接更改 URL 来编辑您请求的范围。 这可以授予您的应用程序比您最初请求的更少的访问权限。 因此，在使用令牌发出任何请求之前，您应该检查用户为令牌授予的作用域。 有关请求和授予的范围的更多信息，请参阅“[OAuth 应用程序的范围](/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 @@ -145,34 +126,17 @@ get '/callback' do end ``` -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. +在我们的应用程序中，我们使用 `scopes.include?` 来检查我们是否被授予获取经验证用户的私密电子邮件地址所需的 `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. +此外，由于作用域之间存在层次关系，因此您应该检查您是否被授予了最低层级的必需作用域。 例如，如果应用程序请求了 `user` 作用域，但可能只被授予 `user:email` 作用域。 在这种情况下，应用程序并未获得它要求的作用域，不过被授予的作用域仍是足够的。 -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 调用可能会以 `404` 或 `401` 状态失败，或者返回不同的信息子集。 -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. +为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 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 %} 的端点。 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 -#### 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 @@ -189,7 +153,7 @@ end erb :basic, :locals => auth_result ``` -We can do whatever we want with our results. In this case, we'll just dump them straight into _basic.erb_: +我们可以用我们的结果做任何我们想做的事。 在这种情况下，我们将它们直接转储到 _basic.erb_ 中： ``` erb

Hello, <%= login %>!

@@ -208,29 +172,19 @@ We can do whatever we want with our results. In this case, we'll just dump them

``` -### Implementing "persistent" authentication +### 实现“持久”身份验证 -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. +如果我们要求用户每次访问网页时都必须登录应用程序，这将是一个非常糟糕的模式。 例如，尝试直接导航到 `http://localhost:4567/basic`。 您会收到一个错误。 -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_. +如果我们能够绕过整个 “点击这里”过程会怎么样：只需_记住_，只要用户登录到 +{% data variables.product.product_name %}，他们就应该能够访问此应用程序？ 不用担心， +因为_这正是我们要做的_。 -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. +我们的上述小服务器相当简单。 为了加入一些智能身份验证功能，我们将切换到使用会话来存储令牌。 这将使身份验证对用户透明化。 -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. +此外，由于我们在会话中保留作用域，因此我们需要处理用户在经过我们检查后更新作用域或撤消令牌的情况。 为此，我们将使用 `rescue` 块，并检查第一个 API 调用是否成功，以验证令牌是否仍然有效。 后，我们将检查 `X-OAuth-Scopes` 响应标头，以验证用户是否尚未撤消 `user:email` 作用域。 -Create a file called _advanced_server.rb_, and paste these lines into it: +创建一个名为 _advanced_server.rb_ 的文件，并将以下行粘贴到其中： ``` ruby require 'sinatra' @@ -310,15 +264,11 @@ get '/callback' do end ``` -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`). +许多代码应该看起来很熟悉。 例如，我们仍使用 `RestClient.get` 来调用 {% data variables.product.product_name %} API，仍将结果传递到 ERB 模板（在此处被称为 `advanced.erb`）中进行呈现。 -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. +此外，我们现在采用 `authenticated?` 方法来检查用户是否已通过身份验证。 如果否，则调用 `authenticate!` 方法，该方法执行 OAuth 流并使用授予的令牌和作用域更新会话。 -Next, create a file in _views_ called _advanced.erb_, and paste this markup into it: +接下来，在名为 _advanced.erb_ 的_视图_中创建一个文件，并将以下标记粘贴到其中： ``` erb @@ -343,18 +293,11 @@ Next, create a file in _views_ called _advanced.erb_, and paste this markup into ``` -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_. +从命令行调用 `ruby advanced_server.rb`，这将在端口 `4567`（即我们用于简单 Sinatra 应用程序的端口）上启动服务器。 当您导航到 `http://localhost:4567` 时，应用程序会调用 `authenticate!` 将您重定向到 `/callback`。 然后，`/callback` 将我们送回 `/`，由于我们已通过身份验证，因此将呈现 _advanced.erb_。 -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 %} 中的回调 URL 更改为 `/` 即可完全简化此往返路由。 但是，由于 _server.rb_ 和 _advanced.rb_ 都依赖于相同的回调 URL，因此我们必须费一点力气使其行之有效。 -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. +此外，如果我们从未授权此应用程序访问我们的 {% data variables.product.product_name %} 数据，我们会在早期的弹出和警告窗口中看到相同的确认对话框。 [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ [Sinatra]: http://www.sinatrarb.com/ @@ -363,6 +306,6 @@ we would've seen the same confirmation dialog from earlier pop-up and warn us. [REST Client]: https://github.com/archiloque/rest-client [libraries]: /libraries/ [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 +[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/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md index d320f4f9d6..2efc24b09b 100644 --- a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md @@ -170,7 +170,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap 同样，我们可以查看[经身份验证用户的仓库][user repos api]： ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/user/repos ``` @@ -207,7 +207,7 @@ $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=own 我们需要 `POST` 一些包含详细信息和配置选项的JSON。 ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ -d '{ \ "name": "blog", \ "auto_init": true, \ @@ -242,7 +242,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog 与 github.com 一样，API 为经过身份验证的用户提供了一些查看议题的方法。 要 [查看您的所有议题][get issues api]，请调用 `GET /issues`： ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/issues ``` @@ -250,7 +250,7 @@ $ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ /orgs//issues`： ```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ +$ curl -i -H "Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \ {% data variables.product.api_url_pre %}/orgs/rails/issues ``` @@ -283,7 +283,7 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues 要创建议题，我们需要进行身份验证，因此我们将在标头中传递 OAuth 令牌。 此外，我们还将 JSON 正文中的标题、正文和标签传递到要在其中创建议题的仓库下的 `/issues` 路径： ```shell -$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ +$ curl -i -H 'Authorization: token {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \ $ -d '{ \ $ "title": "New logo", \ $ "body": "We should have one", \ diff --git a/translations/zh-CN/content/rest/overview/other-authentication-methods.md b/translations/zh-CN/content/rest/overview/other-authentication-methods.md index e641de8216..fcb65f0f46 100644 --- a/translations/zh-CN/content/rest/overview/other-authentication-methods.md +++ b/translations/zh-CN/content/rest/overview/other-authentication-methods.md @@ -1,88 +1,80 @@ --- -title: Other authentication methods -intro: You can use basic authentication for testing in a non-production environment. +title: 其他身份验证方法 +intro: 您可以在非生产环境中使用基本身份验证进行测试。 redirect_from: - /v3/auth versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -While the API provides multiple methods for authentication, we strongly -recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) for production applications. The other -methods provided are intended to be used for scripts or testing (i.e., cases -where full OAuth would be overkill). Third party applications that rely on -{% data variables.product.product_name %} for authentication should not ask for or collect {% data variables.product.product_name %} credentials. -Instead, they should use the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). +虽然 API 提供多种身份验证方法，但我们强烈建议对生产应用程序使用 [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)。 提供的其他方法旨在用于脚本或测试（即没有必要使用完整 OAuth 方法的情况）。 依赖 +{% data variables.product.product_name %} 进行身份验证的第三方应用程序不应要求或收集 {% data variables.product.product_name %} 凭据。 +它们应该使用 [OAuth web 工作流程](/apps/building-oauth-apps/authorizing-oauth-apps/)。 {% endif %} {% if currentVersion == "github-ae@latest" %} -To authenticate we recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) tokens, such a personal access token through the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). +要验证身份，我们建议使用 [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) 令牌，这种个人访问令牌通过 [OAuth web 流程](/apps/building-oauth-apps/authorizing-oauth-apps/)验证。 {% endif %} -### Basic Authentication +### 基本身份验证 -The API supports Basic Authentication as defined in -[RFC2617](http://www.ietf.org/rfc/rfc2617.txt) with a few slight differences. -The main difference is that the RFC requires unauthenticated requests to be -answered with `401 Unauthorized` responses. In many places, this would disclose -the existence of user data. Instead, the {% data variables.product.product_name %} API responds with `404 Not Found`. -This may cause problems for HTTP libraries that assume a `401 Unauthorized` -response. The solution is to manually craft the `Authorization` header. +API 支持在 [RFC2617](http://www.ietf.org/rfc/rfc2617.txt) 中定义的基本身份验证，但有一些细微区别。 主要区别在于 RFC 要求使用 `401 Unauthorized` 响应来回复未经验证的请求。 在很多情况下这会暴露用户数据的存在。 对于此类请求，{% data variables.product.product_name %} API 的响应是 `404 Not Found`。 这可能导致 HTTP 库假定返回 `401 Unauthorized` 的问题。 解决方案是手动创建 `Authorization` 标头。 -#### Via OAuth and personal access tokens +#### 通过 OAuth 和个人访问令牌 -We recommend you use OAuth tokens to authenticate to the GitHub API. OAuth tokens include [personal access tokens][personal-access-tokens] and enable the user to revoke access at any time. +我们建议您使用 OAuth 令牌向 GitHub API 验证。 OAuth 令牌包含[个人访问令牌][personal-access-tokens]，允许用户随时撤销访问权限。 ```shell $ curl -u username:token {% data variables.product.api_url_pre %}/user ``` -This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. +如果您的工具只支持基本身份验证，但您想要利用 OAuth 访问令牌的安全功能，这个方法非常有用。 -#### Via username and password +#### 通过用户名和密码 {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% data variables.product.prodname_dotcom %} API with an API token, such as an OAuth access token, GitHub App installation access token, or personal access token, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)." - +**注意：**自 2020 年 11 月 13 日开始，对于所有 {% data variables.product.prodname_dotcom_the_website %} 帐户（包括 {% data variables.product.prodname_free_user %}、{% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %} 计划上的帐户），{% data variables.product.prodname_dotcom %} 已停止对 API 的密码验证。 现在，您必须使用 API 令牌（如 OAuth 访问令牌、GitHub 应用程序安装访问令牌或个人访问令牌，具体取决于您需要使用令牌执行的操作）向 {% data variables.product.prodname_dotcom %} API 验证。 更多信息请参阅“[疑难排解](/rest/overview/troubleshooting#basic-authentication-errors)”。 + {% endnote %} {% endif %} {% if enterpriseServerVersions contains currentVersion %} -To use Basic Authentication with the {% data variables.product.product_name %} API, simply send the username and -password associated with the account. +要将基本身份验证用于 +{% data variables.product.product_name %} API，只需发送帐户相关的用户名和 +密码。 -For example, if you're accessing the API via [cURL][curl], the following command -would authenticate you if you replace `` with your {% data variables.product.product_name %} username. -(cURL will prompt you to enter the password.) +例如，如果您通过 [cURL][curl] 访问 API，则将 `` 替换为您的 {% data variables.product.product_name %} 用户名后，以下命令将对您进行身份验证。 （cURL 将提示您输入密码。） ```shell $ curl -u username {% data variables.product.api_url_pre %}/user ``` -If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). +如果您启用了双重身份验证，请务必了解如何[使用双重身份验证](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -#### Authenticating for SAML SSO +#### SAML SSO 身份验证 {% note %} -**Note:** Integrations and OAuth applications that generate tokens on behalf of others are automatically authorized. +**注：**代表其他工具生成令牌的集成和 OAuth 应用程序将自动获得授权。 {% endnote %} -If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a personal access token (PAT) and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization. +如果您要使用 API 访问实施 [SAML SSO][saml-sso] 身份验证的组织，您需要创建个人访问令牌 (PAT) 并[授权该令牌][allowlist]访问组织。 访问 `X-GitHub-SO` 中指定的 URL 以授权令牌访问组织。 ```shell $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test @@ -94,7 +86,7 @@ $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api } ``` -When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your personal access token: +在请求可能来自多个组织的数据时（例如，[请求由用户创建的议题列表][user-issues]），`X-GitHub-SSO` 标头将指示哪些组织需要您授权个人访问令牌： ```shell $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/user/issues @@ -102,26 +94,26 @@ $ curl -v -H "Authorization: token TOKEN" {% data variables.product.api > X-GitHub-SSO: partial-results; organizations=21955855,20582480 ``` -The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your personal access token. +`organizations` 的值是需要您授权个人访问令牌的组织列表，用逗号分隔。 {% endif %} {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -### Working with two-factor authentication +### 使用双重身份验证 -When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a personal access token{% if enterpriseServerVersions contains currentVersion %} or OAuth token instead of your username and password{% endif %}. +启用双重身份验证后，REST API 中_大多数_端点的[基本身份验证](#basic-authentication)均要求您使用个人访问令牌{% if enterpriseServerVersions contains currentVersion %} 或 OAuth 令牌，而不是用户名和密码{% endif %}。 -You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% if enterpriseServerVersions contains currentVersion %} or with the "[Create a new authorization][/rest/reference/oauth-authorizations#create-a-new-authorization]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% data variables.product.prodname_dotcom %} API.{% if enterpriseServerVersions contains currentVersion %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} +您可以使用 [{% data variables.product.product_name %}开发者设置{% endif %}来生成新的个人访问令牌，{% if enterpriseServerVersions contains currentVersion %}或者使用 OAuth 授权 API 中的“\[创建新授权\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]”](https://github.com/settings/tokens/new)端点来生成新的 OAuth 令牌{% endif %}。 更多信息请参阅“[创建用于命令行的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)”。 然后，您将使用这些令牌以通过 {% data variables.product.prodname_dotcom %} API [使用 OAuth 令牌进行身份验证][oauth-auth]。{% if enterpriseServerVersions contains currentVersion %} 仅当您创建 OAuth 令牌或使用 OAuth 授权 API 时才需要通过用户名和密码进行身份验证。{% endif %} {% endif %} {% if enterpriseServerVersions contains currentVersion %} -#### Using the OAuth Authorizations API with two-factor authentication +#### 结合使用 OAuth 授权 API 与双重身份验证 -When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code: +当您调用 OAuth 授权 API 时，基本身份验证会要求您使用一次性密码 (OTP) 以及您的用户名和密码，而不是令牌。 当您尝试使用 OAuth 授权 API 进行身份验证时，服务器将响应 `401 Unauthorized` 和以下标头之一，以指示需要使用双重身份验证代码： -`X-GitHub-OTP: required; SMS` or `X-GitHub-OTP: required; app`. +`X-GitHub-OTP: required; SMS` 或 `X-GitHub-OTP: required; app`. -This header tells you how your account receives its two-factor authentication codes. Depending how you set up your account, you will either receive your OTP codes via SMS or you will use an application like Google Authenticator or 1Password. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." Pass the OTP in the header: +此标头指示您的帐户如何接收其双重身份验证代码。 您将通过 SMS 接收 OTP 代码，或者使用 Google Authenticator 或 1Password 等应用程序，具体取决于您的帐户设置。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。 在标头中传递 OTP： ```shell $ curl --request POST \ @@ -137,6 +129,5 @@ $ curl --request POST \ [oauth-auth]: /rest#authentication [personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line [saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on -[saml-sso-tokens]: https://github.com/settings/tokens [allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on [user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user diff --git a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md index 812762ce3b..b88d058900 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,34 +1,35 @@ --- -title: Resources in the REST API -intro: 'Learn how to navigate the resources provided by the {% data variables.product.prodname_dotcom %} API.' +title: REST API 中的资源 +intro: '了解如何导航 {% data variables.product.prodname_dotcom %} API 提供的资源。' redirect_from: - /rest/initialize-the-repo/ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +topics: + - api --- -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 %}. +本文介绍构成官方 {% data variables.product.product_name %} REST API 的资源。 如果您有任何问题或要求，请联系 {% data variables.contact.contact_support %}。 -### Current 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). +默认情况下，对 `{% data variables.product.api_url_code %}` 的所有请求都会收到 REST API 的 **v3** [版本](/developers/overview/about-githubs-apis)。 我们建议您[通过 `Accept` 标头明确请求此版本](/rest/overview/media-types#request-specific-version)。 Accept: application/vnd.github.v3+json {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} -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)." +有关 GitHub GraphQL API 的信息，请参阅 [v4 文档](/graphql)。 有关迁移到 GraphQL 的信息，请参阅“[从 REST 迁移](/graphql/guides/migrating-from-rest-to-graphql)”。 {% endif %} -### Schema +### 架构 -{% 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. +{% if currentVersion == "free-pro-team@latest" %}所有 API 访问都通过 HTTPS 进行，{% else %}API{% endif %} 从 `{% data variables.product.api_url_code %}` 访问。 所有数据都 +作为 JSON 发送和接收。 ```shell $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs @@ -50,55 +51,43 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > X-Content-Type-Options: nosniff ``` -Blank fields are included as `null` instead of being omitted. +空白字段作为 `null` 包含在其中，而不是被忽略。 -All timestamps return in ISO 8601 format: +所有时间戳以 ISO 8601 格式返回： YYYY-MM-DDTHH:MM:SSZ -For more information about timezones in timestamps, see [this section](#timezones). +有关时间戳中时区的更多信息，请参阅[此节](#timezones)。 -#### Summary representations +#### 摘要表示 -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.) +当您获取资源列表时，响应包括该资源的属性_子集_。 这就是资源的“摘要”表示。 （对于某些属性，API 要经过大量计算后才可提供。 出于性能考虑，摘要表示排除了这些属性。 要获得这些属性，请获取“详细”表示。) -**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: +**示例**：当您获取仓库列表时，您将获得每个仓库的摘要表示。 在本例中，我们获取 [octokit](https://github.com/octokit) 组织拥有的仓库列表： 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.) +当您获取单个资源时，响应通常包括该资源的_所有_属性。 这就是资源的“详细”表示。 （请注意，授权有时会影响表示中包含的详细信息数量。） -**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: +**示例**：当您获取单个仓库时，您将获得该仓库的详细表示。 在本例中，我们获取 [octokit/octokit.rb](https://github.com/octokit/octokit.rb) 仓库： GET /repos/octokit/octokit.rb -The documentation provides an example response for each API method. The example -response illustrates all attributes that are returned by that method. +本文档提供每种 API 方法的示例响应。 示例响应说明了该方法返回的所有属性。 -### Authentication +### 身份验证 -{% if currentVersion == "github-ae@latest" %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places. This is to prevent the accidental leakage of private repositories to unauthorized users. +{% 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`。 这是为了防止私有仓库意外泄露给未经授权的用户。 -#### Basic authentication +#### 基本验证 ```shell $ curl -u "username" {% data variables.product.api_url_pre %} ``` -#### OAuth2 token (sent in a header) +#### OAuth2 令牌（在标头中发送） ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} @@ -106,14 +95,14 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. {% note %} -Note: GitHub recommends sending OAuth tokens using the Authorization header. +注：GitHub 建议使用授权标头发送 OAuth 令牌。 {% endnote %} -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. +阅读[关于 OAuth2 的更多信息](/apps/building-oauth-apps/)。 请注意，OAuth2 令牌可使用生产应用程序的 [web 应用程序流](/developers/apps/authorizing-oauth-apps#web-application-flow)来获取。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -#### OAuth2 key/secret +#### OAuth2 键/密钥 {% data reusables.apps.deprecating_auth_with_query_parameters %} @@ -121,20 +110,20 @@ Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens c curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos' ``` -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. +使用 `client_id` 和 `client_secret`_不会_验证为用户，只会识别您的 OAuth 应用程序以提高速率限制。 权限仅授予用户，而不授予应用程序，因此只会返回未经验证用户可以看到的数据。 因此，您应该仅在服务器到服务器的场景中使用 OAuth2 键/密钥。 不要将 OAuth 应用程序的客户端密钥泄露给用户。 -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)". +在私有模式下无法使用 OAuth2 键和密钥进行身份验证，尝试验证时会返回 `401 Unauthorized`。 更多信息请参阅“[启用私有模式](/enterprise/admin/installation/enabling-private-mode)”。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} -Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +阅读[有关未经验证速率限制的更多信息](#increasing-the-unauthenticated-rate-limit-for-oauth-applications)。 {% endif %} -#### Failed login limit +#### 失败登录限制 -Authenticating with invalid credentials will return `401 Unauthorized`: +使用无效凭据进行身份验证将返回 `401 Unauthorized`： ```shell $ curl -I {% data variables.product.api_url_pre %} -u foo:bar @@ -142,13 +131,11 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > { > "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` -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`: +在短时间内检测到多个使用无效凭据的请求后，API 将暂时拒绝该用户的所有身份验证尝试（包括使用有效凭据的尝试），并返回 `403 Forbidden`： ```shell $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} @@ -156,70 +143,63 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > 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" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` -### Parameters +### 参数 -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: +许多 API 方法采用可选参数。 对于 `GET` 请求，任何未指定为路径段的参数都可以作为 HTTP 查询字符串参数进行传递： ```shell $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed" ``` -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. +在此例中，'vmg' 和 'redcarpet' 是为路径中的 `:owner` 和 `:repo` 参数提供的值，而 `:state` 是查询字符串中传递的参数。 -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': +对于 `POST`、`PATCH`、`PUT` 和 `DELETE` 请求，未包含在 URL 中的参数应编码为 JSON，内容类型为 'application/json'： ```shell -$ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product.api_url_pre %}/authorizations +$ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations ``` -### Root endpoint +### 根端点 -You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports: +您可以向根端点发出 `GET` 请求，以获取 REST API 支持的所有端点类别： ```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 global node IDs +### GraphQL 全局节点 ID -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. +请参阅“[使用全局节点 ID](/graphql/guides/using-global-node-ids)”指南，详细了解如何通过 REST API 查找 `node_id` 以及如何在 GraphQL 操作中使用它们。 -### Client errors +### 客户端错误 -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. +接收请求正文的 API 调用上可能存在三种类型的客户端错误： +1. 发送无效的 JSON 将导致 `400 Bad Request` 响应。 + HTTP/1.1 400 Bad Request Content-Length: 35 - + {"message":"Problems parsing JSON"} -2. Sending the wrong type of JSON values will result in a `400 Bad - Request` response. - +2. 发送错误类型的 JSON 值将导致 `400 Bad +Request` 响应。 + HTTP/1.1 400 Bad Request Content-Length: 40 - + {"message":"Body should be a JSON object"} -3. Sending invalid fields will result in a `422 Unprocessable Entity` - response. - +3. 发送无效的字段将导致 `422 Unprocessable Entity` 响应。 + HTTP/1.1 422 Unprocessable Entity Content-Length: 149 - + { "message": "Validation Failed", "errors": [ @@ -231,142 +211,121 @@ receive request bodies: ] } -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: +所有错误对象都具有资源和字段属性，以便客户端可以知道问题所在。 还有一个错误代码，让您知道该字段有什么问题。 以下是可能的验证错误代码： -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. +| 错误代码名称 | 描述 | +| ---------------- | -------------------------------------------------- | +| `missing` | 资源不存在。 | +| `missing_field` | 资源上的必需字段尚未设置。 | +| `invalid` | 字段的格式无效。 请查看文档以了解更具体的信息。 | +| `already_exists` | 另一个资源具有与此字段相同的值。 在必须具有某些唯一键（例如标签名称）的资源中可能会发生这种情况。 | +| `unprocessable` | 提供的输入无效。 | -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. +资源还可能发送自定义验证错误（其中 `code` 为 `custom`）。 自定义错误始终包括一个描述错误的 `message` 字段，大多数错误还包括 `documentation_url` 字段，该字段指向一些可能有助于解决错误的内容。 -### HTTP redirects +### HTTP 重定向 -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. +API v3 酌情使用 HTTP 重定向。 客户端应假定任何请求都可能会导致重定向。 接收 HTTP 重定向*不是*错误，客户端应该遵循该重定向。 重定向响应将包括 `Location` 标头字段，其中包含客户端应向其重复请求的资源的 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. +| 状态代码 | 描述 | +| ----------- | ------------------------------------------------------------------------------- | +| `301` | 永久重定向。 用于发出请求的 URI 已被 `Location` 标头字段中指定的 URL 所取代。 此请求以及对此资源的所有未来请求都应定向到新的 URI。 | +| `302`、`307` | 临时重定向。 该请求应按 `Location` 标头字段中指定的 URI 逐字重复，但客户端应对未来的请求继续使用原来的 URI。 | -Other redirection status codes may be used in accordance with the HTTP 1.1 spec. +其他重定向状态代码可根据 HTTP 1.1 规范使用。 -### HTTP verbs +### HTTP 请求方法 -Where possible, API v3 strives to use appropriate HTTP verbs for each -action. +API v3 尽可能对每个操作使用适当的 HTTP 请求方法。 -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. +| 请求方法 | 描述 | +| -------- | ------------------------------------------------------------------------------ | +| `HEAD` | 可以针对任何资源发出以仅获取 HTTP 标头信息。 | +| `GET` | 用于检索资源。 | +| `POST` | 用于创建资源。 | +| `PATCH` | 用于通过部分 JSON 数据更新资源。 例如，议题资源具有 `title` 和 `body` 属性。 `PATCH` 请求可以接受一个或多个属性来更新资源。 | +| `PUT` | 用于替换资源或集合。 对于没有 `body` 属性的 `PUT` 请求，请确保将 `Content-Length` 标头设置为零。 | +| `DELETE` | 用于删除资源。 | -### Hypermedia +### 超媒体 -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. +所有资源都可以具有一个或多个链接到其他资源的 `*_url` 属性。 这些属性旨在提供明确的 URL，使适当的 API 客户端不需要自己构建 URL。 强烈建议 API 客户端使用这些属性。 这样做有助于开发者未来更容易升级 API。 所有 URI 都应成为适当的 [RFC 6570][rfc] URI 模板。 -You can then expand these templates using something like the [uri_template][uri] -gem: +然后，您可以使用 [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 - -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. +默认情况下，如果请求返回了多个项，将按每页最多 30 项进行分页。 您可以使用 `page` 参数指定更多页面。 对于某些资源，您还可以使用 `per_page` 参数设置自定义页面大小，每页最多 100 项。 请注意，由于技术原因，并非所有端点都遵循 `per_page` 参数，相关示例请参阅[事件](/rest/reference/activity#events)。 ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Note that page numbering is 1-based and that omitting the `page` -parameter will return the first page. +请注意，页码从 1 开始，省略 `page` 参数将返回第一页。 -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. +有些端点使用基于光标的分页。 光标是指向结果集中位置的字符串。 使用基于光标的分页时，结果集中没有固定的“页”概念，因此无法导航到特定页面。 相反，您可以使用 `before` 或 `after` 参数遍历结果。 -For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. +有关分页的更多信息，请查看我们的[分页浏览][pagination-guide]指南。 -#### Link header +#### 链接标头 {% note %} -**Note:** It's important to form calls with Link header values instead of constructing your own URLs. +**注：**确保使用链接标头值构成调用，而不是构建自己的 URL。 {% endnote %} -The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. For example: +[链接标头](http://tools.ietf.org/html/rfc5988)包括分页信息： 例如： 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", -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). +此 `Link` 响应标头包含一个或多个[超媒体](/rest#hypermedia)链接关系，其中一些可能需要扩展为 [URI 模板](http://tools.ietf.org/html/rfc6570)。 -The possible `rel` values are: +可能的 `rel` 值为： -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. +| 名称 | 描述 | +| ------- | ------------ | +| `next` | 结果下一页的链接关系 | +| `last` | 结果最后一页的链接关系。 | +| `first` | 结果第一页的链接关系。 | +| `prev` | 结果前一页的链接关系。 | -### Rate limiting +### 速率限制 -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. +对于使用基本验证或 OAuth 的 API 请求，每小时最多可发出 5,000 个请求。 无论是使用[基本验证](#basic-authentication)还是 [OAuth 令牌](#oauth2-token-sent-in-a-header)，经验证的请求都与经验证的用户相关联。 这意味着在使用同一用户拥有的不同令牌进行验证时，该用户授权的所有 OAuth 应用程序将共享同一配额——每小时 5,000 个请求。 {% if currentVersion == "free-pro-team@latest" %} -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. +对于属于 {% data variables.product.prodname_ghe_cloud %} 帐户的用户，使用 OAuth 令牌对相同 {% data variables.product.prodname_ghe_cloud %} 帐户拥有的资源发出的请求上限已提升至每小时 15,000 点。 {% endif %} -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. +在 GitHub Actions 中使用内置 `GITHUB_TOKEN` 时，每个仓库的速率限制为每小时 1,000 个请求。 对于属于 GitHub Enterprise Cloud 帐户的组织，此限制是每个仓库每小时 15,000 个请求。 + +对于未经验证的请求，速率限制允许每小时最多 60 个请求。 未经验证的请求与原始 IP 地址相关联，与发出请求的用户无关。 {% data reusables.enterprise.rate_limit %} -Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). +请注意，[搜索 API 具有自定义速率限制规则](/rest/reference/search#rate-limit)。 -The returned HTTP headers of any API request show your current rate limit status: +任何 API 请求返回的 HTTP 标头都显示当前速率限制状态： ```shell $ curl -I {% data variables.product.api_url_pre %}/users/octocat @@ -378,20 +337,20 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat > X-RateLimit-Reset: 1372700873 ``` -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). +| 标头名称 | 描述 | +| ----------------------- | ---------------------------------------------------------------------- | +| `X-RateLimit-Limit` | 每小时允许您发出的最大请求数。 | +| `X-RateLimit-Remaining` | 当前速率限制窗口中剩余的请求数。 | +| `X-RateLimit-Reset` | 当前费率限制窗口重置时间，以 [UTC 标准时间秒](http://en.wikipedia.org/wiki/Unix_time)为单位。 | -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. +如果您需要不同格式的时间，任何现代编程语言都可以实现您的目标。 例如，如果您在 Web 浏览器上打开控制台，您可以轻松地以 JavaScript Date 对象获取重置时间。 ``` 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 @@ -403,15 +362,15 @@ If you exceed the rate limit, an error response returns: > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting" > } ``` -You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. +您可以[检查速率限制状态](/rest/reference/rate-limit)，而不会引发 API 命中。 -#### Increasing the unauthenticated rate limit for OAuth applications +#### 提高 OAuth 应用程序的未经验证速率限制 -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. +如果您的 OAuth 应用程序需要以更高的速率限制进行未经验证的调用， 您可以在端点路由之前传递应用程序的客户端 ID 和密钥。 ```shell $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos @@ -425,21 +384,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 +#### 保持在速率限制之内 -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). +如果使用基本验证或 OAuth 时超出了速率限制，您可以通过缓存 API 响应和使用[条件请求](#conditional-requests)来解决此问题。 -#### Abuse rate limits +#### 滥用速率限制 -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. +为了在 {% data variables.product.product_name %} 上提供优质的服务，使用 API 时，某些操作可能会受到额外的速率限制。 例如，使用 API 快速创建内容、主动轮询而不是使用 web 挂钩、发出多个并发请求或重复请求计算成本高昂的数据，可能会导致滥用速率限制。 -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/). +滥用速率限制无意干扰 API 的合法使用。 您的正常速率限制应该是您目标的唯一限制。 为确保您成为 API 的好公民，请查看我们的[最佳实践指南](/guides/best-practices-for-integrators/)。 -If your application triggers this rate limit, you'll receive an informative response: +如果您的应用程序触发此速率限制，您将收到信息响应： ```shell > HTTP/1.1 403 Forbidden @@ -448,25 +407,23 @@ If your application triggers this rate limit, you'll receive an informative resp > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" > } ``` {% if currentVersion == "free-pro-team@latest" %} -### User agent required +### 必需用户代理 -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. +所有 API 请求都必须包含有效的 `User-Agent` 标头。 没有 `User-Agent` 标头的请求将被拒绝。 我们要求您使用 {% data variables.product.product_name %} 用户名或应用程序的名称作为 `User-Agent` 标头值。 这是为了方便我们在发现问题时与您联系 。 -Here's an example: +例如： ```shell 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: +默认情况下，cURL 会发送有效的 `User-Agent` 标头。 如果您通过 cURL（或通过备用客户端）提供了无效的 `User-Agent` 标头，将会收到 `403 Forbidden` 响应： ```shell $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta @@ -476,25 +433,20 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta > Request forbidden by administrative rules. > Please make sure your request has a User-Agent header. -> Check for other possible causes. +> 检查其他可能的原因。 ``` {% endif %} -### Conditional requests +### 条件请求 -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`. +大多数响应返回 `ETag` 标头。 许多响应还会返回 `Last-Modified` 标头。 您可以根据这些标头的值，分别使用 `If-None-Match` 和 `If-Modified-Since` 标头对这些资源发出后续请求。 如果资源没有更改，服务器将返回 `304 Not Modified`。 {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**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. +**注**：发出条件请求并收到 304 响应不会计入您的[速率限制](#rate-limiting)，因此我们建议您尽可能使用它。 {% endtip %} @@ -534,16 +486,11 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T > X-RateLimit-Reset: 1372700873 ``` -### Cross origin resource sharing +### 跨源资源共享 -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. +API 支持适用于任何来源 AJAX 请求的跨源资源共享 (CORS)。 您可以阅读 [CORS W3C 建议](http://www.w3.org/TR/cors/)或 HTML 5 安全指南中的[这方面介绍](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki)。 -Here's a sample request sent from a browser hitting -`http://example.com`: +以下是从浏览器点击发送的示例请求 `http://example.com`： ```shell $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" @@ -552,7 +499,7 @@ Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval ``` -This is what the CORS preflight request looks like: +以下是 CORS 预检请求的示例： ```shell $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS @@ -564,13 +511,9 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra Access-Control-Max-Age: 86400 ``` -### JSON-P callbacks +### JSON-P 回调 -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. +您可以向任何 GET 调用发送 `?callback` 参数，以便让结果包裹在 JSON 函数中。 当浏览器希望绕开跨域问题将 {% data variables.product.product_name %} 内容嵌入网页时，通常使用此方法。 响应包括与常规 API 相同的数据输出，加上相关的 HTTP 标头信息。 ```shell $ curl {% data variables.product.api_url_pre %}?callback=foo @@ -591,7 +534,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo > }) ``` -You can write a JavaScript handler to process the callback. Here's a minimal example you can try out: +您可以编写一个 JavaScript 处理程序来处理回调。 以下是一个最小的处理程序示例，您可以尝试编写： @@ -602,28 +545,26 @@ You can write a JavaScript handler to process the callback. Here's a minimal exa 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.

-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. +所有标头都具有与 HTTP 标头相同的字符串值，但有一个值得注意的例外 ：链接。 链接标头已预先解析，并以 `[url, options]` 元组的数组形式出现。 -A link that looks like this: +链接如下所示： Link: ; rel="next", ; rel="foo"; bar="baz" -... will look like this in the Callback output: +... 在回调输出中将如下所示： ```json { @@ -645,37 +586,40 @@ A link that looks like this: } ``` -### Timezones +### 时区 -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. +某些创建新数据的请求（例如创建新的提交）允许您在指定或生成时间戳时提供时区信息。 我们按照优先顺序应用以下规则来确定 API 调用的时区信息。 -* [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) +* [使用 `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 +#### 明确提供带有时区信息的 ISO 8601 时间戳 -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). +对于允许指定时间戳的 API 调用，我们使用这种明确的时间戳。 这方面的示例是[提交 API](/rest/reference/git#commits)。 -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. +这些时间戳看起来像 `2014-02-27T15:05:06+01:00`。 另请参阅[本示例](/rest/reference/git#example-input)，了解如何指定这些时间戳。 -#### Using the `Time-Zone` header +#### 使用 `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). +可以提供根据 [Olson 数据库中的名称列表](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)定义时区的 `Time-Zone` 标头。 ```shell $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/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. +这意味着当您在这个标题定义的时区做出 API 调用时，我们会生成一个时间戳。 例如，[内容 API](/rest/reference/repos#contents)为每个添加或更改生成 git 提交，并使用当前时间作为时间戳。 此标头将确定用于生成当前时间戳的时区。 -#### Using the last known timezone for the user +#### 使用用户的最后一个已知时区 -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. +如果未指定 `Time-Zone` 标头，并且您对 API 进行验证过身份的调用，则我们对经过身份验证的用户使用最后一个已知时区。 最新一个已知的时区在您浏览 {% data variables.product.product_name %} 网站时都会更新。 -#### Defaulting to UTC without other timezone information +#### 在没有其他时区信息的情况下默认使用 UTC -If the steps above don't result in any information, we use UTC as the timezone to create the git commit. +如果上述步骤未产生任何信息，我们将使用 UTC 作为时区来创建 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/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md index 16a1a8ffcb..fe1b674a00 100644 --- a/translations/zh-CN/content/rest/reference/enterprise-admin.md +++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md @@ -100,7 +100,7 @@ IdP 必须使用 `{% data variables.product.api_url_code %}/scim/v2/enterprises/ {% note %} -**注：**企业 SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的企业。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 +**注：**企业 SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的企业。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 {% endnote %} diff --git a/translations/zh-CN/content/rest/reference/migrations.md b/translations/zh-CN/content/rest/reference/migrations.md index 266786ee84..754383a25b 100644 --- a/translations/zh-CN/content/rest/reference/migrations.md +++ b/translations/zh-CN/content/rest/reference/migrations.md @@ -16,7 +16,7 @@ topics: ## 组织 -迁移 API 仅适用于经过身份验证的组织所有者。 更多信息请参阅“[组织的权限级别](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)”和“[其他身份验证方法](/rest/overview/other-authentication-methods)”。 +迁移 API 仅适用于经过身份验证的组织所有者。 For more information, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#permission-levels-for-an-organization)" and "[Other authentication methods](/rest/overview/other-authentication-methods)." {% data variables.migrations.organization_migrations_intro %} diff --git a/translations/zh-CN/content/rest/reference/repos.md b/translations/zh-CN/content/rest/reference/repos.md index 62d2e2baf9..fdad9cd5cf 100644 --- a/translations/zh-CN/content/rest/reference/repos.md +++ b/translations/zh-CN/content/rest/reference/repos.md @@ -193,7 +193,7 @@ topics: ## 页面 -{% data variables.product.prodname_pages %} API 可检索关于您的 {% data variables.product.prodname_pages %} 配置以及构建状态的信息。 只有经过验证的所有者才能访问有关网站和构建的信息{% if currentVersion != "github-ae@latest" %}，即使网站是公开的也一样{% endif %}。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)”。 +{% data variables.product.prodname_pages %} API 可检索关于您的 {% data variables.product.prodname_pages %} 配置以及构建状态的信息。 只有经过验证的所有者才能访问有关网站和构建的信息{% if currentVersion != "github-ae@latest" %}，即使网站是公开的也一样{% endif %}。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)”。 在其响应中包含 `status` 键的 {% data variables.product.prodname_pages %} API 端点中，其值可能是以下值之一： * `null`：站点尚未构建。 @@ -205,7 +205,7 @@ topics: 在返回 GitHub Pages 站点信息的 {% data variables.product.prodname_pages %} API 端点中，JSON 响应包括以下字段： * `html_url`：所渲染的 Pages 站点的绝对 URL（包括模式）。 例如，`https://username.github.io`。 * `source`：包含所渲染 Pages 站点的源分支和目录的对象。 这包括： - - `branch`：用于发布[站点源文件](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)的仓库分支。 例如，_main_ 或 _gh-pages_。 + - `branch`：用于发布[站点源文件](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)的仓库分支。 例如，_main_ 或 _gh-pages_。 - `path`：提供站点发布内容的仓库目录。 可能是 `/` 或 `/docs`。 {% for operation in currentRestOperations %} diff --git a/translations/zh-CN/content/rest/reference/scim.md b/translations/zh-CN/content/rest/reference/scim.md index 098645bbef..08134f0b67 100644 --- a/translations/zh-CN/content/rest/reference/scim.md +++ b/translations/zh-CN/content/rest/reference/scim.md @@ -14,7 +14,7 @@ SCIM API 由 SCIM 启用的身份提供程序 (IdP) 用来自动预配 {% data v {% note %} -**注：**SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的组织。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 +**注：**SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的组织。 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 {% endnote %} diff --git a/translations/zh-CN/content/rest/reference/teams.md b/translations/zh-CN/content/rest/reference/teams.md index fae4009043..cd13c52b7e 100644 --- a/translations/zh-CN/content/rest/reference/teams.md +++ b/translations/zh-CN/content/rest/reference/teams.md @@ -18,7 +18,7 @@ topics: ## 讨论 -团队讨论 API 允许您获取、创建、编辑和删除团队页面上的讨论帖子。 您可以使用团队讨论进行不特定于存储库或项目的对话。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论帖子。 更多信息请参阅“[关于团队讨论](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)”。 要详细了解对讨论帖子的评论，请参阅[团队讨论评论 API](/rest/reference/teams#discussion-comments)。 此 API 仅适用于团队组织中经过身份验证的成员。 +团队讨论 API 允许您获取、创建、编辑和删除团队页面上的讨论帖子。 您可以使用团队讨论进行不特定于存储库或项目的对话。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论帖子。 更多信息请参阅“[关于团队讨论](//organizations/collaborating-with-your-team/about-team-discussions/)”。 要详细了解对讨论帖子的评论，请参阅[团队讨论评论 API](/rest/reference/teams#discussion-comments)。 此 API 仅适用于团队组织中经过身份验证的成员。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} @@ -26,7 +26,7 @@ topics: ## 讨论评论 -团队讨论评论 API 允许您在[团队讨论](/rest/reference/teams#discussions)帖子上获取、 创建、编辑和删除讨论评论。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论上的评论。 更多信息请参阅“[关于团队讨论](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions/)”。 此 API 仅适用于团队组织中经过身份验证的成员。 +团队讨论评论 API 允许您在[团队讨论](/rest/reference/teams#discussions)帖子上获取、 创建、编辑和删除讨论评论。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论上的评论。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions/)”。 此 API 仅适用于团队组织中经过身份验证的成员。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} @@ -39,7 +39,7 @@ topics: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**注：**当您为具有组织身份提供程序 (IdP) 的团队设置了团队同步时，如果尝试使用 API 更改团队的成员身份，则会看到错误。 如果您有权访问 IdP 中的组成员身份，可以通过身份提供程序管理 GitHub 团队成员身份，该提供程序会自动添加和删除组织的成员。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。 +**注：**当您为具有组织身份提供程序 (IdP) 的团队设置了团队同步时，如果尝试使用 API 更改团队的成员身份，则会看到错误。 如果您有权访问 IdP 中的组成员身份，可以通过身份提供程序管理 GitHub 团队成员身份，该提供程序会自动添加和删除组织的成员。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。 {% endnote %} @@ -54,7 +54,7 @@ topics: 团队同步 API 允许您管理 {% data variables.product.product_name %} 团队与外部身份提供程序 (IdP) 组之间的连接。 要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。 用于身份验证的令牌还需要获得授权才能与 IdP (SSO) 提供程序一起使用。 更多信息请参阅“授权个人访问令牌用于 SAML 单点登录组织”。 -您可以通过 IdP 通过团队同步管理 GitHub 团队成员。 必须启用团队同步才能使用团队同步 API。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。 +您可以通过 IdP 通过团队同步管理 GitHub 团队成员。 必须启用团队同步才能使用团队同步 API。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml index 6501ee4c75..38eee4caa4 100644 --- a/translations/zh-CN/data/glossaries/external.yml +++ b/translations/zh-CN/data/glossaries/external.yml @@ -88,7 +88,7 @@ - term: 优选 description: >- - To choose a subset of changes from a series of changes (typically commits) and record them as a new series of changes on top of a different codebase. In Git, this is performed by the `git cherry-pick` command to extract the change introduced by an existing commit on another branch and to record it based on the tip of the current branch as a new commit. For more information, see [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation. + 从一系列更改（通常是提交）中选择一部分更改，并在不同的代码库上将它们记录为新的更改系列。在 Git 中，这通过 `git cherry-pick` 命令来执行，在另一个分支上解压缩现有提交引入的更改，并根据当前分支的提示将其记录为新提交。更多信息请参阅 Git 文档中的 [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick)。 - term: 子团队 description: >- diff --git a/translations/zh-CN/data/release-notes/2-20/15.yml b/translations/zh-CN/data/release-notes/2-20/15.yml index aa3c664487..9252e94116 100644 Binary files a/translations/zh-CN/data/release-notes/2-20/15.yml and b/translations/zh-CN/data/release-notes/2-20/15.yml differ diff --git a/translations/zh-CN/data/release-notes/2-21/17.yml b/translations/zh-CN/data/release-notes/2-21/17.yml index 384428f84e..0f892b663e 100644 --- a/translations/zh-CN/data/release-notes/2-21/17.yml +++ b/translations/zh-CN/data/release-notes/2-21/17.yml @@ -1,6 +1,6 @@ --- date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. +intro: 由于影响多个客户的重大错误，下载已禁用。修复程序将在下一个修补程序中提供。 sections: security_fixes: - '**高：**在 GitHub Enterprise Server 中发现了远程代码执行漏洞，可能在构建 GitHub Pages 站点时被利用。GitHub Pages 使用的用户控制配置选项没有受到足够的限制，因此可以覆盖导致在 GitHub Enterprise Server 实例上执行代码的环境变量。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。此漏洞影响 GitHub Enterprise Server 3.0.3 之前的所有版本，已在 3.0.3、2.22.9 和 2.21.17 中修复。此漏洞通过 GitHub Bug Bounty 计划报告，已分配 CVE-2021-22864。' @@ -18,8 +18,8 @@ sections: - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 - 推送到命令行上的仓库时不报告安全警报。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance: + 日志旋转可能无法指示服务过渡到新日志文件，导致继续使用旧日志文件，最终根磁盘空间耗尽。 + 为了补救和/或防止这个问题，请在 [管理 shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-sh) (SSH) 中运行以下命令或联系 [GitHub Enterprise 支持](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) 寻求协助： ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/zh-CN/data/release-notes/2-21/18.yml b/translations/zh-CN/data/release-notes/2-21/18.yml new file mode 100644 index 0000000000..2ec4787df3 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/18.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**高：**在 GitHub 企业服务器中发现了一个不当的访问控制漏洞，该漏洞允许从 GitHub App 的 [Web 身份验证流程](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) 生成的访问令牌通过 REST API 读取专用仓库元数据，而无需获得适当的权限。要利用此漏洞，攻击者需要在实例上创建 GitHub 应用程序，并让用户通过 Web 身份验证流程授权应用程序。返回的私有仓库元数据将仅限于令牌标识的用户拥有的仓库。此漏洞影响了 GitHub Enterprise Server 3.0.4 之前的所有版本，但在 3.0.4、2.22.10、2.21.18 版本中已修复。此漏洞已分配 CVE-2021-22865，并通过 [GitHub Bug Bounty 计划]](https://bounty.github.com) 报告。" + - 包已更新到最新的安全版本。 + bugs: + - 服务未作为日志旋转的一部分而过渡到新的日志文件，导致磁盘使用量增加。 + - 内部仓库搜索结果上的标签显示为“私有”而不是“内部”。 + known_issues: + - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级期间不会保持。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 + - 推送到命令行上的仓库时不报告安全警报。 diff --git a/translations/zh-CN/data/release-notes/2-21/6.yml b/translations/zh-CN/data/release-notes/2-21/6.yml index 8638d1d9cd..66c91ea2be 100644 Binary files a/translations/zh-CN/data/release-notes/2-21/6.yml and b/translations/zh-CN/data/release-notes/2-21/6.yml differ diff --git a/translations/zh-CN/data/release-notes/2-22/10.yml b/translations/zh-CN/data/release-notes/2-22/10.yml new file mode 100644 index 0000000000..a0acd4d1f7 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-22/10.yml @@ -0,0 +1,16 @@ +--- +date: '2021-04-01' +sections: + security_fixes: + - "**高：**在 GitHub 企业服务器中发现了一个不当的访问控制漏洞，该漏洞允许从 GitHub App 的 [Web 身份验证流程](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) 生成的访问令牌通过 REST API 读取专用仓库元数据，而无需获得适当的权限。要利用此漏洞，攻击者需要在实例上创建 GitHub 应用程序，并让用户通过 Web 身份验证流程授权应用程序。返回的私有仓库元数据将仅限于令牌标识的用户拥有的仓库。此漏洞影响了 GitHub Enterprise Server 3.0.4 之前的所有版本，但在 3.0.4、2.22.10、2.21.18 版本中已修复。此漏洞已分配 CVE-2021-22865，并通过 [GitHub Bug Bounty 计划]](https://bounty.github.com) 报告。" + - 包已更新到最新的安全版本。 + bugs: + - 在 GitHub Enterprise 11.10.x 或更早版本中设置的时区没有被一些默认使用 UTC 时间的服务使用。 + - 服务未作为日志旋转的一部分而过渡到新的日志文件，导致磁盘使用量增加。 + - 内部仓库搜索结果上的标签显示为“私有”而不是“内部”。 + known_issues: + - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级期间不会保持。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 diff --git a/translations/zh-CN/data/release-notes/2-22/9.yml b/translations/zh-CN/data/release-notes/2-22/9.yml index 7cca9aa8f8..5e7396af4e 100644 --- a/translations/zh-CN/data/release-notes/2-22/9.yml +++ b/translations/zh-CN/data/release-notes/2-22/9.yml @@ -1,6 +1,6 @@ --- date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. +intro: 由于影响多个客户的重大错误，下载已禁用。修复程序将在下一个修补程序中提供。 sections: security_fixes: - '**高：**在 GitHub Enterprise Server 中发现了远程代码执行漏洞，可能在构建 GitHub Pages 站点时被利用。GitHub Pages 使用的用户控制配置选项没有受到足够的限制，因此可以覆盖导致在 GitHub Enterprise Server 实例上执行代码的环境变量。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。此漏洞影响 GitHub Enterprise Server 3.0.3 之前的所有版本，已在 3.0.3、2.22.9 和 2.21.17 中修复。此漏洞通过 GitHub Bug Bounty 计划报告，已分配 CVE-2021-22864。' @@ -24,8 +24,8 @@ sections: - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance: + 日志旋转可能无法指示服务过渡到新日志文件，导致继续使用旧日志文件，最终根磁盘空间耗尽。 + 为了补救和/或防止这个问题，请在 [管理 shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-sh) (SSH) 中运行以下命令或联系 [GitHub Enterprise 支持](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) 寻求协助： ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/zh-CN/data/release-notes/3-0/0.yml b/translations/zh-CN/data/release-notes/3-0/0.yml index d7a09e28e3..bb64e619ff 100644 --- a/translations/zh-CN/data/release-notes/3-0/0.yml +++ b/translations/zh-CN/data/release-notes/3-0/0.yml @@ -133,7 +133,7 @@ sections: - 依赖关系图无法解析 `setup.py` Python 清单文件，导致日志中的 HTTP 500 错误。 这种情况再加上重复的记录问题，导致根卷的使用增加。 - 竞争条件可能导致依赖关系图数据库迁移失败。 - 自定义时区从较早发布的 GitHub Enterprise Server 升级的实例可能在 web UI 中有不正确的时间戳。 - - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). + - Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。 deprecations: - heading: 弃用 GitHub Enterprise Server 2.19 diff --git a/translations/zh-CN/data/release-notes/3-0/1.yml b/translations/zh-CN/data/release-notes/3-0/1.yml index 0c1e46f56e..1f4433e088 100644 --- a/translations/zh-CN/data/release-notes/3-0/1.yml +++ b/translations/zh-CN/data/release-notes/3-0/1.yml @@ -44,7 +44,7 @@ sections: - 'restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。' - '依赖关系图无法解析 `yarn.lock` Javascript 清单文件，导致日志中的 HTTP 500 错误。' - '自定义时区从较早发布的 GitHub Enterprise Server 升级的实例可能在 web UI 中有不正确的时间戳。' - - 'Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`).' + - 'Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。' - | 用户可能会遇到一些资产（如头像）不加载，或者无法推送/拉取代码。这可能是由于 `haproxy-cluster-proxy` 服务中的 PID 不匹配造成的。要确定您是否有受影响的实例： diff --git a/translations/zh-CN/data/release-notes/3-0/2.yml b/translations/zh-CN/data/release-notes/3-0/2.yml index 5cd8c3ca72..13f80e8c55 100644 --- a/translations/zh-CN/data/release-notes/3-0/2.yml +++ b/translations/zh-CN/data/release-notes/3-0/2.yml @@ -30,7 +30,7 @@ sections: - 当启用维护模式时，某些服务将继续列为“活动进程”。 指定的服务预期在维护模式下运行。如果您遇到这个问题但不确定，请联系 [GitHub Enterprise 支持](https://enterprise.githubsupport.com/hc/en-us) 或 [GitHub Premium 支持](https://premium.githubsupport.com/)。 - 如果笔记本包含非 ASCII UTF-8 字符，网页界面中的 Jupyter Notebook 渲染可能会失败。 - restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。 - - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). + - Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。 - | 用户可能会遇到一些资产（如头像）不加载，或者无法推送/拉取代码。这可能是由于 `haproxy-cluster-proxy` 服务中的 PID 不匹配造成的。要确定您是否有受影响的实例： diff --git a/translations/zh-CN/data/release-notes/3-0/3.yml b/translations/zh-CN/data/release-notes/3-0/3.yml index ad50d52bd7..b9a10a27e2 100644 --- a/translations/zh-CN/data/release-notes/3-0/3.yml +++ b/translations/zh-CN/data/release-notes/3-0/3.yml @@ -1,6 +1,6 @@ --- date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. +intro: 由于影响多个客户的重大错误，下载已禁用。修复程序将在下一个修补程序中提供。 sections: security_fixes: - '**高：**在 GitHub Enterprise Server 中发现了远程代码执行漏洞，可能在构建 GitHub Pages 站点时被利用。GitHub Pages 使用的用户控制配置选项没有受到足够的限制，因此可以覆盖导致在 GitHub Enterprise Server 实例上执行代码的环境变量。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。此漏洞影响 GitHub Enterprise Server 3.0.3 之前的所有版本，已在 3.0.3、2.22.9 和 2.21.17 中修复。此漏洞通过 GitHub Bug Bounty 计划报告，已分配 CVE-2021-22864。' @@ -29,10 +29,10 @@ sections: - 当启用维护模式时，某些服务将继续列为“活动进程”。 指定的服务预期在维护模式下运行。如果您遇到这个问题但不确定，请联系 [GitHub Enterprise 支持](https://enterprise.githubsupport.com/hc/en-us) 或 [GitHub Premium 支持](https://premium.githubsupport.com/)。 - 如果笔记本包含非 ASCII UTF-8 字符，网页界面中的 Jupyter Notebook 渲染可能会失败。 - restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。 - - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). + - Pages 的旧版本未清理，可能填充用户磁盘 (`/data/user/`)。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) for assistance: + 日志旋转可能无法指示服务过渡到新日志文件，导致继续使用旧日志文件，最终根磁盘空间耗尽。 + 为了补救和/或防止这个问题，请在 [管理 shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-sh) (SSH) 中运行以下命令或联系 [GitHub Enterprise 支持](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) 寻求协助： ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/zh-CN/data/release-notes/3-0/4.yml b/translations/zh-CN/data/release-notes/3-0/4.yml new file mode 100644 index 0000000000..d9a22f1fb0 --- /dev/null +++ b/translations/zh-CN/data/release-notes/3-0/4.yml @@ -0,0 +1,25 @@ +--- +date: '2021-04-01' +intro: '对于 {% data variables.product.prodname_ghe_server %} 3.0+ 的最低基础设施要求已经增加。更多信息请参阅“[关于GitHub Enterprise Server 3.0 及更高版本的最低要求](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)”。' +sections: + security_fixes: + - "**高：**在 GitHub 企业服务器中发现了一个不当的访问控制漏洞，该漏洞允许从 GitHub App 的 [Web 身份验证流程](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) 生成的访问令牌通过 REST API 读取专用仓库元数据，而无需获得适当的权限。要利用此漏洞，攻击者需要在实例上创建 GitHub 应用程序，并让用户通过 Web 身份验证流程授权应用程序。返回的私有仓库元数据将仅限于令牌标识的用户拥有的仓库。此漏洞影响了 GitHub Enterprise Server 3.0.4 之前的所有版本，但在 3.0.4、2.22.10、2.21.18 版本中已修复。此漏洞已分配 CVE-2021-22865，并通过 [GitHub Bug Bounty 计划]](https://bounty.github.com) 报告。" + - 包已更新到最新的安全版本。 + bugs: + - 当启用维护模式时，某些服务仍然列为“活动进程”，尽管预计它们将运行， 并且不应该被列出。 + - 在从 2.22.x 升级到启用 GitHub Actions 的 3.0.x 后，自托管运行器版本没有更新，也没有自托管更新。 + - 旧 GitHub Pages 构建未进行清理，导致磁盘使用量增加。 + - '`memcached` 未在活动的副本上运行。' + - 启用 GitHub Actions 时更新文件权限失败。 + - 在 GitHub Enterprise 11.10.x 或更早版本中设置的时区没有被一些默认使用 UTC 时间的服务使用。 + - 服务未作为日志旋转的一部分而过渡到新的日志文件，导致磁盘使用量增加。 + - '`ghe-saml-mapping-csv` 命令行实用生成了一条警告消息。' + - 内部仓库搜索结果上的标签显示为“私有”而不是“内部”。 + known_issues: + - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级期间不会保持。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 + - 如果笔记本包含非 ASCII UTF-8 字符，网页界面中的 Jupyter Notebook 渲染可能会失败。 + - restructuredText(RST) 渲染在 web 界面可能失败，反而显示原始 RST 标记文本。 diff --git a/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md b/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md index 603f819c3d..0c2241b5de 100644 --- a/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md @@ -4,5 +4,7 @@ | `completed_workflow_run` | 当工作流程状态更改为`完成`时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。 | | `created_workflow_run` | 工作流程运行创建时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[创建示例工作流程](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)”。 | | `delete_workflow_run` | 工作流程运行被删除时触发。 更多信息请参阅“[删除工作流程运行](/actions/managing-workflow-runs/deleting-a-workflow-run)”。 | +| `disable_workflow` | 工作流程禁用时触发。 | +| `enable_workflow` | 在之前被 `disable_workflow` 禁用后，当工作流程启用时触发。 | | `rerun_workflow_run` | 工作流程运行重新运行时触发。 更多信息请参阅“[重新运行工作流程](/actions/managing-workflow-runs/re-running-a-workflow)。 | | `prepared_workflow_job` | 工作流程作业启动时触发。 包括提供给作业的机密列表。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。 | diff --git a/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md index 34889210fc..83453db412 100644 --- a/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md +++ b/translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md @@ -2,4 +2,4 @@ 您可以执行策略来控制仓库管理员是否被允许在组织的仓库中为 {% data variables.product.prodname_advanced_security %} 启用功能。 您可以为企业帐户拥有的所有组织或您选择的单个组织配置策略。 -对组织禁止 {% data variables.product.prodname_advanced_security %} 将使仓库管理员无法为其他仓库启用 {% data variables.product.prodname_advanced_security %} 功能，但不会对已启用功能的仓库禁用功能。 有关 {% data variables.product.prodname_advanced_security %} 功能配置的更多信息，请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 +对组织禁止 {% data variables.product.prodname_advanced_security %} 将使仓库管理员无法为其他仓库启用 {% data variables.product.prodname_advanced_security %} 功能，但不会对已启用功能的仓库禁用功能。 有关 {% data variables.product.prodname_advanced_security %} 功能配置的更多信息，请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。 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 26ea19355f..cc993ff124 100644 --- a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,9 +1,9 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% warning %} -**Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). +**弃用通知：** {% 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. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} +{% if enterpriseServersions contained 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/branches/set-default-branch.md b/translations/zh-CN/data/reusables/branches/set-default-branch.md index 4724f27f26..d4ca85049c 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 @@ -您可以为新仓库设置默认分支名称。 更多信息请参阅“[管理仓库的默认分支](/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 %} +您可以为新仓库设置默认分支名称。 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](/organizations/managing-organization-settings/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 %} diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-visibility.md index 2a89e1284f..ed222b20b8 100644 --- a/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ 作业的仓库可以是公开或私有的。 如果您使用私有仓库，只有学生或团队可以查看您提供的反馈。 -您也可以决定是否授予学生对作业仓库的管理员权限。 如果学生应该能够执行作业仓库的管理任务，则授予管理员权限。 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”和“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)”。 +您也可以决定是否授予学生对作业仓库的管理员权限。 如果学生应该能够执行作业仓库的管理任务，则授予管理员权限。 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”和“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。 在“Repository visibility（仓库可见性）”下，选择可见性。 （可选）选择 **Grant students admin access to their repository（授予学生对其仓库的管理员权限）**。 diff --git a/translations/zh-CN/data/reusables/classroom/guide-create-new-classroom.md b/translations/zh-CN/data/reusables/classroom/guide-create-new-classroom.md index e5ae3ae20c..6982e5e317 100644 --- a/translations/zh-CN/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/zh-CN/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. 在组织列表中，单击您希望用于教室的组织。 （可选）您可以创建一个新组织。 更多信息请参阅“[从头开始创建新组织](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)”。 ![组织列表中用于创建新教室的组织](/assets/images/help/classroom/click-organization.png) +1. 在组织列表中，单击您希望用于教室的组织。 （可选）您可以创建一个新组织。 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 ![组织列表中用于创建新教室的组织](/assets/images/help/classroom/click-organization.png) 1. 为您的教室键入名称。 ![用于键入教室名称的文本字段](/assets/images/help/classroom/type-classroom-name.png) 1. 单击 **Create classroom（创建教室）**。 ![用于键入教室名称的文本字段](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/zh-CN/data/reusables/code-scanning/click-alert-in-list.md b/translations/zh-CN/data/reusables/code-scanning/click-alert-in-list.md index 5a0ef73cc4..217addbf3b 100644 --- a/translations/zh-CN/data/reusables/code-scanning/click-alert-in-list.md +++ b/translations/zh-CN/data/reusables/code-scanning/click-alert-in-list.md @@ -1 +1,6 @@ -1. 在“Code Scanning（代码扫描）”下，单击要探索的警报。 ![来自 {% data variables.product.prodname_code_scanning %} 的警报列表](/assets/images/help/repository/code-scanning-click-alert.png) +1. 在“Code Scanning（代码扫描）”下，单击要探索的警报。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1"%} + ![来自 {% data variables.product.prodname_code_scanning %} 的警报列表](/assets/images/help/repository/code-scanning-click-alert.png) +{% else %} + ![来自 {% data variables.product.prodname_code_scanning %} 的警报列表](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) +{% endif %} 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 0ae3f234ac..555ed25950 100644 --- a/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -在运行安全性或版本更新时，有些生态系统必须能够解决来自其来源的所有依赖项，以验证版本更新是否成功。 如果清单或锁定文件包含任何私有依赖项，{% data variables.product.prodname_dependabot %} 必须能够访问这些依赖项所在的位置。 组织所有者可以授予 {% data variables.product.prodname_dependabot %} 访问包含同一个组织内项目依赖项的私有仓库. 更多信息请参阅“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)”。 您可以在仓库的 _dependabot.yml_ 配置文件中配置对私有注册表的访问。 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)。” +在运行安全性或版本更新时，有些生态系统必须能够解决来自其来源的所有依赖项，以验证版本更新是否成功。 如果清单或锁定文件包含任何私有依赖项，{% data variables.product.prodname_dependabot %} 必须能够访问这些依赖项所在的位置。 组织所有者可以授予 {% data variables.product.prodname_dependabot %} 访问包含同一个组织内项目依赖项的私有仓库. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)”。 您可以在仓库的 _dependabot.yml_ 配置文件中配置对私有注册表的访问。 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)。” 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 fccc2fe8fa..58e340711a 100644 --- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md +++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md @@ -6,7 +6,7 @@ | 包管理器 | YAML 值 | 支持的版本 | 私有仓库 | 私有注册表 | 供应 | | -------------- | ---------------- | ---------------------- |:-----:|:-----:|:-----:| -| Bundler | `bundler` | v1 | | **✓** | **✓** | +| Bundler | `bundler` | v1, v2 | | **✓** | **✓** | | Cargo | `cargo` | v1 | **✓** | **✓** | | | Composer | `composer` | v1, v2 | **✓** | **✓** | | | Docker | `docker` | v1 | **✓** | **✓** | | diff --git a/translations/zh-CN/data/reusables/dotcom_billing/coupon-expires.md b/translations/zh-CN/data/reusables/dotcom_billing/coupon-expires.md new file mode 100644 index 0000000000..647b2c3aa8 --- /dev/null +++ b/translations/zh-CN/data/reusables/dotcom_billing/coupon-expires.md @@ -0,0 +1 @@ +如果您使用优惠券支付订阅费用，当优惠券到期时，您的支付方式将收取订阅的全部费用。 如果您没有保存的支付方式，您的帐户将被降级为用户帐户的 {% data variables.product.prodname_free_user %} 或组织的 {% data variables.product.prodname_free_team %} 。 diff --git a/translations/zh-CN/data/reusables/education/about-github-education-link.md b/translations/zh-CN/data/reusables/education/about-github-education-link.md index 89779dbe78..c22de47487 100644 --- a/translations/zh-CN/data/reusables/education/about-github-education-link.md +++ b/translations/zh-CN/data/reusables/education/about-github-education-link.md @@ -1 +1 @@ -在申请个人折扣之前，请检查您的学习社区是否已作为 {% data variables.product.prodname_education %} 学校与我们合作。 更多信息请参阅“[关于 {% data variables.product.prodname_education %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education)”。 +在申请个人折扣之前，请检查您的学习社区是否已作为 {% data variables.product.prodname_campus_program %} 学校与我们合作。 更多信息请参阅“[关于 {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)”。 diff --git a/translations/zh-CN/data/reusables/enterprise_installation/replica-limit.md b/translations/zh-CN/data/reusables/enterprise_installation/replica-limit.md index 21bd197854..a3be67043c 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/replica-limit.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/replica-limit.md @@ -1,7 +1,7 @@ {% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} -**Note:** There is a maximum of 8 high availability replicas (both passive and active/geo replicas) allowed for {% data variables.product.product_name %}. +**注意：** 允许 {% data variables.product.product_name %} 使用最多 8 种高可用性副本（被动和主动/地理副本）。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/github-actions/actions-github-connect-requirement.md b/translations/zh-CN/data/reusables/github-actions/actions-github-connect-requirement.md new file mode 100644 index 0000000000..146bd14b2c --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/actions-github-connect-requirement.md @@ -0,0 +1 @@ +要允许 {% data variables.product.prodname_ghe_server %} 使用直接来自 {% data variables.product.prodname_dotcom_the_website %} 的操作，您可以使用 {% 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 %} 操作](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”中所述。 diff --git a/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md b/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md index 097473e2bb..23914f6e0c 100644 --- a/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md +++ b/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md @@ -2,16 +2,17 @@ 初学者工作流程模板将 `PATH` 设置为包含 OpenJDK 8，用于 x64 平台。 如果要使用不同的 Java 版本或面向不同的架构（`x64` 或 `x86`），您可以使用 `setup-java` 操作选择不同的 Java 运行时环境。 -例如，要使用 9.0.4 版本的 JDK，用于 x64 平台，您可以使用 `setup-java` 操作，将 `java-version` 和 `architecture` 参数配置为 `'9.0.4'` 和 `x64`。 +例如，要使用 Adoptium 提供的用于 x611 平台的 11 版 JDK，您可以使用 `setup-java` 操作，将 `java-version`、`distribution` 和 `architecture` 参数配置为 `'11'`、`'adopt'` 和 `x64`。 {% raw %} ```yaml{:copy} steps: - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 + - name: Set up JDK 11 for x64 + uses: actions/setup-java@v2 with: - java-version: '9.0.4' + java-version: '11' + distribution: 'adopt' architecture: x64 ``` {% endraw %} 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 index e31792a4c6..ad95882bf5 100644 --- 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 @@ -1,5 +1,5 @@ {% warning %} -**警告：** 如果您的组织使用团队同步，撤销个人的 SSO 身份将从映射到 IdP 组的任何团队中删除此人。 更多信息请参阅“[同步团队与身份提供程序](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”。 +**警告：** 如果您的组织使用团队同步，撤销个人的 SSO 身份将从映射到 IdP 组的任何团队中删除此人。 更多信息请参阅“[同步团队与身份提供程序](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 {% endwarning %} diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md index 1e1a9a2251..0d1f97630d 100644 --- a/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ b/translations/zh-CN/data/reusables/identity-and-permissions/sync-team-with-idp-group.md @@ -1 +1 @@ -启用团队同步后，团队维护员和组织所有者可在 {% data variables.product.prodname_dotcom %} 上或通过 API 将团队连接至 IdP 组。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”和“[团队同步](/rest/reference/teams#team-sync)”。 +启用团队同步后，团队维护员和组织所有者可在 {% data variables.product.prodname_dotcom %} 上或通过 API 将团队连接至 IdP 组。 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”和“[团队同步](/rest/reference/teams#team-sync)”。 diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-saml.md index 6367a12399..ee0d86bc2b 100644 --- a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-saml.md +++ b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-saml.md @@ -1 +1 @@ -3. 确认 SAML SSO 已启用。 更多信息请参阅“[管理组织的 SAML 单点登录](/articles/managing-saml-single-sign-on-for-your-organization)”。 +3. 确认 SAML SSO 已启用。 更多信息请参阅“[管理组织的 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/)”。 diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md index 69b4e50a3a..0d7f97c6da 100644 --- a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md +++ b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md @@ -1,5 +1,5 @@ 要对 Okta 启用团队同步，您或 IdP 管理员必须： -- 使用 Okta 为组织启用 SAML SSO 和 SCIM。 更多信息请参阅“[使用 Okta 配置 SAML 单点登录和 SCIM](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)”。 +- 使用 Okta 为组织启用 SAML SSO 和 SCIM。 更多信息请参阅“[使用 Okta 配置 SAML 单点登录和 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)”。 - 提供 Okta 实例的租户 URL。 - 为安装为服务用户的 Okta 生成具有只读管理员权限的有效 SSWS 令牌。 更多信息请参阅 Okta 文档中的[创建令牌](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/)和[服务用户](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm)。 diff --git a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md index d3e50c0e62..6e37e4c6c1 100644 --- a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,16 +1,27 @@ -{% if currentVersion == "free-pro-team@latest" %} -默认情况下，您将收到新 -{% data variables.product.prodname_dependabot_alerts %} 的通知： -- 通过电子邮件收到通知， 每次发现关键或严重性高的漏洞时都会发送电子邮件（**每次发现漏洞时发送电子邮件**选项） -- 在用户界面中接收通知，如有任何漏洞依赖项，将在仓库的文件和代码视图中显示警告（**UI 警报**选项） -- 在命令行上接收通知，当您推送到具有任何漏洞依赖项的仓库时，警告将显示为回叫（**命令行**选项） -- 在收件箱中收到通知，关键或严重性高的新漏洞会显示 Web 通知（**Web** 选项） +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +{% if currentversion == "free-proteam@latest"%}默认情况下，您将收到通知：{% endif %}{% if enterpriseServersions contains currentversion and currentversion gt "enterprise-server@3 %}默认情况下，如果您的站点管理员在您的实例上配置了通知电子邮件，您将收到 {% data variables.product.prodname_dependabot_alerts %}︰{% endif %} + +- 通过电子邮件，在为仓库启用 {% data variables.product.prodname_dependabot %} 时，当有新的清单文件提交到仓库，以及当发现具有关键或高严重性的新漏洞时，将发送一封电子邮件（**Email each time a vulnerability is found（每次找到漏洞时发送电子邮件）**选项）。 +- 在用户界面中接收通知，如有任何漏洞依赖项，将在仓库的文件和代码视图中显示警告（**UI 警报**选项）。 +- 在命令行上接收通知，当您推送到具有任何漏洞依赖项的仓库时，警告将显示为回叫（**命令行**选项）。 +- 在您的收件箱中，作为 web 通知。 为仓库启用 {% data variables.product.prodname_dependabot %} 时，当有新的清单文件提交到仓库，以及当发现具有关键或高严重性的新漏洞时，将发送 web 通知（**Web** 选项）。 +- 在 {% data variables.product.prodname_mobile %} 上，作为 web 通知。 更多信息请参阅“[为移动版 GitHub 启用推送通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)”。 + +{% note %} + +**注意：**电子邮件和 web/{% data variables.product.prodname_mobile %} 通知是： + +- _按仓库_ 在存储库中启用 {% data variables.product.prodname_dependabot %} 时，或者当新的清单文件提交到仓库时。 + +- _按组织_，当发现新的漏洞时。 + +{% endnote %} 您可以自定义您接收 {% data variables.product.prodname_dependabot_alerts %} 的通知。 例如，您可以使用 **Email a digest summary of vulnerabilities（以电子邮件发送漏洞摘要）**和 **Weekly security email digest（每周安全性电子邮件摘要）**选项通过电子邮件接收最多 10 个仓库的每周警报摘要。 {% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" or currentVersion == "enterprise-server@3.1" %} 默认情况下，如果站点管理员配置了使用电子邮件接收实例通知，您将 {% data variables.product.prodname_dependabot_alerts %} 的通知： - 通过电子邮件收到通知， 每次发现{% if currentVersion ver_gt "enterprise-server@2.23" %}关键或严重性{% endif %}高的漏洞时都会发送电子邮件（**每次发现漏洞时发送电子邮件**选项） diff --git a/translations/zh-CN/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/zh-CN/data/reusables/organizations/team-discussions-are-for-orgs.md index 1718745475..799ebee892 100644 --- a/translations/zh-CN/data/reusables/organizations/team-discussions-are-for-orgs.md +++ b/translations/zh-CN/data/reusables/organizations/team-discussions-are-for-orgs.md @@ -1 +1 @@ -团队讨论只能在组织的团队页面上提供。 更多信息请参阅“[关于团队讨论](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)”。 +团队讨论只能在组织的团队页面上提供。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 diff --git a/translations/zh-CN/data/reusables/organizations/team-synchronization.md b/translations/zh-CN/data/reusables/organizations/team-synchronization.md index c612ce44e5..c90e377900 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" or currentVersion == "github-ae@latest" %} -您可以使用团队同步通过身份提供程序自动添加和删除团队中的组织成员。 更多信息请参阅“[同步团队与身份提供程序组](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)”。 +您可以使用团队同步通过身份提供程序自动添加和删除团队中的组织成员。 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 {% endif %} diff --git a/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md b/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md index 126fa8336d..ca47bc9ce6 100644 --- a/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md +++ b/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md @@ -11,5 +11,5 @@ - [从团队中删除组织成员](/articles/removing-organization-members-from-a-team) - [将组织成员升级为团队维护员](/articles/giving-team-maintainer-permissions-to-an-organization-member) - 删除团队的仓库访问权限{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} -- [管理团队的代码审查任务](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} +- [管理团队的代码审查任务](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} - [管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md index b4762b69c4..47359eeafc 100644 --- a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. 针对要完成的任务，新创具有适当作用域的个人访问令牌 (PAT)。 如果您的组织需要 SSO，则必须为新令牌启用 SSO。 {% warning %} - **注：**如果选择 `write:packages` 作用域，请在创建 PAT 时取消选择 `repo` 作用域。 将具有 `repo` 作用域的 PAT 添加为仓库中的机秘，可让仓库中的所有协作者访问该机密。 这会在操作中使用作用域为 `repo` 的 PAT 时授予不必要的额外访问权限。 有关操作安全最佳实践的更多信息，请参阅“[GitHub Actions 的安全强化](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)”。 + **注意：** 默认情况下， 当您在用户界面中选择 `write:packages` 范围的个人访问令牌 (PAT) 时，`repo` 范围也将被选中。 `repo` 范围提供了不必要和广泛的访问权限，我们建议您尤其避免使用 GitHub Actions 工作流程。 更多信息请参阅“[GitHub Actions 的安全性增强](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)”。 作为一种解决方法，您可以在以下 URL 的用户界面中为 PAT 选择 `write:packages` 范围：`https://github.com/settings/tokens/new?scopes=write:packages`。 {% endwarning %} diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index da99a62f82..1f80199d66 100644 --- a/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,5 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} +PAT 可以授予对您的帐户的广泛访问权限。 在创建 PAT 以向 {% data variables.product.prodname_container_registry %} 验证时，您应该只选择必要的 `read:packages`、`write:packages` 或 `delete:packages` 范围。 + 要在 {% data variables.product.prodname_actions %} 工作流程中向 {% data variables.product.prodname_github_container_registry %} 验证，请使用 `GITHUB_TOKEN` 以获得最佳的安全性和体验。 有关更新使用个人访问令牌向 `ghcr.io` 验证的工作流程的指南，请参阅“[升级访问 `ghcr.io` 的工作流程](/packages/guides/using-github-packages-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)”。 diff --git a/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md index a23fdc598b..550c8614ee 100644 --- a/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/guides/migrating-to-github-container-registry-for-docker-images)" and "[Container guides for {% data variables.product.prodname_registry %}](/packages/guides/container-guides-for-github-packages)."{% endif %} +**注意：**{% data variables.product.prodname_registry %} Docker 注册表 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 将在未来的 {% data variables.product.product_name %} 版本中提供改进的容器支持。{% elsif currentVersion == "free-pro-team@latest" %} 现在提供改进的容器支持。 更多信息请参阅“[关于 GitHub Container Registry](/packages/guides/about-github-container-registry)”。 要了解如何迁移您现有的 Docker 映像和使用它们的任何工作流程，请参阅“[迁移到 Docker 映像的 {% data variables.product.prodname_github_container_registry %}](/packages/guides/migrating-to-github-container-registry-for-docker-images)”和“[ {% data variables.product.prodname_registry %} 容器指南](/packages/guides/container-guides-for-github-packages)”。{% endif %} {% endwarning %} diff --git a/translations/zh-CN/data/reusables/pages/choose-visibility.md b/translations/zh-CN/data/reusables/pages/choose-visibility.md index 644f2553f0..13adb3be1d 100644 --- a/translations/zh-CN/data/reusables/pages/choose-visibility.md +++ b/translations/zh-CN/data/reusables/pages/choose-visibility.md @@ -1 +1 @@ -1. （可选）如果您使用 {% data variables.product.prodname_ghe_cloud %} 从组织拥有的私有或内部仓库发布项目站点，请选择站点的可见性。 在 "{% data variables.product.prodname_pages %}" 下，选择 **{% data variables.product.prodname_pages %} visibility（可见性）**下拉菜单，然后单击可见性。 更多信息请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 ![选择站点可见性的下拉菜单](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file +1. （可选）如果您使用 {% data variables.product.prodname_ghe_cloud %} 从组织拥有的私有或内部仓库发布项目站点，请选择站点的可见性。 在 "{% data variables.product.prodname_pages %}" 下，选择 **{% data variables.product.prodname_pages %} visibility（可见性）**下拉菜单，然后单击可见性。 更多信息请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 ![选择站点可见性的下拉菜单](/assets/images/help/pages/public-or-private-visibility.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md index 81195c37bf..e735e86eaa 100644 --- a/translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md +++ b/translations/zh-CN/data/reusables/pages/org-owners-can-restrict-pages-creation.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**注意：**组织所有者现在可以限制从组织拥有的仓库发布 {% data variables.product.prodname_pages %} 站点。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的发布](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization)”。 +**注意：**组织所有者现在可以限制从组织拥有的仓库发布 {% data variables.product.prodname_pages %} 站点。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 {% endnote %} {% endif %} \ No newline at end of file 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 bf1041637e..87e4d2ec46 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" %} 默认{% endif %}在互联网上公开，即使站点的仓库是私有或内部的。{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} 否则，如果{% else %} 如果{% 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){% if currentVersion == "free-pro-team@latest" %}”和“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。{% else %}”。{% endif %} +**警告**：{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}如果您的站点管理员启用了公共页面，{% endif %}{% data variables.product.prodname_pages %} 站点{% if currentVersion == "free-pro-team@latest" %} 默认{% endif %}在互联网上公开，即使站点的仓库是私有或内部的。{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} 否则，如果{% else %} 如果{% 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){% if currentVersion == "free-pro-team@latest" %}”和“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。{% else %}”。{% endif %} {% endwarning %} diff --git a/translations/zh-CN/data/reusables/pages/sidebar-pages.md b/translations/zh-CN/data/reusables/pages/sidebar-pages.md new file mode 100644 index 0000000000..371201ab38 --- /dev/null +++ b/translations/zh-CN/data/reusables/pages/sidebar-pages.md @@ -0,0 +1,3 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %} +1. 在左侧边栏中，单击 **Pages（页面）**。 ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png) +{% endif %} diff --git a/translations/zh-CN/data/reusables/pages/update_your_dns_settings.md b/translations/zh-CN/data/reusables/pages/update_your_dns_settings.md index e46e1334da..fcce18ae48 100644 --- a/translations/zh-CN/data/reusables/pages/update_your_dns_settings.md +++ b/translations/zh-CN/data/reusables/pages/update_your_dns_settings.md @@ -1 +1 @@ -{% if currentVersion == "free-pro-team@latest" %}1. 如果为站点启用了自定义域，为避免域名被占用，请更新您的 DNS 设置。 更多信息请参阅“[为 {% data variables.product.prodname_pages %} 站点配置自定义域](/articles/configuring-a-custom-domain-for-your-github-pages-site)”。{% endif %} +{% if currentVersion == "free-pro-team@latest" %}1. 如果为站点启用了自定义域，为避免域名被占用，请更新您的 DNS 设置。 更多信息请参阅“[为 {% data variables.product.prodname_pages %} 站点配置自定义域](/pages/configuring-a-custom-domain-for-your-github-pages-site)”。{% endif %} diff --git a/translations/zh-CN/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/zh-CN/data/reusables/pages/www-and-apex-domain-recommendation.md index 9af6da13e8..7215e61ffd 100644 --- a/translations/zh-CN/data/reusables/pages/www-and-apex-domain-recommendation.md +++ b/translations/zh-CN/data/reusables/pages/www-and-apex-domain-recommendation.md @@ -1 +1 @@ -如果使用 apex 域作为自定义域名，建议还设置一个 `www` 子域。 如果通过 DNS 提供程序配置每种域类型的正确记录，{% data variables.product.prodname_pages %} 将自动在域之间创建重定向。 例如，如果您配置 `www.example.com` 作为站点的自定义域，并且为 apex 和 `www` 域设置了 `ALIAS` 和 `CNAME` 记录，则 `example.com` 将重定向到 `www.example.com`。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)”。 +如果使用 apex 域作为自定义域名，建议还设置一个 `www` 子域。 如果通过 DNS 提供程序配置每种域类型的正确记录，{% data variables.product.prodname_pages %} 将自动在域之间创建重定向。 例如，如果您配置 `www.example.com` 作为站点的自定义域，并且为 apex 和 `www` 域设置了 {% data variables.product.prodname_pages %} DNS 记录，则 `example.com` 将重定向到 `www.example.com`。 请注意，自动重定向仅适用于 `www` 子域。 自动重定向不适用于任何其他子域，如 `blog`。 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 2a01a2e977..d05d123825 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 %} - 您负责确保无法访问仓库的人员删除任何机密信息或知识产权。 -- 对私有{% 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)”。 +- 对私有{% 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 %} 仓库进行复刻。 For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)" and "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)." {% endwarning %} diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/zh-CN/data/reusables/repositories/sidebar-code-scanning-alerts.md index d87d94b277..173235a53d 100644 --- a/translations/zh-CN/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ b/translations/zh-CN/data/reusables/repositories/sidebar-code-scanning-alerts.md @@ -1 +1 @@ -1. 在左侧边栏中，单击 **Code scanning alerts（代码扫描警报）**。 （可选）选择您使用的代码扫描工具。 !["Code scanning alerts（代码扫描警报）" 选项卡](/assets/images/help/repository/sidebar-code-scanning-alerts.png) +1. 在左侧边栏中，单击 **Code scanning alerts（代码扫描警报）**。 !["Code scanning alerts（代码扫描警报）" 选项卡](/assets/images/help/repository/sidebar-code-scanning-alerts.png) diff --git a/translations/zh-CN/data/reusables/saml/about-linked-identities.md b/translations/zh-CN/data/reusables/saml/about-linked-identities.md index d55cf3ee81..0bb65a0baf 100644 --- a/translations/zh-CN/data/reusables/saml/about-linked-identities.md +++ b/translations/zh-CN/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -您可以查看成员已链接到其 {% data variables.product.product_name %} 帐户的单点登录身份。 如果可用，该条目将包含 SCIM 数据。 更多信息请参阅“[关于 SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)”。 +您可以查看成员已链接到其 {% data variables.product.product_name %} 帐户的单点登录身份。 如果可用，该条目将包含 SCIM 数据。 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 如果成员将错误的身份链接到其 {% data variables.product.product_name %} 帐户，您可以撤销链接的身份以允许该成员重试。 diff --git a/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md b/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md index 396e0ee95a..249056612f 100644 --- a/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/zh-CN/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,5 @@ {% note %} -**注：**外部协作者无需使用 IdP 进行身份验证即可访问实施 SAML SSO 的组织中的资源。 有关外部协作者的更多信息，请参阅“[组织的权限级别](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)”。 +**注：**外部协作者无需使用 IdP 进行身份验证即可访问实施 SAML SSO 的组织中的资源。 有关外部协作者的更多信息，请参阅“[组织的权限级别](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)”。 {% endnote %} 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 index 7fd08aaace..1839a08f29 100644 --- 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 @@ -7,6 +7,7 @@ | Alibaba Cloud | Alibaba 云访问密钥机密 | alibaba_cloud_access_key_secret | | Amazon Web Services (AWS) | Amazon AWS 访问密钥 ID | aws_access_key_id | | Amazon Web Services (AWS) | Amazon AWS 机密访问密钥 | aws_secret_access_key | +| Asana | Asana 个人访问令牌 | asana_personal_access_token | | Atlassian | Atlassian API 令牌 | atlassian_api_token | | Atlassian | Atlassian JSON Web 令牌 | atlassian_jwt | | Azure | Azure DevOps 个人访问令牌 | azure_devops_personal_access_token | @@ -37,8 +38,12 @@ | GoCardless | GoCardless Sandbox 访问令牌 | gocardless_sandbox_access_token | | Google Cloud | Google API 密钥 | google_api_key | | Google Cloud | Google Cloud 私钥 ID | google_cloud_private_key_id | +| Grafana | Grafana API 密钥 | grafana_api_key | | Hashicorp Terraform | Terraform Cloud / Enterprise API 令牌 | terraform_api_token | | Hubspot | Hubspot API 密钥 | hubspot_api_key | +| Intercom | Intercom 访问令牌 | intercom_access_token | +| Lob | Lob Live API 密钥 | lob_live_api_key | +| Lob | Lob Test API 密钥 | lob_test_api_key | | Mailchimp | Mailchimp API 密钥 | mailchimp_api_key | | Mailgun | Mailgun API 密钥 | mailgun_api_key | | npm | npm 访问令牌 | npm_access_token | @@ -51,6 +56,7 @@ | Proctorio | Proctorio 密钥 | proctorio_secret_key | | Pulumi | Pulumi 访问令牌 | pulumi_access_token | | PyPI | PyPI API 令牌 | pypi_api_token | +| RubyGems | RubyGems API 密钥 | rubygems_api_key | | Samsara | Samsara API 令牌 | samsara_api_token | | Samsara | Samsara OAuth 访问令牌 | samsara_oauth_access_token | | SendGrid | SendGrid API Key | sendgrid_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 index d9680d770d..9de42cb5f0 100644 --- 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 @@ -50,6 +50,7 @@ | Proctorio | Proctorio 密钥 | | Pulumi | Pulumi 访问令牌 | | PyPI | PyPI API 令牌 | +| RubyGems | RubyGems API 密钥 | | Samsara | Samsara API 令牌 | | Samsara | Samsara OAuth 访问令牌 | | Shopify | Shopify App 共享密钥 | diff --git a/translations/zh-CN/data/reusables/sponsors/choose-updates.md b/translations/zh-CN/data/reusables/sponsors/choose-updates.md index fe1072b917..6f452d58ff 100644 --- a/translations/zh-CN/data/reusables/sponsors/choose-updates.md +++ b/translations/zh-CN/data/reusables/sponsors/choose-updates.md @@ -1 +1 @@ -4. 决定是否要接收来自被赞助帐户的电子邮件更新，然后选择或取消选择“Receive updates from _ACCOUNT_（接收来自 ACCOUNT 的更新）”。 ![接收来自赞助帐户的更新的复选框](/assets/images/help/sponsors/updates-checkbox-manage.png) +4. Decide whether you want to receive email updates from the sponsored account, then select or unselect "Receive email updates from _ACCOUNT_." ![接收来自赞助帐户的更新的复选框](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/zh-CN/data/reusables/sponsors/click-add-tier.md b/translations/zh-CN/data/reusables/sponsors/click-add-tier.md index 3d0d6e9ac3..427804a96d 100644 --- a/translations/zh-CN/data/reusables/sponsors/click-add-tier.md +++ b/translations/zh-CN/data/reusables/sponsors/click-add-tier.md @@ -1 +1 @@ -1. 在页面底部，单击 **Add a tier（添加等级）**。 ![添加等级按钮](/assets/images/help/sponsors/add-a-tier-button.png) +1. To create a monthly tier, click **Add a monthly tier** at the right of the page. Alternatively, to create a tier for one-time payments, click **One-time tiers** and then click **Add a one-time tier**. ![添加等级按钮](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/zh-CN/data/reusables/sponsors/enable-custom-amounts.md b/translations/zh-CN/data/reusables/sponsors/enable-custom-amounts.md new file mode 100644 index 0000000000..1889367cb9 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/enable-custom-amounts.md @@ -0,0 +1,2 @@ +1. When you have at least one tier, you'll see an option to enable custom amounts above the monthly and one-time tiers. If you want to allow sponsors to set their payment amount, then select **Enable custom amounts**. ![Enable custom amounts](/assets/images/help/sponsors/enable-custom-amounts.png) +1. Optionally, if you enable custom amounts you can set a default amount to display for the custom tiers. Specify a whole dollar amount and click **Set default amount**. ![Set a default amount](/assets/images/help/sponsors/set-default-amount.png) diff --git a/translations/zh-CN/data/reusables/sponsors/feedback.md b/translations/zh-CN/data/reusables/sponsors/feedback.md new file mode 100644 index 0000000000..e5cb6b1814 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/feedback.md @@ -0,0 +1 @@ +您可以与 {% data variables.product.company_short %} 分享您对 {% data variables.product.prodname_sponsors %} 的反馈。 To join the conversation, see "[Sponsors Feedback](https://github.com/github/feedback/discussions/categories/sponsors-feedback)." diff --git a/translations/zh-CN/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/zh-CN/data/reusables/sponsors/manage-updates-for-orgs.md index 1b9bc07920..2b31a36319 100644 --- a/translations/zh-CN/data/reusables/sponsors/manage-updates-for-orgs.md +++ b/translations/zh-CN/data/reusables/sponsors/manage-updates-for-orgs.md @@ -1 +1 @@ -您可以指定从组织赞助的帐户接收更新的电子邮件地址。 更多信息请参阅“[管理组织赞助帐户的更新](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)”。 +您可以指定从组织赞助的帐户接收更新的电子邮件地址。 更多信息请参阅“[管理组织赞助帐户的更新](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)”。 diff --git a/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md b/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md index ef0c7dbcb8..598554d9d7 100644 --- a/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md +++ b/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md @@ -1 +1 @@ -1. （可选）如果您是组织的赞助者，要按比例支付，而不是按月全额支付，请在“Due today（今天到期）”下，单击 **Pay prorated $X.XX today（今天按比例支付 $X.XX）**。 ![链接到支付按比例计算的金额](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file +1. Optionally, if you're sponsoring as an organization, to pay a prorated amount instead of making the full monthly payment, under "Total due now", click **Pay prorated $X.XX instead**. ![链接到支付按比例计算的金额](/assets/images/help/sponsors/pay-prorated-amount-link.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md b/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md index ee10ac2b03..66e270e6c9 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 starting a monthly sponsorship on behalf of your user account, you'll immediately be charged a prorated amount for the time until your next regular billing date. 如果您代表组织进行赞助，可以选择按比例支付金额或按月全额付款。 diff --git a/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md b/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md index c908270d0c..a84fd2930a 100644 --- a/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md +++ b/translations/zh-CN/data/reusables/sponsors/review-and-publish-tier.md @@ -1 +1 @@ -1. 校对您的等级，然后单击 **Publish tier（发布等级）**。 ![发布等级按钮](/assets/images/help/sponsors/publish-tier-button.png) +1. Proofread your tier, then click **Publish _TYPE_ tier**. ![Publish monthly tier button](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/zh-CN/data/reusables/sponsors/review-tiers-to-select.md b/translations/zh-CN/data/reusables/sponsors/review-tiers-to-select.md new file mode 100644 index 0000000000..2c1f976a93 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/review-tiers-to-select.md @@ -0,0 +1 @@ +1. 在页面右侧的“Select a tier（选择等级）”下，审查可用的赞助等级。 If more than one type of tier is available "Monthly" tiers are shown, click **One-time** to show the tiers for one-time payments. ![Show "One-time" tiers](/assets/images/help/sponsors/show-one-time-tiers.png) diff --git a/translations/zh-CN/data/reusables/sponsors/select-a-tier.md b/translations/zh-CN/data/reusables/sponsors/select-a-tier.md index aaa4f8a09f..64dd7ffa1c 100644 --- a/translations/zh-CN/data/reusables/sponsors/select-a-tier.md +++ b/translations/zh-CN/data/reusables/sponsors/select-a-tier.md @@ -1 +1 @@ -1. 在页面右侧的“Select a tier（选择等级）”下，审查可用的赞助等级。 然后在您需要的等级右侧，单击 **Select（选择）**。 ![选择等级框](/assets/images/help/sponsors/select-a-tier-box.png) +1. To the right of the tier you want, click **Select**. If want to select a custom amount, enter the sponsorship amount before clicking "Select." ![选择等级框](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md b/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md index b96c2c47f4..9b3e361810 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 choose from multiple sponsorship tiers, with one-time or monthly payment amounts and benefits that are set by the sponsored account. 您的赞助将分享您帐户的现有帐单日期、付款方式和收据。 diff --git a/translations/zh-CN/data/reusables/sponsors/tier-details.md b/translations/zh-CN/data/reusables/sponsors/tier-details.md index 29fa1ccc94..c5cbaf2eba 100644 --- a/translations/zh-CN/data/reusables/sponsors/tier-details.md +++ b/translations/zh-CN/data/reusables/sponsors/tier-details.md @@ -1,3 +1,3 @@ -您最多可以创建十个赞助等级供赞助者选择。 每个等级都有自己的每月付款额（美元）和福利，如提早访问新版本或出现在项目的自述文件中。 +您最多可以创建十个赞助等级供赞助者选择。 Each tier has its own monthly or one-time payment amount in US dollars and benefits, such as receiving early access to new versions or being featured in the project's README. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). -一旦您发布某个等级，便不能编辑这个等级的价格。 而只能撤销该等级并新建一个等级。 现有赞助者将保持撤销的等级，直到他们改变赞助等级或取消其赞助。 +一旦您发布某个等级，便不能编辑这个等级的价格。 而只能撤销该等级并新建一个等级。 Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/zh-CN/data/reusables/support/accessing-premium-content.md b/translations/zh-CN/data/reusables/support/accessing-premium-content.md index ae7033cb9d..564a706cab 100644 --- a/translations/zh-CN/data/reusables/support/accessing-premium-content.md +++ b/translations/zh-CN/data/reusables/support/accessing-premium-content.md @@ -1,4 +1,4 @@ ### 访问高级内容 -您可以登录到 {% data variables.contact.contact_enterprise_portal %} 访问高级内容。 +您可以登录到 {% data variables.contact.contact_landing_page_portal %} 访问高级内容。 diff --git a/translations/zh-CN/data/reusables/support/contacting-premium-support.md b/translations/zh-CN/data/reusables/support/contacting-premium-support.md index cf521f793c..b998a7a387 100644 --- a/translations/zh-CN/data/reusables/support/contacting-premium-support.md +++ b/translations/zh-CN/data/reusables/support/contacting-premium-support.md @@ -1,4 +1,4 @@ ### 联系 {% data variables.contact.premium_support %} -{% data variables.contact.premium_support %} 客户可以使用 {% data variables.contact.contact_enterprise_portal %} 以书面（英文）形式报告问题。 您也可以通过手机获得英语支持。 要获取 {% data variables.contact.premium_support %} 电话号码，请参阅 {% data variables.contact.enterprise_portal %} 中的“[24x7 电话支持](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)”。 +{% data variables.contact.premium_support %} 客户可以使用 {% data variables.contact.contact_landing_page_portal %} 以书面（英文）形式报告问题。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user_settings/billing_plans.md b/translations/zh-CN/data/reusables/user_settings/billing_plans.md new file mode 100644 index 0000000000..8d26ab1479 --- /dev/null +++ b/translations/zh-CN/data/reusables/user_settings/billing_plans.md @@ -0,0 +1 @@ +1. In your user settings sidebar, click **Billing & plans**. ![Billing & plans settings](/assets/images/help/settings/settings-sidebar-billing-plans.png) diff --git a/translations/zh-CN/data/reusables/webhooks/discussion_desc.md b/translations/zh-CN/data/reusables/webhooks/discussion_desc.md index 1b221660e0..344e3e3a50 100644 --- a/translations/zh-CN/data/reusables/webhooks/discussion_desc.md +++ b/translations/zh-CN/data/reusables/webhooks/discussion_desc.md @@ -1 +1 @@ -`discussion` | `object` | The [`discussion`](/graphql/guides/using-the-graphql-api-for-discussions#discussion) resource. \ No newline at end of file +`discussion` | `object` | [`discussion`](/graphql/guides/using-the-graphql-api-for-discussions#discussion) 资源。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/webhooks/discussions-webhooks-beta.md b/translations/zh-CN/data/reusables/webhooks/discussions-webhooks-beta.md index 2033ca20ea..a925eeb672 100644 --- a/translations/zh-CN/data/reusables/webhooks/discussions-webhooks-beta.md +++ b/translations/zh-CN/data/reusables/webhooks/discussions-webhooks-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Webhook events for {% data variables.product.prodname_discussions %} are currently in beta and subject to change. +**注意：**{% data variables.product.prodname_discussions %} 的 web 挂钩事件目前处于测试阶段，可能会更改。 {% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/variables/contact.yml b/translations/zh-CN/data/variables/contact.yml index b8e54b2b9c..5e6040e0d6 100644 --- a/translations/zh-CN/data/variables/contact.yml +++ b/translations/zh-CN/data/variables/contact.yml @@ -24,9 +24,12 @@ contact_enterprise_portal: '[GitHub Enterprise 支持门户](https://enterprise. #Azure support (GitHub AE) portal ae_azure_portal: 'Azure 支持门户' contact_ae_portal: '[Azure 支持门户](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)' -#GitHub Support portal (for dotcom) +#GitHub Support portal (for dotcom - this sends users to a contact form) support_portal: 'GitHub 支持门户' contact_support_portal: '[GitHub 支持门户](https://support.github.com/contact)' +#GitHub Support portal (this sends users to the Support landing page) +landing_page_portal: 'GitHub 支持门户' +contact_landing_page_portal: '[GitHub 支持门户](https://support.github.com/)' #The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) community_support: 'GitHub Community Support' #The GitHub Community forum